time-nuts@lists.febo.com

Discussion of precise time and frequency measurement

View all threads

Re: [time-nuts] Z3801A gps week rollover

HM
Hal Murray
Mon, Sep 5, 2016 5:55 PM

I did a little math on the dates and it looks like the rollover happened in
the last couple of days...

Thanks for the heads up.

Mine started on Aug 17th

/var/log/ntp/clockstats.20160817:57617 2.033 127.127.26.1
T219970101000002300103
8  64 0

That's from ntpd's clockstats which only logs every 64 samples.

Is there a date code in the serial number (or anyplace else)?  I have 2
units.  One has rolled over.  The other hasn't (yet).
HEWLETT-PACKARD,Z3801A,3542A01377,3543-A
HEWLETT-PACKARD,Z3801A,3542A04389,3543-A


Years ago, I powered up a unit that been off for a long time.  It came up
with the wrong date.  Feeding it the date before it got lock solved the
problem.  (Or something like that.)  Has anybody tried that yet?

--
These are my opinions.  I hate spam.

holrum@hotmail.com said: > I did a little math on the dates and it looks like the rollover happened in > the last couple of days... Thanks for the heads up. Mine started on Aug 17th /var/log/ntp/clockstats.20160817:57617 2.033 127.127.26.1 T219970101000002300103 8 64 0 That's from ntpd's clockstats which only logs every 64 samples. Is there a date code in the serial number (or anyplace else)? I have 2 units. One has rolled over. The other hasn't (yet). HEWLETT-PACKARD,Z3801A,3542A01377,3543-A HEWLETT-PACKARD,Z3801A,3542A04389,3543-A -------- Years ago, I powered up a unit that been off for a long time. It came up with the wrong date. Feeding it the date before it got lock solved the problem. (Or something like that.) Has anybody tried that yet? -- These are my opinions. I hate spam.