I'm running the map limiter...similar to the afc hack. And I'm throwing a cel 13. I understand that the obd2 ecu's are picky. But what I'm wondering is would running it richer or leaner remidy the code? Has anyone fixed their cel 13 problem? If so...how?

 

I'm constantly getting the CEL 13 with my Greddy kit on stock boost. I just ended up resetting the ECU because it just looks annoying to have the light on. You may already know this, but the code doesn't throw the car in limp mode. In any case, from what I hear, don't expect this problem to go away unless you get an EMS like Hondata or AEM.

 

I've had the same problem for months now. I have been street tuning my car alot lately and i am yet to get rid of the CEL.

 

Yes, I understand that it's not throwing the car into limp mode. But I kind of want to get rid of the cel...just incase I get another cel, I won't know unless I check it randomly.

So what I was wondering is if there is a way to find out what the ecu doesn't like about the readings it's getting. And if anyone got rid of their's by adding or subtracting fuel with their afc or map limiter.

Anyone get rid of a cel 13?

 

It has nothing to do with how lean or rich you are. Go here for your cel codes:

http://jdmfan.com/index.php?information=dtc

This is the only cel I've ever gotten with my Greddy kit. It seemed to happen mostly when I was in traffic. I've heard it has something to do with where you locate the IAT sensor, so I moved it to right before the throttle body, instead of after the filter. So far it's been fine, but I only got that cel about 5 times or so anyway.

 

you guys using the hack? i got that cel, i believe its because the voltage output by the map sensor to the ecm is too low, due to the vafc hack , -35 thru -50 settings?

 

change out your plugs, see if that helps

 

^^^ what I did...

 

yeah, I was told the same thing by the owner of a local speed shop. I asked what codes might pop up with the AFC hack -- after i explained what it was -- and he said a 13. he told me what it was and said that since the OBDII ECU is sensitive, it'll pop a 13 because of the aggressive adjustments from the hack setting.

 

Anyone running the hack and most with stock greddy setup will have this problem REGUARDLESS of what you do.

The code is for a faulty BARO sensor which on obd2 cars is built into the ecu. FYI non of your baro sensors are broken, but due to the drastic difference between the readings the baro picks up and the map (because of the hack and blue box) the car constantly thinks the baro is broken. Hence we all have to live with a virtually permanent code 13. Its just one of the small happy things we live with because we're not standalone.

Cliff notes: ALL AFC HAC and MOST GREDDY USERS have this code. Nothing you can do about it besides switch to standalone.

 

i agree wit you 100%

 

Thanks for that explanation shadowdawn. That makes sense. Soooo, since we've just got to live with the cel....how do you all know if you get another cel? Do you just check it randomly? Or just cross your fingers and hope that you don't throw a cel that will throw you into limp mode and you boost too much. Any tips?

 

Yep, have to check it randomly. Thats what I do.

And dont' be one of those people that take the bulb out and never check your codes, you'll probably blow something up doing that

 

you'll know when your engine goes into limp mode. If you can't tell, well. . . . For one, the car will idle higher than normal. Secondly, if you try and accelerate from a stop, the engine will bog, possibly backfire, and feel sluggish in general. You'll also have a hard time getting past 3K rpm. my engine has gone into limp mode several times due to a defective GReddy blue box.