NI-XNET 18.0 Runtime Driver Win32/64 Eng/Ger/Jpn NI-XNET仪器驱动程序18.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-XNET 18.0 Runtime Driver Win32/64 Eng/Ger/Jpn NI-XNET仪器驱动程序18.0运行时下载
NI-XNET
NI-XNET为配置、开发和调试应用程序提供支持，适用于汽车以太网、CAN、LIN和FlexRay网络的原型验证、仿真和测试。
NI-XNET是一个NI仪器驱动程序，具有一组易用的常见功能，用于读写PXI、PCI、NI CompactDAQ和NI CompactRIO等不同平台的汽车以太网、CANI、LIN和FlexRay帧和信号。NI-XNET CAN、LIN和FlexRay接口经优化，适合需要对数百个CAN帧和信号进行高速实时操作的应用，如硬件在环仿真、快速控制原型、总线监控和自动化控制等。
18.0Runtime
文件大小: 183607872 字节 (175.10 MB)
修改日期: 2019-06-25 02:43
MD5: 1c721494276122b94493a1c66d4a1a8d（官方正确）
SHA1: e112e8452f42d0e5a47d5b8edea7d9f06b45d378
SHA256: 31b7de247904eeab857df64ab84b64d69450f5e57661c4dfac6b7adbfa8be478
CRC32: 80124396
NI-XNET 18.0 ReadmeMay 2018This file contains important information about NI-XNET, including installation instructions and known issues.OverviewSupported Operating SystemsApplication Software SupportInstallation InstructionsProduct Security and Critical UpdatesNew Features and ChangesSupported HardwareBug FixesAdditional Programming TopicsAutomating the Installation of NI ProductsUsing NI Software with Microsoft Windows 10Using NI Software with Microsoft Windows 8.1LabVIEW NXG Support and ConsiderationsLegal InformationOverviewNI-XNET is an NI instrument driver that features a common set of easy-to-use functions for reading and writing CAN, LIN, and FlexRay frames and signals in many different platforms including USB, PXI, PCI, NI CompactDAQ, and NI CompactRIO.Supported Operating SystemsNI-XNET supports the following operating systems:
[*]Windows 10/8.11/7 SP12
[*]Windows Embedded Standard 7 SP12
[*]Windows Server 2012 R21
[*]Windows Server 2008 R2 SP12
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/info and enter the Info Code PAESupport.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 for more information about how to install this security update.The NI-XNET installer does not support Windows Server 2003/NT/Vista/XP/Me/2000/98/95 or the Windows Server non-R2 editions.NI-XNET does not support guest accounts on Windows 7. You must log into an administrative or user account to use NI-XNET on these operating systems.Application Software SupportThe following table lists the application software versions supported by NI-XNET.
Application Software1Versions Supported by NI-XNET 18.0
LabVIEW2015, 2016, 2017, and 2018
LabVIEW Real-Time (RT)2015, 2016, 2017, and 2018
LabVIEW NXG2.1
LabWindows™/CVI™2013 and higher
1 Application software support for LabVIEW NXG is not included with NI-XNET and must be downloaded separately via NI Package Manager. Refer to Installing NI-XNET for LabVIEW NXG for instructions.
Microsoft Visual Studio SupportNI-XNET supports the following Microsoft Visual Studio versions and associated programming languages.
Programming LanguagesVersions Supported by NI-XNET 18.0
Microsoft Visual C/C++6.0 and later
Installation InstructionsRefer to the following instructions to install NI-XNET from a DVD. To install NI-XNET for LabVIEW NXG, refer to Installing NI-XNET for LabVIEW NXG.Before installing the NI-XNET software, log on as Administrator or as a user with Administrator privileges. The NI-XNET software setup program must have Administrator privileges because the program modifies the configuration registry of your system. Complete the following steps to install the NI-XNET software.
[*]Insert the NI-XNET software DVD into the DVD drive. If the installer does not launch automatically, navigate to the DVD using Windows Explorer and launch the autorun.exe file from your NI-XNET software DVD.
[*]Click Install.
[*]The installation wizard guides you through the necessary steps to install the NI-XNET 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.
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 Features and ChangesNew NI-XNET 18.0 Features and Changes as Compared to NI-XNET 17.5.1The NI-XNET 18.0 release adds the following features:
[*]Added ability in System Designer to discover XNET hardware ports and select new names for them. (LabVIEW NXG)
[*]Added a new J1939 session property, SAE J1939:Include Destination Address in PGN. (C and LabVIEW 2018 only)
[*]Added support for LabVIEW NXG 2.1.
[*]Added support for LabVIEW 2018.
The NI-XNET 18.0 release changes the following:
[*]Removed support for LabVIEW 2014.
New NI-XNET 17.5.1 Features and Changes as Compared to NI-XNET 17.5The NI-XNET 17.5.1 release changes the following:
[*]Bug Fix for cDAQ-9171 support.
New NI-XNET 17.5 Features and Changes as Compared to NI-XNET 17.0.1The NI-XNET 17.5 release adds the following features:
[*]Read LIN clusters from AUTOSAR 3.x and 4.x files.
[*]Extract LIN frames and signals. The signal names are the names of the SYSTEM-SIGNAL instances.
[*]Attach LIN frames to the ECUs as "Rx/Tx."
[*]Extract LIN cluster specific information (i.e. schedules and configuration frames).
NotesNI-XNET supports PDUs only if there is a 1:1 mapping between the PDU and frame layout. The import is limited to features supported by the NI-XNET driver.[*]Added user accessible checksum values to NI-XNET LIN frames.
[*]Added support for ISC-178X smart cameras.
[*]Added support for signals larger than 52 bits in the API and the Database Editor.
[*]Signals up to 64 bits can be read/written as double floating point (rounded).
[*]Signals of any size can be read/written as byte strings using a conversion session.
The NI-XNET 17.5 release changes the following:
[*]Removed support for CVI 2012.
New NI-XNET 17.0.1 Features and Changes as Compared to NI-XNET 17.0The NI-XNET 17.0.1 release changes the following:
[*]Bug Fix for LabVIEW 64-bit support.
New NI-XNET 17.0 Features and Changes as Compared to NI-XNET 16.1The NI-XNET 17.0 release adds the following features:
[*]Support for LabVIEW 2017.
[*]Support for PCIe-8510.
[*]Read CAN clusters from AUTOSAR 3.x and 4.x files.
[*]Extract CAN frames and signals. The signal names are the names of the SYSTEM-SIGNAL instances.
[*]Attach CAN frames to the ECUs as "Rx/Tx."
[*]Extract CAN FD specific settings.
NotesNI-XNET supports PDUs only if there is a 1:1 mapping between the PDU and frame layout. The import is limited to features supported by the NI-XNET driver.
The NI-XNET 17.0 release changes the following:
[*]Improvements that require a firmware update for NI 9860 modules and the cDAQ integrated XNET port.
[*]Removed support for LabVIEW 2013.
[*]Removed support for CVI 2010.
New NI-XNET 16.1 Features and Changes as Compared to NI-XNET 16.0The NI-XNET 16.1 release adds the following features:
[*]Added support for the USB-850x USB modules.
[*]Added C-API examples for J1939.
[*]Enabled setting a custom baud rate for ISO CAN FD in the Bus Monitor and Database Editor.
[*]Enabled excluding IDs in the Bus Monitor.
[*]Enabled setting a node address for J1939 in the Bus Monitor.
The NI-XNET 16.1 release changes the following:
[*]Removed support for CVI 8.5, 9.0, and 2009.
Supported Hardware
[*]USB-8502 (High-Speed/FD CAN)
[*]USB-8506 (LIN)
[*]PCI-8511 (Low-Speed/Fault-Tolerant CAN)
[*]PCI-8512 (High-Speed/FD CAN)
[*]PCI-8513 (Software-Selectable/FD CAN)
[*]PCI-8516 (LIN)
[*]PCI-8517 (FlexRay)
[*]PCIe-8510 (Hardware-Selectable)
[*]PXI-8511 (Low-Speed/Fault-Tolerant CAN)
[*]PXI-8512 (High-Speed/FD CAN)
[*]PXI-8513 (Software-Selectable/FD CAN)
[*]PXI-8516 (LIN)
[*]PXI-8517 (FlexRay)
[*]PXIe-8510 (Hardware-Selectable)
[*]TRC-8542 NI-XNET CAN HS/FD Transceiver Cable
[*]TRC-8543 NI-XNET CAN XS (LS/FT, HS/FD)Transceiver Cable
[*]TRC-8546 NI-XNET LIN Transceiver Cable
[*]C Series modules:
[*]NI 9861 (C Series Low-Speed CAN)
[*]NI 9862 (C Series High-Speed/FD CAN)
[*]NI 9866 (C Series LIN)
[*]NI 9860 (C Series Hardware-Selectable)
Supported platforms for XNET C Series modules:
[*]CompactDAQ—NI-DAQmx 15.0 (or newer) is required for:
[*]USB Chassis: cDAQ-9171, cDAQ-9174, and cDAQ-9178
[*]Ethernet Chassis: cDAQ-9181, cDAQ-9184, and cDAQ-9188
[*]Wireless Chassis: cDAQ-9191
[*]cDAQ Controller: cDAQ-9138 (Windows and RT) and cDAQ-9139 (Windows and RT)
[*]cDAQ Controller: cDAQ-9132 (Windows and RT) and cDAQ-9134 (Windows and RT)
[*]cDAQ Controller: cDAQ-9133 (Windows and RT) and cDAQ-9135 (Windows and RT)
[*]CompactDAQ—NI-DAQmx 15.1 (or newer) is required for:
[*]USB Chassis: cDAQ-9179
[*]cDAQ Controller: cDAQ-9136 (Windows and RT) and cDAQ-9137 (Windows and RT)
[*]CompactDAQ—NI-DAQmx 17.1 (or newer) is required for:
[*]Ethernet Chassis: cDAQ-9185 and cDAQ-9189
[*]CompactRIO—CompactRIO 18.0 (or newer) and LabVIEW 2015 (or newer) are required for the following targets:
[*]LabVIEW FPGA is required to build and deploy a bitstream with NI 986x modules in the project, unless otherwise specified.
[*]Real-Time Controller: cRIO-9012, cRIO-9014, cRIO-9022, cRIO-9023, cRIO-9024, and cRIO-9025
[*]CompactRIO Reconfigurable Chassis: cRIO-9111, cRIO-9112, cRIO-9113, cRIO-9114, cRIO-9116, and cRIO-9118
[*]Integrated CompactRIO Real-Time Controller: cRIO-9081, cRIO-9082, cRIO-906x, and cRIO-903x
[*]Single-Board RIO: sbRIO-9627, sbRIO-9607
[*]CompactRIO Real-Time Controller: cRIO-9032, cRIO-9037
[*]When using a cRIO-903x or cRIO-906x, a bitstream is not needed with NI 986x modules in the project.
[*]CompactRIO—CompactRIO 18.0 (or newer) and LabVIEW 2016 (or newer) are required for the following targets:
[*]CompactRIO Real-Time Controller: cRIO-9035 (Sync), cRIO-9039 (Sync)
[*]When using a cRIO-903x, a bitstream is not needed with NI 986x modules in the project.
[*]CompactRIO—CompactRIO 18.0 (or newer) and LabVIEW 2017 (or newer) are required for the following targets:
[*]CompactRIO Real-Time Controller: cRIO-9040, cRIO-9042, cRIO-9043, cRIO-9045, cRIO-9047, cRIO-9048, and cRIO-9049
[*]When using a cRIO-904x, NI 986x modules will only be usable in Real-Time mode, and no bitstream is necessary.
The NI-XNET software supports only National Instruments CAN, FlexRay, and LIN hardware products. For information about software for CAN products from other vendors, refer to the documentation you received with those products.Known Issues
Issue NumberIssue
672838Inserting a USB-850x device can result in an unusable device with internal errors on PharLap. Workaround: Remove and reinsert the device or reboot the system.
675253When using the Port Configuration Utility, it is not possible to rename ports beyond 160.
684861NI-XNET does not handle J1939 PDU1 broadcasts properly.
684951Unaddressed J1939 Input Queue and Signal sessions do not receive data unless a stream session is also open on the interface.
685825J1939 FIBEX databases that contain ECU names are not imported correctly, and saving the database will result in overwriting the name with 0.
687144Extremely long strings passed to the XNET Create Session VI can cause LabVIEW to crash.
687562Rev C (and later) PCI/PXI-8511 and -8512 devices might switch to Bus Off when attempting to transmit immediately following a reboot or Self-Test.
687624NI-XNET CAN FD sessions (non-BRS) require CAN FD Baudrate to be set.
688639Having multiple startup VIs that contain NI-XNET project sessions can cause a LabVIEW RT target to hang.
Bug FixesThe following items are the IDs and titles of a subset of issues fixed in this release. This is not an exhaustive list of issues fixed. If you have a CAR ID, you can search this list to validate that the issue has been fixed.
Bug IDSummary
664692In certain situations, removed hardware could appear as CAN-1, LIN-1, or FlexRay-1.
667510Properties configured when adding an alias are ignored the first time the database is opened after modifying the source database.
673342Errors returned from XNET property nodes cannot be cleared until all running VIs stop in LabVIEW.
674352Bus Monitor and Database Editor display incorrect baud rate details for custom baud rates.
679050In a built application (exe), some XNET I/O Controls do not show any values in the drop-down menu.
684806Applications mixing the use of 32-bit and 64-bit baud rate properties causes errors.
684870Expanding an XNET Device, Subframe, or LIN Schedule Entry IO control in an empty project crashes LabVIEW NXG.
686078Default output payloads not handled properly for J1939 frames with payloads greater than 255 bytes.
686083Transmitting multiple J1939 frames of different sizes in rapid succession results in corrupted frames on the bus.
686442Reading single point frame input sessions with an insufficient frame count can cause LabVIEW to crash.
Additional Programming TopicsNI-CAN CompatibilityIf you intend to use the NI-CAN API with your NI-XNET PCI/PXI hardware, refer to the NI-XNET Compatibility for NI-CAN appendix in the NI-CAN Hardware and Software Manual.Deployed databases on LabVIEW Real-Time targetsWhen upgrading the NI-XNET software on your LabVIEW Real-Time target, you need to re-deploy your database files to that target using a host computer that runs the same version of NI-XNET as the target.Removing and inserting C Series modules on CompactRIO targets during device communication is not supportedInserting a module into or removing a module from a cRIO chassis that is actively communicating with an NI 986x module can cause application failures and possibly device damage.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.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 NI Installer?.
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.LabVIEW NXG Support and ConsiderationsThe following sections detail considerations for using NI-XNET with LabVIEW NXG.LabVIEW NXG Operating Systems and System RequirementsSoftware support for LabVIEW NXG differs in the following ways:
[*]System requirements—Only 64-bit (x64) processors are supported.
[*]Operating system—Only 64-bit operating systems are supported. Refer to the Supported Operating Systems section for more information.
Installing NI-XNET for LabVIEW NXGLabVIEW NXG is installed using NI Package Manager. Complete the following steps to install NI-XNET for LabVIEW NXG.
[*]Visit ni.com/info and enter the info code NXGDownload to access the LabVIEW NXG download page.
[*]Click Download LabVIEW NXG.
[*]NI Package Manager installs, and then automatically opens a download window.
[*]Select LabVIEW NXG Suite, and click the green Install button.
[*]Select LabVIEW NXG 2.1 and NI-XNET.
[*]Complete the installer instructions to download LabVIEW NXG and NI-XNET.
LabVIEW NXG HelpView context help in LabVIEW by pressing <Ctrl-H> and hovering over an object.Search for items using the search bar in the upper right corner of the LabVIEW window. You can also view context help for the search results.Additional documentation is available online at ni.com/manuals.LabVIEW NXG ExamplesLaunch LabVIEW and click the Learning tab.LabVIEW lessons are located in the Lessons tab, and LabVIEW Examples are located in the Examples tab. Follow the instructions in the lessons and examples.Legal InformationCopyright© 2009–2018 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.
374802L-01
页:
[1]