To observe the behavior of your real-time application and the target computer on which it is running, use logging and profiling blocks.
File Log | Write signal data file log on target computer |
Enable File Log | Enable or disable file logging of signals on target computer |
Enable Profiler | Start and stop execution profiler on target computer |
Log Event | Log an execution profiling event |
Target | Represent real-time application and target computer status |
Target.FileLog | Target Computer file logger |
Targets | Configure and manage target objects |
ProfilerData | Data returned from profiler |
Instrument | Create real-time instrument object |
enable | Start file logging of signal data |
disable | Stop file logging of signal data |
list | Get information about available file logs of signal data |
import | Import file log data from target computer |
abort | Abort file log data import from target computer |
discard | Delete file log data from target computer |
startProfiler | Start profiling service on target computer |
stopProfiler | Stop profiling service on target computer |
getProfilerData | Retrieve profile data object |
resetProfiler | Reset profiling service state to Ready
|
Troubleshoot Signal Data Logging from Nonvirtual Bus, Fixed-Point, and Multidimensional Signals
Investigate issues that can occur when signal data logging from signals in nonvirtual buses, signals with fixed-point data type, and multidimensional signals.
Troubleshoot Signal Data Logging from Send and Receive Blocks
Investigate issues that can occur when signal data logging from Send and Receive blocks.