How to deal with signal logging within a library block
3 views (last 30 days)
I'm developing Simulink library blocks, and during development and testing, it's convenient to enable logging on some signals. When the library block is placed in a model, is there a way to turn on/off logging for signals within that block? I'd rather the default be that the signals within the library block are not logged.
The reason for this is that when I use the library block in my main model, I don't want the internal signals logged. The main model contains many library blocks, and if all signals within all library blocks were logged, it would be overwhelming. However, I generally also create and maintain a separate test model for each library block, and I do want the interal signals logged in that model.
What is the best way to deal with this?