[time-nuts] Leap second - MSF time signal

Deirdre O'Byrne deirdre.dub at gmail.com
Sun Jan 1 11:21:19 EST 2017


Didn't the DUT1 code change from -0.4s during the minute starting 23:58:00
to +0.6s during the minute starting 23:59:00?

On 1 January 2017 at 16:06, Peter Vince <petervince1952 at gmail.com> wrote:

> Hi Deirdre,
>
>      Well done getting such a clear recording!  Yes, the leap-second is
> effectively inserted after the DUT1 code on MSF as you say, even though
> that isn't crystal clear from the MSF spec document that David linked to.
> The DUT1 codes refer to the "current" minute, whilst all the rest of the
> time and date information refers to the next minute epoch!
>
>      Peter
>
>
> On 1 January 2017 at 15:01, Deirdre O'Byrne <deirdre.dub at gmail.com> wrote:
>
> > Your decoded timecode only has 60 data points for the 61-seconds of the
> > last minute of 2016 UTC, so it's impossible to say what your decoder did
> > with the leap second. (Also I think you have an error in your parity bit
> > for the time for midnight (bit 57B)).
> >
> > The long wave spectrum seems to show the same fourteen 0.1+0.9-second
> > pulses between 23:59:07 and 23:59:20 (inclusive), which tends to suggest
> > that the leap second was indeed inserted between the DUT1 code and the
> Year
> > code.
> >
> > Interestingly the long wave spectrum also shows DCF77 - a project for
> when
> > I get bored! :)
> >
> >
> _______________________________________________
> time-nuts mailing list -- time-nuts at febo.com
> To unsubscribe, go to https://www.febo.com/cgi-bin/
> mailman/listinfo/time-nuts
> and follow the instructions there.
>


More information about the time-nuts mailing list