Central electric module 9 not responding 2014 GTI

[ag13]

Still could use some help with this. Everything on the car is running as it such but I still have no access to this module. I have done the door lock, battery, car on/off, disconnected battery, all doors open/ closed tricks and still no access. Any help would be greatly appreciated.

Do you folks think I should unplug the module and let it sit for a few minutes without power to reset it?

 

[DV52]

Still could use some help with this. Everything on the car is running as it such but I still have no access to this module. I have done the door lock, battery, car on/off, disconnected battery, all doors open/ closed tricks and still no access. Any help would be greatly appreciated.

ag13: I've been watching your thread unfold with academic interest (but alas without the ability to help). The only contribution that I can make to solving your problem (and it's a very small contribution) is by way of reference to your CodingLog File. I have parsed the data from this file below and I have stripped-out the control modules that don't relate to your auto-scan report. I'm not sure what Dana had in mind when she (I'm assuming that Dana is a "she") requested the file, but I'm guessing that she wanted to look at the changes that you have made to the coding/adaptation channels. Without seeking to steal any of Dana's thunder (and she wields a considerable amount of thunder!) do the changes in the table look correct?

Since discussion thus far has cantered on the BCM, I note that the only alteration in the codinglog file to your BCM is a change to Byte 12 from Hex70 to Hex30. Was this change correct?

 

[ag13]

Thanks for posting. I actually made several changes to that module that don't seem to appear on the list. Running lights to fog, led tag light no warning I'm sure this was more technically labeled, mirror dip, etc. this has been quite mind blogging as to why I can't get back in. I even tried using a security but it stated some sort of seed issue.

ag13: I've been watching your thread unfold with academic interest (but alas without the ability to help). The only contribution that I can make to solving your problem (and it's a very small contribution) is by way of reference to your CodingLog File. I have parsed the data from this file below and I have stripped-out the control modules that don't relate to your auto-scan report. I'm not sure what Dana had in mind when she (I'm assuming that Dana is a "she") requested the file, but I'm guessing that she wanted to look at the changes that you have made to the coding/adaptation channels. Without seeking to steal any of Dana's thunder (and she wields a considerable amount of thunder!) do the changes in the table look correct?

Since discussion thus far has cantered on the BCM, I note that the only alteration in the codinglog file to your BCM is a change to Byte 12 from Hex70 to Hex30. Was this change correct?

 

[DV52]

Thanks for posting. I actually made several changes to that module that don't seem to appear on the list. Running lights to fog, led tag light no warning I'm sure this was more technically labeled, mirror dip, etc. this has been quite mind blogging as to why I can't get back in. I even tried using a security but it stated some sort of seed issue.

ag13: Again, my apology if my reply regarding your issue is less-than-helpful, but I note that there are no entries in the file that you posted after 24 September 2014 (for your car). The missing line entries that you mention could be explained if (like me) you are using Mr Ross's Beta SW ver concurrently with the full release SW ver. If this is so, there is a separate CodingLog.txt file in the Ross-Tech \Beta directory.

 

[ag13]

As if this couldnt get any stranger. Dealer did a reset of the system this past week during scheduled maintainance. I no longer get an error code, gateway scan now states central electronics is status ok, but I still have no communication with it. Same box pops up unable to communicate. I would be happy to pay for additional help on this from Ross tech of its available.

ag13: Again, my apology if my reply regarding your issue is less-than-helpful, but I note that there are no entries in the file that you posted after 24 September 2014 (for your car). The missing line entries that you mention could be explained if (like me) you are using Mr Ross's Beta SW ver concurrently with the full release SW ver. If this is so, there is a separate CodingLog.txt file in the Ross-Tech \Beta directory.

 

[Uwe]

I'm scratching my head. Can you please post a current Auto-Scan from your car?

-Uwe-

 

[ag13]

Now am worried even more with you scratching your head: Uwe I have to hit done on module 9 because it hangs up on it, had it hung there for up to 30 mins when I finally hit done go back and then it continues scanning other modules. I appears it communicating but when I try to access it I get the unable to communicate with module. I have tried every trick from battery disconnect to opening all doors unlocking locking etc.

VCDS Version: Release 14.10.0 (x64)
Data version: 20141022

Monday,24,November,2014,20:58:14:53396

Chassis Type: AJ (7N0)
Scan: 01 02 03 08 09 15 16 17 19 25 2E 37 42 44 46 52 56 62 72 77
         

VIN: WVWHD7AJ2EW000948   Mileage: 16660km-10352miles

01-Engine -- Status: OK 0000
02-Auto Trans -- Status: OK 0000
03-ABS Brakes -- Status: OK 0000
04-Steering Angle -- Status: OK 0000
08-Auto HVAC -- Status: OK 0000
09-Cent. Elect. -- Status: OK 0000
15-Airbags -- Status: OK 0000
16-Steering wheel -- Status: OK 0000
17-Instruments -- Status: OK 0000
19-CAN Gateway -- Status: OK 0000
25-Immobilizer -- Status: OK 0000
2E-Media Player 3 -- Status: OK 0000
37-Navigation -- Status: OK 0000
42-Door Elect, Driver -- Status: OK 0000
44-Steering Assist -- Status: OK 0000
46-Central Conv. -- Status: OK 0000
52-Door Elect, Pass. -- Status: OK 0000
56-Radio -- Status: OK 0000
62-Door, Rear Left -- Status: OK 0000
72-Door, Rear Right -- Status: OK 0000
77-Telephone -- Status: OK 0000
 
-------------------------------------------------------------------------------
Address 01: Engine (CBF)       Labels: 06J-907-115-CBF.clb
   Part No SW: 1K0 907 115 AT    HW: 1K0 907 115 AK
   Component: 2.0l R4/4V TFSI     0020  
   Revision: E3H26---    Serial number:               
   Coding: 040301081C070160
   Shop #: WSC 01357 011 00200
   VCID: 78D107C10B03DFE157B-802D

No fault code found.
Readiness: 0000 0000

-------------------------------------------------------------------------------
Address 02: Auto Trans        Labels: 02E-927-770.lbl
   Part No SW: 02E 300 058 P    HW: 02E 927 770 AL
   Component: GSG DSG AG6     521 3513  
   Revision: 05652104    Serial number: 00001307120742
   Coding: 0000020
   Shop #: WSC 01357 011 00200
   VCID: 277314BD963D80190E1-8072

No fault code found.

-------------------------------------------------------------------------------
Address 03: ABS Brakes (J104)       Labels: 1K0-907-379-60EC1F.clb
   Part No SW: 1K0 907 379 BL    HW: 1K0 907 379 BL
   Component: ESP MK60EC1   H31 0152  
   Revision: 00H31001    
   Coding: 114B600C492200FA881406E892210041B70800
   Shop #: WSC 01357 011 00200
   VCID: 7DDF16D5E421FAC904D-8028

No fault code found.

-------------------------------------------------------------------------------
Address 08: Auto HVAC (J301)       Labels: 3C8-907-336.clb
   Part No SW: 7N0 907 426 BH    HW: 7N0 907 426 BH
   Component: AC Manuell    H20 0505  
   Revision: 00001019    
   Coding: 0010000002
   Shop #: WSC 01357 011 00200
   ASAM Dataset: EV_ACManueBHBVW36X A01010
   ROD: EV_ACManueBHBVW36X_SE36.rod
   VCID: 7BDB18CDF235F4F93A9-802E

No fault code found.

-------------------------------------------------------------------------------
Address 09: Cent. Elect.        Labels: 1K0-937-08x-09.clb
   Part No SW: 1K0 937 086 T    HW: 1K0 937 086 T
   Component: BCM PQ35  M   111 0709  
   Coding: 6F180A3898232BC4008800C1200083A448810386435D8D604B8020200040
   Shop #: WSC 01357 011 00200
   VCID: 41A7AA25D8595E29205-8014

   Subsystem 1 - Part No: 5K1 955 119   Labels: 1KX-955-119.CLB
   Component: Wischer 09071  26  0512 
   Coding: 009F95


-------------------------------------------------------------------------------
Address 15: Airbags (J234)       Labels: 5K0-959-655.clb
   Part No SW: 5C0 959 655 M    HW: 5C0 959 655 M
   Component: AirbagVW10G   014 0726  
   Serial number: 003L4R02ADUO  
   Coding: 00004737
   Shop #: WSC 01357 011 00200
   ASAM Dataset: EV_AirbaVW10SMEVW360 001026
   ROD: EV_AirbaVW10SMEVW360_SK35.rod
   VCID: 3C59DBD1B7BB33C1733-8069

   Seat occupied recognition: 
   Subsystem 1 - Part No SW: 5K0 959 339 B    HW: 5K0 959 339 B
   Component: BF-Gewichtss.  006 0001 
   Serial number: ---0000R--00008FM400

   Crash sensor for side airbag; driver side: 
   Subsystem 2 - Part No SW: 5K0 959 354     HW: 5K0 959 354 
   Component: S.Sens.Fahr.V  H02 ---- 
   Serial number: 3572MSME0A311578ZZZS

   Crash sensor for side airbag; front passenger side: 
   Subsystem 3 - Part No SW: 5K0 959 354     HW: 5K0 959 354 
   Component: S.Sens.Beif.V  H02 ---- 
   Serial number: 3582MSME0070617BZZZQ

   Crash sensor for side airbag; rear; driver side: 
   Component: S.Sens.Fahr.H  --- ---- 
   Serial number: 3512QSME480B3049ZZZU

   Crash sensor for side airbag; rear; passenger side: 
   Component: S.Sens.Beif.H  --- ---- 
   Serial number: 3522QSME5A183232ZZZQ

   Crash sensor for front airbag; driver side: 
   Component: F.Sens.Fahr  --- ---- 
   Serial number: 35527SME625E732FZZZU

   Crash sensor for front airbag; front passenger side: 
   Component: F.Sens.Beif  --- ---- 
   Serial number: 35627SME1E54732FZZZS

No fault code found.

-------------------------------------------------------------------------------
Address 16: Steering wheel (J527)       Labels: 5K0-953-569.clb
   Part No SW: 5K0 953 507 AH    HW: 5K0 953 549 B
   Component: Lenks.Modul   008 0090  
   Revision: --------    Serial number:  90422MH2000W8
   Coding: 189A140000
   Shop #: WSC 46056 001 104857
   ASAM Dataset: EV_SMLSNGKUDS A05001
   ROD: EV_SMLSNGKUDS_SE36.rod
   VCID: 76CD09F9C917A991457-8023

   Multi Function Steering Wheel Control Module: 
   Subsystem 1 - Part No SW: 5K0 959 542 B    HW: 5K0 959 542 B  Labels: 3C8-959-537.CLB
   Component: E221__MFL-TAS  H30 0036 
   Serial number: 0089279             
   Coding: 830000

No fault code found.

-------------------------------------------------------------------------------
Address 17: Instruments (J285)       Labels: 5K0-920-xxx-17.clb
   Part No SW: 5K6 920 973 C    HW: 5K6 920 973 C
   Component: KOMBI         H05 0705  
   Serial number: 00000000000000
   Coding: 070901
   Shop #: WSC 01357 011 00200
   ASAM Dataset: EV_Kombi_UDS_VDD_RM09 A04716
   ROD: EV_Kombi_UDS_VDD_RM09_SE25.rod
   VCID: 3753C4FD8E9D10999E1-8062

No fault code found.

-------------------------------------------------------------------------------
Address 17: Instruments (J285)       Labels: 5K0-920-xxx-17.clb
   Part No SW: 5K6 920 973 C    HW: 5K6 920 973 C
   Component: KOMBI         H05 0705  
   Serial number: 00000000000000
   Coding: 070901
   Shop #: WSC 01357 011 00200
   ASAM Dataset: EV_Kombi_UDS_VDD_RM09 A04716
   ROD: EV_Kombi_UDS_VDD_RM09_SE25.rod
   VCID: 3753C4FD8E9D10999E1-8062

No fault code found.

-------------------------------------------------------------------------------
Address 19: CAN Gateway (J533)       Labels: 7N0-907-530-V2.clb
   Part No SW: 7N0 907 530 AF    HW: 7N0 907 530 AF
   Component: J533  Gateway H52 1634  
   Revision:   H52       Serial number: 020713F1001299
   Coding: 350002
   Shop #: WSC 01357 011 00200
   VCID: 74C933F1D76BBB817B3-8021

No fault code found.

-------------------------------------------------------------------------------
Address 25: Immobilizer (J334)       Labels: 5K0-920-xxx-25.clb
   Part No SW: 5K0 953 234     HW: 5K0 953 234 
   Component: IMMO          H05 0705  
   Serial number: 00000000000000
   Coding: 000000
   Shop #: WSC 01357 011 00200
   ASAM Dataset: EV_Immo_UDS_VDD_RM09 A03709
   ROD: EV_Immo_UDS_VDD_RM09_SE25.rod
   VCID: 6AF52D898DAF7D71D1F-803F

No fault code found.

-------------------------------------------------------------------------------
Address 2E: Media Player 3 (J650)       Labels: 5N0-035-342.lbl
   Part No SW: 5N0 035 342 G    HW: 5N0 035 342 G
   Component: SG EXT.PLAYER H19 0770  
   Revision: A1001003    Serial number: 7665038284    
   Coding: 010100
   Shop #: WSC 01357 011 00200
   VCID: 2B7BE88D4AD5A479EA9-807E

No fault code found.

-------------------------------------------------------------------------------
Address 37: Navigation (J794)       Labels: 1K0-035-27x-37.clb
   Part No SW: 1K0 035 274 K    HW: 1K0 035 274 K
   Component: RNS315-NAR    H76 0410  
   Serial number: VWZAZ2P0026729
   Coding: 040004210400060400008000
   Shop #: WSC 01383 790 50316
   ASAM Dataset: EV_RNS315NARV2UDS 001705
   ROD: EV_RNS315NARV2UDS.rod
   VCID: 2C79EB9147DBA341E33-8079

   Data medium: 
   Subsystem 1 - Part No: 3AA 919 866 B
   Component: NAR_V5N  0046 

No fault code found.

-------------------------------------------------------------------------------
Address 42: Door Elect, Driver        Labels: 1K0-959-701-MIN3.lbl
   Part No SW: 5K0 959 701 H    HW: 5K0 959 701 H
   Component: Tuer-SG         009 2105  
   Coding: 0001460
   Shop #: WSC 01357 011 00200
   VCID: 3753C4FD469D10999E1-8062

No fault code found.

-------------------------------------------------------------------------------
Address 44: Steering Assist        Labels: 1Kx-909-14x-44.clb
   Part No: 1K0 909 144 R
   Component: EPS_ZFLS Kl. 74     3501  
   Revision: 00H22000    
   Shop #: WSC 01357 011 00200
   VCID: 3957C2C5708906E9685-806C

No fault code found.

-------------------------------------------------------------------------------
Address 52: Door Elect, Pass.        Labels: 1K0-959-702-MIN3.lbl
   Part No SW: 5K0 959 702 H    HW: 5K0 959 702 H
   Component: Tuer-SG         009 2105  
   Coding: 0001460
   Shop #: WSC 01357 011 00200
   VCID: 3851C7C14B831FE197B-806D

No fault code found.

-------------------------------------------------------------------------------
Address 62: Door, Rear Left        Labels: 1K0-959-703-GEN3.lbl
   Part No SW: 5K0 959 703 D    HW: 5K0 959 703 D
   Component: Tuer-SG         007 2101  
   Coding: 0001168
   Shop #: WSC 01357 011 1012552
   VCID: 354FCEF55C91E2898CD-8060

No fault code found.

-------------------------------------------------------------------------------
Address 72: Door, Rear Right        Labels: 1K0-959-704-GEN3.lbl
   Part No SW: 5K0 959 704 D    HW: 5K0 959 704 D
   Component: Tuer-SG         007 2101  
   Coding: 0001168
   Shop #: WSC 01357 011 1012552
   VCID: 364DC9F94197E991857-8063

No fault code found.

-------------------------------------------------------------------------------
Address 77: Telephone (J412)       Labels: 7P6-035-730.clb
   Part No SW: 7P6 035 730 K    HW: 7P6 035 730 K
   Component: TELEFON       H15 3200  
   Revision: 1B001001    Serial number: 00007665094725
   Coding: 0A10040000010100
   Shop #: WSC 01357 011 00200
   ASAM Dataset: EV_UHVNA 002720
   ROD: EV_UHVNA.rod
   VCID: 3A55DDC9BD8F0DF161F-806F

No fault code found.

End-------------------------(Elapsed Time: 02:33)--------------------------

 

[Uwe]

There's never a reason to wait for more than (I'm going to say this somewhat arbitrarily) 1 minute in VCDS unless there's something obvious going on. If it sits there longer than that doing nothing and hasn't told you it's going to be a while, something is, uh, not functioning nominally. In other words, don't bother waiting 30 minutes.

