[Herman916]

I’ve noticed a few other MDXers on facebook having the same issue I have. My clock is off by exactly an hour and I cannot adjust the time to be right.
If I turn off daylight savings, it stays and when I try to manually adjust it +/- it instantly goes back to 12:00 on the nav screen and pressing RESET does nothing.
Anyone else having this issue or know how to get it adjusted?

 

[Daddynemo]

Tagging along for this one. No battery failures or disconnects. Just randomly an hour ahead a few mornings ago. And the same for me, try to adjust in settings and the clock turns red and resets after one or two pushes to adjust.

 

[Herman916]

A guy on facebook sent me this article. Looks like it’s a Honda/Acura glitch that’s getting a ton of cars and models with the original nav system.

Honda and Acura's Navigation Systems Show 20-Year Old Dates, No Solution Available Yet

Some of the Honda and Acura owners face an unusual problem with their navigation systems, which are showing an incorrect time and date, and no solution to correct that.

www.autoevolution.com

 

[colinnwn]

Interesting. I hadn't spent the time to research it yet but I expected as much, that at least MDXes of this generation and possibly other cars with the same nav system subcontractor would be affected.

The software that runs the system is on the nav DVD. Fixing this will likely require a new DVD. But it probably can't be fully explained without having a deep understanding of the nav system code and lookup tables.

Some aspects of the system are loaded on an OS DVD before the nav DVD is loaded. For my 2006 I did not have to preload an OS DVD before my 2020 nav DVD update.

It will be interesting if Honda actually comes through and provides a fix DVD at a small cost, versus either orphaning the system or charging the typical $100-150 DVD cost.

As of 2021 they had intended to orphan all nav system updates through the 2006 MDX. Some prior model years they orphaned years ago.

Sent from my Pixel 6 using Tapatalk

 

[Daddynemo]

The 8th gen civic was mentioned, that spans all the way to 2012. But i wonder to what years this will affect? As an aftermarket parts installer as well, this is gonna create quite a mess with customers we've done add ons to. Thanks for the info, hopefully they add more info soon.

 

[Herman916]

I’m hoping Honda/Acura can come up with a solution ASAP at no cost to the consumer. This is a “Y2K(22)” issue people were having issues with 22 years ago. You’d assume they would have been ready for this or already “fixed” it.

 

[colinnwn]

Even Microsoft had a Y2K22 bug come up in their Outlook Cloud infrastructure, and they are a technology company with massive resources, so this isn't unique to Honda.

What I find most inexcusable is that we had just gone through Y2K, and knew what a problematic issue it was. A reasonable lifespan for vehicles easily exceeds 20 years, and storage of data is plentiful now (which historically expensive limited data storage was the cause of the Y2K bug). There was no reason not to write the code to in a way that would prevent any problem in 100-999 years.

It was just laziness and the "I won't be here when it becomes a problem" syndrome. But after it was done, it doesn't surprise me at all that Honda had no idea, and it was completely forgotten about 20 years ago. Very few companies document and prepare for expected problems that will resurface in 20 years.

 

[colinnwn]

Here is another article that identifes the likely problem. Someone went into the GPS diagnostic menu and found the date said May 2002. That is 1024 weeks in the past. This is also exactly 10 bits of numbers. It's also the way the GPS standard counts weeks starting from January 6, 1980.

The last rollover for GPS was in April 2019. The next is in 2038. So if it's the root problem, it still isn't clear why the Honda interface is displaying Jan 2002. It is probably some kind of numeric overflow problem.

Also for whatever reason even though Honda chose the same week scheme and limit as GPS, they didn't start their epoch on the same date as GPS did. So much stupid here.

They claim that this problem will self resolve in August 2022. If that happens I think it will also indicate that it was an overflow of the week counter, and in August the code will read the week counter as having rolled over fully zeroed out again.

https://jalopnik.com/honda-clocks-are-stuck-20-years-in-the-past-and-this-mi-1848306970

 

[mvl]

Someone in the comments of one of the posts said the issue is with setting the time, not keeping it. So if you wait until noon and attempt to set it then (when the software resets to noon) the clock may stay correct (despite the bad date) from that point onwards.

 

[colinnwn]

Not on mine. I have the 2020 maps update that corrected the daylight savings time schedule so my clock is always correct. But I tried to use the clock offset feature at exactly 12 noon actual local time, and no matter how many hours or minutes I did the offset, it didn't save, went right back to noon.

Now I didn't try for example doing the offset from 11 am actual local time, and adding an hour so the corrected time would be noon, for example if you had the wrong DST schedule for springing forward. I guess I could try that tomorrow.

