View Full Version : Ford Transit MY16 Correction
autoTkey
29th May, 2023, 08:26 AM
Hello,
I got this from dash of a Ford Transit MY2016 TDCi with V850 D70F3525 unlocked inside.
It should be 183528km. Could someone update it to 38528km, please?
autoTkey
30th May, 2023, 06:38 AM
No one can do these or no one is interested?
autoTkey
30th May, 2023, 10:56 AM
Solved. It was simple actually with a hint from older thread - https://www.digital-kaos.co.uk/forums/showthread.php/868225-Ford-transit-2017y-need-help-correct-miles-d70f3525
Also a pinout:
965002
https://www.youtube.com/watch?v=1wzTCM9gTNY
autoTkey
1st June, 2023, 03:27 PM
Since the car is away and I could not test it on bench because it needs CAN signal only now I got confirmation from the client that this procedure didn't work.
It showed only 00000's instead of the new mileage.
Attaching the file I changed. I guess not so simple after all. Or something stupid I didn't do...
Hopefully someone could correct it.
autoTkey
5th June, 2023, 06:27 AM
Still not solved... Is it not possible by EEPROM?
marina_rv
5th June, 2023, 02:31 PM
data AD 6A F0 0A
reverse -> Dec / cons = distance
autoTkey
6th June, 2023, 09:02 AM
Yes, mate. That's exactly what I've done in the edited dump which I posted 6 days ago.
Thanks but problem is something else.
It is a simple calculation 024BE46D reversed but car does not accept it. Dash shows 000000's instead of the mileage.
Anyway in few days the car will be able to come to our workshop and will try it again.
autoTkey
16th June, 2023, 10:20 AM
data AD 6A F0 0A
reverse -> Dec / cons = distance
Nope, this is not the real mileage data, mate.
After driving for some kilometers the car still shows the same data in the dump. So if it does not change then it is not the mileage or it is not the main memory for the mileage...
Powered by vBulletin® Version 4.2.5 Copyright © 2025 vBulletin Solutions Inc. All rights reserved.