VW Vortex - Volkswagen Forum banner

VCDS MKVI / MK6 Platform, Handy Coding tweaks

1M views 1K replies 301 participants last post by  Bentiem 
#1 · (Edited)
Ross-Tech is not responsible for any damage or problems that may result from following these instructions. They are to be used at your own risk. The Ross-Tech Wiki platform specific tweaks pages have replaced the contents in this post. This thread is active for general discussion.


  1. It is always recommended to perform a complete Auto-Scan and save it prior to coding changes. Please see the Online Manual: Auto Scan Screen
  2. Never Copy coding from a different vehicle and Paste it to your module(s).
  3. All Auto-Scans must be posted using the current release of VCDS which is found Here





----------------------------------------------------------------------------

Notes:

Address 09 - Central Electronics:


  1. If this module does not communicate, unlock all vehicle doors and try again.

  2. Byte 18 *Do Not alter this if you are not retrofitting rear lights*





Address 46 - Central Conv.:

  • The 46-Cent. Conv. module does not really exist on the 2010 Golf (or other Mk6 type vehicles). All functions formerly found in 46 have been integrated into the (BCM) 09-Cent Elect. We think a "virtual" entry for 46 is still included in the Gateway Installation List for compatibility reasons (internal communications with other modules in the car).


Address 55 - Xenon Range

  • It may be possible to enable a Tourist Mode feature via the MFA as shown in this example Travel Mode. Registered customers will need to contact us directly for assistance and have a legitimate need for this feature, such as traveling to another country where driving in the opposite side of the road is necessary.


Address 62 - Door, Rear Left:

  • Later production MK6 platform vehicles may use rear door modules that are integrated in the front much like 46 is integrated in 09. We think a "virtual" entry for 46 is still included in the Gateway Installation List for compatibility reasons (internal communications with other modules in the car).


Address 72 - Door, Rear Right:

  • Same applies from Address - 62 above.


Address 56 - Radio:

  • The newer RNS-315 does not communicate with a scan tool. Use address 37-Navigation (J794) instead.


----------------------------------------------------------------------------

Retrofits:

  • Retrofitting information is available on the Ross-Tech Wiki:
    Retrofitting Page

  • RoW Vehicle, Retrofit indirect TPMS using coding only:
    How to: retrofit indirect Tire Pressure Monitoring in 5 minutes. (7K6)
    Depending on the Instrument cluster that's installed, Byte 2, Bit 0 may need turned On = 1 for the TPMS light/icon to work. The current VCDS includes this documentation in the Long Coding Helper

    Side notes:
    • M.Y. 2010 BCM equipped US market vehicles used the 65-TPMS module, which was simply an additional function of the 09-Cent. Elect. module, with TPMS sensors mounted in each wheel.
    • Starting in M.Y. 2011 the U.S. market 1K/AJ vehicles now use the ABS style of TPMS mentioned in the thread above. They have the TPMS reset button from the factory.


  • NAR Vehicle, European switch retrofit:
    DIY - Wiring a Euro Headlight Switch to run parking lights

  • NAR Vehicle, Alarm Siren retrofit:
    DIY: Alarm Siren Install

  • NAR Golf / Gti LED Tail Light retrofit:

    Forum discussion about coding and installing LED lights and Byte 18 coding can be found here: LED tail Install with or without Rear Fog

    2012 Golf R and 2012 Separate LED DRL type Xenon Golf models should also see Tom's notes on the extra wire swap. Notes on LED Tail / Rear Fog Install

    Most NAR vehicles retrofitting the rear fog lamp with factory/incandescent configuration can choose the standard RoW selection in the Long Coding Helper. They need to swap wires as mentioned in the above links and the following should be helpful: Non-LED Rear Fog Light

    If you cannot find the coding configuration after reading the various forum sources, Registered Ross-Tech customers can send us complete Auto-Scans with "LED Tail Light retrofit" in the subject line. Please include the part number of all four lights, RH or LH drive vehicle details, and with or w/o a rear fog lamp.

  • NAR Jetta LED Tail Light retrofit:
    This is still a work in progress, but forum discussion about coding and installing LED lights and Byte 18 coding can be found here: 2010 Jetta LED Tail Coding

  • NAR Golf / Gti Auto Headlights and RLS retrofit:
    Tips related to Coding and Adaptation on a US 2010 Market Gti can be found here: Adding Rain and Light Sensor

  • Door Warning Lights retrofit:
    Installing Door Waring Lights involves wiring and coding. Coding for the latest door modules is documented in the current release of VCDS but there are two styles of door modules as noted above. The production split for NAR vehicles was in 2010:

    1. If the vehicle has the conventional modules all 4 will communicate independently using addresses 42, 52, 62 and 72. In these cases connect to each module and add the "Door Exit/Warning Light installed" (typically + 64) value to the existing short coding. Ex: If the short coding was 0001204 add 64 for a new value of 0001268.
    2. If the vehicle uses the newer (UDS) style of modules only the front modules will communicate using addresses 42 and 52. Each rear module can be accessed and long coded from the respective right/left front module. Select the front (master) or rear (sub-system) module from the drop down list and use the long coding helper to configure "Door Exit/Warning Light installed" by checking the box and saving the new coding.

  • Mirror down in reverse
    Mirror down in reverse is generally not possible with coding alone if the car did not have this feature from production. This typically involves/requires:

    1. Coding the 09-Cent. Elect. module for the option.
    2. The pair of front window motors/door module addresses 42-Door Elect, Driver -and- 52-Door Elect, Pass. capable of and coded for this feature.
    3. The exterior passenger mirror assembly with memory capability and additional wiring from that mirror to the door module.


    Ross-Tech does not have a complete list of the door modules that support this. If you need assistance determining what parts are required please contact your local dealer or parts distributor.


