So I tried to get clever and fill equations with an IF statement. I believe it fails due to the order in which TP evaluates but, could be something else.
In my case all the rows except the last one have this equation
CELL(ROW()+1;COL();FALSE) - (THIS() / 15)
The last row has
(256 - THIS()) / 15
Works but I wanted to save time and avoid having to set multiple equations.
So I tested an IF statement to fill all rows with a 0 except the last one which got a 1. Like this
IF(ROW()==ROWS()-1;1;0)
So then I tried replacing the 1 and 0 with the actual equations and no go. Not sure the why but, understandable as there is a order of events required for that IF statement to work as one equation relies on that other. Was wishful thinking
Bosch Motronic style axis label equations in conversion editor FAIL
Moderators: Mangus, robertisaar, dex
Bosch Motronic style axis label equations in conversion editor FAIL
Last edited by nomecone on Thu May 01, 2025 5:38 am, edited 1 time in total.
Re: Bosch style axis label equations in conversion editor My failure
I finally came back to this and, actually tried editing an axis for load. I have only been able to edit when using raw hex properly. Putting in an updated converted value does not evaluate properly.
I wonder if there is a method other than direct hex edit that can work for Bosch style axis in TunerPro.
I wonder if there is a method other than direct hex edit that can work for Bosch style axis in TunerPro.
Re: Bosch style axis label equations in conversion editor My failure
I crossed this...
https://www.tunerpro.net/examples
Note here the use of 255 Then in the example files linked on the page 256 is used 255 seems to be correct to me. Max value is FF = 255
(256-255)*40 = 40 this does not seem right. Should be zero.
(255-255)*40 = 0 this seems right to me
Looks like most if not all motronic xdfs copy pasted from the example file and now have 256 in every occurrence of the equation. Not my favorite type of fix to make. WHOOPY. Maybe time to cross the line and hand edit the XDF in Notepad++
https://www.tunerpro.net/examples
Note here the use of 255 Then in the example files linked on the page 256 is used 255 seems to be correct to me. Max value is FF = 255
(256-255)*40 = 40 this does not seem right. Should be zero.
(255-255)*40 = 0 this seems right to me
Looks like most if not all motronic xdfs copy pasted from the example file and now have 256 in every occurrence of the equation. Not my favorite type of fix to make. WHOOPY. Maybe time to cross the line and hand edit the XDF in Notepad++