Devil7
3rd January, 2019, 10:46 PM
Hey guys
This is seriously getting to me now - a while ago i was altering the mileage on my track bike - managed to do in the end with the help from @clusters
This was his advice
-----------------------
You can get it close with windows calculator.
Calculated in Km, hex to decimal X32.
Decimal/32 to hex then xor with ffff to get the other two bytes..
-----------------------
With that in mind i was after 8207 in miles - a bit of messing about i got this
584249
Happy with the result - now to change mileage on the actual cluster that was going on my race bike
584251
simply copied the hex ( 019F FE60) ** 019F to decimal = 415, x32 = 13280 **
8219 mils in kilometres is 13227 - both clocks read 13151 not a massive problem obvs just the clusters conversion
Coming back to this wanting to understand how to get the numbers more precise - and ended up frying my own brain - below are a few tests ( as 415 x32 was getting me close i did a few more -414,413 etc)
584256
How the hell is this possible - 414 x32 is less (obvs) yet mileage is greater - even 409 x32 is
Worst of all - if i replace the lot with 0000FFFF (should be zero) its 19 miles - and the last digit in every single test i've done is 9
I've edited every single part of the data dump, looking for a minor value - nothing !!!
What am i missing guys? what am i doing wrong
CURRENT DATA DUMP @8219 MILES
FFFFFFFF FFFFFFFF FDF92AC6 12300AFF
0A3F0353 036522FF 0064408F 0065FFFF
433502FF A0EEFFFF FFFFFFFF FFFF0000
20104030 60500170 CB014E3F FFFFFFFF
FFFF0071 04FFFFFF FFFFFFFF 02FB0216
0223FFFF 003C0F09 FFFFFFFF FFFFFFFF
0000FEEE FFFFFFFF FFFFFFFF FFFFFFFF
FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF
019FFE60 019FFE60 019FFE60 019FFE60 <<mileage
019FFE60 019FFE60 019FFE60 019FFE60 <<
019FFE60 019FFE60 019FFE60 019FFE60 <<
019FFE60 019FFE60 019FFE60 019FFE60 <<
FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF
FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF
FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF
FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF
This is seriously getting to me now - a while ago i was altering the mileage on my track bike - managed to do in the end with the help from @clusters
This was his advice
-----------------------
You can get it close with windows calculator.
Calculated in Km, hex to decimal X32.
Decimal/32 to hex then xor with ffff to get the other two bytes..
-----------------------
With that in mind i was after 8207 in miles - a bit of messing about i got this
584249
Happy with the result - now to change mileage on the actual cluster that was going on my race bike
584251
simply copied the hex ( 019F FE60) ** 019F to decimal = 415, x32 = 13280 **
8219 mils in kilometres is 13227 - both clocks read 13151 not a massive problem obvs just the clusters conversion
Coming back to this wanting to understand how to get the numbers more precise - and ended up frying my own brain - below are a few tests ( as 415 x32 was getting me close i did a few more -414,413 etc)
584256
How the hell is this possible - 414 x32 is less (obvs) yet mileage is greater - even 409 x32 is
Worst of all - if i replace the lot with 0000FFFF (should be zero) its 19 miles - and the last digit in every single test i've done is 9
I've edited every single part of the data dump, looking for a minor value - nothing !!!
What am i missing guys? what am i doing wrong
CURRENT DATA DUMP @8219 MILES
FFFFFFFF FFFFFFFF FDF92AC6 12300AFF
0A3F0353 036522FF 0064408F 0065FFFF
433502FF A0EEFFFF FFFFFFFF FFFF0000
20104030 60500170 CB014E3F FFFFFFFF
FFFF0071 04FFFFFF FFFFFFFF 02FB0216
0223FFFF 003C0F09 FFFFFFFF FFFFFFFF
0000FEEE FFFFFFFF FFFFFFFF FFFFFFFF
FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF
019FFE60 019FFE60 019FFE60 019FFE60 <<mileage
019FFE60 019FFE60 019FFE60 019FFE60 <<
019FFE60 019FFE60 019FFE60 019FFE60 <<
019FFE60 019FFE60 019FFE60 019FFE60 <<
FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF
FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF
FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF
FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF