NI-XNET interfaces combine the performance and flexibility of low-level microcontroller interfaces with the speed and power of Windows and LabVIEW Real-Time OS development. Designed from the ground up for performance and ease of use in demanding applications such as hardware-in-the-loop simulation, these interfaces work well in high-signal-count, low-latency environments.
The key technology behind the performance of NI-XNET is the NI-XNET device-driven DMA engine. This patent-pending technology reduces system latency, a common pain point for PC-based CAN, LIN, and FlexRay interfaces, from milliseconds to microseconds. The engine works with onboard per-port processors to move CAN, LIN, and FlexRay frames and signals between the interface and the user program without CPU interrupts, freeing host processor time for processing complex models and applications.
|Network, Ports||PCI||PXI||C Series|
|NI-XNET FlexRay, 2-port||PCI-8517/2||PXI-8517/2|
|NI-XNET CAN, low-speed/fault-tolerant, 1-port||PCI-8511||PXI-8511||NI 9861|
|NI-XNET CAN, low-speed/fault-tolerant, 2-port||PCI-8511/2||PXI-8511/2|
|NI-XNET CAN, high-speed/FD, 1-port||PCI-8512||PXI-8512||NI 9862|
|NI-XNET CAN, high-speed/FD, 2-port||PCI-8512/2||PXI-8512/2|
|NI-XNET CAN, software-selectable/FD, 1-port||PCI-8513||PXI-8513|
|NI-XNET CAN, software-selectable/FD, 2-port||PCI-8513/2||PXI-8513/2|
|NI-XNET LIN, 2-port||PCI-8516/2||PXI-8516/2|
|NI-XNET LIN, 1-port||NI 9866|
Figure 1. Simple NI-XNET Example Code for Reading and Writing CAN Signals
Figure 2. The Same NI-XNET Code Adapted to Reading and Writing FlexRay Signals by Changing the Session Inputs
Emerging embedded networks, especially in the automotive industry, are combining CAN, LIN, and FlexRay buses to maximize performance while maintaining cost benefits and reducing transition efforts. A common API simplifies the development and maintenance of applications that prototype, simulate, and test these hybrid embedded networks. With the extra performance benefits of the FlexRay bus comes added complexity and bandwidth requirements for test, simulation, and prototyping systems.
The NI-XNET API is designed to make it easier for both new and experienced CAN, LIN, and FlexRay engineers to get up and running quickly with CAN, LIN, and FlexRay applications. With the tight integration of the LabVIEW project, more than 140 out-of-the-box examples, example signal databases, and comprehensive documentation, NI-XNET makes it easier to develop CAN, LIN, and FlexRay applications. NI-XNET also makes it easy to use the same software application in different environments and use cases by working with the same NI-XNET API for PCI, PXI, NI CompactDAQ, and NI CompactRIO.
Real-time processing of CAN, LIN, and FlexRay signal and frame data is crucial for accurate hardware-in-the-loop simulation and rapid control prototyping. LabVIEW applications for NI-XNET devices work on both Windows and LabVIEW Real-Time targets with little to no code modification, which simplifies building and maintaining code across platforms. NI-XNET interfaces are designed to operate in a real-time environment with minimum jitter and maximum performance, making simulations more accurate and test systems more reliable.
NI-XNET interfaces combine the performance of low-level microcontroller programming with the speed and power of Windows and LabVIEW Real-Time OS development. The patent-pending NI-XNET device-driven DMA engine reduces system latency, a common pain point for PC-based CAN interfaces, from milliseconds to microseconds. The engine enables the onboard processor to move CAN frames and signals between the interface and the user program without CPU interrupts, freeing host processor time for processing complex models and applications.
The mark LabWindows is used under a license from Microsoft Corporation. Windows is a registered trademark of Microsoft Corporation in the United States and other countries.