[time-nuts] Lucent / Z3810A log time offset.

[Bob Camp]

Hi
> On Dec 7, 2014, at 1:31 PM, Paul <tic-toc at bodosom.net> wrote:
> 
> On Sun, Dec 7, 2014 at 10:26 AM, Bob Camp <kb8tq at n1k.org> wrote:
> 
>> Any time you have a power "burp" the clock will start back at what ever it
>> thinks was the time was last.
>> 
> 
> I understand this.
> 
> I was referring to:
> 
> 
>>> Log 037:20141201.00:25:47:  GPS reference valid at 20141202.01:47:41
>>> Log 043:20141201.00:25:42:  GPS reference valid at 20141202.01:47:36
>> 

If the magic “write the time to flash” routine runs once every 2 hours, then that would explain the log. Numbers like 4 or 8 times a day are not uncommon for this sort of thing. 

Bob 

> 
> These two events were at least an hour apart.  The second one (1:47:36)
> does not precede the first (1:47:41).
> 
> If "GPS reference valid" doesn't mean the Oncore thinks time is valid
> that's okay but it only happened once and there have been multiple power
> resets.  Just no others that (accidentally) happened within ~20 seconds
> (the POST window I assume) of each other.
> 
> I'll wait a few days and do another power reset now that I'm ready for
> concurrent monitoring of both units.
> 
> By the way the time glitch was only logged on REF 1.
> 
> Snippet showing the system adopting the bad time stamp:
> Log 037:20141201.00:25:47:  GPS reference valid at 20141202.01:47:41
> Log 038:20141202.01:48:45:  Locked mode entered
> Log 043:20141201.00:25:42:  GPS reference valid at 20141202.01:47:36
> Log 044:20141202.01:48:41:  Locked mode entered
> _______________________________________________
> 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.