Re: Trimble Geoexplorer 1,2 date problems
- From: Terje Mathisen <"terje.mathisen at tmsw.no">
- Date: Sat, 28 Mar 2009 14:16:01 +0100
Sam Wormley wrote:
Roman Szeremeta wrote:Their excuse for producing incorrect data is that it doesn't matter!!!
Because of the GPS Week Number Rollover, it is impossible with the current
navigation message to determine the correct date for more than 1024 weeks
(19.6 years), with out an external date source or an internal clock set by
the user... no matter who is the manufacturer.
http://www.navcen.uscg.gov/gps/geninfo/y2k/gpsweek.htm
That isn't quite true:
It is in fact trivial to check the current UTC-TAI offset and use that to determine that the 10-bit week count must have rolled over.
You can even use the known offset at the last (first) rollover to check if a second rollover must have occured.
This would allow the firmware to last for 70+ years from now.
Terje
--
- <Terje.Mathisen at tmsw.no>
"almost all programming can be viewed as an exercise in caching"
.
- Follow-Ups:
- Re: Trimble Geoexplorer 1,2 date problems
- From: claudegps
- Re: Trimble Geoexplorer 1,2 date problems
- From: Sam Wormley
- Re: Trimble Geoexplorer 1,2 date problems
- References:
- Trimble Geoexplorer 1,2 date problems
- From: Roman Szeremeta
- Re: Trimble Geoexplorer 1,2 date problems
- From: Sam Wormley
- Re: Trimble Geoexplorer 1,2 date problems
- From: Roman Szeremeta
- Re: Trimble Geoexplorer 1,2 date problems
- From: Sam Wormley
- Trimble Geoexplorer 1,2 date problems
- Prev by Date: Re: Trimble Geoexplorer 1,2 date problems
- Next by Date: Re: Trimble Geoexplorer 1,2 date problems
- Previous by thread: Re: Trimble Geoexplorer 1,2 date problems
- Next by thread: Re: Trimble Geoexplorer 1,2 date problems
- Index(es):
Relevant Pages
|