Andrew Lindh writes:
Use an engineering command to set it to 16:
root engineering timing early_utc_leap 16
You can also set the TS2100 to add a leap second at the correct time:
root timing leap 1 07/01/2015 00:00:00
Tried that, but it seems that this setting stays only for a ongoing
hour.
Esa Heikkinen tn1ajb@... writes:
Robert Watzlavick kirjoitti:
I'm seeing the same thing with my TS-2100 - it is one second behind WWV
based on the front panel display. My ET-6000 appears to be in sync.
Ok - then this is verified...
So the only way (for me) is to run this with
and...@netplex.net said:
I have a nice set of TS2100 GPS Rubidium boxes as primary servers that
provide time and PPS to more current NTP servers. It's too bad the firmware
is so old and this bug won't be fixed.
If you are using ntpd, you can fudge the time by a second so ntpd will
I'm seeing the same thing with my TS-2100 - it is one second behind WWV
based on the front panel display. My ET-6000 appears to be in sync.
What's interesting though is that I have a little applet on my iPhone
(NetTime) that connects to nist.time.gov and it is also a second behind.
-Bob
Robert Watzlavick kirjoitti:
I'm seeing the same thing with my TS-2100 - it is one second behind WWV
based on the front panel display. My ET-6000 appears to be in sync.
Ok - then this is verified...
So the only way (for me) is to run this with 1PPS from Thunderbolt. Good
thing is that
Hi!
It seems that there's serious bug in Symmetricom Tymserve 2100 most
recent firmware (V4.1). When leap second pending flag was added to GPS
transmission (according to data shown by Lady Heather) the Tymserve's
time started to be exactly 1 second late from UTC!
Currently it claims that
