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

What's the title of the video as its just showing a sad box face saying YouTube took too long to respond?
Hi Tom,

It looks ready to view from where I’m sat:

IMG_8399.jpeg


If you search YouTube for VCDS Instrument Cluster Swap you should come across the picture above. Here’s what Google presents me from the said search:

IMG_8400.jpeg

The link in the yellow box is the text version of how to conduct the procedure, the orange box is the YouTube clip that talks you through the process.

Hope this helps.

Kind regards,

Tom
 
What I can tell you for sure is that as tdi 1.4 A2 left the factory the engine ecu coding was 00002
The only other coding option was 00005 which was an identical set of maps to 00002

So if your ecu is coded to 10005 then it’s not standard Audi firmware in the ecu
Who put the firmware on the ecu is a mystery unless you have something from the previous owner / service history to establish the source of the firmware

Looking at the sticker on top of the ecu you will see the firmware version that it was originally programmed with this being a four digit number For the AMF engine 1281 or 1514 are the two common ones used on engines paired with the webasto Aux heater

The AMF engine was fitted to different cars in the VAG range and they have their own firmware numbers and associated coding
I did have a list of these but fear it was lost some years ago with a hard drive failure
I remember the coding being different but in all honesty I can’t recall if there was a 1 at the beginning of the coding

Paul


Sent from my iPhone using Tapatalk
No service history or any information with the car whatsoever, however I believe it's been loved and modded at some point in its past as egr was disabled and cat gutted too it turns out so with finding its got remapped ecu too I wonder if someone like stealth has worked there magic, maybe they keep records of cars they have done but I doubt it!
 
Results from my AMF (not modified)
 

Attachments

  • compressed_1703445159831.jpeg
    compressed_1703445159831.jpeg
    23.4 KB · Views: 40
  • compressed_1703445160605.jpeg
    compressed_1703445160605.jpeg
    273.2 KB · Views: 35
  • compressed_1703445173570.jpeg
    compressed_1703445173570.jpeg
    293.7 KB · Views: 41
  • compressed_1703445172233.jpeg
    compressed_1703445172233.jpeg
    252 KB · Views: 37
  • compressed_1703445160036.jpeg
    compressed_1703445160036.jpeg
    23.2 KB · Views: 44
  • compressed_1703445160284.jpeg
    compressed_1703445160284.jpeg
    22.4 KB · Views: 42
This is one of the best and most interesting threads I've read on a topic like this, great investigation! :)

I know the answer to at least part of this mystery, but I don't want to spoil it if someone has been squirrelling away and thinks they might have nearly cracked it. @depronman @PlasticMac @2work

I'll say that you're very close with the thought about it being important if the car has climate control or not... And that the answer is out there, but knowing some German helps ;)

I can do a full post later if we're at a dead end :)
 
This is one of the best and most interesting threads I've read on a topic like this, great investigation! :)

I know the answer to at least part of this mystery, but I don't want to spoil it if someone has been squirrelling away and thinks they might have nearly cracked it. @depronman @PlasticMac @2work

I'll say that you're very close with the thought about it being important if the car has climate control or not... And that the answer is out there, but knowing some German helps ;)

I can do a full post later if we're at a dead end :)

Please bring your knowledge to the party


Sent from my iPhone using Tapatalk
 
If you take a look at the wiring diagrams, you can see that the “ECON” button on a non climate controlled car is actually a physical switch that connects directly to the ECU.
On a climate control car, this connection isn’t present and the state of this button is instead communicated over CAN bus.

It is true, there is no “coding” to tell the ECU if it has climate control or not (there actually may be, I need to research more). But the ECU is still “aware” via some internal flags that are part of the “map blocks”.
For the heater to work, 2 flags need to be set correctly. One flag tells the ECU to decode the CAN frames from the climate control. The other is a switch that moves the auxiliary heater inhibit source from a pin state “physical” to a memory location: That of the previously decoded CAN frame.

I imagine the default values for these flags is “no climate control” or at least the “physical” auxiliary heater inhibit button, and the calibrator who setup these ECU’s in the early 2000’s just didn’t bother to change them for map block 5. This is the reason that either coding setting will work for those who have none climate cars.

I’ll add some more details and references to support this later :)
 
And @Andrew is correct, the mystery bit in measuring block 16 is the state of the ECON button. It has potential to be a little more complex than that on a climate control car, but it is effectively that.
 
If you take a look at the wiring diagrams, you can see that the “ECON” button on a non climate controlled car is actually a physical switch that connects directly to the ECU.
On a climate control car, this connection isn’t present and the state of this button is instead communicated over CAN bus.

It is true, there is no “coding” to tell the ECU if it has climate control or not (there actually may be, I need to research more). But the ECU is still “aware” via some internal flags that are part of the “map blocks”.
For the heater to work, 2 flags need to be set correctly. One flag tells the ECU to decode the CAN frames from the climate control. The other is a switch that moves the auxiliary heater inhibit source from a pin state “physical” to a memory location: That of the previously decoded CAN frame.

I imagine the default values for these flags is “no climate control” or at least the “physical” auxiliary heater inhibit button, and the calibrator who setup these ECU’s in the early 2000’s just didn’t bother to change them for map block 5. This is the reason that either coding setting will work for those who have none climate cars.

I’ll add some more details and references to support this later :)

Great theory BUT
My own car is none climate and webasto
Webasto did not work for over two years, when I started to investigate it became apparent that if I changed the engine ecu coding from 00005 to 00002 then the webasto worked
Actually it didn’t but that was a faulty thermistor in the webasto. The bit sequence was all 0’s when codes to 00002 but had a 1 in the sequence when codes to 00005

I’ve since fixed the webasto and on coding 00005 it doesn’t work but change to coding 00002 and it fires up perfectly
If I press the econ button a 1 is set in the big sequence and the webasto does not fire up

Thoughts

Cheers. Paul


Sent from my iPhone using Tapatalk
 
I would still hazard a guess it's the same thing, just defaults that changed through firmware versions? Regardless of the reason behind it, the mechanism and solution is the same.

Below is how the logic works. The red text what Bosch calls the signals and variables, black is my notes. I am counting numbers from 0 not 1.
1707255404734.png

To make this work correctly, you need to find the variables in blue your ECU file and adjust them to suit.
Non-Climatronic cars should have CAN frame decoding disabled, and Climatronic cars should have decoding enabled of course.
All cars should be switched to use the upper logic flow, not the AC button state. That flow is only for cars with AC and no Auxiliary heater.

On other VAG cars, you can adjust the CAN frame decoding via coding, but the inhibit source selection bit is never accessible. It may be possible to bring this out into a coding setting, but more research is needed.

EDIT: ECON button state (CAN) may or may not be more than that. I'm not sure what logic the Climatronic module uses to set this flag.
 
Back
Top