Error Reported When Using NI-VCOM in VeriStand

Updated Jul 12, 2024

Reported In

Software

  • VeriStand
  • Vehicle Communication Toolkit

Issue Details

I am using the NI-VCOM to simulate an ECU to send the CAN messages. The VeriStand definition file is deployed successfully, but when I enable the transmission, no messages are sent. I check the status of NI-VCOM. The State is "Error" and the Error Code is 2. I don't know the meaning of the error code. What should I do to find the root cause?
Capture.PNG

Solution

Set the DebugLevel to 0 during the development of the project. 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 RBSConfig.xml file.
  • Linux RT: The log files are in /c/ni-rt/NIVeriStand/Custom Devices/NI VCOM
 
 
 

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.