VW e-Golf MK 7 - 2015/16 - Coding issues

   #21  

trangakil

Verified VCDS-User
Verified
Joined
Jul 27, 2018
Messages
24
Reaction score
5
Location
Netherlands
VCDS Serial number
C?ID=329157
By the way, regarding the "thieving method" is it possible to get (steal) the turn signal from the headlights? Headlights are full led...
 
   #22  

Uwe

Benevolent Dictator
Staff member
Joined
Jan 29, 2014
Messages
29,955
Reaction score
21,394
Location
USA
VCDS Serial number
HC100001
Hi Uwe,

I'll try to make a screenshot tomorrow.
The exact message (my closest guess) was when trying to run an auto-scan:

" Communication error 0" and a line to go into the options and test menu.
Go to [Options]
Click [Config]
Click on the Update tab.
Click the [Check for Updates] button.


-Uwe-
 
   #23  

DV52

Verified VCDS User
Verified
Joined
May 16, 2014
Messages
3,609
Reaction score
4,018
Location
Melbourne, Australia
VCDS Serial number
C?ID=194404
Hi Guys,

After programming the whole day I got a little bit further!
What I did:
- Programmed the turn signal as indicated, unfortunately there was no difference;
hmm...... this outcome is entirely unremarkable - given that simply enabling the 2 x turn-signal Leutche-sets when there is no wire connected to the pins on the BCM will not achieve much

So in the end the braking lights, the fog lights and the normal lights are now in accordance with regulation. The signal lights also, but still if I'm hitting the brake, the also are lighting up...
Hope someone can help me out with this last part.
Again - hmm.................I've re-looked at your original admap settings and there are only 2 x instances of the Leuchte-command "Brake light" as follows:

ENG116960-ENG116335-Leuchte24SL HRA65-Lichtfunktion C 24 > Brake light
ENG116958-ENG116293-Leuchte22BR MA57-Lichtfunktion A 22 > Brake light

On RoW vehicles, the Leuchte24SL HRA65 leuchte-set is normally allocated to Parking light, rear right inside (rear lights) and the Leuchte22BR MA57 Leuchte is normally allocated to the Brake light, rear center (third brake light)

The traditional Leuchte-sets for the 2 x outer brakes lights are:

Leuchte20BR LA71 - Brake light, rear left (rear lights)
Leuchte21BR RC8 - Brake light, rear right (rear lights)

But neither of these 2 x Luechte-sets currently have a Brake light function according to your original admap

So - I'm totally bamboozled. My only guess is that the Brake lights and the turn-signals are wired in parallel -but this is only the case if the Brake light performs EXACTLY the same as the turn-signal -does it?

Don
 
   #24  

trangakil

Verified VCDS-User
Verified
Joined
Jul 27, 2018
Messages
24
Reaction score
5
Location
Netherlands
VCDS Serial number
C?ID=329157
but this is only the case if the Brake light performs EXACTLY the same as the turn-signal -does it?

Don
Hi Don,

Yes it does, the turn signals exactly performs the same as the brake. Just one difference, when not using the brake, and using the turnsignals they work fine...
 
   #25  

trangakil

Verified VCDS-User
Verified
Joined
Jul 27, 2018
Messages
24
Reaction score
5
Location
Netherlands
VCDS Serial number
C?ID=329157
Go to [Options]
Click [Config]
Click on the Update tab.
Click the [Check for Updates] button.


-Uwe-
This was probably a real newbie question....
Just updated it, will try later today!
 
   #26  

DV52

Verified VCDS User
Verified
Joined
May 16, 2014
Messages
3,609
Reaction score
4,018
Location
Melbourne, Australia
VCDS Serial number
C?ID=194404
By the way, regarding the "thieving method" is it possible to get (steal) the turn signal from the headlights? Headlights are full led...
Good lateral thinking - theoretically yes. I guess that it's a matter of the eventual electrical load on the internal components in the control module. The BCM is a very sophisticated beast and I believe (guess really) that it can self limit the electrical current on any of the lighting pins.

