Guy on Simulink

Simulink & Model-Based Design

Importing variable-step signals into Simulink

This week I received the following question from a Simulink user:

I have a data acquisition system which saves signals at variable intervals. I want to import this data into a variable-step simulation. When I use the From Workspace block, the Simulink variable-step solver seems to take large steps and skip some of my points. How can I force the solver to take steps at the times specified in my input data?

Generating a variable-step signal

To illustrate this problem, I will generate data using one variable-step simulation and try to input it into another. To begin I simulate the following model using the ode15s stiff solver:

Example Simulink model using a variable-step solver

When inspecting the logged data, we can see that the step size is not constant:

logged variable-step signal

Importing the signal into a model

To import this data in a simulation, I use a root-level Inport block.

Model where the data is imported

Since the data to import is continuous, I enable the Interpolate option of the Inport block:

Enable Interpolation

Then I configure the model to use the saved data as input:

Load From Workspace

Reproducing the problem

The Simulink variable-step solvers adjusts the step size during the simulation to achieve the specified tolerance for state error as defined in the model configuration. The variable-step solver does not have to take steps at the times specified in the imported data. In my example model, when I run the simulation, the imported signal looks like:

Signal read by default

The solution

We need to instruct the Simulink variable-step solver to execute at the times specified by the imported data. To do this, open the Data Import/Export configuration pane and look at the Save options section. Set the Output options to “Produce additional output”, and specify the time points of the imported data as the Output times.

Output options: Produce Additional outputs

Now the imported data looks as expected.

Signal reads correctly

Additional Note

For optimal performance, I recommend pre-processing the data before importing it. For example if your signal contains points very close in time with similar values, you can filter them out. This will make your simulation run faster. Let me know if you would like to see a follow up post on that topic.

Now it's your turn

Did you ever encountered problems when importing data into Simulink? Do you have tricks to recommend? Leave a comment here

  • print


To leave a comment, please click here to sign in to your MathWorks Account or create a new one.