07-20-2016 08:02 PM
I have a cDAQ-9174 that I am trying to configure to use DO and DI at the same time in two different tasks. It gives me the following error -89137:
Possible reason(s):
Specified route cannot be satisfied, because it requires resources that are currently in use by another route.
Source Device: cDAQ1
Source Terminal: do/SampleClock
Destination Device: cDAQ1
Destination Terminal: Slot1/ConvertPulse
Required Resources in Use by
Task Name: _unnamedTask<32>
Source Device: cDAQ1
Source Terminal: di/SampleClock
Destination Device: cDAQ1
Destination Terminal: Slot1/ConvertPulse
Task Name: _unnamedTask<33>
I understand that this is because some route is in use, but I'm not sure what that means. I tried to reference the device routes in MAX, but I don't really understand it. I attached my code. You can see I want to read and write at the same time, which I feel should be a pretty straightforward thing to do. I found a note on NI's site about setting the clocks with the timing property node. I tried to do that, but I couldn't get it to work anyway.
Can anyone tell me how I can use DI and DO tasks on the same cDAQ at the same time?
Solved! Go to Solution.
07-20-2016 10:44 PM
Hi Jo-Jo,
As I understand, cDAQ-9174 is just a chasis, it does not perform Digital I/O by itself, you must have digital I/O device to perform your task instead of only using a chasis.
I also take a look into your VI, as I can see, I'm not sure about your intention to put the DAQmx Create Task at the first place. Furthermore, I also wonder some points:
In conclusion, as you stated in the post, I understand that you only have the cDAQ 9174, which is only a chasis, not a DAQ device hence you could not perform any Dataacquisition from the chasis itself. Before you really get into the programming part, I suggest you to use NI-MAX to perform Test Panel function to observe the functionality and behaviours of your device before writing a code for them.
Valjean.V
07-28-2016 07:53 PM
I figured out I can't do hardware timed reads at the same time I do hardware timed writes with this module, so that was the problem.