Owners of older Honda and Acura models started their cars on New Year’s Day but found their vehicles turned into time machines, according to a report from jalopnik. Rather than transitioning seamlessly into the year 2022, car clocks jumped back 20 years, and Honda says a solution could be months away.
Mine @Honda 2007 CR-V clock now useless in 2022; reset to 2:00 MST on 1/1/2002 after each boot. 32-bit integer signed overflow from yymmddHHMM? Would unsigned int solve it? This is time critical. 😉 Thousands of us need a software update! pic.twitter.com/BSGCaxnMmx
— Sumner Silent (@_______ Silent) January 4, 2022
As noted by jalopnik, there are reports of issues with digital clocks on Honda and Acura forums all over the internet with the issue only affecting older vehicles with navigation. It’s not clear exactly which years are affected, but judging by user reports, it appears that the issue is common in models released from 2006 to 2014 in the US, Canada, and the UK.
Regardless of the year or model, the Y2K22 problem manifests itself in the same way: the date displayed on the navigation system has been reset to the year 2002 and shows a time that differs by several hours. Some users mention that the individual radio clock also shows an incorrect time, and even if they try to manually adjust the time and date, the system doesn’t seem to save those changes.
“American Honda is aware of a potential concern regarding the clock display on certain older Acura and Honda models equipped with navigation systems,” Honda spokesman Chris Naughton said. The edge. “We are currently investigating this issue to determine potential countermeasures and have no additional details to share at this time.”
A post on the CR-V Owners forum shows a more detailed response from both Honda in the US and the UK, with the US representative noting that drivers could experience the issue from January to August 2022 and the system will “correct automatically” itself after this period. Meanwhile, the UK spokesperson won’t give an exact timeline for the resolution, saying that “Honda’s engineering department is currently working on this” and that “a service bulletin from Honda UK will be issued to our dealers on how to resolve this.”
According to jalopnik, the problem may be caused by a coding complication. Jacalar, a user on the Drive Accord forum, says that after diving into the diagnostics menu of their navigation system, they found that the date on the GPS was set to May 19, 2002, which is 1024 weeks ago.
As explained by jalopnik, a GPS uses a starting point, also known as an era, to determine the date and time. This information is sent to GPS devices in a series of 10 binary digits representing the current week, which starts at zero and ends at 1023 – the number would return to zero in week 1024. Since the first week zero was set on January 6, 1980, we have experienced a large-scale rollover of the GPS week number every 19.7 years, with the first in August 1999 and the most recent on April 6, 2019. It is possible that Honda’s navigation software kept did not consider a rollover on New Year’s Day, possibly due to a coding error, causing navigation systems to revert to the start of the set calendar.
Apparently this isn’t the first time the clocks in Hondas and Acuras have been hit by such a strange problem. On August 16, 2017, a day coinciding with the 40th anniversary of Elvis Presley’s death, the navigation systems on older Honda and Acura models failed completely and were mysteriously stuck at 0:00 AM.