Multifunction DAQ

cancel
Showing results for 
Search instead for 
Did you mean: 

AO buffering problems

Solved!
Go to solution

As an alternative for future readers, below's a snippet of how I tend to prefer to do these things.  My method routes the signal within a task context.  When the task is cleared, the routing will not persist to cause mischief for other tasks.  The method shown previously using "Connect Terminals" routes the signal within a device context.  The routing *can* (and often does) persist after tasks are created and cleared.

 

Just an FYI, each method has its merits, I just have found that I usually prefer the task context with auto-cleanup.

 

 

-Kevin P

 

ao pause trigger.png

Message 11 of 11
(421 Views)