Simulation Data Inspector - empty SIL data

Hi everyone. Hope no one asked about this issue before, I didn’t find anything similar.

Running Matlab/Simulink R2020a on Linux 18.04 OS.

Trying the tutorial you can find here: https://it.mathworks.com/help/rtw/gs/verify-whether-simulation-results-match-generated-executable-program-results.html. The only difference is the setup for XCP TCP/IP, because I’m trying to test everything on the same pc: I’d like to see if the generated C code is returning me the same output I obtain with the Simulink model, running everything on my own pc. So I thought that could be useful to set up “ert.tlc” file to be generated, with “Hardware board: None” option setup.

Everything works as expected until the “Compare Simulation and Executable Program Results” section of the tutorial. Then, after finishing previous “Monitor & Tune” run named “Run 2”, it seems that the content of the last “Run 2” inside the “Simulation Data Inspector” window is completely empty: I’m not able to display “X” nor “Force: f(t):1”, there are no signals that I can select. Moreover, the log data variable named “logsout” (that’s properly logging “X” and “Force: f(t):1” on the first Simulink model run named “Run 1”) gets cleared when passing to the next “Monitor & Tune” run.

Is there any setting that I have to add or change? Or am I doing any mistake in the system’s configuration? Maybe possible issues related to Matlab version?

Thanks in advance.

Answer 1

[Saarthak Gupta]

Hi Lore,

The steps seem to work fine on Windows, MATLAB/Simulink R2020a. The system target file was set to ert.tlc, and the Hardware board was set to None as well. The Simulink Data Inspector correctly shows all logged signals in the respective run windows.

It may be a platform and/or version specific issue. I suggest you try it on a Windows machine, or on a newer version of MATLAB/Simulink (e.g., R2023a).

Before clicking on Monitor & Tune, please ensure that the Transport Layer is configured to XCP on TCP/IP (and not tcpip or serial)

A possible workaround for logsout being cleared could be to save the variable to an external mat file and loading it into the workspace after Monitor & Tune has executed.

To save the "logsout" file locally, as "out.mat":

save out.mat logsout;

To load the logsout file once Monitor & Tune has executed:

logsout = load(out.mat);