I note from your admap that the 2 x Leuchte-sets for the front turn signal have a Lastyyp setting of 33- LED-Modul Blinkleuchten. I don't know the maximum wattage that this setting will allow for the total load of the front LED plus the rear incandescent turn signal (which I assume is 21 Watts), but it's something to bear in mind (I suggest). Of course you can always turn-off the lamp monitoring function on the Leuchte-set if DTC s result.

The other good thing about your good idea is that the turn-signal function inherently requires a lower wattage load from the car's voltage rail by virtue of its "duty cycle". By this I mean, the turn-signal lamp only sees current flow for 50% of the time that it operates: because it cycles ON/OFF. This has the consequential effect of requiring only 25% of the wattage needed to illuminate a lamp for 100% of the time. This happens because of the famous I^2R formula. So - perhaps my fears above can be discounted (a little)

Before you make a decision about this approach, why don't you "patch-up" a temporary arrangement with a 21 Watt lamp which is connected in parallel to one of the front turn-signal lamps. Fire-up the turn-signal and see what happens - hopefully you won't have created a white-smoke generator (only kidding - you will have the protection of the lamp monitoring function in the BCM)

Don
 
Last edited:
   #27  

trangakil

Verified VCDS-User
Verified
Joined
Jul 27, 2018
Messages
24
Reaction score
5
Location
Netherlands
VCDS Serial number
C?ID=329157
Hi Don, as I can understand it is worth a try! I will work on the car later today, so this will be the first thing to do...

Perhaps a dumb question, but on which pins of the BCM are the Front turn signals?
 
   #28  

DV52

Verified VCDS User
Verified
Joined
May 16, 2014
Messages
3,609
Reaction score
4,018
Location
Melbourne, Australia
VCDS Serial number
C?ID=194404
Perhaps a dumb question, but on which pins of the BCM are the Front turn signals?
Left side Leuchte-set = Leuchte 0 BLK VL B36 - So BCM pin #36 on the B socket
Right side Leuchte-set = Leuchte1BLK VRB20 - So BCM pin #20 on the B socket

The pin # will be embossed on the BCM housing (not all, but sufficient to be able to count the missing pin numbers)
The socket Alphas are also embossed on the BCM Housing - like this:


Don
 
   #29  

trangakil

Verified VCDS-User
Verified
Joined
Jul 27, 2018
Messages
24
Reaction score
5
Location
Netherlands
VCDS Serial number
C?ID=329157
Hi All,

So after a couple of days I have an update again!

I have used the theving method from the front turn signals and wired it to the back (from the BCM). It works perfectly fine without any fault codes of errors (also in VCDS).

Have to say, I can recommend the Beta version on Electric vehicles, in this case the e-Golf, it shows a lot more coding options compared to the regular release.

Would like to thank everyone who have read the topic and everyone who has helped me solving this issue.

Up to the next issue!
 
   #30  

trangakil

Verified VCDS-User
Verified
Joined
Jul 27, 2018
Messages
24
Reaction score
5
Location
Netherlands
VCDS Serial number
C?ID=329157
To go into the second problem (the next elephant) being the charging socket, I'll first explain the why, what I did and the issue:

Why
Actually I thought the e-Golf (old version) had a range of like 200km with each full charge. However the real range is about 100 - 110km (during normal weather 22 degrees celcius), driving in the ECO+ mode like a granny will help to go up to 150km.
So in my opinion the range really sucks, I already knew the range was bad, but it really disappointed me...
However the DC fast charging mode will defenitely help to get over this bump.
So my US e-Golf has the DC fast charging port but it is combined with the US plug (J1772). In order to keep it's original state and not wanting to use adaptors, I attempted to change the port to the Mennekes Type 2 port.