----------------------------------------------------------------------------

General:

Using the Long Coding Helper when checkboxes are not present

Several of the convenience settings can be changed from the MFI without a scan tool. VW has this site for all models:
http://www.ownerwelcome.com

----------------------------------------------------------------------------

Testing:

If anyone wants to test this additional menu, please post your scan.

Auto-Close

Explained in detail by Mr.Timewise Here

Dana's Scan
A3 feedback
Mk6 door warning lights
[color=#000080 & [color=#404040 [/color]
 
See less See more
#6 ·
Re: VCDS MKVI / MK6 Platform, Handy Coding tweaks (mtben)

Quote, originally posted by mtben »
Will you also include information about the new stationwagon?
More exactly 5k0 937 087 D

That looks like a 2010 Jetta BCM / 09 module. Please create a new thread with your AutoScan and any specific questions you have.
 
#8 ·
Re: VCDS MKVI / MK6 Platform, Handy Coding tweaks (Dana @ Ross-Tech)

Does the Jetta Sportwagen MKVI require a +CAN type cable or will my old HEX-USB cable be able to address all modules?
 
#10 ·
Re: VCDS MKVI / MK6 Platform, Handy Coding tweaks (Dana @ Ross-Tech)

Quote, originally posted by Dana @ Ross-Tech »
You will need a HEX-USB+CAN interface. If you are a registered Ross-Tech customer we offer upgrades. http://www.ross-tech.com/Merch...etHEX

The Micro-CAN would also work for that vehicle. http://www.ross-tech.com/Merch...AGCOM

Thanks. But from the way I read about Micro-CAN, it wouldn't work for my Touareg (despite the fact that it has CAN-BUS)? Plus being more expensive, it would be cheaper for me to upgrade to the HEX-USB+CAN. Is there anything that the HEX-USB+CAN doesn't do that the Micro-CAN does do?
 
#11 ·
Re: VCDS MKVI / MK6 Platform, Handy Coding tweaks (spockcat)

No - the HEX-USB+CAN is our most complete coverage product and the product we recommend to repair shops to cover all VW/Audi models between '95 and 2010. The Micro-CAN is intended for enthusiasts working on the MKV, MKVI based vehicles. It does not work on all VW/Audi platforms.
For a better idea of what works with what model, consult our World Compatibility Chart http://www.ross-tech.net/VCDS/...s.pdf
 
#13 ·
Re: VCDS MKVI / MK6 Platform, Handy Coding tweaks (bigshaft)

Hi Edward! There is a VW Vortex member that has ordered LED Euro. Golf tail lights (with adapters and coding instructions) but he hasn't updated me on the install. The parts may not have arrived yet.
Did the TPMS activate on your Jetta by coding 09 - Cent. Electronics?
 
#14 ·
FV-QR

Dana,
I too have ordered LED tails. Several forums have indicated that the relevant coding in Central Electronics, Byte 18. However when I go to that byte there is a warning message not to alter the coding. Can you provide any further explanation as to the the issues with this byte? TM Tuning offers a device with the lights, which I believe is produced by Kufatec (though not certain), which preforms the required coding. However given the warning in VCDS I'm not so sure I want to allow this. Any information is appreciated...
I can provide a complete scan, just didn't want to clutter this thread...



Modified by chadcronin at 10:54 AM 2-22-2010
 
#15 ·
Re: VCDS MKVI / MK6 Platform, Handy Coding tweaks (Dana @ Ross-Tech)

Thanks for the info i have not implemented the tpms mod yet as it is winter here and my car is stored but be assured it will be done as will many other mods this Kick *** forum provides. This place rocks!
 
#16 ·
Re: VCDS MKVI / MK6 Platform, Handy Coding tweaks (Dana @ Ross-Tech)

This may come in handy a bit later when we get the LED thing sorted out - I found some interesting information over in the MKVI forum regarding adaptation of LED tails:
http://forums.vwvortex.com/zer...34981
Quote, originally posted by MrEastside78 »
You need vagcom to reprogram. I´m sure your lokal dealer can help you.
Set your new code in BYTE 18 to:
Byte 18 Bit 2
04 = 00000100
I´m not sure this will make you remove your errors, because cars whitout xenon and prductionsweek before week 45 2009 has a different software. This software can not be reprogrammed, need to change your hardware BCM.
Maybee you can find an answer in this thread: http://www.motor-talk.de/forum...e=179
read from site 180 and forwards. Need to understand german or use google translate.



Modified by sfpegasus at 2:17 PM 2-22-2010
 
#17 ·
FV-QR

^ Thanks. I saw that - it's what led me to Byte 18 and the warning in VCDS. Reading through the referenced thread (via a translator) it's not clear [to me] whether it is saying that there is an issue with all cars produced before week 45 or just those w/o Bi-Xenon... At the moment my main concern is lees with the required coding but more with the warnings associated with byte 18.
 
#18 ·
Re: FV-QR (chadcronin)

Well, like I posted in the MKVI forum, I think enough doubt exists to wait a month until VW settles the discussion. Then I'll be ALL OVER it.
 
#19 ·
Re: FV-QR (sfpegasus)

I completely agree. Chad and I emailed and my Byte 18 summary is:
Byte 18 is marked unsafe due to reports of control module failure and undesirable results on various makes and models. I do not have any reports from the US indicating that the installation and coding for a LED retrofit was successful.
 
#20 ·
Re: VCDS MKVI / MK6 Platform, Handy Coding tweaks (Dana @ Ross-Tech)

i figured the mkvi's were going to be similar
 
#21 ·
Re: FV-QR (Dana @ Ross-Tech)

Quote, originally posted by Dana @ Ross-Tech »
I completely agree. Chad and I emailed and my Byte 18 summary is:
Byte 18 is marked unsafe due to reports of control module failure and undesirable results on various makes and models. I do not have any reports from the US indicating that the installation and coding for a LED retrofit was successful.

I suspect this install falls into this unsafe category?
http://mk6.mk5golfgti.co.uk/fo...sg488
 
#22 ·
Re: FV-QR (sfpegasus)

I like how you guys programmed the soft coding so I dont have to refer to threads like this to change the hex/bit coding to the correct numbers hehehe
Its funny that the vcds has more capabilities than my 8000.00 snap on scanner lol http://****************.com/smile/emthup.gif
 
#23 ·
Re: FV-QR (Slimjimmn)

Quote, originally posted by sfpegasus »

I suspect this install falls into this unsafe category?
http://mk6.mk5golfgti.co.uk/fo...sg488

Someone sent me that link as well, I need to review it. I can say that Byte 18 coding value shown is NOT advised when you don't have LED tails and are experimenting.


Quote, originally posted by Slimjimmn »
I like how you guys programmed the soft coding so I dont have to refer to threads like this to change the hex/bit coding to the correct numbers hehehe
Its funny that the vcds has more capabilities than my 8000.00 snap on scanner lol http://****************.com/smile/emthup.gif

Thanks
 
#25 ·
Re: FV-QR (CanadianTurbo)

Subscribed for LED tails info
 
#26 ·
Re: VCDS MKVI / MK6 Platform, Handy Coding tweaks (Dana @ Ross-Tech)

Dana,
Is there a way to turn off the door chime when the key is in the ignition? I realize that it turns off after 30 seconds or so, but would like to disable it completely. I was able to do this on the Mk4 R32, but can't seem to find the coding in the Mk6.
Thanks!
Kyle
 
This is an older thread, you may not receive a response, and could be reviving an old thread. Please consider creating a new thread.
Top