Have 1500rpm idle and P0505

When you put the RamAir on did you run a new tune on the ecu to compensate for the additional intake breath of air? then after running new tune you have to run an ISCV reset & then TPS chec, then re-set adaptations, then 12 minute tune
\

I actually deposited the new tune before putting ramair on, as I was anticipating it's arrival. A test ride showed nothing amiss at that time, and the tune would be more than adequate. (Have to be careful of unintended wheelies!) When ramair came, I installed it, and did 12 minute tune. Seeing all was normal, shut it down, and left it knowing work and several dr appointments would keep me occupied. When I did get back to it, the idle was way up and the P0505 Check light was on. Just noodling around got me to turning that adjustment nut and recovering the idle speed. After bringing it in close, I reset adaptations, and did 12 minute tune. Idle stabilized where it belongs, Stepper does pass it's ignition on test when you hear it cycling in and out, as you turn the ignition on. I am going to see that it's connector is tight and that I didn't somehow mess up the wiring coming to it, and check some others to be sure. I will probably skin the covering off the stepper bundle and use some convoluted tube to recover them after I inspect them. Since it appears the ISCV is doing it's job, if getting the check light to go proves to be futile...I shall cover it up and ignore it! Scan with tuneECU once in a while to make sure no other codes have been set!
 
Another update, and thinking ISCV is gone to its great reward....or is going. I did a full on ISCV reset with TuneECU, cold engine, new battery. First set TPS to .60, it was .63. Not bad, but let's get it on spec. Went to ISCV set and initial reading was .60! Backed nut off until it said .72 as requested. TuneECU said it was adapting the ISCV, and when done, I went ahead and reset adaptations to do a 12 minute tune. Lo and behold! Idle shot up to 2300 rpm on start! Bollocks! So, got on the ISCV and cranked it back down to 900 rpm, reset adaptations again, and well voltages are .6 and .6 again. I believe now my ISCV is knackered and failing. My kludge will keep it riding good, but think a new sensor is the only way to get the check light to go away and stay away. What say ye?
 
Sound to me like you did the procedure wrong from your write up.

Here it is in a nut shell. Key on headlight fuse out. Tune ecu hooked up to the bike.

First double click ISCV RESET you will hear and see the stepper motor retract.

Second once stepper motor is fully retracted you set the primary TPS to .6volts plus or minus .02 volts.

Third double click ISCV RESET again and the stepper motor will move forward opening the throttle bodies a wee bit. This small amount is .12 volts plus or minus .05 volts. So you should see .72 volts if it was perfect. If not and it is out of tolerance you adjust the 7mm nut until you reach. 72 volts or within the tolerance.

Fourth double click the ISCV RESET again and you will see the ecu doing its adaptive stuff once it done click reset adaptives turn key off for 5 seconds then you're ready to go provided you plug the head light fuse in.

I'm not sure if that's the way you did it your write up does not look like it.

Also you can ruin a tps by over tightening it.
 
Doesn't work that way in Android....if it should it is not explicit. You start the procedure under Test and Adjustments, and it says "adjust tps to indicate .60 volts." you do it, and tap "next" then it prompts to adjust ISCV to .72 hit next again and TuneECU will do it's adaptation routine. Not sure how you would discern these extra moves if it doesn't stipulate! In any case it seems, though you are describing the windows procedure, ( I HATE windows...is that strong enough a word?) what I did was acceptable....it sill should not have gotten 2300 rpm out of that procedure. Any windows nuances would not have created a different outcome. BUT, while I did not find any lose connections, is there a scenario where if ONE of the wires to the ISCV had a break in it, it would drive it out of range but it still sort of work....as it is doing here?
 
Last edited:
Doesn't work that way in Android....if it should it is not explicit. You start the procedure under Test and Adjustments, and it says "adjust tps to indicate .60 volts." you do it, and tap "next" then it prompts to adjust ISCV to .72 hit next again and TuneECU will do it's adaptation routine. Not sure how you would discern these extra moves if it doesn't stipulate! In any case it seems, though you are describing the windows procedure, ( I HATE windows...is that strong enough a word?) what I did was acceptable....it sill should not have gotten 2300 rpm out of that procedure. Any windows nuances would not have created a different outcome. BUT, while I did not find any lose connections, is there a scenario where if ONE of the wires to the ISCV had a break in it, it would drive it out of range but it still sort of work....as it is doing here?
Ok I did not realize you use android but the process should basically be the same. First adjustment to .6 +/- .02 volts has to be done with the stepper motor fully retracted by the ECU or your screwed from the start. You should be able to at least feel the motor shaft retracting away from the throttle bodies. After that then the command tells the stepper motor to move forward .12 volts which is where you check to see if you have a total voltage of .72 +/- .05 volts and if not adjust the stepper motor nut to bring the voltage in. then on to finish the test ending with a reset adaptive's.

I can see a high idle if the .6 volts was set while the stepper motor was in as the throttle bodies are not fully shut when you set the voltage so the motor reads the ecu data and opens the throttle bodies even more.


Aside from that do you know if the primary TPS has ever been changed?
 
Ok I did not realize you use android but the process should basically be the same. First adjustment to .6 +/- .02 volts has to be done with the stepper motor fully retracted by the ECU or your screwed from the start. You should be able to at least feel the motor shaft retracting away from the throttle bodies. After that then the command tells the stepper motor to move forward .12 volts which is where you check to see if you have a total voltage of .72 +/- .05 volts and if not adjust the stepper motor nut to bring the voltage in. then on to finish the test ending with a reset adaptive's.

I can see a high idle if the .6 volts was set while the stepper motor was in as the throttle bodies are not fully shut when you set the voltage so the motor reads the ecu data and opens the throttle bodies even more.


Aside from that do you know if the primary TPS has ever been changed?


Worked on a bike few weekends ago, had idling problems. I thought it was the Idle stepper motor, it was making odd noises and even after an ISCV reset and TPS reset still held the idle on button off. Was sure it was the idle stepper motor. Tried resetting twice same result. Fitted spare TPS problem gone stepper motor quiet. Happy rider, apart from having to buy a new TPS. Also as Warp says do not over-tighten it.
 
Well, that gives me some ideas to work with....I need to go in for annual service, I just might get their guru to do it! I do believe in the end this is related to fitting ramair....it just made such a difference in airflow that recalibration would have to be done.
 
I may have identified an intermittent connection which prevents the ISCV getting either power or control signal. Not digging into it just yet, and have both tps and ISCV set to equal voltage so the bike will idle properly, though I do think it is in a limp mode...which is no less powerful than normal for what it's worth. If a wire is the problem it would result from handling when I was putting in the ramair kit. Hopefully the point to patch will be easily found.
 
When you got hands the size of a frying pan, you end up upsetting all manner of things from time to time. In any case I knew I wasn't doing reset wrong....ISCV just doesn't know where to go, and will not always bottom out on test since it may not get the signal to do so.
 
Back
Top