Troubleshooting VeriStand: NI-XNET Issues

NI-XNET provides support for developing applications for prototyping, simulating, and testing Automotive Ethernet, CAN , LIN , and FlexRay networks. The NI-XNET devices work with the use of this driver. The driver not only makes the programming environments work with this hardware but creates the possibility to configure them with the help of NI-XNET Database Editor or from VeriStand itself.

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.

Before going through troubleshooting steps for common issues of using XNET in VeriStand, have a look at the NI-XNET Getting Started guide and define whether your application is meeting the set standards or not. If you are using CAN protocol to communicate data in VeriStand, you can have a look at Getting Started with CAN calibration in VeriStand Guide.
 

Troubleshooting Steps:

• According to the version of the software and CompactRIO driver version you use, ask yourself “Do I Need to Compile a Blank Bitfile for NI-XNET in VeriStand”.
• In VeriStand, it is possible to add XNET debugging channels to monitor the buses. The Monitoring Incoming NI-XNET Frame Logging can help you to properly add the channels.
• If the device has a specific configuration refer to its manual to configure the database properly. 
  • Use NI-XNET Custom Baud Rate in VeriStand for configuring the device’s Baud Rate according to your needs.
  • If you have Incorrect or Slow CAN Frames When using NI-XNET in CAN FD & BRS pay attention to the specified Baud Rate, and use the frequently used configuration if you can not find information from your device’s User Manual.
• The modification of the NI-XNET database outside VeriStand can cause Error 1003, 1026, or 7 when Debugging a NI-XNET Database in VeriStand. This can occur if the XNET folder is modified or deleted from the target.