{"id":785,"count":3,"description":"
\r\n

NI C Series Communication Modules<\/h2>\r\n\r\n
\r\n

NI C Series communication modules add industrial, vehicle-network and serial interfaces to CompactDAQ and CompactRIO systems. They support applications that must exchange, log, simulate or monitor data on CAN, CAN FD, LIN, FlexRay, RS-232, RS-422, RS-485 and Ethernet networks.<\/p>\r\n\r\n

Select the module by the required communication protocol and physical layer, not simply by the connected device. Bus speed, port count, electrical isolation, termination, timestamping, cabling, software support and target platform all affect whether a C Series communication interface is suitable for the complete system.<\/p>\r\n <\/div>\r\n\r\n

C Series Communication Interface Types<\/h3>\r\n\r\n
\r\n \r\n \r\n \r\n \r\n \r\n \r\n \r\n \r\n \r\n
Communication Type<\/th>\r\n Typical Interface<\/th>\r\n Primary Use<\/th>\r\n Key Selection Considerations<\/th>\r\n <\/tr>\r\n <\/thead>\r\n
CAN and CAN FD<\/td>\r\n Controller Area Network<\/td>\r\n Automotive ECU communication, battery systems, vehicle logging and CAN test<\/td>\r\n Classic CAN or CAN FD support, baud rate, termination, isolation and channel count<\/td>\r\n <\/tr>\r\n
LIN<\/td>\r\n Local Interconnect Network<\/td>\r\n Low-cost automotive subnetwork monitoring and simulation<\/td>\r\n LIN master or slave role, schedule requirements, signal database and vehicle wiring<\/td>\r\n <\/tr>\r\n
FlexRay<\/td>\r\n Deterministic automotive network<\/td>\r\n Automotive development, validation and network simulation<\/td>\r\n Channel configuration, synchronization, topology and software compatibility<\/td>\r\n <\/tr>\r\n
Serial<\/td>\r\n RS-232, RS-422 or RS-485<\/td>\r\n Industrial instruments, PLCs, motion devices and legacy equipment<\/td>\r\n Electrical standard, point-to-point or multidrop network, isolation and connector wiring<\/td>\r\n <\/tr>\r\n
Ethernet<\/td>\r\n Industrial or network Ethernet<\/td>\r\n Network-connected instruments, embedded devices and distributed test systems<\/td>\r\n Network architecture, protocol stack, bandwidth, addressing and software integration<\/td>\r\n <\/tr>\r\n <\/tbody>\r\n <\/table>\r\n <\/div>\r\n\r\n

Representative NI C Series Communication Module Families<\/h3>\r\n\r\n
\r\n \r\n \r\n \r\n \r\n \r\n \r\n \r\n \r\n
Module Family<\/th>\r\n Unique Category<\/th>\r\n Core Function<\/th>\r\n Best Fit<\/th>\r\n <\/tr>\r\n <\/thead>\r\n
NI-985x Series<\/td>\r\n CAN and LIN Communication<\/td>\r\n Interfaces for automotive CAN, CAN FD or LIN networks, depending on the exact module<\/td>\r\n Vehicle-network logging, ECU validation and CAN\/LIN simulation<\/td>\r\n <\/tr>\r\n
NI-986x Series<\/td>\r\n Automotive Network Communication<\/td>\r\n Interfaces for CAN and FlexRay applications, depending on the exact module<\/td>\r\n Automotive development and deterministic vehicle-network testing<\/td>\r\n <\/tr>\r\n
NI-987x Series<\/td>\r\n Serial Communication<\/td>\r\n RS-232, RS-422 or RS-485 interfaces with configurations varying by model<\/td>\r\n Industrial serial equipment, automation controllers and legacy devices<\/td>\r\n <\/tr>\r\n
NI-988x Series<\/td>\r\n Ethernet Communication<\/td>\r\n Ethernet interface capability for CompactRIO and CompactDAQ communication architectures<\/td>\r\n Network-connected test, monitoring and embedded-control systems<\/td>\r\n <\/tr>\r\n <\/tbody>\r\n <\/table>\r\n <\/div>\r\n\r\n

Confirm the complete part number before ordering. Protocol support, port quantity, connector type, electrical isolation and supported CompactDAQ or CompactRIO platforms can differ within the same module family.<\/p>\r\n\r\n

How to Select a C Series Communication Module<\/h3>\r\n\r\n

1. Identify the Protocol and Physical Layer<\/h4>\r\n\r\n

Determine whether the connected equipment uses CAN, CAN FD, LIN, FlexRay, Ethernet, RS-232, RS-422 or RS-485. Protocol names alone are not enough: confirm the electrical signaling standard, connector, cable type, network topology and any required termination.<\/p>\r\n\r\n

For example, a device described as \u201cserial\u201d may require RS-232 point-to-point communication, RS-485 multidrop wiring or RS-422 differential signaling. These interfaces are not electrically interchangeable.<\/p>\r\n\r\n

2. Confirm Channel Count and Network Topology<\/h4>\r\n\r\n

Count the number of independent buses or serial ports required. One physical CAN network normally uses one interface channel, while separate vehicle networks, isolated subsystems or simultaneous simulation and logging may require multiple channels.<\/p>\r\n\r\n

For RS-485 systems, also determine whether the application uses two-wire or four-wire wiring, half-duplex or full-duplex communication, and multiple nodes on one bus.<\/p>\r\n\r\n

3. Verify Data Rate and Bus Loading<\/h4>\r\n\r\n

Confirm the required baud rate, message frequency, frame type and expected bus loading. A module must support not only the nominal network rate but also the complete application workload, including monitoring, transmission, timestamping and data logging.<\/p>\r\n\r\n

CAN FD applications should verify both arbitration-phase and data-phase communication requirements. High traffic levels may also increase host processing and file-storage requirements during long-duration logging.<\/p>\r\n\r\n

4. Evaluate Isolation and Grounding<\/h4>\r\n\r\n

Isolation is important when equipment operates at different ground potentials, when communication wiring extends across machinery or vehicles, or when electrical noise is expected. Isolated interfaces can help reduce ground-loop risk and protect the measurement or control system from common-mode disturbances.<\/p>\r\n\r\n

Isolation does not remove the need for correct cable shielding, grounding and termination. Review the complete wiring arrangement before connecting a module to powered equipment.<\/p>\r\n\r\n

5. Plan Termination and Cabling<\/h4>\r\n\r\n

CAN networks normally require termination at the two physical ends of the bus. Incorrect termination, excessive stub length, unsuitable cable or poor shield connection can cause communication errors even when the selected module supports the correct protocol.<\/p>\r\n\r\n

Serial and Ethernet systems also require appropriate cable type, pinout, shielding and connector conversion. Confirm whether the required terminal block, breakout cable or adapter is included in the planned system.<\/p>\r\n\r\n

6. Review Timing and Timestamping Requirements<\/h4>\r\n\r\n

Logging applications often require accurate timestamps so bus traffic can be correlated with analog measurements, digital I\/O, GPS data or control events. Determine whether the test needs approximate software timestamps, hardware timestamps, synchronized acquisition or deterministic real-time response.<\/p>\r\n\r\n

For mixed I\/O systems, plan synchronization at the system level. A communication interface installed in the same chassis as an analog module does not automatically guarantee that all data shares the same timing reference.<\/p>\r\n\r\n

7. Confirm Software and Database Compatibility<\/h4>\r\n\r\n

Automotive communication modules commonly use NI-XNET software for supported CAN, LIN and FlexRay applications. Serial interfaces typically use the applicable NI serial or VISA software stack. Verify driver support for the exact module, operating system and controller before purchase.<\/p>\r\n\r\n

Vehicle-network applications may also require DBC, FIBEX, LDF or other signal-description files. These databases define message IDs, signal scaling, byte order and network schedules; the hardware interface alone does not provide this application information.<\/p>\r\n\r\n

CAN, CAN FD, LIN and FlexRay Considerations<\/h3>\r\n\r\n

CAN and CAN FD<\/h4>\r\n\r\n

CAN is widely used for robust distributed communication in vehicles, battery systems, industrial equipment and machinery. CAN FD extends the format to support larger payloads and, in supported networks, a faster data phase. Confirm whether the system uses classic CAN only or requires CAN FD capability.<\/p>\r\n\r\n

Review nominal bit rate, CAN FD data rate, network termination, cable length, node count and the need to transmit, receive, log or simulate messages. A passive monitoring application can have different requirements from an ECU simulation or hardware-in-the-loop system.<\/p>\r\n\r\n

LIN<\/h4>\r\n\r\n

LIN is a lower-cost single-wire automotive network commonly used for body electronics and local subsystems. Selection should account for master or slave behavior, schedule timing, signal database availability and the intended monitoring or simulation role.<\/p>\r\n\r\n

FlexRay<\/h4>\r\n\r\n

FlexRay is designed for deterministic automotive communication and can be used where timing behavior is critical. Confirm the network configuration, channel arrangement, synchronization requirements and the software environment used to configure and interpret the traffic.<\/p>\r\n\r\n

\r\n

A C Series communication module provides an interface to the network. It does not automatically supply a vehicle database, ECU calibration file, simulation model or the correct cable harness. These supporting elements should be included in the system design and quotation request.<\/p>\r\n <\/div>\r\n\r\n

Serial and Ethernet Communication Considerations<\/h3>\r\n\r\n

RS-232, RS-422 and RS-485<\/h4>\r\n\r\n

RS-232 is generally used for short-distance point-to-point communication. RS-422 and RS-485 use differential signaling and are commonly selected for longer cable runs or electrically noisy industrial environments. RS-485 also supports multidrop network arrangements when wired and terminated correctly.<\/p>\r\n\r\n

Confirm connector pinout, handshake signals, duplex mode, voltage levels, cable length and whether galvanic isolation is required. Legacy serial devices often use manufacturer-specific command sets that must be supported by the control software.<\/p>\r\n\r\n

Ethernet<\/h4>\r\n\r\n

Ethernet connectivity can support network-connected instruments, embedded equipment and distributed test architectures. Selection should consider the intended network protocol, IP addressing, network security, required throughput and whether the interface is used for control, data exchange or system integration.<\/p>\r\n\r\n

For deterministic control or high-throughput acquisition, evaluate the entire controller, chassis, network and application architecture rather than relying only on the Ethernet port speed.<\/p>\r\n\r\n

CompactDAQ and CompactRIO Platform Compatibility<\/h3>\r\n\r\n

CompactDAQ systems<\/a> are well suited to PC-based measurement, logging and portable test applications. Communication modules can be combined with analog, digital and sensor I\/O when bus traffic must be correlated with physical measurements.<\/p>\r\n\r\n

CompactRIO systems<\/a> are used for embedded monitoring, real-time control and FPGA-based applications. Verify exact module support for the selected chassis, controller, operating mode and software environment before finalizing a CompactRIO architecture.<\/p>\r\n\r\n

Review available \u041c\u043e\u0434\u0443\u043b\u0438 NI \u0441\u0435\u0440\u0438\u0438 C<\/a> when the system also needs analog input, analog output, digital I\/O, temperature measurement or dynamic-signal acquisition.<\/p>\r\n\r\n

\u0422\u0438\u043f\u0438\u0447\u043d\u044b\u0435 \u043f\u0440\u0438\u043c\u0435\u043d\u0435\u043d\u0438\u044f<\/h3>\r\n\r\n