[thecableguy]

Hello! I can calculate the original mileage from the dump attached, however what I’m really wanting to know is how to reapply an exact odometer correction.

Note: The dump attached is one I found online since I’m using a bench cluster.

For example, the algorithm has two components that are skewed across 20 different numbers. So like, 12x 8919 and 8x 8920…my question is this:

How do we know which amount of both to put in when we’re calculating the replacement reading?

Is this a well-known algorithm? For example, the cluster manufacturer was Australian Arrow Pty. Ltd. (AAPL), Australia’s division of Yazaki.

[Clusters]

Pretty simple algo, that file has 241095 Km.

Modified Yazaki, without the complement words.

2f17 X 20 = 241100
Minus 5 for the 5 2f16 = 241095

[thecableguy]

Thankyou very much for the response

I’m very new to this; what is a complement word?

Also, how do they get 5x 2f16 and not, say, 7x? That’s the bit that’s confusing me as I try and reverse the algorithm’s direction to encode a reading instead of decoding it.

[Clusters]

7x 2f16 would make it 241093

The hard way, convert each word to decimal, then add them together.

To get a new value, mileage / 20 to hex. To make it simple, use multiples of 20.

[thecableguy]

Okay, I’ve figured it out this is what I did:

The first part is calculated by dividing the reading by 20 and rounding it up.

The second part is calculated by doing the same, but then rounding it down.

The fractional component that remains after you divide the reading by 20 is multiplied by 20 to give you the number of times the second component should be repeated.

Obviously then, the number of times the first component appears is determined by 20 minus the number of times the second one appears.