Solution
In DAQmx-enabled CompactRIO controllers like cRIO 904X or 905X, each slot has it's own timing engine. For example if you are using cRIO-9049, you use 8 different timing engines thus potentially creating 8 different tasks that have an individual timing source. Therefore, to configure the right timing source, select it<n> for clock sharing instead of ai/SampleClock.
Refer the following table for the timing engine nomenclature.
| 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 an analog input module in slot0 of cRIO1 and want to share this sampling clock with the other tasks, you will select /cRIO1/it0/SampleClock as source of DAQmx Timing.vi in the other tasks.