Webasto! Why won’t it work on its own…. VCDS enabled??

I’m sat in my 2001 MY AMF it’s manual heating controls A2
With the engine ecu coded to 00005 block 016 is reading 11000000 with the econ button lit up
Press econ so light is out 10000000

The first digit is stating ambient above 5 deg C and dash is stating 11deg C so that looks like the only reason the webasto is not running is that ambient temp is too high

Recode to 00005
And all of the above is the same

With either engine ecu coding of 00002 or 00005 I can force the webasto to start by logging into aux heater (018) then basic settings (04) then 22
There was lots of smoke the first fire up which cleared in few mins
I’m going for some iced water to fool the ambient temp sensor and going to retry it on 00005


Sent from my iPhone using Tapatalk
 
Last edited:
7766fbe175d3d41068cb33561cfd25c0.jpg



Sent from my iPhone using Tapatalk
 
I’m sat in my 2001 MY AMF it’s manual heating controls A2
With the engine ecu coded to 00005 block 016 is reading 11000000 with the econ button lit up
Press econ so light is out 10000000

The first digit is stating ambient above 5 deg C and dash is stating 11deg C so that looks like the only reason the webasto is not running is that ambient temp is too high

Recode to 00005
And all of the above is the same

With either engine ecu coding of 00002 or 00005 I can force the webasto to start by logging into aux heater (018) then basic settings (04) the 22
There was lots of smoke the first fire up which cleared in few mins
I’m going for some iced water to fool the ambient temp sensor and going to retry it on 00005


Sent from my iPhone using Tapatalk
On a car with Climate, (well mine anyway), the ECON button lights up, when ECON is ON, not when it's OFF.
Mac.
 
The webasto kicked in when codes to 00005 and the ambient sensor had been sat in iced water for some 10 mins resulting in a dash temp of 4deg C

Whilst this is good news for me it goes against what we thought we understood ie that engine coding of 00005 prevented the webasto from operating- this is clearly not true, well defo not true for firmware version 1281?
It ‘may’ be the case with 1514 firmware
This therefore adds a further dimension to this puzzle

Paul


Sent from my iPhone using Tapatalk
 
The webasto kicked in when codes to 00005 and the ambient sensor had been sat in iced water for some 10 mins resulting in a dash temp of 4deg C

Whilst this is good news for me it goes against what we thought we understood ie that engine coding of 00005 prevented the webasto from operating- this is clearly not true, well defo not true for firmware version 1281?
It ‘may’ be the case with 1514 firmware
This therefore adds a further dimension to this puzzle

Paul


Sent from my iPhone using Tapatalk
Which firmware do your AMF maps employ? as these findings back up what I am seeing
 
All of them 1281 1514 and the one I can’t remember which is the amf engine with electrical heater
1514 is the majority though


Sent from my iPhone using Tapatalk
 
All of them 1281 1514 and the one I can’t remember which is the amf engine with electrical heater
1514 is the majority though


Sent from my iPhone using Tapatalk
Could the ECON input to the ECU be floating, in Map 5, because it's not being set?
Might explain the variations.
Mac.
 
All of them 1281 1514 and the one I can’t remember which is the amf engine with electrical heater
1514 is the majority though


Sent from my iPhone using Tapatalk
Evening Paul,

Both my fleet:

Project EUD January 2001 AMF
Project OEM September 2002 AMF

Are operating on firmware 1514 and do not allow the Webasto to kick in whilst running the 00005 map. The Webasto kicks in whilst running the 00002 map though.

I’m guessing firmware 1281 was very early which was phased out quickly.

Kind regards,

Tom
 
Not on 1281 that behaves the same with respect to bit2 (2nd from the left hand side) when codes to 00002 and 00005
If I get chance tomorrow I’ll fit a loan ecu with 1514 on it and retry

Paul


Sent from my iPhone using Tapatalk
 
Evening Paul,

Both my fleet:

Project EUD January 2001 AMF
Project OEM September 2002 AMF

Are operating on firmware 1514 and do not allow the Webasto to kick in whilst running the 00005 map. The Webasto kicks in whilst running the 00002 map though.

I’m guessing firmware 1281 was very early which was phased out quickly.

Kind regards,

Tom

Not as quickly as you might think
Check the physical sticker on the ecu for the original firmware

Paul


Sent from my iPhone using Tapatalk
 
Not on 1281 that behaves the same with respect to bit2 (2nd from the left hand side) when codes to 00002 and 00005
If I get chance tomorrow I’ll fit a loan ecu with 1514 on it and retry

Paul


Sent from my iPhone using Tapatalk

Hi Paul,

Have you seen the list I added a few minutes ago.

Evening Paul,

Both my fleet:

Project EUD January 2001 AMF
Project OEM September 2002 AMF

Are operating on firmware 1514 and do not allow the Webasto to kick in whilst running the 00005 map. The Webasto kicks in whilst running the 00002 map though.

I’m guessing firmware 1281 was very early which was phased out quickly.

Kind regards,

Tom

Firmware 1514 looks to be what is effected when the 00005 map is selected.

Kind regards,

Tom
 
Hi Paul,

Have you seen the list I added a few minutes ago.



Firmware 1514 looks to be what is effected when the 00005 map is selected.

