Moderator Note: Thread moved to model-specific forum for better responses.

 

i read an article that said this "bug" was affecting early model Honda's.
and Honda engineers were working on it.
so, if it's fixed...it's fixed

the article likened the bug to y2k.

 

AcuraClentRelations tweet:

 

My 02 TLS still has the problem. I was wondering if having the car sit in a garage or other GPS blockage zone might affect how soon it reverts to normal???

 

This is crazy why some NAVI clocks start working again and some (seems like most) do not. I thought if i called Tech Support and made sure they had my VIN, they would be able to do something. I'm not sure if IGGY or LMN called tech Support, but theirs started working. I can't imagine that they can't figure out what the problem is... They said they would contact me when they knew something (whatever that means). I will wait a week or so and call again. I got my Case # from them. This seems like a stupid problem to have after 15 years....

 

My 2000 TL Navi clock is still showing 0:00. It did not correct by itself today.

 

Not really, my car was parked outside all the time and still having the issue.

 

I've been reading about this too, it sounds like something to do with Unix Epoch time, where time is actually measured from a start date of 00:00:00 1 January 1970 and then incremented by seconds. This is going to cause what's similar to y2k known as the year 2037 bug where any time-based system using a 32-bit integer offset is going to fail! I noticed my clock from the satellite started reading 01 jan 1998 and forward when this 00:00 bug hit, today it shows a date of February 4th, 1998. I read that this was due to an update by "The Government" to the GPS system, but that sounds kind of fishy that an update can be pushed to the GPS system that messes up a clock. I wonder what a hacker can do with this! lol

 

my 2003 Accura TL stopped working ~8/18. I checked with my repair person and he said that all Accura models from the late 90's through 2007 and that he thinks the problem is an Accura software change of some sort.

Has anyone found an answer to this yet?

 

Tons of people here:

Merging thread
https://acurazine.com/forums/second-...orking-948841/

 

Im still down. lol Sucks to be me!

 

My 04 Ody still at 0:00

 

My '01 CL-S with Navi is still showing 0:00.

 

03 TLS still reading 00:00, unable to adjust!

 

2000 TL, same deal

 

I can't understand why AcuraClient said the fix would happen 17 Sep 2017. I called Acura and they said there is NO FIX yet, but they are working on it ...

Our 202 MDX Touring Navi clock still shows 0:00.

 

I've been trying to figure this out, but anyone that is still not working, have you bought an Annual update disc? Me and My friend both have 01 TLs, and his recovered, but mine didnt. Only difference I can find is that I bought and update (which he now calls me stupid for)....

 

No update. I would not update a 16yo nav system but apparently Im in the minority.

 

Hmmm. What vehicle do you have?

 

Working in my car now.

 

I figured its going to be the same as the previous outage on the older vehicles. Slowly but surely

 

I have the latest disc available, and mine is still not working.

 

I purchased a DVD update for the GPS. The disc indicates Jan. 2004, version 2.11C of the software.

 

I have the 2012 updated disc in my 2003 TLS. Appears the updated disc has nothing to do with this issue. I am puzzled at how some models have recovered, but the majority have not?

 

The clock on my '03 TL/S with Navi is also still not working (since 8/17). I am really confused as to how some people here are reporting that their clock came back on and others have not. Most have not it seems, but the fact that any of them would start working again is confusing. To those posters who questioned whether it may be an update disc, rest assured that is not the problem. I received a letter saying that there would be no more disc updates when my car was 10 years old, so i bought that one in 2013, or maybe 2012. I did call the Tech Support line on 9/18 and received a Case Number. They are supposed to contact me ------ eventually. I would advise anyone who has not called, to do so. The more people who complain, perhaps the more likely they will figure out this problem. Do they really want a ton of Acura owners angry at them when the next car purchase date arrives. Honestly, this has bothered me enough that i probably would not look at an Acura vehicle anymore. My TL is 15 years old already, so another car is in the future for sure. I see the Tweet above from Acura Client Relations that they said the clock on my car should have restarted on 9/17 --- one day before i called the Tech Support Line and the Tech Rep said nothing of this apparent cure. So, it seems that they don't really know what the problem is. Why some started working is a mystery. I will call back and mention this Tweet and see what they say. Even if they diagnose the problem, i even wonder how it could be fixed. I have a hard time believing they will recall all these old cars to fix it if it requires some new NAVI software. Maybe the fix can be downloaded through the GPS or even maybe they could put the fix on a DVD and mail it to us, and we can install it in the NAVI dvd player ourselves. I have no idea ---- just talking out loud....lol. All i know is that i am quite upset since my car has fairly low miles and is in excellent condition. It still feels like a new car to me. If i was on the verge of replacing it, i may not care as much. But i am sure i have a few more years. I am thinking of getting a small SUV like the RDS, or even the Honda CRV but not now. I am going to call them tomorrow and see if they have any real information they can share --- like why some clocks started working and why they said some would start working on 9/17.

 

