March 2016
This file contains information about the NI-XNET software for Windows 10/8/7/Vista/XP and LabVIEW™ Real-Time (RT). Information in this file is organized in the following sections:
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»NI-XNET Documentation.
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.
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.
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.
You can install and run this version of the NI-XNET software on the following operating systems:
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 operating systems.
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. |
This version of the NI-XNET software supports the following National Instruments hardware products on Windows and LabVIEW RT:
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.
This version of the NI-XNET software supports the following development environments:
The NI-XNET 15.5 release adds the following features:
The NI-XNET 15.0 release adds the following features:
The NI-XNET 15.0 release changes the following:
The NI-XNET 14.5 release adds the following features:
The NI-XNET 14.1 release adds the following features:
The NI-XNET 14.0 release adds the following features:
The NI-XNET 14.0 release changes the following:
The NI-XNET 1.8 release adds the following features:
The NI-XNET 1.8 release adds the following features for C Series modules used with CompactRIO:
The NI-XNET 1.8 release changes the following:
The NI-XNET 1.7 release adds the following features for PCI/PXI XNET interfaces and C Series modules used with CompactDAQ:
The NI-XNET 1.7 release adds the following features for all XNET interfaces:
Changes to the Channel API (LabVIEW):
Changes to the Frame API (LabVIEW):
Changes to the Channel API (ANSI C):
Changes to the Frame API (ANSI C):
The NI-XNET 1.6 release adds the following features:
The NI-XNET 1.6 release changes the following:
The NI-XNET 1.5.1 release adds the following features:
The NI-XNET 1.5.1 release changes the following:
The NI-XNET 1.5 release adds the following features:
The NI-XNET 1.5 release changes the following:
The NI-XNET 1.4 release adds the following features:
The NI-XNET 1.4 release changes the following:
The NI-XNET 1.3.1 release adds the following feature:
The NI-XNET 1.3.1 release changes the following:
The NI-XNET 1.3 release adds the following features:
The NI-XNET 1.3 release changes the following behavior:
The NI-XNET 1.1.1 release adds the following features:
The NI-XNET 1.1 release adds the following features:
The NI-XNET 1.1 release changes the following behavior:
The following items are the IDs and titles of a subset of issues known to be present in NI-XNET 15.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 |
---|---|
- | - |
The following items are the IDs and titles of a subset of issues fixed between NI-XNET 15.0 and NI-XNET 15.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 |
---|---|
501084 | Issues fixed on scanning for interfaces in NI VeriStand using NI-XNET Bus Monitor. |
542151 | Issues fixed when NI-XNET Project Session is deployed as a Startup Executable on NI CompactRIO 903x targets. |
546524 | Synchronization issues fixed in the FlexRay DAQmx Synchronization example. |
571052 | Issues fixed in LDF import with one-bit signals using a physical value encoding. |
574357 | Issues fixed on localized (Czech) Windows XP SP3. |
577697 | Issue fixed with some cyclic frame transmissions when repeatedly starting and stopping sessions. |
The following items are the IDs and titles of a subset of issues fixed between NI-XNET 14.5 and NI-XNET 15.0. 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 |
---|---|
516451 | Issues using Add/Remove Signals dialog in the NI-XNET Bus Monitor. |
The following items are the IDs and titles of a subset of issues fixed between NI-XNET 14.0 and NI-XNET 14.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 |
---|---|
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. |
405281 | Using database object names that differ only by case in LabVIEW 2012 can cause a problem. You can resolve this issue only by moving to a different LabVIEW version. |
491096 | LabVIEW memory corruption occurs when using invalid references for XY Read. |
496726 | LabVIEW crashes when attempting to store a CAN frame in a LabVIEW queue. |
294267 | Unable to link examples for 64-bit due to a missing nixnet.lib. |
The following items are the IDs and titles of a subset of issues fixed between NI-XNET 1.8 and NI-XNET 14.0. 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 |
---|---|
472485 | XNET Clear hangs when writing blank frame data. |
405944 | Read Signal Waveform may return invalid data. |
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. |
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. |
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.
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.
Inserting a module into or removing a module from a cRIO chassis that is actively communicating with an NI 986x module can cause application failures and possibly device damage.
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 about automating the installation of NI products, refer to the following KnowledgeBase articles:
Microsoft Windows 10 is the latest version of the Windows operating system and features significant changes compared to previous versions. Windows 10 introduces several new capabilities and also combines features from both Windows 7 and Windows 8. For more information about NI support for Windows 10, visit ni.com/windows10.
When you install NI software on Microsoft Windows 8.1, you will notice a few additional tiles in the Apps view, including shortcuts to NI application software products such as NI LabVIEW, Measurement & Automation Explorer (NI MAX), and NI Launcher. For more information about NI support for Windows 8.1, visit ni.com/windows8.
NI-XNET will drop support for Microsoft Windows 7 RTM (with no service pack), 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 7 RTM (with no service pack), 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 |
---|---|
LabVIEW | lifecycle |
LabWindows™/CVI™ | cvi_lifecycle |
Measurement Studio | mstudiolifecycle |
TestStand | tslcp |
DIAdem | ddlcp |
SignalExpress | selcp |
VeriStand | nivslifecycle |
Copyright
© 2009–2016 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.
NI 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:
U.S. Government Restricted Rights
If you are an agency, department, or other entity of the United States Government ("Government"), the use, duplication, reproduction, release, modification, disclosure or transfer of the technical data included in this manual is governed by the Restricted Rights provisions under Federal Acquisition Regulation 52.227-14 for civilian agencies and Defense Federal Acquisition Regulation Supplement Section 252.227-7014 and 252.227-7015 for military agencies.
IVI Foundation Copyright Notice
Content from the IVI specifications reproduced with permission from the IVI Foundation.
The IVI Foundation and its member companies make no warranty of any kind with regard to this material, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. The IVI Foundation and its member companies shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this material.
Trademarks
Refer to the NI Trademarks and Logo Guidelines at ni.com/trademarks for information on NI trademarks. Other product and company names mentioned herein are trademarks or trade names of their respective companies.
Patents
For patents covering the NI products/technology, refer to the appropriate location: Help»Patents in your software, the patents.txt file on your media, or the NI Patent Notice at ni.com/patents.
374802D-01