[time-nuts] GPS leap second pending (Fury/Z38XX)
magnus at rubidium.dyndns.org
Sun Jan 25 14:26:14 EST 2015
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
You will be at UTC+2h since it will be summer-time.
On 01/25/2015 05:03 PM, Hans Holzach wrote:
> 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 lasts 1 second.
> but in the meantime it dawned on me that maybe the leap second date
> respects my time zone (CET; UTC + 1). and indeed, as soon as i change
> ptim:tzone from 1 to 0, the reported leap second date is june 30!
> 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 with a 60 second minute
> Check again after June 1st.
> /tvb (i5s)
> > On Jan 25, 2015, at 3:54 AM, Hans Holzach <hans.holzach at
> gmail.com> wrote:
> > 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 at febo.com
> To unsubscribe, go to
> and follow the instructions there.
More information about the time-nuts