This bug has been fixed in Release 14 Service Pack 3 (R14SP3). For previous product releases, read below for any possible workarounds:
We have verified this as a bug in the Data Acquisition Toolbox 2.5.1 (R14SP1) in the way the engine works with an external clock. When working with an external clock, the engine sometimes makes errors in determining when a particular hardware trigger took place.
When a device is operating with external clocking, it is hard for the software to determine when a trigger or a sample occurred. The toolbox uses the SampleRate property to estimate when a sample or trigger occurred. To work around this issue, set the SampleRate property to a value equal or greater than the external clock rate.
Best Answer