So according to what i read Timing is Calculated:
'AdvanceFromRPM2' +(MAPTiming x MAPMultplier)
And the 'MAPtiming' can be substituted for WOTMAP, HOTMAP, or Cold map.
But the 'MAPmultiplier' only comes into the equation when the raw 'MAPtiming' number is a negative number.
But when tuning how do you use RPMLMT(LimitForHotMAPAdvance) and SPKLMT(AdvanceFromRpmMAX).
From the MPTune Calculated tables RPMLMT is the Minimum timing and SPKLMT is the Maximum, meaning no matter what the other tables add up to these to set the boundaries.
This is the TSMEC SIV 2.5 ATX table the RPMLMT in the cal is set to 15.3 and as you see in the graph the smallest timing number is 15.5 (it rounds)
Here is where i maxed out the RPMLMT table to 64* as you see the table is pancaked flat because the min was set higher than the SPKLMT max and this is what it looks like
Then here is when i lowered the RPMLMT all the way down to -64* and you have a graph that has much more contour than the original, now that the 15.3 floor has been removed.
Previously i have been stumped when i had knock and tried to remove timing only to find that even if i adjusted the WOTMAP to pull 64 degrees of timing out it didn't remove the knock.
Now i see that if i want or need to lower the timing i also have to lower the RPMLMT(LimitForHotMAPAdvance) if the timing is already that low.
After all that my question is Why is there a minimum? What is the purpose for RPMLMT(LimitForHotMAPAdvance)?
Should i just lower that by a few degrees until the knock goes away? or lower it a bunch and then add timing in the MAPAdvance tables where it wasn't knocking?