Hmmm, yes, you're absolutely right. Now I'm confused!
Peter
On 1 January 2017 at 16:21, Deirdre O'Byrne wrote:
> 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 wrote:
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 wrote:
> Hi Deirdre,
>
> Well done getting such a clear recording! Yes, the leap-second is
> effectively inserted after the DUT1
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
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 s
On Sun, Jan 01, 2017 at 02:28:23AM +, Deirdre O'Byrne wrote:
> https://www.youtube.com/watch?v=FpBxB2Yqh-U
Nice.
> Starting at 23:58:00 -
> A 1000101101001011000111010001110110010110
> B 10001000
>
> Starting at 23:59:00
https://www.youtube.com/watch?v=FpBxB2Yqh-U
Time signal -
0011223344556
0123456789012345678901234567890123456789012345678901234567890
Starting at 23:58:00 -
A 1000101101001011000111010001110110010110
B 10
