Evil-EK

A buddy of mine put a obd2b to obd1 conversion harness in his 2000 si. The car runs but when it gets up to normal temp the cel comes on. It is throwing a code 43 (fuel supply). I have tried resetting the ecu and have checked for other fuel related issues but I find nothing. Got any ideas?

Ministry

I would check the injectors, fuel filter, fuel pump, fuel lines.

this didn't happen until he switched to OBDI ecu?

Evil-EK

No he had a cel for secondary o2 and decided to just convert the car to obd1 to eliminate the secondary o2. I donated the p28 and he bought the harness. I have checked all the above but the filter. My turbo ls/vtec threw this code and it was the primary o2 going bad that caused it.

shifty35

This is just a stock P28, or a chipped one? What program/settings? Do you have a copy of the bin?

Could be the program is running really lean/rich at idle, making the computer think something is up with the fuel system.

Ministry

<TABLE WIDTH="90%" CELLSPACING=0 CELLPADDING=0 ALIGN=CENTER><TR><TD>Quote, originally posted by BigBlockH22atch &raquo;</TD></TR><TR><TD CLASS="quote">My turbo ls/vtec threw this code and it was the primary o2 going bad that caused it.</TD></TR></TABLE>

well have ya checked that? I kinda doubt a clogged fuel filter would cause your ecu to throw a code

Evil-EK

na it is a stock p28. and I dont think the o2 is causing it. the car only has like 43k miles on it.

IHateJDM

friend of mine just had that code (64K miles on his) and his o2 was the cause. He was throwing a code for o2 also though. Is the Fuel system code your only cel?

Evil-EK

Yes the fuel system code is the only one.

IHateJDM

does your gas cap seal the tank correctly?

Evil-EK

That is a new idea. I totaly over looked that. I will check it and see. Thanks guys.

thehatchninja

maybe you should chip it for b16, it will never run right if you don't, even if it isn't throwing codes.

mwieczorek43

<TABLE WIDTH="90%" CELLSPACING=0 CELLPADDING=0 ALIGN=CENTER><TR><TD>Quote, originally posted by thehatchninja &raquo;</TD></TR><TR><TD CLASS="quote">maybe you should chip it for b16, it will never run right if you don't, even if it isn't throwing codes.</TD></TR></TABLE>
I agree with what he said. Anything worth doing, is worth doing right.

pdiggitydogg

The problem is probably because its running the d16z6 program for a b16a2.
It needs to be chipped to simulate the p30