Looking for 2nd gen (2010) Tundra 93C66 Odometer Programming Info

[Zero Cool]

I FINALLY understand how this works!

First off, I want to say thank you to everyone that has posted and helped and all the other forum posts on the subject. All have been helpful and especially CLUSTERS man you are out there. I found your name on some of the most OBSCURE websites! LOL you have quite the web presence! Thank you to all!

So while I was able to read and program my Tundra cluster and get it close to whatever mileage I wanted. I didn’t exactly understand how it worked. I googled and googled and was trying to learn about the Yazaki-17 wear leveling algorithm. And found lots of examples using software, or expensive programmers etc etc but nothing that EXPLAINED to me exactly how it worked. Then I found a youtube video in Portuguese (I had to translate it one word at a time using google translate LOL) that sort of gave me the key. In this video he programmed 10,000 KM/Miles and I was able to freeze the screen and copy it into my programmer and duplicate it on my cluster. But it was the WAY that programming was laid out that it finally clicked in my head and I finally understood what was going on and how it worked. Now I get it.

AS It has been explained. There are 34 blocks in total. The first 17 blocks are the mileage and the next 17 blocks are the check sum.

Let’s say we want to program 80,000 Miles/KM. take 80,000 divide by 17 and we get 4705.88235xxx Ignore the change and just take the 4705 and convert to HEX and we get 1261. Now we have to reverse the order so we get 61 12. Program all 17 of the first blocks with 61 12 and the next 17 blocks with all 00 00 and if we program the cluster at that point, we will get 79985 on the display. Which is 4705 times 17 = 79985

If we want to get to 80,000 exactly, we now have to count forward. 80,000 minus 79985 = 15 so, if we advance the count by 15 by changing the first 15 blocks up one digit to 62 12 (remember it is reversed so it’s actually 1262 hex is one more than 1261, reverse it and its 62 12)
and change the first 15 checksum blocks to FF FF we will then get exactly 80,000 on the display.

as it works on blocks of 17 and then rolls around and starts over. If we wanted to keep advancing. One block at a time. Making it 16 blocks of 62 12 and 16 blocks of FF FF we would display 80,001, 17 blocks would be 80,002 AND….if we keep going. And now make the first block 63 12 and the first block of the checksum 00 00 we would then have 80,003!!! And we keep advancing and rolling around in a circular pattern and we’ve got it!

So we can program any mileage that way exactly.

lets say we want 236,546 a number chosen at random. We first divide by 17 and we get 13914 ignoring the change. We then convert to HEX and we get 365A, we reverse it and get 5A 36. We change the first 17 blocks to 5A 36 and change all check sum blocks to 00 00 and we program and we should see 236,538 on the display. So if we change the first block to 5B 36 an the first checksum to FF FF we then should display 236,539, and if we keep going a total of 8 times (236,546 – 236,538 = 8) we then would get the exact number we want 236,546

this now makes perfect sense. It took a minute to click in my head what and how this was actually working but I get it now!

I need to do some real world testing next! Stay tuned for more fun and adventure!

ZC