What driver do I need to configure a PXI-1045 chassis in NI Max?

[barrydahlin]

I have a system with a MXI-4 and PXI-1045 chassis.  On a separate PC I'm trying to set up NI-MAX to simulate the hardware resources so I can work on the software.  When I identify the PXI System chassis 1 as a PXI-1045 I get a warning:  "This chassis has been identified but is not described in the pxisys.ini for this system."  What do I need to do to correct this warning?

[Mr.F]

Hi Barry,

The driver for PXI identification etc. is PXI platform services and that is installed with DAQmx. Do you have any hardware on this other machine or are you trying to simulate some hardware in a PXI 1045 chassis that not present?

[barrydahlin]

I'm trying to simulate hardware in a PXI-1045 chassis.

[barrydahlin]

I should have added the chassis is not present and the simulated devices seem to be working fine but I'm not sure what will happen when I put the code on the test set with the 1045 chassis

[Mr.F]

Hi Barry,

How are you simulating a PXI 1045 chassis? Are you identifying one of your PXI busses as a PXI chassis?

[barrydahlin]

Hi,

In NI MAX under PXI System I identify the chassis as a PXI-1045.  If I identify it as a PXI -1042 the Chassis Status shows "This chassis is properly configured.".  The chassis also is displayed under Devices and Interfaces with the simulated boards in the chassis. Identified as a PXI-1045 only the simulated boards are under Devices and Interfaces.

[Mr.F · Accepted solution]

Hi Barry,

I take it that you are indeed identifying one of your PXI busses as a PXI chassis, in order to make it appear that the chassis is actually in your system. This is forcing MAX to look at PXI bus and consider it a PXI chassis. This does not err for the PXI 1042 but does with the PXI 1045 due to hardware differences between the two, namely the PXI 1045 is a multi segment chassis where as the PXI 1042 is a single segment. Unfortunately, there isn’t a way to simulate a PXI chassis; this currently is not a feature in MAX, the method you are using is an unsupported procedure.

Either way, simulated devices cannot make use of advanced timing abilities like sharing triggers and clocks via the PXI trigger lines. Your best bet is to name your devices accordingly on your development machine so that you reference the right devices when you move to the actual hardware. Pay attention to routes that involve signals to or from PXI trigger lines and if you have any devices that need the PXI system timing slot’s special routing abilities.