Odd TPS WGDC table values cause no-start if changed in Tephra 88590715
Thread Starter
Newbie
Joined: Aug 2011
Posts: 6
Likes: 0
From: Anchorage, AK
Odd TPS WGDC table values cause no-start if changed in Tephra 88590715
When tuning with Tephra V7 88590715, I see that there are erroneous values in the "Max total upward WGDC Correction Vs TPS" table where the throttle position 0-100 values would normally go, see picture >
If I change these values, the vehicle will not start on the 2nd or 3rd restart, just crank with no spark/no fuel. It took me awhile to figure out that changing these was the culprit.
I copied the values into excel to see what they were,
0
70.58823529
10139.21569
25660.78431
0
70.58823529
10139.21569
25660.78431
0
This makes no sense to me! All my xml defs are factory fresh (I recently purged my ECUflash directory)
With the adjacent values zero'd out (as in picture), Evoscan shows WGDC trying to be added, 16%, but oddly enough this may have no impact on actual duty cycle.
any insight is appreciated!
If I change these values, the vehicle will not start on the 2nd or 3rd restart, just crank with no spark/no fuel. It took me awhile to figure out that changing these was the culprit.
I copied the values into excel to see what they were,
0
70.58823529
10139.21569
25660.78431
0
70.58823529
10139.21569
25660.78431
0
This makes no sense to me! All my xml defs are factory fresh (I recently purged my ECUflash directory)
With the adjacent values zero'd out (as in picture), Evoscan shows WGDC trying to be added, 16%, but oddly enough this may have no impact on actual duty cycle.
any insight is appreciated!
Last edited by PIE-R; Nov 15, 2014 at 09:30 PM.
Thread
Thread Starter
Forum
Replies
Last Post
okevolutionVIII
ECU Flash
6
Jan 1, 2014 10:15 PM