How can I stop logging signals in a model which appear under extmode_sf_data in the data inspector?

When running a model in external mode (TI C2000) I see in the data inspector extmode_sf_data and Signals.

Under signals I see signals which I have selected in the model by right clicking and selecting Log Selected Signals. However the signals under extmode_sf_data I have not selected (as far as I know). I also can not find them under Signal Monitoring & Tracing ==> Configure Logging. I do not need them. There also seems to be no logic in why these signals are selected. I think it is also adding extra data which I do not need. So How can I stop logging signals in a model which appear under extmode_sf_data in the data inspector?

Answer 1

[Rasmita]

Hi,

It is my understanding that, you want to stop logging signals which appear under “extmode_sf_data”. While viewing the simulation output in SDI, with the Simulink model running in External mode, the “Inspect” pane lists all the selected signals for logging under “Signals” tab, along with an extra tab “extmode_sf_data”.

In order to stop signals from logging, you can use following functionality by specifying log as ‘off’:

Simulink.sdi.markSignalForStreaming()

For more information on this functionality refer below documentation and the example given in it:

https://www.mathworks.com/help/simulink/slref/simulink.sdi.marksignalforstreaming.html

Hope this helps!

Regards,

Rasmita

[N/A]

Hello Rasmita, thanks for your answer. The method you are proposing involves scripting or using the command line. This is not very efficient since I did not select these signals in the first place. The most simple and easy way for me would be selecting or deselecting a signal for logging in the model by right clicking or using the Simulink Signal Logging Selector.

This issue applies to a tab parameters and ext mode_sf_data which I see in the data inspector.

Currently we are also working with R2023a here I, with another model, we do not have this issue. After the updating the model, where I encounter this issue, to R2023a I will post an update if the issue is still there.