MATLAB: Am I unable to find the logged data from Scope block in the MATLAB workspace in R2019a

outputsimulationsimulinksimulink.simulationoutputsingle

In R2019a, it seems that selecting "Log data to workspace" of the Scope block does not actually log the data to the MATLAB workspace as in old releases.

I have also tried using the To Workspace block and the behavior is the same. What setting has been changed in R2019a?

Best Answer

This behavior is expected in R2019a.

Starting from R2019a, the default setting of "*Single simulation output"* option has been changed from 'off' to 'on':

https://www.mathworks.com/help/simulink/gui/single-simulation-output.html

Therefore, Simulink returns all simulation outputs to MATLAB within a single SimulationOutput object, which include signal, state, output, DSM logging, and scope and toworkspace block logging. If not specified, the variable is named as out.

To get the outputs in separate variables as before, you need to uncheck this option.

Related Solutions

MATLAB: Does the “To Workspace” block log data to a variable called “out” starting from R2019a

Whether the "To Workspace" block logs data to "out.simout" or just "simout" (or whichever variable name that you specified) depends on whether the model parameter "Single Simulation Output" is enabled or not:

Since R2019a, the default setting is that Single Simulation Output is enabled. Before that, it used to be disabled by default. This has been documented in the following release note:

https://www.mathworks.com/help/releases/R2019a/simulink/release-notes.html#mw_52b12dad-66f8-4c92-8ac4-9bdbac516ec0

To change this behavior, you can simply disable the parameter as shown in the panel above, or by running the following command:

>> set_param(gcs,'ReturnWorkspaceOutputs',off)

MATLAB: Does “setVariable” in Simulink Test not update variables

In R2019b, the behavior of "setVariable" is modified such that it overrides only model variables (as opposed to MATLAB variables).

I attached a simpler model ("SimpleVars_R2019b.slx") to help illustrate this. This model has two "From Workspace" blocks, one set to "a" and one set to "evalin('base', 'b')".

If you call "findVars" on this model, only "a" is considered to be a model variable, even though both output their timeseries when run:

>> vars = Simulink.findVars('SimpleVars_R2019b')
vars = 
    VariableUsage with properties:
            Name: 'a'
          Source: 'base workspace'
      SourceType: 'base workspace'
           Users: {'SimpleVars_R2019b/From↵Workspace'}

The R2019b behavior provides stricter control of overrides and achieves parity with other Simulink tools. You will need to update the model to use variables which are recognized by Simulink.

Please update the "From Workspace" block variable parameter from "evalin('base', 'y_coordinate')" to just "y_coordinate". Then save the model and run the test file again.

You should observe that "setVariable" updates all of the variables now.

Best Answer

Related Solutions

MATLAB: Does the “To Workspace” block log data to a variable called “out” starting from R2019a

MATLAB: Does “setVariable” in Simulink Test not update variables

Related Question