W212 trailer module coding help ?

[Pingpong]

Hi folks, got a favour to ask for some advice.

I have tried to code a mates W212 My 2010 E class rear SAM to recognise his tow bar.

I initially tried using DAS 2014, but even this was no good... even under developer mode ( it finds TM_212 ) under the BODY module, as I thought it may be in the SAMR, but when I try to activate the TM_212 I get the message that it's "not part of the car" or something like that...

Damn...

I then swapped out HDDs for a 2011 DAS vintage.... got closer, as it allowed me to try offline coding with a password... but again, no joy...

I then went further with DAS 2008, which unfortunately is too old to have any data for the W212, but it does have better developer mode functions such as trailer recognition.

Question, would Vediamo be more suitable for this task ?

OR, could I add the W212 data to my copy of DAS 2008 and take advantage of the offline coding ? Bit like retrofitting W204 options into newer versions of DAS / Xentry.

I've not tried XDOS yet, but can only assume this won't be much better...

Any help would be appreciated chaps & thanks for reading, as this may help a lot of other folks who want to code their REAR SAM to recognise the trailer module ( in Xentry i think the code is either C550 or 550 ).

Kind regards,

PingPong

[abg17]

vediamo encode it with no problem

[Pingpong]

vediamo encode it with no problem

Thanks bud...

Do I need to look for TM_212 module then ?

Do you have any tips ? As If I can do this, I'll make a "how to guide" for others to follow

Kind regards,

PP

[Pingpong]

Quick update from myself to anyone who cares to read lol

I've learnt a lot over the last day...

Vediamo 5.000 won't talk to my Compact C4 ( c3 ) MUX !

Anyhow... using DAS 09 / 2014 in developer mode just won't cut it, nor did DAS 2011.....

Anyhow, I obtained Vediamo 4.02 & applied the patches, the license ( thanks to some kind souls... )

I as an test ( after having a nosed in Simulation mode ) decide to connect my MUX to the program & did the Caesar update.

Success, it recognises the MUX serial, no issues & then confirms it as part D.

I went into the .cbf library & initially couldn't select what I thought would be the correct module ( say SamR ? )

Anyhow... I let Vediamo do an autoscan ( which is an option ) and I got lots of errors, as it reports ONLY the ECUs it can see.

I then narrowed it down to a valid ECU, when to interrogate it & it's easy to navigate within that ECU selected ( which looks like a GLOBAL ECU directory for the vehicle ).

I then selected say VMAX ( which is a parameter you can't mess up too much ! )

And voila, I can easily change it from say it's default of 250km/hr to say 300kh/hr ( or whatver you are allowed in the drop downs ).

You simply press ECU & it codes it

I've seen the variant coding & this was all valid...

Hopefully I can variant code my mates W212 towhitch ( as it's present ) and that'll work !

I may post a "How to" if anyone is interested ( if it works ).

cheers

PingPong

[Pingpong]

hmmm.


Had mixed results with my friends car...

quick screenshot said "reading codstring failed"  

Pls see attached  

   

Did I forget to unlock the ECU first ?  CR6EU5 sounds like the Engine ECU though.... ???

I was trying to simply add the Trailer module to the Rear SAM or Main Gateway....

Any help appreciated folks ??  

Kind regards,

PP.

:UPDATE :

For anyone who thinks this actually needs coding, it's nonsense, we plugged the vehicle in & guess what, the car recognises the caravan, parking sensors deactivate on reverse, indicators work fine, even the alarm only flashes the car indicators.

So, this problem is solved in so much as coding is irrelevant !!!

I still never got to variant code it, but will find out one day when he's back to let me plug his car in