A couple quick thoughts:
1. Double check that the routing is supported by your device. You can do this from MAX by selecting the device and then selecting the "Device Routes" tab at the bottom. Routes that are shown as "indirect" may require use of internal resources (often a counter/timer), and this could in turn cause a conflict with your DAQ needs.
2. I'm a little surprised at the lack of error, but I generally never use "Connect Terminals" for signal routing. "Connect Terminals" makes a more persistent routing that remains in place when tasks are done.
3. I use the DAQmx "Export Signal" vi and property node to make routes that persist only for the duration of the task that owns the signal in question. I'm not sure of my memory right now, but be aware that task-based routing might not produce an error until you attempt to start the task. I would have expected an immediate error from "Connect Terminals", but don't have experience to base that on.
-Kevin P
ALERT! LabVIEW's subscription-only policy came to an end (finally!). Unfortunately, pricing favors the captured and committed over new adopters -- so tread carefully.