Kind regards,

Tom

Need to be proven with more examples else why I’ll try a 1514 ecu in my car tomorrow if I get time

Anyone else running 1281 able to verify my own findings that coding makes no difference and the webasto works on 00002 and 00005

Equally people running 1514 can you confirm webasto only runs on 00002 and defo doesn’t run on 00005

Cheers. Paul


Sent from my iPhone using Tapatalk
 
On a car with Climate, (well mine anyway), the ECON button lights up, when ECON is ON, not when it's OFF.
Mac.
Good Evening Mac,

That is correct then. By pressing The ECON button (lights up) the air conditioning is turned off to save fuel and therefore it will be more ECONomical.

In addition if a Supplementary Heater is present this will be prevented from functioning to save even more fuel, as page 104 of the handbook.


1703099723413.jpeg



Andy
 
Not as quickly as you might think
Check the physical sticker on the ecu for the original firmware

Paul


Sent from my iPhone using Tapatalk
Hi Paul,

I confirmed that they are both operating on firmware 1514 by checking recent scan reports.

What I have noticed though, from historical scans is that Project EUD was running firmware 1281 this time last year which was well before I sent the ECU away to you for treatment.

I can only guess that the information you added originated from a 1514 firmware ECU . I cannot confirm which firmware Project OEM was initially running as I’ve wiped my laptop since then and lost the historical scan reports.

Assume that anyone running a mapped ECU will also be operating on firmware 1514.

Kind regards,

Tom
 
Hi Paul,

I confirmed that they are both operating on firmware 1514 by checking recent scan reports.

What I have noticed though, from historical scans is that Project EUD was running firmware 1281 this time last year which was well before I sent the ECU away to you for treatment.

I can only guess that the information you added originated from a 1514 firmware ECU . I cannot confirm which firmware Project OEM was initially running as I’ve wiped my laptop since then and lost the historical scan reports.

Assume that anyone running a mapped ECU will also be operating on firmware 1514.

Kind regards,

Tom

No your assumption is incorrect
1281 and 1514 have been supplied, more recently 1514 as been supplied for anyone originally running either 1281 or 1514 due to the view that 1514 is a later firmware and therefore a better basis for the ‘adjusted’ maps

I’ll confirm tomorrow how 1514 behaves in respect to the webasto and coding

Paul


Sent from my iPhone using Tapatalk
 
No your assumption is incorrect
1281 and 1514 have been supplied, more recently 1514 as been supplied for anyone originally running either 1281 or 1514 due to the view that 1514 is a later firmware and therefore a better basis for the ‘adjusted’ maps

I’ll confirm tomorrow how 1514 behaves in respect to the webasto and coding

Paul


Sent from my iPhone using Tapatalk
Hi again Paul,

Sorry for dragging this out but its quite interesting stuff to me. Here's the evidence that I'm working with which drew me to my assumption. The below scan report is from early-into-ownership of the JR A2:
Screenshot 2023-12-20 at 19.51.21.png


You'll see that the firmware was 1281 back in December 2022

Now check this report which was conducted in April 2023 upon getting the ECU back into the car after its holiday, you'll see its very same vehicle by VIN which is now operating on firmware 1514:
Screenshot 2023-12-20 at 20.04.07.png


My assumption is drawn from the Webasto working perfectly earlier this year in firmware 1281 ahead of the ECU holiday, but didn't fire up in the recent cold spell on firmware 1514 until this thread revealed that reverting back from the 00005 map to the 00002 map might cure the issue; it obviously did kick in straight after reverting the coding back as I reported earlier in this thread.

Maybe the Webasto will fire up when on the fuller map if my ECU is put back to firmware 1281. I'm assuming that your loan ECU operating on firmware 1514 will not allow the Webasto to fire up whilst running the 00005 map.

As I'd like to run the fuller map all year round due to having non-standard gearboxes fitted, what would I loose if my firmware was reverted from 1514 back to 1281.

Kind regards,

Tom
 
Hi again Paul,

Sorry for dragging this out but its quite interesting stuff to me. Here's the evidence that I'm working with which drew me to my assumption. The below scan report is from early-into-ownership of the JR A2:
View attachment 116633

You'll see that the firmware was 1281 back in December 2022

Now check this report which was conducted in April 2023 upon getting the ECU back into the car after its holiday, you'll see its very same vehicle by VIN which is now operating on firmware 1514:
View attachment 116635

My assumption is drawn from the Webasto working perfectly earlier this year in firmware 1281 ahead of the ECU holiday, but didn't fire up in the recent cold spell on firmware 1514 until this thread revealed that reverting back from the 00005 map to the 00002 map might cure the issue; it obviously did kick in straight after reverting the coding back as I reported earlier in this thread.

Maybe the Webasto will fire up when on the fuller map if my ECU is put back to firmware 1281. I'm assuming that your loan ECU operating on firmware 1514 will not allow the Webasto to fire up whilst running the 00005 map.

As I'd like to run the fuller map all year round due to having non-standard gearboxes fitted, what would I loose if my firmware was reverted from 1514 back to 1281.

Kind regards,

Tom

Nothing


Sent from my iPhone using Tapatalk
 
Back
Top