Error -50103 : How can I get the resource which is reserved

[fefe]

I get the error -50103 when I try to start two A0 task on two different channels. The error message tells me that "The specified resource is reserved".

But how can I known what is the specified resource. Is that a clock signal, a buffer or what else ?

More generally, how can I known the resources used by a task ? Is that a VI which can gives me all the resources used by a task?

Thank for your answer

Félix


Software : Labview 7, Driver : daqmx 7.3,
Board : PCI 6259 M serie

[leongchuan]

jus connect the error out of 1 AO to the error in of the other AO will do

[Dennis_Knutson]

The reserved resource is your DAQ board. You should not be using two separate simultaneous tasks for the same DAQ board. You should use a single task with two channels configured.

[fefe]

Hello Dennis,

I would like to generate continuously on two outputs. I compute in real time the output signals, but the two signals have not the same period (the sample rate in the same). So I compute the signal for one period of the first signal and put it in the buffer of the first task. I do the same for the second signal, but not at the same time because the periods of the two signals are different.

If I use only one task, I have two write the some amount of data for the two channels in the buffer every time. So I have to use an intermediate buffer, which is much more complicated: Is that an other solution (write in the buffer channel after channel ... ?)

Thank for the answer

Felix

[Poormanphysics]

Hello:

I'm trying out a shipped example called PID-Control Multichannel VI and I'm getting the same error? How can NI shipped it with this problem? Anyway what should be the remedy here?

Thanks,

Berns

[Tom_W_[DE]]

Hi Berns-

Please see my response here.

Thanks-

[tspj20]

Hi,

I want the daq board to output two analogue continuous waveforms which have a know phase difference between each other. This should be the only difference. How can I configure the two channels using the same task, to prevent the 50103 error from occuring?

Thanks,

Talini