What I did
After doing some research I decided to order the EU wiring harness (OEM codes: 5QE915925E 5GE971531N).
When the e-Golf came into the EU the first thing I tried was swapping the harness, after dismanteling the car and first checking all wires I came to the conclusion literally every wire is the same except for the Locking Mechanism of the plug and the relais combined with it.
But I was ofcourse thinking easy and swapped the harness... After swapping, the dash lighted up like a christmas three and giving errors in the electrical system. Also the locking mechanism of the chargeport was constantly moving the locking pin in and out (while not doing anything). So I got a bit frightened and changed in back to the original harness, everything went back to normal after clearing the DTC's.
However I was not yet ready to give up... After hooking it up to VCDS and seeing the option in Module 8C to change the region from NAR to EU, I coded this. The car indicated now that the chargeplug was in the car, so not able to start, please note this was with the old wiring harness.
After switching it to the EU harness with keeping the coding on EU standard, the car wasn't giving fault codes and the locking mechanism did not trip anymore. However the car still indicated the chargeplug is in the car, so again not able to start.

Issues
It kind of seems I got a little bit further when going into the adaption channels of VCDS in the 8C module. It seems the data of connections etc. are there for the J1772 plug, but aren't there for the Mennekes plug. Even when trying to adjust something (to check if something happens) I ran into the problem that it needs the numeric password.
I already tried a whole list (have to wait like 30 minutes after 3 attemps) I did not get the right code to adjust something in the 8C module. In another topic I noticed another member asked this and Uwe did not figured that one out yet.

Remains a couple of options:
1. Get the correct security code and try to figure out what to adjust in the adaption channels;
2. Get the data from an EU e-Golf and do step 1 but leave the figuring part behind;
3. Get the data from an EU e-Golf and flash the 8C module with ODIS.

The last option was indicated by a company I approached, however they don't have the data yet. I think it is worth a try..
However I already called and went with the car to the 4 "VCDS" specialists (companies) and they all indicated that they don't know (same goes for the trouble with the lights...).

Let's see if we can eat this elephant :)

So after fixing the light problem, the next is already waiting. As described above I have tried some things, just one error I made in my description above. The adjustments can be made in the "BD-Hi Volt. Batt. Charg" module and not the 8c module as mentioned above.
When I finished the lights yesterday, I started to swap (again) the wiring harness, so the same issues applied at first. However as recommended by Uwe earlier I have installed the Beta version of VCDS and started coding.
The results are below:

Original coding 1
[/url]

Original coding settings


Changes (after these changes 2 faults)


The following 2 fault codes resulted after this:
Code:
1059842 - Charging Socket B 
          P33E2 00 [009] - Electrical Malfunction
          Confirmed - Tested Since Memory Clear
             Freeze Frame:
                    Fault Status: 00000001
                    Fault Priority: 2
                    Fault Frequency: 5
                    Reset counter: 47
                    Mileage: 35950 km
                    Date: 2018.08.03
                    Time: 14:00:23

1059074 - Charging Socket B; Plug Locking Detection 
          P31D6 00 [009] - Electrical Malfunction
          [Socket_B_Lock_Check_short_circuit_high]
          Confirmed - Tested Since Memory Clear
             Freeze Frame:
                    Fault Status: 00000001
                    Fault Priority: 2
                    Fault Frequency: 5
                    Reset counter: 47
                    Mileage: 35950 km
                    Date: 2018.08.03
                    Time: 14:00:23

So after trying some more coding options I changed the following and just one fault code remained:

Changes part 2:




1 Fault code remains:


With this remaning fault code the car thinks the cable is plugged in (while it is not) and therefore it won't start.

So in my opinion, based on the information I have at the moment, the following options have came up (from my side):
1. I'm missing something in the Codingtable (I have to select another option);
2. I have to adapt some things through the adaption channels (however I don't now what the settings should be and in addidion there is a accescode required which I don't have);
3. The VCDS beta version, has some bugs and therefore not working properly when coding this module (experimental coding);
4. The relais of the locking mechanism is broken, that is also what the fault code is indicating. However should not be the case, but anything is possible!

