Dashboards instruction / Инструкция по работе с приборками

 Posts: 3
 Joined: 18 Feb 2020, 21:50
Re: Dashboards instruction / Инструкция по работе с приборками
Please explain with pictures How to change the meter reading to the value of 100 kilometers?
I made many attempts to follow the instructions in the discussion and I didn’t succeed
Thanks in advance.
I made many attempts to follow the instructions in the discussion and I didn’t succeed
Thanks in advance.
Re: Dashboards instruction / Инструкция по работе с приборками
All explained in first post here
In backup we trust.

 Posts: 3
 Joined: 18 Feb 2020, 21:50
Re: Dashboards instruction / Инструкция по работе с приборками
how to change from mileskm on Color screen upD70F3425 and blackwhite upD70F3421
ODO/mileskm
ODO/mileskm

 Posts: 3
 Joined: 18 Feb 2020, 21:50
Re: Dashboards instruction / Инструкция по работе с приборками
how to change from mileskm on Color screen upD70F3425 and blackwhite upD70F3421
ODO/mileskm
ODO/mileskm
Re: Nippon Seiki MB91F223 instruction
can i trouble you please to expand on this, im having a hard time to wrap my mind around it.gniqu wrote: ↑17 Nov 2020, 02:44Do some math can help to caculate the exact ODO

876C 7893 (FFFF876C=7893)
806C 7F93 (FFFF806C=7F93)
806C 7F93 HEX2DEC=4127+884736=888863 km
876C 7893 step 24 km
876C 7F93 step 1 km
ODO=888863+24+1=888888 km

here is an example
actual cluster has 211,891 kilometers on it, hex is D2192DE6
when put it 211891 into tacho soft it gives hex DD1922E6
when you write the tachosoft hex to the cluster the odometer says 211711, a difference of 180 kilometers , should say 211,891.
so how do we use maths to get the exact hex?
thanks
Re: Dashboards instruction / Инструкция по работе с приборками
i think i figured it out
using this web site
https://www.rapidtables.com/convert/num ... ohex.html
DD1922E6 convert to decimal 3709412070
D2192DE6 convert to decimal 3524865510
difference is 184,546,560
take 3709412070 and minus 184,546,560 gives us 3524865510
convert 3524865510 into hex using that site and we get D2192DE6
put D2192DE6 into cluster and we get the exact number we needed 211891
however, feel free to correct me if im wrong
using this web site
https://www.rapidtables.com/convert/num ... ohex.html
DD1922E6 convert to decimal 3709412070
D2192DE6 convert to decimal 3524865510
difference is 184,546,560
take 3709412070 and minus 184,546,560 gives us 3524865510
convert 3524865510 into hex using that site and we get D2192DE6
put D2192DE6 into cluster and we get the exact number we needed 211891
however, feel free to correct me if im wrong
Re: Dashboards instruction / Инструкция по работе с приборками
6b31tb wrote: ↑17 May 2021, 07:04i think i figured it out
using this web site
https://www.rapidtables.com/convert/num ... ohex.html
DD1922E6 convert to decimal 3709412070
D2192DE6 convert to decimal 3524865510
difference is 184,546,560
take 3709412070 and minus 184,546,560 gives us 3524865510
convert 3524865510 into hex using that site and we get D2192DE6
put D2192DE6 into cluster and we get the exact number we needed 211891
however, feel free to correct me if im wrong
The calculation is much more complicated than described above.
Re: Dashboards instruction / Инструкция по работе с приборками
after much hunting i think i have figured it out
the first two hex are the odometer, the remain two hex are the inverse check sum
i went hunting with google and found a few things out.
..............................................................................
Mitsubishi Outlander yazaki c86 2012...and similar
4C 07 B3 F8 is 59776 KM
4C 07 > 07 4C> HEX>DEC x32 = ori milage
CS
4C + B3 = FF
07 + F8 = FF
Milage writen in adress 03F
Its simple but many calcs no calculate CS
..............................................................................
HEX Invertor, original on left, inverted on right
0F
1E
2D
3C
4B
5A
69
78
87
96
A5
B4
C3
D2
E1
F0
..............................................................................
you’ll notice the characters 33 85 CC 7A repeated 8 times. This is the major odometer value in HEX. The numbers are actually the HEX invert of each other, and act like a checksum. A HEX lookup table, which is 0F and F0 backward is used to determine the inverse of each character.
For example, a “3” will be inverted as “C”, and 8” inverted as “7” and “5” inverted as “A”.
Therefore the only characters that store actual information are the first two HEX digits, 33 and 85.
To decode, simply convert the number to decimal using a hex to decimal converter, and then multiply by 16 to give you the odometer reading in kilometers. I got 211,024km.
Using this method of calculation, I need the new cluster to read 314K, so I can divide it by 16 and convert it to HEX to give me the base value in the odometer dump. This value, 4C CF will then have a checksum of B3 30, which I will write to the chip.
Now I know it’s not exactly accurate but close enough, because there is a minor incremental value that I haven’t decoded. I made an excel sheet to help me convert the numbers.
the first two hex are the odometer, the remain two hex are the inverse check sum
i went hunting with google and found a few things out.
..............................................................................
Mitsubishi Outlander yazaki c86 2012...and similar
4C 07 B3 F8 is 59776 KM
4C 07 > 07 4C> HEX>DEC x32 = ori milage
CS
4C + B3 = FF
07 + F8 = FF
Milage writen in adress 03F
Its simple but many calcs no calculate CS
..............................................................................
HEX Invertor, original on left, inverted on right
0F
1E
2D
3C
4B
5A
69
78
87
96
A5
B4
C3
D2
E1
F0
..............................................................................
you’ll notice the characters 33 85 CC 7A repeated 8 times. This is the major odometer value in HEX. The numbers are actually the HEX invert of each other, and act like a checksum. A HEX lookup table, which is 0F and F0 backward is used to determine the inverse of each character.
For example, a “3” will be inverted as “C”, and 8” inverted as “7” and “5” inverted as “A”.
Therefore the only characters that store actual information are the first two HEX digits, 33 and 85.
To decode, simply convert the number to decimal using a hex to decimal converter, and then multiply by 16 to give you the odometer reading in kilometers. I got 211,024km.
Using this method of calculation, I need the new cluster to read 314K, so I can divide it by 16 and convert it to HEX to give me the base value in the odometer dump. This value, 4C CF will then have a checksum of B3 30, which I will write to the chip.
Now I know it’s not exactly accurate but close enough, because there is a minor incremental value that I haven’t decoded. I made an excel sheet to help me convert the numbers.
Re: Dashboards instruction / Инструкция по работе с приборками
All this is interesting. But the exact calculation is considered differently. Simple standards are not applicable. The exact calculation is actually very difficult.