^the second gen is old enough for them not to care. the fact theyre researching this is surprising to me actually. I may be in minority but its just a clock and these cars are on their 2nd, 4th or 10th owners by now not likely their target market for an upgrade to a new(er) acura and unlike the transmissions do not take away from use of the car.

Good luck in your fight and those that havent been fixed.

 

Just wait until you have a 15 year old car with an infotainment system that is completely useless. No way today's version of Carplay and Andoid Auto will still do their thing and don't expect the manufactures to send you app updates. This clock issue is the tip of the iceberg.

 

This is a puzzeling issue to me! The same phenominon occured at exactly the same time last year, to many 2G TL models.. That problem auto-corrected, which tells me, Acaura is be very familiar with the past issue! Why it's taking so long to fix, and why some owners report their cars clock is working again, makes no sense at all! Very frustrating.

 

Yes 08KBP_VA, you have a point in that these cars are considered 'old' at this point and perhaps Honda/Acura shouldn't care very much about solving this problem, and that many of these cars may have 2 or 3 owners by now. Maybe they think that these current customers aren't worth the trouble of working on this problem. However, i think they care about every customer up to a point. It is a reputation issue. But this is such a lame problem to have at this point and apparently they have had this problem before. The other thing for me is that I am the original owner and my '03 TL/S is still like a new car. I also have the original transmission, but i am fully aware of the issues many of these cars had. Mine was made early (actually in June 2002), yet i escaped the really bad tranny units. Acura did install the oil jet in the fill hole in early 2004 and i change the fluid very regularly, so i guess i have been lucky. The TSB listed the affected units by VIN and mine was outside the TSB-listed VINs. I suppose the oil jet also saved it. With 103,000 miles, it is very possible that my car will still be around many years from now. I would even change the tranny if i had to. So, to be honest seeing my navi clock display 0:00 does actually bother me..... to the point i would look to buy something else unless they fix this problem. Call it personal.... maybe it is.
I agree frankjnjr, it is crazy that some clocks work and others don't in the exact same car, and some have self-corrected. I will try and call back Tech Services today and see if they have any answers yet.

 

I bought a new 2000 RL and when it was about 8 years old I was driving one day on the highway and the engine died. I had it towed to the nearest Acura dealer and within about 20 minutes they told me it was the fuel pump relay under the dash. They said it is a very, very common problem in Honda and Acura. They even had the relay in stock!! I asked if it was covered as a major safety item (car dying in traffic) and they said the part and labor was not covered or even discounted.
When it came time to buy an SUV a few years later, I ordered a new Mercedes ML350. My wife is now ready to buy a new car and we are shopping around for a Mercedes E-class 4-door. I still have the RL with 187,800 miles on it and a clock that reads 0:00.
When Alpine engineered this navi unit in the mid 1990's, it looks like they used an 8-bit RISC microcontroller (or something similar in the circuit for clock gating) with an 8KB or 16KB flash and SRAM of 1024 bytes. Does that number (1024) sound familiar? The fella at Jalopnik.com hit the problem right on the nose when he posted his analysis on his website.
When I read that Acura was telling callers that the problem was at the GPS satellites, my blood started to boil. Now I've been waiting to hear that Acura is telling people that they're going to get a fix transmitted to the satellites to correct the problem, but they just need the assistance of the Department of Defense........................................... .....

 

You hardly drive that car. The average driver would have put the mileage you have put more than 2x the mileage on that vehicle in the same time. That's likely why you haven't experienced transmission issues. The oil jets have proven to do nothing to increase the longevity of those autotragic transmissions.

As you pointed out yourself, different cars from the same model and even same year can have different components. It's not hard to imagine that there may be differences in GPS units from one to the next and thus may experience problems differently.

 

i dont even glance at the clock in my cars...
thats what we have phones for! lol

 

