ma...@non-stop.com.au said:
Today is start of new epoch.
As per: http://adn.agi.com/GNSSWeb/
1753:0 Full GPS week since 1st epoch : day of week number
729:0 GPS Week since latest epoch : seconds of week at midnight for
that day
I don't think so. If this was a new epoch, that 729
Yes. This week is not the start of a new epoch.
On Sun, Aug 11, 2013 at 10:10 AM, Hal Murray hmur...@megapathdsl.net wrote:
ma...@non-stop.com.au said:
Today is start of new epoch.
As per: http://adn.agi.com/GNSSWeb/
1753:0 Full GPS week since 1st epoch : day of week number
729:0
Please explain what happened today then?
Also, the 2 module that I cannot set to the correct date are both Furino
GT-77's.
Over on the NTP list they are claiming it's the start of the new GPS 1024 week
epoch.
If you have a look at the rest of the days here: http://adn.agi.com/GNSSWeb/
Today was
marki wrote:
Today is start of new epoch.
I think the next epoch is April 7, 2019 (1024 weeks after the last
epoch, August 22, 1999). (Strictly speaking, the epoch is a point in
time -- the 1024-week period is an era. Eras begin and end at epochs.)
Best regards,
Charles
Yep Sorry, I see what you mean, can't be the GPS week rollover bug then.
I am at a loss to explain this one then.
-Original Message-
From: time-nuts-boun...@febo.com [mailto:time-nuts-boun...@febo.com] On Behalf
Of Mark C. Stephens
Sent: Sunday, 11 August 2013 6:33 PM
To: Discussion of
Harbinger sues Deere and GPS companies for $1.9 billion in damages
http://tinyurl.com/k7w3psl
http://www.reuters.com/article/2013/08/09/us-harbinger-deere-lawsuit-idUSBRE97
80ZD20130809
Ah, the American way. When in trouble, sue everybody.
N.J. Man In A Jam, After Illegal GPS
But according to Furuno it is a problem:
http://www.furuno.com.cy/important-notice.html
Important notice to our customers who use FURUNO GPS receivers for marine use
that are affected by GPS week number rollover. [eRideOPUS GPS GNSS receivers
are not affected by this matter.]
We thank you very
As has been discussed here before.
The GPS firmware programmer finalizing his stuff at GPS week X (approaching
1024) will make sure his receiver will survive until X weeks into the next era.
What X is is hard for the end user to know. 1024 weeks is long time beyond
normal warranties.
I have
bg wrote:
As has been discussed here before.
The GPS firmware programmer finalizing his stuff at GPS week X
(approaching 1024) will make sure his receiver will survive until X
weeks into the next era. What X is is hard for the end user to know.
1024 weeks is long time beyond normal warranties.
On 08/11/2013 05:18 AM, Mark C. Stephens wrote:
Okay this is what worked for me:
1. Removed power and antenna.
2. apply power with no antenna.
3. send :GPS:INIT:DATE 2007,08,11
4. plug antenna back in.
For some reason if I used the correct date, the Z3815A warped back to 1993.
But I am
On 08/11/2013 07:07 AM, Hal Murray wrote:
With the wrong date and time, the GPS should not find almanac data, so will
not lock.
I don't think that's the right way of describing the problem.
The satellites broadcast on a known frequency, but that gets shifted all over
the place by Doppler.
OK, good, found the bug. Now, iwe wish it were possible to download
the firmware, make the correction and then upload...
On Sun, Aug 11, 2013 at 1:14 PM, Magnus Danielson
mag...@rubidium.dyndns.org wrote:
On 08/11/2013 05:18 AM, Mark C. Stephens wrote:
Okay this is what worked for me:
1.
Azelio, is your Furuno playing up?
-Original Message-
From: time-nuts-boun...@febo.com [mailto:time-nuts-boun...@febo.com] On Behalf
Of Azelio Boriani
Sent: Sunday, 11 August 2013 9:30 PM
To: Discussion of precise time and frequency measurement
Subject: Re: [time-nuts] Warped back to
Hi
One point worth mentioning - the device will still be quite happy acting as a
GPSDO. It simply will not be of much use for NTP (or any other date dependent
system).
Bob
On Aug 11, 2013, at 7:44 AM, Mark C. Stephens ma...@non-stop.com.au wrote:
Azelio, is your Furuno playing up?
If Furuno can supply the FW to update with, we would be more than happy.
A slight alteration of the code would suffice...
if (week 729)
week += 2048;
else
week += 1024;
Which would keep them floating for another 1024 weeks. If they then let
us know where the two constats is located so
On 08/11/2013 03:08 PM, Bob Camp wrote:
Hi
One point worth mentioning - the device will still be quite happy acting as a
GPSDO. It simply will not be of much use for NTP (or any other date dependent
system).
I'm sure that the NTP drivers can be hacked to make necessary
adjustments without
Hi
… and since NTP is open source, doing the hack is not dependent on getting a
new firmware image for the GPS.
Bob
On Aug 11, 2013, at 9:12 AM, Magnus Danielson mag...@rubidium.dyndns.org
wrote:
On 08/11/2013 03:08 PM, Bob Camp wrote:
Hi
One point worth mentioning - the device will
Hi Bob,
On 08/11/2013 03:37 PM, Bob Camp wrote:
Hi
… and since NTP is open source, doing the hack is not dependent on getting a
new firmware image for the GPS.
Yes, but it only helps the NTP side of things.
Made a point about the wrap-around-compensation on one of the NTP lists
just now,
At least one my Z3805's is also showing a date from 1993.
___
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 instructions there.
Furuno will not give you the time of day :-) :-)
Don
Magnus Danielson
Hi Bob,
On 08/11/2013 03:37 PM, Bob Camp wrote:
Hi
and since NTP is open source, doing the hack is not dependent on
getting a new firmware image for the GPS.
Yes, but it only helps the NTP side of things.
Made a
Bob Camp wrote:
Hi
… and since NTP is open source, doing the hack is not dependent on getting a
new firmware image for the GPS.
Hacking ntpd is one possibility, with the risk that a workaround for
some broken GPS receiver also affects GPS receivers which are working
correctly.
At least
Hi
Well, if it works fine as a GPSDO, and NTP can be fixed to work with it, that
covers ninety something percent of what most people do with this sort of stuff.
Bob
On Aug 11, 2013, at 9:43 AM, Magnus Danielson mag...@rubidium.dyndns.org
wrote:
Hi Bob,
On 08/11/2013 03:37 PM, Bob Camp
Hi
I think that without much risk, you could put in a gps epoch setting in the
ntp configuration file. More or less make it a check and correct if needed
sort of thing. No setting in the file would mean disable the check and correct
code.
Bob
On Aug 11, 2013, at 12:58 PM, Martin Burnicki
According to the Thunderbolt manual on July 30, 2017 Tbolts will experience a
rollover error.
In version 4 of Lady Heather (being developed), I have added a rollover
compensation mechanism. If the GPS year is less than the OS year, 1024 weeks
is added to the GPS time until the year catches
mag...@rubidium.dyndns.org said:
I'm sure that the NTP drivers can be hacked to make necessary adjustments
without too much code.
The code is already in there. It's got a fudge option in the config file.
That was intended to fixup small offsets. I think it will work with big
offsets too.
On 08/11/2013 07:39 PM, Mark Sims wrote:
According to the Thunderbolt manual on July 30, 2017 Tbolts will experience a
rollover error.
In version 4 of Lady Heather (being developed), I have added a rollover
compensation mechanism. If the GPS year is less than the OS year, 1024
weeks
Hal,
Is the change cumulative? In other words is one tries 2^n times, could
you get there?
BTW. Thanks for your advice on scopes.
I finally ordered a DS1102. I had ordered a DS2072 but it would have
been 4-6 weeks till arrival, if then. In the interim, I convinced
myself a 2072 would
Hi
The issue with the fudge option is that you need to engage it at exactly the
right point. Put another way, there's a period between it failing and your
entering a fudge that the NTP server is down. With a couple lines of auto
correct code in there, it would (essentially) never fail. If you
Bob Camp wrote:
Hi
The issue with the fudge option is that you need to engage it at
exactly the right point. Put another way, there's a period between it
failing and your entering a fudge that the NTP server is down.
The question is whether you know in advance *when* the problem will occur.
Hi
I'd claim that the modulo 1024 wrap is a known issue with GPS. I would not
force the correction on all users. I'd just make it an optional item. This
obviously also applies to things like LH and other TimeNut stuff. As we try to
keep the gear going much longer than the original designers
als...@nc.rr.com said:
Is the change cumulative? In other words is one tries 2^n times, could you
get there?
I don't think so. Even if it did a += rather than an =, you still have the
problem of a float not being big enough to hold 1024 weeks plus a few ms.
Turns out guys have hacked
Hi
If we are keeping this stuff running for decades (think of the WWII stuff we
still try to use) then we need a long term / across the board fix. Making all
the vendors open source their firmware is one way, I doubt it will work.
Reverse engineering all the firmware is also unlikely to be an
li...@rtty.us said:
The issue with the fudge option is that you need to engage it at exactly the
right point. Put another way, there's a period between it failing and your
entering a fudge that the NTP server is down.
Yup. But if you are running along and suddenly your GPS breaks, you might
Hi
On Aug 11, 2013, at 5:32 PM, Hal Murray hmur...@megapathdsl.net wrote:
li...@rtty.us said:
The issue with the fudge option is that you need to engage it at exactly the
right point. Put another way, there's a period between it failing and your
entering a fudge that the NTP server is
On 08/11/2013 11:32 PM, Hal Murray wrote:
li...@rtty.us said:
The issue with the fudge option is that you need to engage it at exactly the
right point. Put another way, there's a period between it failing and your
entering a fudge that the NTP server is down.
Yup. But if you are running
Hi
On Aug 11, 2013, at 6:07 PM, Magnus Danielson mag...@rubidium.dyndns.org
wrote:
On 08/11/2013 11:32 PM, Hal Murray wrote:
li...@rtty.us said:
The issue with the fudge option is that you need to engage it at exactly the
right point. Put another way, there's a period between it failing and
I don't* number my seconds with my PPS devices so as long as the PPS
tracks the GPS system the reported date is irrelevant. If this
problem effects an ntp controlled clock group I think it means you're
misconfigured** e.g. misusing the TRUE option.
* Well not quite true but the point remains.
Hi
I agree that if you are using GPS simply as a PPS source, then this isn't quite
as important. I believe that some are using GPS as a time of day (etc) source
as well. I think that the how / why / what of doing this with NTP probably
belongs over on the NTP list. The issue is a bit broader
38 matches
Mail list logo
