So I recently got Auterra Dyno-Scan for PalmOS, which is really cool so far btw, and plugged it in to see what my car had to say. I have a 7th gen 2003 Accord V6 6MT (Manual) Coupe and I'm seeing the following DTCs and was wondering if anyone knows what they mean:

P1700
B3EA8
B11BB

The first one is always there and the second two show up occasionally. I tried to clear the codes and they all come back after a few seconds. I'm wondering if they are related to the OEM Navigation System install I did - my original car did not have the Navi. The car functions fine and the CEL is not lit.

The Auterra software didn't know, google wasn't helpful - all I could find was the P1700 trouble code of that number for Subaru that was for AUTOs, and I couldn't find anything on here.

 

A p1700 is the a trobule code indicating a transmission trouble code is stored. Unless you have the factory Honda software, you will have to go to your dealer to have it diagnosed ( ka-ching ) makes techs like me wealthy.

 

Is the code more descriptive then that? Or is it that generic?

Could it be caused by activating the rev limiter?

 

I may have given you some bad info.... If your car is a 6-speed, it won't have a trans control computer.... is p1700 really the code you got? Because Honda shows that that code doesn't even exist. Recheck the code and repost. BTW.... for all of you V6 - 6-speed owners out there.... I would advise that you not hit the rev limiter.... EVER. I have seem some valve damage from over revving, and it isn't covered under warranty, because there is a little tell-tale code that tells me as the technician exactly what speed the engine was running at (over-revving) and for how long. One case I remember was some guy that was on the freeway, tried to down shift to fourth and hit second instead, grenaded his motor. ECM said it was at 12,000 some rpm for 4 seconds.... No warranty for you, sorry its abuse.

 

I e-mailed Auterra, the makers of the PalmOS OBD hardware and software that I own, and here is their reply:

-----

We have diagnosed this Honda problem numerous time. The issue is a software
bug in some Honda ECUs. The issue is that instead of returning blank numbers
00 00 when there are no codes, the ECU actually returns bytes from whatever
the last message was (essentially random garbage). The OBD II specification
say it must be 00 00 when no codes are set. If anything else, then interpret
as a DTC.

In short, the scan tool is operating correctly and it's a known Honda bug.
Just ignore any messages you can find a definition for. They are not real
codes.

-----

This seems like a legitimate answer to me. None of these codes make sense for my car. Although I wonder how the Honda's HDS deals with this. Maybe it doesn't quite support the OBD2 standard and the Honda scanner extracts DTC using some other sideband information.

I'm just happy my car is OK.