Well, Said can tell us for sure (since he owns the firmware in the Fury) but
you could call this is correct, because:
1) a leap second is not pending this month
2) the current leap second count is still 16
3) the next leap second happen between 2015-06-30 and 2015-07-01
4) the current month ends
true, this depends on the definition of pending. however, i found it a
bit odd that the software reports a scheduled (but not pending this
month) leap second on july 1st. it's june 30 that is 86401 seconds long,
not the day after. in my opinion there is nothing between june 30 and
july 1 that
my jackson labs fury (1.22) reports:
leapsecond pending: 0
leapsecond accumulated: 16
leapsecond date: 2015,7,1
leapsecond duration: 60
strange...
hans
___
time-nuts mailing list -- time-nuts@febo.com
To unsubscribe, go to
I agree, it looks kinda OK, even if a bit of unconventional format.
Would be interesting to hear the motivation for not listing it at the
last of June.
Cheers,
Magnus
On 01/25/2015 03:59 PM, Tom Van Baak wrote:
Well, Said can tell us for sure (since he owns the firmware in the Fury) but
Hans,
For POSIX type clocks, 1 July 2015 will have two seconds denoted
00:00:00, but for real UTC clocks it will be 30 June that has 23:59:59
and 23:59:60.
You will be at UTC+2h since it will be summer-time.
Cheers,
Magnus
On 01/25/2015 05:03 PM, Hans Holzach wrote:
true, this depends on
- Original Message -
From: Hans Holzach hans.holz...@gmail.com
To: time-nuts@febo.com
Sent: Sunday, January 25, 2015 8:03 AM
Subject: Re: [time-nuts] GPS leap second pending (Fury/Z38XX)
true, this depends on the definition of pending. however, i found it a
bit odd that the software
