Story:

1. Freelander2 2009 without Telestart option
2. Upgrade via SDD
3. CCF change - success
4. AHCM (webasto) upgrade - no success, SDD communication error A01
5. PCM upgrade - success
6. Message on IPC: Auxilary heater not available low fuel
7. Thermotest shows 81h error - EOL checksum. This isn't very strange after unsuccessful flashing.
8. Then i do EEPROM dump upload to TTV - 81h error is off, but...
9. Thermotest shows new error:



So ID's over CAN bus are mismatched May this means that some part of AHCM software has been uploaded by SDD?
10. I do several other dumps upload without success ..

May someone has been experienced similar issue? If someone was successful with AHCM upgrade - please write SDD version and cable used.

I assume you are referring to a Webasto Winter pre heating unit ? Not common in UK if at all. FL2 MY10 TD4 GS traded in at 2 years
FL2 MY13 TD4 GS Current

Did you tried to do this step by step as you written on the first post or did you followed the procedure for activating Webasto Telestart in the SDD?
Because that procedure is doing all necessary things for you... Flashing engine and webasto firmware and activating the necessary things in CCF.
At least this is what I am remembering.... It was a looong time ago...

Can you try the SDD procedure again?...
Do you have the original EEPROM dump from this unit to flash it back?

.

Of course i folloved SDD procedure I have retried SDD flashing several times - nothing, always communication error with AHCM, other modules flashed without any problems. Yes, i flashed original dump - CAN ID's mismatch too. Now i thinking about EEPROM dump extraction from vbf file - may i will have some success. And may be last option - programmer and full dump of MC9...

I don't remember well, but if exists in case of AHCM, you can follow the procedure for replacing the AHCM and then the SDD will try to update the softwares inside the webasto to the latest version ...
Or just try to use the SDD in engineering mode and forcibly flash the desired vbf file to the AHCM.

I don't found possibility to configure AHCM as new device, but forcible flashing is a good idea

Hi VitasMatas,
Have you ever found a solution? Something similar happened to me today, and the end result is that the SDD doesn’t see the AHCM at all. No luck in trying to re-run the Enable Telestart option again, and no luck trying to add the module again.
Thanks for any guidance, much appreciated! MY2011, TD4 Auto, Xenon headlights, fog lamps DRLs, sunroof, tinted windows, almond electric seats w/ lumbar support, leather steering wheel w/ audio controls, dog/luggage guard, ambient lights, flush Whispbars, Mantec sump&tank guards, Xtrons Head Unit

Hi,

i can't say yes or no, because i haven't a chance to tried restore my friend's car until now(a bit big distance between us)..

But what i collect:

1. You need an old SDD 131
2. You need an WTT with engineering mode opened
3. You must update AHCM firmware with SDD(you shall have an error during update, but car now detects AHCM)
4. You must upload an working dump to Webasto with WTT

I can't confirm is this solution working or not ...

This is already very helpful, thank you! And it matches with some input I got from other sources. Will try to get a cable and old SDD in the next few days, and then attempt the procedure. Will report back here! MY2011, TD4 Auto, Xenon headlights, fog lamps DRLs, sunroof, tinted windows, almond electric seats w/ lumbar support, leather steering wheel w/ audio controls, dog/luggage guard, ambient lights, flush Whispbars, Mantec sump&tank guards, Xtrons Head Unit

VitasMatas wrote:

3. You must update AHCM firmware with SDD(you shall have an error during update, but car now detects AHCM)

You shall switch on telestart option as before - then SDD will update PCM, BCM and AHCM.

Tried, no luck. Car is 2011, though. And... multiple .prm files have been written via WTT since the telestart activation mishap, in the hope of recovery. Still no sign of AHCM on MS-CAN. Next step... replacing the webasto motherboard altogether. I think that an EEPROM rewrite would have done the trick but I was able to source a replacement board. Let’s see what happens next, once it arrives and I can make some time for the replacement job I’ll report back. MY2011, TD4 Auto, Xenon headlights, fog lamps DRLs, sunroof, tinted windows, almond electric seats w/ lumbar support, leather steering wheel w/ audio controls, dog/luggage guard, ambient lights, flush Whispbars, Mantec sump&tank guards, Xtrons Head Unit

Last upgrade:
1. Take somehow any interface, but not Mongoose Pro. Yesterday i used old Mongoose, NOT Pro and SDD 131;
2. Program FBH like NEW !
3. Dont forget external power supply!
4. Profit

P.S. First programming try was unsuccessful with A01 error, but second were Ok.

alex_pescaru wrote:

Do you have the original EEPROM dump from this unit to flash it back?

You can't via SDD. You need a different cable and software to connect to the webasto unit via its second protocol - WTT. I am replying from my mobile and can't do the search on the forum, but there is another topic around here that should provide all details. Also... At least in my understanding, all you can backup even via WTT is the configuration file, not the actual EEPROM/bootloader in webasto. And, at least in my case, that's precisely what was messed up by SDD. Solution was to rewrite the EEPROM by taking the motherboard out and using a specialised EEPROM programmer. I would assume that for a really safe backup the same tool would have to be used. Sorry I can't provide more info, but would definitely recommend to go through the post mentioned above - just search webasto on the forum. MY2011, TD4 Auto, Xenon headlights, fog lamps DRLs, sunroof, tinted windows, almond electric seats w/ lumbar support, leather steering wheel w/ audio controls, dog/luggage guard, ambient lights, flush Whispbars, Mantec sump&tank guards, Xtrons Head Unit