.@febo.com] On Behalf Of Hal Murray
Sent: Thursday, September 08, 2016 2:54 PM
To: Discussion of precise time and frequency measurement <time-nuts@febo.com>
Cc: hmur...@megapathdsl.net
Subject: Re: [time-nuts] Z3801A gps week rollover
petervince1...@gmail.com said:
> Can I just ask why the Z3801
You might want to try some lithium AA cells. They start out around 1.65V.
They are MUCH less prone to leakage than any "alkaleak" battery and have a very
long shelf-life (i.e. good for low drain memory backups). As always, when
adding a backup battery to a GPS, verify that the battery
The gps rcvr does not have a batter but will indeed support an external
battery.
I attached 2 AA batteries in a external easily replaceable holder and ran
the 2 wires to the receiver 10 pin plug. (At least I think it was 10)
I change the batteries every 2 years not so much for voltage as concern
kb...@n1k.org said:
> The bigger problem for NTP is when the leap second correction process is
> thrown off by the âtime warpâ. When leap seconds get fixed in mid-August
> rather than the end of June ⦠not a good thing.
Is that still a problem? If so, do you have any details. I don't
On 09/09/2016 01:17 PM, Bob Camp wrote:
Hi
On Sep 9, 2016, at 3:06 AM, Magnus Danielson wrote:
Hi,
On 09/08/2016 11:53 PM, Hal Murray wrote:
petervince1...@gmail.com said:
Can I just ask why the Z3801As are having week roll-over problems now - I
didn't
Hi
> On Sep 9, 2016, at 3:06 AM, Magnus Danielson
> wrote:
>
> Hi,
>
> On 09/08/2016 11:53 PM, Hal Murray wrote:
>>
>> petervince1...@gmail.com said:
>>> Can I just ask why the Z3801As are having week roll-over problems now - I
>>> didn't think it was 2048 weeks
Hi,
On 09/08/2016 11:53 PM, Hal Murray wrote:
petervince1...@gmail.com said:
Can I just ask why the Z3801As are having week roll-over problems now - I
didn't think it was 2048 weeks since GPS "zero-hour" until late on the 6th
of April 2019?
It's probably 1024 weeks since a date was built
The Z3801A status page takes 3 seconds to process/send. Not surprising that
the time is a bit off. Lady Heather only requests the SYST:STAT message once
per minute (at hh:mm:33 seconds) because it blocks the unit from doing anything
else while it is handling it. The main things extracted
hol...@hotmail.com said:
> Happy until the next power glitch... the setting does not seem to persist
> between boots. There may also be other conditions that causes it to forget
> your date.
I just power cycled mine. It came back correct without setting the date.
I've assumed there is a
That makes sense - thanks guys!
Peter
On 8 September 2016 at 22:53, Hal Murray wrote:
>
> petervince1...@gmail.com said:
> > Can I just ask why the Z3801As are having week roll-over problems now -
> I
> > didn't think it was 2048 weeks since GPS "zero-hour"
petervince1...@gmail.com said:
> Can I just ask why the Z3801As are having week roll-over problems now - I
> didn't think it was 2048 weeks since GPS "zero-hour" until late on the 6th
> of April 2019?
It's probably 1024 weeks since a date was built into the firmware.
It's like the year 2000
Hi
After the first batch of GPS devices rolled over, the manufacturers came up
with a “fix”
for the problem. If the date came out to a number *before* the firmware was
issued,
it was corrected forward in time. This only works over a single span of GPS
dates.
Depending on when the firmware
Can I just ask why the Z3801As are having week roll-over problems now - I
didn't think it was 2048 weeks since GPS "zero-hour" until late on the 6th
of April 2019?
Peter
___
time-nuts mailing list -- time-nuts@febo.com
To unsubscribe, go to
Yes, rollovers should not be a problem and should only affect the date display.
However, I have seen devices/software that use GPS fail to work because of what
appears to be an invalid date. It seems that they are validating the data from
the receiver and if, for instance, the date is
they have no effect on 1PPS or 10 MHz outputs.
>
> /tvb
>
> - Original Message -
> From: "paul swed" <paulsw...@gmail.com>
> To: "Discussion of precise time and frequency measurement" <
> time-nuts@febo.com>
> Sent: Thursday, Septembe
2016 8:16 AM
Subject: Re: [time-nuts] Z3801A gps week rollover
> Mark,
> From some earlier threads on rollovers. Do you even need to set the time at
> all?
> Granted not great if the 3801 is a time source, but if its just frequency
> do you care?
> Thanks
> Paul
> WB8
Mark,
>From some earlier threads on rollovers. Do you even need to set the time at
all?
Granted not great if the 3801 is a time source, but if its just frequency
do you care?
Thanks
Paul
WB8TSL
On Tue, Sep 6, 2016 at 11:30 AM, Mark Sims wrote:
> Happy until the next power
Happy until the next power glitch... the setting does not seem to persist
between boots. There may also be other conditions that causes it to forget
your date.
And when setting the date, you should disconnect the antenna first, then power
on. Once the unit starts tracking satellites you
I had one that screwed up. I power cycled and set the date. It's happy now.
I'm not sure of the exact recipe to tell it the right date. After feeding it
a date of roughly today, the status screen jumped to Jan 2007. After it
found a few satellites and such, it jumped to Sep 2016.
--
That would be sunday midnight, GPS time, as GPS time-gears have GPS week
shift between saturday and sunday. This naturally makes Monday extra
monday as the system that fail do it during sunday.
Cheers,
Magnus
On 09/05/2016 06:29 AM, Mark Sims wrote:
I did a little math on the dates and it
hol...@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
T21997010102300103
8 64 0
That's from ntpd's
Hi
The rollover is in the GPS module firmware. If you dig into it, they didn't
quite update the firmware once every 3 months, but almost that often. Each
manufacturer latched onto various versions as they sailed by. None of them had
a validation process that could keep up with 4 releases a
On 9/4/2016 10:48 PM, Mark Sims wrote:
Sometime (I didn't have it connected) in the last couple of weeks
my Z3801A went into gps week rollover.
If you have a Z3801A that had been working properly you might want to
check yours. Different firmware versions roll over at different
times.
My
I did a little math on the dates and it looks like the rollover happened in the
last couple of days...
___
time-nuts mailing list -- time-nuts@febo.com
To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the
Sometime (I didn't have it connected) in the last couple of weeks my Z3801A
went into gps week rollover. It now reports the year as 1997. It had been
working propely. Lady Heather caught the anomaly and automatically added 1024
weeks worth of seconds to the date/time which compensated for
25 matches
Mail list logo