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

石鑫华视觉

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.8 Driver Win32 Eng/Ger/Jpn NI-XNET仪器驱动程序1.8下载

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.8
文件大小: 636419859 字节 (606.94 MB)
修改日期: 2019-06-25 02:42
MD5: e6e418c68bd7eb88f5aade9d0fccfc2e（官方正确）
SHA1: 37f4ffc20d43d2512179b7ac498949329ebdc1dc
SHA256: ae83ff250d1659488e95fd582069127bc6d68e209923c69d02ac6906f2a169e1
CRC32: 086483bb

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

2020-10-20 22:43 上传

点击文件名下载附件

NI-XNET 1.8 Readme

August 2013

ni.com/xnet

This file contains information about the NI-XNET software for Windows 8/7/Vista/XP and LabVIEW™ Real-Time (RT). Information in this file is organized in the following sections:

• Documentation
• Installing NI-XNET 1.8
• Supported Platforms
• How to Use NI Software with Microsoft Windows 8
• NI-XNET Drops Support for Microsoft Windows Vista, Windows XP, and Windows Server 2003 in 2016
• New Features and Changes
• Known Issues
• Bug Fixes
• Additional Programming Topics
• Errata to the NI-XNET Hardware and Software Manual
• Important Information
  

---

Documentation

The XNET Software and Hardware Installation Guide included with the NI-XNET installation media 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 document 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.8

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.
  

NI-XNET Updates and Notifications

National Instruments posts information about critical updates and security notifications on ni.com. Visit ni.com/info and enter Info Code updates to access this information.

Automating the Installation of NI Products

You can automate the installation of most NI products using command-line arguments to suppress some or all of the installer user interface and dialog boxes. However, starting with the August 2012 releases (products using NI Installers version 3.1 or later), you may need to perform additional steps before or during a silent installation of NI software.

If the NI product you are installing uses Microsoft .NET 4.0, the .NET installer may run before any NI software installs and may require a reboot before the installation of NI software begins. To avoid a .NET reboot, install .NET 4.0 separately before you install NI software.

For more information, refer to the following KnowledgeBase articles:

• For more information on silent installations of individual NI products, refer to KB 4CJDP38M, Automating the Installation of a Single Installer.
• For more information on silent installations of suited NI products, such as NI Developer Suite, refer to KB 4GGGDQH0, Automating 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 National Instruments Installer?.
  

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 8 (32-bit and 64-bit)
• Windows 7 (32-bit and 64-bit)
• Windows Vista Business edition, Service Pack (SP) 1 or greater (32-bit and 64-bit)
• Windows XP (32-bit) SP3 or later
• Windows Server 2003 R2, SP2 or greater (32-bit)
• Windows Server 2008 R2, SP1 or greater (64-bit, not supported on Server Core Role)
  

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.

NI-XNET does not support guest accounts on Windows 7/Vista/XP. You must log into an administrative or user account to use NI-XNET on these OSes.

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.

