Audizine - An Automotive Enthusiast Community

Results 1 to 9 of 9
  1. #1
    Veteran Member Three Rings Eli0073's Avatar
    Join Date
    Jul 17 2020
    AZ Member #
    555366
    Location
    USA And Finland

    Help Wanted, Looking for someone with VCDS experience in San Antonio TX?

    Guest-only advertisement. Register or Log In now!
    I believe my rear door Modules somehow became corrupted while coding using OBDEleven. Even do I was not coding the doors. Looking for someone with VCDS experience in the San Antonio TX area that can help me out figured it out what the heck happen?

    Willing to Pay if necessary.

    Sent from my IN2017 using Audizine Forum mobile app
    Last edited by Eli0073; 11-30-2020 at 08:43 AM.

  2. #2
    Veteran Member Three Rings Eli0073's Avatar
    Join Date
    Jul 17 2020
    AZ Member #
    555366
    Location
    USA And Finland

    Anybody? Lol! #sad

    Sent from my IN2017 using Audizine Forum mobile app

  3. #3
    Senior Member Three Rings Clod's Avatar
    Join Date
    Dec 31 2010
    AZ Member #
    68874
    Location
    Boston

    I am surprised that this would get corrupted by changing something other than the module itself unless something shorted or you interagated the control module and unknowingly changed something. Did you do a scan of the rear modules?

  4. #4
    Veteran Member Three Rings Eli0073's Avatar
    Join Date
    Jul 17 2020
    AZ Member #
    555366
    Location
    USA And Finland

    I was unlocking via OBDEleven the Ambient lights Menu on the MMI to activate the foot well lights. I did all the activation reset the MMI menu appear.

    However my dimmer switch does not work anymore and my car is not getting any power to light the rear doors window switch. They windows go up and down but they don't have lights anymore...

    I redo all I did again via OBDEleven reset the MMI. Still not working..

    I remove the rear door panels check all the connections, the are good plugged properly to the Module. Still not red lights on rear window switch.
    I have no idea how to fix this. Because everything should work fine since I reverted back the coding I did. And I double checked the history logs of what I did. I never touch the rear doors during the coding.

    Scan the car..among other unknown codes I have this one
    Trouble codes:

    U020100 - Lost Communication With “Door Control Module C”

    static

    U020200 - Lost Communication With “Door Control Module D”

    I use this thread. I did all the coding except the one in the doors because I did them already months ago.

    https://www.audi-sport.net/xf/thread...lights.276625/


    Sent from my IN2017 using Audizine Forum mobile app

  5. #5
    Veteran Member Three Rings Eli0073's Avatar
    Join Date
    Jul 17 2020
    AZ Member #
    555366
    Location
    USA And Finland

    How do I do a scan of the rear door Modules?

    Sent from my IN2017 using Audizine Forum mobile app

  6. #6
    Senior Member Three Rings Clod's Avatar
    Join Date
    Dec 31 2010
    AZ Member #
    68874
    Location
    Boston

    Did you install lights? Why did you enable the menu?

  7. #7
    Veteran Member Three Rings Eli0073's Avatar
    Join Date
    Jul 17 2020
    AZ Member #
    555366
    Location
    USA And Finland

    Because I was doing the Foot well lights retrofit.

    Sent from my IN2017 using Audizine Forum mobile app

  8. #8
    Senior Member Three Rings Clod's Avatar
    Join Date
    Dec 31 2010
    AZ Member #
    68874
    Location
    Boston

    So the best thing to do, if you have not already done so, is to uninstall or disconnect all the lights you put in. Once you do this, return all the coding to how it was originally and reset the MMI. See if this works. If this does not work then when you installed the lights, I would assume that something shorted or loaded the circuit such that it damaged something.

  9. #9
    Veteran Member Three Rings Eli0073's Avatar
    Join Date
    Jul 17 2020
    AZ Member #
    555366
    Location
    USA And Finland

    I did that already...unwire the lights that are wired to the window switch and nothing. I also when back to the original rear door long codes and cycle the doors and even disconnect the battery of the car and still nothing.

    I'm getting this codes..

    19 Gateway

    System description: GW MQB High
    Software number: 5Q0907530AJ
    Software version: 2246
    Hardware number: 5Q0907530M
    Hardware version: 212
    Serial number: 21111510801872
    ODX name: EV_GatewConti
    ODX version: 013020
    Long coding: 0101000830085A005B00022C980B0000000101000000000000 0000000000

    Subsystems:
    System description: E221 - MFL
    Software version: 0014
    Hardware version: H02
    Serial number: 16 11 2015 D0042979

    Trouble codes:
    U020100 - Lost Communication With “Door Control Module C”
    static
    Date: 2020-11-27 22:52:13
    Mileage: 76802 km
    Priority: 2
    Malfunction frequency counter: 1
    Unlearning counter: 253
    Supply voltage, terminal 30: 14.1 V
    Terminal 15: On
    U020200 - Lost Communication With “Door Control Module D”
    static
    Date: 2020-11-27 22:52:13
    Mileage: 76802 km
    Priority: 2
    Malfunction frequency counter: 1
    Unlearning counter: 253
    Supply voltage, terminal 30: 14.1 V
    Terminal 15: On
    U112600 - Undefined control module No communication
    static
    Date: 2020-11-27 22:52:13
    Mileage: 76802 km
    Priority: 2
    Malfunction frequency counter: 1
    Unlearning counter: 253
    Supply voltage, terminal 30: 14.1 V
    Terminal 15: On
    U106A00 - Digital sound system control module No Communication
    static
    Date: 2020-11-27 22:52:13
    Mileage: 76802 km
    Priority: 2
    Malfunction frequency counter: 1
    Unlearning counter: 253
    Supply voltage, terminal 30: 14.1 V
    Terminal 15: On
    U112600 - Undefined control module No communication
    static
    Date: 2020-11-27 22:52:13
    Mileage: 76802 km
    Priority: 2
    Malfunction frequency counter: 1
    Unlearning counter: 253
    Supply voltage, terminal 30: 14.1 V
    Terminal 15: On
    U112400 - Data bus Additional installations detected
    static
    Date: 2020-11-27 22:52:13
    Mileage: 76802 km
    Priority: 2
    Malfunction frequency counter: 1
    Unlearning counter: 253
    Supply voltage, terminal 30: 14.1 V
    Terminal 15: On


    5F Multimedia

    System description: MU-S-S-US
    Software number: 8V0035844C
    Software version: 0660
    Hardware number: 8V0035844
    Hardware version: 014
    Serial number: A7A02411150378
    ODX name: EV_MUStd6C3PASE
    ODX version: 002020
    Long coding: 01730102FF0A000021220001001A00002F0002040180010006

    Subsystems:
    System description: ControlUnit_B
    Software version: 0054
    Hardware version: H41
    Serial number: C1000009101500010043

    System description: DU Std
    Software version: 0014
    Hardware version: H49
    Serial number: AUZ8Z9FY30F620

    Trouble codes:
    U101400 - Control module incorrectly coded
    static
    Date: 2020-11-27 17:37:39
    Mileage: 76801 km
    Priority: 4
    Malfunction frequency counter: 1
    Unlearning counter: 252
    Dynamic environmental data: 02868B1017555555555555A8
    B11CF53 - Tuner for satellite radio Deactivated
    static
    Date: 2020-11-27 17:37:40
    Mileage: 76801 km
    Priority: 4
    Malfunction frequency counter: 1
    Unlearning counter: 252
    Dynamic environmental data: 02868B2446FF000000FFFF00

    Sent from my IN2017 using Audizine Forum mobile app

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  


    © 2001-2025 Audizine, Audizine.com, and Driverzines.com
    Audizine is an independently owned and operated automotive enthusiast community and news website.
    Audi and the Audi logo(s) are copyright/trademark Audi AG. Audizine is not endorsed by or affiliated with Audi AG.