Documentation

This is machine translation

Translated by Microsoft
Mouseover text to see original. Click the button below to return to the English verison of the page.

Note: This page has been translated by MathWorks. Please click here
To view all translated materals including this page, select Japan from the country navigator on the bottom of this page.

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, see Configure a Signal for Logging and Enable Signal Logging for a Model.

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

Signal Logging Workflow

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

  1. Mark individual signals for signal logging. See Configure a Signal for Logging.

  2. Enable signal logging for a model. See Enable Signal Logging for a Model.

  3. Simulate the model.

  4. Access the signal logging data. See 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. Then overriding signal logging settings to select different subsets of signals for logging. You can use the Signal Logging Selector or a programmatic interface. See Override Signal Logging Settings.

Use this approach to log signals in models that use model referencing. See Models with Model Referencing: Overriding Signal Logging Settings.

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 in Rapid Accelerator Mode

Signal logging in rapid accelerator mode does not log the following kinds of signals. When you update or simulate a model that contains these signals, Simulink® displays a warning that those signals are not logged.

  • Signals inside Stateflow® charts

  • Signals that use a custom data type

If you set the Configuration Parameters > Solver > Periodic sample time constraint parameter to Ensure sample time independent, you cannot use signal logging in rapid accelerator mode.

Signal Logging Limitations

  • Rapid accelerator mode supports signal logging, with the requirements and limitations described in Signal Logging in Rapid Accelerator Mode.

  • Top-model and Model block software-in-the-loop (SIL) and processor-in-the-loop (PIL) simulation modes support signal logging. For a description of limitations, see Top-Model SIL/PIL Limitations (Embedded Coder) and Model Block SIL/PIL Limitations (Embedded Coder).

  • Array of buses signals support signal logging, with the requirements described in Import Array of Buses Data.

  • You cannot log signals in For Each subsystems.

  • If you configure a bus signal or bus element for signal logging that is an input to a subsystem, you cannot automatically refactor the subsystem interface to use In Bus Element and Out Bus Element blocks. For details about that refactoring, see Convert Models to Use Bus Element Ports.

  • You cannot log local data in Stateflow Truth Table blocks.

Related Examples

More About

Was this topic helpful?