PXI

cancel
Showing results for 
Search instead for 
Did you mean: 

Auto detection of PXI devices

Solved!
Go to solution

Hi,

 

we run some PXI systems connected to PCs and sometimes the cards are swapped. Now I would like to write an application (Monitor temperatures, self calibration, calibration, SN) for all systems and need an auto detection of all cards in the system.

 

Problem: The solutions provided with the DAQmx system - devices property don't seem to work (empty) if you (only) have scope/fgen/sync devices.

If I place a IVI device control on the frontpanel  without filter I have all devices in the pull down, but can't find a property to resolve that pull down to devices....

VISA will find the PXI backplane 😕

Modular instruments ??

Read the configuration from MAX file?

 

 

 

Greetings from Germany
Henrik

LV since v3.1

“ground” is a convenient fantasy

'˙˙˙˙uıɐƃɐ lɐıp puɐ °06 ǝuoɥd ɹnoʎ uɹnʇ ǝsɐǝld 'ʎɹɐuıƃɐɯı sı pǝlɐıp ǝʌɐɥ noʎ ɹǝqɯnu ǝɥʇ'


0 Kudos
Message 1 of 6
(4,268 Views)

Hey Henrik,

 

could you please specify the PXI controller and the modules you have. There should be differences in the functionality between different modules.

 

 

Best regards

 

Thomas

Message 2 of 6
(4,228 Views)

 

Thank you Thomas for the reply, will pass all Labs to have a look.

All are external PC controlled mostly via MXI(?) fiber. And the cards  6652 , 5422, 5922,5900,5124, 6251 ...  

DAQmx, Scope, FGEN  and who knows what the future brings?

 

MAX can find them, so how to ask MAX with LabVIEW to get the answer what is in the rack?

 

Greetings from Germany
Henrik

LV since v3.1

“ground” is a convenient fantasy

'˙˙˙˙uıɐƃɐ lɐıp puɐ °06 ǝuoɥd ɹnoʎ uɹnʇ ǝsɐǝld 'ʎɹɐuıƃɐɯı sı pǝlɐıp ǝʌɐɥ noʎ ɹǝqɯnu ǝɥʇ'


0 Kudos
Message 3 of 6
(4,223 Views)

Here we go

Chassis 1045Q, 1062Q

MXI:8336, 8375

Modules

5124

5402

5404

5406

5421

5422

5900

5922

6251

6602

6652

6672

Mostly PXI, some PXIe

Might be some DSO or FPGA will follow.....

(And that is one Lab... If you have access to the NI customer database lookup PTB 😉  and some colleagues signaling interest in this software ..)

 

Greetings from Germany
Henrik

LV since v3.1

“ground” is a convenient fantasy

'˙˙˙˙uıɐƃɐ lɐıp puɐ °06 ǝuoɥd ɹnoʎ uɹnʇ ǝsɐǝld 'ʎɹɐuıƃɐɯı sı pǝlɐıp ǝʌɐɥ noʎ ɹǝqɯnu ǝɥʇ'


0 Kudos
Message 4 of 6
(4,211 Views)
Solution
Accepted by topic author Henrik_Volkers

Hello Henrik,

 

The way MAX handles these is via the associated drivers for the device.  However, there is an underlying layer that can detect most if not all NI devices.  This has been abstracted into the NI System Configuration driver.  You can use the NI System Configuration driver to detect devices that are present in the system and get basic things like serial number, current temperature, calibration dates, self-calibrate, self-test, etc.  I believe these functions apply to all devices, but I'm not certain.

 

The NI System Configuration API Help is here that can help get you started.

 

 

 

Seth B.
Principal Test Engineer | National Instruments
Certified LabVIEW Architect
Certified TestStand Architect
Message 5 of 6
(4,206 Views)

Thank you Seth,

 

That looks very promising. As soon as I have access to the equipment I'll give it a try :).

 

(Will mark it as solution after test 😉 )

Greetings from Germany
Henrik

LV since v3.1

“ground” is a convenient fantasy

'˙˙˙˙uıɐƃɐ lɐıp puɐ °06 ǝuoɥd ɹnoʎ uɹnʇ ǝsɐǝld 'ʎɹɐuıƃɐɯı sı pǝlɐıp ǝʌɐɥ noʎ ɹǝqɯnu ǝɥʇ'


0 Kudos
Message 6 of 6
(4,187 Views)