anybody using an FIC and throwing this code?

its some TDC sensor for one of the cams i think - i forget.

seems to be a common problem on the aem forums - anybody find an answer?

 

Does the fic tap that line? It's probably sinking too much of the signal.

 

yes it does. i figure its eating up a bit too much voltage - i know the wiring is correct because i ran the harness last night with the AEM bypass plug and had no issues.

 

Maybe try putting a resistor on the fic line.

 

i have acquired another unit in the meantime. same model number, same revision. this one works just fine - no codes!

some of these units are bad.

however, now with the new one i have another issue. i can feel the car hesitate somewhere around the 3500rpm mark. i'm not overly concerned with this really, but i would definitely like to rule out any knock/detonation potential. would the car throw a code if it detects a knock big enough to cause hesitation?

 

Not really. The F2x is too loud at WOT for the sensor to be usfull. The ecu stops listening at wot.

 

this is at normal driving, sorry forgot to clarify

 

You may get random misfire codes, but I strongly advise against using the cel as a tuning tool. Det cans are the best way to go. Are you running a wideband, and does the fic offer datalogging?

 

is this the standard fic or the one modified (now make different model# for my 2000-2005)?
if it is the standard fic you need to send in to have updated to your model year car.

 

it is the correct unit.

i got a hold of ANOTHER 1912 and the CEL is gone. this old one is going back.