Here's my current set-up:
-GReddy TDO4
-GReddy type31 FMIC
-TurboXS MBC @ 8 psi
-Stock FPR
-Stock fuel pump
-Nology wires
-NGK 7 series plugs
-Timing NOT retarded
-DSM 450cc
-VAFC is set at: 1-4K= -40% and above 4K= -37%.

I used to have it set at: 1-4K= -35% all across but a MIL/CEL popped up a code 45 (too rich) and 72 (misfire #2 cyclinder). After reconfiguring it to my current set-up which is listed above, no more code 45 and 72. But now, a code 13 which is "Barometric Pressure Circuit High/Low Input". How can I fix this? I should be able to set my AFC to compensate for that right? Thank you for your time......


[Modified by thermalfi'd16, 10:59 PM 1/9/2003]

 

ok i have the same problem. i think it's a thing with the 99-00's. I talked VaporTrail and b18bturbo about it... i doubt u can get rid of it. Viren said it was because of too much adjustment on the afc. I realy wouldn't worry about it too much. I have the SAME problem. I've been driving around with them for 3 months now car seems normal. i reset it every now and then when i'm tired of seeing the amber CEL. As long as ur not getting the code 72 anymore i wouldn't worry too much

 

hhhmmmm. I cant stand staring at that MIL. There has to be a way........

 

i have a 00 civic Si and am using the AFC hack and get no check engine lights

maybe it's cause i'm using a CTR ecu and not the Si one

 

i have a 97 type r with 440s and a vafc, not using the hack. i still throw 13s sometimes, and im guessing its due to the amount of fuel im pulling out.

 

Well, I just received a PM from EE_chris. He mentioned that the barometric and MAP is the same sensor but different output. If that's the case, then this MIL/CEL 13 can affect the fuel management which can lead for the ECU go on a "limp" mode. Any input on this?

 

Sorry, but I need to bump this up for clarification...

 

i had same problem, not anymore, i got a p72 obd1 ecu and the jumper everything is tight now, oooooooohhhhh my Giiiiizzzzzzadamn this **** is fizzzaster now.......

 

>>ok i have the same problem. i think it's a thing with the 99-00's. I talked VaporTrail and b18bturbo about it... i doubt u can get rid of it. Viren said it was because of too much adjustment on the afc. I realy wouldn't worry about it too much. I have the SAME problem. I've been driving around with them for 3 months now car seems normal. <<

This is exactly the same situation for me too. I've got a 99 EX ECU. there doesn't seem to be any negative effect other than the CEL being on all the time. I'm throwing a code for my secondary O2 sensor as well, but still... those codes do not cause the ECU to inhibit performance IMO.

 

i have ran 1bar with the afc hack and no cel

 

yah... we're cursed with limp dick obd2's

 

Any more info on this? Now im having this problem!

 

LOL!! no offense...it just made me smile a bit...

 

i also had the CEL 13. ONce i got sick of the light so i took the bulb out . Needless to say, i put the bulb back in and took that afc hack **** out and bought an aem ems...wideband is on its way.

 

i'm running the hack with 440s on my '97 D16Y8. no CELs for me!

 

the code 13 is nothing. It's b/c we are obd2 it will show up. I'm sure if u switch to obd1 you will not throw the code anymore. It's not in limp mode so I it won't mess with your hp at all.

 

I am obd 1 and im throwing the code.

 

The barometric pressure sensor is on the ECU board itself, different from the MAP sensor.

 

So what would cause this code to be thrown?

 

I throw the code 13 too. But there is no performance loss. If there is a fix, I'd like to know. But if I recall throwing the code has something to do with the difference in what the map sensor and the baro sensor is reading. Because of this difference the ecu thinks that the baro sensor is damaged. So I'm pretty sure that there isn't anything we can do about it with our OBDII's.

 

He hit the nail straight on the HEAD with that.

So basically code 13 = something ALL afc hack and most greddy users have to live with as obd2. Plain and simple. If you need to check other codes, you have to occasionally jump the service connector and see if you have anything besides just a code 13.