Does someone have any other ideas / solutions?

Thanks in advance!
 
Last edited:
   #31  

trangakil

Verified VCDS-User
Verified
Joined
Jul 27, 2018
Messages
24
Reaction score
5
Location
Netherlands
VCDS Serial number
C?ID=329157
Hi All,

Is someone able to tell me what the security code is for the "BD" module?

Thanks!
 
   #32  

Andy

Administrator
Staff member
Joined
Jan 29, 2014
Messages
2,654
Reaction score
4,047
Location
Sector 7G
VCDS Serial number
HC424490
I checked but have not found a Security Access for the BD module.
 
  • Like
Reactions: Uwe
   #33  

NEtech

VCDS Distributor
Joined
Feb 7, 2014
Messages
2,171
Reaction score
3,508
Location
Denmark
VCDS Serial number
C?ID=56995
Is someone able to tell me what the security code is for the "BD" module?
If any used, there can be more than one.
Why and for what do you need a security code ?
 
   #34  

trangakil

Verified VCDS-User
Verified
Joined
Jul 27, 2018
Messages
24
Reaction score
5
Location
Netherlands
VCDS Serial number
C?ID=329157
I checked but have not found a Security Access for the BD module.
Hi Andy,

Thank you for the brief call yesterday and your reply!
 
   #35  

trangakil

Verified VCDS-User
Verified
Joined
Jul 27, 2018
Messages
24
Reaction score
5
Location
Netherlands
VCDS Serial number
C?ID=329157
If any used, there can be more than one.
Why and for what do you need a security code ?
Hi NEtech,

Changes to the module require a security access code. I have used a variety of the know codes, but it seems not to be one of those.
I need it to change some values in the adaption mode (channels). Please see the third page for a more detailed description. If you have any knowledge about this code, I would really appreciate if you can help me out with it.

Thanks.
 
   #36  

NEtech

VCDS Distributor
Joined
Feb 7, 2014
Messages
2,171
Reaction score
3,508
Location
Denmark
VCDS Serial number
C?ID=56995
First check measurement value: "Security Access: Number of invalid keys"

If you want to test, try this, no guaranties.
Copy this file to C:\Ross-Tech\VCDS-Beta\Labels\User
Enter the show text for secure access in [BD].
Please make screenshot of message(s).
 
   #37  

trangakil

Verified VCDS-User
Verified
Joined
Jul 27, 2018
Messages
24
Reaction score
5
Location
Netherlands
VCDS Serial number
C?ID=329157
First check measurement value: "Security Access: Number of invalid keys"

If you want to test, try this, no guaranties.
Copy this file to C:\Ross-Tech\VCDS-Beta\Labels\User
Enter the show text for secure access in [BD].
Please make screenshot of message(s).

Hi NEtech,
Read your message today and tried it out, it worked! Unfortunately the goal is not achieved (I keep getting faults).
Just wanted to thank you and update you, I will post a more eleborated update (with pictures) tomorrow.
:thumbs:
 
   #38  

trangakil

Verified VCDS-User
Verified
Joined
Jul 27, 2018
Messages
24
Reaction score
5
Location
Netherlands
VCDS Serial number
C?ID=329157
So after fixing the light problem, the next is already waiting. As described above I have tried some things, just one error I made in my description above. The adjustments can be made in the "BD-Hi Volt. Batt. Charg" module and not the 8c module as mentioned above.
When I finished the lights yesterday, I started to swap (again) the wiring harness, so the same issues applied at first. However as recommended by Uwe earlier I have installed the Beta version of VCDS and started coding.
The results are below:

Original coding 1
[/url]

Original coding settings


Changes (after these changes 2 faults)


The following 2 fault codes resulted after this:
Code:
1059842 - Charging Socket B 
          P33E2 00 [009] - Electrical Malfunction
          Confirmed - Tested Since Memory Clear
             Freeze Frame:
                    Fault Status: 00000001
                    Fault Priority: 2
                    Fault Frequency: 5
                    Reset counter: 47
                    Mileage: 35950 km
                    Date: 2018.08.03
                    Time: 14:00:23

