[time-nuts] Lucent KS-24361, curious observation
kb8tq at n1k.org
Mon Dec 1 18:44:54 EST 2014
> On Dec 1, 2014, at 11:47 AM, Paul <tic-toc at bodosom.net> wrote:
> On Mon, Dec 1, 2014 at 11:15 AM, Graham <planophore at aei.ca> wrote:
>> It has been less than 18 hours since I powered them up so I am not yet
>> wondering why the the REF-0 LED's are in the state they are as I have seen
>> reports of others having to wait 24 hours or so before every "locks in".
> There are differing states. My pair went OK+Standby in about 10 minutes
> but they're not "stable" at that point.
> Here's a log snippet:
> Log 019:20141128.00:00:00: Power on
> Log 020:20141128.00:00:26: Power settings ok, Int: 17 dBm, Ext: 17 dBm
> Log 021:20141128.00:52:21: Position hold mode started
> Log 022:20141128.01:28:32: GPS reference valid at 20141128.20:34:00
> Log 023:20141128.20:35:04: Locked mode entered
> Log 024:20141129.10:35:03: Ready for 4 hour flywheel
> Log 025:20141129.16:35:03: Ready for 8 hour flywheel
Checking the log from time to time is a very good idea.
> The first timestamp after power-on is 00:00 of the last valid date prior to
Until it gets GPS lock, the time stamps can be pretty confusing.
> I assume the deltas are correct. So 1:29 to Locked and 20 more
> hours to "stable". Holdover uncertainty continues to decrease for many
> more hours. It decreased from hundreds of microseconds to 3 at the time of
> that log and is now at 900 nanoseconds.
The holdover uncertainty numbers on these are every bit as “interesting” as the numbers the Z3801 puts out. Fun to watch. I would not count on them being correct.
> 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