this is found on my constants table and was hoping someone could explain. why would you delay this function and what should this be normally set to?

also, "tps threshhold vs rpm for wot"? i also have a duplicate of this table which says "tps threshhold vs rpm for wot,fast"
why do i have 2 of these tables

"tps threshhold vs rpm for wot,fast"
rpm %tps
800 69.9
1200 69.9
1600 69.9
2000 69.9
2400 97.7
2800 97.7
3200 97.7
3600 97.7
4000 97.7


this is what "tps threshhold vs rpm for wot"
looks like

rpm %tps
800 60.2
1200 60.2
1600 60.2
2000 60.2
2400 69.9
2800 69.9
3200 69.9
3600 69.9
4000 69.9


383 stroker, 64cc 23deg trickflow heads c/w edlebrock performer intake and adapter, cam is an extreme 4x4 comp. Cam. 12-235-2 grind ( .447/.462 lift, duration 210 218 lift @50, 111 lobe separation) . unit has hypr. Flattop floating pistons, eagle cast crank, 5.7eagle rods. 10.2:1 comp. Headers c/w 2.5” flowmaster exhaust. 16147060 pcm, $85def
454tbi 80lbinjectors

 

Some heavier vehicles need a slight pause before goinng to WOT, because there is so much weight relative to the HP available, others, use it a mileage thing, you actually don't need WOT every time you use 100% TPS. So they have a little delay, kinda like saying do you really want to go WOT or can we think about this.

Then the other table is like OK, we're already reved up so we can go to PE WOT, IF the TPS value is so high.

No universal answers on settings, that's part of burning chips, finding out what works for your combination