Logging and Profiling
To observe the behavior of your real-time application and the target computer on which it is running, use logging and profiling blocks.
|Delete file log data from target computer|
|Returns block paths corresponding to File Log blocks in application|
|Returns decimation value of File Log block based on block path|
|Retrieve profile data object|
|Get information about available file logs of signal data|
|Import file log data from target computer|
|Reset profiling service state to |
|Sets decimation value on File Log blocks based on block path and input decimation value|
|After copying file logs from target to development computer, import file logs into Simulation Data Inspector|
|After copying file logs from target to development computer, list available file logs for import into Simulation Data Inspector|
|Start profiling service on target computer|
|Starts signal data live streaming and File Log logging|
|Stop profiling service on target computer|
|Stops signal data live streaming and File Log logging|
Investigate issues that can occur when signal data logging from signals in nonvirtual buses, signals with fixed-point data type, and multidimensional signals.
Investigate issues that prevent some signals from streaming to the Simulation Data Inspector.
Investigate issues that can occur when signal data logging from signals in referenced models in test harnesses.
Investigate issues that can occur when signal data logging from Send and Receive blocks.
Investigate issue related to error that a signal cannot be streamed or logged.