Home Support Documentation Bugs

Vehicle Communication Toolkit 2025 Q3 Known Issues

Updated Sep 3, 2025

Overview

This document contains the Vehicle Communication Toolkit known issues that were discovered before and since the release of Vehicle Communication Toolkit 2025 Q3. 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
3177625

Bus Monitor (GRPC Peer) crashes LabVIEW

Here is the list of ways to detect Bus Monitor bug, as it is happening on Unload stage: 1. WinDbg attached to any LabVIEW API shipping example - crash detected from the first run. 2. Run continuously any Single-Point shipping example with decreased waits - crash will happen in a minute or two 3. Additionally Disable Bus Monitor, run point 1 and ensure that it works fine and crash never happens.

Workaround:

A workaround for this issue is to Disable the Bus Monitor from WebUI in VCOMConfig.xml

Reported Version:

Vehicle Communication Toolkit: 2025 Q3

Resolved Version:

N/A

Added:

N/A
2870604

Importing a Config from ZIP returns an Error 1092

When you import a previous exported config from the system explorer, you get an error 1092.

Workaround:

There is currently no known workaround for this issue.

Reported Version:

Vehicle Communication Toolkit: 2024 Q4

Resolved Version:

N/A

Added:

N/A
3219048

XNET Custom Interface support change in VCOM 2025Q3 request

Steps to reproduce Open configuration tool (WebUI) For "CAN" function module navigate to the "Hardware Port" Fill the "NIXNET Custom Interface" optional field. Save the configuration and run the simulation using saved file.

Workaround:

There is currently no known workaround for this issue.

Reported Version:

Vehicle Communication Toolkit: 2025 Q3

Resolved Version:

N/A

Added:

N/A

Final Time Issue Listed

Issues found in this section will not be listed in future known issues documents for this product.

There are currently no issues to list.

Additional Resources

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

 

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).