This document contains the Vehicle Communication Toolkit known issues that were discovered before and since the release of Vehicle Communication Toolkit 2023 Q1. 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 |
|---|---|---|---|
| 2323630 |
Cannot connect to an ECU with XCP when CCP is also supportedWhen an .a2l file contains both CCP and XCP information, the Measurement and Calibration Toolkit always uses CCP to connect and you cannot switch to XCP
Workaround: Remove CCP
information from the .a2l file before using XCP
|
Reported Version: Vehicle Communication Measurement and Calibration Toolkit: 2023 Q1 Resolved Version: N/A Added: Mar 29, 2023 |
|
| 2325864 |
The Database Viewer does not display CCP information from the .a2L fileYou cannot view CCP information from the .a2L file in the Database Viewer
Workaround: There is currently no known workaround for this issue
|
Reported Version: Vehicle Communication Measurement and Calibration Toolkit: 2023 Q1 Resolved Version: N/A Added: Mar 29, 2023 |
|
| 2333925 |
When configurating a RBSConfig XML file for doing measurement and calibration over CAN/CANFD, you must set the “Network Descriptor” parameterWhen configurating a RBSConfig XML file for doing measurement and calibration over CAN/CANFD, you must set the “Network Descriptor” parameter, otherwise, the WebUI configuration tool generates an error that prompts you to set the “Network Descriptor” parameter.
Workaround: The network descriptor is a necessary parameter for creating a Configuration XML File for the CAN communication. But the configuration XML file for calibration does not require the network descriptor. The example Configuration file used with VCOM measurement and calibration toolkit examples present here : "C:\Users\Public\Documents\National Instruments\NI-VCOM\configuration\RBS_Config\Measurement and Calibration Toolkit" uses the "PROVEtechRBS_Example_CAN_FD.dbc" network descriptor file present here : "C:\Users\Public\Documents\National Instruments\NI-VCOM\database" . Please use any valid .dbc database file to create the Configuration XML file for calibration
|
Reported Version: Vehicle Communication Measurement and Calibration Toolkit: 2023 Q1 Resolved Version: N/A Added: Mar 30, 2023 |
|
| 2341209 |
Cannot set value for optional "Enable Event Multicast" parameter in Automotive Ethernet TAP ModeAn error is generated when you try to configure the "Enable Event Multicast" parameter in Automotive Ethernet Tap Mode
Workaround: The “Enable Event
Multicast” parameter does not apply to Automotive Ethernet TAP Mode. Do not
attempt to configure this parameter when you apply this mode
|
Reported Version: Vehicle Communication Toolkit: 2023 Q1 Resolved Version: N/A Added: Mar 29, 2023 |
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