Back to Top

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.6 (or newer) is required for:
      
      • USB Chassis: NI cDAQ-9171, NI cDAQ-9174, and NI cDAQ-9178
      • Ethernet Chassis: NI cDAQ-9181, NI cDAQ-9184, and NI cDAQ-9188
      • Wireless Chassis: NI cDAQ-9191
      • Stand-Alone Chassis: NI cDAQ-9138 (Windows & RT) and NI cDAQ-9139 (Windows & RT)
        
    • CompactRIO - NI-RIO 13.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, NI cRIO-9023, NI cRIO-9024 and NI cRIO-9025
      • 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 13.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.
        
    • CompactRIO - NI-RIO 13.0 (or newer) and LabVIEW 2013 (or newer) required for the following targets:
      
      • Integrated CompactRIO Real-Time Controller: NI cRIO-9068
      • LabVIEW FPGA 2013 (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 2010 (32-bit), LabVIEW 2011 (32-bit), LabVIEW 2012 (32-bit), and LabVIEW 2013 (32-bit)
• LabVIEW Real-Time (RT) 2010, 2011, 2012, and 2013
• LabWindows/CVI 8.5 and higher
• Microsoft Visual C/C++ 6.0
  

Back to Top

---

How to Use NI Software with Microsoft Windows 8

When you install National Instruments software on Microsoft Windows 8, you will notice a few additional tiles on the Start screen, including shortcuts to NI application software products such as NI LabVIEW, Measurement & Automation Explorer (MAX), and the new NI Launcher.

Using NI Launcher

NI Launcher helps you find and launch installed NI products. It provides you with a method of finding NI products similar to the Start menu in previous versions of Microsoft Windows. To use NI Launcher, click the NI Launcher tile on the Start screen. NI Launcher launches the desktop and opens a menu containing a list of NI products. Click any NI product to launch it.

Note  Unlike previous versions of Microsoft Windows, MAX does not appear as a desktop shortcut. You can launch MAX either from the Start screen or from within NI Launcher.

Pinning Frequently Used Applications

For convenience, you can pin your most-used NI applications, such as MAX, to either the Start screen or the Taskbar on the desktop, as necessary:

Current Application	Icon Location	Pin to Action
Windows 8 Desktop	Desktop Taskbar	Right-click application and select Pin to Taskbar
Windows 8 Desktop	Start screen	Right-click application and select Pin to Start
Windows 8 Start screen	Desktop Taskbar	Right-click application and select Pin to taskbar from the menu bar on the bottom of the screen

Finding All Programs

If you want to find a particular application or related files, such as documentation files, from the Start screen, you can access all installed files by right-clicking anywhere on the Start screen and selecting All apps. A list of all installed software and related files appears, in alphabetical order by creator or type.

For more information about NI support for Windows 8, visit ni.com/windows8.

Back to Top

---

NI-XNET Drops Support for Microsoft Windows Vista, Windows XP, and Windows Server 2003 in 2016

National Instruments NI-XNET driver software will drop support for Microsoft Windows Vista, Windows XP, and Windows Server 2003 as of July 1, 2016. Versions of NI-XNET that ship after July 1, 2016 will not install or run on Windows Vista, Windows XP, or Windows Server 2003. For detailed information about NI application software product life cycles, visit ni.com/info and enter one of the following Info Codes:

Product	Info Code
NI LabVIEW	lifecycle
NI LabWindows/CVI	cvi_lifecycle
NI Measurement Studio	mstudiolifecycle
NI TestStand	tslcp
NI DIAdem	ddlcp
NI SignalExpress	selcp
NI VeriStand	nivslifecycle

Back to Top

---

New NI-XNET 1.8 Features and Changes as Compared to NI-XNET 1.7

The NI-XNET 1.8 release adds the following features:

• Added support for LabVIEW 2013 (32-bit).
• Added support for the NI cRIO-9068 Integrated CompactRIO Real-Time Controller.
  

The NI-XNET 1.8 release adds the following features for C Series modules used with CompactRIO:

• Enabled logging of trigger occurrences in stream input sessions.
• Enabled logging of CAN and LIN bus error occurrences in stream input sessions.
• XNET CAN interfaces can now be used with up to 500 frames, up from 192.
• XNET LIN interfaces can now be used with up to 96 LIN schedules, up from 32.
• Added support for duplicate CAN output objects.
• The minimum LIN break time can now be set to 10 bits for fault-injection purposes.
• Added support for LIN diagnostics, including Node Configuration (free-format only).
  

The NI-XNET 1.8 release changes the following:

• Removed support for LabVIEW 2009.
• C Series support for CompactRIO: Increased the time to discover XNET C Series modules after an FPGA bitstream has been deployed.
  

New NI-XNET 1.7 Features and Changes as Compared to NI-XNET 1.6

The NI-XNET 1.7 release adds the following features for PCI/PXI XNET interfaces and C Series modules used with CompactDAQ:

• Added support for NI 9861 and NI 9862 C Series modules in CompactDAQ chassis to the NI-CAN Compatibility Library for NI-XNET.
  Using the NI-CAN Compatibility Library for NI-XNET, those C Series modules will show up in NI MAX under NI-CAN Devices as PCI-8511 and PCI-8512.
• Added support for XNET C Series modules in USB CompactDAQ chassis to PCI/PXI Real-Time targets.
• Enabled logging of trigger occurrences in stream input sessions.
• Enabled logging of CAN and LIN bus error occurrences in stream input sessions.
• XNET CAN interfaces can now be used with up to 500 frames, up from 192.
• XNET LIN interfaces can now be used with up to 96 LIN schedules, up from 32.
• Added support for duplicate CAN output objects.
• The minimum LIN break time can now be set to 10 bits for fault-injection purposes.
• Added support for LIN diagnostics, including Node Configuration (free-format only).
  

The NI-XNET 1.7 release adds the following features for all XNET interfaces:

• The NI-XNET Database Editor allows multi-selections to simultaneously edit multiple entries.
• The NI-XNET Bus Monitor now displays additional frame statistics for CAN and LIN interfaces.
• The NI-XNET Bus Monitor now displays CAN error frames.
• The NI-XNET Bus Monitor can now transmit frames on a port that is already used for receiving data.
• Improved performance of database deployment to remote targets.
  

Updates for the NI-CAN Compatibility Library for NI-XNET

Changes to the Channel API (LabVIEW):

• CAN Get Property.vi: The Interface Series 2 comparator, Interface Series 2 mask, and Interface Series 2 filter mode properties are now supported.
  

Changes to the Frame API (LabVIEW):

• ncConfigCANNet.vi and ncConfigCANNetRTSI.vi: The Standard comparator, Extended comparator, Standard mask, and Extended mask attributes are now supported.
• ncGetAttr.vi: The Transmit mode, Series 2 comparator, Series 2 mask, and Series 2 filter mode attributes are now supported.
• ncReadNet.vi and ncReadObj.vi: The CanWarnOldData warning is now supported.
  

Changes to the Channel API (ANSI C):

• nctGetProperty function: The nctPropIntfSeries2Comp, nctPropIntfSeries2Mask, and nctPropIntfSeries2FilterMode parameters are now supported.
  

Changes to the Frame API (ANSI C):

• ncConfig function (using the Network Interface Object): The NC_ATTR_COMP_STD, NC_ATTR_COMP_XTD, NC_ATTR_MASK_STD, NC_ATTR_MASK_XTD, NC_ATTR_TRANSMIT_MODE, NC_ATTR_SERIES2_COMP, NC_ATTR_SERIES2_MASK, and NC_ATTR_SERIES2_FILTER_MODE attributes are now supported.
• ncGetAttribute function (using the Network Interface Object): The NC_ATTR_TRANSMIT_MODE, NC_ATTR_SERIES2_COMP, NC_ATTR_SERIES2_MASK, and NC_ATTR_SERIES2_FILTER_MODE attributes are now supported.
• ncSetAttribute function: The NC_ATTR_TIMESTAMP_FORMAT » NC_TIME_FORMAT_RELATIVE attribute is now supported.
• ncRead function: The CanWarnOldData status is now supported.
  

New NI-XNET 1.6 Features and Changes as Compared to NI-XNET 1.5.1

The NI-XNET 1.6 release adds the following features:

• Added support for the NI cDAQ-9138 and NI cDAQ-9139 NI CompactDAQ Stand-Alone Chassis (Windows and RT).
• New feature: Raised the FlexRay limit of 8 PDUs per frame to 16.
  

The NI-XNET 1.6 release changes the following:

• NI-DAQmx 9.6 is now the minimum required version when using XNET C Series devices with Compact DAQ.
• The XNET Database Open.vi and XNET String to IO Name.vi VIs have been deprecated, because they were required only for LabVIEW 8.5.x and 8.6.x.
  

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

The NI-XNET 1.5.1 release adds the following features:

• Added support for LabVIEW 2012 (32-bit).
  

The NI-XNET 1.5.1 release changes the following:

• Removed support for LabVIEW 8.6.
• Removed support for Windows XP prior to Service Pack 3.
  

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.8. 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.
404255	If you install DAQmx version 9.7.0 or older before installing NI-XNET it is possible for your XNET cSeries modules to show up with an "Attributes" tab in MAX that will contain text saying "Unsupported Module". It is ok to ignore this tab and it does not mean anything is wrong your XNET device. This tab can be removed by upgrading to DAQmx version 9.7.5 or newer.
405281	Using database object names that only differ by case in LabVIEW 2012 can cause a problem. This can only be resolved by moving to a different LabVIEW version.

Back to Top

---

Bug Fixes

The following items are the IDs and titles of a subset of issues fixed between NI-XNET 1.7 and NI-XNET 1.8. 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
412046	When using set property for LINDiagP2min with the interface set as master you will receive an invalid property value error.
412047	When using get property of LINDiagP2min with the interface set as master an Invalid Property error was not being returned.

The following items are the IDs and titles of a subset of issues fixed between NI-XNET 1.6 and NI-XNET 1.7. 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
341928	You cannot import diagnostic frames from LDF files (MasterReq/SlaveResp). That includes schedule tables that contain diagnostic frames.
377696	Bus Monitor logs to TDMS files with channel and group names different than NI-XNET examples.
376526	Database editor removes non-XNET data from FIBEX files without warning.
376366	FlexRay Frame Write does not work with payloads > 240 bytes.
372525, 372522	LabVIEW may crash when exiting after running NI-XNET application.
371891	Cannot transmit a frame with 0-length payload just by using a Trigger Signal.
367632	The database property ShowInvalidFromOpen? sometimes shows invalid properties when set to false.
367186	FlexRay frames in the dynamic segment do not support variable sized frames for Frame Input sessions.
365824	FlexRay databases with a frame configured for a different channel in separate slots do not behave correctly.
362589	Having an XNET port selected in MAX causes plug-and-play for NI-XNET Compact DAQ modules to fail.
353541	The example, Remote Transceiver Wakeup.vi, has an incorrectly numbered case statement.
349441	LIN examples do not enable termination when running as a LIN master.
345565	The NI-XNET Database Editor does not import GenMsgSendType attributes of .dbc files
342255	FlexRay frames in the dynamic segment do not support variable sized frames for Frame Output sessions.
310744	NI-XNET Compatibility Library for NI-CAN: Redeploying a MAX database to a Pharlap target requires a restart for the NI-XNET Compatibility Library for NI-CAN to recognize the changes.
172536	Conversion sessions do not work with FlexRay frames using in-cycle repetition.

The following items are the IDs and titles of a subset of issues fixed between NI-XNET 1.5.1 and NI-XNET 1.6. 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
347556	Reading a FlexRay frame with a size that is not a multiple of 24 bytes causes error 0xBFF63090.
354304	FlexRay PDUs linked to more than 8 frames are not supported.
364015	NI-XNET Compatibility Library for NI-CAN: Stack corruption when calling ncRead() on a CAN object without any enqueued data.
344769	TDMS logfile examples may cause an unexpected error in LabVIEW 2012 when displaying all frames from the logfile.
365898	FlexRay PDU Input Single Point example VI has no defaults.
338758	LabVIEW crashes when building a Real-Time executable containing NI-XNET sessions.

The following items are the IDs and titles of a subset of issues fixed between NI-XNET 1.5 and NI-XNET 1.5.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
353852	XNET port wakes up on session start even if no wakeup is on the bus when using single channel FlexRay.
354314	A flush right after a FlexRay Frame Input Queued session is created causes error 0xBFF63001.
345678	NI-XNET Compatibility Library for NI-CAN: Calling nctInitialize() or the CAN Initialize VI with an interface number of –1 causes error 0xBFF63015.

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 during device communication is not supported

Inserting/Removing a module into a cRIO chassis that is actively communicating with an NI 986x module can cause application failures and possibly device damage.

Back to Top

---

Errata to the NI-XNET Hardware and Software ManualNo Special Characters in Database Alias

In the NI-XNET API for LabVIEW  » Additional Topics  » XNET I/O Names  » XNET Database I/O Name section of the NI-XNET Hardware and Software Manual, the String Use for the states:

"The can use any character, but only letters, numbers, underscore (_), and space ( ) are recommended."

This description of as well as others (such as NI-XNET API for C » Reference » Functions » nxdbAddAlias) should state:

"Lowercase letters, uppercase letters, numbers, underscore (_), and space ( ) are valid characters for . Period (.) and other special characters are not supported within the name. Because the is used as the filename portion of an internal filepath (that is, absolute path and file extension removed), it must use the minimum file conventions for all operating systems."

Back to Top

---

Important Information

Copyright

© 2009–2013 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.

End-User License Agreements and Third-Party Legal Notices

You can find end-user license agreements (EULAs) and third-party legal notices in the following locations after installation:

• Notices are located in the \_Legal Information and directories.
• EULAs are located in the \Shared\MDF\Legal\license directory.
• Review \_Legal Information.txt for information on including legal information in installers built with NI products.
  

Trademarks

Refer to the NI Trademarks and Logo Guidelines at ni.com/trademarks for information on National Instruments trademarks. 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.