Unsung

So the next problem I'm dealing with the car is the ECU. If you haven't been following my posts, the problem is the CEL comes on after 5 seconds, then super, and I mean super, rich conditions.

So I decided to throw in my ECU into my buddies car, same injectors, similar setup, etc. Start up the car, runs fine for 5 seconds, CEL for him too, car bogs and dies. So obviously something is wrong with the ECU/Basemap.

My question: What are the signs of a fried ECU? Does it sound more like a bad basemap? Just trying to diagnose and wanted some opinions. Thanks.

rjardy

what ROM editing program are you using?


Rob

Nid Styles

Fried ECU.

Basemap wouldn't cause it to throw a CEL. Unless there is glitch in the actual burn somewhere, but it sounds like the O2 circuit is frizzled to me. Wouldn't be the harness because he tried it in two different cars, and it did the same thing.

dabrown

Actualy a basemap that has the wrong sensor enable will cause a cell. I would try cutting the jumper as well to verify that the ecu is not fried.

Nid Styles

<TABLE WIDTH="90%" CELLSPACING=0 CELLPADDING=0 ALIGN=CENTER><TR><TD>Quote, originally posted by dabrown &raquo;</TD></TR><TR><TD CLASS="quote">Actualy a basemap that has the wrong sensor enable will cause a cell. I would try cutting the jumper as well to verify that the ecu is not fried.</TD></TR></TABLE>

Like bad calibration? Sorry, never had that problem.

hulkhb

TTT we need this issue resloved.

5thgencivic

<TABLE WIDTH="90%" CELLSPACING=0 CELLPADDING=0 ALIGN=CENTER><TR><TD>Quote, originally posted by nd_styles &raquo;</TD></TR><TR><TD CLASS="quote">

Like bad calibration? Sorry, never had that problem.</TD></TR></TABLE>

I was throwing 2 codes because my P28 didn't have a baro sensor(not a USDM) A code for the baro and an injector error. The car would not stay running. I had another basemap done with the 2 disabled and everything has been fine since. Could have been a bad basemap as well, but those things still needed to be disabled.

Unsung

Just tried another 550cc basemap in the same ECU, it had the same problem, but started up with a CEL also. So far the only ECU that hasn't had a CEL is when I put my stock ECU back in.

simple4012

might be a sloppy install of the chips

Unsung

<TABLE WIDTH="90%" CELLSPACING=0 CELLPADDING=0 ALIGN=CENTER><TR><TD>Quote, originally posted by simple4012 &raquo;</TD></TR><TR><TD CLASS="quote">might be a sloppy install of the chips</TD></TR></TABLE>

I wouldn't doubt it. I'm pretty much an electronics idiot.

Mad Cow

Have you tried to pull the code?If not, try it.. see what the code is.

My first guess was code 43 (fuel supply, too rich or too lean), but that shouldn't cause you to go super rich.

Unsung

ECU has never stored codes since day one. I've used this same p28 when i was NA with the Kenji program. Even when I was NA and would ocasionally toss a CEL, non limp, the code would never store.

Thats why I swapped back in my Stock P2T ECU to see if I could pull a code, but no code came up in 5 seconds like the p28. I let it "idle" for about 30 seconds with the stock ECU and still no code.

Unsung

I've used this harness for 2 years previous to the turbo install.

5thgencivic

Have you tried more than one basemap? If your ECU is not storing codes there is a wiring problem, chipping problem, faulty ECU or something. I had a bad basemap, but my ECU would always store codes.

Unsung

I've tried 2 basemaps in this ECU. Remember this ECU/Harness worked fine for over a year until I put the turbo kit on. Pretty sure I cooked the ECU somehow. I'm going to see if my buddy can come over after work tomorrow so I can give his ECU w/ 550cc basemap a shot again in my car.

PHiZ

uh, a complete description of your setup might help. We don't know if you're talking hondata, or elsewise.
-PHiZ

VTC_CiViC

So you've tried the same ECU with different maps in different cars with the same results?

Call me crazy but it sounds like a dead ECU to me.

Unsung

Problem somewhat solved. ECU is bad. Put my buddies ECU in my car and it runs fine.