Bosch Motronic style axis label equations in conversion editor FAIL

[nomecone]

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

axis oldworking method.PNG (22.92 KiB) Viewed 9219 times

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)

axis if equation 1 0 works.PNG (19.94 KiB) Viewed 9219 times

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

axis if equation actual not.PNG (32.51 KiB) Viewed 9219 times

[nomecone]

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.

[nomecone]

I crossed this...
https://www.tunerpro.net/examples

Note here the use of 255

motronic axis tp.PNG (43.17 KiB) Viewed 8269 times

Then in the example files linked on the page 256 is used

motronic axis tp 2.PNG (37.47 KiB) Viewed 8269 times

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++

[AK16]

Hallo, is this only with an external axis possible? I have tried with internal axis - there is nothing to put the conversion for each axis point in.

[AK16]

(256-255)*40 = 40 this does not seem right. Should be zero.
(255-255)*40 = 0 this seems right to me

-> 256 is right.

[nomecone]

Hallo, is this only with an external axis possible? I have tried with internal axis - there is nothing to put the conversion for each axis point in.

You would put the equations in the rows/columns of the data. Does not need to be external axis.

[nomecone]

(256-255)*40 = 40 this does not seem right. Should be zero.
(255-255)*40 = 0 this seems right to me

-> 256 is right.

I can't recall where I landed on this one. I can say that I have found in the official BMW docs for the e30m3 you can find instances that they they used 255 in some equations and 256 in others. So... Yeah BMW/Bosch is not consistent or the Damos document is wrong/typo for some things.

[nomecone]

Hallo, is this only with an external axis possible? I have tried with internal axis - there is nothing to put the conversion for each axis point in.

You would put the equations in the rows/columns of the data, in the conversion tab of a table you should see rows and columns that you can add the equations to. And the documentation for the program you can find information on how to do this. Does not need to be external axis.

[AK16]

You would put the equations in the rows/columns of the data, in the conversion tab of a table you should see rows and columns that you can add the equations to. And the documentation for the program you can find information on how to do this. Does not need to be external axis.

Can you show me a picture, where i can do this?



rpm axis in a Opel bin file:
0F 0D 0C 0D 0C 19 9C
256: 400 1000 1520 2000 2520 3000 4000
255: 360 960 1480 1960 2480 2960 3960
rL:
06 11 0D 0C 0D 0C
256: 2,05 2,9 3,55 4,15 4,8 5,4
255: 2 2,85 3,5 4,1 4,75 5,35
engine Temp:
37 10 0F 77
256: -9,75 31,5 43,5 54,75
255: -10,5 30,75 42,75 54
-> you can only see it in the rpm axis, that 256 is right.


BMW RPM:
02 09 19 32 19 83
256: 560 640 1000 2000 4000 5000
255: 520 600 960 1960 3960 4960
-> i think 256 is right