NI-XNET 1.5 Driver Win32 Eng/Ger/Jpn NI-XNET仪器驱动程序1.5下载

石鑫华视觉

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.5 Driver Win32 Eng/Ger/Jpn NI-XNET仪器驱动程序1.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帧和信号进行高速实时操作的应用，如硬件在环仿真、快速控制原型、总线监控和自动化控制等。

1.5
文件大小: 472832180 字节 (450.93 MB)
修改日期: 2019-06-25 02:42
MD5: 2c3ae1b726b8ccf5e0795b7f3fc976a2（官方正确）
SHA1: 8655eb1e02cd686a48a15976b3d5564600ed69ab
SHA256: 8703cc649ac8528a2a507146402165e726bb5f964fda2529359dbb609e0717c2
CRC32: 0c968143

NI-XNET1.5.txt (278 Bytes, 下载次数: 0, 售价: 10 元)

2020-10-20 22:36 上传

点击文件名下载附件

NI-XNET 1.5 Readme

March 2012

ni.com/xnet

This 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.5
• New Features and Changes
• Known Issues
• Bug Fixes
• Additional Programming Topics
  

---

Documentation

The 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 Top

---

Installing NI-XNET 1.5

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 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 Silently

You 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 Top

---

Supported PlatformsSupported Operating Systems

You 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.

Caution  If 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 Hardware

