03-10-2011 05:56 PM
Hello one and all... I have a cDAQ operations question... I have a test stand built that has a cDAQ (9174 chassis) that started out with just a 9225 and 9239 that I'm using to gather power measurements (volts, amps, power factor, etc.)... and has functioned flawlessly for the last year or so. Along with that I've been running a Measurement Computing PMD-1208LS for gathering my analog signals as well as using one of the analog outputs for my motor signal... recently the 1208LS started flaking out, loosing connectivity, and finally started loosing channels.
So I just replaced that unit (1208LS) with a 9263 and a 9205 and just got it hooked up... thought it should be a relatively painless transition, AI is AI right? ..apparently not so much. I've ran DAQ Assistant and all the channels are correct, I have the hardware hooked up correctly and this thing runs like a dog or not at all... keep getting an error (50103). So obviously I have something set wrong, programmed poorly, or something. I've looked for a tutorial or some such with little to no luck... anyone have a link to one?
..and I have another question or two...
Will I have an issue using more than one DAQ Assistant VI to pull data from the cDAQ? I wouldn't think it'd be an issue, but maybe it is.
I also have DAQ Assistant VI's nested inside While Loops inside Case Structures... Not sure if this is a problem or not. Wasn't with the other hardware, but maybe there's too much overhead with the DAQ Assistant VI's... ??
I'm half tempted to pull all my data from a single DAQ Assistant VI and just parse it out to where it needs to go...
A point to some night time reading would be much appreciated!
Thanks!
Chad
03-11-2011 10:04 AM
Ok, I think I might have found my answer... according to the cDAQ user guide... "However, channels from a single module cannot be used in multiple tasks." I'm going to assume that each instance of DAQ Assistant is a "task"?? Am I correct in this assumption?
Thanks!
C
03-11-2011 03:05 PM
@chuggins143 wrote:
Ok, I think I might have found my answer... according to the cDAQ user guide... "However, channels from a single module cannot be used in multiple tasks." I'm going to assume that each instance of DAQ Assistant is a "task"?? Am I correct in this assumption?
Thanks!
C
yes, each DAQ Assistant is a task.
Each task instantiates its own timing system, and allowing one timing system to get samples from one channel on a cartridge and another timing system(another DAQ Assistant) to get samples from another channel on the same cartridge would cause nightmares 🙂
good luck with your app!!
-gaving