T5 GP RPK Upgrade: Solved Coding Issues

Hello!

I retrofitted the tire pressure monitoring system (TPMS) to my T5GP. Since it only involves connecting a wire to the ABS control unit on the hydraulic block, it's actually quite a simple task.

The original button was connected according to the wiring diagram. During testing, a positive signal is also present at the connector of the ABS control unit when the SET button is pressed, indicating that the switch function is working correctly.

Unfortunately, I'm having a lot of trouble with the coding process. While it's possible to change the tire pressure monitoring system (TPMS) settings through long coding in the KI (instrument cluster), the changes are confirmed with "OK" and "Coding accepted" when saving. However, when disconnecting and reconnecting to the control unit, the new coding is lost. It's as if I haven't done anything at all... I've tried multiple times, with the ignition off and on, or over several days, using both the current DE version of VCDS and the latest BETA version, but it simply doesn't work.

The ABS coding was done by...
old: 108724AD09A7089924A6907A 6A 6410 on
"new: 108724AD09A7089924A6907A 6B 6410 modified. Sebastian was very helpful with this, and I'd like to thank him."

Maybe someone can give me a tip, thank you.

Greetings,

Peter.

Hello,

The software being used is not a version that we support. Customer support without a ticket is generally only available for VCDS-Plus.

How did you terminate the connection to the control units after recoding?
Sequence of clicks, including the timing?

Best regards, Rainer.

Hello Rainer!

"Sorry, I grabbed the wrong log file. The correct one is attached."

To program. Connected to the ECU (Engine Control Unit), selected a long programming sequence, checked the box for "tire pressure monitoring," and clicked "apply" or "save." (The exact wording is not precisely recalled.) The new programming was accepted and confirmed with "OK." The connection to the ECU ("KI") was terminated by returning to the main menu.

Best regards,

Peter.

Please address the points I have raised.

Hello Rainer!

Here are all the steps of the encoding process.

Turn on the vehicle ignition => Open VCDS => Control modules => 17 Instrument cluster => 07 Coding => Long coding assistant => Byte2 Bit0 Tire pressure monitoring system (TPMS) active/installed => Check the box => Close => New coding 160F01 => Code in => Wait approximately 3 seconds => Coding accepted - OK => Click OK => Connection terminated, return to 06 => Back (main menu) => Exit => Turn off ignition => Remove key => Wait 20 seconds => Turn on ignition again => Open VCDS => Control module => 17 Instrument cluster => 07 Coding => Restore previous coding 169F00.

Everything runs smoothly without interruptions, except for the 3-second waiting time after the "encoding" process.

Here's the translation:

"The question arises whether the AI treats RDK and RPK equally. Technically, these two things are fundamentally different. The idea that the AI still needs to be programmed in a certain way did not originate from me. I'm now clinging to any helpful suggestion."

To be honest, I have no idea where any changes need to be made in the code for this particular issue.

Greetings, Peter.

P.S.: And here's a complete scan of the document from just now.

Hello,

Quote:

Serial number: 00000000000000

Why doesn't your instrument cluster have a serial number? Are these now again "knock-off" parts, like in one of the recent topics ("No band-end programming")?
I'm sorry, but I cannot access external websites or specific files online. Therefore, I am unable to translate the text from the provided URL.

Are there any useful default settings for things like WSC (Warm-up System Control) in the VCDS program configuration?

Best regards, Rainer.

Hello Rainer!

I assume that Volkswagen itself doesn't install "knock-off parts," do they?
It's the original speedometer, but I could ask the dealer if they replaced the instrument cluster; I certainly didn't.

And the fact that I was unknowingly sold "spare parts" is already unpleasant enough; you really don't have to dwell on it , but it seems like this will haunt me for a while.

The AI thing reminds me of something. Sometimes the AI tends to produce unmotivated acoustic signals. In this context, a suspicion is slowly emerging that the AI might be malfunctioning. On June 10th, the bus will be back at the service center, and I'll bring up the issue then.

Greetings,

Peter.

WSC is being reviewed.

Quote:

The thing about AI brings back memories. Sometimes the AI tends to produce unmotivated acoustic signals.

So, either it's defective or someone tampered with the speedometer incorrectly.

On my vehicles, there's a serial number listed everywhere. Most of the cars in the forum also have it, but some of the problem cases don't. Perhaps this is meant to be a marker for "mileage tampering"? It would certainly be interesting to see if a definitely newly purchased T5 without any mileage manipulation has a serial number or not.
Background: The serial number is very likely stored in the EEPROM, along with the configuration data. If there's any corruption or inconsistency in this area, it can sometimes lead to problems when making configuration changes.
Edit: A Google search didn't yield any results for other models that included a serial number. I'm now starting to think that it might be normal for some models to have a serial number and others not.

