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-XNET 18.0 Runtime Driver Download 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 Runtime Driver Download Win32/64 Eng/Ger/Jpn NI-XNET仪器驱动程序18.0运行时下载
http://pcmv.cn/thread-25176-1-1.html?fromuid=9
(出处: 视觉论坛VISIONBBS|视觉之家VISIONHOME)
NI-XNET 18.0 Readme
Overview
Supported Operating Systems
Windows 10/8.11/7 SP12
Windows Embedded Standard 7 SP12
Windows Server 2012 R21
Windows Server 2008 R2 SP12
Application Software Support
Application Software1 | Versions Supported by NI-XNET 18.0 |
LabVIEW | 2015, 2016, 2017, and 2018 |
LabVIEW Real-Time (RT) | 2015, 2016, 2017, and 2018 |
LabVIEW NXG | 2.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 Support
Programming Languages | Versions Supported by NI-XNET 18.0 |
Microsoft Visual C/C++ | 6.0 and later |
Installation Instructions
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 Updates
New Features and ChangesNew NI-XNET 18.0 Features and Changes as Compared to NI-XNET 17.5.1
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.
Removed support for LabVIEW 2014.
New NI-XNET 17.5.1 Features and Changes as Compared to NI-XNET 17.5
Bug Fix for cDAQ-9171 support.
New NI-XNET 17.5 Features and Changes as Compared to NI-XNET 17.0.1
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).
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.
Removed support for CVI 2012.
New NI-XNET 17.0.1 Features and Changes as Compared to NI-XNET 17.0
Bug Fix for LabVIEW 64-bit support.
New NI-XNET 17.0 Features and Changes as Compared to NI-XNET 16.1
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.
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.0
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.
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:
CompactDAQ—NI-DAQmx 15.0 (or newer) is required for:
CompactDAQ—NI-DAQmx 15.1 (or newer) is required for:
CompactDAQ—NI-DAQmx 17.1 (or newer) is required for:
CompactRIO—CompactRIO 18.0 (or newer) and LabVIEW 2015 (or newer) are required for the following targets:
CompactRIO—CompactRIO 18.0 (or newer) and LabVIEW 2016 (or newer) are required for the following targets:
CompactRIO—CompactRIO 18.0 (or newer) and LabVIEW 2017 (or newer) are required for the following targets:
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)
USB Chassis: cDAQ-9179
cDAQ Controller: cDAQ-9136 (Windows and RT) and cDAQ-9137 (Windows and RT)
Ethernet Chassis: cDAQ-9185 and cDAQ-9189
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 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 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.
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:
Known Issues
Issue Number | Issue |
672838 | Inserting 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. |
675253 | When using the Port Configuration Utility, it is not possible to rename ports beyond 160. |
684861 | NI-XNET does not handle J1939 PDU1 broadcasts properly. |
684951 | Unaddressed J1939 Input Queue and Signal sessions do not receive data unless a stream session is also open on the interface. |
685825 | J1939 FIBEX databases that contain ECU names are not imported correctly, and saving the database will result in overwriting the name with 0. |
687144 | Extremely long strings passed to the XNET Create Session VI can cause LabVIEW to crash. |
687562 | Rev 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. |
687624 | NI-XNET CAN FD sessions (non-BRS) require CAN FD Baudrate to be set. |
688639 | Having multiple startup VIs that contain NI-XNET project sessions can cause a LabVIEW RT target to hang. |
Bug Fixes
Bug ID | Summary |
664692 | In certain situations, removed hardware could appear as CAN-1, LIN-1, or FlexRay-1. |
667510 | Properties configured when adding an alias are ignored the first time the database is opened after modifying the source database. |
673342 | Errors returned from XNET property nodes cannot be cleared until all running VIs stop in LabVIEW. |
674352 | Bus Monitor and Database Editor display incorrect baud rate details for custom baud rates. |
679050 | In a built application (exe), some XNET I/O Controls do not show any values in the drop-down menu. |
684806 | Applications mixing the use of 32-bit and 64-bit baud rate properties causes errors. |
684870 | Expanding an XNET Device, Subframe, or LIN Schedule Entry IO control in an empty project crashes LabVIEW NXG. |
686078 | Default output payloads not handled properly for J1939 frames with payloads greater than 255 bytes. |
686083 | Transmitting multiple J1939 frames of different sizes in rapid succession results in corrupted frames on the bus. |
686442 | Reading single point frame input sessions with an insufficient frame count can cause LabVIEW to crash. |
Additional Programming TopicsNI-CAN Compatibility
Deployed databases on LabVIEW Real-Time targets
Removing and inserting C Series modules on CompactRIO targets during device communication is not supported
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 NI Installer?.
Using NI Software with Microsoft Windows 10
Using NI Software with Microsoft Windows 8.1
LabVIEW NXG Support and Considerations
LabVIEW NXG Operating Systems and System Requirements
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 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 Help
LabVIEW NXG Examples
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.