{"id":747,"count":11,"description":"
\r\n

NI PXI MXI Interfaces and Remote Control Modules<\/h2>\r\n\r\n
\r\n

NI PXI MXI interfaces connect an external desktop computer, industrial PC, rackmount workstation, server or another PXI system to a PXI or PXI Express chassis. MXI extends the host computer\u2019s PCI or PCI Express bus through a cable, allowing compatible PXI instruments to operate as resources within the host system\u2019s PCI hierarchy.<\/p>\r\n\r\n

PXI MXI hardware is used for external-PC control, high-bandwidth acquisition, multichassis expansion, distributed test racks and legacy-system support. Selecting an interface requires more than matching connector appearance: the host adapter, chassis-side module, cable generation, lane width, chassis controller slot, computer BIOS and required throughput must form a supported system.<\/p>\r\n <\/div>\r\n\r\n

What Is a PXI MXI Interface?<\/h3>\r\n\r\n

MXI, or Multisystem eXtension Interface, is a hardware architecture that extends a computer bus between separate enclosures. In a typical PXI configuration, a host-side PCI Express card connects through an MXI cable to a remote-control module installed in the system-controller slot of a PXI or PXI Express chassis.<\/p>\r\n\r\n

Because the connection is based on PCI or PCI Express rather than conventional Ethernet communication, the host operating system can enumerate supported PXI instruments as locally attached devices. Existing NI instrument drivers normally communicate with the modules without requiring a separate network protocol in the test application.<\/p>\r\n\r\n

\r\n

A chassis-side MXI module is not normally a complete remote-control system by itself. Verify the matching host interface, cable type, cable quantity, connector, generation and supported computer architecture before ordering. Mechanically similar MXI cables and interfaces are not necessarily electrically compatible.<\/p>\r\n <\/div>\r\n\r\n

PXI MXI Architecture Comparison<\/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 \r\n
MXI Architecture<\/th>\r\n Representative Capability<\/th>\r\n Typical Application<\/th>\r\n Important Selection Point<\/th>\r\n <\/tr>\r\n <\/thead>\r\n
MXI-Express x1<\/td>\r\n Approximately 132 to 250 MB\/s theoretical bandwidth, depending on the model<\/td>\r\n Legacy PXI control, switching, DMM and moderate-rate DAQ systems<\/td>\r\n Confirm whether the chassis uses a classic PXI or PXI Express controller slot<\/td>\r\n <\/tr>\r\n
MXI-Express x4<\/td>\r\n Up to approximately 1 GB\/s theoretical link bandwidth<\/td>\r\n General PXIe instrumentation and moderate-bandwidth acquisition<\/td>\r\n Remote-control and daisy-chain modules have different functions<\/td>\r\n <\/tr>\r\n
MXI-Express Gen2 x8<\/td>\r\n Up to approximately 4 GB\/s theoretical bandwidth<\/td>\r\n Digitizers, RF instruments, FPGA processing and higher-rate DAQ<\/td>\r\n Match the chassis-side module with the correct Gen2 host adapter and cable<\/td>\r\n <\/tr>\r\n
MXI-Express Gen2 x16<\/td>\r\n Up to approximately 8 GB\/s theoretical bandwidth<\/td>\r\n Legacy high-throughput PXIe systems using approved host platforms<\/td>\r\n Host BIOS and computer qualification can be more restrictive than physical slot compatibility<\/td>\r\n <\/tr>\r\n
MXI-Express Gen3 x16<\/td>\r\n Up to 16 GB\/s theoretical link bandwidth; sustained application throughput is system dependent<\/td>\r\n High-speed streaming, RF, semiconductor and data-intensive automated test<\/td>\r\n An x16 configuration may require multiple matched cables and adequate host PCIe resources<\/td>\r\n <\/tr>\r\n
Fiber-Optic MXI<\/td>\r\n Long-distance PCI Express extension with electrical isolation between locations<\/td>\r\n Distributed laboratories, separate equipment rooms and electrically noisy installations<\/td>\r\n Fiber support and usable lane width depend on the exact interface and firmware<\/td>\r\n <\/tr>\r\n <\/tbody>\r\n <\/table>\r\n <\/div>\r\n\r\n

NI PXI MXI Interface Product Guide<\/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 \r\n \r\n \r\n \r\n \r\n \r\n
\u041c\u043e\u0434\u0435\u043b\u044c<\/th>\r\n Unique Category<\/th>\r\n Key Differentiator<\/th>\r\n Best Fit<\/th>\r\n <\/tr>\r\n <\/thead>\r\n
HDD-8261<\/a><\/td>\r\n External RAID Data-Streaming System<\/td>\r\n MXI-connected external storage architecture for recording large measurement data sets; not a PXI chassis controller<\/td>\r\n Maintaining legacy stream-to-disk and high-capacity acquisition systems<\/td>\r\n <\/tr>\r\n
PXI-8360<\/a><\/td>\r\n Classic PXI x1 Remote Controller<\/td>\r\n MXI-Express x1 copper interface for controlling a conventional PXI or CompactPCI chassis from an external computer<\/td>\r\n Legacy classic-PXI systems with moderate transfer requirements<\/td>\r\n <\/tr>\r\n
PXIe-8361<\/a><\/td>\r\n PXIe x1 Remote Controller<\/td>\r\n Single-port MXI-Express x1 chassis interface with up to 214 MB\/s theoretical bandwidth<\/td>\r\n General external-PC control where instrument throughput is limited<\/td>\r\n <\/tr>\r\n
PXIe-8364<\/a><\/td>\r\n x1 Daisy-Chain Expander<\/td>\r\n 250 MB\/s-class MXI-Express x1 bus-extension module for supported multichassis topologies<\/td>\r\n Expanding low- to moderate-bandwidth systems across multiple chassis<\/td>\r\n <\/tr>\r\n
PXIe-8370<\/a><\/td>\r\n x4 Remote Controller<\/td>\r\n MXI-Express x4 chassis-side remote-control interface with up to 1 GB\/s theoretical bandwidth<\/td>\r\n General PXIe systems requiring more bandwidth than an x1 connection<\/td>\r\n <\/tr>\r\n
PXIe-8374<\/a><\/td>\r\n x4 Daisy-Chain Expander<\/td>\r\n MXI-Express x4 copper bus-extension module supporting selected multichassis configurations<\/td>\r\n Scalable test systems using multiple moderate-bandwidth PXIe chassis<\/td>\r\n <\/tr>\r\n
PXIe-8381<\/a><\/td>\r\n Gen2 x8 Remote Controller<\/td>\r\n Single-link MXI-Express Gen2 x8 chassis interface with up to 4 GB\/s theoretical bandwidth<\/td>\r\n High-speed digitizers, RF modules, FPGA devices and data acquisition<\/td>\r\n <\/tr>\r\n
PXIe-8383<\/a><\/td>\r\n Gen2 x8 Remote-Control Bundle<\/td>\r\n Catalog designation associated with a PCIe-8383 host interface, PXIe-8381 chassis module and compatible x8 cable<\/td>\r\n Procuring a matched Gen2 x8 external-PC control configuration<\/td>\r\n <\/tr>\r\n
PXIe-8384<\/a><\/td>\r\n Gen2 x8 Daisy-Chain Expander<\/td>\r\n 4 GB\/s-class bus-extension module used to add supported chassis or compatible MXI-connected devices<\/td>\r\n High-bandwidth multichassis PXIe systems<\/td>\r\n <\/tr>\r\n
PXIe-8388<\/a><\/td>\r\n Gen2 x16 High-Bandwidth Remote Controller<\/td>\r\n Legacy MXI-Express Gen2 x16 architecture with up to 8 GB\/s theoretical bandwidth<\/td>\r\n Maintaining approved high-throughput Gen2 x16 test systems<\/td>\r\n <\/tr>\r\n
PXIe-8398<\/a><\/td>\r\n Gen3 x16 Remote Controller<\/td>\r\n Current-generation MXI-Express Gen3 x16 module with copper and supported fiber options and up to 16 GB\/s theoretical bandwidth<\/td>\r\n High-performance RF, semiconductor, digitizer and stream-to-disk systems<\/td>\r\n <\/tr>\r\n <\/tbody>\r\n <\/table>\r\n <\/div>\r\n\r\n

The table follows the products currently assigned to this category. Some entries represent bus-extension or storage functions rather than a conventional host-to-chassis controller. Confirm the exact model designation and included system components before purchasing.<\/p>\r\n\r\n

How to Select a PXI MXI Interface<\/h3>\r\n\r\n

1. Define the Required System Function<\/h4>\r\n\r\n

First determine whether the requirement is external-PC control, expansion from a master PXI chassis, daisy chaining additional chassis, connection to an external storage system or communication between independently controlled systems.<\/p>\r\n\r\n

A remote controller and a bus-extension module are not interchangeable. Remote-control modules connect the host PCI Express hierarchy to the first chassis, while daisy-chain interfaces extend that hierarchy from an existing controller or master chassis to additional enclosures.<\/p>\r\n\r\n

2. Identify the Chassis Controller Slot<\/h4>\r\n\r\n

Classic PXI and PXI Express chassis use different controller-slot connectors. The PXI-8360 is designed for compatible conventional PXI systems, while PXIe models require a PXI Express system-controller slot.<\/p>\r\n\r\n

A hybrid peripheral slot does not normally replace the dedicated controller slot. Check the exact \u0428\u0430\u0441\u0441\u0438 PXI<\/a> manual and slot map before selecting an MXI module.<\/p>\r\n\r\n

3. Match the Host-Side Interface<\/h4>\r\n\r\n

An external computer normally requires a compatible PCI, PCI Express, ExpressCard or Thunderbolt host interface. The physical slot must provide the required electrical lane width and PCIe generation. A mechanically x16 slot may be electrically wired for fewer lanes or share bandwidth with another motherboard device.<\/p>\r\n\r\n

Record the host-interface model, part number, computer model, motherboard slot and operating system. For legacy systems, also confirm whether the quotation includes the host card or only the chassis-side module.<\/p>\r\n\r\n

4. Match MXI Generation and Lane Width<\/h4>\r\n\r\n

MXI-Express x1, x4, Gen2 x8, Gen2 x16 and Gen3 x16 hardware use different link architectures. A newer module should not be assumed to operate with an older host card or cable simply because the connectors appear similar.<\/p>\r\n\r\n

The complete link normally operates according to its slowest compatible component. Installing a high-bandwidth module in a lower-lane host slot or connecting it through an inappropriate cable prevents the system from reaching the expected performance and may prevent link establishment entirely.<\/p>\r\n\r\n

5. Calculate Required Sustained Throughput<\/h4>\r\n\r\n

Estimate the aggregate data rate of every instrument transferring data through the MXI link:<\/p>\r\n\r\n

Required data rate = active channels \u00d7 sample rate \u00d7 transferred bytes per sample.<\/strong><\/p>\r\n\r\n

Include digitizer records, RF I\/Q streams, FPGA transfers, output waveforms, timestamps and simultaneous instrument activity. Theoretical MXI bandwidth is not the same as sustained application throughput. PCIe protocol overhead, memory copies, driver behavior, transfer size, chassis switches and host architecture reduce the usable rate.<\/p>\r\n\r\n

For continuous acquisition, review the complete PXI data-streaming<\/a> path, including host memory and storage performance.<\/p>\r\n\r\n

6. Select Copper or Fiber Cabling<\/h4>\r\n\r\n

Copper MXI cables are suitable for short connections within a rack, workbench or nearby equipment installation. They normally provide the maximum lane width supported by the matching interface but have limited distance.<\/p>\r\n\r\n

Fiber-optic configurations support longer distances and provide electrical separation between locations. This is useful when the host computer and PXI chassis are in separate rooms or have different ground potentials. Fiber availability, maximum distance and effective lane width depend on the exact interface, cable and firmware.<\/p>\r\n\r\n

7. Determine Single- or Multichassis Requirements<\/h4>\r\n\r\n

A basic remote-control module may support only one host-to-chassis link. Multichassis systems require a compatible downstream or daisy-chain interface such as the PXIe-8364, PXIe-8374 or PXIe-8384, or a newer multichassis-capable architecture.<\/p>\r\n\r\n

Check the supported topology, number of chassis, cable order and accumulated PCIe switch depth. Large PCIe device trees can exceed the BIOS resource-allocation capability of some computers even when every individual interface is electrically compatible.<\/p>\r\n\r\n

8. Verify Lifecycle and Replacement Requirements<\/h4>\r\n\r\n

Several earlier MXI interfaces remain important for installed systems but are no longer preferred for new designs. A technically newer interface may require a new host card, cables, chassis, firmware, operating system or software qualification.<\/p>\r\n\r\n

When maintaining validated production equipment, preserving the original MXI family can reduce software and system requalification. For a new high-bandwidth system, the PXIe-8398 generally provides a more current Gen3 architecture.<\/p>\r\n\r\n

Host-Side and Chassis-Side Components<\/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
Component<\/th>\r\n Location<\/th>\r\n Function<\/th>\r\n What to Verify<\/th>\r\n <\/tr>\r\n <\/thead>\r\n
Host Interface<\/td>\r\n Desktop PC, workstation, server or master chassis<\/td>\r\n Connects the host PCI Express hierarchy to the external MXI link<\/td>\r\n Model, generation, electrical lane width, slot availability and BIOS support<\/td>\r\n <\/tr>\r\n
MXI Cable<\/td>\r\n Between host and chassis or between chassis<\/td>\r\n Carries PCI Express communication and supported control signals<\/td>\r\n Copper or fiber, generation, lane count, connector, length and quantity<\/td>\r\n <\/tr>\r\n
Remote-Control Module<\/td>\r\n PXI or PXIe system-controller slot<\/td>\r\n Bridges the external MXI connection to the chassis backplane<\/td>\r\n Chassis slot type, bandwidth, matching host card and supported topology<\/td>\r\n <\/tr>\r\n
Daisy-Chain Interface<\/td>\r\n Master or expansion chassis<\/td>\r\n Adds downstream chassis or compatible external devices<\/td>\r\n Upstream and downstream module roles, port usage and maximum topology<\/td>\r\n <\/tr>\r\n
PXI Platform Software<\/td>\r\n Host operating system<\/td>\r\n Provides PXI system identification, configuration and management<\/td>\r\n Operating-system version, PXI Platform Services and instrument drivers<\/td>\r\n <\/tr>\r\n <\/tbody>\r\n <\/table>\r\n <\/div>\r\n\r\n

PXI MXI Remote Control vs Embedded Controller<\/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 \r\n \r\n
Consideration<\/th>\r\n MXI Remote Control<\/th>\r\n Embedded PXI Controller<\/th>\r\n <\/tr>\r\n <\/thead>\r\n
Computer Location<\/td>\r\n External computer connected by cable<\/td>\r\n Controller installed directly in the chassis<\/td>\r\n <\/tr>\r\n
Processor Choice<\/td>\r\n Can use selected desktop, server or workstation hardware<\/td>\r\n Limited to compatible PXI embedded-controller models<\/td>\r\n <\/tr>\r\n
GPU and Storage Expansion<\/td>\r\n Can use host-computer PCIe slots, GPUs and storage resources<\/td>\r\n Determined by the embedded controller and chassis configuration<\/td>\r\n <\/tr>\r\n
Physical Integration<\/td>\r\n Requires a host interface, MXI cable and additional computer<\/td>\r\n Provides a compact self-contained PXI system<\/td>\r\n <\/tr>\r\n
PCIe Compatibility<\/td>\r\n Depends on host BIOS, motherboard resources and MXI generation<\/td>\r\n Controller and chassis are normally qualified as a platform<\/td>\r\n <\/tr>\r\n
\u041e\u0431\u0441\u043b\u0443\u0436\u0438\u0432\u0430\u043d\u0438\u0435<\/td>\r\n The external computer can often be serviced separately<\/td>\r\n The controller is part of the PXI chassis assembly<\/td>\r\n <\/tr>\r\n
Best Fit<\/td>\r\n High-performance computing, specialized storage or centralized control<\/td>\r\n Portable, compact and standardized standalone test systems<\/td>\r\n <\/tr>\r\n <\/tbody>\r\n <\/table>\r\n <\/div>\r\n\r\n

Review available PXI controllers<\/a> when comparing remote and embedded architectures. Processor speed alone should not determine the choice; PCIe topology, maintainability, environmental requirements and qualification effort are also important.<\/p>\r\n\r\n

PXI MXI vs Ethernet Instrument Control<\/h3>\r\n\r\n

MXI and Ethernet serve different system functions. MXI transparently extends a PCI or PCI Express hierarchy, allowing low-latency access and high-throughput DMA transfers between the host and PXI instruments. Ethernet communicates through network protocols and does not normally make the PXI backplane appear as a local PCIe bus.<\/p>\r\n\r\n

Ethernet is useful for distributed instruments, long-distance networking and systems that benefit from standard network infrastructure. MXI is preferred when the host must directly enumerate PXI modules or sustain high-bandwidth instrument transfers. Review PXI GPIB, Ethernet and VXI interfaces<\/a> for conventional external-instrument communication.<\/p>\r\n\r\n

Multichassis Expansion and Synchronization<\/h3>\r\n\r\n

MXI expansion allows one computer to access instruments installed across multiple supported chassis. This increases slot capacity but also creates additional PCIe switches, shared links and possible bandwidth bottlenecks. High-throughput modules should be distributed according to the available upstream bandwidth rather than only the number of empty slots.<\/p>\r\n\r\n

MXI connectivity does not by itself guarantee synchronized sampling or deterministic trigger alignment. Applications requiring phase-coherent acquisition must separately design the reference clock, sample clock, trigger and timing connections. Review compatible PXI synchronization modules<\/a> and chassis timing features.<\/p>\r\n\r\n

Software, BIOS and Startup Considerations<\/h3>\r\n\r\n

PXI Platform Services provides chassis identification and system-level support, while each instrument requires its applicable driver, such as NI-DAQmx, NI-SCOPE, NI-RFSA, NI-DCPower or NI-SWITCH. The MXI interface does not replace the drivers required by the measurement modules.<\/p>\r\n\r\n

The host computer must enumerate the complete remote PCIe hierarchy during startup. Depending on the system, the PXI chassis may need to be powered before the computer. If the chassis or instruments are missing, check:<\/p>\r\n\r\n