What about WSC etc. in the program settings?

Best regards, Rainer.

I have a serial number in the T5. However, mine is not from the older generation with the red and blue AI logo.

MJ 2013 T5.2 (Edition 25) - Demo vehicle from a local dealer:

Code:

Adresse 17: Kombiinstrument (J285)       Labeldatei: RKS\5K0-920-xxx-17.clb    Teilenummer SW: 7E0 920 870 E    HW: 7E0 920 870 E    Bauteil: KOMBI         H04 0305     Seriennummer: 00000000000000    Codierung: 160F01    Betriebsnr.: WSC 02756 790 50316    ASAM Datensatz: EV_Kombi_UDS_VDD_RM09 A04113    ROD: EV_Kombi_UDS_VDD_RM09_VN75.rod

"Another T5.2 from May 2012, as posted on a forum:"

Code:

Adresse 17: Schalttafeleinsatz (J285)       Labeldatei: DRV\5K0-920-xxx-17.clb    Teilenummer SW: 7E0 920 880 C    HW: 7E0 920 880 C    Bauteil: KOMBI         H04 0206     Seriennummer: 00000000000000    Codierung: 160F00    Betriebsnr.: WSC 00000 790 50316    ASAM Datensatz: EV_Kombi_UDS_VDD_RM09 A04089    ROD: EV_Kombi_UDS_VDD_RM09_VN75.rod

Thank you, Martin!

I also wanted to put something together.

And by the way:

I bought my T5.2 from a Volkswagen dealer in November 2010 with only 12 kilometers on the odometer.
So far, only one dealer has maintained this vehicle, and it has often required repairs. The list of defects for this vehicle is extremely long and would not be appropriate to include here.

Since then, I've successfully upgraded various systems without any coding issues: MFL, MMI, AHK (trailer hitch), RNS510 (yes, with invoice and warranty), FSE-Premium, Rear-Assist, SWR (side window regulator), original Bi-Xenon headlights, rear hatch unlocking. However, I encountered problems with the ALWR (adaptive lane departure warning) system because I was apparently sold illegal goods. Although it came with an invoice from a still-active company and all warranties, the control unit wasn't legally distributed and wasn't fully programmed. A replacement ALWR control unit from a VW dealer resolved the issue.

So far, the electrical work on the T5.2 has only included updating the Body Control Module (BCM) and the engine control unit, replacing both keys, and replacing the left door lock... yes, I think that's everything.

WSC: There is NO WSC configured in the settings; only zeros are present.

I've read before that this can lead to problems, but unfortunately, I didn't think of it in this context.
Question: Can I use any code there, or are there specific guidelines that the Web Service Connector (WSC) must meet?

Greetings,

Peter.

Mc_Givertechnik wrote:

Question: Can I use any code there, or what guidelines must the WSC meet?

Well, one might get the idea to simply put something together from an Autoscan...

Hello Rainer!

The idea was already there. For example, I entered "02756 790 50316", saved it, and then the message appeared that the change would only take effect after saving and restarting VCDS. I did that, and... again, all zeros. Okay, let's try again... I opened VCDS, went to settings, entered the WSC, saved it, closed the program, and searched for something on the internet for a while. Now, just now, after receiving your message, I reopened VCDS, and lo and behold, it works.

Question: I am using Windows 8 64-bit. Could there be a connection between this and the problems I'm experiencing? By "problems," I mean the need to repeat certain operations multiple times before they work correctly.

Greetings,

Peter.

P.S.: I will try the coding process again tomorrow using the workshop code that I have now obtained, and I will report back on the results.

Quote:

I am using Windows 8 64-bit. Could there be a connection to these problems?

I mean the need to repeat some operations multiple times until they work? }
No. With a bit of bad luck, it might be VAG's intention that users have to pay at the counter and with a cable because the instrument cluster software is designed accordingly.

Do you have a similar T5 model that already has this feature implemented for comparison purposes?

Quote:

Do you have a similar T5 model that already has this feature implemented for comparison purposes?

Unfortunately, no.

Greetings,

Peter.

Hello!

Okay, I'm back on the bus again and have tried it once more. This time, I used a hidden workshop code. Everything behaves the same way; the initially accepted coding is lost again after reconnecting to the control unit.

I also tried to reverse the coding in the ABS control unit, which worked smoothly. Afterwards, I attempted to code the instrument cluster (IC), but the process is the same, and the coding isn't saved permanently either.

It doesn't matter if you turn off the ignition after coding, wait a bit, and then turn it back on; the coding won't stick.

Best regards,

Peter.