NI Automotive Diagnostic Command Set Toolkit 15.0 Runtime Win32/64Eng 汽车诊断命令集工具包ADCS15.0运行版下载
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 15.0 Runtime Win32/64Eng 汽车诊断命令集工具包ADCS15.0运行版下载
汽车诊断命令集工具包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公司在美国和其他国家的注册商标。
15.0RT
文件大小: 224554864 字节 (214.15 MB)
修改日期: 2019-06-25 02:42
MD5: 1f4839c6af4ef6583876700ceb60e9a5（官方正确）
SHA1: 3edea108d5ce16679c0ab02740a40c073d3b7a6d
SHA256: e48134327c68b7f5689979f15c57cd0383db3986b0a403d7a00cea0603c149d4
CRC32: 22d11265
百度网盘和NI官方下载地址：
Automotive Diagnostic Command Set 15.0 ReadmeSoftware for Windows 8/7/Vista/XP and LabVIEW™ Real-Time (RT)August 2015Thank you for using National Instruments products.For more information about National Instruments products, refer to ni.com/support.This file contains information about the Automotive Diagnostic Command Set software for Windows 8/7/Vista/XP and LabVIEW Real-Time (RT).Information in this file is organized in the following sections:
[*]Documentation
[*]Supported Platforms
[*]Installing the Automotive Diagnostic Command Set
[*]New Features and Changes as Compared to Automotive Diagnostic Command Set 1.0.0
[*]New Features and Changes as Compared to Automotive Diagnostic Command Set 1.0.2
[*]New Features and Changes as Compared to Automotive Diagnostic Command Set 1.0.3
[*]New Features and Changes as Compared to Automotive Diagnostic Command Set 1.0.4
[*]New Features and Changes as Compared to Automotive Diagnostic Command Set 1.1
[*]New Features and Changes as Compared to Automotive Diagnostic Command Set 1.1.1
[*]New Features and Changes as Compared to Automotive Diagnostic Command Set 1.2
[*]New Features and Changes as Compared to Automotive Diagnostic Command Set 14.0
[*]ECU Simulator
[*]Additional Programming Topics
[*]Bug Fixes
[*]Automotive Diagnostic Command Set Updates and Notifications
[*]Automating the Installation of NI Products
[*]How to Use NI Software with Microsoft Windows 8.x
[*]NI Software Support for Microsoft Windows Vista, Windows XP, and Windows Server 2003
[*]Legal Information
DocumentationThe Automotive Diagnostic Command Set User Manual is the primary reference document. This manual includes an introduction to diagnostic protocols. It also includes information about how to get started with application development and a complete reference for all Automotive Diagnostic Command Set functions. The Automotive Diagnostic Command Set User Manual is in Adobe Acrobat Portable Document Format (PDF). You can download the Acrobat Reader for free at www.adobe.com.To open the Automotive Diagnostic Command Set User Manual, go to: Programs»National Instruments»Automotive Diagnostic Command Set Manual.Supported PlatformsYou must install and run this version of the Automotive Diagnostic Command Set software on the following operating systems:
[*]Windows XP (32-bit)
[*]Windows Vista (32-bit and 64-bit)
[*]Windows 7 (32-bit and 64-bit)
[*]Windows 8.0/8.1 (32-bit and 64-bit)
For more information about using National Instruments hardware and software products with Windows 7, refer to ni.com/windows7.National Instruments recommends using Service Pack 2 when using the USB-847x interfaces in hyperthread or multicore CPU environments on Microsoft Windows XP.Supported Software and HardwareThe Automotive Diagnostic Command Set software supports the following software and hardware:
[*]NI-CAN software version 2.7 or newer
[*]NI-CAN hardware supported by NI-CAN 2.7
[*]NI-XNET software version 1.7 or newer
[*]NI-XNET CAN and LIN hardware supported by NI-XNET 1.7 or newer
[*]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)
Note: The Automotive Diagnostic Command Set software supports only National Instruments CAN hardware products.For information about software for CAN products from other vendors, refer to the documentation you received with those products.Supported Development EnvironmentsThe Automotive Diagnostic Command Set software supports the following development environments:
[*]LabVIEW 2012 (32-bit/64-bit), 2013 (32-bit/64-bit), 2014 (32-bit/64-bit), and 2015 (32-bit/64-bit)
[*]LabVIEW Real-Time (ETS) 2012, 2013, 2014, and 2015
[*]LabWindows™/CVI™ 8.5 or newer
[*]Microsoft Visual C/C++ 6.0
Note: The Automotive Diagnostic Command Set software does not support LabWindows™/CVI™ Real-Time Module.Installing the Automotive Diagnostic Command SetBefore installing the Automotive Diagnostic Command Set software, log on as Administrator or as a user with Administrator privileges. The Automotive Diagnostic Command Set software setup program must have Administrator privileges because the program modifies the configuration registry of your system. Complete the following steps to install the Automotive Diagnostic Command Set software.
[*]Insert the Automotive Diagnostic Command Set software CD into your CD-ROM drive. The installer launches if your CD-ROM drive plays data CDs automatically. If the installer does not launch automatically, navigate to the CD using Windows Explorer and launch the autorun.exe file from your Automotive Diagnostic Command Set software CD.
[*]The installation wizard guides you through the necessary steps to install the Automotive Diagnostic Command Set software. You can go back and change values where appropriate by clicking the Back button. You can exit the setup where appropriate by clicking Cancel.
[*]When the installation is complete, click Finish.
Installing Automotive Diagnostic Command Set SilentlyYou can programmatically control which features in the Automotive Diagnostic Command Set distribution to enable or disable for installation. You therefore can install a subset of the Automotive Diagnostic Command Set distribution silently. Refer to the template_spec.txt file in the specfiles directory on the Automotive Diagnostic Command Set software CD for more information about installing Automotive Diagnostic Command Set silently and selecting which features to install automatically.Installing the Automotive Diagnostic Command Set with a LabWindows/CVI UpgradeWhen you execute a LabWindows/CVI upgrade and have an Automotive Diagnostic Command Set installed on your computer, the Automotive Diagnostic Command Set supports the earlier LabWindows/CVI version.To use the Automotive Diagnostic Command Set in the new LabWindows/CVI version, complete the following steps:
[*]Uninstall the Automotive Diagnostic Command Set using the Windows Control Panel (Add or Remove Programs»National Instruments Software»NI Automotive Diagnostic Command Set).
[*]Reinstall the Automotive Diagnostic Command Set. The installation routine now recognizes the new LabWindows/CVI version and installs the support for the new LabWindows/CVI version.
Note: The Automotive Diagnostic Command Set is no longer supported in the earlier LabWindows/CVI version after you complete these steps.New Features and Changes as Compared to Automotive Diagnostic Command Set 1.0.0The Automotive Diagnostic Command Set 1.0.2 release adds the following features:
[*]The C language interface and example files location has changed.
[*]The language interface and example files for Microsoft Visual C/C++ 6.0 have moved from the Program Files\National Instruments\Automotive Diagnostic Command Set\MS Visual C\Users\Public\Documents\National Instruments\Automotive Diagnostic Command Set\MS Visual C\ directory on Windows Vista, and the Documents and Settings\All Users\Shared Documents\National Instruments\Automotive Diagnostic Command Set\Examples\MS Visual C\ directory on Windows XP. This change satisfies Windows Vista requirements when allowing users to save changes or add files to the directory.
[*]New Max RspPending Count property added: The number of times a ReqCorrectlyRcvd–RspPending (0x78) Negative Response Message is accepted to extend the command timeout (default 5). If this message is sent more often in response to a request, an error –8120 is returned. If the ECU implements commands with a long duration (for example, flash commands), extending this number may be required.
[*]New VWTP Command Timeout property added: VWTP Command Timeout is the time in milliseconds the host waits for a VWTP 2.0 command to be executed (the default is 50 ms). The specification states this as 50 ms plus the network latency, but some ECUs may require higher values.
New Features and Changes as Compared to Automotive Diagnostic Command Set 1.0.2The Automotive Diagnostic Command Set 1.0.3 release adds the following features:
[*]Added support for LabVIEW 2009.
[*]Removed support for LabVIEW 7.1.
[*]Added support for NI-XNET CAN hardware.
[*]Added support for NI CompactRIO and NI R-Series hardware.
[*]The Diag Set Property.vi default for the Fill CAN Frames property is set to 1: Replace.
[*]The Diag Set Property.vi default for the Fill Byte property is set to 255 (0xff).
[*]New output parameter in UDS DiagnosticSessionControl.vi: session parameter record returns implementation-dependent data from the ECU.
[*]New output parameter in UDS ECUReset.vi: power down time returns the minimum time of the standby sequence that the server remains in the power-down sequence in seconds. A value of FF hex indicates a failure or time not available.
[*]New VIs and corresponding ndUDS C functions:
[*]UDS RequestDownload.vi: Initiates a download of data to the ECU.
[*]UDS RequestUpload.vi: Initiates an upload of data from the ECU.
[*]UDS TransferData.vi: Transfers data to/from the ECU in a download/upload process.
[*]UDS RequestTransferExit.vi: Terminates a download or upload process initialized with UDS RequestDownload.vi or UDS RequestUpload.vi.
[*]OBD Request Permanent Fault Codes.vi: Executes the OBD Request Permanent Fault Codes service. All permanent Diagnostic Trouble Codes (DTCs) are read.
New Features and Changes as Compared to Automotive Diagnostic Command Set 1.0.3The Automotive Diagnostic Command Set 1.0.4 release adds the following features:
[*]Added support for LabVIEW 2010.
[*]Removed support for LabVIEW 8.2.
New Features and Changes as Compared to Automotive Diagnostic Command Set 1.0.4The Automotive Diagnostic Command Set 1.1 release adds the following features:
[*]Added support for LabVIEW 2011.
[*]Removed support for LabVIEW 8.5.
[*]Added OBD-II Examples for LabVIEW and LabWindows/CVI.
[*]Added support for Diagnostic over IP (ISO 13400).
[*]All examples use NI-XNET by default.
[*]Diagnostic Demo ECU supports NI-XNET.
[*]Added Diagnostic Service functions UDS06 ReadMemoryByAddress.vi and UDS06 WriteMemoryByAddress.vi to support the 2006 release of UDS (ISO 14229) (refer to the Automotive Diagnostic Command Set User Manual for more information about how to use UDS06 ReadMemoryByAddress.vi and UDS06 WriteMemoryByAddress.vi).
[*]Added new functions Diagnostic Frame Send.vi and Diagnostic Frame Recv.vi to transmit/receive CAN frames on diagnostic identifiers (for example, to tweak transport protocols such as inserting transport protocol errors).
[*]Removed dependencies to NI-CAN Installer. (If you are using NI-CAN or NI-XNET hardware from National Instruments, you need to install the NI-CAN or NI-XNET driver manually before using the Automotive Diagnostic Command Set on your dedicated CAN hardware.)
Note: Diagnostic over IP is not supported on any LabVIEW 8.6 RT target.New Features and Changes as Compared to Automotive Diagnostic Command Set 1.1The Automotive Diagnostic Command Set 1.1.1 release adds the following features:
[*]Added support for LabVIEW 2012.
[*]Removed support for LabVIEW 8.6.
New Features and Changes as Compared to Automotive Diagnostic Command Set 1.1.1The Automotive Diagnostic Command Set 1.2 release adds the following features:
[*]Added support for LabVIEW 2013.
[*]Removed support for LabVIEW 2009.
[*]Added support for Diagnostics on LIN for NI-XNET LIN devices.
[*]Added property to set the termination for CAN and LIN on NI-XNET devices.
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).
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).
ECU SimulatorThe Automotive Diagnostic Command Set software provides an ECU simulation for CAN and LIN. All examples of the Automotive Diagnostic Command Set are preconfigured to communicate with the ECU simulation.LabVIEW users can find the ECU simulator under National Instruments\LabVIEW\examples\Automotive Diagnostic Command Set\Diagnostic Demo ECU.llb.Microsoft Visual C/C++ users can find the ECU simulator under Documents and Settings\All Users\Documents\National Instruments\Automotive Diagnostic Command Set\MS Visual C\Diagnostic Demo ECU.Additional Programming TopicsThe Automotive Diagnostic Command Set software installs the necessary C/C++ support files in the following locations:
[*]On Windows 8, 7, and Vista (with Standard User Account), the typical path to the C examples folder is \Users\Public\Documents\National Instruments\Automotive Diagnostic Command Set\Examples\MS Visual C.
[*]On Windows XP, the typical path to the C examples folder is \Documents and Settings\All Users\Documents\National Instruments\Automotive Diagnostic Command Set\Examples\MS Visual C.
[*]The header file for Visual C/C++ 6 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.
Bug FixesThe following items are the IDs and titles of a subset of issues fixed between Automotive Diagnostic Command Set 1.0.4 and Automotive Diagnostic Command Set 14.0.If you have a CAR ID, you can search this list to validate that the issue has been fixed. This is not an exhaustive list of issues fixed in the current version of Automotive Diagnostic Command Set.
Bug IDFixed Issue
64116Fixed the issue that the ADCS Transport Layer API used the same VI names as the NI-CAN Channel API. The ADCS Transport Layer VI names have been changed.
421967Close Diagnostic closed the entire XNET interface. This issue has been fixed.
430716Fixed the issue that a transmission of big data blocks failed for STmin = 0.
453825The timing of consecutive frames for processing large block transfers within the ISO Transport Protocol has been fixed.
463844Fixed the issue that ADCS used the same in-memory database as NI-XNET.
The following items are the IDs and titles of a subset of issues fixed between Automotive Diagnostic Command Set 14.0 and Automotive Diagnostic Command Set 15.0.If you have a CAR ID, you can search this list to validate that the issue has been fixed. This is not an exhaustive list of issues fixed in the current version of Automotive Diagnostic Command Set.
Bug IDFixed Issue
515640Fixed the issue that you could not run an NI-XNET LIN Stream Session on the same port on which an ADCS Session was running.
515304Setting the Termination Property for a LIN Session closed the entire NI-XNET interface. This issue has been fixed.
Known IssuesThe following items are the IDs and titles of a subset of issues known to be present in Automotive Diagnostic Command Set 15.0. If you have a CAR ID, you can search this list to validate issues known not to have been addressed for this release. This is not an exhaustive list of known issues in the current version of Automotive Diagnostic Command Set.
Issue NumberIssue
514438Automotive Diagnostic Command Set 15.0 does not support any NI CompactRIO RT Controller running the NI Linux Real-Time Operating System (such as an NI cRIO-9068 or NI cRIO-903x) if you are using an NI 985x C Series module.
Automotive Diagnostic Command Set Updates and NotificationsNational Instruments posts information about critical updates and security notifications on ni.com. Visit ni.com/info and enter Info Code updates to access this information.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. However, starting with the August 2012 releases (products using NI Installers version 3.1 or later), you may need to perform additional steps before or during a silent installation of NI software.If the NI product you are installing uses Microsoft .NET 4.0, 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.0 separately before you install NI software.For more information about automating the installation of NI products, refer to the following KnowledgeBase articles:
[*]For more information about silent installations of individual NI products, refer to KB 4CJDP38M, Automating the Installation of a Single Installer.
[*]For more information about silent installations of NI products in a suite, such as NI Developer Suite, refer to KB 4GGGDQH0, How Do I Automate the Installation of a Suited Installer?.
[*]To determine what version of NI Installers your product contains, refer to KB 4CJDR18M, How Can I Determine the Type and Version of My National Instruments Installer?.
How to Use NI Software with Microsoft Windows 8.xWhen you install National Instruments software on Microsoft Windows 8.x, 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.Using NI LauncherNI Launcher helps you find and launch installed NI products. It provides you with a method of finding NI products similar to the Start menu in previous versions of Microsoft Windows. To use NI Launcher, click the NI Launcher tile in the Apps view. NI Launcher launches the desktop and opens a menu containing a list of NI products. Click any NI product to launch it.NoteNI MAX does not appear as a desktop shortcut when installed on Microsoft Windows 8.x. You can launch NI MAX either from the Apps view or from within NI Launcher.Pinning Frequently Used ApplicationsFor convenience, you can pin your most-used NI applications, such as MAX, to either the Start screen or the Taskbar on the desktop, as necessary:
Current ApplicationIcon LocationPin to Action
Windows 8.x DesktopDesktop TaskbarRight-click application and select Pin to Taskbar
Windows 8.x DesktopStart screenRight-click application and select Pin to Start
Windows 8.x Start screenDesktop TaskbarRight-click application and select Pin to taskbar from the menu bar on the bottom of the screen
Finding All ProgramsIf you want to find a particular application or related files, such as documentation files, from the Start screen, you can access all installed files from the Apps view. To get to the Apps view, right-click anywhere on the Start screen and select All apps (Windows 8.0) or click the down arrow on the bottom left of the screen (Windows 8.1).For more information about NI support for Windows 8.x, visit ni.com/windows8.Automotive Diagnostic Command Set Drops Support for Microsoft Windows Vista, Windows XP, and Windows Server 2003 in 2016Automotive Diagnostic Command Set will drop support for Microsoft Windows Vista, Windows XP, and Windows Server 2003 as of July 1, 2016. Versions of Automotive Diagnostic Command Set that ship after July 1, 2016 will not install or run on Windows Vista, Windows XP, or Windows Server 2003. For detailed information about NI application software product life cycles, visit ni.com/info and enter one of the following Info Codes:
ProductInfo Code
LabVIEWlifecycle
LabWindows™/CVI™cvi_lifecycle
Measurement Studiomstudiolifecycle
TestStandtslcp
DIAdemddlcp
SignalExpressselcp
VeriStandnivslifecycle
Legal InformationCopyright© 2007–2015 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.National Instruments 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 National Instruments trademarks. Other product and company names mentioned herein are trademarks or trade names of their respective companies.PatentsFor patents covering the National Instruments products/technology, refer to the appropriate location: Help» Patents in your software, the patents.txt file on your media, or the National Instruments Patent Notice at ni.com/patents.375413A-01
页:
[1]