I have a 1991 Accord that I did an F23A (99 Accord engine) swap in. I used an F22B intake manifold and TB. It has a chipped P28 with a Crome basemap on it. The car idles, runs and drives great.

It has no check engine light after start-up and idle, and I can drive it just fine until deceleration while in gear (slowing car down with engine while in gear) and then the check engine light pops on. It will still run fine after check engine light is on, but it's annoying. I checked codes and I get a code for my MAP sensor which doesn't make sense because I have tried two different MAP's. I've checked the wiring and it's all right. Vacuum could possibly be off because of the difference in the original F22A's IM and the F22B's IM but it runs and idles fine.

Any ideas on this bizarre problem?

Thanks!
Nick

 

Do you have any way to datalog what engine conditions the ECU is seeing when it trips the MAP DTCode?

 

I've never datalogged before, the ECU does have the port and I own a HondaLog from moates.net http://www.moates.net/product_info.p...products_id=79 but I don't have or know of any software to datalog with that's free.

Thanks for your response!
Nick

 

Well if your only running a Crome base map that could be the problem. If you haven't had this setup tuned that is what I suggest you do? When you have it tuned then you will be able to see what the problem is.

There is freeware dataloging software out there called Freelog. But I've never used it myself. I hear it is pretty much a "you get what you pay for" type deal. Free so don't expect much.

 

I'd love to have it tuned but I'm trading the car and I just wanted to trace down and fix whatever is causing this problem. Do you have any other ideas?

Is there a special channel that's machined out in the TB that goes to the map?

 

bump

 

Got problem figured out! Thanks for your help!

 

Would you like to post what the solution to the problem was so maybe someone in the future could maybe learn form your adventure?

 

Yeah it was the wrong code, I had already fixed the MAP's code previously but kept getting a code for a different thing which happened to by my VSS.