Often users put many 'To Workspace' sink blocks throughout their schematic. However, they may be best served by using Simulink’s signal logging features. (See “Logging Signals” in Simulink Help which explains all).
You can turn on signal logging for individual signals without the need for any ‘To Workspace’ Blocks, or you can just enable logging for a scope, of course. (In both cases name your signals appropriately first). You can do this programmatically, so could, for example, write a script that will turn on signal logging for all signals in a given subsystem if desired.
You can then access them and plot, analyse etc – using Fixed Point Toolbox functions if desired. E.g.
Note that one thing that you can’t really do with this is make use of the override features of the fixed point type to identify underflow & overflows – this is because DSPBA explicitly does the maths according to the output type using its own internal format and constructs the result accordingly, rather than do the math using Fixed point types directly
For example, if you change the fixed point preferences :
>> fipref.LoggingMode = 'On'
>> fipref.DataTypeOverride = 'ScaledDoubles'
The Simulink Sum block will record an overflow,
Warning: Overflow occurred. This originated from 'fixedptlogtest/Sum'.
Community support is provided during standard business hours (Monday to Friday 7AM - 5PM PST). Other contact methods are available here.
Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.