Load Signal Data for Simulation

Load signal data for simulating a model

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.
Playback block — Load data from the workspace, a file, or the Simulation Data Inspector.
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.

Blocks

expand all

Signal Data Loading

Inport	Create input port for subsystem or external input
In Bus Element, Bus Element In	Select input from external port
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 into Simulink model
From Spreadsheet	Read data from spreadsheet
From Workspace	Load signal data from workspace into Simulink model
Playback	Load data from workspace, file, or Simulation Data Inspector (Since R2022b)
Signal Editor	Display, create, edit, and switch interchangeable scenarios

Functions

expand all

Signal Data Loading

`createInputDataset`	Generate dataset object for root-level Inport or bus element ports in model
`Simulink.Bus.createMATLABStruct`	Create MATLAB structures that use same hierarchy and attributes as buses
`Simulink.SimulationData.createStructOfTimeseries`	Create structure of `timeseries` data to load as simulation input for bus
`getRootInportMap`	Create custom object to map signals to top-level input ports
`getInputString`	Create comma-separated list of variables to map
`getSupportedFileTypes`	Return file type of signals in spreadsheet file (Since R2024b)
`loadScenarioToWorkspace`	Load scenario to base workspace (Since R2024b)
`mapDataToInport`	Map data to root input ports (Since R2024b)
`convertToSLDataset`	Convert contents of MAT file to `Simulink.SimulationData.Dataset` object in another MAT file
`getSlRootInportMap`	Create custom object to map signals to root-level inports using Simulink mapping mode
`signalBuilderToSignalEditor`	Import signal data and properties from Signal Builder block to Signal Editor block
`Simulink.playback.createSignals`	Create `Simulink.playback.Signal` object to add to Playback block (Since R2024a)

Objects

expand all

Signal Data Loading

`Simulink.playback.Signal`	Container for signals to add to Playback block (Since R2024a)
`Simulink.SimulationData.DatasetRef`	Create `Simulink.SimulationData.DatasetRef` object
`Simulink.SimulationData.Dataset`	Access logged simulation data or group simulation input data
`matlab.io.datastore.SimulationDatastore`	Datastore for inputs and outputs of Simulink models

Tools

Root Inport Mapper

Import, visualize, and map signal and bus data to root-level inports

Model Settings

Input

Option to load external input data for simulation using top-level input ports

Topics

Signal Loading

Provide Signal Data for Simulation
Identify model signal data requirements and load input signal data.
Overview of Signal Loading Techniques
Understand the techniques available for importing signal data into a model.
Comparison of Signal Loading Techniques
Determine the signal loading approach that meets your modeling requirements. Often, mapping signal data to root inports works well.
Control How Models Load Input Data
Control how a simulation loads input data using block parameters, model parameters, and different input data formats.
Load Signal Data That Uses Units
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 Data Logged in Another Simulation
Load signal data into a model that was logged in a previous simulation.
Load Data to Represent Variable-Step Input from Model Hierarchy
Capture dynamics in external input data for a continuous signal by specifying additional time steps for a variable-step solver.
Load Input Data for Basic Test Cases
Create input data for a basic test of model behavior.

Load Data to Root-Level Input Ports

Load Data to Root-Level Input Ports
Load data from a workspace and apply it to a root-level input.
Load Bus Data to Root-Level Input Ports
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.
Map Data Using Root Inport Mapper Tool
To import, visualize, and map signal and bus data to root inports, use the Root Inport Mapper tool.
Map Root Inport Signal Data
Open the Root Inport Mapper Tool and select the map mode.
Create Signal Data for Root Inport Mapping
Create data for root inport mapping using specific guidelines and conventions.
Map Signal Data to Root Input Ports
Map signal data to root input ports by selecting map modes and options and selecting data. Interpret mapping results.
Import Signal Data for Root Inport Mapping
Import signal and bus data for root inport mapping. You can also import test vectors from Simulink^® Design Verifier™ environment.
Create and Use Custom Map Modes
Create custom map modes if you do not want to use existing map modes in the Root Inport Mapper tool.
Root Inport Mapping Scenarios
Work with scenarios in the Root Inport Mapper tool. Create and save scenarios, and load previously saved scenarios.
Generate MATLAB Scripts for Simulation with Scenarios
After associating a scenario with the model, generate a MATLAB^® script to perform batch simulations.
Import Custom File Type
Import custom file types to Signal Editor or Root Inport Mapper.
Create Custom File Type for Import
To import custom file types to Signal Editor and Root Inport Mapper, create custom file type readers for your data.

Other Signal Loading Techniques

Load Input Data for Bus Using In Bus Element Blocks
Load input data for a bus using In Bus Element blocks.
Load Data Using the From Workspace Block
Load simulation input data using the From Workspace block.
Load Data Using the From File Block
Create and save signal data to load from a MAT file using the From File block.
Load Data Using Playback Block
Load data from the workspace, a file, and the Simulation Data Inspector using the Playback block.
Load Big Data for Simulations
Load big data as simulation input.
Stream Data from a MAT-File as Input for a Parallel Simulation
Stream input data for parallel simulations from a MAT-file.
Load Data with Interchangeable Scenarios
Use Signal Editor block to work with interchangeable scenarios.

Related Information

Featured Examples

Using Mapping Modes with Custom-Mapped External Inputs

Implement a custom mapping algorithm that is similar to a Simulink mapping mode.

Open Model