It appears that, like last month's test, the phase data pattern transmitted is constant and repeats every minute. The pattern is different than last time however:
+-- sec 0 v vvvv April 15 2012 1001100101 0100000011 1110111100 1110101100 0010111000 1101101000 <-- sec 59 1011011110 0000100111 1001100111 1111010010 0100101111 1111111110 ^^^^ March 11 2012 vvvv April 15 2012 sync=01001100101010 tpar=00000 hour=11110111101110101100 min=010111 sync=01011011110000 tpar=01001 hour=11001100111111010010 min=100101 ^^^^ March 11 2012 vvvv April 15 2012 dston=0 leap=0 dlpar=110 dst=110100 r=1000 dston=1 leap=1 dlpar=111 dst=111111 r=1101 ^^^^ March 11 2012 I'm pretty sure I have the phase ambiguity correct since the two sync bits between minute frames (at secs 0 and 59) have the same value across both tests. But the other bits and fields don't make any sense with respect to the NIST spec: The minute field doesn't increment, the dston/leap parity bits aren't correct, etc. So my guess is that they're only testing the autocorrelation properties of different sync patterns rather than the full protocol. But who knows.. _______________________________________________ time-nuts mailing list -- [email protected] To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
