Hondata

i have a gm 3bar map sensor after i boost sometimes the map sensor code comes on its really annoying.. makes the car go into limp i have t utrn thwe key on and off

after i got the car tuned it got worse maybe because of more psi...

everytime i boost after i let off it throws a code
?? wtf ?

here is my tune

please post a datalog showing the problem

i didnt datalog.. it was on the dyno..

its not gonna matter.. its just gonna show boost and when i decel it throws the code.. thats it. it reads perfectly in accordance with the dynos sensors ..

Until you provide a datalog showing the problem, it is impossible to speculate what the problem may be.

try another known good 3 bar mapsensor. i've seen a run of a few going bad. tune a car and it runs great for a week or two. car starts idling poorly and reading erroroneously. swap a new sensor in and no problems anymore. you might also want to put an inline filter (like the type supplied w/ electronic boost controllers) to keep anything from blowing into the sensor.

Do you have closed loop setup?

I read somewhere a long time ago, that during a prolonged decel the ecu will switch from open to closed loop, if closed loop is not disabled ( or setup ) this will throw a CEL. This was back in my Uberdata days so i dont know if there is any relevance.

I cant remember where i read this, and i cant be sure that i have given accurate details, maybe someone can agree/disagree.

Just a thought. Good luck.

jordancivic wrote:Do you have closed loop setup?

I read somewhere a long time ago, that during a prolonged decel the ecu will switch from open to closed loop, if closed loop is not disabled ( or setup ) this will throw a CEL. This was back in my Uberdata days so i dont know if there is any relevance.

I cant remember where i read this, and i cant be sure that i have given accurate details, maybe someone can agree/disagree.

Just a thought. Good luck.

i used to drive/tune my own car exclusively with closed loop disabled so i could run leaner and increase economy. never had that issue. i'd have to disagree on that account.

Yeah, think it was a glitch with the UBer code or something, like i said i didnt know if it would have any relevance here.

Thanks for clearing that up anyway.