Received this yesterday from TomTom:
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - CONSIDER UPGRADING YOUR DEVICE
This message is regarding your navigation device with serial number:
L47128A00485
Due to the upcoming WNRO on 6 April 2019, your navigation device will continue to navigate, but will not be able to show the correct time and estimated time of arrival (ETA).
We are working to see if an update is possible and will contact you when there is news.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Admittedly my car TomTom is pretty old and unsupported (bought it around
2007 IIRC) so it's nice of TomTom to reach out.
Now at least I get to see if my GPS exhibits an error due to rollover.
On 2019-04-05 03:09, Terje Mathisen wrote:
Alan Browne wrote:
Received this yesterday from TomTom:
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CONSIDER UPGRADING YOUR DEVICE
This message is regarding your navigation device with serial number:
L47128A00485
Due to the upcoming WNRO on 6 April 2019, your navigation device will
continue to navigate, but will not be able to show the correct time
and estimated time of arrival (ETA).
Good that they know about the issue and warn you, pretty stupid of
them to not at least program in a basic window when making the firmware:
get_week_number();
convert_week_to_date();
while (date < firmware_date)
add 1024*7 days to date;
If the firmware is 20+ years old, that would not work.
I'd use a local week counter and save it in flash on each week tick,
myself.
Alan Browne wrote:
Received this yesterday from TomTom:
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CONSIDER UPGRADING YOUR DEVICE
This message is regarding your navigation device with serial number:
L47128A00485
Due to the upcoming WNRO on 6 April 2019, your navigation device will
continue to navigate, but will not be able to show the correct time
and estimated time of arrival (ETA).
Good that they know about the issue and warn you, pretty stupid of them
to not at least program in a basic window when making the firmware:
get_week_number();
convert_week_to_date();
while (date < firmware_date)
add 1024*7 days to date;
Alan Browne wrote:
On 2019-04-05 03:09, Terje Mathisen wrote:
Alan Browne wrote:
Received this yesterday from TomTom:
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CONSIDER UPGRADING YOUR DEVICE
This message is regarding your navigation device with serial number:
L47128A00485
Due to the upcoming WNRO on 6 April 2019, your navigation device
will continue to navigate, but will not be able to show the correct
time and estimated time of arrival (ETA).
Good that they know about the issue and warn you, pretty stupid of
them to not at least program in a basic window when making the firmware: >>>
get_week_number();
convert_week_to_date();
while (date < firmware_date)
add 1024*7 days to date;
If the firmware is 20+ years old, that would not work.
Updating the firmware at least once every 20 years would work, but i'm guessing the real problem is that they don't have any easy/cheap way to update it?
I'd use a local week counter and save it in flash on each week tick,
myself.
That's the second problem: They probably don't have any form of writable non-volatile storage. :-(
One of my very first GPS devices was a Motorola Oncore timing receiver,
based on a development board made by hams (TAPR), where I had to solder everything myself. This board had afair no storage at all outside the
GPS module.
On 2019-04-05 15:38, Terje Mathisen wrote:
Alan Browne wrote:
On 2019-04-05 03:09, Terje Mathisen wrote:
Alan Browne wrote:
Received this yesterday from TomTom:
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - >>>>> CONSIDER UPGRADING YOUR DEVICE
This message is regarding your navigation device with serial number: >>>>>
L47128A00485
Due to the upcoming WNRO on 6 April 2019, your navigation device
will continue to navigate, but will not be able to show the correct
time and estimated time of arrival (ETA).
Good that they know about the issue and warn you, pretty stupid of
them to not at least program in a basic window when making the
firmware:
get_week_number();
convert_week_to_date();
while (date < firmware_date)
add 1024*7 days to date;
If the firmware is 20+ years old, that would not work.
Updating the firmware at least once every 20 years would work, but i'm
guessing the real problem is that they don't have any easy/cheap way
to update it?
I'd use a local week counter and save it in flash on each week tick,
myself.
That's the second problem: They probably don't have any form of
writable non-volatile storage. :-(
Most do, at least consumer articles such as car GPS or handheld units
(since they store waypoints, maps, etc.)
One of my very first GPS devices was a Motorola Oncore timing
receiver, based on a development board made by hams (TAPR), where I
had to solder everything myself. This board had afair no storage at
all outside the GPS module.
I had various including the Trimble SVeeSix. No storage of its own (it
was a sensor board more for development projects than anything else - implementing 'solutions' was the user's problem...
But that was a long time ago...
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 296 |
Nodes: | 16 (2 / 14) |
Uptime: | 75:33:03 |
Calls: | 6,657 |
Calls today: | 3 |
Files: | 12,203 |
Messages: | 5,332,646 |
Posted today: | 1 |