2013 A6 Allroad 4G C7 - xenon retrofit

nugentp · May 16, 2019

So - here was an unexpected wrinkle with hooking up the old fog lights - the coding I currently have has the all-weather/corner lamp activation enabled when going round bends which causes the relay to go a bit buzzy and mad as the voltage ramps up & down analog style for a nice subtle transition on the lamp. I was driving in twilight when the buzzing started so it took me a couple of 'bad relay' swap outs before I figured it out.

So now I need to seek out the coding bit in the BCM to disable the corner function - I just want the fogs to be on when I push a button - I don't need a gazillion lines of software in the BCM doing this so called intelligent lighting function. An alternative solution might be to not use the relay for the 2nd lights but I was worried about pulling too much current out of the BCM. So I played safe and got buzzed, but better that than a frazzled BCM ;-)

Meantime the buzzy relay is on the bench so as not to raise my blood pressure any higher. I think its time for a beer to thin my blood.

nugentp · May 16, 2019

I found the bit - BCM (Address 09) - Byte 04 - CLEAR bit3. This byte was set to 88 and the turny wheel corner light is active.
I changed to 80 and the weather light is only active when front fog button is on. Result !

nugentp · May 17, 2019

So the new pins for the CAN gateway arrived and I tried the new gateway - sure enough CP kicked in, but I could make contact with the AHLS controller at address 55 and need to get CP removed on that as well as correct coding - its partially in german so I need to study it properly after CP is removed.

nugentp · May 19, 2019

Some pics taken along the way which may be helpful for others - focussed on the electrical aspects - not so much the joy of inner wing and bumper removal:

Running the cable from the inner wing through the bulkhead grommet at the driver side A-pillar

View from inside the inner wing:

With bare terminals protected by a wee zip-lock band and wrapped with tape to the pull cable, this is how I fed the headlamp motor wires from cabin side into the inner wing - all the bulkier plugs stay inside:

View of red and brown plugs in the BCM (J519) that need to be tinkered with for the bi-xenon conversion.

When you have the engine side loom broadly in place, you can see some convenient slots to carry the new cable - I reinforced the loom at those points for a bit of endurance.

The new loom sections run nicely along the front cross-member and pick existing cable for air temp sensor.

Finally a xenon lamp photo:

I also re-inforced the cable entry at the A-pillar before I buttoned everything done after some tests:

There is plenty long enough cable on the Kufatec loom in my experience - ties up recently well behind driver side headlamp.

Pic of the CAN gateway plug without the necessary EXTENDED bus for the AHLS controller:

Must say the OE wiring could look tidier, but I think those little scraps of tape just identify which bus is which - they aren't insulating any joints.

Rear view of black fuse carrier (ST1) at SB where I added the new switched 12V feed for the AHLS controller.

nugentp · May 19, 2019

Last handful of pics...

The fuse pin supplied on the loom is too big for the mini fuse pins so I chopped it and crimped on the right one.

I later revisited the white/black wire on the red plug after the conversion to get the trigger signal for the old-school relay circuit driving the original low level fogs.

I chose a suitable location on ST2 for the old fog light fuse:

Fuse blocks all wrapped up in fabric tape so about done in this corner:

I found somewhere suitable to attach the AHLS module - figuring the OE location is on passenger side but I ain't going there. I found a better location for that fog relay after this pic - clipped onto bottom of that relay carrier:

nugentp · Jun 24, 2019

The local dealer was able to remove component protection on my 'new' gateway with extended bus without problems. I have now added address 55 for AHLS to the installation list and getting comms with the AHLS module (J431). First step is to get this module coded correctly for an A6 Allroad Avant - the experimental coding helper is not quite nailing it for me despite trying a dozen or more combinations that seem to smell right. Until coding is correct, I am getting the following fault codes on J431. Car is UK, RHD. I have tried to find a similar vehicle in the forum library but nothing perfect yet. Any insight welcome.

Code:

Monday,24,June,2019,18:35:43:30756
VCDS Version Release 19.6.0 Running on Windows 7 x86(Parallels)
www.Ross-Tech.com

                Address 55: Headlight Range       Labels: 8X0-907-357.clb
Control Module Part Number: 4H0 907 357 A    HW: 4H0 907 357 A
  Component and/or Version: ....LWR12.... H02 0013
           Software Coding: 1122A6101000A300
            Work Shop Code: WSC 02391 785 00200
              ASAM Dataset: EV_HeadlRegulBasic 005001 (AU57)
                       ROD: EV_HeadlRegulBasic.rod
                      VCID: 2C14001C4773132F1B-8079
3 Faults Found:

126986 - Front Left Ride-Height Sensor 
          C1034 15 [137] - Open or Short to Plus
          MIL ON - Confirmed - Tested Since Memory Clear
             Freeze Frame:
                    Fault Status: 00000001
                    Fault Priority: 2
                    Fault Frequency: 1
                    Reset counter: 109
                    Mileage: 152729 km
                    Date: 2019.06.24
                    Time: 18:33:37

127242 - Rear Left Ride-Height Sensor 
          C1036 15 [137] - Open or Short to Plus
          MIL ON - Confirmed - Tested Since Memory Clear
             Freeze Frame:
                    Fault Status: 00000001
                    Fault Priority: 2
                    Fault Frequency: 1
                    Reset counter: 109
                    Mileage: 152729 km
                    Date: 2019.06.24
                    Time: 18:33:37

