Updates and Changes for Extended Support Versions

Browse updates and changes made in versions on extended support.

Note If you cannot find changes for your version, it might be a more recent version, documented as a new feature. Or, your version might not have included user-facing updates. You can find more information about non-visible changes, such as bug fixes, compatibility updates, and stability adjustments or maintenance adjustments, in the product Release Notes, available on ni.com.

Vehicle Communication Software Suite 2024 Q1 Changes

Learn about new features, behavior changes, and other updates in Vehicle Communication Software Suite 2024 Q1.

Vehicle Communication Toolkit New Features

  • Base and Full Versions:
    • Upgrades supported version of LabVIEW to 2024 Q1
    • Upgrades supported version of VeriStand to 2024 Q1
    • Adds support for a Bus monitor
    • Adds support of byte array data type signals in the NI-VCOM custom device and LabVIEW API

Behavior Changes

  • NI-VCOM has a new database viewer for RBS, the Calibration Toolkit, and the Diagnostic Toolkit. The new database viewer allows a more hierarchical and dense view of database content and provides a smoother search experience.
  • The Read Signal - State RBS VI in the NI-VCOM LabVIEW API is now named Read (State VCOM).vi. Update the name of the VI if you use this API in your NI-VCOM application.

Vehicle Communication Software Suite 2023 Q3 Changes

Learn about new features, behavior changes, and other updates in Vehicle Communication Software Suite 2023 Q3.

Vehicle Communication Toolkit New Features

  • Base and Full Versions:
    • Adds support for J1939 protocol
    • Adds support for CAN and LIN virtual devices
    • Adds support for multiple VCOM custom devices, each with unique configurations, in the same VeriStand project containing multiple controllers. Each controller can be associated with one VCOM custom device.
    • Adds support for LabVIEW API signal selection in the Read and Write VIs.
    • Adds support for deploying configuration files to remote targets from the WebUI rather than manually copying files between machines.
    • Adds performance improvements for importing large .arxml files and large numbers of signals.
  • Full Version Only:
    • Adds support for optional Diagnostic Toolkit
    • Adds support for AUTOSAR Global Time Synchronization

Behavior Changes

  • The VeriStand Custom Device is now called NI:VCOM rather than Provetech:RBS
  • The VeriStand Custom Device API is now located on the NI-VCOM:Restbus simulation palette
  • The Measurement and Calibration Toolkit is now configured automatically.
  • The VCOM custom device now creates channels that are not scalable by default, but you can set them to be scalable if necessary.

Vehicle Communication Toolkit 2023 Q1 Changes

Learn about new features, behavior changes, and other updates in Vehicle Communication Toolkit 2023 Q1.

New Features

  • Base and Full Versions:
    • Upgrades supported version of NI-XNET SDK to 2022 Q3
    • Adds support for configuring CRC_11BIT_ADD checksum type in RBSConfig tool for CAN bus
    • Adds support for checking CRC value correctness upon receiving CAN/CAN-FD, LIN, FlexRay, and Automotive Ethernet messages in disassembly module
    • Adds support for checking Secured-PDU security algorithm correctness upon receiving CAN/CAN-FD and Automotive Ethernet messages in disassembly module
    • Extends support for AUTOSAR E2E Profile 4 for CAN/CAN-FD messages
  • Full Version Only:
    • Adds support for optional Measurement and Calibration Toolkit
    • Adds support for setting the VLAN Priority field in the Ethernet header
    • Adds support for configuring different port numbers for Automotive Ethernet sender and receiver
    • Adds support for AUTOSAR E2E Profile 4m and 7m for SOME/IP fields in Automotive Ethernet module

Behavior Changes

  • Older versions of the NI-VCOM Toolkit Custom Device for VeriStand may not work properly with Vehicle Communication Toolkit 2023 Q1. Delete the Custom Device from your VeriStand project and add a new Custom Device to resolve this issue.