ok my tuner came by and burnt me a basemap for my new settup. car started but check engine light came on so we did a quick test with a paper clip. But that didn't help because didn't get any blinks at all. the light just stayed on. So my tuner buddy reburnt another map taking out the knock sensor. This time when i started the car, it was fine but then 2 seconds later the check engine light came on again. The car was dripping oil from a loose connection on the oil feed line on the firewall so we had to stop things. He had to go so I just finished repairing the oil line.

Now the car idles fine at 8-900rpms steady with oil pressure @ 20ish psi at idle but the check engine light is still on. anyone got any ideas? i've got a 3bar map sensor piggy'd onto the stock map with the 3bar unplugged and the stock map sensor plugged on. Thats about all I can think about.


Modified by alfee at 4:06 PM 1/29/2006

 

From what I know, if you don't get any blinks it's a sign of a bad burn or ecu. Any blinks you should be able to trace to the problem.

 

have you tried another ecu?

 

what is your fuel cut set at?

I have had my fuel cut set on 9 on a stock map sensor map, and it always triggered the always on CEL. I redid the map everything pretty much the same except fuel cut was set to ~24.....no light after that.

I don't know it that'll help, but it was something I noticed. Post the .bin if you can.

***above is with uberdata***

 

well i doubt it's the ecu since the last time i drove my car it was on the dyno and the motor blew. Since then the ecu has not been used at all and only the chip has been re-burnt and started about 3 times total this week from then till now. All i can think of is the coolant temp sensor. For some reason i pulled the two wires (red & green) out of its socket plug when taking the head off awhile back when the motor blew. But I'm sure they're on correctly with the Red wire on top and the Green on bottom. Can someone confirm this for me?? looks like this
Also, I let the car idle for about 15minutes and it seemed fine with good water temp about 35-40% i'd say. so...HMMMMMM???

https://honda-tech.com/zerothread?id=1478314

 

so the second time around the CEL came off then came back on after 2 seconds? if so then u have a code. did u check the code after u burnt the chip the second time around or was it still solid?

 

yep, the light was off the 2nd time around at startup, then 2 seconds into it the light came on. I was happy at first to see it was off, then shoooot it came back on. Haven't checked the code as my friend (tuner) had to leave. So I'm guessing its a problem related to the map and how its configured/burnt? Just as long as its not a bolt on problem hopefully it can be squared away.

 

check the code urself and see what its throwing. if the light goes off when u start the car and then comes back on u have a cel code. it doesnt mean the ecu is bad at all or the burn is bad. maybe u dont have an O2 sensor and ur tuner forgot to disable it. if the car revs clean to the redline then the burn is fine, u just have issues with a sensor in the car

 

If the ECU is setup for datalogging (J12 removed), you won't be able to flash the codes using a paperclip since the ecu is now in full-duplex mode.

 

<TABLE WIDTH="90%" CELLSPACING=0 CELLPADDING=0 ALIGN=CENTER><TR><TD>Quote, originally posted by .nate &raquo;</TD></TR><TR><TD CLASS="quote">If the ECU is setup for datalogging, you won't be able to flash the codes using a paperclip. </TD></TR></TABLE>

what???? since when? my ecu is setup with datalogging and i can check the codes with no problem by jumping the service connector?

 

hrmmm thats odd??? haven't heard this before. And YES my ecu is setup for datalogging w/ a nokia cable. Can anyone else confirm/ or deny this ECU question??

Currently, I'm out of town for the week and won't be able to get to test the check engine light till the weekend. I'll post up my results soon as I get'm.

 

Let me clarify: Jumping the diagnostic connector won't flash the CEL if J12 is removed. This allows for better datalogging, but breaks the diagnostic connector.

OBD1 J12

 

perfect

I'll take a look at my ecu asap