Hallo Victor, any block output should be visible as signal at the place where it is generated. For "wires" just crossing subsystem boundaries no signals are generated by Simulink (this is different to dSpace). If we want to display specific signals we use a "vector concatenate" in the signal connection and set the "Number of inputs" to 1.
If you are missing signals at block outputs please post an minimal example for investigation. regards Wilhelm. Am 17.12.2014 15:31, schrieb [email protected]: > Hello, > > > > We’re using EtherLAB2, and Matlab R2014b. We have a problem that after > compiling and running code, some signals are not available in > TestManager. We have some outputs of calculation blocks (temperature, > angle of encoder) that we’re not using in our control loop, but would > like to monitor in TestManager. Can you suggest what we could do to get > these variables in TestManager? > > We do see some parameters / channels in TestManager, but it appears that > some are optimized away. What we have tried sofar: > > - Add test point / log data property on signal wire > > - Wire to “add” block -> this works temporarily because you can > see the output of the “add” block, but it gets optimized away after a > few compiles (or so it seems) > > - Make an atomic subblock and add something there. > > We’d like to have some way to ‘scope’ data that’s calculated in our > application. Do you have suggestions for settings in Simulink or Etherlab? > > > > With kind regards, > > Victor > > > > _______________________________________________ > etherlab-users mailing list > [email protected] > http://lists.etherlab.org/mailman/listinfo/etherlab-users > _______________________________________________ etherlab-users mailing list [email protected] http://lists.etherlab.org/mailman/listinfo/etherlab-users
