11-23-2009 07:27 PM
I have 2 USB NI-9221 DAQ installed on one computer, and am trying to pin down which DAQ is getting assigned to each part of my program. I've set up one subvi to use Dev1 channel names and the other to use Dev2 channels, but when I run the compiled code on the target PC the DAQ channels assignments appear to be reversed! How do I pin them down? I've tried removing both devices in MAX and pluging them back in in different order, but they are still crossed up. I've tried swapping the channel names in LabVIEW but it's still going to the wrong ones.
Solved! Go to Solution.
11-23-2009 11:41 PM
You need to swap the device names in MAX...not in LabVIEW.
Unplug one device. Open MAX. Look at "devices and interfaces". Which one shows that the device is not plugged in?
Now you know. Now make some stickers which say "Dev1" and Dev2", and put them on the appropriate devices.
Now write your code accordingly. 🙂
11-24-2009 01:38 PM
scottmc,
Device names can change so I understand how you can be confused. My advice to you (in addition to what Diane recommended) is that when you click on a Device in MAX you should see an entry that lists the serial number of the device like: DDE595. You can then correlate this to the serial number of your specific device so that you know which one is which.
11-24-2009 03:08 PM
On a new machine with running Windows the first pluged in USB device will get Dev1 and the second will get Dev2.
In the case you plug in the USB devices while Windows is not running and you will start Windows the device which is found first will get Dev1. The sequence is the same as shown in the Device Manager >> USB Controllers. Hopefully you have a good documentation of the motherboard to find out which port is located where.
Just as background information why you will see the devices swaped.
And don't swap the devices before deleting them in MAX. Otherwise you will get Dev3 and Dev4.
01-08-2010 12:53 PM
I was able to get this worked out, thanks for the tips. I was able to change my fixturing around so that I was able to do my testing with a single DAQ, but the double DAQ tricks listed here did work.