PDA

View Full Version : MGZT mileage



chris_e36_328
11th August, 2011, 04:31 PM
Hi guys,
got an MG ZT 2.0d, the DM2 lists only c56 as Rover 75 but does not read the correct value.
Is it safe to assume the ZT and 75 have same algorithm and the data is placed in the same areas, as every package I'm looking for info only lists the 75? I'll be at customers tomorrow again and will try read it with Xprog, but wonder whether it should be done as one of the bimmers. Any info would be greatly appreciated.

dashradio
11th August, 2011, 10:15 PM
Same, 93c56 but read it off board, some programmers corrupt these, or diagnostic with Diga

chris_e36_328
11th August, 2011, 11:00 PM
Thanks bud, much appreciated. I did actually pull it out. DM2 been good so far, but even though I soldered it twice on the board it would still not recognise the mileage so I left it at that till I get something else to read it properly with to do manual edit. Many thanks again. do you know whether the LCM will go by OBD as in BM or similar jobie as with EWS?cheers

chris_e36_328
19th August, 2011, 11:18 PM
Hi guys,
unfortunately I got stuck on something that I assumed was going to be an easy one. My bad I guess.
Please could someone be willing to shed some light on this?
The car is 2004 MG ZT? 93CS56 read with XprogM offboard, however the data does not seem to match what's in tachosoft. Please see attachements. Currently 160k.cheers

vageric
20th August, 2011, 08:27 AM
post your dump

chris_e36_328
20th August, 2011, 10:55 AM
Here it is. 160k, would like 145k if possible. many thanks

chris_e36_328
21st August, 2011, 06:28 PM
has anyone got a calculator I could use for the ZT?

r-parts
21st August, 2011, 06:51 PM
76391

please try this

chris_e36_328
22nd August, 2011, 12:13 AM
please try this

Many thanks bud. Just a quick one: does it mean, that the fact that the original file's mileage content does not match the tachosoft description needs to be disregarded? Only asking as been at customers twice already and wouldn't want to do another trial run and mess him about if it doesn't go this time either. Many thanks again pal.

r-parts
23rd August, 2011, 10:26 PM
I tried to read with dp3, it showed the wrong miles, that happens some times.
when i backup and programm it shows the miles i put in.

this is a file to try.
so to awnser your question, i just corrected as i always do, you must try if it works, dp3 has not have MG menu.
when it shows incorrect, swap milage bytes on line 040 and try again.

chris_e36_328
26th August, 2011, 12:30 AM
I tried to read with dp3, it showed the wrong miles, that happens some times.
when i backup and programm it shows the miles i put in.


Job done. Thanks bud,much appreciated.

r-parts
26th August, 2011, 08:17 AM
this was with my file or did you have to swap the milaege?

In that case just ignore the old readings and put in new calculated miles.

chris_e36_328
26th August, 2011, 09:14 AM
Hi mate, not sure what you mean by
..or did you have to swap the milaege?

Your file was done using same algorithm as licznik and tachosoft, which seems to be incorrect for the ZT. Location is correct, but the calculated value is not.That was my original querry. DM2 sorted it out no probs.Thanks anyway

myexige
27th August, 2011, 10:16 AM
licznik and tachosoft will work if you reset the service timers before changing anything.

chris_e36_328
27th August, 2011, 08:57 PM
licznik and tachosoft will work if you reset the service timers before changing anything.
Thanks bud, will give this a go next time. cheers for sharing.