Amarin Corp Plc (AMRN)

[sts66]

OT: Tech tip to anyone with a Honda or Acura built between 2004-2012 with a NAV system - the calendar and clocks are borked because of a stupid programming error akin to the Intel Y2K bug and there is no solution available until maybe August of this year - :

On 1/1/22 every Honda and Acura with NAV systems built between 2004-2012 suddenly had their calendar date revert to 1/1/2002, the dash display clock is stuck one hr ahead, and you can't adjust the GPS clock via the Setup page - it won't accept any corrections to the time - mine is stuck at 12:00. After some sleuthing yesterday I only found complaints about this from owners on 2004-2006 Acura TLs on Acurazine.com, but as I kept looking I found an article that said it was a global problem - god knows how many millions of vehicles are affected, and no solution is expected until Aug 2022 - poor programming of the original NAV system - the issue appears to reside in how the calculation of the GPS system time/date is hard coded:

https://tiremeetsroad.com/2022/01/03/honda-acura-owners-report-incorrect-date-time-issue-after-new-year-date-reads-january-1-2002-shows-incorrect-time/

Y2K22 Bug

The best explanation of what’s happening is from Drive Accord forum member Jacalar. After poking around in his Accord’s Navigation systm diagnostic menu, he discovered his GPS date was set 1024 weeks back, or May 19, 2002.

“This is actually a GPS Epoch issue,” Jacalar says. “Going into the “hidden” diagnostic menu on Sunday, I discovered the GPS date was now “May 19, 2002?. That date was exactly 1024 weeks ago (1024 = 2^10) We jumped forward an hour due to May being in daylight savings time.”

“Many GPS devices only work on a single 1024-week span and will no longer show an accurate date once the week count rolls over, regardless where that roll over falls,” 2012 Honda Accord HFP further clarified.

This has happened with Hondas before. On August 16, 2017, Honda owners reported their clocks zeroed out to 00:00.

One Honda Odyssey owner figured out his Odyssey’s clocked rolled back to January 1998.

Subtract 1024 weeks from August 17, 2017, and you get…January 1, 1998.

Honda eventually sent out free navigation update discs to affected owners after two months.
Likely an issue with the head unit

As mentioned by the above Honda CR-V owner, this is likely a coding issue that is head unit specific.

Honda and Acura head units are receiving the correct signals for date and time from GPS satellites or manual input and, due to a technicality of how date and time is digitally stored, cannot store a specific date and time past Dec 31, 2021.

Most likely, Honda is working with their head unit suppliers to come up with the best solution.

We’ll hear an update from Honda soon, as this is a global problem.

A fix may come in the form of a recall and updated discs, or as they mentioned, it will self-correct by August.

Official Honda Responses

CRV Owners Club is cataloging official responses from Honda.

Honda USA– “We have escalated the NAVI Clock Issue to our Engineering Team and they have informed us that you will experience issue from Jan 2022 thru August 2022 and then it will auto-correct. Please be assured that we will continue to monitor this and will advise you if a fix is available before that time.”

How such a programming error will automatically self-repair in August 2022 is not obvious to me given the 1024-week span programming error, so I think that's just Honda blowing smoke up our asses and god knows when this will get fixed. There were about 28M Hondas sold during this time period worldwide, but I don't know how many have/had NAV systems - there were about 1.5M Acuras sold during that period, and the majority of them had NAV systems - they were standard equipment on all RLs, and became standard equipment in the best selling TL in 2007. Since Honda and Acuras will basically run forever if properly maintained, safe to assume there's millions of pissed off owners out there right now - only ones not still on the road were those totaled in an accident.