Blacky
September 25th, 2020, 03:10 PM
The V8 editor displays the exact values that will be stored in the controller's calibrations. Sometimes that can appear as if the values being entered into a calibration are being subtly changed behind your back.
For example the spark tables can only store values down to 1/2 a degree in accuracy. So it can store 10.0, 10.5, 11.0, 11.5, 12.0 etc. degrees of timing in the table. If you entered 10.2 then the V8 editor automatically corrects the it to the closest valid value which would be 10.0 degrees. If you entered 10.4, the it would correct it to 10.5 degrees.
E.g.
Start with 30.0
23516
Enter the value30.4
23515
Press [Enter] and the V8 editor automatically corrects the value to 30.5
23514
For example the spark tables can only store values down to 1/2 a degree in accuracy. So it can store 10.0, 10.5, 11.0, 11.5, 12.0 etc. degrees of timing in the table. If you entered 10.2 then the V8 editor automatically corrects the it to the closest valid value which would be 10.0 degrees. If you entered 10.4, the it would correct it to 10.5 degrees.
E.g.
Start with 30.0
23516
Enter the value30.4
23515
Press [Enter] and the V8 editor automatically corrects the value to 30.5
23514