Solution
In cRIO DAQmx program, you should select it<n> for clock sharing instead of ai/SampleClock.
In cRIO 904X or 905X, each slot has different timing engine. For example if you are using cRIO9049, you can use 8 different timing engines thus you can create 8 different tasks which have individual timing source. See the following table for each timing engine name.
| Samp TimingEngine Value | Analog Input, Digital Input, and NI 9361 Timing Engine Used | Analog Output and Digital Output Timing Engine Used |
|---|
| 0 | it0 | ot0 |
| 1 | it1 | ot1 |
| 2 | it2 | ot2 |
| 3 | it3 | ot3 |
| 4 | it4 | ot4 |
| 5 | it5 | ot5 |
| 6 | it6 | ot6 |
| 7 | it7 | ot7 |
For example. if you have analog input module in slot0 of cRIO1 and want to share this sampling clock with the other tasks, you should select
/cRIO1/it0/SampleClock for source of
DAQmx Timing.vi in the other tasks.
Please refer to the
DAQmx help CompactRIO Timing Engines topic for more information.