fredu
New Member
Posts: 14
|
Post by fredu on Dec 4, 2021 18:07:49 GMT
A week age my 2015 GOLF SV battery ran down after using the radio for too long while parked.
The car was jump started by roadside assistance, but ever since then it has been losing charge overnight.
First I suspected (original 2014) battery may be near end of life so replaced with new, a correctly spec'd Bosch AGM.
But no change. Still going flat when parked for more that one day.
Tested for parasitic draw and found the MIB2 infotainment system is drawing 1.2A to 1.5A even when the car is switched off and locked.
And this draw is continuous. Doesn't stop after a period of time.
Battery state of charge drops to 50% over one night, but increases to 95% after engine running for an hour or so so clearly no problem with charging system.
This has only been happening since the jump start.
By way of a bit of background, in July 2021 I replaced the original MIB1 head unit with a brand new, legal MIB2 unit supplied by the VW franchised dealer who sold me the car.
I'd bought it from them in Sept. 2020 and the MIB upgrade was part of the deal; but unfortunately they're a long way from me and Covid lockdowns meant they couldn't do the installation and coding.
After doing the physical installation and got my local VW dealer to remove Component Protection ... however they didn't seem to know how to install the FeC's so until I can find someone here in the south of Ireland, with ODIS, who actually knows what they're doing, I'm stuck with a just working radio, working blue tooth telephony and a working reversing camera but nothing else.
I don't believe the incomplete coding has anything to do with the parasitic drain I'm experiencing now otherwise it would have been happening ever since I did the installation in July.
I wasn't there at the time that the roadside assistance service did the jumpstart so I don't know if they connected to the chassis terminal or the battery negative.
Is it possible that they could have damaged the new head unit by connecting the jump leads incorrectly?
And if so then could that damage somehow be limited only to the sudden current drain while leaving the unit itself working as it did before?
I suspect the more likely explanation is that either the jumpstart, or some kind of system reset after the flat battery, may have changed something somewhere in the rest of the car's coding which is somehow preventing the MIB2 system from "going to sleep".
If that is so then how would I go about finding and correcting it with obdeleven?
Any explanation or ideas would be gratefully received.
|
|
|
|
Post by dv52 (Australia) on Dec 4, 2021 19:55:44 GMT
fredu : hmm........too many unknowns to start making suggestions as to the cause of the problem.Still in the information gathering stage!
What does your scan report say? Maybe post-up a copy, so we can see how the car is equipped and what the CAN diagnostics say?
Don
|
|
|
|
Post by vwjap on Dec 4, 2021 21:34:01 GMT
You tried a hard reset of the mib? Press and hold on/off till restart
|
|
fredu
New Member
Posts: 14
|
Post by fredu on Dec 5, 2021 0:32:29 GMT
Yes. Tried a hard reboot. But no change.
|
|
|
|
Post by vwjap on Dec 5, 2021 10:31:23 GMT
Do you have the old unit? Can you put it back in? See if drain is still there?
Also what is the new unit? Discover pro? (Because on some units you can change the FEC container to put it into a service mode that enables all the fec’s)
|
|
fredu
New Member
Posts: 14
|
Post by fredu on Dec 5, 2021 13:20:24 GMT
Hi Don,
Scan follows.
OBDeleven data log
Date: 2021-12-05 13:04
VIN: WVWZZZAUZFW533864
Car: Volkswagen Golf Sportsvan
Year: 2015
Body type: 5-dr hatchback
Engine: CRKB
Mileage: 108238 KM
---------------------------------------------------------------
01 Engine
System description: R4 1,6L EDC
Software number: 04L906021AP
Software version: 6561
Hardware number: 04L907309E
Hardware version: H22
ODX name: EV_ECM16TDI01104L906021AP
ODX version: 002010
Long coding: 01250012036505092000
Trouble codes:
No trouble codes found
---------------------------------------------------------------
02 Transmission
System description: GSG DQ200-MQB
Software number: 0CW300047R
Software version: 5201
Hardware number: 0AM927769K
Hardware version: H43
Serial number: CU501408126131
ODX name: EV_TCMDQ200021
ODX version: 001001
Long coding: 0014
Trouble codes:
No trouble codes found
---------------------------------------------------------------
03 Brakes
System description: ESC
Software number: 5Q0907379M
Software version: 0571
Hardware number: 5Q0907379H
Hardware version: H31
Serial number: 62284000000797
ODX name: EV_Brake1UDSContiMK100IPB
ODX version: 033001
Long coding: 03FA8AA12423896F037F060641C725C0512491C06082A4F3F842F078C202
Trouble codes:
No trouble codes found
---------------------------------------------------------------
08 Air Conditioning
System description: AC Manuell
Software number: 5G0907426Q
Software version: 0907
Hardware number: 5G0907426Q
Hardware version: H02
ODX name: EV_ACManueBHBVW37X
ODX version: 003019
Long coding: 08120104202100001000000000000000
Trouble codes:
No trouble codes found
---------------------------------------------------------------
09 Central Electrics
System description: BCM PQ37BOSCH
Software number: 5Q0937086S
Software version: 0106
Hardware number: 5Q0937086S
Hardware version: 028
Serial number: 86582608140425
ODX name: EV_BodyContrModul1UDSBosc
ODX version: 013004
Long coding: 03001842C2C102730BA44080B10403281008000000000000000000000000
Subsystems:
System description: WWS 140718
Software version: X596
Hardware version: 043
Serial number: 140724021638
Long coding: 0E4DDD
System description: RLS
Software version: 0059
Hardware version: 037
Serial number: S5Y14M08D19H08M49S43
Long coding: 00A8DD
System description: Sensor, DWA
Software version: 0315
Hardware version: 005
Serial number: 000000000ZY141901YUZ
System description: Sirene, DWA
Software version: 0311
Hardware version: 004
Serial number: 00000000000029624461
Trouble codes:
No trouble codes found
---------------------------------------------------------------
13 Adaptive Cruise Control
System description: ACC Bosch MQB
Software number: 5Q0907572D
Software version: 0304
Hardware number: 5Q0907572D
Hardware version: H05
Serial number: 24081403211086
ODX name: EV_ACCMRRBoschVW372
ODX version: 001015
Long coding: 001C1300FE0339
Trouble codes:
No trouble codes found
---------------------------------------------------------------
15 Airbag
System description: AirbagVW20
Software number: 5Q0959655AA
Software version: 0386
Hardware number: 5Q0959655AA
Hardware version: 014
Serial number: 003MLR087UF4
ODX name: EV_AirbaVW20SMEVW37X
ODX version: 002130
Long coding: 98CCC000000000005C5400CF00C800000065
Subsystems:
System description: BeltPretRevFL
Software version: 0341
Hardware version: H35
Serial number: 34185455B30071441140
Long coding: 333135
System description: BeltPretRevFR
Software version: 0341
Hardware version: H35
Serial number: 34185454B20081470045
Long coding: 333135
System description: SideSensor_Df
Software version: 0887
Hardware version: 001
Serial number: 3576700000015841A01F
Long coding: 2D2D2D
System description: SideSensor_Pf
Software version: 0887
Hardware version: 001
Serial number: 358670000008A541A01P
Long coding: 2D2D2D
System description: SideSensor_Dr
Software version: 6149
Hardware version: 001
Serial number: 3516502A716C6CE051DN
Long coding: 2D2D2D
System description: SideSensor_Pr
Software version: 6149
Hardware version: 001
Serial number: 3526502A516C6CE1432D
Long coding: 2D2D2D
System description: FrontSensor_D
Software version: 6149
Hardware version: 001
Serial number: 3556502C917750B15323
Long coding: 2D2D2D
Trouble codes:
No trouble codes found
---------------------------------------------------------------
16 Steering Column
System description: Lenks. Modul
Software number: 5Q0953507DB
Software version: 0110
Hardware number: 5Q0953549C
Hardware version: 002
Serial number: 22081404221588
ODX name: EV_SMLSKLOMQB
ODX version: 017001
Long coding: 0410
Trouble codes:
No trouble codes found
---------------------------------------------------------------
17 Dashboard
System description: KOMBI
Software number: 517920941
Software version: 4270
Hardware number: 517920941
Hardware version: 203
ODX name: EV_DashBoardVDDMQBAB
ODX version: 009037
Long coding: 27E502082780000001803A201400000000000000
Trouble codes:
U112100 - Databus missing message
static
---------------------------------------------------------------
19 Gateway
System description: GW MQB High
Software number: 5Q0907530T
Software version: 1188
Hardware number: 5Q0907530F
Hardware version: 128
Serial number: 0002386958
ODX name: EV_GatewLear
ODX version: 011016
Long coding: 030100140B087300EF00005C1C0F00010001050000000000000000000000
Subsystems:
System description: J367-BDMHella
Software version: 8043
Hardware version: H03
Serial number: 7040224203
System description: E221__MFL-DC1
Software version: 0038
Hardware version: H16
Serial number: 27140002152730034352
Long coding: 2CFFFF
Trouble codes:
No trouble codes found
---------------------------------------------------------------
42 Driver Door
System description: TSG FS
Software number: 5Q0959393B
Software version: 0025
Hardware number: 5Q0959393B
Hardware version: 020
Serial number: 12081402090169
ODX name: EV_DCUDriveSideEWMINKLO
ODX version: 006003
Long coding: 003002208001048000001000
Subsystems:
System description: FOND_FHSG_DRV
Software version: 0005
Hardware version: 005
Serial number: 00000000000003575522
Long coding: 0D0000
Trouble codes:
No trouble codes found
---------------------------------------------------------------
44 Steering Assistance
System description: EPS_MQB_ZFLS
Software number: 5Q0909144P
Software version: 1043
Hardware number: 5Q0909144P
Hardware version: 122
ODX name: EV_SteerAssisMQB
ODX version: 010031
Long coding: 8103
Trouble codes:
No trouble codes found
---------------------------------------------------------------
52 Passenger Door
System description: TSG BFS
Software number: 5Q0959392B
Software version: 0025
Hardware number: 5Q0959392B
Hardware version: 020
Serial number: 15081406070569
ODX name: EV_DCUPasseSideEWMINKLO
ODX version: 006003
Long coding: 003000208001048000801000
Subsystems:
System description: FOND_FHSG_PSG
Software version: 0005
Hardware version: 005
Serial number: 00000000000003567533
Long coding: 150000
Trouble codes:
No trouble codes found
---------------------------------------------------------------
5F Multimedia
System description: MU-S-ND-ER
Software number: 3Q0035874A
Software version: 0245
Hardware number: 3Q0035874A
Hardware version: H24
Serial number: VWZAZ2T1454650
ODX name: EV_MUStd4CTSAT
ODX version: 001022
Long coding: 027309010000000011010000800802001F0000727080010096
Subsystems:
System description: ABT_Std-2_Nav
Software version: 1028
Hardware version: H52
Serial number: VWZ8Z9REN00ZBA
Trouble codes:
No trouble codes found
|
|
fredu
New Member
Posts: 14
|
Post by fredu on Dec 5, 2021 13:39:48 GMT
Not so easy to put the old unit back.
Not just a question of swapping out.
I had to change the screen module as well because they use a different cable.
Not sure if it's Discover Pro.
Hardware code is 3Q0035874A if that helps.
But enabling all the FeC's won't help because they've never been installed in the first place.
My local VW dealer managed to remove Component Protection but that seems to be as far as their skill set goes
The VW coding instructions supplied with the unit included an ODIS procedure to "Rewrite PR numbers" which I assume would have also restored the FeC's, but that was too much for them.
They insisted they would need the car for 3 days to do it which I don't believe. I'm not willing to pay their school fees.
Still looking for someone here who can do it, but that's another issue.
As I said in the original post, I don't think it's related to the sudden current drain otherwise it would have shown up earlier.
|
|
|
|
Post by dv52 (Australia) on Dec 5, 2021 20:33:58 GMT
hmm......... I'm not sure that I understand why the long-code string on the hex5F module is set-up as it is?
It's coded for MOST (optical fiber communications normally linked to an external amp - but no amplifier of any sort is coded).
It's coded for a bunch of dashboard "slide" facilities (phone, audio and navigation)- which I suspect are not installed on your car because you have a bog-standard clock based instrument cluster (this might explain the error on the hex17 module)
It's coded for EU navigation, but you say that that FECs were never installed
in summary- the long-code string is a complete mystery (to me) and I suspect that the adaptation channel settings on the hex 5F module might also be problematic
The way to address these problems is to use the values from the old hex5F module and compare them with the retrofit unit. Did you record these values before you swapped modules?
Don
|
|
|
|
Post by dv52 (Australia) on Dec 5, 2021 20:38:14 GMT
Do you have the old unit? Can you put it back in? See if drain is still there? Also what is the new unit? Discover pro? (Because on some units you can change the FEC container to put it into a service mode that enables all the fec’s) vwjap: You always surprise me - I didn't know about the FEC container having this facility!!! Is it a process that can be explained in a forum?
Don
|
|
|
|
Post by vwjap on Dec 5, 2021 23:17:47 GMT
Not 100% sure really, but it was for the software engineers to back door the FEC’s onto the unit, they may have moved on again tho, back to like changing it with whatthefec but using some metainfo2 hack,
but I think it went something like this, the exceptlist file had FEC’s that were to be ignored on load up, and they were enabled because you’ve told them not to look to see if they were in the FECcontainer file, but as I understand some people in Germany had a problem when setting it up, so they’ve gone back to adding the FEC’s via a patch file, just like when you’d use whatthefec changing the feccontainer directly,
|
|
fredu
New Member
Posts: 14
|
Post by fredu on Dec 7, 2021 1:21:34 GMT
Hi Don, I had noticed the coding for MOST but didn't want to change it as I didn't know what it was. I've now disabled it, but that hasn't cleared the hex17 error. Yes, it is coded for EU navigation. In fact the navigation is the main reason for doing the upgrade in the first place. When selected, the navigation screen comes up and asks for the data card, but when I put the original VW card into the SD slot it sees it but doesn't accept it. I'm not sure about the instrument cluster coding. Could it have the wrong unit specified? Because mine definitely has the multifunction centre screen per the attached photo showing insets of the various screens available. I'm a bit confused as to just what has and hasn't been done and/or what needs to be done to get the system running properly. The VW installation instructions talk about "Rewriting PR codes". But then I read about SWaP codes and FeC codes. As I understand it these various codes are provided by some central VAG computer which then maps them to my VIN. But ultimately I have no clear idea of just what they do or how they relate to one another. All I do know is that none of them seem to exist on my system. As things stand today I have a fully functional radio; I can access and play media on both SD slots as well as the USB port; I have full bluetooth and telephony functionality from both the touch screen and steering wheel controls; as mentioned, the nav. screen comes up but won't accept the data card; and the reversing camera is working on the infotainment screen. But EVERY other function comes up as unavailable including things as basic as setting the date and time. If I want to retrieve the values from the old hex5F unit then can you confirm that it is safe for me to temporarily swap the units. The workshop which did the Component Protection Removal (which, shockingly, is a major VW and Merc. dealer and workshop) informed me in no uncertain terms that if I ever even so much as unplug any of the cars control modules, including the infotainment head unit, then the Component Protection would reinstate itself and I'd have to go back to them to get it removed again. Frankly I find that very hard to believe, which is yet another reason I'm reluctant to go back there, but it would be great if you can confirm one way or the other. For the record, I confess to being a novice when it comes to automotive setup and configuration but I do have a background in industrial and marine CanBus systems so I do have at least some idea what I'm looking at. Coming back to the problem of the parasitic draw; isn't it the case that if the hex5F module is "staying awake" then the likely culprit could be a signal on the bus rather that something in the unit coding itself? And if so then where does the sleep/wake signal for the hex5F module come from? Cheers, Fred  |
|
|
|
Post by vwjap on Dec 7, 2021 10:04:27 GMT
Fec’s are pretty simple,
All radios have all the hardware the same, Vw just sell different options, now they put a wall up to certain options in the factory when your car is made if you don’t spec the option, this wall is the FEC, now if it’s enabled in the factory then it’s like they put a door in the wall so when you start the unit it come up to the wall and if you haven’t got it enabled it doesn’t have access to that option, if it’s got the door it enables the option, simple as that
Now putting a new unit in the car is I bit complicated, because people steal the units Vw have put a protection in (like the old radio codes) but the new way is have a central computer (gateway) ask all the other computers if they belong to the car, it it doesn’t then that ecu will be limited, this is component protection (cp) now if you buy a “new” unit or can prove the unit is legit Vw will remove cp by plugging it into the servers in Germany and say it’s a new unit, this will tell the gateway that this is now the unit for the vehicle (which your dealer did), but when you do this the unit still has all the walls in place for the options, so you then have to ask the server in Germany to open all the doors (add the fec’s) (which your dealer didn’t do)
Now one problem with this is nav (as I understand) because Vw don’t like you adding nav to a car, so they won’t enable that FEC from the factory, as the car was never bought with that option,
I’ve unplugged mine a few times and never had a problem with cp 🤷♂️
|
|
|
|
Post by vwjap on Dec 7, 2021 10:19:04 GMT
Maybe a wall is not a good analogy maybe rooms with a locked door is better
So when each FEC is enabled your given that key
So say you have 10 rooms (voice, sports, Bluetooth, nav, etc)
And you spec 5 options so you get 5 keys
On startup the unit looks what keys you have and opens the 5 doors and the other 5 remain locked, those 5 options work, the others don’t
Now when you spec (buy) another option (say CarPlay) Vw servers give you the key (fec) to that room and put the key on your key ring (feccontainer)
Now don52 the software engineers dont want to go through all the nonsense adding fec’s so they have a hidden door (exception list) where they just ignore the locked door (FEC) and walk round the side to the hidden one
|
|
|
|
Post by dv52 (Australia) on Dec 7, 2021 20:42:42 GMT
Fred: vwjap analogy of doors in a wall is very good - that's exactly the way that FECs operate; they are a series of personal licenses that enable various features in the MIB. I'm confused about your dealer's advice regarding Component Protection (CP). In brief CP works like this: every time that you turn the ignition key to the ON position, the module that OBD11 calls "Gateway" goes through the CP interrogation process (the Gateway module is called the "CP master module"). The Gateway module starts the CP process by asking each of the main modules on the CAN network for their identity. The Gateway module then compares each of the replies against the identities in its own master list of the modules that have been legitimately registered. If there is a discrepancy in the comparison, a CP error is generated. Note: the CP error (if generated) really only applies for the current ignition cycle - but the entire process is repeated in the next ignition cycle! The dealer's procedure that you undertook changed the module identity in the Gateway master list from the old to the new MIB. The CP master list is encrypted and it sits in non-volatile memory in your car. So, it doesn't matter how many times you remove/replace the MIB - as long as the identity of the MIB remains unchanged, it will pass the CP interrogation process (after each ignition cycle). Think about it - removing the MIB from the car is electrically the same as unplugging the car's battery. If your dealer's advice was correct, you would need to go back to have CP errors deleted every time that you changed a battery - what utter nonsense!! vwjap is very knowledgeable regarding how to hack MIBs to enable FECs - but the official VW process for factory installed FECs should also have been completed on your car. The dealer process for CP error removal is a 2 x part procedure; the actual registering of the new module identity into the Gateway master list AND the transfer of the FECs from the old MIB into the new MIB. Was this done? Now, your old MIB didn't have the navigation function - so it didn't have the associated FEC. Does your new module have the SATNAV FEC and is it compatible with your country region? If you don't know how to find these details, look at YouTube videos BUT (and there is always a "but")- if you unplug your existing (registered) MIB and re-install the old MIB, you should expect a CP error. Your car currently has the new MIB identity registered - if you put back the old MIB, the CP interrogation process won't pass. However, this shouldn't affect the exercise of extracting data from the old MIB - and once you re-install the new MIB, the CP error should clear (because the identity of the new MIB will be the same as in the car's master list)
Don
|
|
|
|
Post by vwjap on Dec 8, 2021 22:16:05 GMT
Don you normally loose all FEC’s in the new unit when you clear CP, and I think if you didn’t have nav on the original then it won’t be enabled when you load the FEC’s
Also I think if you have nav on a MIB1 and swap to a Mib2 then you lose nav as it’s a different fec between the units
|
|
goni
New Member
Posts: 45
|
Post by goni on Dec 12, 2021 0:14:04 GMT
Maybe a bit out of topic sorry, i swapped too from mib 1 to 2.5 and i no longer have "Driver Assistance" available and start stop button in screen is "Function not available" too, can it be problem with coding?
|
|
|
|
Post by dv52 (Australia) on Dec 12, 2021 7:48:18 GMT
goni:Not sure what precisely is meant by "Driver Assistance" as it relates to the MIB - but the function that is encoded into the Start Stop button is programmed into the MIB by the hex5F channel Button in center console-Function of button 1. Set the value to Start-stop
Don
|
|
goni
New Member
Posts: 45
|
Post by goni on Dec 12, 2021 8:55:06 GMT
The Driver assistance in my infotaiment contained only "driver assist" and " proactive occupant protection" , but when i try to access that setting in infotaiment screen it says Function currently not available. Same for Start Stop icon in vehicle status . I couldnt find what you instructed me to do anywhere but i found this function not activated ..can this be the problem?  |
|
|
|
Post by vwjap on Dec 12, 2021 14:09:11 GMT
09 (so should be the same)
Button in center console:
Funktion Taster 1:
Start-stop
Funktion Taster 2:
not coded/not installed
Funktion Taster 3:
Driving program
Funktion Taster 4:
not coded/not installed
Zusatzcodierung Fahrprofiltaster hat keine LED:
LED installed
5F
Start_Stop_reasons_0x27:
activated
Start_Stop_reasons_0x27_msg_bus:
Databus Infotainment
You tried changing service?
You tried clearing app data
|
|
goni
New Member
Posts: 45
|
Post by goni on Dec 12, 2021 17:36:47 GMT
Hello, after that adaptation Start Stop button in discover pro works perfectly , but driver assistance is still not available can you help with that too? Car only had proactive passanger pritection and driver assist or smthg like that i cannot remember well, thank you a lot Here is a pic of message when i try to click in Driver assistance  |
|
|
|
Post by vwjap on Dec 12, 2021 18:19:00 GMT
Maybe the systems arnt activated in the menu system and may have to add the one by one
Try setting these see if you can get in then
Car_Function_Adaptations_Gen2:
menu_display_Lane_Departure_Warning:
activated
menu_display_Lane_Departure_Warning_clamp_15_off:
Not activated
menu_display_Lane_Departure_Warning_over_threshold_high:
activated
menu_display_Lane_Departure_Warning_standstill:
Not activated
menu_display_Lane_Departure_Warning_after_disclaimer:
Not activated
menu_display_lane_assistant:
activated
menu_display_lane_assistant_clamp_15_off:
Not activated
menu_display_lane_assistant_over_threshold_high:
activated
menu_display_lane_assistant_standstill:
Not activated
menu_display_lane_assistant_after_disclaimer:
Not activated
|
|
goni
New Member
Posts: 45
|
Post by goni on Dec 12, 2021 18:52:48 GMT
Hi, car doesn't have lane assist or departure feautre , as I mentioned only function that were listed in Driver Assistance when I had mib1 were "Proactive occupant protection " and "Driver assist" .
|
|
|
|
Post by vwjap on Dec 13, 2021 9:27:14 GMT
I just wanted you to add something easy to see, so that you could see if you could then get into the menu, then we could try to work out what switches control the two you mentioned later as I don’t know the acronyms for the two options your asking about
|
|
goni
New Member
Posts: 45
|
Post by goni on Dec 13, 2021 11:18:33 GMT
Hi , i managed to activate the function by activating "menu_display_weariness_recognition" ,i still need to find the Proactive occuoant protection, also i dont have Conveninence consumers list in screen but i have them in AID
|
|
|
|
Post by vwjap on Dec 13, 2021 11:23:42 GMT
I think that’s Reversible seat belt
|
|
goni
New Member
Posts: 45
|
Post by goni on Dec 13, 2021 11:24:38 GMT
Yes it was exactly that , just enabled it thank you a lot for your time , if somehow you know the conv.consumers list i would appreciate .
|
|
|
|
Post by vwjap on Dec 13, 2021 18:27:30 GMT
Try bcme in the same part
|
|
goni
New Member
Posts: 45
|
Post by goni on Dec 14, 2021 12:31:28 GMT
Its already activated but doesnt work  |
|
|
|
Post by vwjap on Dec 14, 2021 20:51:39 GMT
What about these?
Car_Function_List_BAP_Gen2-BCmE_0x23), activated
Car_Function_List_BAP_Gen2-BCmE_0x23_msg_bus), Databus Infotainment
|
|
goni
New Member
Posts: 45
|
Post by goni on Dec 15, 2021 10:41:20 GMT
This function was already activated as you mentioned it
|
|