1059074 - Charging Socket B; Plug Locking Detection 
          P31D6 00 [009] - Electrical Malfunction
          [Socket_B_Lock_Check_short_circuit_high]
          Confirmed - Tested Since Memory Clear
             Freeze Frame:
                    Fault Status: 00000001
                    Fault Priority: 2
                    Fault Frequency: 5
                    Reset counter: 47
                    Mileage: 35950 km
                    Date: 2018.08.03
                    Time: 14:00:23

So after trying some more coding options I changed the following and just one fault code remained:

Changes part 2:




1 Fault code remains:


With this remaning fault code the car thinks the cable is plugged in (while it is not) and therefore it won't start.

So in my opinion, based on the information I have at the moment, the following options have came up (from my side):
1. I'm missing something in the Codingtable (I have to select another option);
2. I have to adapt some things through the adaption channels (however I don't now what the settings should be and in addidion there is a accescode required which I don't have);
3. The VCDS beta version, has some bugs and therefore not working properly when coding this module (experimental coding);
4. The relais of the locking mechanism is broken, that is also what the fault code is indicating. However should not be the case, but anything is possible!

Does someone have any other ideas / solutions?

Thanks in advance!
So as promised yesterday, I would provide a more elaborated update today.
After the last coding attempt as described in post 33, I asked a cardealership (which had a EU e-Golf from 2015 for sale) if I could hook up VCDS to it. After doing that I made an autoscan of that vehicle and a controllermap of the "BD" unit.
Comparing my controllermap to this one showed me some differences:


In order to change the values I needed to code the module, with help of NEtech I was able to gain security access and to change values within the adaption channels.

However after changing the values (tried for socket A and B) it still gave me one fault and the car still thinks there is a cable plugged in (while it is not).

Code:
2097921 - External Plug on Charging Socket A 	
          P33EC 00 [009] - Electical Malfunction	
          Confirmed - Tested Since Memory Clear	
             Freeze Frame:	
                    Fault Status: 00000001	
                    Fault Priority: 2	
                    Fault Frequency: 1	
                    Reset counter: 48	
                    Mileage: 35996 km	
                    Date: 2018.08.16	
                    Time: 15:33:10	
	
                    Power outlet A for battery charging-Locking for H-V charge plug: not locked	
                    Power outlet A for battery charging-Status connect. recognition: detected	
                    Power outlet A for battery charging-Connector locking requirement: 0	
                    Power outlet A for battery charging-Connector unlocking requirement: 0	
                    Power outlet A for battery charging-Max. current of charge connector: 0 A	
                    Power outlet A for battery charging-Activation charge cover lock charge socket A: not requested	
                    Power outlet A for battery charging-Status charge cover lock charge socket A: not locked	
                    Power outlet A for battery charging-Activation charge cover unlock charge socket A: not requested	
                    Power outlet A for battery charging-Charge socket temperature sensor AC: 21.80 °C	
                    Power outlet A for battery charging-Charge sensor temperature sensor DC: 21.80 °C
And if I code socket B:
Code:
1059074 - Charging Socket B; Plug Locking Detection 	
          P31D6 00 [009] - Electrical Malfunction	
          [Socket_B_Lock_Check_short_circuit_high]	
          Confirmed - Tested Since Memory Clear	
             Freeze Frame:	
                    Fault Status: 00000001	
                    Fault Priority: 2	
                    Fault Frequency: 1	
                    Reset counter: 48	
                    Mileage: 35996 km	
                    Date: 2018.08.16	
                    Time: 16:24:37
After also swapping the relais for the locking mechanism it seems the relais is working correct.

Leaving me with the remaning conclusion:
1. I'm just doing it wrong and missing something;
2. I need to flash the module to an EU version with ODIS.


Screenshots for NEtech:






 
Top