C Series modules:
- NI 9861 (C Series Low-Speed CAN)
- NI 9862 (C Series High-Speed CAN)
- NI 9866 (C Series LIN)
- NI 9860 (C Series XNET)
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
- cDAQ Controller: NI cDAQ-9138 (Windows and RT) and NI cDAQ-9139 (Windows and RT)
- CompactDAQ—NI-DAQmx 14.0 (or newer) is required for:
- cDAQ Controller: NI cDAQ-9134 (Windows)
- CompactDAQ—NI-DAQmx 14.1 (or newer) is required for:
- cDAQ Controller: NI cDAQ-9134 (RT)
- CompactDAQ—NI-DAQmx 14.5 (or newer) is required for:
- cDAQ Controller: NI cDAQ-9135
- CompactDAQ—NI-DAQmx 15.1 (or newer) is required for:
- USB Chassis: NI cDAQ-9179
- cDAQ Controller: NI cDAQ 9136/37
- CompactRIO—NI Compact RIO 16.0 (or newer) and LabVIEW 2013 SP1 (or newer) are 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 2013 SP1 (or newer) is required to build and deploy a bitstream with NI 986x modules in the project.
- Integrated CompactRIO Real-Time Controller: NI cRIO-9081, NI cRIO-9082, and NI cRIO-906x
- LabVIEW FPGA 2013 (or newer) is required to build and deploy a bitstream with NI 986x modules in the project.
- CompactRIO—NI Compact RIO 16.0 (or newer) and LabVIEW 2014 (or newer) are required for the following targets:
- Integrated CompactRIO Real-Time Controller: NI cRIO-903x
- LabVIEW FPGA 2014 (or newer) is required to build and deploy a bitstream with NI 986x modules in the project.
- CompactRIO—NI Compact RIO 16.0 (or newer) and LabVIEW 2015 (or newer) are required for the following targets:
- Single-Board RIO: NI sbRIO-9627, NI sbRIO-9607
- LabVIEW FPGA 2015 (or newer) is required to build and deploy a bitstream with NI 986x modules in the project.
- CompactRIO Real-Time Controller: NI cRIO-9032, NI cRIO-9037
- When using NI Compact RIO 16.0 (or newer) with NI cRIO-903x or NI cRIO-906x, a bitstream is not needed with NI 986x modules in the project.
- CompactRIO—NI Compact RIO 16.0 (or newer) and LabVIEW 2016 (or newer) are required for the following targets:
- CompactRIO Real-Time Controller: cRIO-9035 (Sync), cRIO-9039 (Sync)
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 2013, 2014, 2015, and 2016
- LabVIEW Real-Time (RT) 2013, 2014, 2015, and 2016
- LabWindows/CVI 8.5 and higher
- Microsoft Visual C/C++ 6.0
Back to Top
New NI-XNET 16.0 Features and Changes as Compared to NI-XNET 15.5The NI-XNET 16.0 release adds the following features:
- Added support for LabVIEW 2016.
- Enabled logging of LIN No Response Frames in stream input sessions and the Bus Monitor.
- Enabled PGN filtering by source address for J1939.
- The NI-XNET run-time installer includes a Port Configuration Utility to configure NI-XNET devices on Windows hosts.
You can find the utility in \Program Files (x86)\National\NI-XNET\portConfig.
The NI-XNET 16.0 release changes the following:
- Improvements that require a firmware update for NI 9860 modules and the cDAQ integrated XNET port.
- Removed support for LabVIEW 2012.
- Removed the NI-XNET Hardware and Software Manual from Start»All Programs»National Instruments»NI-XNET»NI-XNET Documentation.
New NI-XNET 15.5 Features and Changes as Compared to NI-XNET 15.0The NI-XNET 15.5 release adds the following features:
- Added support for the PXIe-8510 high-density module.
- Added support for ISO CAN FD (ISO 11898-1:2015).
- Added support for the cRIO-9032 and cRIO 9037 CompactRIO real-time controllers.
- Added support for the NI cDAQ-9179 USB chassis.
- Added support for the NI cDAQ 9136/37 cDAQ controller.
- Added support for the Software Selectable NI-XNET Transceiver Cable HS/FD (High-Speed ISO CAN FD) and LS/FT (Low-Speed Fault Tolerant).
- Added ISO CAN FD support for the NI-XNET BusMonitor and NI-XNET Database Editor.
- Added the ability to transmit CAN frames within the NI-XNET Bus Monitor on any NI real-time target that NI-XNET supports.
New NI-XNET 15.0 Features and Changes as Compared to NI-XNET 14.5The NI-XNET 15.0 release adds the following features:
- Added support for LabVIEW 2015.
- Added support for the SAE J1939 application protocol.
- Added support for the Cyclic/Event frame timing type.
- Added support for SAE J1939 database properties. To maintain legacy behavior, set the Ignore Application Protocol property on the alias.
The NI-XNET 15.0 release changes the following:
- Removed support for LabVIEW 2011.
New NI-XNET 14.5 Features and Changes as Compared to NI-XNET 14.1The NI-XNET 14.5 release adds the following features:
- Added support for the NI cDAQ-9135 cDAQ Controller.
- Added support for the NI cRIO-903x cRIO Controllers.
- Added support for DBC export.
- Added support for multiple clients using the Bus Monitor on Real-Time targets.
New NI-XNET 14.1 Features and Changes as Compared to NI-XNET 14.0The NI-XNET 14.1 release adds the following features:
- Added support for the NI cDAQ-9134 cDAQ Controller (RT).
New NI-XNET 14.0 Features and Changes as Compared to NI-XNET 1.8The NI-XNET 14.0 release adds the following features:
- Added support for LabVIEW 2014.
- Added support for 64-bit LabVIEW.
- Added support for the NI cDAQ-9134 cDAQ Controller (Windows).
- Added support for the non-ISO CAN FD protocol.
- Added support for multiple input and output streams on the same port.
- Added support for merging database.
- Added support for LIN output stream immediate and replay modes.
- Added support for LIN checksum corruption.
- Added support for LDF export.
- Added support for Bus Monitor on Real-Time targets.
The NI-XNET 14.0 release changes the following:
- Removed support for LabVIEW 2010.
New NI-XNET 1.8 Features and Changes as Compared to NI-XNET 1.7The NI-XNET 1.8 release adds the following features:
- Added support for LabVIEW 2013 (32-bit).
- Added support for the NI cRIO-906x 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.6The 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-XNETChanges 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.1The NI-XNET 1.6 release adds the following features:
- Added support for the NI cDAQ-9138 and NI cDAQ-9139 NI cDAQ Controller (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.5The 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.4The 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.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 Top
Known IssuesThe following items are the IDs and titles of a subset of issues known to be present in NI-XNET 16.0. 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 |
— | On cRIO targets with VxWorks, start the NI-XNET Bus Monitor on an NI-XNET interface from Start»All Programs»National Instruments»NI-XNET instead of starting from MAX. |
Back to Top
Bug FixesThe following items are the IDs and titles of a subset of issues fixed between NI-XNET 15.5 and NI-XNET 16.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 |
| 306177 | Issues fixed in the LIN Dynamic Database Creation example. |
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. |
Back to Top
Additional Programming TopicsNI-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 targets during device communication is not supportedInserting 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.
Back to Top
Automating the Installation of NI ProductsYou 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:
- For more information about silent installations of individual NI products, refer to KB 4CJDP38M, Automating the Installation of a Single Installer.
- For more information about silent installations of NI products in a suite, such as NI Developer Suite, refer to KB 4GGGDQH0, How Do I Automate the Installation of a Suited Installer?.
- To determine what version of NI Installers your product contains, refer to KB 4CJDR18M, How Can I Determine the Type and Version of My NI Installer?.
Using NI Software with Microsoft Windows 10Microsoft 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.
Using NI Software with Microsoft Windows 8.1When 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 16.0 Drops Support for Microsoft Windows 7 RTM, Windows Vista, Windows XP, and Windows Server 2003With this release, NI-XNET drops support for Microsoft Windows 7 RTM (with no service pack), Windows Vista, Windows XP, and Windows Server 2003. NI-XNET 16.0 and later will not install or run on an unsupported OS. You cannot deploy or distribute applications that use NI-XNET 16.0 to an unsupported OS. Additionally, after installing NI-XNET 16.0, you cannot use any installers built on this computer with any version of LabVIEW, LabWindows™/CVI™, NI TestStand™, or Measurement Studio on an unsupported OS.
For more information about the changes to our OS support for 2016, refer to KB 79UC78LS, Why Does my LabVIEW, LabWindows/CVI, Measurement Studio, or TestStand Built Installer Fail on Windows XP/Vista and Server 2003?.
Legal InformationCopyright
© 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:
- 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.
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.
374802E-01
发表于 2020-10-20 23:04:23
