07-05-2013 12:09 PM
I configure 2 DAQS via USB hub at my desk (development PC) with all digital outputs, some open collector and some active using two DAQ Assistants, one for Daq1 and one for Daq2. I save the VI where they’re used.
I go into Max and rename Dev1 and Dev2 to 1875DAQ1 and 1875DAQ2 AND in attributes I associate their respective serial numbers, so they don’t get switched when plugged into another pc.
In Max I then Export settings to a file on our network.
I go to another PC and import these settings in MAX. Then connect the hub with the DAQs, and in Labview 2011 I open the VI and open the DAQ Assistant for each DAQ, and I get the error message shown below. Behind the error message I see the two tabs for Settings and Device. Device is where it shows the digital outputs as either OC or Active. When I click OK on the error message, the Device tab DISAPPEARS, so I can’t verify the configuration of my DAQ outputs as active or OC. Why am I getting this message?
Why can’t I view my DEVICE tab?
07-05-2013 12:16 PM - edited 07-05-2013 12:22 PM
Just select 'Details' and check the device and physical channel selected for each of these configured virtual channels (DigitalOut_1..DigitalOut_N) and compare it with, what is listed in MAX under 'Device and Interfaces'.... are they same??
07-05-2013 12:22 PM
Yeah, that's kinda a drag with importing MAX configurations and USB devices.
Unless there is a USB device of the right type MAX creates a simulated divice when importing the config and associates all the tasks with the simulated device. plug in the 6501 rename it and delete the simulated device. MAX will prompt you to retarget and tasks to the actual device but the tasks will still need a save since the device type changed from simulated to real.
07-05-2013 01:07 PM
Thank you moderator and Jeff. Moderator: Details shows me correct info on which channels I selected but it doesn't tell me their configuration - active or open collector. MAX shows the proper device names under Devices and Interfaces, but I cannot get any configuration or channel info from MAX.
Jeff, when I import the configuration, the proper DAQs ARE connected at that time, so it should find them and not have to create simulated device.
07-05-2013 11:40 PM
@hammer3 wrote:
Jeff, when I import the configuration, the proper DAQs ARE connected at that time, so it should find them and not have to create simulated device.
Yes, it "SHOULD"
NI Devmon could be improved.
AND , if you had paid attention during the MAX import you could have "Replaced" "Dev1" then
07-08-2013 05:48 AM
I DID pay attention and I DID replace Dev1 and Dev2 every time.
07-09-2013 12:11 PM
The code with the DAQ Assistant Express VI works properly on other computers. The only problem is I can't view the channel tasks nor CHANGE them from any pc other than the one I CREATED it on. Is this EXPECTED behavior of the 6501 DAQmx Assistant?
07-09-2013 12:23 PM
Ah, one of those.
You know for situations like this I prefer to avoid those Express vis and create the DAQmx Tasks as part of the LabVIEW project. Those Tasks are really just a few lines in a xml file somewhere. if that xml file has a *.lvproj extension they deploy just fine. On the other hand if you want to export and import those xml lines to MAX you need to save the Tasks in MAX then they export and import just like the lines that create the devices themselves.
Tasks, (Scales and channels too) need to be created once! Preferably, during development and not at run-time.
07-09-2013 01:02 PM
Thanks Jeff. I have a lot to learn about DAQmx.
07-09-2013 01:05 PM
@hammer3 wrote:
Thanks Jeff. I have a lot to learn about DAQmx.
Once you get the hang of it though it can't be beat! (You should have seen what data acquisition was like in the 90's! You wouldn't believe it!)