Sent from my Pixel 6 using Tapatalk

 

[beersnob]

I’ve noticed a few other MDXers on facebook having the same issue I have. My clock is off by exactly an hour and I cannot adjust the time to be right.
If I turn off daylight savings, it stays and when I try to manually adjust it +/- it instantly goes back to 12:00 on the nav screen and pressing RESET does nothing.
Anyone else having this issue or know how to get it adjusted?

Same issue here- 2006 MDX/original Map Disc. I'm in the Mountain Time Zone, and my clock always starts at 1:00 when I disconnect my battery. (clock works but never corrects the time). The fix (or "hack"): pull the fuse (mine is listed as rear entertainment Fuse #1 in the secondary underhood fuse box). If you install the fuse at 1 o'clock, the radio clock will now show the correct time. I assume it will be off once DST ends next spring. Not sure how time zone updates will occur, but at least for now, the clock on the radio is correct. (people in other time zones may have to install the fuse at noon or 2PM I guess)

 

[MDX05GUY]

05 MDX Nav/Tour in the same boat just noticed this happening to mine a few days ago. Clock is a hour ahead I'll give beersnob suggestion a try. I'm on EST it's stuck on 1200 date 5/30/02.

 

[eurojap]

Bought the '06 new in August of '06. Still driving it. Have never touched the clock settings until recently when I found the issue that is the subject of this thread. So, just saying me too. Haven't tried any hacks but, I like the fuse to force the system off. That may be a work around until Acura cleans this up. So bizarre really. Absolutely no reason for this other than a software engineer back in about 2002 somewhere screwed up.

I can't find anywhere that shows the date. I dug around the menu pretty deep but, didn't see any years or dates displayed anywhere. I'm guessing we all have the exact same software glitch. My DVD is probably from somewhere in the mid twenty-teens. I don't updated it regularly as I don't drive this vehicle on vacations or anything. Its just my winter beast now. A winter beast that can't tell time.

 

[colinnwn]

I have the 2020 disk and there is no place to change the date in the user menus. I haven't tried to look in the diagnostic menus meant for Techs only. But I doubt there is. Aside from which side of a time zone you are on for one hour at midnight, there is no ambiguity about the actual date, and date/time is central to making GPS navigation work.

Sent from my Pixel 6 using Tapatalk

 

[John N.]

Putting my '06 MDX on the list. Calendar went back to 2002 and the clock was off by one hour. I disconnected the battery for a few hours and when reconnected the clock is now several hours off and cannot be reset. Actual time: 11:22pm. Clock says 5:08.

 

[daveiniowa777]

I had the same problem John N. At this point, I'm going to disconnect the fuse and try to at least get it matched on an hour so I only have to figure out how many hours it's off to figure out what time it is. My radio is crap as well, lights don't work so if it's dark, I can't see the clock anyway.

Debating on buying this.......Or just a new aftermarket one.

2005-2006 Acura Mdx 6 CD Radio Receiver 1AF0 1AF2 Ac616 - Etsy

This Car Parts item is sold by StereoSquad. Ships from Aurora, CO. Listed on Dec 20, 2022

www.etsy.com

 

[colinnwn]

Most Honda components you can remove and replace the backlights on little neowedge post bulbs. I haven't checked the stereo to see if that's possible.

But I have this stereo. And you can't set the clock on it independent of the GPS. It sets itself based on the GPS and so you have the same problem you currently have.

Sent from my Pixel 6 using Tapatalk

 

[daveiniowa777]

Understood in regards to the clock, realize they are separate issues. If you happen to come across how to replace the radio bulbs please let me know!!

 

[colinnwn]

Looks like the audio unit is possibly the exception, the FSM doesn't say there are bulbs to replace. Here are the troubleshooting steps though

 

[mikegio]

I’ve noticed a few other MDXers on facebook having the same issue I have. My clock is off by exactly an hour and I cannot adjust the time to be right.
If I turn off daylight savings, it stays and when I try to manually adjust it +/- it instantly goes back to 12:00 on the nav screen and pressing RESET does nothing.
Anyone else having this issue or know how to get it adjusted?

I’ve noticed a few other MDXers on facebook having the same issue I have. My clock is off by exactly an hour and I cannot adjust the time to be right.
If I turn off daylight savings, it stays and when I try to manually adjust it +/- it instantly goes back to 12:00 on the nav screen and pressing RESET does nothing.
Anyone else having this issue or know how to get it adjusted?

Exactly the same issue here on my 2007 MDX