This document contains the Vehicle Communication Toolkit known issues that were discovered before and since the release of Vehicle Communication Toolkit 1.0. Known issues are performance issues or technical bugs that NI has acknowledged exist within this version of the product.
Not every issue known to NI appears on this list; it is intended to show the most severe and common issues that you may encounter and provide workarounds when possible. Other technical issues that you may encounter could occur through normal product use or system compatibility issues. You may find more information on these issues in NI’s Product Documentation, Knowledgebase, or Community; see Additional Resources.
|
Bug Number |
Legacy ID |
Description |
Details |
|---|---|---|---|
| 1880303 |
The Open Session VIs are broken in LabVIEW 2021 64-bitsThe Open Session VIs are broken in LabVIEW 2021 (64-bit).
Workaround: Copy the vi.lib\Vehicle Communication Toolkit folder from the LabVIEW 32-bit installation to the LabVIEW 64-bit vi.lib directory. This issue is fixed in the NI Vehicle Communication Toolkit 1.1. |
Reported Version: Vehicle Communication Toolkit 1.0 Resolved Version: Vehicle Communication Toolkit 1.1 Added: N/A |
|
| 2090630 |
VeriStand 2021 VCOM Custom Device returns error 13 in Windows 10Error 13 is reported on some Windows 10 machines because of a missing dependency when using the VCOM Custom Device for VeriStand 2021.
Workaround: This issue is fixed in the NI Vehicle Communication Toolkit 1.1. |
Reported Version: Vehicle Communication Toolkit 1.0 Resolved Version: Vehicle Communication Toolkit 1.1 Added: N/A |
|
| 2107722 |
ECU configured as Network Management has missing signals in the signal treeTransmission PDUs (TX PDUs) are missing in the signal tree and cannot be retrieved by the API for Restbus Simulation if an ECU is configured as a Network Managemet ECU in the ARXML database. This problem affects both VeriStand Custom Device and LabVIEW API.
Workaround: This issue is fixed in the NI Vehicle Communication Toolkit 1.1. |
Reported Version: Vehicle Communication Toolkit 1.0 Resolved Version: Vehicle Communication Toolkit 1.1 Added: N/A |
|
| 2107726 |
Missing Network Management frames in signal tree if they were not configured to be sent to the DUTIf Network Management frames are not tagged in an ARXML database as "Send" frames, they will be missing in the signal tree and cannot be retrieved by the API for Restbus Simulation. This problem affects both VeriStand Custom Device and LabVIEW API.
Workaround: This issue is fixed in the NI Vehicle Communication Toolkit 1.1. |
Reported Version: Vehicle Communication Toolkit 1.0 Resolved Version: Vehicle Communication Toolkit 1.1 Added: N/A |
|
| 2107732 |
Network Management PDUs missing in Signal Tree if ECU configured as Device Under Test in the Configuration FileNetwork Management PDUs are missing in the signal tree for RX nodes. They cannot be retrieved by the API for Restbus Simulation if an ECU is configured in the list of ECUs Under Test and a CAN Function module is used in the XML configuration file. This problem affects both VeriStand Custom Device and LabVIEW API.
Workaround: This issue is fixed in the NI Vehicle Communication Toolkit 1.1. |
Reported Version: Vehicle Communication Toolkit 1.0 Resolved Version: Vehicle Communication Toolkit 1.1 Added: N/A |
|
| 2107735 |
Some Auto signals are misconfigured and miscalculated when set to use Motorola endiannessThe Auto Signals configuration and calculation are incorrect for some signals defined in the database with big-endian order. This problem affects both VeriStand Custom Device and LabVIEW API.
Workaround: This issue is fixed in the NI Vehicle Communication Toolkit 1.1. |
Reported Version: Vehicle Communication Toolkit 1.0 Resolved Version: Vehicle Communication Toolkit 1.1 Added: N/A |
|
| 2107738 |
Multicast messages are not received properly with TAP Mode in Automotive Ethernet devicesMulticast messages are not received properly when TAP Mode is configured in the RBS Configuration XML file for an Automotive Ethernet module. This problem affects both VeriStand Custom Device and LabVIEW API.
Workaround: This issue is fixed in the NI Vehicle Communication Toolkit 1.1. |
Reported Version: Vehicle Communication Toolkit 1.0 Resolved Version: Vehicle Communication Toolkit 1.1 Added: N/A |
|
| 2107741 |
Wakeup signal in Network Management frames not working correctly for Automotive EthernetThe Wakeup signal does not work correctly when a frame is configured as a Network Management frame for an Automotive Ethernet module in the database. This problem affects both VeriStand Custom Device and LabVIEW API.
Workaround: This issue is fixed in the NI Vehicle Communication Toolkit 1.1. |
Reported Version: Vehicle Communication Toolkit 1.0 Resolved Version: Vehicle Communication Toolkit 1.1 Added: N/A |
Issues found in this section will not be listed in future known issues documents for this product.
There are currently no issues to list.
Explore Support Content and Product Documentation
Ask the NI Community
Request Support from an Engineer
A valid service agreement may be required, and support options vary by country