Automotive Diagnostic Command Set Toolkit 21.5 Readme
January 2022
This file contains installation instructions and compatibility information for Automotive Diagnostic Command Set Toolkit.
You can find more release information on ni.com.
Automotive Diagnostic Command Set Toolkit Release Notes: Known issues, bugs fixed since the last release, and other notes about this release
Automotive Diagnostic Command Set Toolkit Manuals: New features, behavior changes, and other documentation
Overview
Supported Operating Systems
Application Software Support
Installation Instructions
Product Security and Critical Updates
New Features
Supported Hardware and Software
ECU Simulator
Using NI-XNET with the Automotive Diagnostic Command Set Toolkit
Additional Programming Topics and Known Issues
Accessing the Help
Automating the Installation of NI Products
Using NI Software with Microsoft Windows 10
Unsupported Windows Operating Systems
Legal Information
Overview
The Automotive Diagnostic Command Set Toolkit helps you design and implement automotive diagnostic applications for ECU production test.
Supported Operating Systems
Automotive Diagnostic Command Set Toolkit 21.5 supports the following operating systems:
Windows 10
Windows Server 2019
Windows Server 2016
Note Automotive Diagnostic Command Set Toolkit no longer supports Windows Vista/XP/7/8.x, Windows Server 2003/2008/2012, or any 32-bit Windows operating system. Automotive Diagnostic Command Set Toolkit 21.5 will not install or run on an unsupported OS. You cannot deploy or distribute applications that use Automotive Diagnostic Command Set Toolkit 21.5 to an unsupported OS. Additionally, after installing Automotive Diagnostic Command Set Toolkit 21.5, you cannot use any installers built on this computer with any version of LabVIEW, LabWindows™/CVI™, NI TestStand™, or Measurement Studio on an unsupported OS.
Application Software Support
Automotive Diagnostic Command Set Toolkit 21.5 supports the following application software versions, including service packs. If you are not using NI application software, refer to Microsoft Visual Studio Support.
Application Software
Versions Supported by Automotive Diagnostic Command Set Toolkit 21.5
LabVIEW
2018 SP1, 2019 SP1, 2020 SP1, and 2021 SP1
LabVIEW Real-Time Module
2018 SP1, 2019, 2020, and 2021
LabWindows™/CVI™
2015 and later
Microsoft Visual C/C++
2008 and later
Note Automotive Diagnostic Command Set Toolkit software does not support LabWindows™/CVI™ Real-Time Module.
Microsoft Visual Studio Support
If you are using the Automotive Diagnostic Command Set Toolkit .NET Class Library, .NET Framework 4.0 (minimum) is required. The Automotive Diagnostic Command Set Toolkit 21.5 .NET Class Library can be used with Visual C# or Visual Basic .NET in any Visual Studio version that can target .NET Framework 4.0 or .NET Framework 4.5.
To use the .NET API, you must install the .NET class libraries or the .NET wrapper in addition to the NI device driver. For information about versions of the .NET Framework and the drivers each supports, as well as the download location of the installer files, refer to .NET Resources for NI Hardware and Software.
Installation Instructions
Download the Automotive Diagnostic Command Set Toolkit installer from ni.com/downloads. NI software includes NI Package Manager to handle the installation. Refer to the NI Package Manager Manual for more information about installing, removing, and upgrading NI software using Package Manager.
Notes
If applicable, install an application development environment (ADE), such as LabVIEW, LabWindows/CVI, or Microsoft Visual Studio.
MSVC and LabWindows/CVI users should always install the MSVC Support feature.
Product Security and Critical Updates
Visit ni.com/security to view and subscribe to receive security notifications about NI products. For information about critical updates from NI, refer to Available Critical and Security Updates for NI Software.
New Features
Added support for LabVIEW 2021.
Added support to always pad CAN frames to the length of Max DLC.
Added support for configuring DoIP Acknowledgement behavior.
Added support to set the TCP and UDP ports to use for DoIP.
Supported Hardware
The following list details the hardware models supported in Automotive Diagnostic Command Set Toolkit 21.5.
NI-CAN software version 18.0 or later
NI-CAN hardware supported by NI-CAN 18.0
NI-XNET software version 18.0 or later
NI-XNET CAN hardware supported by NI-XNET 18.0 and later1
NI-XNET Automotive Ethernet hardware supported by NI-XNET 19.0 and later
CompactRIO and R-Series hardware using NI 9852/9853 two-port CAN modules for NI CompactRIO (we recommend using NI 986x on NI CompactRIO instead of NI 985x)
1 You can address NI-XNET Automotive Ethernet devices using their assigned IP addresses. To use a specific interface name (e.g., ENET1) together with a custom IP configuration, you can use an XNET IP Stack from ADCS. The IP Stack feature requires NI-XNET 20.1 or later.
Note Automotive Diagnostic Command Set Toolkit software supports only NI Automotive Ethernet, CAN, and LIN hardware products. For information about software for Automotive Ethernet, CAN, and LIN hardware products from other vendors, refer to the documentation you received with those products.
Accessing the Help
Refer to the Automotive Diagnostic Command Set Toolkit Help, accessible from \Users\Public\Documents\National Instruments\Automotive Diagnostic Command Set\Documentation, for information about Automotive Diagnostic Command Set.
The help includes an introduction to diagnostic protocols. It also explains how to get started with application development and includes a complete reference for all Automotive Diagnostic Command Set Toolkit functions.
ECU Simulator
The Automotive Diagnostic Command Set Toolkit software provides an ECU simulation for CAN and LIN. All examples of the Automotive Diagnostic Command Set Toolkit are preconfigured to communicate with the ECU simulation.
LabVIEW users can find the ECU simulator under \\examples\Automotive Diagnostic Command Set\ADCS Demo ECUs.llb.
Microsoft Visual C/C++ and LabWindows/CVI users can find the ECU simulators at
\Users\Public\Documents\National Instruments\Automotive Diagnostic Command Set\Examples\MS Visual C\ADCS Demo ECU CAN Ethernet, or
The Automotive Diagnostic Command Set Toolkit software installs the necessary C/C++ support files in the following locations:
The typical path to the C examples folder is \Users\Public\Documents\National Instruments\Automotive Diagnostic Command Set\Examples\MS Visual C.
The header file for Visual C/C++ 2008 and 2015 is in the Program Files\National Instruments\Shared\ExternalCompilerSupport\C\include folder.
The library file is in the Program Files\National Instruments\Shared\ExternalCompilerSupport\C\lib32\msvc folder.
Using the VW Transport protocol with NI-XNET:
If you are using the VW Transport Protocol on NI-XNET hardware, we suggest using the Frame Stream Input and Output Mode. Example: CAN1@ni_genie_nixnet uses CAN interface 1 on NI-XNET with Frame Stream Mode.
Automotive Diagnostic Command Set Toolkit 20.0 has fixed parameter lists and calling conventions of a subset of functions introduced with Automotive Diagnostic Command Set Toolkit 19.0. Requires recompiling all C/C++/CVI applications built with Automotive Diagnostic Command Set 19.0 and using one of the following functions:
ndDoIPSendVehicleIdentReqEIDAllVersions
ndDoIPSendVehicleIdentRequestAllVersions
ndDoIPSendVehicleIdentReqVINAllVersions
ndDoIPGetEntitiesAllVersions
ndDoIPConnectVersion
Using NI-XNET with the Automotive Diagnostic Command Set Toolkit
If you are using NI hardware that is supported by NI-XNET, it is recommended that you use NI-XNET 19.0 or later with this version of Automotive Diagnostic Command Set Toolkit.
CAN FD support with the Automotive Diagnostic Command Set Toolkit
CAN FD features are only supported with NI-XNET version 17.0.1 or later.
Recommended Maximum Message Length for CAN FD
NI recommends the following maximum message length for CAN FD based on the system RAM size.
System RAM Size
Maximum Message Length
≤512 MB
8 MB
512 MB – 3.5 GB
64 MB
>3.5 GB
256 MB
Automating the Installation of NI Products
You can automate the installation of most NI products using command-line arguments to suppress some or all of the installer user interface and dialog boxes.
If the NI product you are installing uses Microsoft .NET 4.6.2, the .NET installer may run before any NI software installs and may require a reboot before the installation of NI software begins. To avoid a .NET reboot, install .NET 4.6.2 separately before you install NI software.
For more information about automating the installation of NI products, refer to Automating an Installer in the NI Package Manager manual.
Using NI Software with Microsoft Windows 10
Microsoft Windows 10 is the latest version of the Windows operating system and features significant changes compared to previous versions. Windows 10 introduces several new capabilities and also combines features from both Windows 7 and Windows 8. For more information about NI support for Windows 10, refer to NI Product Compatibility for Microsoft Windows 10.
Unsupported Windows Operating Systems
Automotive Diagnostic Command Set Toolkit no longer supports Windows Vista/XP/7/8.x, Windows Server 2003/2008/2012, or any 32-bit Windows operating system. Versions of this product that ship after May 1, 2021, may not install or execute correctly on these operating systems. For detailed information about NI operating system support, visit https://www.ni.com/r/win32bitsupport.
Under the copyright laws, this publication may not be reproduced or transmitted in any form, electronic or mechanical, including photocopying, recording, storing in an information retrieval system, or translating, in whole or in part, without the prior written consent of National Instruments Corporation.
NI respects the intellectual property of others, and we ask our users to do the same. NI software is protected by copyright and other intellectual property laws. Where NI software may be used to reproduce software or other materials belonging to others, you may use NI software only to reproduce materials that you may reproduce in accordance with the terms of any applicable license or other legal restriction.
End-User License Agreements and Third-Party Legal Notices
You can find end-user license agreements (EULAs) and third-party legal notices in the following locations after installation:
Notices are located in the \_Legal Information and directories.
EULAs are located in the \Shared\MDF\Legal\license directory.
Review \_Legal Information.txt for information on including legal information in installers built with NI products.
U.S. Government Restricted Rights
If you are an agency, department, or other entity of the United States Government ("Government"), the use, duplication, reproduction, release, modification, disclosure or transfer of the technical data included in this manual is governed by the Restricted Rights provisions under Federal Acquisition Regulation 52.227-14 for civilian agencies and Defense Federal Acquisition Regulation Supplement Section 252.227-7014 and 252.227-7015 for military agencies.
IVI Foundation Copyright Notice
Content from the IVI specifications reproduced with permission from the IVI Foundation.
The IVI Foundation and its member companies make no warranty of any kind with regard to this material, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. The IVI Foundation and its member companies shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this material.
Trademarks
Refer to the NI Trademarks and Logo Guidelines at ni.com/trademarks for information on NI trademarks. Other product and company names mentioned herein are trademarks or trade names of their respective companies.
Patents
For patents covering the NI products/technology, refer to the appropriate location: Help» Patents in your software, the patents.txt file on your media, or the NI Patent Notice at ni.com/patents.