Synchronizing Waveform datataype timing properties with system clock for 24/7 applications.

[erwins]

When using the waveform datatype in my applications I noticed that the T0 field of this datatype is getting out of pace with the system clock of the machine of where it is running on.

The origin of this behaviour is that time synchronisation only takes place at the start of a measurement session after which waveform timestamps are derived from the measurement device's clock and not from the system's clock. Small differences in clock accuracy cause the clocks to run out of phase.

This effect is especially noticable on applications that are running 24/7 e.g monitoring Industrial continuous processes for weeks at a time.

When this happens and data is saved for analysis afterwards there could be problems synchronizing  this saved data with data of other sources because timestamps are different.

The only way to prevent this is stopping the task and starting it again but this is not always possible due to the nature of the processes monitored.

It would be very nice to have an option in the AIread function  that can automatically synchronizes waveform timestamps with the systemclock on a timely basis.

Funtionally this would be something I programmed in the attached VI.

[AristosQueue (NI)]

You have not attached a VI -- attachments are not possible within the Idea Exchange. Perhaps you can post it elsewhere and then provide a link here?

[RavensFan]

Which clock is the inaccurate one?  I would think the system Windows clock is less accurate than the timing clock of the DAQ device.  In which case there needs to be a way to fix the system clock, not the DAQ device clock.