Use the nipxiconfig command-line utility to configure your PXI system in Linux and reserve/route PXI triggers. This utility is shipped with all NI drivers providing support for PXI(e) hardware in Linux Desktop.
Using nipxiconfig
In order to use nipxiconfig, ensure the following:
This is a simple example of configuring a PXIe System that consists of a PXIe-1065 chassis with a PXIe-8108 embedded controller connected via MXIe-x4 to a PXIe-1085 Chassis.
Below is the procedure to configure the above system.
In this example, the PXIe-1065 is referred to as Chassis 1 and PXIe-1085 is referred to as Chassis 2.
Note: PXI Express hardware will identify and display automatically. For certain older PXI products, the hardware must be manually identified. For instructions on doing this, use nipxiconfig --help to view the utility's help documentation.
Figure 2. Displaying system hardware using nipxiconfig in CentOS 7
Triggers need to be routed across the segments explicitly when using drivers that do not provide automatic routing. The nipxiconfig utility in Linux can be used to route triggers across segments. Below is an example of routing triggers for the PXIe-1085 chassis that was used in the above example. For more information on PXI timing and triggering, see Using PXI Timing and Triggering Functionality.
Figure 3. Trigger bus view using nipxiconfig on CentOS 7
For example, if you want to reserve PXI_Trig1 from Chassis 2, use the following command:
--reserve-trigger 2 1
Figure 4. Reserving PXI_Trig1 in chassis 2 using nipxiconfig on CentOS
For example, now that PXI_Trig1 is reserved, suppose you want to route it from segment 3 towards slot 1. At the same time, you will route PXI_Trig3 from the middle segment outwards. To do this, use the following commands:
--route-trigger 2 1 3
--route-trigger 2 3 2
Figure 5. Route PXI Triggers using nipxiconfig on CentOS 7