Not really. As soon as outdoor temperature drops below +5C, the "Smart charging" regime fades away and the battery will get "full blast" charging - at approx. 14.8 Volts full time when engine is running. I'd say the battery will be fully charged.

E.g. yesterday it was -3C. Two 30+ min drives charging at the max voltage - as on day before, and on the day before that...
The voltage drops before driving are due to running Webasto 10-15 mins.
T6F_BM2_14.8V.jpg

When it gets really cold (-20C and below) as battery's charge acceptance deteriorates certainly need to keep eye on "energy balance" of the battery. To be on safe side, the rule of thumb we use is: in average need to run vehicle as long as Webasto is used for preheating.
 
Good to hear! :thumbsup:
If you still could dwell a bit on this - I'm curious how the flashing is now seen in "Advanced ID" under 18-Aux. Heater :geek:?

View attachment 62099

Monday,09,March,2020,15:51:33:24383
VCDS Version: Release 19.6.2 (x64)
Address 18: Aux. Heat
Control Module Part Number: 7E0 963 272 B
Component and/or Version: STH-T5GP2 003 0009
Software Coding: 5001
Work Shop Code: WSC 02737
VCID: 2B52A617425A0F1720-807F

Advanced Identification/FAZIT
Identification: WOS-000
Date: 21.07.16
Manufacturer number: 4632
Test stand number: 5009
Flash Status
Programming Attempts(application): 1/2/2
Flash Date: 00.00.00
Misc.
Hardware number: 7E0 963 273 A
Workshop System Name: J364
Equipment/PR Code: 000000000000000000000000
Dataset Number: -----------
Dataset Version: ----
ASAM Dataset: EV_AuxilParkiHeateWOST5G2
ASAM Dataset Revision: 001013
VCDS Info:
VCID: 2B52A617425A0F1720-807F
Labels: 7E0-963-27X-18.clb
ROD: EV_AuxilParkiHeateWOST5G2.rod
 
Having some weird issue with VCDS - every time I go to change some adaptations under module 09 (Cent. Elec.) as soon as I select something in the drop down list the VCDS disconnects and I get a communication error message. Sometimes I get "Unable to communicate with address 09. Are you sure the doors are unlocked?

I have created a thread elsewhere just wanted to check here too...

As you can see for the scan above, communication otherwise seems ok
 
  • Like
Reactions: mmi
Monday,09,March,2020,15:51:33:24383
VCDS Version: Release 19.6.2 (x64)
Address 18: Aux. Heat
Control Module Part Number: 7E0 963 272 B
Component and/or Version: STH-T5GP2 003 0009
Software Coding: 5001
Work Shop Code: WSC 02737
VCID: 2B52A617425A0F1720-807F

Advanced Identification/FAZIT
Identification: WOS-000
Date: 21.07.16
Manufacturer number: 4632
Test stand number: 5009
Flash Status
Programming Attempts(application): 1/2/2
Flash Date: 00.00.00
Misc.
Hardware number: 7E0 963 273 A
Workshop System Name: J364
Equipment/PR Code: 000000000000000000000000
Dataset Number: -----------
Dataset Version: ----
ASAM Dataset: EV_AuxilParkiHeateWOST5G2
ASAM Dataset Revision: 001013
VCDS Info:
VCID: 2B52A617425A0F1720-807F
Labels: 7E0-963-27X-18.clb
ROD: EV_AuxilParkiHeateWOST5G2.rod
So this looks like you had to flash it twice.
I wonder what went wrong with the first attempt.
 
  • Like
Reactions: mmi
Then, a suggestion - if you are running Webasto from starter battery, change coding to 5101 (now 5001) by ticking Bit 0 (of byte 0).

Then Webasto would be under van's own "energy management" which would inhibit starting Webasto if starter battery is too low. Otherwise there is a chance to end up having non-starting but warm van :D
(Ignore the Bit 3 in the picture)
View attachment 62098

Currently internal low voltage cut-out is set 11.3 Volts (see adaptations).
View attachment 62099

Thanks again @mmi - this is now activated too !

KKE Aux Heat on Batt Mgmnt.png
 
