Windows系统下(Linux和MAC系统下请自行了解清楚)NI的各种软件、模块、工具包、驱动程序,使用NI许可证管理器来激活的,绝大部分的都可以使用NI Lincense Activator来激活,以下链接可下载:
NI序列号Serial Number生成激活工具NI License Activator,LabVIEW/VBAI/VDM/VAS等软件模块工具包破解工具不限版本
http://pcmv.cn/thread-490-1-1.html
视觉论坛的各种资源,除了视觉相关的模块有使用外,大部分的都不会使用,所以仅提供资源不能提供技术支持。资源的下载地址一般会同时提供NI官方地址和百度网盘的下载地址。某些工具包NI的地址失效或没有NI的下载地址,那视觉论坛也没有办法,只能尝试使用百度网盘地址下载;如果百度网盘的下载地址失效过期,可联系论坛客服更新。现在NI的下载服务器对我国IP地址不是很友好,有些时候速度很慢或大的资源下载很容易出错,这样会造成安装过程各种类型报错而无法安装。建议在下载完成后,对下载资源做校验和验证(NI一般会提供MD5或SHA256等),与官方或视觉论坛提供的校验和对比,一致就可以安装,如果不一致,则需要重新下载。视觉论坛早期下载的资源,那时候NI没有这么多限制,基本上都是正常下载的资源;后期下载的资源,都与NI的正确校验和对比过,保证是正确的资源才上传到百度网盘,所以百度网盘的资源基本上是正确的。校验和工具下载地址:
文件Hash计算器FHash,文件校验和验证下载文件正确性验证,MD5值计算、SHA1值计算、SHA256值计算、CRC32值计算
http://pcmv.cn/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官方下载地址:
NI Automotive Diagnostic Command Set Toolkit 15.0 Runtime Win32/64Eng 汽车诊断命令集工具包ADCS15.0运行版下载
http://pcmv.cn/thread-25686-1-1.html?fromuid=9
(出处: 视觉论坛VISIONBBS|视觉之家VISIONHOME)
Automotive Diagnostic Command Set 15.0 Readme
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
Documentation
Supported Platforms
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)
Supported 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)
Supported 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
Installing the Automotive Diagnostic Command Set
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 Silently
Installing the Automotive Diagnostic Command Set with a LabWindows/CVI Upgrade
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.
New Features and Changes as Compared to Automotive Diagnostic Command Set 1.0.0
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 FilesNational InstrumentsAutomotive Diagnostic Command SetMS Visual CUsersPublicDocumentsNational InstrumentsAutomotive Diagnostic Command SetMS Visual C directory on Windows Vista, and the Documents and SettingsAll UsersShared DocumentsNational InstrumentsAutomotive Diagnostic Command SetExamplesMS 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.2
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.3
Added support for LabVIEW 2010.
Removed support for LabVIEW 8.2.
New Features and Changes as Compared to Automotive Diagnostic Command Set 1.0.4
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.)
New Features and Changes as Compared to Automotive Diagnostic Command Set 1.1
Added support for LabVIEW 2012.
Removed support for LabVIEW 8.6.
New Features and Changes as Compared to Automotive Diagnostic Command Set 1.1.1
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.2
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.0
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 Simulator
Additional Programming Topics
On Windows 8, 7, and Vista (with Standard User Account), the typical path to the C examples folder is UsersPublicDocumentsNational InstrumentsAutomotive Diagnostic Command SetExamplesMS Visual C.
On Windows XP, the typical path to the C examples folder is Documents and SettingsAll UsersDocumentsNational InstrumentsAutomotive Diagnostic Command SetExamplesMS Visual C.
The header file for Visual C/C++ 6 is in the Program FilesNational InstrumentsSharedExternalCompilerSupportCinclude folder.
The library file is in the Program FilesNational InstrumentsSharedExternalCompilerSupportClib32msvc folder.
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 Fixes
Bug ID | Fixed Issue |
64116 | Fixed 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. |
421967 | Close Diagnostic closed the entire XNET interface. This issue has been fixed. |
430716 | Fixed the issue that a transmission of big data blocks failed for STmin = 0. |
453825 | The timing of consecutive frames for processing large block transfers within the ISO Transport Protocol has been fixed. |
463844 | Fixed the issue that ADCS used the same in-memory database as NI-XNET. |
Bug ID | Fixed Issue |
515640 | Fixed the issue that you could not run an NI-XNET LIN Stream Session on the same port on which an ADCS Session was running. |
515304 | Setting the Termination Property for a LIN Session closed the entire NI-XNET interface. This issue has been fixed. |
Known Issues
Issue Number | Issue |
514438 | Automotive 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 Notifications
Automating the Installation of NI Products
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.x
Using NI Launcher
Pinning Frequently Used Applications
Current Application | Icon Location | Pin to Action |
Windows 8.x Desktop | Desktop Taskbar | Right-click application and select Pin to Taskbar |
Windows 8.x Desktop | Start screen | Right-click application and select Pin to Start |
Windows 8.x Start screen | Desktop Taskbar | Right-click application and select Pin to taskbar from the menu bar on the bottom of the screen |
Finding All Programs
Automotive Diagnostic Command Set Drops Support for Microsoft Windows Vista, Windows XP, and Windows Server 2003 in 2016
Product | Info Code |
LabVIEW | lifecycle |
LabWindows™/CVI™ | cvi_lifecycle |
Measurement Studio | mstudiolifecycle |
TestStand | tslcp |
DIAdem | ddlcp |
SignalExpress | selcp |
VeriStand | nivslifecycle |
Legal Information
Notices are located in the <National Instruments>_Legal Information and <National Instruments> directories.
EULAs are located in the <National Instruments>SharedMDFLegallicense directory.
Review <National Instruments>_Legal Information.txt for information on including legal information in installers built with NI products.