Additional Information
If you are experiencing custom device configuration or deployment errors, please see the articles in the Related Links section below.
If you can verify a run-time error or unexpected behavior comes from the custom device, then the source of the problem is from the RT Driver VI. This would include the Execute Model case of an inline model custom device, the Read Data from Hardware and Write Data to Hardware cases of an inline hardware custom device, and the contents of the while loop in an asynchronous custom device.
Custom device development can be challenging. Refer to the
Creating Custom Devices - VeriStand Help landing page to learn more about types of custom devices, what it takes to create one, how to access when to need one, and the process of, planning, implementing, debugging, and building one from scratch.
For a comprehensive, in-depth, older (but still useful) guide into VeriStand custom device development, please review the
NI VeriStand Custom Device Developer’s Guide.