Error-50103 occurred at DAQmx Start Task.vi:2

[Stone1234]

Hello, everyone,

 

I am a new user of labview.

I have a simple question here.

 

The card I am using is BNC-2120

 

The purpose of my code is:

(1)   wait for a trigger signal (AI2) (First part in the above flat sequence)

(2)   after it is triggered, wait for about 5 seconds, then give a pulse signal (AO0) to a switch (Later parts in the above flat sequence)

(3)   During the total procedure (waiting part and afterwards), record the signal (AI0) (the bottom for loop, looks strange, but it works ok for my system.)

 

It works OK sometimes.

But it often indicates an error when I try to run it. The information about the error is:

 

“Error-50103 occurred at DAQmx Start Task.vi:2

 

Possible reason(s):

The specified resource is reserved. The operation could not be completed as specified.

Task Name:_unnamedTask<180>”

 

I think the problem is probably from the trigger part. But I can not fix it.

 

Could anybody help me?

 

Thank you very very much!

  

Stone1234

[RavensFan · Accepted solution]

Which DAQ card are you using?  The BNC-2120 is not a card but just a connector block.

The problem is that you are trying to do two different analog input reads using two different acquisition rates using the same sample clock.  So one clock VI or the other is probably giving the error message because the other one has already reserved it.

You will need to come up with a common sample clock rate and create a task that contains both channels you want to acquire from.  Then you can either decimate your data as needed and perform calculations.   Once your trigger condition is met on the one channel, then you can initiate another parallel loop (perhaps using a notifier) to do your analog outputs.

[MattBradley]

One additional thought: Make sure you free up any resources when you are done (use the DAQmx Clear Task).

[Stone1234]

Sorry, The card is PCI-6221. 😛

Thank you for your good suggestions.

The problem has been fixed.

[Stone1234]

Thank Ravens Fan and MattBradley.

The problem has been fixed following your suggestions!

I really appreciate your help.