Question on this...

I was noticing that Tunercat wouldn't retain a value of 1.04.

It would take 1.03 and 1.05, but if I put in 1.04 and saved the file, when I reopened the file it would be 1.05.

I emailed Tunercat about it and they said the following:

That's just because the displayed value is rounded to two decimal places. This is an 8-bit parameter so the decimal value can be 0 to 255. The scale factor for this parameter is 0.015625 so the calibration values work out as follows:


Decimal Calibration Rounded
Value Value Value
64 1.00000 1.00
65 1.015625 1.02
66 1.03125 1.03
67 1.046875 1.05
68 1.0625 1.05

However, when I go into Tunerpro, the values appear to be completely different...

If I open the file in Tunerpro, the 1.05 displayed in Tunercat becomes .262 in Tunerpro, whereas the value of 1.00 in Tunercat is .250 in Tunerpro.

I notice in Tunerpro, the conversion equation is X * .003.

If I wanted to show the values in Tunerpro the way the guys at Tunercat says they really are, do I just change the conversion equation to X * 1.015625 and then increase the number of decimal places?

 

View the data as hex. Thats absolute resolution.

 

If only I knew how to read hex...

 

Tunerpro has an option to display as hex.

Google “hex to INT calculator”
Translate to INT. (integer).

Only 256 INT values possible in the ECU. No decimals.

 

If all you want is them to show identical values, yes, use your preferred scaling across both apps.

 

Ah ok... yeah for me its gotta be kept super simple