I don't know if you're doing it all right and it's your hardware that's the issue .... or if you're making a mistake.


If it's the hardware then there's nothing anyone can add so let's assume it's how you're doing it.

The instructions seem quite good on http://www.audienthusiasts.com/VagComABS.html so it could be you're new to VCDS.

Maybe this will help??

[1] Make sure you have the latest version of VCDS running.

[2] Always take a screenshot/a record of the module you're changing so you can restore it to how it was.

[3] Bytes start from the left to the right in their number order. This is displayed so you shouldn't get it wrong but double check you're in the right one.

[4] Bits are numbered from the right to the left i.e. 76543210
This still catches me out if I've left my brain turned off ! Bit 0 is the furthest on the right. Bit 7 is the furthest left.

[5] When making changes via the Long Coder always move the cursor onto another byte to ensure the change is set and then press escape. Check the change against the previous number before you hit do it.


Maybe post up what you've done to see if we can spot something? Also do you have 2G or 3G ??

It seems once you've done the relevant change to get it displayed in MMI (different for each system) then simply changing Byte 1 Bit 3 from 0 to 1 in 03- ABS should tell you if it's gonna work or not. i.e. do you get the "Coding Rejected - Error 31 - Request out of range message". Admittedly you may not have the Long Coder telling you what it's for but someones done the hard work for you and worked it out so just make the change above. It's hardly "flipping bits blindly"

If you get it then it seems the hardware is incompatible. Then it's just enabling it for the Instrument Cluster.
i.e. [17 - Instruments]
[Coding - 07] -> Long Coding Helper -> Byte 4 Bit 0 - Change 0 - 1



As I say post up what you've done and lets see if we can narrow it down.