You can test your system in environments that resemble your application. You begin with model simulation on a development computer, then use software-in-the-loop (SIL) and processor-in-the-loop (PIL) simulations. Real-time testing executes an application on a standalone target computer that can connect to a physical system. Real-time testing can include effects of timing, signal interfaces, system response, and production hardware.
Real-time testing includes:
Rapid prototyping, which tests a system on a standalone target connected to plant hardware. You verify the real-time tests against requirements and model results. Using rapid prototyping results, you can change your model and update your requirements, after which you retest on the standalone target.
Hardware-in-the-loop (HIL), which tests a system that has passed several stages of verification, typically SIL and PIL simulations.
This example workflow describes the major steps of creating and executing a real-time test:
Create test cases that verify the model against requirements. Run the model simulation tests and save the baseline data.
Set up the real-time target computer.
Create test harnesses for real-time testing, or reuse model simulation test
harnesses. In Test Sequence or Test Assessment
verify statements assess the real-time execution. In
the test harnesses, use target and host scopes to display signals during
In the Test Manager, create real-time test cases.
For the real-time test cases, configure target settings, inputs, callbacks, and iterations. Add baseline or equivalence criteria.
Execute the real-time tests.
Analyze the results in the Test Manager. Report the results.
Baseline or equivalence comparisons can fail because of missing data or time-shifted data from the real-time target computer. When investigating real-time test failures, look for time shifts or missing data points.
You cannot override the real-time execution sample time for applications built from models containing a Test Sequence block. The code generated for the Test Sequence block contains a hard-coded sample time. Overriding the target computer sample time can produce unexpected results.
Your target computer must have a file system to use
statements and test case logging.
Real-time testing often takes longer than comparative model testing, especially if you execute a suite of real-time tests that cover several scenarios. Before executing real-time tests, complete requirements-based testing using desktop simulation. Using the desktop simulation results:
Debug your model or make design changes that meet requirements.
Debug your test sequence. Use the debugging features in the Test Sequence Editor. See Debug a Test Sequence.
Update your requirements and add corresponding test cases.
Real-time testing requires a standalone target computer. Simulink® Test™ only supports target computers running Simulink Real-Time™. For more information, see:
Real-time applications require specific configuration parameters and signal properties.
A real-time test case requires a real-time system target file. In the model or
harness configuration parameters, in the Code Generation pane,
set the System target file to
generate system target code.
If your model requires a different system target file, you can set the parameter
using a test case or test suite callback. After the real-time test executes, set the
parameter to its original setting with a cleanup callback. For example, this
callback opens the model and sets the system target file parameter to
slrt.tlc for the model
open_system(fullfile(matlabroot,'toolbox','simulinktest',... 'simulinktestdemos','sltestProjectorController')); set_param('sltestProjectorController','SystemTargetFile','slrt.tlc');
Models must use a data format other than
set the data format:
Open the configuration parameters.
Select the Data Import/Export pane.
Select the Format.
To configure your signals of interest for real-time testing:
Enable signal logging in the Configuration Parameters, in the Data Import/Export pane.
Connect signals to Scope blocks from the Simulink
Real-Time block library. Set the Scope type
Name each signal of interest using the signal properties. Unnamed signals can be assigned a default name which does not match the name of the baseline or equivalence signal.
In this example test harness, the logged signals:
Have explicit names.
Use file scopes to return signal data to the Test Manager.
Use target scopes to display data on the target computer.
To display signals on the target computer during real-time execution, add target scopes to your test harness. To display signals in the Simulink Real-Time Explorer, add host scopes. This test harness includes both target and host scopes for signal visualization. See Scope.
Use the Test Manager to create real-time test cases. In the toolstrip, click New > Real-Time Test.
You can select a baseline, equivalence, or simulation real-time test. For
simulation test types,
verify statements serve as pass/fail
criteria in the test results. For equivalence and baseline test types, the
equivalence or baseline criteria also serve as pass/fail criteria.
Baseline — Compares the signal data returned from the target computer to the baseline in the test case. To compare a real-time execution result to a model simulation result, add the model baseline result to the real-time test case and apply optional tolerances to the signals.
Equivalence — Compares signal data from a simulation and a real-time test, or two real-time tests. To run a real-time test on the target computer, then compare results to a model simulation:
Select Simulation 1 on target.
Clear Simulation 2 on target.
The test case displays two simulation sections, Simulation 1 and Simulation 2.
Comparing two real-time tests is similar, except that you select both simulations on target. In the Equivalence Criteria section, you can capture logged signals from the simulation and apply tolerances for pass/fail analysis.
Simulation: Assesses the test result using only
verify statements and real-time execution. If no
verify statements fail, and the real-time test executes,
the test case passes.
Using this option, specify how you want to load the real-time application. The real-time application is built from your model or test harness. You can load the application from:
Model — Choose
Model if you are running the real-time test
for the first time, or your model changed since the last real-time
Model typically takes the longest
because it includes model build and download.
Model loads the application from the model,
builds the real-time application, downloads it to the target computer, and
executes it on the target computer.
Target Application — Choose
Target Application to send the target
application from the host to a target computer, and execute the application.
Target Application can be useful if you want
to load an already-built application on multiple targets.
Target Computer — This option executes an
application that is already loaded on the real-time target computer. You can
update the parameters in the test case and execute using
This table summarizes which steps and callbacks execute for each option.
|Test Case Execution Step (first to last)||Load Application From|
|Model||Target Application||Target Computer|
|Executes pre-load callback||Yes||Yes||Yes|
|Loads Simulink model||Yes||No||No|
|Executes post-load callback||Yes||No||No|
|Sets Signal Builder group||Yes||No||No|
|Builds real-time application from model||Yes||No||No|
|Downloads real-time application to target computer||Yes||Yes||No|
|Sets runtime parameters||Yes||Yes||Yes|
|Executes pre-start real-time callback||Yes||Yes||Yes|
|Executes real-time application||Yes||Yes||Yes|
|Executes cleanup callback||Yes||Yes||Yes|
Select the model from which to generate the real-time application.
If you use a test harness to generate the real-time application, select the test harness.
For real-time tests, you can override the simulation stop time, which can be
useful in debugging a real-time test failure. Consider a 60-second test that returns
verify statement failure at 15 seconds due to a bug in the
model. After debugging your model, you execute the real-time test to verify the fix.
You can override the stop time to terminate the execution at 20 seconds, which
reduces the time it takes to verify the fix.
Real-time tests offer a Pre-start real-time application callback which executes commands just before the application executes on the target computer. Real-time test callbacks execute in a sequence along with the model load, build, download, and execute steps. Callbacks and step execution depends on how the test case loads the application.
Load application from:
Load application from:
Load application from:
Pre-start real-time callback
Pre-start real-time callback
Pre-start real-time callback
You can execute iterations in real-time tests. Iterations are convenient for executing real-time tests that sweep through parameter values or Signal Builder groups. Results appear grouped by iteration. For more information on setting up iterations, see Test Iterations. You can create:
Tabled iterations from a parameter set — Define several parameter sets in the Parameter Overrides section of the test case. Under Iterations > Table Iterations, click Auto Generate and select Parameter Set.
Tabled iterations from signal builder groups — If your model or test harness uses a signal builder input, under Iterations > Table Iterations, click Auto Generate and select Signal Builder Group. If you use a signal builder group, load the application from the model.
Scripted iterations — Use scripts to iterate using model variables
or parameters. For example, in the model
SettlingTest harness uses a Test
Sequence block to create a square wave test signal for the
oscillator system using the parameter
In the test file
SettlingTestCases, the real-time test
scripted iterations cover a frequency sweep from 5 Hz to 35 Hz. The script
iterates the value of
frequency in the Test
%% Iterate over frequencies to determine best oscillator settings % Create parameter sets freq = 5.0:1.0:35.0; for i_iter = 1:length(freq) % Create iteration object testItr = sltestiteration(); % Set parameters setVariable(testItr,'Name','frequency','Source','Test Sequence',... 'Value',freq(i_iter)); % Register iteration addIteration(sltest_testCase, testItr); end
In addition to baseline and equivalence signal comparisons, you can assess real-time
test execution using
verify statements. A
statement assesses a logical expression and returns results to the Test Manager. Use
verify inside a Test Sequence or Test
Assessment block. See Assess Model Simulation Using verify Statements.