You can use several different approaches to load data into a model, including:
Root-level input ports — Import signal data from a workspace, using the Input configuration parameter to import it to a root-level input port of a Inport, Enable, or Trigger block. To import many signals to root-level input ports, consider using the Root Inport Mapper tool.
From File block — Read data from a MAT-file, outputting the data as a signal.
From Spreadsheet block — Read data from Microsoft® Excel® spreadsheets or CSV spreadsheets, outputting the data as one or more signals.
Source blocks — Add a source block, such Sine Wave block, to generate signals to input to another block.
Signal Editor block — Display, create, edit, and switch interchangeable scenarios.
Persistent data — Stream big data from a MAT-file into a model.
You can create input signal data in a file, workspace variable, or model parameter. You can use data logged in a previous simulation, from another source, or create the data yourself. To determine which signal loading approach to use, see Comparison of Signal Loading Techniques.
|Inport||Create input port for subsystem or external input|
|Enable||Add enable port to subsystem or model|
|Trigger||Add trigger or function port to subsystem or model|
|From File||Load data from MAT-file|
|From Spreadsheet||Read data from spreadsheet|
|From Workspace||Load signal data from workspace into Simulink model|
|Signal Builder||Create and generate interchangeable groups of signals whose waveforms are piecewise linear|
|Signal Editor||Display, create, edit, and switch interchangeable scenarios|
|Create custom object to map signals to root-level inports|
|Convert contents of MAT-file to |
|Create custom object to map signals to root-level inports using Simulink mapping mode|
|Generate dataset object for root-level Inport or bus element ports in model|
|(Not recommended) Create and access Signal Builder blocks|
|Import signal data and properties from Signal Builder block to Signal Editor block|
|Create comma-separated list of variables to map|
|Return initial state data of block diagram|
|Create MATLAB structures that use the same hierarchy and attributes as buses|
|Create structure of |
|Start Signal Editor|
Identify model signal data requirements and load input signal data.
Understand the techniques available for importing signal data into a model.
Determine the signal loading approach that meets your modeling requirements. Often, mapping signal data to root inports works well.
Load signal data that uses units from data logged in a previous simulation. Signal logging, the To File block, and the To Workspace block can include units information for Dataset or Timeseries logging formats.
Load signal data into a model that was logged in a previous simulation.
Import signal data to a continuous plant model, which uses signal data that is smooth and uninterrupted in time, with a signal data for each time value.
Test a discrete algorithm by importing discrete signals, which are signals that you define using evenly spaced time values. One signal value is read at each time step, using the sample time of the source block.
When you import signal data for most input test cases, try to minimize the number of time points. The signal data that you load includes samples with ramps and discontinuities.
Load data from a workspace and apply it to a root-level input.
Import bus data to top-level input ports by manually specifying the data in the Input configuration parameter or by using the Root Inport Mapper tool.
To import, visualize, and map signal and bus data to root inports, use the Root Inport Mapper tool.
Open the Root Inport Mapper Tool and select the mapping mode.
Create data for root inport mapping using specific guidelines and conventions.
Use the Signal Editor to create and edit input signals that you can organize for root-level port mapping or multiple simulations.
View and inspect signal data before mapping the data.
Preview input signal or bus data with the Signal Preview window.
Map signal data to root input ports by selecting map modes and options and selecting data. Interpret mapping results.
Import signal and bus data for root inport mapping. You can also import test vectors from Simulink® Design Verifier™ environment.
Create custom map modes if you do not want to use existing map modes in the Root Inport Mapper tool.
Work with scenarios in the Root Inport Mapper tool. Create and save scenarios, and load previously saved scenarios.
After associating a scenario with the model, generate a MATLAB® script to perform batch simulations.