DAQMx - two counters, one inverse of the other

[cghuebner]

I've not tested so far if really a counter is used to do the inversion. I will try to use the 2nd counter on the 6210 to perform another task. Regarding the toggling of the inversion: For this first the terminals need to be disconnected and then reconnected. I did not find a property node for routes. There is one minor problem with my code: It still leaves the routed terminal sometimes in the high state after termination. Suggestions how to prevent this are welcome 🙂

Uppdate: My statement above is wrong, I just terminated the VI with the stop sign in the menu and not the stop button. With the stop button, it works as expected.

Christian

[cghuebner]

Seemingly, the route requires a counter. When trying to route with the other counter being used for a different task, I getan error:

Possible reason(s):

Specified inversion cannot be satisfied, because it requires resources that are currently in use by another route.

Source Device: Dev2
Source Terminal: PFI4
Destination Device: Dev2
Destination Terminal: PFI5

Required Resources in Use by
Task Name: _unnamedTask<1AD>
Source Device: Dev2
Source Terminal: 80MHzTimebase
Destination Device: Dev2
Destination Terminal: Ctr1Source

[cghuebner]

So it is really the inversion that needs a resource (counter). When I switch of inversion (just route the output), no error message and behaviour as expected. Is that documented somewhere?

NI hardware is cool

NI software is okay

NI documentation is a mess