{"id":18656,"date":"2026-05-05T18:12:43","date_gmt":"2026-05-05T22:12:43","guid":{"rendered":"https:\/\/blogs.mathworks.com\/simulink\/?p=18656"},"modified":"2026-05-05T18:12:43","modified_gmt":"2026-05-05T22:12:43","slug":"logging-simscape-variables-like-simulink-signals","status":"publish","type":"post","link":"https:\/\/blogs.mathworks.com\/simulink\/2026\/05\/05\/logging-simscape-variables-like-simulink-signals\/","title":{"rendered":"Logging Simscape variables like Simulink Signals"},"content":{"rendered":"
\"\"<\/img><\/a><\/div>
Did you know that starting in R2024a, it is possible to log Simscape variables like if they were Simulink signals?<\/span><\/div>
Let's see how that works.<\/span><\/div>

The Problem<\/span><\/h2>
Here is a pattern I often see in Simscape models. To log variables from Simscape blocks, users add sensor blocks and <\/span>PS-Simulink Converter<\/span><\/a>, and then log the output Simulink signal.<\/span><\/div>
mdl = <\/span>'CavitationInTwoPhaseFluid'<\/span>;<\/span><\/span><\/div><\/div>
open_system(mdl)<\/span><\/span><\/div><\/div><\/div>
\"\"<\/img><\/div>
After simulating, you can access all logged signals in the <\/span>logsout<\/span>.<\/span><\/div>
out = sim(mdl);<\/span><\/span><\/div><\/div>
out.logsout<\/span><\/span><\/div>
ans = <\/span><\/div>
Simulink.SimulationData.Dataset 'logsout' with 3 elements\r\n\r\n <\/strong> <\/strong> Name <\/strong> BlockPath <\/strong>\r\n <\/strong> <\/strong> ____________ <\/strong> ________________________________________ <\/strong>\r\n 1 [1x1 Signal] Pconverter ...InTwoPhaseFluid\/PS-Simulink Converter\r\n 2 [1x1 Signal] Displacement ...nTwoPhaseFluid\/PS-Simulink Converter1\r\n 3 [1x1 Signal] Psource CavitationInTwoPhaseFluid\/Sine Wave \r\n\r\n - Use braces { } to access, modify, or add elements using index.\r\n<\/div><\/div><\/div><\/div><\/div><\/div>
While it is a perfectly valid pattern, adding sensor blocks just to log signals is inefficient. This adds blocks to the model, impacting the performance and clarity of the model.<\/span><\/div>

Simscape Logging - A non-ideal workaround<\/span><\/h3>
For as far as I can remember, <\/span>Simscape offers its own logging<\/span><\/a> that is separate from Simulink logging. While it is useful for debugging purposes using the <\/span>Simscape Results Explorer<\/span><\/a>, I find it less convenient for writing more robust and scalable post-processing code. For example, to access the data for the Displacement signal from above, I would need this line of code:<\/span><\/div>
out.simlog_CavitationInTwoPhaseFluid.Translational_Mechanical_Converter_2P.interface_displacement.series.values;<\/span><\/span><\/div><\/div><\/div>
This returns an array of double numbers instead of the <\/span>timeseries<\/span><\/a> or <\/span>timetable<\/span><\/a> like the signals logged in Simulink.<\/span><\/div>
Let's look at a better way.<\/span><\/div>

Simscape Instrumentation Table<\/span><\/h2>
To directly log a Simscape variable like a Simulink signal, start by selecting the block in the canvas. Go to the <\/span>Simscape Block<\/span> tab in the Simulink toolstrip and click <\/span>Instrumentation Table<\/span>. This will open the Model Editor panel with the Simscape Variables tab selected. <\/span><\/div>
In this panel, you can see all the variables for the selected block, enable logging for the ones you want and specify the name of the logged signals.<\/span><\/div>
\"\"<\/img><\/div>
After making those changes, I can simulate the new model and confirm that the results are the same<\/span><\/div>
mdl = <\/span>'CavitationInTwoPhaseFluidSSCLog'<\/span>;<\/span><\/span><\/div><\/div>
open_system(mdl)<\/span><\/span><\/div><\/div>
outAfter = sim(mdl);<\/span><\/span><\/div><\/div>
outAfter.logsout<\/span><\/span><\/div>
ans = <\/span><\/div>
Simulink.SimulationData.Dataset 'logsout' with 3 elements\r\n\r\n <\/strong> <\/strong> Name <\/strong> BlockPath <\/strong>\r\n <\/strong> <\/strong> ____________ <\/strong> ________________________________________ <\/strong>\r\n 1 [1x1 Variable] Pconverter ...aseFluidSSCLog\/Local Restriction (2P)\r\n 2 [1x1 Signal ] Psource ...tationInTwoPhaseFluidSSCLog\/Sine Wave\r\n 3 [1x1 Variable] Displacement ...anslational Mechanical Converter (2P)\r\n\r\n - Use braces { } to access, modify, or add elements using index.\r\n<\/div><\/div><\/div><\/div><\/div>
diffResult = Simulink.sdi.compareRuns(runIDs(end-1), runIDs(end),<\/span>'abstol'<\/span>,1e-3,<\/span>'reltol'<\/span>,1e-3);<\/span><\/span><\/div><\/div>
diffResult.Summary.OutOfTolerance<\/span><\/span><\/div>
ans = uint32<\/span><\/span>\r\n0<\/div><\/div><\/div><\/div><\/div><\/div>
Note that this can all be configured programmatically as described here: <\/span>Log Selected Variables Programmatically<\/span><\/a><\/div>

Using a Coding Agent for Refactoring and Modernization<\/span><\/h2>
Do you think I made those changes myself manually? We're not in 2025 anymore!<\/span><\/div>
What I did is connect my favorite coding agent (configured to use the <\/span>Simulink Agentic Toolkit<\/span><\/a>) to my running MATLAB session and asked:<\/span><\/div>
My Simulink model is logging Simscape variables using sensor blocks and PS-Simulink Converter to then log the Simulink signal. I want you to refactor this model to delete sensor blocks used only for logging and instead use the Simscape Instrumentation Table to log the Simscape variables like Simulink signal. The name of logged signals should remain the same. Begin by capturing a baseline and validate that the logged signals are the same after your changes.<\/span><\/div>
After just a few seconds, I had the model shown in the above picture and a summary of the changes:<\/span><\/div>
\"\"<\/img><\/div>
Before you ask, yes, removing sensors in a Simscape model can change the results, but only within the specified solver tolerance, nothing significant. That's one more reason to avoid unnecessary sensors.<\/span><\/div>

Now it's your turn<\/span><\/h2>
If you are not familiar with this feature, I recommend these documentation pages:<\/span><\/div>