Anyway, it seems your 09 module is back to talking. Sometimes. When it feels like it. For a while. The question now becomes: Is the module wonky? Or is the scan tool (which consists of VCDS, your Micro-CAN interface, and the PC it's running on) the problem? Let's see what we can see. With it all hooked up, go to [Options], set Debug Level to 1024, then click [Apply]. Then [Select] and [09-Cent.Elect]. If you get in, [Fault Codes-02]. If you don't get in, try it a few times (and you never need to wait more than one minute tops). When you're done, there should be a file named DEBUG-09.DLM in your Debug sub-folder, typically C:\Ross-Tech\VCDS\ Send that file to Support@... along with a link to this thread please.

-Uwe-

 

[ag13]

Email sent, no access

 

[Eric]

One of the slaves of module 09 is causing module 09 to make the scan tool wait indefinitely when we request identification. VCDS is trying to break out of that wait, but the module refuses any further request since it's still (presumably) waiting on that slave. Not sure where you go from there, could be an actual slave malfunctioning, the wiring to it, or any coding/adaptation change you made...

 

[Dana]

One of the slaves of module 09 is causing module 09 to make the scan tool wait indefinitely when we request identification. VCDS is trying to break out of that wait, but the module refuses any further request since it's still (presumably) waiting on that slave. Not sure where you go from there, could be an actual slave malfunctioning, the wiring to it, or any coding/adaptation change you made...

OK now that we know the 09 issue is slave related, and this car only has one slave (unless a RLS is installed, but I doubt that), I have to wonder if it is faulty. You mentioned replacement sylvania silver stars .. and even though those bulbs are NOT noted for causing problems (I run them in my Halogen cars) I have to wonder if the headlight bulbs or some combination of pulling and reinstalling fuses spiked the BCM and/or connected slave wiper motor.

I think we should locate and remove the fuse for the wiper motor so you can Auto-Scan it again and see if my theory is correct. I'll edit this post after I locate a wiring diagram.

Edit:
Vehicle Identification No. WVWHD7AJ2EW000948
2013 (5K19W3) GTI | Production date 16.08.2013
Engine code CBFA
Transmission code PBH

Per the Standard equipment (Canada, Mexico, USA) from November 2011 wiring diagram # 121, J400 (Wiper motor control module) is powered from one of two possible fuses - depending on the installed fuse box:

SB31 (E-Box High)
SB19 (E-Box Low)

If you have parking spots/slots for 2 total relays in the box under the hood I would consider that the Low system.
If you have parking spots/slots for 4 total relays in the box under the hood I would consider that the High system.

Either way, the fuse should be a 30A and that is Terminal 30 (constant battery power) power source.

 

[ag13]

Ok pulled the fuse and confirmed by trying wipers which didn't go on. That said still no access to module and now I do show an error but no code on the gateway list which I can not erase. Help! That said I do remember changing the wiper settings in module 9 to one sweep after using the windshield washer, when I did have access.

 

[DV52]

ag13: I know that it's little solace, but the aberrant behaviour of your BCM is an intriguing mystery (that seems to have captured the interest of lots of folk here). Your thread reads like the unfolding story to a good book - every new post adds yet another dimension to the development of the plot.

Whilst I don't want to interrupt the flow of Dana's hypothesis, just for my own edification can you confirm my suspicion from a previous post - please?

ag13: Again, my apology if my reply regarding your issue is less-than-helpful, but I note that there are no entries in the file that you posted after 24 September 2014 (for your car). The missing line entries that you mention could be explained if (like me) you are using Mr Ross's Beta SW ver concurrently with the full release SW ver. If this is so, there is a separate CodingLog.txt file in the Ross-Tech \Beta directory.

 

[Dana]

Did pulling that fuse for the test resolve the Auto-Scan problem?

 

[Eric]

I don't have a fresh enough version of Sebastian's work (hello! ) to comment about 08, but Dana did mention this car is a RNS 510 retrofit. Nothing wrong with that, however I see 42 had its coding changed to reflect Seat Memory installed. Seeing how the door modules being locked interfere with comms to 09, I'd urge a revert to the original coding of both 42 and 52 if Seat Memory is not actually installed. Very good point DV52

 

[DV52]

Eric: I removed my post after I re-read the thread (about RNS 510 retrofit). Guess I got so interested in the plot of AG13's unfolding story, that I forget about the storyline detail (always a risk with a good book!).

Can you provide more information about the interaction between the door control modules and comms with 09? Why does this happen?

 

[Eric]

Well, I didn't write the firmware in those controllers, but our guess is that locking the doors sends some sort of a sleep signal to the central electrics or the gateway. Is it far fetched that the door modules could make 09 misbehave if they were told to interact with seat memory functionality when there is none? I think reverting the coding is worth a try

 

[DV52]

Well, I didn't write the firmware in those controllers, but our guess is that locking the doors sends some sort of a sleep signal to the central electrics or the gateway. Is it far fetched that the door modules could make 09 misbehave if they were told to interact with seat memory functionality when there is none? I think reverting the coding is worth a try

Eric: Thanks for the explanation which makes sense. And yes, I agree that rolling back the codes is an easy-try.

Ag13: Here's the rest of the compare between the two Auto-scans (first line in each address is the earlier auto-scan)

 

[ag13]

I hope in the end the story doesn't have a bum ending, lol. Ok auto scan still hangs on module 9. I did put back in the oem bulbs, no change. Eric when I get home this evening I will recode back to oem per your breakdown and retry. Just so you all know I REALLY appreciate your help on this. It seriously is a brain teaser.

Eric: Thanks for the explanation which makes sense. And yes, I agree that rolling back the codes is an easy-try.

Ag13: Here's the rest of the compare between the two Auto-scans (first line in each address is the earlier auto-scan)

 

[ag13]

unfortunately no change even restoring all items to oem status.

I hope in the end the story doesn't have a bum ending, lol. Ok auto scan still hangs on module 9. I did put back in the oem bulbs, no change. Eric when I get home this evening I will recode back to oem per your breakdown and retry. Just so you all know I REALLY appreciate your help on this. It seriously is a brain teaser.