This 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-9174
      • NI cDAQ-9178
      • NI cDAQ-9181
      • NI cDAQ-9188
        
    • CompactDAQ - NI-DAQmx 9.4 (or newer) required:
      
      • NI cDAQ-9171
      • NI cDAQ-9191
        
    • CompactRIO - NI-RIO 4.0 (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 Environments

This 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 Top

---

New NI-XNET 1.5 Features and Changes as Compared to NI-XNET 1.4

The NI-XNET 1.5 release adds the following features:

• New feature: Added support for the FlexRay Wakeup procedure.
• New feature: Added support for the FlexRay Symbol Window.
• New feature: Added support for LIN clusters in the FIBEX database (import and export).
• New feature: Added support for LIN clusters in the NI-XNET Database Editor.
• New feature: NI-XNET start/stop supports blocking behavior for session-only mode.
• New feature: Added support for retrieving the started/stopped state of the session. Refer to XNET Read (State Session Info).vi or nxReadState»nxState_SessionInfo.
• New feature: The NI-XNET Bus Monitor now can display the signal values of incoming frames.
• New feature: Added support for 16-bit multiplexers.
• New feature: Added support for importing FIBEX 4.0 database files.
  

The NI-XNET 1.5 release changes the following:

• NI-XNET Compatibility Library for NI-CAN: NI-CAN hardware in MAX now shows up under the new NI-CAN Devices category.
• CAN Frame sessions allow transmitting a frame where the frame's payload length is less than the payload length configured in the database.
  

New NI-XNET 1.4 Features and Changes as Compared to NI-XNET 1.3.1

The 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.3

The 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.1

The 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.1

The 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.0

The 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 Top

---

Known issues

The following items are the IDs and titles of a subset of issues known to be present in NI-XNET 1.5. If you have a CAR ID, you can search this list to validate issues known not to have been addressed for this release. This is not an exhaustive list of known issues in the current version of NI-XNET.

Issue Number	Issue
331644	On Compact DAQ systems, the cyclic output rate is not synchronized with the timestamp counter. This can cause output cyclic messages to transmit at a rate that may drift from the input timestamp rate.
340351	Using signals in the NI-XNET Bus Monitor prevents the subordinate mode. Furthermore, you cannot use those signals in your applications that the Bus Monitor is already using.
341928	One cannot import diagnostic frames from LDF files (MasterReq/SlaveResp). That includes schedule tables that contain diagnostic frames.

Back to Top

---

Bug Fixes

The following items are the IDs and titles of a subset of issues fixed between NI-XNET 1.4 and NI-XNET 1.5. 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 ID	Fixed Issue
312408	Using the same trigger signal multiple times within a single session did not work as described.
339763	Display of FlexRay frames from log files does not work properly.
333628	Revisions C and D of the NI PCI-8513 could enter the bus off state after a cold reboot of the host computer.
328817	Crash on certain PCI Express systems.
319291	Crash in the NI-XNET Database Editor when trying to convert an NCD file into FIBEX.
343178	Crash while using FIBEX database.
332120	Unable to import SAE-J2602 databases.
319616	NI-XNET Compatibility Library for NI-CAN: Error –52000 reported when using frame and channel API on LabVIEW Real-Time targets.
318120	LabVIEW Get DBC Attribute.vi did not use correct enumeration for mode.
316735	Timeout error reported when using a baud rate of 2.5 Mbps on FlexRay.
315556	A negative "number to read" value does not cause the waveform session to return the maximum number of samples.
315555	Running the NI-XNET Bus Monitor in subordinate mode prevents other sessions from being run.

The 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 ID	Fixed Issue
308704	LabVIEW could crash with a "Pure virtual function call invoked" error when using Timebase signal on CompactDAQ.
305079	The Synchronize TimedLoop to FlexRay Macro Tick LabVIEW example could cause LabVIEW Real-Time to crash under certain timing conditions.
299236	The NI-XNET Bus Monitor reported an internal error when attempting to transmit a frame without reading from the network yet.
308335, 310235	Improved behaviour of scaling for LIN signals.
307968	The C API nxReadSignalWaveform() function returned an incorrect value for the NumberOfValuesReturned parameter when no data was available.
307799	Improved behaviour of scaling with invalid number of coefficients for FIBEX files.
305512	The 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 ID	Fixed Issue
299336	The 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 ID	Fixed Issue
287495	NI-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.
281193	Cannot integrate if using FlexRay In Cycle Repeated Frames with 254 bytes.
280120	CAN remote frames are not transmitted when using single-point sessions.
256773	The cycle value returned from XNET Read (State FlexRay Cycle Macrotick).vi is not accurate.
255818	NI-XNET database editor: Deleting an ECU from an imported FIXED database does not delete the ECU from the FIBEX file.
254192	Selecting NI-XNET signals through constant or strings throws an error at session creation time.
250196	LabVIEW Project Assistant: Importing XNET Sessions does not import the session, if identical message- and channel-names exist.
240132	A LIN Slave Stream Input session requires defining a schedule, although it should not need to.
237697	NI-XNET database editor: FlexRay signals are not shown from imported FIBEX files.
234865	NI-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.
228013	You can experience high processor load when using a waveform input session with many signals.
224423	NI-XNET does not read default and error values correctly from .dbc files.
222491	NI-XNET does not read the signal name for a multiplexer correctly from .dbc files.
214704	Collision Resolving Schedules were not always executed as highest priority schedule.
211958	Error –1074384742/0xBFF6309A is generated when trying to use different clusters on the same interface.
211634	LabVIEW Project Assistant: Under certain circumstances, you cannot select LIN interfaces on the Hardware Selection page.
206976	Querying the cluster for a receive frame returns an error if there is an ECU and a frame using the same name.
200103	NI-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 ID	Fixed Issue
195809	NI-XNET Compatibility Library for NI-CAN: ncConfig/ncOpenObject/ncCloseObject functions leak memory and handles.
194073	NI-XNET Compatibility Library for NI-CAN: Notifications cannot be rearmed without disabling them first.
192007	Read timestamp function may return a timestamp that is off by about 7 minutes.
181246	NI-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.
180542	NI-XNET Compatibility Library for NI-CAN: ncConfig called with same parameters on open of CAN objects returns an error.
193647	NI-XNET Compatibility Library for NI-CAN: Added code to avoid hanging ncCreateNotification() when attempting to disarm a pending notification.
206461	NI-XNET Compatibility Library for NI-CAN: Added code to avoid hanging ncCreateNotification() when attempting to close an object with a pending notification.
186551	Losing arbitration while in Single Shot Transmit mode may cause a session to stop sending frames.

Back to Top

---

Additional Programming TopicsNI-CAN Compatibility

If 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 targets

When 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

Inserting 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.

Closing the XNET System in LabVIEW 8.6

In LabVIEW 2009 and higher, the XNET System is opened automatically when you use it to obtain device and interface properties, and closed automatically when your VI goes idle (stops running). In LabVIEW 8.6, the XNET System does not always close when your VI goes idle, so you must call XNET System Close in your diagram.

Back to Top

---

Notice

A 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.

Copyright

Copyright 2009–2012 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.

Trademarks

CVI, 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.