You can use tools provided by LabVIEW and VeriStand to benchmark and debug your custom device.
You should perform benchmarking on a system that is similar to the target. Other components of the VeriStand system, such as models, calculated channels, alarms, and procedures, affect the ultimate execution speed of the system.
|LabVIEW Debugging Tools||Debugging||N/A||LabVIEW||
You can merge debugged VIs into the Custom Device Framework manually. Timing can differ between standalone VIs and VIs in the Custom Device Framework. This tool is not available after VeriStand integration.
For more information, refer to the Debugging Techniques topic in LabVIEW Help.
|Console Viewer||Benchmarking (CPU) and debugging||Low||VeriStand||
A VeriStand workspace tool that displays system definition details, CPU usage, and debugging messages. The tool takes periodic snapshots and prints messages sent by the Print Debug String VI.
This tool is only available on PharLap real-time (RT) targets. CPU spikes and transients might not appear.
|Custom Error Codes||Debugging||N/A||LabVIEW and VeriStand||
You can define custom error codes in LabVIEW and distribute the codes to VeriStand with a custom device. Copy the custom errors.txt file to VeriStand in the <Base>\National Instruments\Shared\Errors\English directory and add the file as a dependency in custom device and Custom Device XML file.
For RT targets, deploy the errors.txt file to the error directory on target to display error descriptions in Console Viewer.
For more information, refer to the Defining Custom Error Codes to Distribute throughout Your Application topic in the LabVIEW Help
|Print Debug String VI||Debugging||NA||LabVIEW||
This VI prints messages to the RT console and the VeriStand data log. This tool works on Windows and RT targets.
|NI Distributed System Manager||Benchmarking (CPU and RAM)||Medium||Installs with LabVIEW.||
The manager works with network variables and manages remote target settings and the status of the Shared Variable Engine. This tool takes periodic snapshots.
To use this tool, you must install System State Publisher on the RT target. CPU spikes and transients might not appear.
|System Channels||Benchmarking and debugging||High||VeriStand||alarms or procedures.|
|NI Real-Time Execution Trace Toolkit||Benchmarking and debugging||Very High||Installs with LabVIEW Real-Time Module.||
This toolkit creates execution trace logs for low-level debugging. These logs provide detailed information on thread and VI timing.
Interacts with the following system channels:
For more information, refer to Debugging Threads in VeriStand.