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地址,只能使用百度网盘地址;如果百度网盘地址失效过期,可联系论坛客服更新。NI的服务器在美国,有时候速度很慢或下载容易出错,这样会造成安装时各种错误而无法安装。建议在下载完成后,对下载资源做校验和(NI一般会提供MD5或SHA256等)验证,与官方或视觉论坛提供的校验和对比,一致就可以安装;如不一致,则需要重新下载。视觉论坛早期下载上传的资源,基本上都是正常下载的资源;2019后下载的资源,都与NI的正确校验和对比过,保证是正确的资源才上传到百度网盘。校验和工具下载地址:文件Hash计算器FHash,文件校验和验证下载文件正确性验证,MD5值计算、SHA1值计算、SHA256值计算、CRC32值计算http://pcmv.cn/thread-26524-1-1.html
NI-CAN 17.0 Driver Win32Eng/Ger/Fre/Jpn NI控制器局域网驱动软件17.0下载
NI-CAN
NI-CAN用于支持开发和部署多个控制器局域网(CAN)应用程序。
NI-CAN驱动软件适用于多种类型的CAN硬件应用程序,如高速CAN、容错CAN和LIN接口。NI-CAN具有强大的底层框架API和上层通道,可实现快速开发。NI-CAN用于为LabVIEW、LabWindows/CVI和ANSI C/C++提供本地支持。此外,NI-CAN还包括通道测试面板、总线监控器和记录器以及数据库编辑器等工具。LabWindows标志经Microsoft公司授权使用。Windows是Microsoft公司在美国和其他国家的注册商标。
Win32Eng/Ger/Fre/Jpn
17.0
文件大小: 448708544 字节 (427.92 MB)
修改日期: 2017-05-22 21:16
MD5: 4627ba40cd473d735196a40901a85d24(官方正确)
SHA1: 54731cc4e68f3f15f8fe3c6e93c6a7fb65235e80
SHA256: d701690db483b650b30871ef350a84e2e9e9d57ec5ce37340c7af6f0828618ae
CRC32: f31c1785
百度网盘和NI官方下载地址:
NI-CAN 17.0 Driver Win32Eng/Ger/Fre/Jpn NI控制器局域网驱动软件17.0下载
http://pcmv.cn/thread-26189-1-1.html?fromuid=9
(出处: 视觉论坛VISIONBBS|视觉之家VISIONHOME)
NI-CAN 17.0 Readme
Documentation
Supported Platforms
Installing NI-CAN
Product Security and Critical Updates
New Features and Changes
Known Issues
Bug Fixes
Additional Programming Topics
Release Notes
Automating the Installation of NI Products
Using NI Software with Microsoft Windows 10
Using NI Software with Microsoft Windows 8.1
Legal Information
Documentation
Supported PlatformsSupported Operating Systems
Windows 10 (32-bit and 64-bit)
Windows 8 (32-bit and 64-bit)
Windows 7 (32-bit and 64-bit)
Supported Hardware
PCI-CAN, PCI-CAN/2 (High-Speed; Series 1 and 2)
PCI-CAN/LS, PCI-CAN/LS2 (Low-Speed/Fault-Tolerant; Series 1 and 2)
PCI-CAN/DS, (Dual Speed: Port-1 High-Speed, Port-2 Low-Speed; Series 1)
PCI-CAN/XS, PCI-CAN/XS2, (Software-Selectable HS/LS/SW; Series 2)
PXI-8460, one-port or two-port (Low-Speed/Fault-Tolerant; Series 1 and 2)
PXI-8461, one-port or two-port (High-Speed; Series 1 and 2)
PXI-8462, (Dual Speed: Port-1 High-Speed, Port-2 Low-Speed; Series 1)
PXI-8464, one-port or two-port (Software-Selectable HS/LS/SW; Series 2)
USB-8472 (Low-Speed/Fault-Tolerant CAN)
USB-8472s (Low-Speed/Fault-Tolerant CAN with synchronization)
USB-8473 (High-Speed CAN)
USB-8473s (High-Speed CAN with synchronization)
USB-8476 (LIN)
USB-8476s (LIN with synchronization)
PCMCIA-CAN, PCMCIA-CAN/2 (Series 1 and 2)
PCI-CAN, (pre-1998 CAN card, part numbers 183887A-01 and 183887B-01)
PCI-CAN/2, (pre-1998 CAN card, part numbers 183887A-02 and 183887B-02)
PCMCIA-CAN, (pre-1998 CAN card, part numbers 184272A-01, 184272B-01, and 184272C-01)
PCMCIA-CAN/2, (pre-1998 CAN card, part numbers 184272A-02, 184272B-02, and 184272C-02)
AT-CAN
AT-CAN/2 (ISAPNP cards; High Speed; Series 1)
Supported Development Environments
LabVIEW 2014 (32-bit), LabVIEW 2015 (32-bit), and LabVIEW 2016 (32-bit), LabVIEW 2017 (32-bit)
LabVIEW Real-Time (ETS) 2014, 2015, 2016, and 2017
LabWindows/CVI 8.0 (or newer)
Microsoft Visual Basic 6.0
Microsoft Visual C/C++ 6.0
Borland C/C++
Installing NI-CAN
Insert the NI-CAN 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 NI-CAN software CD.
The installation wizard guides you through the necessary steps to install the NI-CAN 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.
NI-CAN Updates and Notifications
Product Security and Critical Updates
New Features and Changes as Compared to NI-CAN 16.0
Added support for LabVIEW 2017 (32-bit).
Removed support for LabVIEW 2013.
New Features and Changes as Compared to NI-CAN 15.0
Added support for LabVIEW 2016 (32-bit).
Removed support for LabVIEW 2012.
New Features and Changes as Compared to NI-CAN 14.0
Added support for LabVIEW 2015 (32-bit).
Removed support for LabVIEW 2011.
New Features and Changes as Compared to NI-CAN 2.7.5
Added support for LabVIEW 2014 (32-bit).
Removed support for LabVIEW 2010.
New Features and Changes as Compared to NI-CAN 2.7.4
Added support for LabVIEW 2013 (32-bit).
Removed support for LabVIEW 2009.
Added support for NI 9861 and 9862 devices on cDAQ through NI-XNET (LabVIEW 2010 or newer)
New Features and Changes as Compared to NI-CAN 2.7.3
Added support for LabVIEW 2012 (32-bit).
Removed support for LabVIEW 8.6.
Removed support for Windows XP prior to Service Pack 3.
New Features and Changes as Compared to NI-CAN 2.7.2
Added support for LabVIEW 2011 (32-bit).
Removed support for LabVIEW 8.5.
New Features and Changes as Compared to NI-CAN 2.7
Added support for LabVIEW 2010 (32-bit).
Removed support for LabVIEW 8.2.
New Features and Changes as Compared to NI-CAN 2.6.x
Added support for PCI-8511, 8512, and 8513 devices through NI-XNET (LabVIEW 8.5 or newer)
Added support for PXI-8511, 8512, and 8513 devices through NI-XNET (LabVIEW 8.5 or newer)
New Features and Changes as Compared to NI-CAN 2.5.x
Added support for LabVIEW 2009.
Removed support for LabVIEW 7.1.
Added support for LabVIEW 8.6.
Removed support for LabVIEW 8.0.x.
Location of the C language interface and example files changed:
The language interface and example files for Microsoft Visual C/C++ 6.0 and Borland C have moved from the Program FilesNational InstrumentsNI-CANMS Visual C directory to the UsersPublicDocumentsNational InstrumentsNI-CANMS Visual C directory on Windows Vista and the Documents and SettingsAll UsersShared DocumentsNational InstrumentsNI-CANExamplesMS Visual C directory on Windows XP/2000. This change satisfies Windows Vista requirements when allowing users to save changes or add files to the directory.
The NIEXTCCOMPILERSUPP environment variable is provided as an alias to the location of C language support files (.h and .lib). You can use this variable when compiling and linking an application.
Added support for LabVIEW 8.5.
Known Issues
Issue Number | Issue |
414367 | When viewing NI-XNET cards on the monitor when using a Real-Time target, some cards may display as "Unknown Device." You can view the cards correctly through the NI-CAN RT Configuration Utility in MAX. |
Bug Fixes
Bug ID | Fixed Issue |
361899 | Memory corruption possible when reading data in LabVIEW. |
Bug ID | Fixed Issue |
251950 | System hangs with ncAction Start when Log Start Trigger attribute is enabled. |
282965 | USB CAN modules disappear from MAX when multiple processes are executed at the same time. |
Bug ID | Fixed Issue |
145168 | MUX in Motorola byte order does not work properly when sending less than a full 8-byte frame. |
242580 | Scheduler assertion error on NI PXI-8109 real-time controller when using ports on two different devices. |
Bug ID | Fixed Issue |
142729 | NI USB-8473s synchronization fails with traffic on the bus. |
226671 | Error R6030 when compiling NI-CAN application in Visual Studio 2008. |
233936 | The nctInitStart function fails with NI-XNET compatibility error. |
Bug ID | Fixed Issue |
139394 | Terminating an NI-CAN process on one CAN port might affect other CAN ports or cards. |
Bug ID | Fixed Issue |
122723 | Blue screen when removing an NI USB-847x or PCMCIA CAN interface while running an NI-CAN application on it. |
120242 | Warning states should not trigger a notification callback. |
Bug ID | Fixed Issue |
103680 | Timeline Recovery attribute for ncWriteNetMult VI/function does not work. |
55364 | Importing a CAN database in MAX incorrectly changes datatype for extended arbitration IDs. |
93911 | Calling ncClose frequently may result in a firmware no response error. |
95354 | Notification functions/ncWait for Read operations do not work on NI-847x interfaces. |
42012 | Using the timestamped input read mode with 64 tasks causes a kernel overflow error. |
40750 | You cannot set the Single Shot property when the Network Interface Object is running. |
94653 | The ncOpen function/VI could fail to start communication fast computers. |
Bug ID | Fixed Issue |
4DAGR870 | NI-CAN 2.5.1 does not install VIs to support synchronization between Traditional NI-DAQ and CAN for LabVIEW 8.5. |
Bug ID | Fixed Issue |
47P90370 | Fixed an issue where the LIN firmware was incorrectly calculating the enhanced checksum using the unprotected ID. |
47ICPNSP | Fixed an issue where CAN objects would not restart correctly when the Network Interface is restarted. |
48H8PQ70 | Fixed an issue where the computer would crash when the function SetProcessWorkingSetSize() is used to increase buffer memory. |
Additional Programming TopicsNI-DAQ Synchronization VIs
CAN Clear with NI-DAQ.vi
CAN Clear Multiple with NI-DAQ.vi
CAN Sync Start with NI-DAQ.vi
CAN Sync Start Multiple with NI-DAQ.vi
Support of CANdb (*.DBC) Files
Updating Get/Set Attribute in Frame API for LabVIEW
Release Notes
The NI-XNET Compatibility Layer for NI-CAN currently supports NI-XNET CAN only PCI and CAN only PXI, CAN only C-Series and CAN/LIN USB-850x hardware.
The NI-XNET Compatibility Layer for NI-CAN currently does not support the LabVIEW example Channel Monitor.vi.
For USB-LIN interfaces, the LIN bus must be terminated. This is typically done at the master node. For information about how to enable or disable termination on the USB-LIN, refer to the ncSetAttribute attribute function with the Frame API.
The USB-LIN interfaces require external power from 8–18 V. For more details on the power requirements, refer to the USB-LIN specifications sections in the NI-CAN Hardware and Software Manual.
The USB LED quickly switches between green and amber when the hardware is first detected.
Fatal errors may cause the USB LED to flash in an error code pattern. Count the number of long and short flashes, then contact National Instruments support.
If using the USB CAN or LIN products with a USB hub, the hub must be powered.
Due to the inherent latencies of the Universal Serial Bus (USB), the driver on the host side might process data or states that the NI USB-847x series devices receive later than data from a plug-in (PCI, PXI, or PCMCIA) interface. This does not affect the timestamps, as those are generated on the hardware, but could cause timeout failures with the NI USB-847x series devices that will not happen on plug-in hardware. To avoid these timeout failures, increase the timeout value for functions that perform a wait for a certain state.
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
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.