LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Error -200022 on NI-9401 with DIO and Clock Task

Solved!
Go to solution

Could someone kindly look at this VI and explain how I can resolve getting the reserved task error of - 200022? The VI sets up a clock task to monitor motor steps and another task to monitor inputs from the motor on the NI-9401. There has to be a way to do both tasks together I would hope somehow without this reserve error showing up. If not, how would I manage to do this differently?

 

Thanks.

0 Kudos
Message 1 of 8
(3,252 Views)

BTW, the NI-9401 is being used in slot 3 of the NI-9188. I hope this helps to answer my problem. Thanks again for any help. 

0 Kudos
Message 2 of 8
(3,248 Views)

Is this question really that difficult that no one knows how to resolve it?

0 Kudos
Message 3 of 8
(3,218 Views)

You are getting that error message because you are accesing the same resource for two different tasks.

error -200022

 

To run your VI there is needed the emaxState.ctl. I got broken arrow. 

 

Regards

0 Kudos
Message 4 of 8
(3,195 Views)

Thanks. Yes I realize what the error is, but need to know how to resolve it. I'm currently using cnt1 and inputs 4-7 on the 9401. Would moving the counter down to cnt0 and leaving the other inputs I need on lines 5-7 solve the problem since they would be on difffernt nibbles of that port or would this still throw the reserved error? I attached the missing .ctl file so you can run the VI and maybe help me reconfigure the port setup so I can have a counter with inputs I can monitor on this module.

 

Thanks so much.

0 Kudos
Message 5 of 8
(3,187 Views)
Solution
Accepted by QRP

-          When I ran the VI I got error -200463. I could solve that issue changing in the DAQmx create channel the input line grouping to one channel for each line.

-          Then I ran the VI and I got error -200022. So as workaround you need to change the counter (ctr0) if you are using 4, 5, 6 and 7 as digital lines. However if you make that change you are going to get error -201133. Check the link below to solve that issue:

-          Error -201133

 

Regards

Message 6 of 8
(3,182 Views)

Here the link for error -201133:

Error -201133

 

Message 7 of 8
(3,178 Views)

Thanks. I wondered if using the counter task on the same nibble of the port as the input line task would cause a conflict. I actually moved my inputs up to Line0-2 and left my PWM line on Line 4 keeping the counter at cnt1. I reserved the counter task, then started the input line task for lines0-3 then started the counter task and it all worked! Thanks again for the heads up on the 201133 error too.

 

Thanks again.

 

0 Kudos
Message 8 of 8
(3,173 Views)