If I wanted to change the temperature the auxiliary heater activated at (currently 5'c - thinking to change to 8'c) would this be the correct place to do that? :

Aux Heat Low Temp Threshold.png
 
  • Like
Reactions: g_b
Yes, that would be the correct place. Actually I would tweak also upper threshold accordingly to prevent repetitive starting/stopping of Webasto.
upload_2020-3-11_12-51-25.png

E.g. I have tweaked mine other way - to trigger at slightly cooler temperatures.
upload_2020-3-11_12-54-0.png

However, currently the VCDS cannot do this ---> VW Transporter T6, Address 18 Aux.Heat --- Adaptation FAIL
Fortunately OBDeleven all0wed me to change these.

Just a note - it seems that Security Access is needed for Webasto adaptations, and interestingly different adaptations use different codes. The VCDS shows all the access codes but doesn't explicitly specify which one to use - so if one doesn't work then try another.

----------------
To understand how often the Webasto has been fired up in the past you could dig out a blockmap from Webasto (--> Aux. Heater Blockmaps, Adaptation maps - How-to ) and to even more to elaborate on this :geek:- the same blockmap from engine (module 01) to see how many times engine has been started.
PS. Interested here to see if the flashing zeroed counters in Webasto blockmap - please ;)
 
managed to connect to vcds to give:

Thursday,31,October,2019,20:25:50:04368
VCDS Version: Release 19.6.1 (x64) Running on Windows 10 x64
www.Ross-Tech.com
Thursday,31,October,2019,20:26:54:04368
VCDS Version: Release 19.6.1 (x64)
Address 18: Aux. Heat
Control Module Part Number: 7E0 963 272 B
Component and/or Version: STH-T5GP2 003 0009
Software Coding: 5901
Work Shop Code: WSC 02737
VCID: 2B0306B58384215F4FB-807E

Advanced Identification/FAZIT
Identification: WOS-000
Date: 07.09.16
Manufacturer number: 4830
Test stand number: 9534
Flash Status
Programming Attempts(application): 1/1/1
Flash Date: 00.00.00
Misc.
Hardware number: 7E0 963 273 A
Workshop System Name: J364
Equipment/PR Code: 000000000000000000000000
Dataset Number: -----------
Dataset Version: ----
ASAM Dataset: EV_AuxilParkiHeateWOST5G2
ASAM Dataset Revision: 001013
VCDS Info:
VCID: 2B0306B58384215F4FB-807E
Labels: 7E0-963-27X-18.clb
ROD: EV_AuxilParkiHeateWOST5G2.rod

Address 18: Aux. Heat Labels: 7E0-963-27X-18.clb
Control Module Part Number: 7E0 963 272 B HW: 7E0 963 273 A
Component and/or Version: STH-T5GP2 003 0009
Software Coding: 5901
Work Shop Code: WSC 02737 790 50316
ASAM Dataset: EV_AuxilParkiHeateWOST5G2 001013 (VN75)
ROD: EV_AuxilParkiHeateWOST5G2.rod
VCID: 2B0306B58384215F4FB-807E
Fault Codes have been Erased

1 Fault Found:
0266 - Databus
U1121 00 [009] - Missing Message
[TIMEOUT mDachdisplay]
Confirmed - Tested Since Memory Clear
Freeze Frame:
Fault Status: 00000001
Fault Priority: 6
Fault Frequency: 1
Reset counter: 169
Mileage: 38358 km
Date: 2035.14.02
Time: 20:24:58

Operating condition of parking heater: System malfunction
71
Coolant temperature of parking heater: 16 °C
Coolant temperature: 23 °C
Engine running status: not recognized
Fuel level: 19 l
Heater output: 0 W

@James fitch did you manage to get rid of this fault?
0266 - Databus
U1121 00 [009] - Missing Message
[TIMEOUT mDachdisplay]

And if so, how?
 
  • Like
Reactions: mmi
Hi @Robert - yes, I have the same fault code, I cleared it but it comes back straight away :


Wednesday,11,March,2020,09:09:14:24383
VCDS Version: Release 19.6.2 (x64) Running on Windows 10 x64
www.Ross-Tech.com

