VersaTune User Forum

Hello, I would like to ask you about best practices for Axis editing.
As I could read in hlep column I can't add any columns in the Axis.
Is it hard coded in the ECU?
In NC1 maps I have only 14 or 13 steps which are incremented by 500rpm, NC2 has more steps like 15 achieving 7500RPM
If I am going to increase the REV limiter to like 7500RPM should I just increase the increment into 550,
to be albe to get 7500RPM? Or is there some best practice for this stuff?
And one more when I am at last point of a table does that value continue to be used like forever?
Talking about 7000RPM (ignition timing) = 24.3 will it be still valid for 7500RPM or 8000 RPM ?

1. Table size is hardcoded. You can only change the axis values, not add or remove them.
2. The last row or column value is used for all values above that.
3. Usually if the increment is uniform (500 RPM in this case), it's best to have it uniform after rescaling the axis.

Ugnius @ VersaTune wrote: ↑April 14th, 2025, 3:24 pm 1. Table size is hardcoded. You can only change the axis values, not add or remove them.
2. The last row or column value is used for all values above that.
3. Usually if the increment is uniform (500 RPM in this case), it's best to have it uniform after rescaling the axis.

Thank you very much for your insight.
Than it´s okay for me to rescale it by value 540RPM.

reibes wrote: ↑April 16th, 2025, 6:31 am Than it´s okay for me to rescale it by value 540RPM.

This is one possible approach, another one is to lengthen only the last few intervals (3-4) by a certain amount. By example, instead of having the last RPM points set to 5500/6000/6500/7000 you can have them at 5750/6350/6900/7500. Or 5650/6200/6750/7300 (since right at 7500 the values are going to be interpolated from the last few).