LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

One or more devices do not support multidevice tasks.

Solved!
Go to solution

Hi,

 

I'm working with 2 USB X series DAQs (USB 6356).  I am acquiring analog voltage data from all 8 channels on both DAQs (so 16 analog input channels total).  I need the data acquisition to be synchronized and to trigger from an external digital source (a signal that I currently have wired into PFI0 of Dev A).  I am using a sampling rate of 800 kHz, and a buffer size of 400 kS.

 

I have tried using  one express vi for both devices; two separate express vis for each device; and recently changed to the DAQmx icons (as pictured in the attachment).  Either way I get an error (error -201426: One or more devices do not support multidevice tasks.).  It then references DevA and DevB as the devices that don't support the tasks.  I was under the impression that multidevice tasks are okay with X series devices.  I am using NI DAQmx 9.5.5.

 

In the attached picture, I have left out most of the while loop.  The part of the diagram I left out is just for visualizing and saving the data, I have included the parts I felt necessary for describing my problem.

 

I would really appreciate any advice.

Thank you,

Leslie

0 Kudos
Message 1 of 7
(7,407 Views)

The multiple device might not be compatible with USB devices.  With PCI(e) you have the RTSI bus and with PXI(e) you have the PXI trigger/clock backplane.  DAQmx autoconfigures to use those.  I'm not sure it can do the same with USB.  Hopefully somebody inside of NI will shine some light on this.


GCentral
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines
"Not that we are sufficient in ourselves to claim anything as coming from us, but our sufficiency is from God" - 2 Corinthians 3:5
Message 2 of 7
(7,397 Views)
Solution
Accepted by topic author ldclaar

I think crossrulz is right. No worries though, while they have to be in separate tasks your data will still be synchronized as you want. You will just have to do a couple things in software, because not all the data will be returned in the same array of waveforms. What you can do is create two tasks (one for each device), build an array of tasks, and when you do a read, just do it inside a for loop. Concatenate the waveforms from each read and you will have an array of waveforms with all your data just as if you read it from a single task. You will also need to configure your second task to trigger of DevB/PFI0 and split your trigger wire, wiring it to PFI0 on each device.

Message 3 of 7
(7,386 Views)

Thank you both, for shedding some light on my setup and this error.  The information I was finding on the NI website did not seem to specify that USB Xseries devices were an exclusion to the statement made.

 

I have changed my program and built two separate tasks, which has eliminated the error 201426 message.  I have attached a picture of my newest program.  It is still not functioning, however no error messages are sent.  for(imstuck), I'm not sure what you mean by "build an array of tasks" or read inside a for loop.  We view the digitized signal from each channel (DevA ai0:7 and DevB ai0:7) separately anyway, so would concatenating the waveforms be necessary?  When I run the program and "highlight execution" the program seems to get stuck on the DAQmx read tasks, no errors, it just doesn't proceed or send the waveform data.  Am I missing something or is the for loop/concatenating the waveforms necessary?

 

Thanks again,

Leslie

0 Kudos
Message 4 of 7
(7,367 Views)

@ldclaar wrote:

  We view the digitized signal from each channel (DevA ai0:7 and DevB ai0:7) separately anyway, so would concatenating the waveforms be necessary?  When I run the program and "highlight execution" the program seems to get stuck on the DAQmx read tasks, no errors, it just doesn't proceed or send the waveform data. 

 

Thanks again,

Leslie


Nope, I just assumed since you were trying to read them all in one task that you wanted them grouped. Since your timeout is -1 and it's not returning, that implies that your start trigger isn't being seen by the devices. Are you sure you are getting a digital pulse on that line and that it's wired up correctly?

Message 5 of 7
(7,362 Views)

Thank you so much!  You were right, my trigger signal was being degraded and contaminated due to splitting the signal.  My program is up and running.  Thanks again!

 

0 Kudos
Message 6 of 7
(7,331 Views)

Glad you got it working.

0 Kudos
Message 7 of 7
(7,321 Views)