go to sears and buy a battery with a warranty on it, plus get money back for taking in your non working battery.

 

I ended up taking the Honda battery - they knocked $80 off the price. Also, the Honda replacement batteries are now 100 month warranty. First 3 years at full cost for parts and labor and pro-rated after that.

Car is running much better with the new parts. Hope this solves the problems I've had for the last 5 months or so.

 

I just called the Honda Automobile Customer Service line (1-800-999-1009) and found out that my car is included in this recall. I went to the Honda owners link website and my car has NO recalls listed, so I assume they are keeping this under the radar so as not to alarm owners that is it anything major.

Reguardless if you think your car is running fine or not you should call to see if your car is included in this recall / Product Update.

I have had my cataylic converters replaced 2 times in the past 3 years and i think this would be the root cause of the problem. i was informed that they will be replacing them AGAIN when I take my car in for this update since my car has a history of bad cats. Additionally, the product update says they will be updating my IMA system, it will be intersting to see how my milage does after this is done.

I dont think anyone would like to spend the 1250.00 for the new O2 sensors / cats that are on this car. I am really glad I bought the extended warranty (7 years / 100,000 miles).

Before i read through this site my mileage was about 50 - 52 but since i refilled my tank i am currently at about 62 MPG. Thanks to all you guys out there with all the good tips.

Take care and make the call remember it is your cars fuction to perform to its fullest capicity, why limit this by ignoring something like this.

 

does this affect canadian HCH as well? does anyone have the link to the EGR valve recall too? I want a letter photo just like the first post of this thread so i can shove it into the car's dealers face.

this thread should be sticked!~ i was looking for this kind of thread when i was interested in a HCH.

 

On my search for catchup maintenance lists I was directed to this upgrade. I called Honda at the number, updated the owner information (apparently a different database than OwnerLink) and was told that my car had already received the update in July 2005. I guess I should be glad that the previous owner was so diligent, but is there a way *I* can determine if it was carried out? Haven't other VIN recall type updates made a mark/punch out on the VIN plate or something to indicate a particular update?

 

Yes

This was the 62 mile bug.
Zero one of your trip meters.
Drive for the best MPG you can - like drive on a flat highway at 55 MPH for 61 miles.
At about mile 61 notice the MPG meter.
Starting at mile 62 start driving to get VERY bad MPG, like racing up a hill for a few miles, or start and stop driving in the city, flooring the accelerator with the AC on.

If your car was one of the ones that had the bug and the bug is not fixed you will suddenly get MPG that is VERY low, like 20s or 30s.
This is because the bug makes it start averaging from scratch at about mile 62 even though the MPG meter continues to advance to 63, 64, 65 etc.
So even though the meter is displaying, say, 65 it is only averaging together the last 3 miles of driving.

If your car never had the bug or the bug was fixed your MPG will go down but not as drastically (maybe only around 10 MPG lower by mile 65.)
this is because it is operating correctly and averaging ALL 65 miles together, the 61 good ones and the 4 bad ones.

 

I thought the 62 mile bug was the 2006 models only, Larry has a 2004.

 

I'll take a look next time I hit the highways where I can go 62+ miles in row.

I have noticed that it sure does not take much time to destroy your average and takes forever to build it back up. It seems like I can lose 1-1.5MPG driving in my parking garage and it will take the rest of my 50 mile commute to bring it back halfway. Or let my wife drive the car and guarantee it goes down 3-4MPG, she needs to read up in here.

 

An interesting note: 62 miles is approximately 100 kilometers. (Being a software engineer by trade, I find this kind of interesting, and suspect some sort of power-of-ten or limiting problem.)

 

Yes, tckma, that has been discussed here before. When people were first noticing the bug, folks just noticed it happening "somewhere" around the 60-65 mile mark. A few pinpointed 62 or 63 miles - triggering the metric 100km-theory arose, and others piled on, after noticing that the issue DID occur between 62-63 miles. It can't be just a coincidence. Search around here and you'll find a nice long thread about it!