Recent content by 08Bullitt_0067

Mods? Does the idle climb up and stay up? Or does it start to surge up and down? Do you have the ability to datalog?

Just curious what cams you have and how loud your car is? I have a whipple, comp 127500, lts, mac prochamber, no cats and corsa extremes. Very loud when in the throttle and barely hear any whine, if at all. Put my OEM bullitt axle backs on, and yeah now I can hear the whine a lot more. Sent...

Yes I'm using the built in IAT with the MAF. Thanks for the suggestion, I started looking into relocation kits. Would i need a tune adjustment for that? Also looking into a WB setup. Would one of those replace one of the upstream O2s? Or would I replace one of the down stream O2s (no cats)...

Confirmed... plugged the hole with my finger and it starts running back to normal. Thank you guys for the help. It really was a learning experience sharing your knowledge.

I think I found the issue. I did the induction smoke test and found a threaded hole in the SC manifold on the passenger side. I attached the pic. Based on what pictures i see in the internet, it looks like a threaded plug belongs there. I guess is must have broken loose and vibrated out...

Kam reset didn't make a difference. Ordered a smoke tester. Sent from my SM-N960U1 using Tapatalk

I installed a new set of ntk sensors. The passenger side looks like it was the OEM ford sensor and the driver side was a newer Bosch. Fired up the car and it was behaving similarly, maybe a little better. New scan data shows both sensors reading similarly around 0.01 with some fluctuations...

I finally got the car up on jack stands. First round of visuals, everything looks OK. I pulled out one of the Upstream O2s and looked up the serial number. 0258005717 shows it to be a bosch sensor. I have a couple of NTK 22060 on order. I don't need the extenders as I have the MAC headers...

Wow this is some good info from you guys... 1.) I believe they are the OEM O2s. I never changed them when i installed my headers way back in 2010. After I dropped the valve and killed the OEM motor, I brought it to a shop to have a new (built) motor put in and I added a used whipple to that...

Thanks Dino. So it was the drivers side sensor that was pegged at .07-.08 indicating the issue. Good to know. I'll be checking everything there and if visual checks don't show anything, I'll go with a spray method. I haven't done that for year, but im sure the concept is still the same...

So after a few weeks of dealing with technical issues with FORScan Lite, getting slammed with work and then a sinus surgery, I was finally able to get a scan with the card idling up to running temp. Also a KOEO and a KOER test. First obvious things i noticed: 1. At startup, FUELSYS1 is Closed...

Hopefully tomorrow i can get some time on this. What kinds of things should i look for when data logging? If it's too much to explain what "normal" values should be, I will try to post the log here. Are there other resources i can look at to let me know what values and ranges i should expect...

I spent most of the time i had trying to get FORScan to work. Long story short, the custom tune prevents the software from reading all the vehicle info when it connects. The FORScan team helped resolve that. So now I can datalog. What things should I look at and what values are "Normal"...

Maybe this is or part of the issue. I just got the bluetooth odbII dongle today so hopefully ill have some time this weekend to get a datalog.

I took some picture of the datalog i did with the sct x3 with the car trying to idle. In all cases, the tp_v value is 0.00. is this normal? If i had to guess this parameter is the throttle position voltage?