Another problem with the 9172

[phonoX]

Hello,

I have another problem with my 9172 cDaq Chassis.

Until now I start my measurements by creating a task for each device (PCI, USB,PCMCIA etc.) including the needed channels.

The DAQmx allows me one task for each physical device.

I have now 3 different modules built in my 9172 chassis. My program (c++) starts a task for each module. This fails because I'm only allowed to start one task for the chassis including all modules with their channels.

To fix this problem I need to scan my system and check which module belongs to which chassis.

Does anybody know how to do this?

[KyleBryson]

Hi Karsten,

I'm not a C++ person, so hopefully someone can help out with the equivalent code, or you can figure out how to access these properties.  There are two DAQmx device properties that will give you the information from two perspectives--either a list of the modules in a particular chassis, or the chassis containing a particular module.  I've attached a LabVIEW screenshot using these two properties, which require you to write the Active Device property to select the device you're interested in first.  You should be able to use one or both of these properties for your application.

Please post if you are successful or if you have more questions.

Regards,
Kyle

[phonoX]

Sorry, I have no Labview installed on my machine but I found a function solving the problem:

DAQmxGetDevChassisModuleDevNames(

const char device[], char *data, uInt32 bufferSize);

I had an old version of the nidaqmx.h on my computer. After updating to the newest version I found the needed functionality for the 9172 chassis.

[fabianrol]

Hello,

Would you have the precise example using DAQmxGetDevChassisModuleDevNames ?

I am trying to do the same but I don't know what the property expect as constchar device[], char*data and uInt32 bufferSize

If you had more details on these entry that would be very helpfull

thank you

Best

Fabian