Hi guys can someone hopefully help me? I have posted about changing the dash clocks on my car! So i spoke with the auto spark who said they can code them for me and has stated which I'm aware of is to get a set of clocks to march my car. Mine is a 2011 1.6 tdi 3t2 920 911H and the donor car I've found close by is 2010 (I think) 1.9 tdi 3t2 920 911D. From what I've read is the letter prefix at the end only seems identify what year/period the clocks are from for example if I was to purchase a new set from the dealer it could end up being 3t2 920 911K if I'm right in what I've read? So would anyone know if the D prefix would be suitable for my car as a set with the H prefix seem to be scarce .

 

It's the last 3 numbers that really count and state whether you have low, mid or highline clocks. For my 2010 Yeti I have 940 waiting to retrofit

Well to update I had the clocks coded and got them back tonight. I fitted them back in and they seem to be OK. I can now read the MFD and they even updated the mileage as I was sitting around 312k miles. Any way as soon as I turn the ignition on the cluster pings and error flashes where the mileage is. The car starts a drives and everything in-between so would I need the car scanned to see what the error is for ? 

Do you mean that they made the new instrument binnacle show a mileage value less than the true 312K miles?

 

I dont ask the question to moralise but the ECU also has a record of the mileage (it can be consulted via VCDS) and perhaps the error code is because the reading on the instrument binnacle does not match?

 

I did the opposite, I fitted a remapped ECU that had come from a donor vehicle, my odometer reading remained as it had always been, there were no error codes but if I did a mileage check using VCDS it showed the ECU as having done a much higher mileage than the odometer. I gave the old ECU with the standard map to the new owner and explained the mismatch.

14 hours ago, octaviani said:

 Any way as soon as I turn the ignition on the cluster pings and error flashes where the mileage is.

 

That sounds like the auto-locksmith hasn't done a proper job and messed something up

To be honest I think JR might be right the mileage isn't bang on its 200-300 miles out which Im not worried about I'm more worries if the immobiliser hadn't been sorted and decided to come on somewhere inconvenient. There hasn't been any other issue and the car starts and run and all the dials work I've done about 100 odd miles at present so seems to be fine. So I'm assuming it's the mileage. If I can be bothered and I'm not going to pay over the odds I'll see about getting it looked at as I've couple issues for mot to sort as it decided to snap a rear spring the other day.