I doubt driving around a block is long enough for the system to relearn.

On a MY12, you probably don't even need a button assuming you have a maxidot cluster running SW: 06xx or newer...

Try these instructions: https://www.briskoda.net/forums/topic/363554-tpm/#findComment-4746144

Does the signal chime occur after the pairing process?

I have never Edit Controller 4c

On Cluster Software 608 tpms Reset dont work

Edited yesterday at 14:401 day by Cairus

No signal chime during coding, but I do see the dash symbol and sometimes it's flashes. It seems this process involves at least two things - The ABS controller 03, and instruments 17. VCDS gives me the long coding helper and check boxes to code bits to enable TPMS. Perhaps Ross Tech got something wrong and I should look further into how the bytes are coded. I don't think Skoda want MY12 Yeti to have ABS TPMS!

Give me some time, I'll screen grab all vcds long coding screens with TPMS tick boxes and hope somebody can make sense of them or suggest something has to be done that's missing.

My white screen display did once add TPMS and a reset option to the settings menu, but this was after I code enabled every entry in vcds refering to TPMS. Then I got a bunch of Gateway errors. My older V.W has nothing in the Gateway list enabled for ABS TPMS. There were 2 options in my Yeti Gateway controller list - 4C and another at 6? Although each can be enabled, they error on scan with no communication because it seems they are additional hardware controllers (I suspect for internal tyre sensors?)

I thought taking it for a short drive it would learn sufficient to flag the large tyre pressure change but it didn't change anything. I've found a relatively cheap TPMS switch kit with wiring on Ali, but I'm not optimistic. It appears to have a local indicator backlight led wiring. I would be better reassured if after pressing the switch there was an acknowledgement of some kind 'ding' or dash symbol flash.

I've already read the post link instructions from langers2k and tried it several times. You will see mention of module 4C (Tire Pressure II) which the OP added to the Gateway list. I also get the new Tyre pressure section in MFD settings. But MY12 knows nothing about 4C and won't communicate when enabled and what is 'Tyre Pressure II', something different to Tyre Pressure or TP 1? Do you guys have module 4C showing in your Gateway list without error codes?

Edited 21 hours ago21 hr by voxmagna

4C is a virtual module, it's not expected to be diagnostic compatible.

I don't have my MK2 Octavia any more but that was SW:0608 for the cluster and did support reset via maxidot. It was also the same ABS module.

Just to confirm, you changed the ABS coding from 933F400E09260102C91302EA9022808A300000 to 933F400E09260102C91302EA9022808A360400 ? IIRC, byte 16 bit 1 doesn't have a checkbox so you need to modify it manually.

Then do the instrument cluster and gateway installation list changes.

Thanks I'll recheck the long coding and just try to match the bytes. I did find a web post refering to virtual module 4C. The comment was that vcds was including it in the Gateway list (which then throws errors) when they should have masked it out as invisible. I'm always aware diagnostics relies on the software writer interpretation. I perhaps rely too much on the helper for Byte coding. On previous versions of vcds they incorrectly linked the wrong label files. Label files are the human friendly text created by Ross-Tech. IMHO ECU label files don't always match what you have.

My Yeti has ESC et Al and some comments I found suggested indirect ABS TPMS may not be possible. But I'll persevere. Any idea of mileage for the ABS TPMS learning phase and can I expect it to be inactive until it's learned? I am testing by letting air out of a tyre after coding and vcds reset, but it occurs to me, many may change the coding and not actually test immediately after.

That ABS module is definitely capable of indirect TPMS - being a Yeti has nothing to do with it

VCDS is asking the gateway which is correctly stating there is an unregistered module. Neither VCDS or the gateway know if it's a real module or a virtual one, regardless you need to add 4C to the gateway installation list and then it's fixed.

For example, "46-Central Conv" is shown in your installation list currently - however, that's also a virtual module (created by 09). It's not unusual in the VAG world.