393989 - Headlight 
          C107E 54 [137] - Missing Calibration / Basic Setting
          MIL ON - Confirmed - Tested Since Memory Clear
             Freeze Frame:
                    Fault Status: 00000001
                    Fault Priority: 2
                    Fault Frequency: 1
                    Reset counter: 109
                    Mileage: 152729 km
                    Date: 2019.06.24
                    Time: 18:33:36

nugentp · Jun 24, 2019

Is there a login code needed before coding can be changed ?????

nugentp · Jun 24, 2019

Discovered there is a login code before J431 coding but I still cannot find the magic combination of coding bytes for a UK C7 AR. It lets me change a few things relating to ECE/RDW region but I am not getting correct combination of other coding bytes to get some sense of an allroad coding to work. This will have height sensors connected to air suspension controller and I assume it must only be CANbus connectivity of those values which get communicated to J431, but I still get these nag alarms about height sensors that is expecting to find for non airbag cars with AHLS.

Dana · Jun 25, 2019

Hi Paul,

Please let us know if 55 needed something other than SA code 20103 = Coding/Basic Settings Enabling so I can add that to the lbl file.

Next, I absolutely agree. 55 shouldn't be looking for a level control sensors directly because you have a 34 module. For this reason I ran a search of our emails containing Component "LUFE-DAEMPFER" -and- PN SW "4H0 907 357 A" and narrowed the results to 4G to exclude NAR A6/7 models and the 4H A8.

11116F101000A200
11116F101000A300
11116F101002A200
11215F101000A200
11215F601002A200
11226F101000A300
11226F101002A200
11226F101002A300
11226F601002A300
11236F101002A200
11236F101002A300
11236F601002A300
12236F601002A400

Some of those may be from broken or modified cars but that list may be helpful since the configurations were accepted/stored in scans.

I didn't drop every one into the LCH to see if all of the bits are documented in VCDS so any feedback related to the combo of options that (hopefully) resolve your problem would be appreciated if our LCH was missing info.

Also, the complete Auto-Scan in the current condition would be helpful so I can verify my coding additions to the final BCM (4H0-907-063-V1) file. (English MVB, BS and SOT were added recently but that coding chart isn't complete in the customer version yet.)

nugentp · Jun 25, 2019

Thanks Dana - that's super helpful - hopefully one of those has the magic combination.

Btw - the VCDS suggested SA code of 20103 worked fine.

Totally random thought - I am not near the car right now - do I need to change some coding on controller 34 for height control so it knows to send CAN packets (via the gateway) to controller 55 when fitted ?

Up to now controller 34 is blissfully unaware of existence of new module 55. Maybe I am overthinking it and 55 goes looking for 34 (again via the gateway) to discover what height the car is at ?????

Dana · Jun 25, 2019

That's a perfectly valid theory however my baseline scans have 34 coded to 008000, 008001, 008002 and 008003 so I don't believe that's the missing key. The 34 module LCH includes options such as:

Trailer Recognition Control Module installed [PR-1D4/1M6/KF0/KF1/KF4/KF5]
Adaptive Cruise Control (ACC) installed [PR-8T4]
Audi Drive Select (ADS) Steering installed [PR-QZ7]

Nothing headlight system specific as far as I can tell.

nugentp · Jun 26, 2019

OK - good to know. Here is another question - bear in mind this car was not equipped in factory with extended CAN bus and I have essentially directly connected the J431 module to the 'new' J533 module with twisted pair connection supplied in Kufatec loom - do the necessary CAN Bus termination resistors always reside in the CAN gateway ?

Dana · Jun 26, 2019

The resistors should reside inside the CAN Gateway to the best of my knowledge.

nugentp · Jun 28, 2019

So a happy update which just about closes this thread nicely - I took the first code suggested by Dana - 11116F101000A200 and it was accepted.

I noticed that called out an ECE LIMO so changed Bytes 00 & 01 to reflect RDW AVANT - 17226F101000A200

The main byte that was blocking my attempts to get a code that worked was Byte 3 = 6F which was something I didn't try - gave up after other combinations that failed to get accepted.

With the correct coding I was only left with a fault code for basic setting / calibration, so I ran through the sequence and fault codes all cleared. BRILLIANT - Thanks so much to Dana & others for helping me along the way on this - this thread should help others get the same result so much faster than I did !

The only remaining niggle is that the module is coded as AVANT instead of ALLROAD - doubt it matters much but I tried all combinations of chassis type with ALLROAD in Byte 1 and none were accepted.

Dana · Jun 28, 2019

Awesome! Do you mind posting a final Auto-Scan?

nugentp · Jun 28, 2019

I already posted that in another thread about a possibly related coding related issue on the gateway. Link below:

https://forums.ross-tech.com/showthread.php?18585-Audi-A6-4G-CAN-gateway-swap&p=168781&viewfull=1#post168781

My theory is that the new CAN gateway is from a non-allroad 4G/C7 vehicle and the same coding bytes as my original CAN gateway (without ext bus) make it behave differently... or worse I need a very specific allroad version of the CAN gateway with extbus hardware. I need to look into that as the coding helper for the new gateway is all in German.

2013 A6 Allroad 4G C7 - xenon retrofit

nugentp

Verified VCDS User

nugentp

Verified VCDS User

nugentp

Verified VCDS User

nugentp

Verified VCDS User

nugentp

Verified VCDS User

nugentp

Verified VCDS User

nugentp

Verified VCDS User

nugentp

Verified VCDS User

Dana

Administrator

nugentp

Verified VCDS User

Dana

Administrator

nugentp

Verified VCDS User

Dana

Administrator

nugentp

Verified VCDS User

Dana

Administrator

nugentp

Verified VCDS User