Troubleshooting VeriStand: Custom Device Issues

Updated Jul 27, 2022

Environment

Hardware

  • CompactRIO Chassis
  • NI-9144
  • NI-9145
  • C Series EtherCAT Interface Module

Software

  • LabVIEW
  • VeriStand
  • VeriStand Custom Devices

Driver

  • NI-Industrial Communications for EtherCAT

Custom devices enable you to customize and extend the functionality of NI VeriStand by packaging LabVIEW code, or any code you can call from LabVIEW, into a "device" that you can add to an NI VeriStand system definition file and deploy to a target.

You can create a VeriStand custom device to deploy on a real-time target or troubleshoot NI VeriStand Custom Device to debug and improve its functionality and performance. To use FPGA and Real-Time Scan Resources, it is necessary to use the NI VeriStand Scan Engine Custom Device.

This article is a part of a series on Troubleshooting VeriStand Guide. Refer to the main page for initial troubleshooting steps and find the possible cause of the issue you have.

Custom Device Configuration

While adding a Custom Device to your VeriStand project, it is common to receive the following error messages: Once the Custom device is added to the VeriStand system definition file, other errors can occur during the deployment:

VeriStand Scan Engine – EtherCAT Issues

The Scan Engine and EtherCAT VeriStand Addon allow users to easily read scanned I/O from C series modules located in a CompactRIO, NI 9144, or NI 9145 EtherCAT chassis. 
VeriStand allows you to auto-detect the modules connected to your host PC to configure your project setup. It is common to receive errors while using this feature, and to resolve that, you can follow the following two articles:

Other Support Options

Ask the NI Community

Collaborate with other users in our discussion forums



Request Support from an Engineer

A valid service agreement or active software subscription may be required, and support options vary by country.