I don't think there is much documentation about the learning procedure. I would guess at least 10-15 minutes of 15mph+ driving should get a OK baseline and hopefully a complete calibration after an hour or so. Just as an example from another forum regarding indirect TPMS on a MK60EC1:

• Drove about 50 miles with equally inflated, sensorless tires. No TPMS light or other warnings on dash

• Deflated one of the rear tires slightly, by about 8% (38 -> 35). Drove about 5 miles. No warning light.

• Deflated same tire by about 20% of original value (38 -> 31). TPMS warning light appeared after about a mile.

edit:

Slightly older MK60EC1 in another Yeti showing it working without the phycial button. They had to use VCDS to reset the learning each time instead: https://www.briskoda.net/forums/topic/192503-yeti-with-tpms-switch-abs-module-coding-required/

The extra coding changes and adding 4C is only required to enable reset via maxidot cluster. They also suggest an hour calibration drive.

Edited 1 hour ago1 hr by langers2k

O.k thanks, I made some progress but not there yet. I compared my long code with yours after following vcds labels for byte change and there was a difference. I assumed if I copied and pasted your long code then all the ABS coding would be correct including the unlabelled byte. Did that. Then enabled virtual module 4C in the Gateway installation list and for the first time the scan came back listing 4C without errors.

At IGN on boot I didn't see the tyre dash icon or additional tyre settings in the display. Then I enabled Tyre pressure II in instruments and the icon came up. I went to dash settings store and that worked until I tried to actually store and the confirmation 'Tyre pressures not stored' was given. I'm puzzled about this because tyre pressures aren't measured or stored by indirect ABS TPMS. The Tire pressure warning stayed stuck on the dash screen and through IGN ON reboot. Reset via basic settings in ABS screen confirmed TPMS was active, and after reset the screen block message changed, but the icon still remained stuck on.

I read ABS TPMS reset via vcds didn't work for one poster (Although the helper text said it should without the switch). I'm wondering if there are at least 2 different TPMS systems and messages in the display aren't for indirect ABS so the warning stays lit because it gets garbage data and requires the hard wired reset switch on the ABS controller? It would make sense after coding and enabling to set the warning to default on, then have to reset to test the switch which I've now discovered after holding 2-3 seconds gives a confirmation ding.

When the switch kit arrives I'll explore getting the ABS switch wire through the firewall to test my theory.

This is important too:

1. Deflated one of the rear tires slightly, by about 8% (38 -> 35). Drove about 5 miles. No warning light.

2. Deflated same tire by about 20% of original value (38 -> 31). TPMS warning light appeared after about a mile.

Deflating from 38 to 31 is a big change, although it might have lit at 10% but still took longer than what I'd expect. Thinking some, road conditions (and potholes!) will cause changes in tyre rolling radius as suspension moves up and down and they may want to factor in average background error noise.

Thanks for your help.

Edited 1 hour ago1 hr by voxmagna

1 hour ago, voxmagna said:

No luck yet.

Coded Instruments 17 and ABS 03, Also tried Electronics Byte 8. After coding & scanning there were no errors and the dash TPMS warning now lights momentarily at IGN on for dash lamp self test.

Checked a front tyre pressure at 2.4 Bar, did ABS TPMS reset via vcds (accepted) & drove around the block. Reduced pressure to 2 Bar and repeated the test drive. No TPMS warning.

I know on my V.W working ABS TPMS is very sensitive, it comes on after a tyre change when new tread is thicker and rolling radius increases. I've sometimes had it come on working on the car IGN on and jacking a wheel.

I'm puzzled that if it was simple to enable, they would have done so on the car when new. According to vcds labels, resetting TPMS in the ABS controller should work without a reset button and the only thing left could be that first hard reset is an enabling function? From a few photos of past mod. kits, one wire end had a connector pin. I'll guess that's the wire for the ABS connector.

The ABS coding for Maxi-Dot control is different from that used with a hardware button.