What happens if you restore central electrics byte 29 to hex 00?
Do you still see subsystem E221__MFL-TAS under central electrics?


And then recode the above. Still the fault?
How do I change the 29 byte hex 40 to hex 00 do you want me to disable the mfsw and try enabling the cruise control
 
How do I change the 29 byte hex 40 to hex 00 do you want me to disable the mfsw and try enabling the cruise control
Yes, disable the MFSW in byte 29. And then enable the cruise control.
 
If it's any help for reference I have a T6 with a stork cruise switch and standard mfsw as supplied from new. I also have VCDS so can provide details of the original coding.
That would be great - also for future reference please. Preferably full VCDS Auto-Scan but as minimum engine (01), BCM (09), Instruments (17) sections.
 
That would be great - also for future reference please. Preferably full VCDS Auto-Scan but as minimum engine (01), BCM (09), Instruments (17) sections.
Here you go. There are a few tweaks from standard plus a tow bar module added but nothing drastic altered.

@mmi am I correct in thinking that the persistent Battery Regulator fault is most likely caused by the B2B unit that I have installed? That is a RING RSCDC30 with two leisure batteries and 100W Solar on the roof. I have always ignored the fault report as there has never been any obvious problem resulting from it. The B2B has been there for well over 50,000 miles.

If I can help with anything else please feel free to call.

Rod
 

Attachments

  • Log-VK66 VVU-WV1ZZZ7HZGH118939-97890km-60826mi-Auto Scan.txt
    10 KB · Views: 7
  • Like
Reactions: mmi
Thank you very much for the scan!
@mmi am I correct in thinking that the persistent Battery Regulator fault is most likely caused by the B2B unit that I have installed? That is a RING RSCDC30 with two leisure batteries and 100W Solar on the roof. I have always ignored the fault report as there has never been any obvious problem resulting from it. The B2B has been there for well over 50,000 miles.
Most likely yes. It's indeed just an indication of some extra (over factory configuration) quiescent current. Unfortunately the freeze frame data doesn't show the trigger level ("leak" current).

Based on my experiments I believe the trigger level is at about 40 mA extra. E.g. leaving Carista dongle (draws 40 mA) plugged in OBD-socket triggers the fault eventually (in 1-7 days, pretty random). However, leaving VCDS connected (120 mA current draw) definitely triggers the fault in less than 8 hours.
 
Yes byte 29 bit 6 in the central electrics
Well, based on @rod_vw 's scan and confirmed MFSW and CC on stalk configuration it looks like the byte 29 bit 6 might be related Cruise on MFSW setup. Instead you could try the same as in the scan - BCM byte 29 bit 5 (hex "20") to enable only MFSW without CC.

Noted on another scan that without MFSW but Cruise on stalk the byte 29 is plain hex "00".



EDIT (9 hours later) - Just had realized @rod_vw has LED-headlights and actually I had verified the (byte 29) bit 5 to be part of LED power setup here --> [Guide] How To Retrofit MFSW And Cruise Control To T6 Eu6 2019 Startline - Also Hacking DSG Paddles For CCS

Another thing to note is that MFSW connection to BCM is different between EU5 (T73b/17) and EU6 (T73b/36) engines (wiring diagram No 65/2)
 
Last edited:
So I have done what you suggested mfsw controls stop working as its connected to pin 36b and I also get these faults

Screenshot_20220305-170536_OBDeleven.jpg

Screenshot_20220305-170545_OBDeleven.jpg

Screenshot_20220305-170706_OBDeleven.jpg
 
So I have done what you suggested mfsw controls stop working as its connected to pin 36b and I also get these faults
The byte 29 bit 6, or bit 5 (as updated in post #164) ?
EDIT: I think we can ignore the bit 5 - see post #164 (edited)


Just to double check the codings please
In OBDeleven > Control Units > Central Elecrics > Info > Tap and hold on "Long coding" (copies the code into clipboard)
Post the coding.

The same for engine.
 
Last edited:
Sorry that's with it all so I don't have faults with mfsw working I will change it again to get the faults back up tomorrow and post this is the instructions I got with the loom so you know what I have done
 

Attachments

  • Pdf_translator_1646210582119.pdf
    6.6 MB · Views: 9
Just a thought is pin 44 A on the bcm a -12v instead of a +12v that I need
Pin 44 on the BCM connector T73a (BCM black connector) is correct +12V (IGNition on) for you. It's fused by SC32. I'm assuming the "A" is the T73a, and "B" is respectively T73b (BCM white connector)
1646564353536.png

However, I'm a bit curious about wiring. See on connector T41 pins 26 and 29 in the snippet below. Are they connected together in your wiring?
1646564799863.png
these are the connections I have done
1646565247663.png

Full OEM wiring diagram in the link - see page 102/2 for the above
 
Yes I've looked at that I also have a concern that in the instructions the image of t10 has alot of cables in that is the same as my middle black plug under the battery and my lowest black plug only had about 4 cables in it so could I have the wrong plug for t10
 
  • Like
Reactions: mmi
Have you checked CC switch statuses by OBDeleven?
OBDeleven > Control Units > Central Electrics > Live data > Channel 4

What's the status of "Main switch"?
OBD11-09-LiveData_Cruise_c.png
 
Sorry I've not been back to you looking at the drawing you sent me I'm just trying to get my head round it I'm guessing t94 and t73b are the black and white plugs at the bcm
 
Back
Top