NI-XNET 1.4 Driver Win32Eng NI-XNET仪器驱动程序1.4下载
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 1.4 Driver Win32Eng NI-XNET仪器驱动程序1.4下载
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帧和信号进行高速实时操作的应用，如硬件在环仿真、快速控制原型、总线监控和自动化控制等。
1.4
文件大小: 419449138 字节 (400.02 MB)
修改日期: 2019-06-25 02:42
MD5: 4f6e6ab769c2149ddf7ff343d0582b14（官方正确）
SHA1: 78d63d895757be3e637af11182c56ff5cc15feec
SHA256: 161e7c2c26bd034ffd7331e3636245592b9343f86a2a3f9937f306262b552d71
CRC32: 17ecb746
NI-XNET 1.4 ReadmeAugust 2011ni.com/xnetThis file contains information about the NI-XNET software for Windows 7/Vista/XP and LabVIEW™ Real-Time (RT). Information in this file is organized in the following sections:
[*]Documentation
[*]Supported Platforms
[*]Installing NI-XNET 1.4
[*]New Features and Changes
[*]Bug Fixes
[*]Errata to the NI-XNET Hardware and Software Manual
[*]Additional Programming Topics
DocumentationThe XNET Software and Hardware Installation Guide included with the NI-XNET CD includes instructions for installing National Instruments hardware and software.The NI-XNET Hardware and Software Manual is the primary document for NI XNET products. This manual includes an introduction to CAN, FlexRay, and LIN, specifications for hardware, information about how to get started with application development, and a complete reference for all NI-XNET functions.The NI-XNET Hardware and Software Manual is in Adobe Acrobat Portable Document Format (PDF). You can download the Acrobat Reader for free at: www.adobe.com.Open the help from Start»All Programs»National Instruments»NI-XNET.Links to the NI-XNET Hardware and Software Manual are in the online help for each NI-XNET function within the National Instruments LabVIEW and LabWindows™/CVI™ development environments.Online help for the NI-XNET features within Measurement & Automation Explorer (MAX) is in the MAX Help Topics menu. The MAX Help Topics menu for NI-XNET also includes a link to the NI-XNET Hardware and Software Help.Back to TopInstalling NI-XNET 1.4Before 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 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-XNET software CD.
[*]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.
Installing NI-XNET SilentlyYou can programmatically control which features in the NI-XNET distribution to enable or disable for installation. You therefore can install a subset of the NI-XNET distribution silently. Refer to the template_spec.txt file in the Specfiles directory on the NI-XNET CD for more information about installing NI-XNET silently and selecting which features to install automatically.Back to TopSupported PlatformsSupported Operating SystemsYou can install and run this version of the NI-XNET software on the following operating systems:
[*]Windows 7 (32-bit and 64-bit)
[*]Windows Vista (32-bit and 64-bit)
[*]Windows XP (32-bit) SP2 or later
[*]Windows Server 2003 R2 (32-bit)
[*]Windows Server 2008 R2 (64-bit)
The NI-XNET installer does not support Windows NT/Me/2000/98/95 or the Windows Server non-R2 editions.Note:Support for Windows Server 2003 R2 may require disabling physical address extensions (PAE). To learn how this may affect your use of Windows Server 2003 and what actions you may need to take, visit ni.com/info and enter the info code PAESupport.
CautionIf you plan to perform an upgrade of your system from a prior version of Microsoft Windows to Microsoft Windows Vista, you are required to uninstall all National Instruments software prior to performing the upgrade. After the upgrade has been completed, you can reinstall your National Instruments software.
Supported HardwareThis version of the NI-XNET software supports the following National Instruments hardware products on Windows and LabVIEW RT:
[*]NI PCI-8511 (Low-Speed/Fault-Tolerant CAN)
[*]NI PCI-8512 (High-Speed CAN)
[*]NI PCI-8513 (Software-Selectable HS/LS/SW CAN)
[*]NI PCI-8516 (LIN)
[*]NI PCI-8517 (FlexRay)
[*]NI PXI-8511 (Low-Speed/Fault-Tolerant CAN)
[*]NI PXI-8512 (High-Speed CAN)
[*]NI PXI-8513 (Software-Selectable HS/LS/SW CAN)
[*]NI PXI-8516 (LIN)
[*]NI PXI-8517 (FlexRay)
[*]C Series modules:
[*]NI 9861 (C Series Low-Speed CAN)
[*]NI 9862 (C Series High-Speed CAN)
[*]NI 9866 (C Series LIN)
Supported platforms for XNET C Series modules:
[*]CompactDAQ - NI-DAQmx 9.3 (or newer) required.
[*]NI cDAQ-9171
[*]NI cDAQ-9174
[*]NI cDAQ-9178
[*]NI cDAQ-9181
[*]NI cDAQ-9188
[*]NI cDAQ-9191
[*]CompactRIO - NI-RIO 3.6.1 (or newer) and LabVIEW 2010 SP1 (or newer) required for the following targets:
[*]Real-Time Controller: NI cRIO-9012, NI cRIO-9014, NI cRIO-9022, and NI cRIO-9024
[*]CompactRIO Reconfigurable Chassis: NI cRIO-9111, NI cRIO-9112, NI cRIO-9113, NI cRIO-9114, NI cRIO-9116, and NI cRIO-9118
[*]LabVIEW FPGA 2010 SP1 (or newer) is required to build and deploy a bitstream with NI 986x modules in the project.
[*]CompactRIO - NI-RIO 4.0 (or newer) and LabVIEW 2011 (or newer) required for the following targets:
[*]Integrated CompactRIO Real-Time Controller: NI cRIO-9081, NI cRIO-9082
[*]LabVIEW FPGA 2011 (or newer) is required to build and deploy a bitstream with NI 986x modules in the project.
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.Supported Development EnvironmentsThis version of the NI-XNET software supports the following development environments:
[*]LabVIEW 8.6, LabVIEW 2009 (32-bit), LabVIEW 2010 (32-bit), and LabVIEW 2011 (32-bit)
[*]LabVIEW Real-Time (RT) 8.6, 2009, 2010, and 2011
[*]LabWindows/CVI 8.5 and higher
[*]Microsoft Visual C/C++ 6.0
Back to TopNew NI-XNET 1.4 Features and Changes as Compared to NI-XNET 1.3.1The NI-XNET 1.4 release adds the following features:
[*]New feature: Added support for new XNET C Series modules: NI 9861 and NI 9866.
[*]New feature: Added TDMS log file format to logging examples.
[*]New feature: Support for the NI cDAQ-9171, NI cDAQ-9181, and NI cDAQ-9191 chassis.
[*]New feature: CAN and LIN sessions can now be created while the corresponding interface is already communicating.
[*]New feature: Up to 192 frames can now be used with XNET CAN interfaces, up from 128.
[*]New feature: Added support for Series 1/Series 2 CAN filters to the NI-CAN Compatibility Library for NI-XNET.
[*]New feature: Added support for the Timestamped Transmit mode to the NI-CAN Compatibility Library for NI-XNET.
The NI-XNET 1.4 release changes the following:
[*]General performance improvements when using XNET C Series modules with CompactDAQ.
[*]The C API property nxPropSession_IntfRef has been removed from the nixnet.h header file. This property was not documented in C API help, and was not listed in LabVIEW property nodes.
New NI-XNET 1.3.1 Features and Changes as Compared to NI-XNET 1.3The NI-XNET 1.3.1 release adds the following feature:
[*]New feature: Support for LabVIEW 2011 (32-bit).
The NI-XNET 1.3.1 release changes the following:
[*]Deprecated feature: Support for LabVIEW 8.5 and 8.5.1.
New NI-XNET 1.3 Features and Changes as Compared to NI-XNET 1.1.1The NI-XNET 1.3 release adds the following features:
[*]New feature: Support of the NI 9862 C Series module.
[*]New feature: FIBEX 3.0 database file support.
[*]New feature: PDU support (FlexRay only).
[*]New feature: Frame/Signal conversion (refer to XNET Convert.vi or the nxConvertFramesToSignalsSinglePoint() and nxConvertSignalsToFramesSinglePoint() functions)
[*]New feature: External transceiver support for CAN XS hardware (NI PCI-8513 and PXI-8513).
[*]New feature: NI-Spy supports logging calls from NI-XNET LabVIEW VIs.
[*]New feature: Reading custom attributes from .dbc files (refer to XNET Database Get DBC Attribute.vi or the nxConvertFramesToSignalsSinglePoint and nxConvertSignalsToFramesSinglePoint functions).
[*]New feature: Allowing multiselect, drag-and-drop in the Tx/Rx frame dialog list boxes of the NI-XNET Database Editor.
[*]New feature: Allowing multiple databases to be used on a single interface (using individual sessions).
The NI-XNET 1.3 release changes the following behavior:
[*]Change: Database export file format changed from FIBEX 2.0.1 to 3.1.
New NI-XNET 1.1.1 Features and Changes as Compared to NI-XNET 1.1The NI-XNET 1.1.1 release adds the following features:
[*]New feature: Support for LabVIEW 2010 (32-bit).
New NI-XNET 1.1 Features and Changes as Compared to NI-XNET 1.0The NI-XNET 1.1 release adds the following features:
[*]New feature: Support for PCI-8516 and PXI-8516 (LIN bus interface).
[*]New feature: Replay mode (CAN only. Refer to the Interface:Output Stream Timing, Interface:Output Stream List, and Interface:CAN:Output Stream List By ID properties.)
[*]New feature: Cyclic frame spacing (CAN only. Refer to the Frame:CAN:Start Time Offset property.)
[*]New feature: Frame level fault insertion (CAN only: Change the period during runtime. Refer to the Frame:CAN:Transmit Time property. CAN only: Skip N transmissions of a cyclic frame. Refer to the Frame:Skip N Cyclic Frames property.)
[*]New feature: Frame reordering (CAN only. Refer to the Interface:CAN:Pending Transmit Order property.)
[*]New feature: LabVIEW Real-Time support on desktop PC real-time systems.
The NI-XNET 1.1 release changes the following behavior:
[*]In the NI-XNET 1.0, you could connect one NI-XNET class to a different NI-XNET class (for example, you could wire an NI-XNET frame to a property node of an NI-XNET signal). This class mismatch in NI-XNET 1.0 usually was detected at runtime only. In LabVIEW 2009, NI-XNET 1.1 shows this as a broken wire at edit time.
Back to TopBug FixesThe following items are the IDs and titles of a subset of issues fixed between NI-XNET 1.3.1 and NI-XNET 1.4. If you have a CAR ID, you can search this list to validate that the issue has been fixed. This is not an exhaustive list of issues fixed in the current version of NI-XNET.
Bug IDFixed Issue
308704LabVIEW could crash with a "Pure virtual function call invoked" error when using Timebase signal on CompactDAQ.
305079The Synchronize TimedLoop to FlexRay Macro Tick LabVIEW example could cause LabVIEW Real-Time to crash under certain timing conditions.
299236The NI-XNET BusMonitor reported an internal error when attempting to transmit a frame without reading from the network yet.
308335, 310235Improved behaviour of scaling for LIN signals.
307968The C API nxReadSignalWaveform() function returned an incorrect value for the NumberOfValuesReturned parameter when no data was available.
307799Improved behaviour of scaling with invalid number of coefficients for FIBEX files.
305512The NI-XNET Database Editor does not show all PDUs correctly when reimporting larger FIBEX files.
The following items are the IDs and titles of a subset of issues fixed between NI-XNET 1.3 and NI-XNET 1.3.1. If you have a CAR ID, you can search this list to validate that the issue has been fixed. This is not an exhaustive list of issues fixed in the current version of NI-XNET.
Bug IDFixed Issue
299336The FlexRay Frame Output Queued and the Convert FlexRay Frames to-from Signals examples returned error 0xBFF6309F (-1074384737).
The following items are the IDs and titles of a subset of issues fixed between NI-XNET 1.1 and NI-XNET 1.3. If you have a CAR ID, you can search this list to validate that the issue has been fixed. This is not an exhaustive list of issues fixed in the current version of NI-XNET.
Bug IDFixed Issue
287495NI-XNET database editor: When trying to enter a value for default value with more then 7 digits, the editor coerces the value and creates the coerced value in the FIBEX file.
281193Cannot integrate if using FlexRay In Cycle Repeated Frames with 254 bytes.
280120CAN remote frames are not transmitted when using single-point sessions.
256773The cycle value returned from XNET Read (State FlexRay Cycle Macrotick).vi is not accurate.
255818NI-XNET database editor: Deleting an ECU from an imported FIXED database does not delete the ECU from the FIBEX file.
254192Selecting NI-XNET signals through constant or strings throws an error at session creation time.
250196LabVIEW Project Assistant: Importing XNET Sessions does not import the session, if identical message- and channel-names exist.
240132A LIN Slave Stream Input session requires defining a schedule, although it should not need to.
237697NI-XNET database editor: FlexRay signals are not shown from imported FIBEX files.
234865NI-XNET Compatibility Library for NI-CAN: .ncd or .dbc files cannot be used by NI-XNET Compatibility Library for NI-CAN on LabVIEW Real-Time targets.
228013You can experience high processor load when using a waveform input session with many signals.
224423NI-XNET does not read default and error values correctly from .dbc files.
222491NI-XNET does not read the signal name for a multiplexer correctly from .dbc files.
214704Collision Resolving Schedules were not always executed as highest priority schedule.
211958Error –1074384742/0xBFF6309A is generated when trying to use different clusters on the same interface.
211634LabVIEW Project Assistant: Under certain circumstances, you cannot select LIN interfaces on the Hardware Selection page.
206976Querying the cluster for a receive frame returns an error if there is an ECU and a frame using the same name.
200103NI-XNET Compatibility Library for NI-CAN: You cannot change the frame timing type of CAN frames once the database is in use.
The following items are the IDs and titles of a subset of issues fixed between NI-XNET 1.0 and NI-XNET 1.1. If you have a CAR ID, you can search this list to validate that the issue has been fixed. This is not an exhaustive list of issues fixed in the current version of NI-XNET.
Bug IDFixed Issue
195809NI-XNET Compatibility Library for NI-CAN: ncConfig/ncOpenObject/ncCloseObject functions leak memory and handles.
194073NI-XNET Compatibility Library for NI-CAN: Notifications cannot be rearmed without disabling them first.
192007Read timestamp function may return a timestamp that is off by about 7 minutes.
181246NI-XNET Compatibility Library for NI-CAN: The nctInitialize function and the CAN Init VI do not use the baud rate of a currently running interface.
180542NI-XNET Compatibility Library for NI-CAN: ncConfig called with same parameters on open of CAN objects returns an error.
193647NI-XNET Compatibility Library for NI-CAN: Added code to avoid hanging ncCreateNotification() when attempting to disarm a pending notification.
206461NI-XNET Compatibility Library for NI-CAN: Added code to avoid hanging ncCreateNotification() when attempting to close an object with a pending notification.
186551Losing arbitration while in Single Shot Transmit mode may cause a session to stop sending frames.
Back to TopAdditional Programming TopicsSynchronization in CompactDAQExplicit routing of the timebase is not required for CompactDAQ, because all modules in the chassis automatically use a shared timebase.The C Series CAN module supports routing of the Start Trigger to/from other modules in the CompactDAQ chassis, including CAN and DAQ modules. This feature is currently documented in context help, but not the full NI-XNET manual.For information about CompactDAQ synchronization in LabVIEW, drop the XNET Session property node to the diagram, select property Interface : Source Terminal : Trigger, and view the context help.For information about CompactDAQ synchronization in C/C++, open nixnet.h, and search for the session property nxPropSession_IntfSrcTermStartTrigger. Context help is provided in the comment.NI-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 targetsInserting an module into a cRIO chassis that is actively communicating with an NI 9862 module causes the module to lose communication. Solution: Do not insert any modules into a cRIO chassis during active communication.Back to TopErrata to the NI-XNET Hardware and Software ManualSynchronization in CompactDAQUpdate to the LabVIEW Interface : Source Terminal : Trigger and nxPropSession_IntfSrcTermStartTrigger session property documentation:
For trigger connections between XNET C Series modules and DAQ C Series modules, the property is write only. The 986x C Series module can receive a start trigger signal from a DAQ C Series module, but not generate a start trigger for a DAQ C Series module.Start trigger routing in CompactDAQUpdate to the LabVIEW Interface : Source Terminal : Start Trigger session property documentation:
To read the DAQmx Start Trigger property, use the Start:Terminal DAQmx Trigger Node property instead of the Start:Digital Edge:Source DAQmx Trigger Node property.
For example, to connect the Start Trigger of an analog input module for use as a CAN interface Start Trigger, read the DAQmx Trigger Node property Start:Terminal, and write the resulting value to this CAN interface property.Update to the C Interface : Source Terminal : Start Trigger session property (nxPropSession_IntfSrcTermStartTrigger) documentation:
To read the DAQmx Start Trigger property, use the DAQmxGetStartTrigTerm function instead of the DAQmxGetDigEdgeStartTrigSrc function.
For example, to connect the Start Trigger of an analog input module for use as a CAN interface Start Trigger, read the DAQmx Start Trigger property using DAQmxGetStartTrigTerm, and write the resulting value to this CAN interface property.Back to TopNoticeA FOSS notice is installed with NI-XNET. By default, the notice is installed at Program Files\National Instruments\NI-XNET\Licenses\NI-XNET FOSS notices.pdf.CopyrightCopyright 2009–2011 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.National Instruments 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.TrademarksCVI, LabVIEW, National Instruments, NI, ni.com, the National Instruments corporate logo, and the Eagle logo are trademarks of National Instruments Corporation. Refer to the Trademark Information at ni.com/trademarks for other National Instruments trademarks.The mark LabWindows is used under a license from Microsoft Corporation. Windows is a registered trademark of Microsoft Corporation in the United States and other countries.Other product and company names mentioned herein are trademarks or trade names of their respective companies.Patents
For patents covering the National Instruments products/technology, refer to the appropriate location: Help» Patents in your software, the patents.txt file on your media, or the National Instruments Patent Notice at ni.com/patents.
页:
[1]