Choose a SIL or PIL Approach

Consider a top model that consists of components A, B, C, and D:

A and B are existing components for which code has previously been generated and tested.
C, a referenced model, and D, a subsystem, are new components.

With software-in-the-loop (SIL) and processor-in-the-loop (PIL) simulations, you can use the following approaches to numerical equivalence testing:

Test code from all components together. See Test Top-Model Code.
Test new components separately (before testing code from all components). See Test Referenced Model Code and Test Subsystem Code.

For some forms of testing, you require a test harness model. The test harness model:

Generates test vectors or stimulus inputs that feed the block under test.
Makes it possible for you to observe or capture output from the block.

The following example shows a simple test harness model.

The block under test is a Model block. The Sine Wave block generates the input for the Model block. Through the Scope block, you can observe the output from the Model block. For information about creating and using test harnesses, see Create Test Harnesses and Select Properties (Simulink Test) and Code Generation Verification Workflow with Simulink Test (Simulink Test).

Test Top-Model Code

To test code generated from the top-model components together (A, B, C, and D), you can use top-model SIL/PIL or Model block SIL/PIL.

Top-model SIL/PIL:
1. Create test vectors or stimulus inputs in the MATLAB workspace.
2. Run the top model in normal, SIL, and PIL simulation modes. The software loads the test vectors or stimulus inputs from the MATLAB^® workspace.
3. For each simulation mode, observe or capture outputs.
4. Verify numerical equivalence by comparing normal outputs against SIL and PIL outputs.
Model block SIL/PIL:
1. Create a Model block that contains the top-model components.
2. Insert the Model block in a simulation model, for example, your test harness model.
3. Run simulations, switching the Model block between normal, SIL, and PIL modes. For the SIL and PIL simulation modes, set the Code interface Model block parameter to Top model.
4. Verify numerical equivalence by comparing normal outputs against SIL and PIL outputs.

For more information, see Simulation with Top Model and SIL/PIL Manager Verification Workflow.

Test Referenced Model Code

To test code generated from the component C as part of a model reference hierarchy, use the Model block SIL/PIL approach:

Insert the Model block C in a simulation model, for example, your test harness model.
Run simulations, switching the Model block between normal, SIL, and PIL modes. For the SIL and PIL simulation modes, set the Code interface Model block parameter to Model reference.
Verify numerical equivalence by comparing normal outputs against SIL and PIL outputs.

For more information, see Simulation with Model Blocks and SIL/PIL Manager Verification Workflow.

Test Subsystem Code

To test code that is generated from the subsystem D, use one of these workflows.

Workflow Description

Simulink Test harness with SIL/PIL Manager

Workflow	Description
Simulink Test harness with SIL/PIL Manager	Perform unit tests on subsystem code that is part of the code generated from the parent model. Generate code for the model that contains the subsystem by running `slbuild(model)` or `slbuild(model, 'RTWModelReferenceTargetOnly')`. In the model, right-click the subsystem and then create a test harness for the subsystem. Open the SIL/PIL Manager. If required, enable code coverage analysis. Then run back-to-back model and SIL or PIL simulations. If required, export an equivalence test case. For more information, see Test Atomic Subsystem Generated Code. If the subsystem is not supported by this workflow, use the SIL or PIL block workflow. For more information about unsupported subsystems and other limitations, see Atomic Subsystem Workflow Limitations.
SIL or PIL block	Generate and test new standalone code from the subsystem. Insert the subsystem in a simulation model, for example, your test harness model. Run a normal mode simulation, capturing the outputs. Create a SIL or PIL block from the subsystem. In the model, replace the subsystem with the SIL or PIL block. Run a simulation of the model, capturing the outputs. Verify numerical equivalence by comparing normal mode subsystem outputs against SIL or PIL block outputs. For more information, see SIL or PIL Block Simulation.

Perform unit tests on subsystem code that is part of the code generated from the parent model.

Generate code for the model that contains the subsystem by running slbuild(model) or slbuild(model, 'RTWModelReferenceTargetOnly').
In the model, right-click the subsystem and then create a test harness for the subsystem.
Open the SIL/PIL Manager. If required, enable code coverage analysis. Then run back-to-back model and SIL or PIL simulations.
If required, export an equivalence test case.

For more information, see Test Atomic Subsystem Generated Code.

If the subsystem is not supported by this workflow, use the SIL or PIL block workflow. For more information about unsupported subsystems and other limitations, see Atomic Subsystem Workflow Limitations.

SIL or PIL block

Generate and test new standalone code from the subsystem.

Insert the subsystem in a simulation model, for example, your test harness model.
Run a normal mode simulation, capturing the outputs.
Create a SIL or PIL block from the subsystem.
In the model, replace the subsystem with the SIL or PIL block.
Run a simulation of the model, capturing the outputs.
Verify numerical equivalence by comparing normal mode subsystem outputs against SIL or PIL block outputs.

For more information, see SIL or PIL Block Simulation.

Summary

Component From Which Code Is Generated	Simulation Uses	Steps	Generated Code Interface	Test Signal Source
Top model	Top-model SIL/PIL	In SIL/PIL Manager: Select SIL/PIL Simulation Only mode. In System Under Test, select `Top model`.	Standalone	MATLAB workspace
Model referenced by Model block	Model block SIL/PIL	In SIL/PIL Manager: Select SIL/PIL Simulation Only mode. In System Under Test, select `Model blocks in SIL/PIL mode`. In Model blocks, set Simulation mode to `Software-in-the-loop (SIL)` or `Processor-in-the-loop (PIL)`.	Determined by Model block parameter Code interface –– standalone or model reference.	Simulation model, for example, test harness model
Subsystem	Simulink Test harness and SIL/PIL Manager	Generate code for model that contains the atomic subsystem. Create a test harness for the subsystem. From SIL/PIL Manager, run back-to-back model and SIL or PIL simulations. If required, export equivalence test case.	Determined by generated parent model code –– standalone or model reference.	Simulink^® Test™ harness
Subsystem	SIL or PIL block	Manual block substitution	Standalone	Simulation model, for example, test harness model.