This content is not available in your preferred language.

The content is shown in another available language. Your browser may include features that can help translate the text.

Error Reported When Using NI-VCOM in VeriStand

Updated May 20, 2026

Reported In

Software

  • VeriStand
  • Vehicle Communication Toolkit
  • Vehicle Communication Software Suite

Issue Details

When using the NI Vehicle Communication Toolkit (NI-VCOM) to simulate an ECU to send the CAN messages. The VeriStand definition file is deployed successfully, but when the transmission is enabled, no messages are sent. 

The VCOM Custom Device State channel value is "Error" and the Error Code is 1 or 2. How do I find the meaning of this error and the root cause?

 

Capture.PNG

Solution

Set the DebugLevel to 0 during the development of the project by editing the NI-VCOM configuration file. A successfully deployed VeriStand project does not mean that the Restbus runs error-free. While deploying your VeriStand project, the Vehicle Communication toolkit (NI-VCOM) creates 3 different log files that report warnings or errors. 

Capture.PNG
 
 
  • Offline Core.log: The offline log contains information written during configuration.
  • Online Core.log: The online log also contains information contained in the offline log plus runtime information.
  • RBS.log: The RBS log contains Custom Device specific information.

 

You can open the Online Core.log to read the prompt message about the error. It is helpful for debugging. The log files will be created on the target.

  • Windows: The log files are in the same directory as the VCOMConfig.xml file.
  • Linux RT: The log files are in /c/ni-rt/NIVeriStand/Custom Devices/NI VCOM
 
Common causes can be:
  • Hardware interface not present or found -> Configure the correct interface name based on the NI Hardware Configuration Utility or NI Measurement and Automation Explorer name.
  • Hardware already configured and used by another resource in a different configuration -> Consider the application and how different code components are interacting to ensure correct setup order or matching configurations.
  • Database (.armxl, .dbc, .ldf) parsing issues due to missing information -> Address missing information.
  • Ethernet ports being in a "link down" state -> Ensure the Link Speed is not "Link Down" in NI Hardware Configuration Utility or NI Measurement and Automation Explorer.
 
 

Additional Information

If your target is Linux RT and you don't know how to transfer files from it, you can refer to Using WebDAV to Transfer Files to Real-Time Target.

Related Links

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.