In the Super_8DM2.ecu file everything tempurature wise is Celcius. When i make an adjustment i have to use a conversion table to know what i want to chane it to in Farenheit. My question is, using notepad in the table below can i change (*xlabel =Deg. C) to (*xlabel =Deg F.) then change (*Factor =1.350000) leave (*offset =-40.00000) where its at and get a table thats in degrees farenheit?
/* Constant 28: EGR Enable Min. MAT Temp. */
/*|| Deg. C = Deg. F
0 = 32
10 = 50
20 = 68
30 = 86
40 = 104
50 = 122
60 = 140
70 = 158
80 = 176
90 = 194
100 = 212
110 = 230
120 = 248 ||*/
{
/*startAddr =2B0,
/*columns =1,
/*rows =1,
/*elementSize =1,
/*bitMask =0,
/*offset =-40.000000,
/*mulOrDivOrBit =0,
/*factor =0.750000,
/*map_name =EGR Enable Min. MAT Temp.,
/*ylabel =,
/*yaxis = ,
/*xlabel =Deg. C,
/*xaxis =,,
};
Thanks, Brian
/* Constant 28: EGR Enable Min. MAT Temp. */
/*|| Deg. C = Deg. F
0 = 32
10 = 50
20 = 68
30 = 86
40 = 104
50 = 122
60 = 140
70 = 158
80 = 176
90 = 194
100 = 212
110 = 230
120 = 248 ||*/
{
/*startAddr =2B0,
/*columns =1,
/*rows =1,
/*elementSize =1,
/*bitMask =0,
/*offset =-40.000000,
/*mulOrDivOrBit =0,
/*factor =0.750000,
/*map_name =EGR Enable Min. MAT Temp.,
/*ylabel =,
/*yaxis = ,
/*xlabel =Deg. C,
/*xaxis =,,
};
Thanks, Brian
OK, i went ahead and made a copy of the .xdf for my personal editing. I changed what i stated above and i also changed the fan temps. to deg. F also with a few other tempature related constants. When i compare them to the Deg. C settings they all seem to be accurate. Can anyone verify this. I just noticed that on ym second go around of the xdf file that it says "XDF
1.110000
DO NOT HAND EDIT!!!! (Trust me)"
Does that include something as simple as what im doing, even though its appearing to be accurate?
1.110000
DO NOT HAND EDIT!!!! (Trust me)"
Does that include something as simple as what im doing, even though its appearing to be accurate?
Moderator
Yes, that will work (changing the factor). When I see things such as the:
"DO NOT HAND EDIT!!!! (Trust me)"
That means the parsing is most likely in a fixed format. So, as you listed in your first post make sure the formatting of the new factor is exact. Right down to the number of decimal places and digits.
Then the locations of the spaces, such as one before the equal sign, and none after it. No space before the comma. The parser is probably very particular about what you can feed it.
RBob.
"DO NOT HAND EDIT!!!! (Trust me)"
That means the parsing is most likely in a fixed format. So, as you listed in your first post make sure the formatting of the new factor is exact. Right down to the number of decimal places and digits.
Then the locations of the spaces, such as one before the equal sign, and none after it. No space before the comma. The parser is probably very particular about what you can feed it.
RBob.
Great! Thats exactly the answer i was hoping for. Thanks alot Rbob 
I still dont know celcius except for 0* and 100*. Anything before and after is foreign to me.
I still dont know celcius except for 0* and 100*. Anything before and after is foreign to me.
Member
As I said in an earlier post where I did the same thing for a 7747, I just copy/pasted the table for *C, changed the name and ID number, then loaded it in TP/RT and used the "covert C to F" function. Then pointed a new value entry to the new *F table and done... Now that ECU has both *C and *F so anyone can look at it any way they choose.
I cant find the Convert C* ot F* function in TP. But I found this in the TunerPro help section just now.
Quote:
The template file
The template file (the XDF file in the case of TunerPro) is a file that tells the editing software how to interpret each byte in the bin file. It basically says, in plain English "the byte at location X in the bin file should be multiplied/divided/offset by W, Y, Z to come up with a real world number." For example, in a made-up bin, lets say the byte at the 215th offset (or said a different way, the 215th byte) in the bin file is F (in hex, which is 15 in decimal). For the ECM that this bin is meant for might use this byte for determining the temperature at which to turn on the engine's cooling fan. Well, 15 by itself isn't a very useful number, so the engineers who designed the computer needed to come up with some numbers with which to do math on it to turn it into a real world number. Lets say they did this:
The value held in the 215th byte should be multiplied by 1.35 and then 40 should be subtracted from it. The final number will be in degrees farenheit.
The template file
The template file (the XDF file in the case of TunerPro) is a file that tells the editing software how to interpret each byte in the bin file. It basically says, in plain English "the byte at location X in the bin file should be multiplied/divided/offset by W, Y, Z to come up with a real world number." For example, in a made-up bin, lets say the byte at the 215th offset (or said a different way, the 215th byte) in the bin file is F (in hex, which is 15 in decimal). For the ECM that this bin is meant for might use this byte for determining the temperature at which to turn on the engine's cooling fan. Well, 15 by itself isn't a very useful number, so the engineers who designed the computer needed to come up with some numbers with which to do math on it to turn it into a real world number. Lets say they did this:
The value held in the 215th byte should be multiplied by 1.35 and then 40 should be subtracted from it. The final number will be in degrees farenheit.
Member
Open the ALDL Setup, then "Edit ALDL" button. Select a table in the left pane. Notice that on the right side there are the table cells, and below that a "Convert Table" button. The dropdown beside that has C->F and F->C in it...
Yeah that converts a .ads file for datalogging but does that convert a .xdf/.ecu file for .bin editing? I found some info in the help file and theres a .xdf editor in the program thats real easy to use. I dont understand yet how to edit the cloumns in the the tables section but im completeing that task by just editing "yunit and ylabels" and just manualy converting the C* to F* and inputing that into the .xdf file with notepad. Seem to be accurate.
Member
Oops, sorry. Trying to catch up on posts and didn't read (or think) carefully... Got XDF/ECU and ADS crossed up... 
Member
Oh, and to edit the values in the degree column, click on the entry in "tables", then F2 (or context/xdf menu) to edit that entry, then choose the "rows" tab. You can set the row lables in there. And then the conversion tab allows you to enter the fomula. Not sure if that helps.