Mitsubishi Colt 2007 L56

[drpeter]

Hi,

i've got a small problem with Colt '2007, read with diga actual value on display was 62744km, diga gave me 62530 (-200km), I need 53660km +/- 50km, so I programmed 53460, now display shows 54200km? Can someone calculate exact value for me 53660km? I am not very good with this and have not much time.

Many thanks,

Peter

[PremierD]

Hi,

i've got a small problem with Colt '2007, read with diga actual value on display was 62744km, diga gave me 62530 (-200km), I need 53660km +/- 50km, so I programmed 53460, now display shows 54200km? Can someone calculate exact value for me 53660km? I am not very good with this and have not much time.

Many thanks,

Peter

The maths are not that accurate mate ... +/- Ax32....but try this ....

[drpeter]

The maths are not that accurate mate ... +/- Ax32....but try this ....

Thanks mate, value became 53390km with your dump, if I programmed 53710km then value became 53795km, so I programmed 53690km it became 53503 and drove the car this morming to another customer far away, when I came back mileage was 53654, job done :-).

[PremierD]

Thanks mate, value became 53390km with your dump, if I programmed 53710km then value became 53795km, so I programmed 53690km it became 53503 and drove the car this morming to another customer far away, when I came back mileage was 53654, job done :-).

Some drive mate ....As I said + or -....Just a lottery ..Glad you sorted it .....

[Motika]

Guys. Could somebody please alter this mitsu colt 2007 dump to 39323 miles. It currently has 49127miles. L56R.

Thanks

[tachonow]

Car type: Mitsubishi Colt - 93c56 - 2005 year
The mileage is stored in the next lines:
00C0: 0C 35 F3 CA 0C 35 F3 CA 0C 35 F3 CA 0C 35 F3 CA
00D0: 0C 35 F3 CA 0C 35 F3 CA 0C 35 F3 CA 0C 35 F3 CA
00E0: 0C 35 F3 CA 0C 35 F3 CA 0C 35 F3 CA 0C 35 F3 CA
00F0: 0C 35 F3 CA 0C 35 F3 CA 0C 35 F3 CA 0C 35 F3 CA
where the next bytes:
0C 35 F3 CA - is a mileage

km/32>hex then NOT
100000km/32=3125>hex=0C 35 NOT=F3 CA

[Motika]

Car type: Mitsubishi Colt - 93c56 - 2005 year
The mileage is stored in the next lines:
00C0: 0C 35 F3 CA 0C 35 F3 CA 0C 35 F3 CA 0C 35 F3 CA
00D0: 0C 35 F3 CA 0C 35 F3 CA 0C 35 F3 CA 0C 35 F3 CA
00E0: 0C 35 F3 CA 0C 35 F3 CA 0C 35 F3 CA 0C 35 F3 CA
00F0: 0C 35 F3 CA 0C 35 F3 CA 0C 35 F3 CA 0C 35 F3 CA
where the next bytes:
0C 35 F3 CA - is a mileage

km/32>hex then NOT
100000km/32=3125>hex=0C 35 NOT=F3 CA


Forgive me for being a bit thick but i dont understand the 'NOT' bit

[tachonow]

Forgive me for being a bit thick but i dont understand the 'NOT' bit
Its logic function for operation FFFF- hex value.
So FFFF- 0C35=F3CA
Use Windows Scientific Calculator. Have this function.

[Motika]

Thanks for the help but i have just tried this algo but for the current mileage on my dump and the result is not the same as my dump

[PremierD]

Forgive me for being a bit thick but i dont understand the 'NOT' bit

It's really Xor mate .. or subtract from FF FF ...
But the algo is / 16 .. or 16.191
Replace the hex on the above lines with 0F 44 F0 BB for all the instances of 13 13 EC EC in your dump .. and it will be close I think

[Motika]

Strange problem apparently my programmer can read this L56R eeprom as 93c56 but is unable to program it. It can only program it as a 93C56x16. If i then program it as 93c56x16 i get an incorrect value on the dash. I'm using original Upa-usb and its the only programmer i've got at the moment. Any ideas how i can resolve this?

[Motika]

Have just realized that i made an error in reading this as 93c56 instead of 93c56x16 and thats means i've corrupted my dump. Anyone got a dump for this car in miles please?

[Motika]

Help! Somebody?