NI Automotive Diagnostic Command Set Toolkit 20.6 Win32/64Eng 汽车诊断命令集工具包ADCS20.6
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 20.6 Win32/64Eng 汽车诊断命令集工具包ADCS20.6
汽车诊断命令集工具包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公司在美国和其他国家的注册商标。
ADCS20.6
文件大小: 1035565056 字节 (987.59 MB)
修改日期: 2020-12-09 08:07
MD5: a6483a4a76b8c8a4cb63c03ff33cd43c（官方正确）
SHA1: 59247cb533663d0fd95d02683d0dd02091d3c9d1
SHA256: 2f73cee8b2e2cd7fef6fb1a277faac14263840f954e40f15898e82041bbef5f5
CRC32: 10523a8e
百度网盘和NI官方下载地址:
Automotive Diagnostic Command Set Toolkit 20.6 ReadmeOctober 2020This file contains important information about the Automotive Diagnostic Command Set Toolkit software for Windows and LabVIEW Real-Time (RT), including installation instructions, new features, and known issues.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 IssuesKnown IssuesBug FixesAccessing the HelpAutomating the Installation of NI ProductsUsing NI Software with Microsoft Windows 10Using NI Software with Microsoft Windows 8.1Legal 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 20.6 supports the following operating systems:
[*]Windows 10/8.11/7 SP12 (32-bit and 64-bit)
[*]Windows Server 2016
[*]Windows Server 2012 R21 (64-bit)
[*]Windows Server 2008 R2 SP11 (64-bit, not supported on Server Core Role)
1 NI software installs VC2015 Runtime and .NET 4.6.2. Windows 8.1 and Windows Server 2012 R2 require Microsoft updates to support these items. Refer to Microsoft KB2919442 and KB2919355 for more information about how to install these updates.2 NI software is signed with a SHA-256 certificate. Windows 7 SP1, Windows Embedded Standard 7 SP1, and Windows Server 2008 R2 SP1 require Microsoft updates to support SHA-256. Refer to Microsoft KB3033929 and KB3125574 for more information about how to install these updates.NoteIn 2016, NI dropped support for Windows Vista, Windows XP, Windows Server 2003, and installations of Windows 7 without any service packs. Automotive Diagnostic Command Set Toolkit will not install or run on an unsupported OS. You cannot deploy or distribute applications that use Automotive Diagnostic Command Set Toolkit to an unsupported OS. Additionally, after installing this version of Automotive Diagnostic Command Set Toolkit, 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.For more information about the changes to our OS support for 2016, visit ni.com/r/OSSupport2016.NoteSupport for Windows 32-bit operating systems may require disabling physical address extension (PAE). To learn how this might affect your system and what actions you might need to take, visit ni.com/r/PAESupport.ADCS Toolkit Drops Support for Windows 7 (32- and 64-Bit), Windows Server 2008 R2, and All 32-Bit Windows Operating Systems in 2021Automotive Diagnostic Command Set Toolkit will drop support for Windows 7 (32- and 64-bit), Windows Server 2008 R2, and all 32-bit Windows operating systems starting in 2021. 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 ni.com/r/win32bitsupport.Application Software SupportThis version of Automotive Diagnostic Command Set Toolkit software supports the following development environments, including service packs.
Application SoftwareVersions Supported by Automotive Diagnostic Command Set Toolkit 20.0
LabVIEW2017 SP1, 2018 SP1, 2019 SP1, 2020 SP1
LabVIEW Real-Time Module2017, 2018 SP1, 2019, and 2020
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.Installation InstructionsNI installs Automotive Diagnostic Command Set Toolkit using NI Package Manager. If you do not already have NI software installed, Automotive Diagnostic Command Set Toolkit installs NI Package Manager to handle the installation of your NI software. Visit ni.com/r/NIPMDownload to download NI Package Manager. Refer to the NI Package Manager Manual for more information about installing, removing, and upgrading NI software using NI 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. Visit ni.com/critical-updates for information about critical updates from NI.New FeaturesNew Features and Changes as Compared to Automotive Diagnostic Command Set 20.0The Automotive Diagnostic Command Set 20.6 release adds the following features:
[*]Added support for XNET IP Stack.
[*]Added support for LabVIEW 2020 SP1.
[*]Added support for LabWindows/CVI 2020.
New Features and Changes as Compared to Automotive Diagnostic Command Set 19.5The Automotive Diagnostic Command Set 20.0 release adds the following features:
[*]Added support for LabVIEW 2020.
[*]Added support for LabWindows™/CVI™ 2020.
[*]Added support for the PXIe-8522 4-Port, 1000BASE-T1 PXI Automotive Ethernet Interface Module
[*]Added support for the PXIe-8523 4-Port, 100/1000BASE-T1 PXI Automotive Ethernet Interface Module
New Features and Changes as Compared to Automotive Diagnostic Command Set 18.5The Automotive Diagnostic Command Set 19.0 release adds the following features:
[*]Added support for LabVIEW 2019.
[*]Added support for LabVIEW Linux PXI RT.
[*]Added support for LabWindows™/CVI™ 2019.
[*]Added 0xFF flag for DoIP broadcast messages.
[*]Added support for session-based properties.
[*]Added support for the PXIe-8521 4-port, 100BASE-T1 PXI Automotive Ethernet Interface Module.
[*]Added support for installation through NI Package Manager.
[*]Removed support for LabVIEW 2015.
[*]Removed support for LabWindows™/CVI™ 2012 and 2013 (without SP1).
[*]Removed support for NI-CAN 15.0.
[*]Removed support for NI-XNET 15.0.
New Features and Changes as Compared to Automotive Diagnostic Command Set 18.0The Automotive Diagnostic Command Set 18.5 release adds the following features:
[*]Added support for LabVIEW 2018 SP1.
[*]Added support for Diagnostic over IP 2012 Protocol Version.
[*]Added support for Tester Present Auto Timing.
[*]Added support for ECU Determined CAN I/O Mode. CAN I/O mode can be set to "ECU Determined" to use ECUs with CAN 2.0 or CAN FD.
[*]Added Response Plausibility Check property. Defines whether the first byte of the diagnostic response is checked to contain the + 0x40 offset (positive response) or whether the first byte is 0x7F (negative response).
New Features and Changes as Compared to Automotive Diagnostic Command Set 15.0The Automotive Diagnostic Command Set 18.0 release adds the following features:
[*]Added support for LabVIEW 2016, LabVIEW 2017, and LabVIEW 2018.
[*]Added support for ISO CAN FD.
[*]Added support for Diagnostic over IP over non-primary NICs.
[*]Added support for LIN sleep for UDS.
[*]Removed support for LabVIEW 2012, LabVIEW 2013, and LabVIEW 2014.
[*]Removed support for LabWindows™/CVI™ 2010 and earlier versions.
New Features and Changes as Compared to Automotive Diagnostic Command Set 14.0The Automotive Diagnostic Command Set 15.0 release adds the following features:
[*]Added support for LabVIEW 2015.
[*]Removed support for LabVIEW 2011.
[*]Added support for 64-bit LabVIEW and C/C++.
[*]Added support for CompactRIO Real-Time Controllers supported by NI-XNET 15.0 (NI cRIO-9081, NI cRIO-9082, NI cRIO-903x).
New Features and Changes as Compared to Automotive Diagnostic Command Set 1.2The Automotive Diagnostic Command Set 14.0 release adds the following features:
[*]Added support for LabVIEW 2014.
[*]Removed support for LabVIEW 2010.
[*]Added support for WWH-OBD (World-Wide-Harmonized On-Board Diagnostics) based on ISO 27145.
[*]Added the new Get Time Stamp function to measure timestamp information of the first/last send/received frame of the ISO TP for CAN and LIN.
[*]Added support for NI cRIO-9068 Controller (based on NI Linux Real-Time OS).
Supported Hardware and SoftwareThe Automotive Diagnostic Command Set Toolkit software supports the following software and hardware:
[*]NI-CAN software version 16.0 or later
[*]NI-CAN hardware supported by NI-CAN 16.0
[*]NI-XNET software version 16.0 or later
[*]NI-XNET CAN and LIN hardware supported by NI-XNET 16.0 or later
[*]NI-XNET Automotive Ethernet hardware supported by NI-XNET 19.0 or later3
[*]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)
3 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.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.
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
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
Known IssuesYou can access the software and documentation known issues list online. Visit ADCS Known Issues for an up-to-date list of known issues.Bug FixesYou can access the Automotive Diagnostic Command Set Toolkit 20.6 bug fix list online at ADCS 20.6 Bug Fixes. This list describes a subset of issues fixed in this release. If you have a Bug ID, you can search this list to validate that the issue has been fixed.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 the Automotive Diagnostic Command Set Toolkit.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.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, visit ni.com/windows10.Using NI Software with Microsoft Windows 8.1When you install NI software on Microsoft Windows 8.1, you will notice a few additional tiles in the Apps view, including shortcuts to NI application software products such as NI LabVIEW, Measurement & Automation Explorer (NI MAX), and NI Launcher. For more information about NI support for Windows 8.1, visit ni.com/windows8.Legal InformationCopyright© 2009–2020 National Instruments. 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.375413G-01
页:
[1]