6133 card don't sample with external clock

[Kyle_A.]

Hi Barak,

I feel the best next step to troubleshoot this issue is to upgrade the driver to a newer version, or as a last resort revert back to your last known good configuration to see if we can eliminate issues that may come up with the driver.  The most recent version of DAQmx to date is 9.2.1.  Since there is no solid way to reproduce this issue I cannot determine if it should be filed as a bug or not.  Let me know if you are able to upgrade/downgrade driver software for troubleshooting.

[barak]

Hi,

Thanks for your replay.

I already got the daq mx cd and will upgrade next week.

Any Idea what can cause the A/D on the card to respond with timeout but all other HW works OK(Digital I/O and Counters).

[Kyle_A.]

Hi barak,

The DIO on the card is software timed, and does not require a sample clock for its operation.  The counters run off an internal timebase by default, and if a sample clock is used then it becomes a buffered operation which takes some setup.  The AI/AO engines are sample clock driven whether it be a divide down of the internal on board clock or an external sample clock from a counter/other source.  Let me know how the driver upgrade goes, thank you!

[Yuheng]

Hi:

I experience the same problem by using ctr0 as external clock. I trigger the counter with analog start trigger make it retriggerable so that the analog input is retriggerable. However, under some circumstance we can get any data from 6133, but not always. The only way to return to normal is to reset the device in Max. Barak have you finally solve the problem by updating the DAQmx?

[barak]

Hi,

I updated the driver but I can't tell if it solved the problem.

This error is randomly accoure and we had less activity in this specific benth.

I saw that reseting the device (In max) solve the problem so i inserted into my software a device reset before any sampling.

[Yuheng]

Hi Barak:

It seems I found the reason. When you re-route the clock of ADC, say using 'Ctr0InternalOutput', you need to start the ADC by calling the 'DAQmx Start Task ' before star the counter, and clear the counter by 'DAQmx Clear Task' BEFORE clear the ADC. Please refer to the example: Mult-Function-Ctr Retrigg Pulse Train Generation for AI Sample Clock.vi under 'Hardware Input and Output->DAQmx->Synchronization->Multi-Function'.

After I did so I haven't seen any similar error so far. Hopefully this is the solution. Good luck. Please post the update if you solve the problem. Thanks

Yuheng

[Jonathan_S1]

This definitely sounds like a viable solution.  Any time you are using multiple tasks where a sample clock is being shared in some way, it is important to make sure that the "slave" task is started before the "master" task.  In this case, your counter task is the master task.

Jon S