Leap second...

147 views
Skip to first unread message

Nick

unread,
Dec 30, 2016, 10:35:10 PM12/30/16
to neonixie-l
A chance to record 23:59:60 on your nixie clock this New Year's Eve as a leap second is being added - only the 27th ever...

Nick

Terry S

unread,
Dec 31, 2016, 10:03:20 AM12/31/16
to neonixie-l
I wonder how my WWVB based clocks will handle that? Might have to stay up and watch.

Terry

Jon D.

unread,
Dec 31, 2016, 10:05:52 AM12/31/16
to neonixie-l
Does anyone know how the MOD-SIX_7971 will display this extra second?

Jon

H. Carl Ott

unread,
Dec 31, 2016, 10:41:47 AM12/31/16
to neoni...@googlegroups.com
I'm not 100% sure, and I wrote the code. lol,

But really. 

We convert the time info in the GPS NMEA sentence to a 32 bit elapsed seconds count from an epoch date. This is what gets transmitted via the RPTR radio link.  

So.  
Dec 31,  23:59:60
Jan   1,  00:00:00

Should both display the same (as Jan 1  00:00:00).

 If you have any transition effects that run at the top on the minute they will start as usual and then exit with the correct time showing. You should also get a  "SYNCED" message as the clock readjusts its internal RTC to match the received GPS time.  

But if the GPS module itself gets confused, who knows what'll happen. Could be fun to watch.   

carl
--------------------------------------------------------
Henry Carl Ott   N2RVQ    hcar...@gmail.com

On Sat, Dec 31, 2016 at 10:05 AM, Jon D. <jond...@gmail.com> wrote:
Does anyone know how the MOD-SIX_7971 will display this extra second?

Jon

--
You received this message because you are subscribed to the Google Groups "neonixie-l" group.
To unsubscribe from this group and stop receiving emails from it, send an email to neonixie-l+unsubscribe@googlegroups.com.
To post to this group, send email to neoni...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/neonixie-l/4aa7009f-a8f9-4386-a823-18f69cc27e37%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

Nicholas Stock

unread,
Dec 31, 2016, 10:48:57 AM12/31/16
to neoni...@googlegroups.com
Y2K all over again!! 

If I can stay up I'll try and keep an eye on mine.....

Happy New Year Folks!

Scott McInness

unread,
Dec 31, 2016, 11:11:17 AM12/31/16
to neoni...@googlegroups.com

The most recent leap second was inserted on 30 June 2015 at 23:59:60 UTC, so whatever happened 18 months should happen again this time. Note that the leap second is inserted at 23:59:60 UTC, so your local time zone will affect when you actually see the leap second – it’s about eight hours away.

 

Have a read of https://en.wikipedia.org/wiki/Leap_second if you want to know more about why.

To unsubscribe from this group and stop receiving emails from it, send an email to neonixie-l+...@googlegroups.com.


For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "neonixie-l" group.

To unsubscribe from this group and stop receiving emails from it, send an email to neonixie-l+...@googlegroups.com.


To post to this group, send email to neoni...@googlegroups.com.

 

--

You received this message because you are subscribed to the Google Groups "neonixie-l" group.

To unsubscribe from this group and stop receiving emails from it, send an email to neonixie-l+...@googlegroups.com.


To post to this group, send email to neoni...@googlegroups.com.

Terry S

unread,
Dec 31, 2016, 11:22:17 AM12/31/16
to neonixie-l

Tom Van Baak

unread,
Jan 1, 2017, 11:23:26 AM1/1/17
to neoni...@googlegroups.com
> From: "'Terry S' via neonixie-l" <neoni...@googlegroups.com>
> Date: December 31, 2016 at 8:22:17 AM PST
>
> Interesting read: http://www.leapsecond.com/notes/leap-watch.htm
>
> Terry

See also:

http://www.leapsecond.com/pages/CD47/

/tvb

Terry S

unread,
Jan 3, 2017, 12:34:02 PM1/3/17
to neonixie-l
Ok, I'll admit I tried to spot the lead-second. It didn't work.

My WWVB based nixie clock isn't even capable of displaying "60" in the seconds field, so I knew that clock wouldn't show it. However, right next to it I keep an Oregon Scientific WWVB clock. That clock didn't show the leap second, either.

And of course, my Nixichron went into it's hourly display of location and temperature at the top of the hour. Never saw the leap second there, either.

I'm not sure when or if my WWVB clocks synced up correctly.... I'll have to check that this evening.

Fail.

Terry

David Forbes

unread,
Jan 3, 2017, 2:35:25 PM1/3/17
to neoni...@googlegroups.com
Terry,

I knew that none of my clocks that I made would do anything interesting with it,
since none of them have calendars, so I watched the time.gov clock page and shot
a short phone video of the leap second happening. It's a bit weird to watch.

I did have to adjust my rubidium Nixie clock after the event.

On 1/3/2017 10:34 AM, 'Terry S' via neonixie-l wrote:
> Ok, I'll admit I tried to spot the lead-second. It didn't work.
>
> My WWVB based nixie clock isn't even capable of displaying "60" in the seconds
> field, so I knew that clock wouldn't show it. However, right next to it I keep
> an Oregon Scientific WWVB clock. That clock didn't show the leap second, either.
>
> And of course, my Nixichron went into it's hourly display of location and
> temperature at the top of the hour. Never saw the leap second there, either.
>
> I'm not sure when or if my WWVB clocks synced up correctly.... I'll have to
> check that this evening.
>
> Fail.
>
> Terry


--
David Forbes, Tucson, AZ

Mich...@aol.com

unread,
Jan 3, 2017, 3:54:49 PM1/3/17
to neoni...@googlegroups.com
I got all excited to record the event on my MOD-6.
I even turned off the date cycling every minute.
I even setup with my phone to record it.
 
Shit!   I forgot to turn off the temperature from cycling.  :(
 
 
 
Michail Wilson
206-920-6312
 
--
You received this message because you are subscribed to the Google Groups "neonixie-l" group.
To unsubscribe from this group and stop receiving emails from it, send an email to neonixie-l+...@googlegroups.com.
To post to this group, send an email to neoni...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/neonixie-l/f3e29173-99f2-8f3b-16cc-98a2bd937e53%40dakotacom.net.

Terry S

unread,
Jan 3, 2017, 4:27:34 PM1/3/17
to neonixie-l, dfo...@dakotacom.net
You had to adjust the worlds' most accurate clock? That thing should just KNOW about leap seconds.

David Forbes

unread,
Jan 3, 2017, 5:54:27 PM1/3/17
to neoni...@googlegroups.com
Terry,

I use the rubidium clock as a frequency source, not a time reference. It tells
me how well adjusted are the Nixie watches that I run for a few days before
shipping to customers. This was the first time in over five years that I even
bothered to set the atomic clock's display to within a second of UTC.


On 1/3/2017 2:27 PM, 'Terry S' via neonixie-l wrote:
> You had to adjust the worlds' most accurate clock? That thing should just KNOW
> about leap seconds.
>
> On Tuesday, January 3, 2017 at 1:35:25 PM UTC-6, nixiebunny wrote:
>
> Terry,
>
> I knew that none of my clocks that I made would do anything interesting with
> it,
> since none of them have calendars, so I watched the time.gov
> <http://time.gov> clock page and shot
> a short phone video of the leap second happening. It's a bit weird to watch.
>
> I did have to adjust my rubidium Nixie clock after the event.
>

Reply all
Reply to author
Forward
0 new messages