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

Paul tic-toc at bodosom.net
Sun Dec 7 16:11:18 EST 2014

On Sun, Dec 7, 2014 at 3:07 PM, Bob Camp <kb8tq at n1k.org> wrote:

> The local time is updated *after* the GPS Valid hits the log. Put another
> way, the time used for the log is *not* corrected to GPS time until after
> the valid message is logged.

And I completely agree with you.

My point is the [GPS valid] timestamp that's part of the [GPS valid]
message was at least 50 minutes off.  Just the one time.  Maybe the
timestamp associated with this message:

    GPS reference valid at 20141202.01:47:41

(01:47:41 in this case)  as opposed to the Log timestame (00:25:47 in this
case) is a random time that just happens to typically appear to be the
current GPS time but that seems odd.  However the system makes it just a
bit tricky to compare box time to UTC so maybe all the timestamps are bogus.

Log entry split into two lines:

Log 037:20141201.00:25:47  (00:25:47 is current Z3810 time)

GPS reference valid at 20141202.01:47:41 (01:47:41 is what I thought was
current GPS time.)

But if it is GPS time then this is a glitch:

Log 043:20141201.00:25:42 (00:25:42 is current Z3810 time, this log entry
is about 50 minutes after Log 037 above)

GPS reference valid at 20141202.01:47:36 (01:47:36 is obviously not current
GPS time)

More information about the time-nuts mailing list