Control Module Incorrectly Coded U101400

new

dv52 (Australia)
Moderator

Posts: 6,064

Control Module Incorrectly Coded U101400 Oct 29, 2022 23:17:54 GMT mk7 likes this

Quote

Post by dv52 (Australia) on Oct 29, 2022 23:17:54 GMT

Oct 29, 2022 21:11:40 GMT mk7 said:

I did direct wire the rear sensor. Question being do I splice into the rear sensor wires or do I cut them so they are no longer connected to the DCC module?

mk7 : wow- bolded text!!

First, I need to make it clear that I have not personally done this exercise - so I'm relying heavily on the information that you provide.

The DCC module (it's called J250) normally has 3 x level sensors connected; front-left, front-right and rear. We are dealing with the rear sensor (called G76) and the wire colors Blue, Black, Brown.

Notwithstanding my caveat above, I assume that a pivotal part of a project to remove DCC is to disconnect the power supply from the DCC module and more importantly from a CAN network perspective - to tell the Gateway module to no longer communicate with said module. This latter part is done by removing the hex14 module from the Gateway Installation list.

If these steps are completed, the DCC module is dead!! I would deduce therefore that there ain't no point leaving the G76 wires connected to the hex14 module!! So yes, "cut them so they are no longer connected to the DCC module". After the modification, the wiring arrangement should be like this:

Oct 29, 2022 21:11:40 GMT mk7 said:

I have updated the code, scanned, cleared and have the same errors

OK - I suspect the first task is to get the wiring correct for the hex55 module (J745 in my diagram) as above. Next, the left/right power output stages need to be coded. This is normally an automated process that is done by the hex 55 module - but only when J745 is happy that both it and the peripherals are correctly working.

After you are confident that the wiring is completed correctly - try running my basic setting procedures. If the left/right power output modules still remain not coded, you might need to re-apply the long-code string on J745

Don

Last Edit: Oct 29, 2022 23:25:26 GMT by dv52 (Australia)

Please don't ask questions about car coding/repair via the forum "Message" function. The better place for such dialogue is in the forum proper. That way, the wider expertise of the entire forum community can be applied to solve your problem - thank you

mk7
New Member

Posts: 14

Control Module Incorrectly Coded U101400 Oct 29, 2022 23:39:31 GMT

Quote

Post by mk7 on Oct 29, 2022 23:39:31 GMT

Perfect, so I have hardwired (7, 10, 11) and disconnected the wiring to DCC as you noted. Also, I did not mean anything with the bold lol

I cannot run the basic setup features, nothing happens in basic settings in the 55 Module.

I will look into the long code string for J745.

TY!!

Last Edit: Oct 31, 2022 3:20:04 GMT by mk7

MK7 Golf R

mk7 New Member Posts: 14	Control Module Incorrectly Coded U101400 Oct 30, 2022 18:24:25 GMT Quote Select Post Deselect Post Link to Post Back to Top Post by mk7 on Oct 30, 2022 18:24:25 GMT Just an update, going through all modules history and reversing my edits to "stock" to see if I tripped something inadvertently. Fingers crossed
	MK7 Golf R

mk7
New Member

Posts: 14

Control Module Incorrectly Coded U101400 Oct 31, 2022 2:32:12 GMT

Quote

Post by mk7 on Oct 31, 2022 2:32:12 GMT

I reverted everything back in each Control Module, checked all wiring, pulled and re-pinned T26 confirming that it matches the headlight configuration of J745 (as noted in the picture above), re codded and I am still getting these two errors in 55. Everything else seems to be running like it should.

C107E54 - Headlight No basic setting - static
U10BA00 - Local data bus No communication - static

Based off various searches I found that the "U10BA00" code seems to be universal for any module that is having an issue and is not headlight specific.

Then I thought, maybe a bad leveling sensor... then found that the bad leveling sensor is a code "C103615 Left Rear Level Control System Sensor" with some more awesome info from you Don!! But it is on an Audi: www.golfmk7.com/forums/index.php?threads/error-code-c103615-left-rear-level-control-system-sensor-open-shorted-to-b.386893/

Then I read down a few threads on the MK7 post and saw someone say that their ground was pin 10 and power was pin 11...
www.vwvortex.com/threads/dcc-delete-on-nar-2015-golf-r.9493140/post-115559112
So I swapped them quick and sure enough I am getting the "C103615 Left Rear Level Control System Sensor" error now... So maybe the wiring was different on mine.

___________________________________________________________________________________________________________________________________________

So do I have a bad sensor you think? I am not great with a multimeter; but could figure it out with some direction if there is a way to test the sensor.

___________________________________________________________________________________________________________________________________________

And finally.... I was able to run the basic settings and acknowledge them once... but that didn't fix the problem and I was not able to go back in and do it again.

"Basic settings

Control unit: 55 Headlight Regulation

Name: Acknowledge basic setting

Status:

Mileage: 45300 km

Date: 2022-10-30 22:25

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

Basic settings

Control unit: 55 Headlight Regulation

Name: Basic headlamp setting

Status:

Mileage: 45300 km

Date: 2022-10-30 22:25"

Last Edit: Oct 31, 2022 5:25:23 GMT by mk7

MK7 Golf R

dv52 (Australia)
Moderator

Posts: 6,064

Control Module Incorrectly Coded U101400 Oct 31, 2022 21:29:39 GMT mk7 likes this

Quote

Post by dv52 (Australia) on Oct 31, 2022 21:29:39 GMT

Wow- I never cease to be amazed at the vast range of thinking processes that folk use to diagnose faults! It's always a stark reminder (to me) of the ingenuity of carbon-based-life-units

Nevertheless, I'm not entirely sure that swapping the power supply pins on the rear level sensor was good for its karma, or for its well being.

As to your question "do you have a bad sensor?" - sitting here at the remote end of this fragile blue planet and reading your words - I don't know!! You will need to test the device to answer your own question.

So- there are lots of sensors on today's modern cars and without wishing to underplay the diversity in technologies that are used - transducers that decode position (like the level sensor) can be separated into 2 x broad types; induction type and Hall effect type. Generally, these sensor types can be distinguish by the number of wires on their connectors - like this:

2 x wires = Induction type sensor
3 x wires = Hall effect sensor (sometimes these have 4 x wires)

Because G76 has 3 x wires, it's clearly a Hall effect transducer. These sensors have 2 x power pins and an "output" pin. Sometimes the power pins are connected to the car's battery volts - but on a mk7, the power-supply for this particular Hall effect sensor is (one of) the 5V rails.

To determine the polarity of the 5V pins on your J794 module - do this:

Turn on the car's ignition
Grab a multi-meter and make sure that the back/red leads are correctly plugged into the black/red sockets on the meter
Select DC Volts on the meter and select a full scale option that's greater than 5V (normally this is 20V on a digital multi-meter)
Connect the red multi-meter lead to pin #10 and the black multi-meter lead to pin #11 on the 26 x pin connector on J794
With the multi-meter leads connected as per step IV above- if the reading on the meter is positive 5 Volts:
- Pin #10 = +5V
- Pin #11 = earth (for the 5V rail)
if the reading on the meter is negative 5 V
- Pin #10 = earth (for the 5V rail)
- Pin #11 = +5V

To test if the G76 still works, you really need an oscilloscope (which I assume that you don't own) - but you can try using the multi-meter like this:

Connect G76 as per the results of your test above (i.e. if pin #10 = +5V, use my wiring diagram) and set-up the multi-meter as per the initial steps in the procedure above
On J794 26 x pin connector - connect the red multi-meter lead to pin #7 and connect the black multi-meter lead to whichever pin you determined was earth from the previous test above. The reading on the meter should be around positive 5V
Slowly move the arm of the level sensor - you should see a change in the DC voltage. I'm not able to say whether the reading will be a change in the steady-state DC voltage, or whether the reading will be a flicker in DC volts (it depends on the meter) - but you should see a change

Don

Last Edit: Oct 31, 2022 21:35:33 GMT by dv52 (Australia)

mk7
New Member

Posts: 14

Control Module Incorrectly Coded U101400 Nov 1, 2022 15:51:41 GMT

Quote

Post by mk7 on Nov 1, 2022 15:51:41 GMT

Thanks Don! It appears there is some wiring confusion in that thread I originally posted from VWvortex on this wiring situation. Here is the OP's info:

"1 - signal (-) (blue)
2 - blank
3 - power (5v) (black)
4 - ground (brown)
* J431/T26a (AFS Module) (note: wiring diagrams have 7 and 11 reversed, but did not work on my car)

7 - signal (-)
10 - power (5v)
11 - ground
* Mapping

blue - g76 T4ao/1 to J431 T26a/7
brown - g76 T4ao/3 to J431 T26a/10
black - g76 T4ao/4 to J431 T26a/11"
_________________________________________________________________________________________________________________________
And then the "other" post further down the thread I was referring to:
"Although the pinout for my afs ended up being ground on pin 10 and power on 11. Was unsure if which was the one you went with and which was the one you found online."
_________________________________________________________________________________________________________________________

I should have some time tonight to go through your steps, appreciate your time and help!!

Last Edit: Nov 1, 2022 19:27:42 GMT by mk7

MK7 Golf R

mk7
New Member

Posts: 14

Control Module Incorrectly Coded U101400 Nov 1, 2022 18:39:29 GMT

Quote

Post by mk7 on Nov 1, 2022 18:39:29 GMT

Welp, I am a dummy. When I installed the rear LCA's, I forgot to swap the sensor mount from the OEM arms to the new ones. So the rear sensor was not connected at all.

I was able to drill/tap and swap the mount on the new arms, so the rear leveling sensor is now connected appropriately.

Pulled it in/out of the garage to move the sensor a bit and re-scanned. I was getting the same "C103615 Left Rear Level Control System Sensor" error. So I swapped the wires back to the original orientation (Black 10/Brown 11) and go through the scan process only to find the same codes I was having pre-wire swap "C107E54 - Headlight No basic setting" and "U10BA00 - Local data bus No communication" both being static.

Next up, running the multi-meter tests you provided. Thanks a bunch!!

________________________________________________________________________________________________________________________
Update... Tested the polarity on the J794 and it is confirmed that:

Pin 10 is +5V
Pin 11 is Earth

So when I have them hooked up correctly, per your original diagram, I am left with the "C107E54 - Headlight No basic setting" and "U10BA00 - Local data bus No communication" both being static. I did not test the sensor due to it not throwing the "C107E54" code.

Thinking it must be my coding

next steps?

Last Edit: Nov 1, 2022 19:26:54 GMT by mk7

MK7 Golf R

dv52 (Australia)
Moderator

Posts: 6,064

Control Module Incorrectly Coded U101400 Nov 1, 2022 21:28:59 GMT

Quote

Post by dv52 (Australia) on Nov 1, 2022 21:28:59 GMT

OK - so, tiny steps forward in a very slow process!!

hmm.... here's the thing about providing diagnostic advice on a forum like this- it's highly dependent (or more precisely, "it's totally dependent") on the advisor's understanding about a car that in this case, sits in a garage in a town/city at the other end of the earth!! This means that specificity is key - or said in a less tactful way, the information provided (by you) MUST be accurate and it MUST be complete!

So, because you haven't mentioned it - I assume that the C1081F0/C1082F0 - headlamp power output stage not coded errors have now cleared.

The absence of these error is a good step forward because it means that J794 is now happy with your wiring changes and with the resulting CAN environment - and it's successfully auto- programmed the long-code string in each of the slave AFS modules. Well done!!

Thus far, you haven't provided details about these AFS units - please do so (I need to see the equipment information including the long-code value that has been auto-applied to these modules)

Don

mk7
New Member

Posts: 14

Control Module Incorrectly Coded U101400 Nov 1, 2022 22:50:32 GMT

Quote

Post by mk7 on Nov 1, 2022 22:50:32 GMT

That is correct, it removed the C1081F0 error and now only has the original two:

C107E54 - Headlight No basic setting

U10BA00 - Local data bus No communication

Can you show me where/how in OBDEleven to get you the info on the AFS units that you are requesting? TY!

Last Edit: Nov 1, 2022 22:50:58 GMT by mk7

MK7 Golf R

dv52 (Australia)
Moderator

Posts: 6,064

Control Module Incorrectly Coded U101400 Nov 2, 2022 2:59:14 GMT mk7 likes this

Quote

Post by dv52 (Australia) on Nov 2, 2022 2:59:14 GMT

First, allow me to explain stuff - so you know why you are doing it:

This is the CAN arrangement for J745 and the 2x power output modules (called "J667" and "J668") on a mk7:

J533 is what OBD11 calls "Gateway module" and it's included in my picture for completeness. The role of J533 is like the Fat Controller (of Thomas-the-tank-engine fame) - it coordinates ALL communications traffic.

As you can see from my diagram, the thing we have been referring to as AFS is in fact a mini-CAN system - which together with J745 forms the Extended CAN bus - in official VW language. These small-peripheral comms arrangements are common on modern cars - J745 is known as the "master module" and J667 & J668 are called "slave modules" in VCDS, or "Subsystems" in OBD11 speak.

With this understanding as context, here is a part-scan showing how OBD11 reports the modules on a healthy Extended CAN bus:

55 Headlight Regulation


System description: AFS-ECU

Software number: 7P6907357A

Software version: 0080

Hardware number: 7P6907357A

Hardware version: H07

Serial number: --------------

ODX name: EV_HeadlRegulVWAFSMQB

ODX version: 001120

Long coding: 029A00000B010200


Subsystems:

System description: LeiMo links

Software version: 0012

Hardware version: H05

Long coding: 2E0000


System description: LeiMo rechts

Software version: 0012

Hardware version: H05

Long coding: 2E0000


Trouble codes:

No trouble codes found

Notice the term "Subsystems" in the scan extract - it is used by OBD11 to separate the power output modules from the master module.

So to gain access to Subsystems with OBD11, scroll-down the list of option in the Control Unit screen for the hex55 module -see below (the pic is of a different module, but this doesn't matter -it's the same for the hex55 module). Then select the output power modules in turn, then select "Info" - see below. Also select "Coding" option and confirm that the long-code string for both Output Power modules is the same (as each other - they may be different to the values in my part-scan)

Don

Last Edit: Nov 2, 2022 3:13:14 GMT by dv52 (Australia)

mk7
New Member

Posts: 14

Control Module Incorrectly Coded U101400 Nov 2, 2022 19:53:30 GMT nzjzzjsjjs likes this

Quote

Post by mk7 on Nov 2, 2022 19:53:30 GMT

Thank you for the detailed description, I appreciate knowing how things "work" as much as I can.

Sooooo here's the thing, I do not have those Subsystems or any others under "55 Headlight Regulation" module.

Here are the error codes upon initial SCAN. Now I am seeing "intermittent" errors including the headlight control module which I would imagine have something to do with my issue.

17 Dashboard

System description: KOMBI
Software number: 5G1920858B
Software version: 8311
Hardware number: 5G1920858B
Hardware version: 304
ODX name: EV_DashBoardVDDMQBAB
ODX version: 009051
Long coding: 0B2D081A6E88CF0502886B0B5400000000000000

Trouble codes:

U112100 - Databus missing message
Intermittent
Date: 2022-11-01 20:21:09
Mileage: 45300 km
Priority: 6
Malfunction frequency counter: 1
Unlearning counter: 199

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

19 Gateway

System description: GW MQB High
Software number: 5Q0907530AM
Software version: 1265
Hardware number: 5Q0907530F
Hardware version: 128
Serial number: 0005246391
ODX name: EV_GatewLear
ODX version: 013020
Long coding: 0101000838085900FB00023A1C0F00000001050000000000000000000000

Subsystems:

System description: E221__MFL-DC1
Software version: 0040
Hardware version: H11
Serial number: 29160000995740066222
Long coding: 35FFFF

Trouble codes:

U101E00 - Headlamp range control module No communication
Intermittent
Date: 2022-11-01 20:21:11
Mileage: 45300 km
Priority: 2
Malfunction frequency counter: 1
Unlearning counter: 199
Supply voltage, terminal 30: 12.1 V
Terminal 15: On

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

55 Headlight Regulation

System description: AFS-ECU
Software number: 7P6907357D
Software version: 0090
Hardware number: 7P6907357A
Hardware version: H07
Serial number: --------------
ODX name: EV_HeadlRegulVWAFSMQB
ODX version: 001120
Long coding: 022A000103000400

Trouble codes:

C107E54 - Headlight No basic setting
static
Date: 2022-11-01 20:28:54
Mileage: 45300 km
Priority: 1
Malfunction frequency counter: 1
Unlearning counter: 159

U10BA00 - Local data bus No communication
static
Date: 2022-11-01 20:28:53
Mileage: 45300 km
Priority: 2
Malfunction frequency counter: 1
Unlearning counter: 159

_______________________________________________________________________________________________
Once I hold the button and clear the codes only the two remain under the 55 Headlight module:

C107E54 - Headlight No basic setting - static

U10BA00 - Local data bus No communication - static
_______________________________________________________________________________________________

Can you provide the OEM MK7 2017 GOLF R 55 Long Coding? I am not able to find it

Last Edit: Nov 2, 2022 20:17:02 GMT by mk7

MK7 Golf R

dv52 (Australia)
Moderator

Posts: 6,064

Control Module Incorrectly Coded U101400 Nov 2, 2022 21:42:07 GMT mk7 likes this

Quote

Post by dv52 (Australia) on Nov 2, 2022 21:42:07 GMT

Think about your question a bit more!!

Yes, I can find "OEM MK7 2017 GOLF R 55 Long Coding" (NAR models, of course) on the web- but it won't help in this instance because not surprisingly, ALL OEM scans have J250 installed (because this is the OEM factory arrangement)

For example - look HERE (doesn't matter that this is a VCDS scan - it's actually better than the OBD11 scan report, IMO).

Not sure that I can provide more help (can you drive to my workshop - it's easy, just head South and keep driving. If you reach Tasmania, you have gone too far!!

)!!

So, I don't believe that this is a problem with the actual power output modules because the same fault appears on both sides of the car! This fact strongly suggests that the error here is an element that's common to both outpt modulrs.

The fact that there is an intermittent error normally points to a wiring/connector problem with the CAN wires, or with the power-supply pins to J745. Just to confirm that this isn't a physical problem, carefully examine the state of these pins/wires on the 26 x pin connector (it's probably been plugged/unplugged many times). I assume that the non-HID functions on J745 (like DRLs) are operating correctly on this car

Don

Last Edit: Nov 2, 2022 21:57:15 GMT by dv52 (Australia)

grbac
Junior Member

Posts: 51

Control Module Incorrectly Coded U101400 Nov 6, 2022 0:37:03 GMT via mobile dv52 (Australia) likes this

Quote

Post by grbac on Nov 6, 2022 0:37:03 GMT

Hi Don,

finally found what caused the Lighting fault.
Leuchte4TFL LB4 Lasttyp 4 was set to 6 - LED Lichtmodul, after setting it to 1 - LED Tagfahrlichtmodul Versorgung ( Leuchte5 TFL RB32 was already set to this one) the fault became colored green and it cleared right away. All the lights now work as they should without a problem, even though the rear light adaptations are wierd, but they work.
Still can't thank you enough for all the help.

Grbac

Last Edit: Nov 6, 2022 0:41:02 GMT by grbac

Shoutbox

Please don't use the shoutbox for complex questions! For those questions please create a thread in the right subforum.

georgegianna: Recover Your Lost Coins with Paradox Recovery Wizard

I just wanted to express my heartfelt gratitude for your incredible help in recovering my lost funds. Your expertise and dedication have truly made a difference, and I’m so thankful for the support you’ Nov 15, 2024 19:31:32 GMT

derpandabear: Hi everyone, it's been two weeks since I've posted my question. I would greatly appreciate it if anyone can respond to my thread: forum.obdeleven.com/thread/28144/summertime-setting-mk8-golf-gti. Thanks and Best Regards! Nov 16, 2024 19:49:09 GMT

bmwg30lci: sveiki,noreciau gauti daugiau informacijos apie jusu produkcijos paskirti.ar imanoma pakeisti salone migtuku spalvas?pvz; pas bmw g30 lci tamsoje sviecia oranzine spalva o diena balta.as noreciau,kad visuomet butu tik baltas mygtuku pasvietimas. Nov 18, 2024 8:02:36 GMT

whataboutthis: @bmwg201ci jums reikia patikrinti vieno paspaudimo programas, skirtas jūsų varikliui, jei to, ko norite, ten nėra, pateikite užklausą BMW oca temoje. Nov 18, 2024 9:13:28 GMT

dado: GOLF 6 MATCH - include scandinavian DRL lights? does anyone know Nov 18, 2024 10:02:35 GMT

med44: brkica SIL VOUS PLAIT J'AI INSTALER UNE CAMERA SUR UNE GOLF 8 ;ET Jai besoin du fichier 5WA980556B. Nov 19, 2024 0:35:46 GMT

lazar: How do i change app country? bmw features not available Nov 19, 2024 19:18:39 GMT

Deleted: BIuS Nov 20, 2024 1:55:57 GMT

kp55: Hi, Nov 20, 2024 15:29:05 GMT

kp55: I have VW High Beam Assist installed, however in the module under Long Coding some settings are obvious but some are not. Mine was set to left hand drive which I've changed but can anyone who drives a right hand drive please help with settings? Nov 20, 2024 15:36:06 GMT

le4dsoldier: hı Nov 20, 2024 18:39:26 GMT

le4dsoldier: ı need some help, if ı'll buy a normal obdeleven. may ı use longcoding and can ı remove sfd lock Nov 20, 2024 18:40:54 GMT

fliew: Hi All, can anyone help me to reset my 2014 Audi S3 A/C to factory setting with OBD11, thanks. Nov 21, 2024 0:38:03 GMT

t5golf: Hello, I saw in the past a tread about programming/ coding Golf VIII( and other VAG types), for example speed regulation. I saved the list/ tread it on PC but do not find it anymore. Can somone share it? Thx . Nov 21, 2024 7:09:30 GMT

bumble: Does "Confirmation of installation change" in 5F need a Pro or Ultimate license? Nov 21, 2024 10:09:51 GMT

whataboutthis: le4dsoldier if you have a pre 2024 VAG motor that is supported and you have the Pro or Ultimate license you can code Adaptions and long Coding but after 2024 SFD2 STOPS YOU. SFD Can be unlocked but basic plan only allows you to use OCA Nov 21, 2024 16:52:53 GMT

whataboutthis: fliew you need to share more info, car year have you coded in obd11 or vcds etc there is no magic button to revert to factory setting you have to undo all your changes manually in Adaptions and Long Coding you can copy/paste if you have backup Nov 21, 2024 16:54:18 GMT

yncers: кто ставил дорожные знаки на туарег CR7 Nov 23, 2024 18:26:18 GMT

zuhair3434: Hello, i have golf 1.5ETSI imported used from Denmark to israel, i would like to update navegation, does any one know that? Nov 25, 2024 8:39:23 GMT