Well I was going to work at around 6pm and I was tring out the 0-60 on my AP. So I gun it (not too much) and when I threw it in third once it hit about 5,500rpms the car bogged badly. I quickly threw it into neutral. I stopped to check it anything came loose but I did not see anything. I tried it again and it did not bog again. Any ideas why and if anyone had this happen to them. I'm using the stage 2 93 octane V100a with cobb TBE w/ test pipe, cobb intake and Megan o2 housing.

 

Ok, so a friend here at work wanted a ride in the evo with all the mods that I installed and again the car bogged at 5,500 rpm and it threw a cel. I checked the code with the AP and its a P0234 (Engine Overboost Condition). I was not paying attention to the boost gauge so i dont know how much boost it was pushing. Any ideas what caused it. I did reset the ECU and the code is gone.

Christian please help!!!!!

 

on the STRI boost gauge you can press the red extension button (fast tap of button) and the gauge will give the last highest boost peak....so even if you didn't notice you should still be able to go back and check it I think.

so far I've not had that happen...before the o2 was on had you done hard pulls in third past 5K? I would assume you had.....was that the first time then you did so since the o2 was on?

 

I did pull it before the O2 housing was installed and it did not occur. So I'm guessing the addition air flow of the O2 housing is causing that code? I have to recheck the hoses to make sure everything is tight. Well after I turned off the car I realized that i can check the peak with the STRI gauge but when i went to check it didnt show the peak. I guess once you turn it off the peak memory resets itself. I'll try again tonight when i go into work.

 

Bump for further updates to the COBBFORUMS thread on this issue

 

Mine bogged in a simliar way earlier today right around 5000-5500 it just lost power it only did it once and hasnt done it since then. I just have a different air filter and a tbe has anyone had many problems with over boosting with the off the shelf maps.

edit: mine did this in 2nd gear btw

 

sounds like you may be hitting fuel cut due to over boost. I.E. the car may be making just a hair to much boost at a requested field due to the 02 housing. A quick touch up to the wastegate Dutycycle should correct this. If I had the ProTuner EVO software I'd do this for you for free, but it is still a few weeks out My guess is that Christian can make this change (assuming this is the issue) and send back the map.

Another alternative is to try a lower wastegate duty cycle map. Check here first:
http://www.accessecu.com/accessport/evo/06EVOMaps.html

Hope this helps.

Stephen

 

Which map would I use to lower wastegate duty cycle? I'm currently running the stage 2 93 oct v100a, which I think is the latest updated map from Cobb. I would assume the O2 housing did have something to do with it. It happened again yesterday night but did not throw the code like before.

 

If the car is hitting fuel cut, its definitely running outside the intended tune range and could be knocking badly. If the AP has any way to log knock, I suggest getting a few logs of knock to make sure you're not slowly killing your motor each time you go WOT.

 

The code throwing after doing it multiple times points to fuel cut. However, I've never heard anyone refer to fuel cut as "bogging." It feels nothing like a bog, but rather more like hitting a brick wall. If that's what you mean by "bog," then it's definitely fuel cut. This should not be happening with the Cobb AP, because I'm sure they knew to deal with fuel cut in their base tunes...at least I hope.

 

Warrtalon, you are correct, it is like hitting a brick wall for a breif second (fuel cut). At the time I couldn't explain it right so i just wrote "bogging". I added a megan O2 housing to the stage 2 map which as per cobb should only consist of the TBE and cobb intake or stock intake. I'm not sure if that is causing the hesitation. Once the protune is released i do plan to get it tuned.

mrfred - The AP only allows me to view realtime knock count but it does not allow me to log it. At the time of the fuel cut i was not viewing the knock count screen but I plan to test it out soon.

 

I'm gonna hook my AP up later tonight and see if I'm getting any knock as well cause what ever happened earlier freaked me out but it only happened once so I dont know

 

Tape it to the steering wheel. :-)

 

I'm just curious....The Evolutioner said he felt the "bog" at around 5500rpm....wouldn't fuel cut come in at 7600rpm.....would the suggestion be that maybe by accident the map lowered that fuel cut point?

 

misfire for fuel cut. But fuel cut is like an instant Thing feels like you hit a wall almost.