[time-nuts] A Leap Second is coming

Tom Van Baak tvb at LeapSecond.com
Thu Dec 29 19:25:44 EST 2016

Hi Paul,

The Arcron Zeit was one of the early favorites for precise timing. There were a couple other WWVB receivers at the time but IIRC none were as interesting, inexpensive, or hacker friendly as the Arcron. Not sure what model you have (contact me off-list).

Here's a capture of a leap second by an Arcron Zeit. Via usenet (after email and the web, but before google and time-nuts, were invented):



----- Original Message ----- 
From: "Paul Alfille" <paul.alfille at gmail.com>
To: <time at patoka.org>; "Discussion of precise time and frequency measurement" <time-nuts at febo.com>
Sent: Thursday, December 29, 2016 3:48 PM
Subject: Re: [time-nuts] A Leap Second is coming

> Is there a way in LH to test a clock against accurate internew time
> (accurate to .5 seconds I guess)?
> I have the Arcron WWVB clock that is newly supported in LH and I'd like to
> see when the leap second correction is made.
> On Thu, Dec 29, 2016 at 9:11 AM, Vlad <time at patoka.org> wrote:
>>> Some tools here, to see which NTP servers are announcing the event:
>>>  http://www.satsignal.eu/software/net.htm#NTPLeapTrace
>> For those who using Linux, the following shell command verifies that the
>> current 'timezone' file contains leap seconds and can be used with this
>> directive
>> # TZ=right/UTC date -d 'Dec 31 2016 23:59:60'
>> Ideally, it MUST return "Sat Dec 31 23:59:60 UTC 2016". If 'timezone' file
>> is not ready, the output will be "date: invalid date"
>> My TBolt shows me the message that "LeapSeconf event pending". So, if I
>> understand it right, I should see see it on LH 5.0 screen somehow.
>> My lab NTP suppose to start slow down its clock 12 second before the event
>> to match the time.
>> Also I'll collecting the 'main' cycles to see what will happens during the
>> 'jump'.
>> --
>> WBW,
>> V.P.

More information about the time-nuts mailing list