NI does not actively maintain this document.
This content provides support for older products and technology, so you may notice outdated links or obsolete information about operating systems or other relevant products.
In a PXI system, the PXISYS.INI file provides mappings from PCI logical addresses (PCI bus, device, and function numbers) to corresponding PXI slot numbers, allowing device driver software to identify the slot of a PXI module. There is a unique PXISYS.INI file for every combination of PXI chassis and controller and the following instructions will describe how to install the correct PXISYS.INI file using legacy versions of Measurement & Automation Explorer (MAX).
In legacy versions of MAX, you will always find a PXI System entry under "Devices and Interfaces". If you are using a PXI system, it is necessary to always configure the PXI System entry correctly so that MAX saves the appropriate PXISYS.INI file under the Windows system folder.
If you do not have a PXI system you do not need to configure this entry.
The steps required for configuring any PXI System entry are the same, regardless of if you are using an embedded controller or a remote controller (i.e. MXI-4). To configure the PXI System entry follow these steps:
If you have a PXI Combo chassis (PXI-1010 or PXI-1011), or if you are using LabVIEW RT, please refer to the FAQ section.
For more information on configuring your PXI system, please go the Help menu in MAX and open the Measurement & Automation Explorer Help for PXI by navigating to Help Topics»PXI. You will find more information under the entry "PXI System Configuration".
The format of the PXISYS.INI and CHASSIS.INI files are outlined in the PXI Specification. For additional information on the PXI Specification, visit the webpage for the PXI Systems Alliance.
The PXI specification allows many configurations of PXI chassis and system modules. To assist system integrators, the manufacturers of PXI chassis and system modules must document the capabilities of their products. The minimum documentation requirements are contained in .ini files, which consist of ASCII text.
The CHASSIS.INI file describes the capability and features of the chassis and chassis manufacturers are required to provide this file. However, in order to describe the capabilities and structure of the PXI system, the architecture of the system's controller must also be described. The information in the CHASSIS.INI file is combined with information about the system controller into a single system initialization file, PXISYS.INI (PXI System Initialization). There is a unique PXISYS.INI file for every combination of PXI chassis and controller.
The system controller manufacturer will either provide a PXISYS.INI file for the particular chassis model that contains the system controller, or provide a utility that can read an arbitrary CHASSIS.INI file and generate the corresponding PXISYS.INI file.
Every NI PXI chassis ships with a DVD that contains the corresponding CHASSIS.INI file. If an NI PXI controller is also being used, the PXISYS.INI files for every combination of controller and chassis are available on the web here, in which case the user should not need to use the CHASSIS.INI file.
The .ini files can be read by the system integrator, and can also be used by configuration utilities and device drivers. Device drivers and other utility software will read the PXISYS.INI file to determine information about the system. The device drivers should have no need to directly read the CHASSIS.INI file. For example, the PXISYS.INI file can be used by driver software to identify that Slot 8 of a PXI-1010 chassis can be used to interface to an SCXI backplane. Additionally, the PXISYS.INI files provides mappings from PCI logical addresses (PCI bus, device, and function numbers) to corresponding PXI slot numbers, allowing device driver software to identify the slot of a PXI module.
For information about installing the PXISYS.INI file, see the Configuring the PXI System in MAX section.