Well, the bad tranny units went bad quickly. There are many owners who had issues before 30,000 miles. I saw a post once where this owner had 2 units by 80,000, and needed a third. Acura took a lot of heat from many....many owners over this issue. There are chat rooms hare and on other sites that never seem to end when researching this tranny issue. I have low miles for the age of my car, but it is still 103,000 miles and 15 years of operation. It also represents a lot of local miles, where the tranny actually shifts much more often. My VIN actually took me out of the TSB notice (it was based on the last 6 digits) which is why i probably didn't experience the problem. By then, the units were built properly with the right lubrication. Plus, my extreme fluid changes helped in my opinion. The oil jet was merely a precaution in my view but also helped i think..
I don't know about the NAVI units, but it seems to me that all TLs made anywhere close to my date all had the same units. These must be made in huge batches and shipped to the Acura plant. Maybe a 2002 unit may have some software differences then my 2003, so t I'm not sure how much variability could exist with these units. Plus, it is a problem with many units in different cars and in multiple years. But, who is to say. Only Acura can tell me why.... and i hope they do. I don't like things on my car not to work. When this starts to happen i will get another car. It will take more than a non-working clock for me to get rid of my TL of course , but I still am not happy about this....(-__-).

 

That's interesting info about the clock. I didn't buy off on the gov't satellite story i read here and the Acura Tech i spoke to had no idea what i was talking about either. I'm not versed in the techy stuff you mentioned. I will look at that website. Is there a fix for this problem assuming your info is correct about the problem..? Do you think Acura has this info...? Even if they can't fix it, i am hoping that they are truthful about the problem. They are supposed to contact me at some point. Did your RL clock also go out on 8/16/17...??

 

1024 bytes of RAM shouldn't have anything do to with the problem. The guy at Jalopnik guessed that the navi held the number of weeks since January, 1998 due to "some owners reporting that they found the car’s internal clock had rolled back to January, 1998". That indicates a 10 bit value was used to store the number of weeks (a 10 bit unsigned integer can store a number from 0-1023).

This rollover is certainly possible, just note that 1) A 10 bit value is unusual and 2) Storing the date as the number of weeks is also very unusual. Date values are almost always stored as the number of seconds since a given date. But, in an embedded system with limited memory you do what you have to do.

 

Thanks for the info. Does this mean that the problem can be fixed if Acura wants to fix it...? It seems that the recent problem is that the clocks in many models and for many years all went to 0:00, not back to a time in 1998. Is this the same basic problem..? I went to the Jalopnik website but was unable to find anything about this. I'm not very techy anyway to be honest. I plan on relaying all this info to Tech Support. I hope i have time to call them again tomorrow.

 

See the following September 2017 Acura Tech Line Summary Article:

BTS170801
Navigation Screen Clock Reads 00:00
Affected Vehicles: 2001−03 CL, 2001−02 MDX, 2000−03 RL, and 2000−03 TL
http://www.urvi.net/forumfiles/SB/BTS170801.PDF
http://techinfo.honda.com/rjanisis/p.../BTS170801.PDF

 

Well, here it is Oct. 2017 and my 02 TLS w/upgraded Navi disc clock is still showing 00:00. Those who didnt upgrade probably have their clocks back, but what can we upgraders do? Is downgrading the navi DVD a possible fix?
If Acura cant fix this, they should supply us a pretty fancy Acura clock to put on the dash!

C'mon Acura, fix this already...

 

I have a 2002 MDX w/ Navigation. I've had this car since 2004 and its without a doubt the best car I have ever owned; I signed into this chain because on 8/17/17 my clock started displaying 00:00, and I was unable to adjust it. I was hoping my local independent Acura repair shop could get it functioning, and yesterday they let me know that they'd exhausted all the tricks they knew to reset it. While I'm not surprised that a car with 283,300mi. on it stopped functioning, I am really surprised to read this zine and see how many other Acura's who are also suffering from this problem also had it occur on the exact same date. i did call Alpine today to ask what was being done and they did say they were working on a fix. They also said they'd only known about this problem for a month?? I got the number from a post on this site from last year so I'm not sure how that is possible. While my navigation system is functioning MOST of the time, it is not unusual for a disc reading error to pop up when I start or restart the car, at least once a day, and this has been going on for several years; anyone else have this issue? I've upgraded the DVD twice and am wondering if there is a correlation for those of you who have had the clock start functioning again, if this only occurs with owners who had NOT upgraded the DVD? or, to put it another way, Has anyone who has had the clock come back, also upgraded their DVD? Also wondering if anyone with a 2002 model changed the battery inside the DVD unit and then had the clock start functioning again??
thanx; really miss my clock; hope the display will wake up again soon...

 

I tried reverting back to a previous issue Navi DVD once. The system would not accept the earlier DVD, and would not operate properly, until I re-installed the 2013 Version. I agree. It is a sorry state of affairs that Acura is unable to address this clock issue, in a timely manor. I rarely use the clock function on my 03 TLS, but when i need it, I would certainly like it to be there! The Right Thing To Do, in the interest of good will, would be for Acura to at least supply those affected owners, who have contacted Acura Client Services, with some sort of temporary clock solution!