NI Automotive Diagnostic Command Set Toolkit 21.5 Win32/64Eng 汽车诊断命令集工具包ADCS21.5
Windows系统下（Linux和MAC系统下请自行了解清楚）NI的各种软件、模块、工具包、驱动程序，使用NI许可证管理器来激活的，绝大部分的都可以使用NI Lincense Activator来激活：NI序列号Serial Number生成激活工具NI License Activator，LabVIEW/VBAI/VDM/VAS等软件模块工具包破解工具不限版本http://visionbbs.com/thread-490-1-1.html视觉论坛的各种NI资源，除了视觉相关的模块有使用外，大部分的都不会使用，仅提供资源不提供技术支持。资源的下载地址一般会同时提供NI官方和百度网盘的地址。某些工具包NI地址失效或没有NI地址，只能使用百度网盘地址；如果百度网盘地址失效过期，可联系论坛客服更新。NI的服务器在美国，有时候速度很慢或下载容易出错，这样会造成安装时各种错误而无法安装。建议在下载完成后，对下载资源做校验和(NI一般会提供MD5或SHA256等)验证，与官方或视觉论坛提供的校验和对比，一致就可以安装；如不一致，则需要重新下载。视觉论坛早期下载上传的资源，基本上都是正常下载的资源；2019后下载的资源，都与NI的正确校验和对比过，保证是正确的资源才上传到百度网盘。校验和工具下载地址：文件Hash计算器FHash，文件校验和验证下载文件正确性验证，MD5值计算、SHA1值计算、SHA256值计算、CRC32值计算http://visionbbs.com/thread-26524-1-1.html
NI Automotive Diagnostic Command Set Toolkit 21.5 Win32/64Eng 汽车诊断命令集工具包ADCS21.5
汽车诊断命令集工具包Automotive Diagnostic Command Set Toolkit
汽车诊断命令集工具包为ECU生产测试设计和开发汽车诊断应用程序。
汽车诊断命令集(ADCS)工具包是LabVIEW、LabWindows/CVI和Microsoft Visual Studio的软件附件。该附件适用于一系列汽车诊断应用，通常包括读取和写入参数、访问故障诊断代码(DTC)、闪存ECU固件以及启动ECU诊断测试模式。借助ADCS工具包，您可以开发单个应用程序，并根据需要随时进行部署，而无需额外部署或runtime许可证。该附件与许多NI汽车接口设备兼容，可简化各种便携式和车载诊断应用的开发，并提供对UDS、OBD、WWH-OBD等协议的支持。LabWindows标志经Microsoft公司授权使用。Windows是Microsoft公司在美国和其他国家的注册商标。
ADCS21.5
发布日期
2022/1/27
包含的版本
21.5.0完整版
受支持的操作系统
Windows 10 64-bit
Windows Server 2016 64-bit
Windows Server 2019 64-bit
语言
English
应用程序位数
32/64位
文件大小: 1076215808 字节 (1.00 GB)
修改日期: 2022-01-28 07:01
MD5: 09356b84d36ae717e976b830d908eb52（官方正确）
SHA1: a9d6bdb809c4530145d819a4205ed06fd6c85f8c
SHA256: 8c05c9a8a289c51a7d9b4723154c0df3eeda17c45cb76d87153bbf429b1ea3cd
CRC32: 2fbe7bac
百度网盘和NI官方下载地址:
请注册登录视觉论坛账号，购买附件查看下载地址
Automotive Diagnostic Command Set Toolkit 21.5 ReadmeJanuary 2022This 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
OverviewSupported Operating SystemsApplication Software SupportInstallation InstructionsProduct Security and Critical UpdatesNew FeaturesSupported Hardware and SoftwareECU SimulatorUsing NI-XNET with the Automotive Diagnostic Command Set ToolkitAdditional Programming Topics and Known IssuesAccessing the HelpAutomating the Installation of NI ProductsUsing NI Software with Microsoft Windows 10Unsupported Windows Operating SystemsLegal InformationOverviewThe Automotive Diagnostic Command Set Toolkit helps you design and implement automotive diagnostic applications for ECU production test.Supported Operating SystemsAutomotive Diagnostic Command Set Toolkit 21.5 supports the following operating systems:
[*]Windows 10
[*]Windows Server 2019
[*]Windows Server 2016
NoteAutomotive 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 SupportAutomotive 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 SoftwareVersions Supported by Automotive Diagnostic Command Set Toolkit 21.5
LabVIEW2018 SP1, 2019 SP1, 2020 SP1, and 2021 SP1
LabVIEW Real-Time Module2018 SP1, 2019, 2020, and 2021
LabWindows™/CVI™2015 and later
Microsoft Visual C/C++2008 and later
NoteAutomotive Diagnostic Command Set Toolkit software does not support LabWindows™/CVI™ Real-Time Module.Microsoft Visual Studio SupportIf 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 InstructionsDownload 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 UpdatesVisit 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 HardwareThe 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.NoteAutomotive 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 HelpRefer 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 SimulatorThe 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 <National Instruments>\<LabVIEW xxxx>\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
[*]\Users\Public\Documents\National Instruments\Automotive Diagnostic Command Set\Examples\MS Visual C\ADCS Demo ECU LIN.
Additional Programming Topics and Known IssuesThe 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 ToolkitIf 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 ToolkitCAN FD features are only supported with NI-XNET version 17.0.1 or later.Recommended Maximum Message Length for CAN FDNI recommends the following maximum message length for CAN FD based on the system RAM size.
System RAM SizeMaximum Message Length
≤512 MB8 MB
512 MB – 3.5 GB64 MB
>3.5 GB256 MB
Automating the Installation of NI ProductsYou 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 10Microsoft 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 SystemsAutomotive 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.Legal InformationCopyright© 2009–2022 National Instruments Corporation. All rights reserved.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 NoticesYou can find end-user license agreements (EULAs) and third-party legal notices in the following locations after installation:
[*]Notices are located in the <National Instruments>\_Legal Information and <National Instruments> directories.
[*]EULAs are located in the <National Instruments>\Shared\MDF\Legal\license directory.
[*]Review <National Instruments>\_Legal Information.txt for information on including legal information in installers built with NI products.
U.S. Government Restricted RightsIf 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 NoticeContent 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.TrademarksRefer 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.PatentsFor 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.375413H-01
页:
[1]