I installed OBDI chipped ECU into my '01 GSR.

I get a CEL as soon as VTEC engages. I am unable to read the code because it clears as soon as I shut the car off.
So if I shut the car off and start it again, there is no CEL but it comes back as soon as I get to VTEC engagement RPM.

I got the chipped ECU from this seller on Ebay: alex-the-ecu-guy
I haven't messed with the ECU at all besides creating a basemap in Crome for my bigger injectors. I do have a wideband and the car is running perfectly fine at low rpm.

I have a feeling I got a bad ECU. The ECU is a P06 which tells me that it was converted to VTEC but perhaps it was converted incorrectly. The seller does not accept returns but I'm pretty sure I can get my money back through Ebay. Before I do that, I wanted to ask for advice... Maybe somebody had a similar problem and can confirm that this is a bad ECU or maybe I am forgetting something?

Any help greatly appreciated.

 

Check it *before* shutting the car off rather than have us guess. Not very difficult. Figure out if it's the likely candidates, VTEC Pressure Switch or VTEC Solenoid, causing the code. Disable in the program if it's Pressure Switch, or diagnose if it's the Solenoid. Fix the problem or ask to return/exchange.

 

I didn't know I could pull the code while the car is running. I guess I can just put a paper clip in the service connector when it is running?

I don't think there is anything wrong with my motor or the solenoid. VTEC works fine with the stock ECU.

 

Yup, that's all you need to do.

If you don't have a pressure switch or you do and that's the error, simply disable it in your EMS if you're sure your engine is getting proper oil pressure.

 

Try to save a buck, end up spending twice as much :-)
People sometimes never learn.

 

First of all, thank you guys for the help!

What I did today:
I set VTEC to 4500rpm and reloaded the map.
Drove the car.
VTEC engages and the CEL doesn't come on when VTEC engages.
The CEL comes on around 5500rpm (which is roughly what I had VTEC set to before and that is why I assumed that VTEC engagement triggered the CEL)

I pulled over and read the CEL.... two long, one short - code 21.

I am not sure how to diagnose the problem. My VTEC solenoid should be in good shape because I never had this problem before OBDI conversion. My oil level is good. I shouldn't have any problems with my wiring because VTEC does engage perfectly fine.

Any ideas?

 

Hey man Im having the same problem. I have an h22 swapped into my accord and the cel code 21 is coming up for me. My soleniod is fine has nothing wrong with it and it is getting power to it. but my light comes on when vtec is supposed to hit. The other thing is I am also tuned by crome.

 

Did you try cleaning the screen on the Solenoid. Doesnt hurt to do so.

 

I did that already and before and after it all looked good. So there has to be something else that has been over looked.

 

Sounds like either a bad VTEC High-Side Switch at board location IC14.

It is a simple fix, but it would require you to source the proper part and replace the faulty transistor.

The wiring and vtec solenoid are ruled out in this case if you don't get the code with a stock vtec ecu with the same engine harness.

 

Thank you for the help.
I decided to find and try a known good chipped ECU and see if that fixes the problem.

 

I've seen this before...

If you have a '1720' or '1980' ECU board, the transistor at Q26 is the wrong one. They installed a PNP rather than NPN transistor. I made this mistake a couple times back in the day and beat myself up trying to figure out what was wrong.... Look on the transistor in location Q26 and see if it reads B1030 or D1423

Ditto..

 

Thank you guys. You are correct.

Purchased an ECU from Phearable, plugged it in, drove and took it to 8000rpm a few times, no CEL. Returned the other ECU. Problem solved.

Thanks again for the help.

 

this just happened to me too...well after reading your guys info! thanks alot! i believe it's the chip i bought too...maybe it's not setup up for my ecu...as it might be slightly different like you guys said. b/c i know my ecu is not the problem....and my old chip never throw that code. thanks!