PDA

View Full Version : Lexus IS 200 1999 doesn't add up after change



niripas
13th January, 2012, 07:22 PM
I edited the 93c46 using points on the PCB with Tacho Universal. It was showing ok old mileage (verified with TachoSoft). After change the cluster was put in the car. New mileage showed up. And stayed. While the trip counter works, the mileage doesn't change while driving. What could go wrong?

z786
13th January, 2012, 07:47 PM
post dump
bytes need to be stepped up

niripas
13th January, 2012, 08:26 PM
Original dump uploaded, I will post changed dump as soon as the car will be with me. Original mileage 195868. Which bytes stepped up?

r6eck
13th January, 2012, 08:31 PM
look at last 4 lines OF6E F091 ,see where it becomes 0F6E FO96 ,this is your step up

Meat-Head
13th January, 2012, 08:35 PM
niripas (http://www.digital-kaos.co.uk/forums/members/200024-niripas/) Newbie

Join Date: Aug 2010
Posts: 3
Thanks: 0
Thanked 0 Times in 0 Posts
Downloads: 0
Uploads: 0


Hi there, what did you write the IN-correction as?

lashkar97
13th January, 2012, 08:51 PM
i change that in 12500 km
check that and write on dump

niripas
13th January, 2012, 09:29 PM
look at last 4 lines OF6E F091 ,see where it becomes 0F6E FO96 ,this is your step up
?? where? what offset do you mean?


Hi there, what did you write the IN-correction as? I put the following bin:

it should be 124882 and it shows it correctly, it just doesn't count the global mileage

lashkar97: Actually it looks like you edited the zip archive, not the bin inside it, could you reupload, please?

niripas
13th January, 2012, 10:43 PM
Sorry for the confusion.
What I did:
I got a cluster from Lexus IS 200. Connected Tacho Universal to it via points on board. Tacho displayed 195868, which I verified with TachoSoft as correct. Then I changed the value with Tacho Universal function Adjust KM and wrote the eeprom with what I supposed was 124882 (but again tachosoft verified it).
Cluster then went into the car and it always display 124882.

What went wrong?

niripas
15th January, 2012, 06:08 PM
Bought another cluster, repeated procedure - works ok. Looks like I broke the first one somehow...

z786
15th January, 2012, 06:43 PM
i haventgot hex editor on this laptop mate but an explanation on how to step up bytes has been given, u have to do that

niripas
17th January, 2012, 05:28 AM
I still don't know which bytes... Here is the original dump:
Offset(d) 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F

00000000 2D 01 2D 01 2D 01 2D 01 2D 01 2D 01 2D 01 2D 01
00000010 2D 01 2D 01 2D 01 2D 01 2D 01 2D 00 2D 00 2D 00
00000020 2D 00 FF FF FF FF FF FF FF FF FF FF FF FF FF FF
00000030 FF FF FF FF FF FF FF FF FF FF FF FF 00 00 00 00
00000040 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00000050 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00000060 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0C B2
00000070 03 90 38 1A 18 96 07 F4 12 60 00 00 3A 3A 00 00

Would you mind explaining it to me what should I change, please?