SIL Verification Mode: Logged signals not available in SIL run

I am running SIL Verification on my model. However, after running in both Simulation (MIL) and SIL, many of the logged signals are only available from the Simulation run, and those signals cannot be compared with the SIL run.

Looking into which signals are logged, it appears only the inputs to the model are logged in both MIL and SIL, but outputs are only logged in MIL.

Is there a setting I am missing?

Answer 1

[Jaskirat]

Hello @Yousaf

I understand that you are unable to see all the signals in your model during SIL simulation.

This is because SIL/PIL blocks do not support internal signal logging. To do so, you can refer to the following steps:

• Log the signals using “Logging Badge” icon above the signal or using Signal Logging Selector (Simulation > Data Inspector > Signal Logging Selector).
• Go to Model Configuration Parameters:

Code Generation > Interface:

Set MAT-file logging to on.

For Embedded Coder: Code Generation > Verification > Test Point Signals: Enable "Log test point signals".

• Mark signals as "Test Points":

Right-click the signal, select Properties, and check "Test Point".

Only test point signals can be logged in SIL.

You can refer to the following documentation for more details:

https://www.mathworks.com/help/ecoder/ug/configuring-a-sil-or-pil-simulation.html#bsf5v22_sep_br74o58-1

You might encounter some limitations with “Virtual Signals” corresponding to signals being optimized during code generation. The workaround for such signals is provided in the following link:

https://www.mathworks.com/help/simulink/ug/working-with-test-points.html

Hope this helps!

[Yousaf]

The signals are already selected for logging.

The Mat-file logging option is not available, possibly due to the choice of TLC (Autosar).

When making the signals Test Points, I get the following error:

Output argument "preprocessor Flags" (and maybe others) not assigned during call to "coder.internal.getToolchain Custom Defines"

[Jaskirat]

Hi,

Since MAT-File logging is unavailable for Autosar TLC, you can try the following workaround using "External Mode" with XCP communication.

• In your model, navigate to Model Configuration Parameters > Code Generation > Interface.
• Enable External mode and select XCP on TCP/IP as the transport layer.
• Ensure that the necessary signals are marked for logging.
• Build and deploy the model.
• Use the Simulation Data Inspector to monitor and log signals during execution.

You can refer to the following links for more details:

https://www.mathworks.com/videos/external-mode-simulation-with-xcp-communication-1597834777195.html

https://www.mathworks.com/help/autosar/ug/configure_externalmode.html