Cluster Programing - MK1 Audi TT

[Zeilekd]

Hello,

I have a 2002 Audi TT that has a defective cluster. My existing cluster still works but periodically glitches out.

I am either going to replace the MCU on my existing cluster or get a different cluster from a salvaged MK1 TT.

Will VCDS allow me to pull the existing configuration from my existing cluster and then write it to either my repaired cluster or a different cluster?

Could somebody please point me to the instructions to accomplish this?

Thanks!

Kurt

 

[Uwe]

Will VCDS allow me to pull the existing configuration from my existing cluster and then write it to either my repaired cluster or a different cluster?

2002? That will be Immo-3. You can swap clusters with VCDS if and only if you have PINs both for your car and the donor car. I think your best bet will be to send clusters to someone who specializes in that kind of thing. @EuroX or @Jetta 97 may be able to help you.

-Uwe-

 

[EuroX]

VCDS will not pull mcu data or anything that will help. VCDS will help you adapt a used cluster IF you have both pins meaning pin for the current cluster and pin from the donor cluster to make the adaption. Specialized tooling is needed to pull data from cluster mcu which consists of 2 parts. Flash file from mcu as well a eeprom data that's located in the other part of the mcu. In most cases MCU is locked. All these clusters are MM cluster and are known for failing. I am currently working on a permanent solution to this issue. We are currently in the testing phase but our solution will be full proof.

 

[Jetta 97]

Even with both Pins , if TT cluster is not in Factory mode (Virgin state) VCDS or any other tool will not be able to adopt used cluster. I have done this may times.

 

[Zeilekd]

VCDS will not pull mcu data or anything that will help. VCDS will help you adapt a used cluster IF you have both pins meaning pin for the current cluster and pin from the donor cluster to make the adaption. Specialized tooling is needed to pull data from cluster mcu which consists of 2 parts. Flash file from mcu as well an eeprom data that's located in the other part of the mcu. In most cases MCU is locked. All these clusters are MM cluster and are known for failing. I am currently working on a permanent solution to this issue. We are currently in the testing phase but our solution will be full proof.

@EuroX Thanks for the reply. How close is your solution to being available? Are you looking for trial customers? Currently my car is not reliable since I never know if I turn it off whether it’s going to kick into an immobilized state. I’m getting ready to send my cluster off to the UK for new MCUs but I’d like to stay local if possible.

 

[Zeilekd]

Even with both Pins , if TT cluster is not in Factory mode (Virgin state) VCDS or any other tool will not be able to adopt used cluster. I have done this may times.

@Jetta 97 what do you mean virgin state? Are you suggesting that since I had the lcd replaced it’s no longer in a virgin state?

 

[Zeilekd]

2002? That will be Immo-3. You can swap clusters with VCDS if and only if you have PINs both for your car and the donor car. I think your best bet will be to send clusters to someone who specializes in that kind of thing. @EuroX or @Jetta 97 may be able to help you.

-Uwe-

@Uwe thanks for the introductions!

 

[EuroX]

@Jetta 97 what do you mean virgin state? Are you suggesting that since I had the lcd replaced it’s no longer in a virgin state?

If only the LCD was changed you should be alright. What Jetta97 is saying is that with audi TT 8N most time donor dash needs to be reset to virgin state before a pin can be used to adapt it. In regards to my solution. It's not ready yet. Ironing out the kinks with the custom firmware to make it on solid solution so that the dash never fails again.

 

[usmcfieldmp]

In for info. My TT is also in need of cluster service, but I need to figure out my Data Bus Failure issue first (maybe the cluster is the issue?).

 

[Zeilekd]

@Uwe thanks for the introductions!

@Uwe is the Pin that everyone is referring to, the same as the 4 digit immobilizer code? If it is, I have it for my cluster from when I got a new ignition key made. I’d just like to clarify the terminology. And just to be clear, I’m not getting this confused with the radio theft prevention code.

 

[Uwe]

@Uwe is the Pin that everyone is referring to, the same as the 4 digit immobilizer code?

Yes. Perhaps I should have written "Immobilizer PIN" to avoid confusion with:

the radio theft prevention code.

But the catch with Immo-3 is that you need both PINs, the one for your car, and the one for the donor car in order to swap clusters. The latter could probably be extracted from a used cluster with the appropriate immobilizer tools.

-Uwe-

 

[vwtech]

I had a customer MK1 TT rebuilt by @EuroX took some time but it worked out.
Reason I wanted rebuild was to avoid swapping issues.
Maybe an option for both of you?
Just a thought....

Good Luck

 

[Jetta 97]

@Uwe thanks for the introductions!

Answer is in post #8.
What is wrong with your cluster, what problems you have?

 

[Jetta 97]

In for info. My TT is also in need of cluster service, but I need to figure out my Data Bus Failure issue first (maybe the cluster is the issue?).

I am local to you, I am in Dallas-McKinney area. contact me direct to see what is going on with your cluster .

Thank you

 

[Zeilekd]

Yes. Perhaps I should have written "Immobilizer PIN" to avoid confusion with:



But the catch with Immo-3 is that you need both PINs, the one for your car, and the one for the donor car in order to swap clusters. The latter could probably be extracted from a used cluster with the appropriate immobilizer tools.

-Uwe-

Thank You!

Answer is in post #8.
What is wrong with your cluster, what problems you have?

 

[Zeilekd]

@Jetta 97 here is a link to a video I posted to the TT FORUM on Facebook. Please let me know if you are unable to access it.

Audi TT Mk1 Repair tips and procedures | I’ve already sent my cluster out to Odo-Pro for repair | Facebook

I’ve already sent my cluster out to Odo-Pro for repair. Peter at Odo-pro changed the LCD display and went over several of the solder joints. I got it back and it still had this issue. I sent it back...

www.facebook.com

 

[EuroX]

@Jetta 97 here is a link to a video I posted to the TT FORUM on Facebook. Please let me know if you are unable to access it.

Audi TT Mk1 Repair tips and procedures | I’ve already sent my cluster out to Odo-Pro for repair | Facebook

I’ve already sent my cluster out to Odo-Pro for repair. Peter at Odo-pro changed the LCD display and went over several of the solder joints. I got it back and it still had this issue. I sent it back...

www.facebook.com

Most likely MCU failure, fairly common among other issues. All TT clusters are MM that's why they are shit, hence why we are working on using a VDO dash that does not suffer from any of these issues.

 

[Crasher]

TT1 cluster failure was such a big problem in the UK it was the subject of a recall but they still failure

 

[EuroX]

Again MCU failure as stated previously.

 

[Zeilekd]

Most likely MCU failure, fairly common among other issues. All TT clusters are MM that's why they are shit, hence why we are working on using a VDO dash that does not suffer from any of these issues.

@EuroX, it can go for days without glitching and then suddenly glitch multiple times. Would you recommend I have the MCUs replaced or just get a reconditioned cluster? If the MCU failure is that common it seems like a reconditioned cluster with an old MCU is a likely to put me right back in the same situation. I also hear from one guy who offers reconditioned clusters, who would be willing to clone my cluster to a reconditioned one, that ONLY THE FACTORY can put the data on the MCU. Does this make sense?