Main Content

Export Signal Data Using Signal Logging

Signal Logging

To capture signal data from a simulation, usually you can use signal logging. Mark the signals that you want to log and enable signal logging for the model. For details, seeConfigure a Signal for Loggingand启动信号测井模型.

For a summary of other approaches to capture signal data, seeExport Simulation Data.

Signal Logging Workflow

To collect and use signal logging data, perform these tasks.

  1. Mark individual signals for signal logging. SeeConfigure a Signal for Logging.

  2. Enable signal logging for a model. See启动信号测井模型.

  3. Simulate the model.

  4. Access the signal logging data. SeeView and Access Signal Logging Data.

Log Subsets of Signals

One approach for testing parts of a model as you develop it is to mark a superset of signals for logging and then override signal logging settings to select different subsets of signals for logging. You can use the Signal Logging Selector or a programmatic interface. SeeOverride Signal Logging Settings.

Use this approach to log signals in models that use model referencing. For an example, seeViewing Signals in Model Reference Instances.

Additional Signal Logging Options

With the basic signal logging workflow, you can specify additional options related to the data that signal logging collects and to how that data is displayed. You can:

Signal Logging Limitations

Signal logging does not support:

  • Signals inside Stateflow®charts for rapid accelerator simulations.

  • Input signals for Function-Call subsystems, If Action subsystems, or Switch Case Action subsystems.

  • Input signals forMergeblocks.

  • Bus signals insideFor Eachsubsystems.

  • Signals in referenced models insideFor Eachsubsystems when:

    • The model containing theFor Eachsubsystem simulates in rapid accelerator mode.

    • TheFor Eachsubsystem is inside a referenced model simulated in accelerator mode.

  • State port signals forIntegratorandDiscrete-Time Integratorblocks that show the state port.

Related Topics