NI-TimeSync is 6 minutes ahead Windows clock

[mgulin]

Hi all,

I'm using NI-TimeSync 1.3.0 on my cRIO together with NI-TimeSync Plugin for Software-Based 1588 1.3.0

I've noticed that cRIO is synchronized on a clock that is 6 minutes ahead of Windows clock, as well as any other clock on the Internet. I have 3 cRIO devices, and same thing is happening on all of them.

Can someone please explain why is this happening and is it possible to fix it? Currently I'm using hardcoded subtraction of the timestamp by 360 seconds to match cRIO clock with Windows clock.

Best,

Marko.

[Queen_Nadine]

Hello mgulin,

It's typical for there to be some time drift on the cRIO clock.  However, 6 minutes does seem like a fairly large difference. The way that NI-TimeSync operates is that it selects one cRIO's clock to be the 'master clock' of your system. All other RT targets are then synchronized to that target's clock. However, this does not ensure that the master clock is synchronized to your Windows time.

For that reason, I would recommend implementing the Network Time Protocol (NTP).  A simple way to do this is detailed in the following KnowledgeBase article, How Do I Configure My CompactRIO Real-Time Controllers to Synchronize to SNTP Servers?: 

http://digital.ni.com/public.nsf/allkb/F2B057C72B537EA2862572D100646D43 

I hope this helps!

Regards,

[mgulin]

Hello Queen_Nadine,

Thank you for your answer. I understand now that PTP is only for time synchronization between devices that also have PTP implemented. I'm now trying to synchronize cRIO devices with server that runs Ubuntu Server. I tried both, NTP and PTP, however I have some issues with both of them. More detailed description of problems are here: http://forums.ni.com/t5/LabVIEW/Time-synchronization-using-SNTP/td-p/3052702

Thanks!

Best,

Marko.