Engine detuning itself
Thread Starter
Teching In
Joined: Oct 2004
Posts: 5
Likes: 0
Engine detuning itself CAN ANYONE HELP! Gen111 Holden Auto, prepared program loaded it into the car jumped on the throttle lit the back tyres up all the way through first gear while continuing to accelerate then into second and continued to spin the back wheels.
After three days of driving it progressively detuned itself to the point of being unable to spin the back wheels off the mark. identified some torque management setting corrected them performed as good mid and upper range but still would not spin the wheels off the mark by jumping on the throttle.
Reset the computer loaded the exact program that I used initially with the logic the computer has been reset the same program that initially spun the wheels through first gear was now in the computer it should duplicate the initial results, temperature of the day and conditions were similar on both runs the computer appeared to be reset as it ran rough when started indicating any memory had been cleared. BUT NO it would NOT spin the wheels in first when jumping on the throttle. Any comments suggestion would be appreciated.
After three days of driving it progressively detuned itself to the point of being unable to spin the back wheels off the mark. identified some torque management setting corrected them performed as good mid and upper range but still would not spin the wheels off the mark by jumping on the throttle.
Reset the computer loaded the exact program that I used initially with the logic the computer has been reset the same program that initially spun the wheels through first gear was now in the computer it should duplicate the initial results, temperature of the day and conditions were similar on both runs the computer appeared to be reset as it ran rough when started indicating any memory had been cleared. BUT NO it would NOT spin the wheels in first when jumping on the throttle. Any comments suggestion would be appreciated.
Spark advance will also learn out in the presence of
persistent knock (or false knock) by the Knock Learn
Factor, KLF=1 means high octane table value while
KLF=0 means all the way down to the low octane
value. If you copy the high octane table to the low
octane table and it all comes back, this is your prob.
Or, just log/scan the Knock Learn Factor PID and
inspect.
persistent knock (or false knock) by the Knock Learn
Factor, KLF=1 means high octane table value while
KLF=0 means all the way down to the low octane
value. If you copy the high octane table to the low
octane table and it all comes back, this is your prob.
Or, just log/scan the Knock Learn Factor PID and
inspect.
TECH Addict
Joined: Feb 2004
Posts: 2,826
Likes: 0
Originally Posted by jimmyblue
Spark advance will also learn out in the presence of
persistent knock (or false knock) by the Knock Learn
Factor, KLF=1 means high octane table value while
KLF=0 means all the way down to the low octane
value. If you copy the high octane table to the low
octane table and it all comes back, this is your prob.
Or, just log/scan the Knock Learn Factor PID and
inspect.
persistent knock (or false knock) by the Knock Learn
Factor, KLF=1 means high octane table value while
KLF=0 means all the way down to the low octane
value. If you copy the high octane table to the low
octane table and it all comes back, this is your prob.
Or, just log/scan the Knock Learn Factor PID and
inspect.
