Re-scaling MAT counts table $8D SAUJP

[34blazer]

dumb question.....but, to edit the A/D lookup a LF133, can i find it with hex editor or do i need to make the changes to the disassembly(notepad?) and reassemble? also, is there a standard equation to convert A/D counts or will i need to figure it out? not entirely sure on this....

Thanks!

[The1]

changning it in hex should be ok, make a spreadsheet and interpolate the values further and then use the range you want.

[34blazer]

as far as the location, LF133, I cant find it. Im still learning how it is all mapped, is there another way i should be looking at it? it has to be displayed differently.

as far as the equation goes, I didnt understand what you meant. I understand how to change the range of the counts, but do not know how to convert them to temperature.

[charlay86]

as far as the location, LF133, I cant find it. Im still learning how it is all mapped, is there another way i should be looking at it? it has to be displayed differently.

LF133 is Location 0xF133 in the bin file.
calculation for temperature is usually: (hex_value * 0.75) - 40 = Temperature in °C

[34blazer]

as far as the location, LF133, I cant find it. Im still learning how it is all mapped, is there another way i should be looking at it? it has to be displayed differently.

LF133 is Location 0xF133 in the bin file.
calculation for temperature is usually: (hex_value * 0.75) - 40 = Temperature in °C

so on the address bar on the left im looking for 0000F133? or 0000133? or 000033? still cant find it and its driving me nuts LOL

[charlay86]

Just ignore the 'L', you are looking for 0000F133

[34blazer]

Just ignore the 'L', you are looking for 0000F133

yeah its not me then, address only goes up to 00007FF0. dont know where else it could be lol

[charlay86]

hmm ok, well you can try searching the bin file for the table.
tunerpro's hex editor can't search so you'll need to use something else, eg winhex, HxD.

hxdsearch.png (29.2 KiB) Viewed 6189 times

[VL400]

The bin must be only 32k, so its 0-7FFF in size. The ECU/processor maps it to 8000-FFFF, so in ECU speak F133 is 7133 in your bin (7133 + 8000 = F133).

When I have looked at rescaling I found it easier to play with pull up resistors and leave the code alone, a temp sensor is highly non-linear so pullup choice is pretty critical for the range you expect to operate in.

[34blazer]

ugh...somethings not right, its not there either. i must be doing something wrong LOL