Home Support Documentation Bugs

Vehicle Communication Toolkit 1.1 Bug Fixes

Created Jun 22, 2023

Overview

The following items are notable issues fixed between the release of Vehicle Communication Toolkit 1.0 and Vehicle Communication Toolkit 1.1, including additional patches and service packs. If you have an issue ID, you can search this list to validate that the issue has been fixed. This is not an exhaustive list of issues fixed in the current version of Vehicle Communication Toolkit.

Bug Number

Legacy ID

Description

Details
1880303

The Open Session VIs are broken in LabVIEW 2021 64-bits

The 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 10

Error 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 tree

Transmission 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 DUT

If 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 File

Network 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 endianness

The 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 devices

Multicast 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 Ethernet

The 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

Additional Patch Information

Installing some patches may require certain additional steps or considerations. Please refer to the following table for more information about patches for this release.

These patches currently do not have any special instructions.

Glossary of Terms

 

  • Bug ID - When an issue is reported to NI, you may be given this ID or find it on ni.com.  You may also find IDs posted by NI on the discussion forums or in KnowledgeBase articles.
  • Legacy ID – An older issue ID that refers to the same issue.  You may instead find this issue ID in older known issues documents.
  • Description - A few sentences which describe the problem. The brief description given does not necessarily describe the problem in full detail.
  • Workaround - Possible ways to work around the problem.
  • Reported Version - The earliest version in which the issue was reported.
  • Resolved Version - Version in which the issue was resolved or was no longer applicable. "N/A" indicates that the issue has not been resolved.
  • Date Added - The date the issue was added to the document (not the reported date).