You should only use connect signal functions for debugging purposes. You should only use "Export Signal" for exporting signals outside of the DAQmx domain (i.e. to devices that are not supported under DAQmx). DAQmx provides powerful routing capabilities, but as soon as you export the signal outside of the DAQmx domain, the driver can no longer provide you with error checking to see if you've routed things correctly, or if your route is valid. For a visual display of valid routes, click on the routing tab in MAX to view all possible routes available on one device.
If you are routing between two devices and need to synchronize them, for example, having them share a master timebase, you would want to do something like the following:
DAQmxSetSampClkTimebaseSrc(TaskHandle slaveTaskHandle,
DAQmxGetSampClkTimebaseSrc(TaskHandle masterTaskHandle,
char *data,
uInt32 bufferSize););
DAQmxSetSampClkTimebaseRate(TaskHandle slaveTaskHandle,
DAQmxGetSampClkTimebaseRate(TaskHandle masterTaskHandle,
float64 *data););
This would set the slave tasks master timebase rate and source to be the same as the master task. DAQmx will then handle complex routing without you having to worry about routing anything directly to RTSI cables. As the above post mentions, since you configured you're cable in MAX, DAQmx has all the information it needs about how to route these signals between the devices.