How programmatically reset the NI DAQmx

[Prashobh]

Hi,

My data acquisition application needs a set of two USB-5132 DAQ cards for simultaneous 4 channel data acquisition. I have around 20 of these DAQ cards for the field application purposes. By default I have configured the DAQ cards are Dev1 and Dev2 in my LabVIEW program and which is working fine. But when I remove the first two DAQ cards and  connect different NI USB-5132 DAQ cards to the same PC, my program doesn’t acquire the data, as the system is taking these DAQ’s are Dev 3 and 4. This problem can be solved by manually resetting the “NI DAQmx Configuration” and changing  the name of Dev 3 and 4 to Dev1 and Dev2 in the Automation Explorer >> Devices and Interfaces window. But I would like to make these changes programmatically through LabVIEW rather than changing the devices names manually in MAX. Does anyone know a method of allocating device names through Labview ( ver8.2) ? In short I want any DAQ device connected to the system to default to ‘Dev1’ followed by ‘Dev2’ (if second one is connected).

Thanks in advance,

Prashobh.

[Albert.Geven]

Another approach is to check which devices are available and use these devicenumbers.

[Prashobh]

Dear Albert Geven,  

Thanks for your reply. There is an option to "Reset the NI DAQmx Configuration" in the Measurement & Automation Explorer (Automation Explorer >> Tools >> NI-DAQmx Configuration >> Reset NI-DAQmx Configuration). If possible could you please send me the equivalent LabVIEW coding for resetting the NI-DAQmx Configuration.

Regards,

Prashobhkumar.

[Albert.Geven]

I don't know how to call this function in MAX.

But as I said in my other post you can check which devices are available to LabVIEW and use an available device.

This is all I can show you

Device Names Property

Short Name: DevNames

Property of DAQmx System

Indicates the names of all devices installed in the system.

Remarks

The following table lists the characteristics of this property.

Permissions	read only
Resettable	no
Settable while task is running	device-specific
Available in Run-Time Engine	yes