PXI-6682 shows in MAX, but not in DAQmx

[Sebastien Dupere]

Hi,

I recently got a new chassis with some few cards and I am fairly new to everything NI related.

In any case, I also had a new PC (since they asked me to start from scratch)

So I installed the following:

1. NI-Daqmx 9.0
2. NI-Sync 3.1
3. MAX 4.6.1f0

Afterward I plugged my chassis and got all my cards to register automaticly...except for the PXI-6682.

Afterward, I browsed to find the driver myself (in the NI-Sync installer) and that worked. MAX is now able to test it, read it and all that.

Now the problem is I need to know at run time in my C program if the device is there or not...

To achieve this effect, I used this:DAQmxGetSysDevNames

It returned every device except the PXI-6682.

I can "cheat death" by using the name provided in MAX ("Dev11") and use my NI-Sync calls this way...but this is terribly static.

Is there any plausible reasons why a call DAQmx would not recognized a device?

Hints:

1. http://forums.ni.com/ni/board/message?board.id=80&message.id=1257 : Did not give a solution really
2. The driver seems weird...the name in "Device Manager" is "NI PXI-6682" instead of "PXI-6682"
3. If I call DAQmxGetDevProductCategory it returns DAQmx_Val_Unknown (So it knows the device is plugged...but it can't read it
4. My calls NI-Sync are able to control the PXI-6682 just fine

Thank you in advance for any help,

Sebastien Dupere

Message Edited by Sebastien Dupere on 10-26-2009 03:17 PM

Message Edited by Sebastien Dupere on 10-26-2009 03:18 PM

Message Edited by Sebastien Dupere on 10-26-2009 03:19 PM

[Seth_B. · Accepted solution]

Hello Sebastien,

The NI PXI-6682 does not show up as an NI-DAQmx device because it is not controlled by the NI-DAQmx driver.  Instead, all commands and communication are through the NI-SYNC driver.  The NI-DAQmx function "DAQmxGetSysDevNames" only returns the names of devices that can be controlled by the DAQmx driver.  Function calls to and from this device will go through NI-SYNC.  I'm not as familiar with that driver (I work with DAQmx) but they may have a function for returning device names similar to DAQmx's.

(Incidently, in the forum post you linked, the device was a DMM which is controlled by the NI-DMM driver and the above explanation applies for it too.)

Regards,