|Download Help (Windows Only)|
Parent Topic: Creating Custom Devices
|Note This topic is part of the Process for Developing a Custom Device, and it assumes familiarity with that process and the Creating Custom Devices introduction.|
NI VeriStand provides the functionality needed for most real-time testing applications. Before pursuing a custom device, you should first try to meet your needs with the built-in functionality.
However, if you cannot meet your needs using the built-in features of NI VeriStand, you can extend the functionality of NI VeriStand with a custom device. In general, custom devices are best suited for:
Several pre-built custom devices are available from the NI VeriStand Add-ons page at ni.com/veristand/addons. Additionally, several hardware vendors provide custom devices that enable you to use their hardware with NI VeriStand. If you plan to create a custom device for third-party hardware, National Instruments recommends you check with your hardware vendor to see if they provide a premade custom device before building your own.
If the hardware you need to integrate with NI VeriStand is not natively supported, you may be able to integrate it with NI VeriStand by creating a custom device.
If NI VeriStand does not support the measurement or generation mode you need for your hardware type, you may be able to implement it using a custom device. For example, NI VeriStand supports single-point hardware-timed analog acquisition using DAQmx. However, NI VeriStand does not support force or torque measurements for analog DAQ channels, but you can implement this measurement mode as a custom device.
In rare cases, your NI VeriStand project may require a feature that NI VeriStand does not provide. You can extend NI VeriStand to meet your needs through a variety of methods. In general, custom devices are best suited for implementing features that require or use NI VeriStand channel data on the execution host.
For example, the Embedded Data Logger, a custom device that ships with NI VeriStand, allows you to log NI VeriStand channels to a TDMS file without first sending channel data back to the Workspace, as with high-speed streaming. However, if you need to display the previous test results on the workspace while running a new test, a custom workspace object may be more appropriate than a custom device.
After exploring the built-in functionality of NI VeriStand, you should review all options for expanding the functionality of NI VeriStand. If you do not need the full range of custom device functionality, you likely can more easily fulfill your requirements by converting a LabVIEW VI into a compiled model. Other alternatives include utilizing workspace tools, implementing custom FPGA bitfiles, and exploring the various LabVIEW and .NET APIs that ship with NI VeriStand.