IAC on turbo v8 Help needed

[vp304]

ok done what you said in diagnostics mode (with terminal a b bridged)
i knoticed with ignition on iac was like taping away like making a sound. I think thats normal when in diagnostic mode.

Started car with diagnostics terminal removed adjusted idle
at this point i squashed the iac air feed line that goes to the manifold side of the throttle body and it did not change the idle at all so im guesing the iac was closed like it was suposed to be.
Fitted all back up started car with iac plugged in idle was around 750 rpm. Tuner pro still showing around 70 -80 steps tho at idle
was good for about 10 mins then i reved the car a bit and the idle was like 1100 rpm no matter what i did turn the car of and on it still stayed high. AHHHHHHH

Also knoticed on my short drive to the shops to let the car warm up before adjusting the iac, that the iac fault came back on before i did the adjustments

[VL400]

Clicking sound is good, means its driving the pintle against the base.

Still getting a TPS fault? Until you fix that closed loop idle aint going to work that well as you will be on the default TPS vs RPM table.

[vp304]

vl400 sorry for sounding like a n00b but i am

but
closed loop idle ?? what do i have to do to fix my problems

car is on straight gas also if you havnt seen my posts earlier on

still getting tps and iac faults coming up same as before

[VL400]

Closed loop idle speed - where the ECU controls the IAC steps. When its in open loop idle speed control it just uses the base steps. In your logs it will show closed loop idle speed control, cant check it at the moment but might be worth looking at that when the TPS fault is set and the engine is idling. As to how to fix the TPS fault, reset the ecu, and then start logging while going for a drive - log it till it flags a fault and see what the operating conditions were that caused it.

[vp304]

Im at work at the moment on my phone but on page 2 there is a log saved called sunday 21st were i reset the computer and drove the car till both faults come up. If i get spare time at work il try and look at it. But one of you delco pros could prob find the prob in 5mins of looking at the log were it would prob take me hours lol. Il still try and look at it tho cause i really wanna fix it

I knoticed today the no ref cranking fault i get. I wouldnt worry about as i reset the computer started the car 1st shot warm about 5 times and the fault never come up. Only comes up i think when the car is cold as it takes a while to start on gas.

[Jayme]

hahahaahahahahahaha
I just figured it out. the criteria for setting tps stuck is map must be < 65 kpa and then there iis a table for the amount of throttle % allowed per rpm. now at 1500 rpm and ~ 29 % tps is when the code set which is 4:15 in the log. but the kpa at that point is in the 90's so how does that work you are using a 2 bar map sensor but only have the bin configured for a 1 bar. so when your 2 bar adx shows you at 98 kpa, the pcm is only seeing 49 kpa, which means the tps stuck code sets coz the limit at 1500 rpm is 19% tps, the second you go over that, BAM tps stuck error.


in short, go and tick this flag: Map A: MAP Sensor Type Selection A \ A:B Clear = 1Bar


ps: as a side effect of this, you will have been running pretty phenomenal timing, it might have been pinging on boost.

[vn5000]

I havent looked at your bin but i also tuink i know what your prob may be.
You say you never had the prob with $5D bin.This is because 5D doesnt have code 19.
I would say that because you are using an aftermarket throttle body and your tps works but doesnt read 100% at 100% throttle,the ecu is seeing unexpected values for map and tps, and $12 ose which has code 19 is setting it .
Try unselecting process code 19 and see if it fixes your prob.

[antus]

Nah, i wouldnt recommend that, unless your sure its an issue with the range on the tps. If its the map sensor setting as jayme is suggesting, then your spark map will be reading miles out which is dangerous. Hiding the code will only hide the error. Check your map sensor setup first...

[Jayme]

I disagree VN5000. ive just posted above the exact reason for the problem. ive followed the criteria for setting code 19 and the log and it all matches. the problem is using a 2 bar map sensor and having 1 bar selected in the bin. unticking code 19 may stop the light but not the underlying problem.

[vp304]

Wtf 1 bar timing map and boost fuck me how it didnt go bang. Will look at the tune when i get home from work cause i just checked my usb stick and it aint on here. Do i have to make any other changes to the tune besides the 2 bar option