My Garmin GPSMap 750 went back to Jan 2002 last summer. After speaking to Garmin support I installed a firmware update and we are now back in 2022.I don't know details of the Furuno problem, but a similar issue with an old Garmin GPS45 it now gets the date wrong persistently but the position is always correct. This means that I know exactly where I am when I run aground because my tide calculation was bullocks having used an incorrect date.
If you scroll down the GP31 is on the 2019 failure list. My GP31 has an incorrect date but also has a small error in position. I think it is a couple of hundred metres but I need to monitor it to see if it is constant. Furuno advice is to buy another unit which is a shame as it is a nice simple robust GPS. Furuno obviously knew this was a predictable problem but were happy to sell the units without informing buyers that they wouId fail in 20 years. I have a Garmin and Magellan handhelds that are very old but still coped with the rollover.My furunoGP-31 gave the wrong date after the last rollover. The time is correct along with the position so I carry on using it to give data to the dsc radio. I could use the plotter but that isn't always on so the furuno carries on until the position gets wrong.
Edit. Just looked at the list of effected models and mine isn't on it. Hopefully it will just carry on with incorrect date ......
My GP 32 has given the wrong date since the 2021 rollover. The position looks to be roughly correct.Thanks for the heads-up, I have GP32 on the boat so I'd best check that out.
Thanks, didn't use the boat last year. The GP32 feeds both AIS rx and VHFMy GP 32 has given the wrong date since the 2021 rollover. The position looks to be roughly correct.
I’m not overly worried by it as it is a standalone unit at the chart table. I have a plotter, a vhf and an AIS which each have their own gps sources, plus an iPad and a number of smartphones on board.
If you scroll down the GP31 is on the 2019 failure list. My GP31 has an incorrect date but also has a small error in position. I think it is a couple of hundred metres but I need to monitor it to see if it is constant. Furuno advice is to buy another unit which is a shame as it is a nice simple robust GPS. Furuno obviously knew this was a predictable problem but were happy to sell the units without informing buyers that they wouId fail in 20 years. I have a Garmin and Magellan handhelds that are very old but still coped with the rollover.
Suggest you check your unit against another GPS or even a phone.
It's equivalent to omitting the century from the year. If you assume you are both working in the current century you get the right answer. But of course in this case the rollover period is much shorter than 100 years!If the GPS unit is storing the wrong date and time, how does it know if the almanac from the GPS satellite is current?
Does this imply the firmware was written in COBOLIt's equivalent to omitting the century from the year. If you assume you are both working in the current century you get the right answer. But of course in this case the rollover period is much shorter than 100 years!
Nothing to do with COBOL, but I was a programmer at the time of the Y2K debacle that turned out to be rather boring!Does this imply the firmware was written in COBOL
Surprise, surprise, but 2^10 takes 10 bits. Perhaps you were thinking of two rows of 5-hole paper tape? ;-)I probably know just enough about programming to be dangerous, but 2^10 seems like an odd sort of number unless they were using 5 bits, which, again seems odd.
I'm to old to faff around with an astrolabe, so
All I ask is a small chip and a satellite to steer her by...