Address 18: Aux. Heat Labels: 7E0-963-27X-18.clb
Control Module Part Number: 7E0 963 272 B HW: 7E0 963 273 A
Component and/or Version: STH-T5GP2 003 0009
Software Coding: 5101
Work Shop Code: WSC 02737 790 50316
ASAM Dataset: EV_AuxilParkiHeateWOST5G2 001013 (VN75)
ROD: EV_AuxilParkiHeateWOST5G2.rod
VCID: 2B52A617425A0F1720-807E
Fault Codes have been Erased

1 Fault Found:
0266 - Databus
U1121 00 [009] - Missing Message
[New feature! Extended UDS fault detail is only supported by current gen. interfaces]
Confirmed - Tested Since Memory Clear
Freeze Frame:
Fault Status: 00000001
Fault Priority: 6
Fault Frequency: 1
Reset counter: 179
Mileage: 36497 km
Date: 2040.14.29
Time: 09:07:20

Operating condition of parking heater: OFF
71
Coolant temperature of parking heater: 11 °C
Coolant temperature: 12 °C
Engine running status: not recognized
Fuel level: 50 l
Heater output: 0 W
 
Did some experimenting - removed fuse feeding Webasto remote controller AND Webasto overhead control panel (module 6E, see --> LINK ) and then the following came up o_O

Code:
Thursday,19,March,2020,10:53:24:38894
VCDS -- Windows Based VAG/VAS Emulator Running on Windows 7 x64
VCDS Version: 19.11.3.0 (x64)  HEX-V2 CB: 0.4513.4
Data version: 20200107 DS317.0
--------------------------------------------------------------------------------

Address 18: Aux. Heat       Labels: 7E0-963-27X-18.clb
Control Module Part Number: 7E0 963 272 B    HW: 7E0 963 272 B
Component and/or Version: STH-T5GP2     003 0009
Software Coding: 5801
ASAM Dataset: EV_AuxilParkiHeateWOST5G2 001013 (VN75)
ROD: EV_AuxilParkiHeateWOST5G2.rod
VCID: 2B000D1DD38C4EB3AB9-807E

3 Faults Found:

0266 - Databus
          U1121 00 [009] - Missing Message
          [TIMEOUT mDachdisplay]
          Confirmed - Tested Since Memory Clear
             Freeze Frame: [REMOVED]

0280 - Local Data Bus
          U10BA 00 [009] - No Communication
          [TIMEOUT FFBs_01]
          Confirmed - Tested Since Memory Clear
             Freeze Frame: [REMOVED]

0281 - Local Data Bus
          U10BA 00 [009] - No Communication
          [TIMEOUT FFBs_02]
          Confirmed - Tested Since Memory Clear
             Freeze Frame: [REMOVED]
So in the coding there are only few remaining bits to twiddle... to see if overhead control panel can be coded out...
 
Last edited:
Did some experimenting - removed fuse feeding Webasto remote controller AND Webasto overhead control panel (module 6E, see --> LINK ) and then the following came up o_O

Code:
Thursday,19,March,2020,10:53:24:38894
VCDS -- Windows Based VAG/VAS Emulator Running on Windows 7 x64
VCDS Version: 19.11.3.0 (x64)  HEX-V2 CB: 0.4513.4
Data version: 20200107 DS317.0
--------------------------------------------------------------------------------

Address 18: Aux. Heat       Labels: 7E0-963-27X-18.clb
Control Module Part Number: 7E0 963 272 B    HW: 7E0 963 272 B
Component and/or Version: STH-T5GP2     003 0009
Software Coding: 5801
ASAM Dataset: EV_AuxilParkiHeateWOST5G2 001013 (VN75)
ROD: EV_AuxilParkiHeateWOST5G2.rod
VCID: 2B000D1DD38C4EB3AB9-807E

3 Faults Found:

0266 - Databus
          U1121 00 [009] - Missing Message
          [TIMEOUT mDachdisplay]
          Confirmed - Tested Since Memory Clear
             Freeze Frame: [REMOVED]

0280 - Local Data Bus
          U10BA 00 [009] - No Communication
          [TIMEOUT FFBs_01]
          Confirmed - Tested Since Memory Clear
             Freeze Frame: [REMOVED]

