time-nuts@lists.febo.com

Discussion of precise time and frequency measurement

View all threads

Z3801A jumped back to 01 Jan 2006, looks like WNRO

HM
Hal Murray
Tue, Aug 19, 2025 10:04 PM

Anybody else noticed this?
scpi > T2200601021928383000043

It happened over the weekend, 1024 weeks after 01 Jan 2006.

There is/was a way to tell the GPS unit the date and time.  I think the
idea was faster startup, but I remember using it to get past some WNRO
troubles.

It won't take the current date.  Or at least both of mine won't.  So I'm
guessing the date/time is passed to the GPS module and there is another
layer of WNRO testing/fixing in the Z3801A firmware.

Is there a secret recipe to work around this that I don't know about?

Does anybody know how to get the software build date out of a Z3801A?
Just curious.  My copy of the manual says:
Copyright � 2000 Symmetricom,

--
These are my opinions.  I hate spam.

Anybody else noticed this? scpi > T2200601021928383000043 It happened over the weekend, 1024 weeks after 01 Jan 2006. There is/was a way to tell the GPS unit the date and time. I think the idea was faster startup, but I remember using it to get past some WNRO troubles. It won't take the current date. Or at least both of mine won't. So I'm guessing the date/time is passed to the GPS module and there is another layer of WNRO testing/fixing in the Z3801A firmware. Is there a secret recipe to work around this that I don't know about? Does anybody know how to get the software build date out of a Z3801A? Just curious. My copy of the manual says: Copyright � 2000 Symmetricom, -- These are my opinions. I hate spam.
EG
Eric Garner
Wed, Aug 20, 2025 2:55 AM

On my units, you have to tell them the current date prior to them getting
lock.

--Eric


Eric Garner

On Tue, Aug 19, 2025, 7:34 PM Hal Murray via time-nuts <
time-nuts@lists.febo.com> wrote:

Anybody else noticed this?
scpi > T2200601021928383000043

It happened over the weekend, 1024 weeks after 01 Jan 2006.

There is/was a way to tell the GPS unit the date and time.  I think the
idea was faster startup, but I remember using it to get past some WNRO
troubles.

It won't take the current date.  Or at least both of mine won't.  So I'm
guessing the date/time is passed to the GPS module and there is another
layer of WNRO testing/fixing in the Z3801A firmware.

Is there a secret recipe to work around this that I don't know about?

Does anybody know how to get the software build date out of a Z3801A?
Just curious.  My copy of the manual says:
Copyright © 2000 Symmetricom,

--
These are my opinions.  I hate spam.


time-nuts mailing list -- time-nuts@lists.febo.com
To unsubscribe send an email to time-nuts-leave@lists.febo.com

On my units, you have to tell them the current date prior to them getting lock. --Eric _________________________________________ Eric Garner On Tue, Aug 19, 2025, 7:34 PM Hal Murray via time-nuts < time-nuts@lists.febo.com> wrote: > Anybody else noticed this? > scpi > T2200601021928383000043 > > It happened over the weekend, 1024 weeks after 01 Jan 2006. > > There is/was a way to tell the GPS unit the date and time. I think the > idea was faster startup, but I remember using it to get past some WNRO > troubles. > > It won't take the current date. Or at least both of mine won't. So I'm > guessing the date/time is passed to the GPS module and there is another > layer of WNRO testing/fixing in the Z3801A firmware. > > Is there a secret recipe to work around this that I don't know about? > > Does anybody know how to get the software build date out of a Z3801A? > Just curious. My copy of the manual says: > Copyright © 2000 Symmetricom, > > > -- > These are my opinions. I hate spam. > > > _______________________________________________ > time-nuts mailing list -- time-nuts@lists.febo.com > To unsubscribe send an email to time-nuts-leave@lists.febo.com