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 19.5 Driver Download Win32/64 Eng/Ger/Jpn NI-XNET仪器驱动程序19.5下载
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帧和信号进行高速实时操作的应用,如硬件在环仿真、快速控制原型、总线监控和自动化控制等。
19.5
文件大小: 1776259072 字节 (1.65 GB)
修改日期: 2019-10-25 22:50
MD5: a9658a6adad9b5ef696d16c35458f61a(官方正确)
SHA1: 4221531e14e6ee8275c3cd8688c5829528472ea5
SHA256: 8f88f16dbf1aecf47708ac0e778dfba08340de35e9d85668f70ba2d2b0add08a
CRC32: 3c6925a6
NI-XNET 19.5 Driver Download Win32/64 Eng/Ger/Jpn NI-XNET仪器驱动程序19.5下载
http://pcmv.cn/thread-25181-1-1.html?fromuid=9
(出处: 视觉论坛VISIONBBS|视觉之家VISIONHOME)
NI-XNET 19.5 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 Software3 | Versions Supported by NI-XNET 19.5 |
LabVIEW | 2016, 2017, 2018, and 2019 |
LabVIEW Real-Time (RT) | 2016, 2017, 2018, and 2019 |
LabVIEW NXG | 4.0 |
LabWindows™/CVI™ | 2013 and later |
3 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 19.5 |
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 19.5 Features and Changes as Compared to NI-XNET 19.1
Added support for LabVIEW NXG 4.0.
Added support for sbRIO-9603, sbRIO-9608, sbRIO-9609, sbRIO-9628, sbRIO-9629, and sbRIO-9638 chassis.
Added support for PXIe-8522 and PXIe-8523 Automotive Ethernet modules.
New NI-XNET 19.1 Features and Changes as Compared to NI-XNET 19.0
Added support for PXI controllers running NI Linux Real-Time for NI-XNET PCI, PXI, PCIe, PXIe, and C Series devices4.
Added support for network time synchronization with the PXIe-8521 while in Tap mode.
Added support for the PXIe-8521 in LabVIEW NXG 3.1.
New NI-XNET 19.0 Features and Changes as Compared to NI-XNET 18.5
Added support for LabVIEW 2019.
Added support for the PXIe-8521 4-port, 100BASE-T1 Automotive Ethernet Interface Module.
Extended the NI-XNET LabVIEW API to support Automotive Ethernet.
Removed support for LabVIEW 2015.
Removed support for NI-XNET C series modules in a cDAQ chassis when attached to a controller or host running Phar Lap. Support for other Operating Systems remains unaffected.
Removed support for cRIO-9012 and cRIO-9014 controllers. Note that these targets may still support installation, but they are no longer officially supported, and may be removed in a future release.
Changed behavior for Signal Input Waveform sessions to address defects.
Changed options for building LabVIEW or CVI application installers: "NI-XNET Runtime" installs only the NI-XNET Runtime, "NI-XNET Utilities" installs the NI-XNET Database Editor and Bus Monitor in addition to the NI-XNET Runtime.
New NI-XNET 18.5 Features and Changes as Compared to NI-XNET 18.0
Added support for LabVIEW NXG 3.0.
Added support for LabVIEW 2018 SP1.
Added support for the USB-8501 NI-XNET CAN LS/FT Interface.
Added support for importing CAN FD settings from FIBEX 4.1.2 databases.
Added support for J1939 session property, SAE J1939:Include Destination Address in PGN, in LabVIEW NXG.
Lowered the default value for the nxPropSession_J1939ResponseTimeTrSD property from 0.05 s to 0 s to improve performance in handling multipacket messages.
Improved performance when opening large database files.
Removed support for LabVIEW NXG 2.0 and 2.1.
New NI-XNET 18.0 Features and Changes as Compared to NI-XNET 17.5.1
Added ability in SystemDesigner 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 (e.g., 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.
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.
Supported Hardware
USB-8501 Low-Speed/Fault Tolerant USB CAN Interface Device
USB-8502 High-Speed/FD USB CAN Interface Device
USB-8506 USB LIN Interface Device
PCI-8511 Low‑Speed/Fault-Tolerant CAN Interface Device
PCI-8512 High‑Speed/FD CAN Interface Device
PCI-8513 Software‑Selectable/FD CAN Interface Device
PCI-8516 PCI LIN Interface Device
PCI-8517 FlexRay Interface Device
PCIe-8510 PCIe Vehicle Multi-Protocol Interface Device
PXI-8511 Low-Speed/Fault Tolerant PXI CAN Interface Module
PXI-8512 High-Speed, Flexible Data Rate PXI CAN Interface Module
PXI-8513 Software-Selectable PXI CAN Interface Module
PXI-8516 PXI LIN Interface Module
PXI-8517 PXI FlexRay Interface Module
PXIe-8510 PXI Vehicle Multiprotocol Interface Module
PXIe-8521 100BASE-T1 PXI Automotive Ethernet Interface Module
PXIe-8522 1000BASE-T1 PXI Automotive Ethernet Interface Module
PXIe-8523 100/1000BASE-T1 PXI Automotive Ethernet Interface Module
TRC-8542 CAN HS/FD Transceiver Cable
TRC-8543 CAN HS/FD or LS/FT Transceiver Cable
TRC-8546 LIN Transceiver Cable
NI 9860 C Series Vehicle Multiprotocol Interface Module
NI 9861 Low-Speed/Fault Tolerant C Series CAN Interface Module
NI 9862 High-Speed, Flexible Data Rate C Series CAN Interface Module
NI 9866 C Series LIN Interface Module
CompactDAQ—NI-DAQmx 16.0 (or later) is required for:
USB Chassis: cDAQ-9171, cDAQ-9174, cDAQ-9178, and cDAQ-9179
Ethernet Chassis: cDAQ-9181, cDAQ-9184, and cDAQ-9188
Wireless Chassis: cDAQ-9191
cDAQ Controller: cDAQ-9138 (Windows only) and cDAQ-9139 (Windows only)
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)
cDAQ Controller: cDAQ-9136 (Windows and RT) and cDAQ-9137 (Windows and RT)
CompactDAQ—NI-DAQmx 17.1 (or later) is required for:
Ethernet Chassis: cDAQ-9185 and cDAQ-9189
CompactRIO—CompactRIO 19.5 (or later) and LabVIEW 2016 (or later) are required for the following targets:
LabVIEW FPGA is required to build and deploy a bit stream with NI 986x modules in the project, unless otherwise specified.
Real-Time Controller: 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
CompactRIO Real-Time Controller: cRIO-9035 (Sync), cRIO-9039 (Sync)
When using a cRIO-903x or cRIO-906x, a bit stream is not needed with NI 986x modules in the project.
CompactRIO—CompactRIO 19.5 (or later) and LabVIEW 2017 (or later) 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 bit stream is necessary.
CompactRIO—CompactRIO 19.5 (or later) and LabVIEW 2018 (or later) are required for the following targets:
CompactRIO Real-Time Controller: cRIO-9053, cRIO-9054, cRIO-9056, and cRIO-9057
When using a cRIO-905x, NI 986x modules will only be usable in Real-Time mode, and no bit stream is necessary.
CompactRIO—CompactRIO 19.5 (or later) and LabVIEW 2019 (or later) are required for the following targets:
Single-Board RIO: sbRIO-9603, sbRIO-9608, sbRIO-9609, sbRIO-9628, sbRIO-9629, sbRIO-9638
When using an sbRIO-9603, sbRIO-9608, sbRIO-9609, sbRIO-9628, sbRIO-9629, or sbRIO-9638, NI 986x modules will only be usable in Real-Time mode, and no bit stream is necessary.
Known Issues
Issue Number | Summary |
672838 | Inserting a USB-850x device can result in an unusable device with internal errors on Phar Lap. Workaround: Remove and reinsert the device or reboot the system. |
687624 | NI-XNET CAN FD sessions (non-BRS) require CAN FD Baud Rate to be set. |
697677 | NI-XNET does not import the DBC BO_TX_BU property from DBC files and prevents a TX frame from being mapped to multiple transmit ECUs. |
703292 | The J1939 address claim procedure does not detect conflicts between two ECUs running on the same XNET interface. |
704022 | XNET Read (Frame CAN) can return fewer than the requested number of J1939 frames without reporting an error as specified in the documentation. |
705533 | Frame Output Queued sessions do not retransmit cyclic J1939 frames with payloads greater than 8 bytes. These transmit one time when the session starts, and then only when new data is written to the session. |
705671 | Switching a J1939 session to a different ECU Node Name does not use the address from the new ECU, even if that ECU has already claimed an address. The node address must be set after the node name to properly configure the session. |
710192 | The NI-XNET Database Editor does not allow you to create a signal with the same name as one that was previously deleted. Avoid this issue by saving the database and re-opening it after deleting the signal. |
710389 | XNET Wait (Transmit Complete) may cause a stale FlexRay frame to retransmit if the transmit queue is already empty. |
724930 | If XNET Read (Frame Raw) times out partly through reading Ethernet frames, the subset of frames that were successfully read are discarded and are no longer available from the NI-XNET session. |
727473 | NI-XNET Signal Output Single-Point sessions always write mode 0 subframes by default, even if no mode 0 subframe is present for the multiplexer. Avoid this issue by writing initial signal values, including the multiplexer signal, prior to starting the session. |
730930 | Ethernet device PHY State and Port Mode properties are not reset to default values after NI-XNET is uninstalled and reinstalled. |
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 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.