0281 - Local Data Bus
          U10BA 00 [009] - No Communication
          [TIMEOUT FFBs_02]
          Confirmed - Tested Since Memory Clear
             Freeze Frame: [REMOVED]
So in the coding there are only few remaining bits to twiddle... to see if overhead controller can be coded out...
So there are at least 4 of us(confirmed) with the same fault code in the heater after flashing and installation of Telestart. Myself, @markob, @James fitch and @wolny
 
Last edited:
  • Like
Reactions: mmi
Did some experimenting - removed fuse feeding Webasto remote controller AND Webasto overhead control panel (module 6E, see --> LINK ) and then the following came up o_O

Code:
Thursday,19,March,2020,10:53:24:38894
VCDS -- Windows Based VAG/VAS Emulator Running on Windows 7 x64
VCDS Version: 19.11.3.0 (x64)  HEX-V2 CB: 0.4513.4
Data version: 20200107 DS317.0
--------------------------------------------------------------------------------

Address 18: Aux. Heat       Labels: 7E0-963-27X-18.clb
Control Module Part Number: 7E0 963 272 B    HW: 7E0 963 272 B
Component and/or Version: STH-T5GP2     003 0009
Software Coding: 5801
ASAM Dataset: EV_AuxilParkiHeateWOST5G2 001013 (VN75)
ROD: EV_AuxilParkiHeateWOST5G2.rod
VCID: 2B000D1DD38C4EB3AB9-807E

3 Faults Found:

0266 - Databus
          U1121 00 [009] - Missing Message
          [TIMEOUT mDachdisplay]
          Confirmed - Tested Since Memory Clear
             Freeze Frame: [REMOVED]

0280 - Local Data Bus
          U10BA 00 [009] - No Communication
          [TIMEOUT FFBs_01]
          Confirmed - Tested Since Memory Clear
             Freeze Frame: [REMOVED]

0281 - Local Data Bus
          U10BA 00 [009] - No Communication
          [TIMEOUT FFBs_02]
          Confirmed - Tested Since Memory Clear
             Freeze Frame: [REMOVED]
So in the coding there are only few remaining bits to twiddle... to see if overhead control panel can be coded out...
Is it possible to isolate power going to overhead unit only?
 
  • Like
Reactions: mmi
Just a follow up on this but... I’m starting to use the auxiliary heater a lot and worry a bit about draining the main (starter) battery. If I fit a secondary battery under the passenger seat will the heater still run off the main battery? Is there a way to run of the secondary or both batteries ?
 
  • Like
Reactions: mmi
Have a look below.

20200529_021154.jpg
20200529_022007.jpg
It appears that you would need to redirect your heater supply from fuse SC46 to your auxiliary battery to take it off the starter battery.
 
Last edited:
  • Like
Reactions: mmi
In the attachment the OEM way - (also my way).

However, the heater cabin blower will still run from starter battery - approx. 6 Amps still remaining (of total of 12 Amps).

However, I think you can't drain starter battery (too low) by using the Webasto - the Energy Management kicks in well before and either prevents starting the heater or shuts it down. A quote from my post ---> VCDS And Carista Fault Codes
"​
0040 [B1381 00] - Shutdown by Battery Management Module
Van was not driven for 4 weeks, Webasto didn't start from a remote, however the van still cranked and started just fine. Temperature -1℃ .
Battery Management (61) reported available charge 18 Ah (Battery 92 Ah, 2+ years).
"​
 

Attachments

  • T6_Webasto_Power_a (1).pdf
    392 KB · Views: 42
Having some weird issue with VCDS - every time I go to change some adaptations under module 09 (Cent. Elec.) as soon as I select something in the drop down list the VCDS disconnects and I get a communication error message. Sometimes I get "Unable to communicate with address 09. Are you sure the doors are unlocked?

I have created a thread elsewhere just wanted to check here too...

As you can see for the scan above, communication otherwise seems ok
I've seen the same a few times. Still under investigation but at the moment the prime suspect is battery voltage getting low. I seem to get this starting at around 12 Volts at cigarette socket but can't tell what's at the BCM or at the OBD-socket (definitely less anyway).
 
Back
Top