Customizing the NI VeriStand Engine

The NI VeriStand execution engine features a large amount of built-in functionality. However, additional customizations are often required for specific testing or for communication with hardware that is not natively supported. You have three ways to add custom NI LabVIEW code to the NI VeriStand engine: LabVIEW models, custom devices built with the Easy Custom Device Tool, and traditional custom devices.

LabVIEW Models

LabVIEW models are the easiest form of engine customization to create. With LabVIEW 2010 and NI VeriStand 2010 or later, you can create LabVIEW models for NI VeriStand quickly and easily. The instructions for creating LabVIEW models are included in the NI Developer Zone document, "Using Models Created With LabVIEW in NI VeriStand." LabVIEW models have only an execute state, making them ideal for single function additions to the NI VeriStand engine such as math calculations. LabVIEW models do not support discrete run-time states such as initialize, execute, and close. Models always run asynchronously to the primary control loop at a medium priority, so you can preempt them with higher-priority tasks such as I/O or high-priority custom devices. 

Recommended Developer Experience: Certified LabVIEW Associate Developer

Custom Devices Built With the Easy Custom Device Tool

The Easy Custom Device Tool is a way to add flexible customization to the NI VeriStand engine without requiring custom device development skills. This helps you create custom devices even if you have no prior custom device training. You can download this tool from the NI Community at the Easy Custom Device Tool Community Page. Custom devices built using this tool support discrete run-time states, so they are well-suited for customizations that require initialization, run, and clear states. Unlike LabVIEW models, these custom devices support configuration-time settings, such as file paths or device names. The user can modify these settings from the NI VeriStand System Explorer before deploying the configuration. Custom devices created with the Easy Custom Device Tool feature a single-loop architecture, and all inputs and outputs are statically defined by the developer. A custom device generated from the Easy Custom Device Tool offers more flexibility and functionality than LabVIEW models, but it takes more time to create.  

Recommended Developer Experience: Certified LabVIEW Associate Developer

Custom Devices

Custom devices built entirely from the Custom Device Template Tool provide the most flexible way to add custom LabVIEW code to the NI VeriStand engine. You have full control over the functionality of the custom device, and you can implement any LabVIEW code in the device. Using the NI VeriStand Custom Device API, you can dynamically define inputs and outputs in the NI VeriStand System Explorer with user interaction or with configuration files. Additionally, you can implement features such as advanced triggering and timing and synchronization using custom devices. Custom devices require significant LabVIEW programming knowledge to implement. 

Recommended Developer Experience: Certified LabVIEW Developer, LabVIEW Real-Time Experience

Choosing the Correct Form of Customization

The flowchart below can help you decide the best method for NI VeriStand engine customization. While this does not include all possible criteria for choosing a customization method, it covers many of the most common criteria to consider.

Determining Your NI VeriStand Engine Customization Method

Additional Resources

Getting Started With NI VeriStand
NI VeriStand: Real-Time Testing and Simulation Software
Download NI VeriStand Add-Ons

0 Ratings | 0.00 out of 5

 Print |  PDF

Reader Comments | Submit a comment »