Mercedes-Benz Forum banner

41 - 50 of 50 Posts

·
Premium Member
Joined
·
440 Posts
Discussion Starter #41
Thanks for that. Still very confusing.

Sorry for this long post but I am getting desperate.

Before I dive in and start changing more things I am trying to understand Implizite Kodierung [=Implicit Coding] versus Explizite Kodierung [=Explicit Coding]. From my observations so far;

Explizite Kodierung in ME28 F4 Stand allows you to select an option from a drop down box which seems to have just the main variables associated with a particular model and engine.
W220 E50 coding options via Explizite Kodierung.jpg
W220 E50 coding options via Explizite Kodierung.jpg

As an example one option for VV220_50 is; VV220, M113, E50, EU3EU4, NAG, VGB, 250 kmh which I have worked out have these meanings:
  • VV220 = vehicle model (note it is V V 220 and not W220)
  • M113 = engine type
  • E50 = engine capacity (eg 5.0L)
  • EU3EU4 = country = Europe
  • NAG = Transmission {Neues Automatische Getriebe} New Automatic Gearbox or 7G-Tronic
  • ART = AbstandsRegelTempomat [Distance rule cruise control] or VGB = ??
  • 250_kmh = maximum speed available
  • PKK ??
  • MRM part of Steering Control Module (SCM)
  • 400, 600, 850W EC Luefter T B = Engine suction fan
This makes sense as explicit means to state clearly and in detail, leaving no room for confusion or doubt.

Implizite Kodierung in ME28 F3 Stand allows you to change any variables associated with a particular model and engine. I believe these were called Kodierung strings in early models and have a reference indicated for each one. As an example and of particular interest re DTR is 0272 bis 0273;
W220 0272 0273 coding data via Implizite Kodierung.jpg
W220 0272 0273 coding data via Implizite Kodierung.jpg

0272 bis 0273 has three variant coding options available;
W220 0272 0273 coding options via Implizite Kodierung.jpg

In detail these are;
  • Bandende, kein ART (Tempomat aktiv) [=End of the tape, no ART (cruise control active)]
  • Bandende, ART (Tempomat nicht Aktiv) [=End of the tape, ART (cruise control not active)]
  • Bandende externe fahrgeschwindigkeitsregelung [=banding external vehicle speed control]
My interpretation of these options is:
  • Bandende, kein ART (Tempomat aktiv) which was the original setting on my none Distronic car and means that no ART (AbstandsRegelTempomat) [Distance rule cruise control] is available and the vehicle has normal cruise control active.
  • Bandende, ART (Tempomat nicht Aktiv) I believe is the correct setting for a car with Distronic fitted and that the normal cruise control is rendered inactive.
  • Bandende externe fahrgeschwindigkeitsregelung I cannot figure out what this means.
This also makes sense as implicit means implied, indirect, suggested etc.

The options for these coding variables may be accessed two ways;
  • Control unit groups > Drive > ME-SFI 2.8 > Control unit adaptations > Variant Coding > Display of coding data > Coding
  • Control unit groups > Drive > ME-SFI 2.8 > Development data > Control unit adaptations > Control unit adaptations (Variant Coding) > Implizite Kodierung
The display of the results is different but I think the results are the same. The next photo is a sample of ME coding variables via Control unit adaptations.
Sample of ME coding variables via Control unit adaptations.jpg

The next photo is a sample of ME coding variables via Development data.
Sample of ME coding variables via Development data.jpg

It looks to me as if you configure Explizite Kodierung in ME28 F4 Stand first you don’t have to change variables via Implizite Kodierung in ME28 F3 Stand. I am going to devise an experiment to test this but I need to be sure I can reverse everything afterwards before proceeding.

This is what it looked like after a successful Explizite Kodierung where I no longer have a blank for VV220 E50.
W220 successful Explizite Kodierung 01.jpg

W220 successful Explizite Kodierung 02.jpg

But it looks as if I got the option wrong as I have found a photo from a year ago which shows my maximum speed as 210Kmph but now after changing my ME to the above model/engine values (Code VV220, M113, E50 etc) via Explizite Kodierung I seem to have a maximum speed setting via Implizite Kodierung of 250Kmph. My conclusion is that Explizite Kodierung has changed all the values listed in the option.

Notice in this photo taken one year ago that 0224 – 0231 = Vmax: 210 km/h.
W220 original coding data via Implizite Kodierung.jpg

But notice in a photo taken one day ago after setting VV220 E50 in Explizite Kodierung in ME28 F4 Stand that 0224 – 0231 = Vmax: 250 km/h.
W220 recent coding data via Control unit adaptations.jpg

I also note two other relevant unintended changes;
  • ME Coding now shows 0202 -0203 = SPEEDTRONIC not present or SPEEDTRONIC functionality in traction system. Recent ME Coding now shows 0202 -0203.jpg
Recent ME Coding now shows 0202 -0203.jpg

Continued in next post due to upload limit
 

·
Premium Member
Joined
·
440 Posts
Discussion Starter #42
Continued from last post.
  • ME Coding now shows 0272 – 0273 DTR present or cruise control functionality in traction system.
Recent ME Coding now shows 0272 - 0273.jpg
What on earth does that mean?

And now that I have written all that down I realise that my main problem is deciding exactly what is the correct configuration for my W220 when the blasted XENTRY just shows blanks (- - - ) after going through the reading process in Explizite Kodierung in ME28 F4 Stand. This was my original blank result.
Blank coding data via Explizite Kodierung.jpg

Fortunately from more old photographs I have established that my original W220 coding data obtained via Control unit ME-SFI 2.8, Control unit adaptations > Variant Coding > Display of coding data was;
  • 0050 – 0062 = Vehicle model : V220 (sic with one vee)
  • 0150 – 0159 = Engine model : M113 E50
  • 0166 – 0167 = SCM [MRM] : FITTED
  • 0202 – 0203 = SPEEDTRONIC : Present
  • 0224 – 0231 = Vmax: 210 km/h
  • 0236 – 0241 = Transmission : NAG2
  • 0272 – 0273 = DTR : Not present
  • 0309 – 0313 = Electric suction fan : 400/600/850W EC (Bosch/Temic)
The first drop down options for a VV220_E50 are shown here as a sample;
W220 E50 coding options via Explizite Kodierung.jpg
I list all of the available drop down options for a VV220_E50 and for a SS220_E50 at the end of this post.

It is an easy process to weed out the options which come close to matching my original data which is presumed to be (remember I haven’t ever seen it in a read out).
  • Original: VV220, M113, EU3EU4, NAG, ???, 210_kmh, ???, MRM, 400_600_850W, EC, Luefter Bosch/Temic
And I am left with these possible options;.
  • Option A: VV220, M113, EU3EU4, NAG, ART, 250_kmh, PKK, MRM, 400_600_850W, EC, Luefter T_B
  • Option B: VV220, M113, EU3EU4, NAG, VGB, 250_kmh, PKK, MRM, 400_600_850W, EC, Luefter T_B
  • Option C: SS220, M113, EU3EU4, NAG, VGB, 210_kmh, PKK, MRM, 400_600_850W, EC, Luefter T_B
The conclusion from all of this is that there is no match with my original set although option B comes close with 250Kmh instead of 210Kmh and assuming I have VGB and PKK whatever they are.

Option A is the best match for an option with ART in the values. This is the option I used above which now gives me a new set of errors.

Why do I feel like I am just digging a deeper and deeper hole?

Maybe a ME ecu upgrade will solve all of these issues.

Regards,

Brian

Just for the record I list all of the options
VV220_E50 has twelve options.

VV220_M113_E50_oKat_NAG_ART_250_kmh_PKK_MRM_600W_DC_Luefter_Temic_1131530479_1131530079

VV220_M113_E50_oKat_NAG_ART_250_kmh_PKK_MRM_400_600W_850W_EC_Luefter_T_B_1131530479_1131530079

VV220_M113_E50_oKat_NAG_VGB_250_kmh_PKK_MRM_600W_DC_Luefter_Temic_1131530479_1131530079

VV220_M113_E50_oKat_NAG_ART_250_kmh_PKK_MRM_600W_DC_Luefter_Temic_1131530479_1131530079

VV220_M113_E50_oKat_NAG_VGB_250_kmh_PKK_MRM_400_600W_850W_EC_Luefter_T_B_1131530479_1131530079

VV220_M113_E50_EU3EU4_NAG_ART_250_kmh_PKK_MRM_600W_DC_Luefter_Temic_1131530479_1131530079

VV220_M113_E50_EU3EU4_NAG_ART_250_kmh_PKK_MRM_600W_DC_Luefter_Temic_1131530479_1131530079

VV220_M113_E50_EU3EU4_NAG_ART_250_kmh_PKK_MRM_400_600_850W_EC_Luefter_T_B_1131530479_1131530079

VV220_M113_E50_EU3EU4_NAG_VGB_250_kmh_PKK_MRM_600W_DC_Luefter_Temic_1131530479_1131530079

VV220_M113_E50_EU3EU4_NAG_VGB_250_kmh_PKK_MRM_600W_DC_Luefter_Temic_1131530479_1131530079

VV220_M113_E50_EU3EU4_NAG_VGB_250_kmh_PKK_MRM_400_600_850W_EC_Luefter_T_B_1131530479_1131530079

---

And SS220_E50 has seven options;

R220_M113_E50_EU3EU4_NAG_VGB_210_kmh_PKK_MRM_600W_DC_Luefter_Temic_1131530479_1131530079

R220_M113_E50_EU3EU4_NAG_VGB_210_kmh_PKK_MRM_400_600_850W_EC_Luefter_T_B_1131530479_1131530079

SS220_M113_E50_EU3EU4_NAG_VGB_210_kmh_PKK_MRM_600W_DC_Luefter_Temic_1131530479_1131530079

SS220_M113_E50_EU3EU4_NAG_VGB_210_kmh_PKK_MRM_600W_DC_Luefter_Temic_1131530479_1131530079

SS220_M113_E50_EU3EU4_NAG_VGB_210_kmh_PKK_MRM_400_600_850W_DC_Luefter_T_B_1131530479_1131530079

SS220_M113_E50_ULEV_05_NAG_210_kmh_PKK_MRM_400_600_850W_EC_Luefter_T_B_1131530479_1131530079

---
 

·
Premium Member
Joined
·
440 Posts
Discussion Starter #43
I am back again seeking more help understanding ME Variant Coding using DAS.

In trying to get my Distronic configured I set a new ME (Motor electronics) code using Explizite Kodierung just as Brenton did in his video referenced above. I chose a code that had ART in the string and that closely matched some old photos that I took a year ago of my then existing ME Code settings.

BTW it is absolutely essential that you record all your original settings because once changed there is no way to know what they are meant to be without consulting your records. Fortunately modern phones make it easy to photograph the SDS screen at every step.

After successfully unlocking the ME ecu and then saving the Explizite code for a VV220 E50 I decided to read out the new ME code settings and compare them with my old photos. I noticed that about six variables had changed by themselves. So my previous conclusion was correct that configuring the ME ecu by means of Explizite Kodierung is just a convenient way of setting multiple values in one go.

Problem was that some of the new values were obviously wrong when compared to my old photos and I obviously picked the wrong VV220 E50 option. However a detailed inspection of all the available options including VV220, SS220 and R220, shows none match my old data perfectly. So obviously when the car was manufactured or at some time later the values have been changed manually using Implizite Kodierung.

Here are a few examples of how OLD changed to NEW [with brief English description].
  • 0100 bis 0145 Baureihe V220 changed to Baureihe C220 = V V F 220 (Pullman) [Vehicle model]
  • 0198 bis 0199 Motor-Code E/A 2, Crash-Signal ueber CAN changed to Motor-Code E/A 2, Crash-Signal ueber HW-Leitung [Crash signal : Signal via hardware line or CAN]
  • 0202 bis 0203 Motor-Code E/A 2, var.Geschw.begrenzer ein. Changed to Motor-Code E/A 2, var.Geschw.begrenzer aus. [SPEEDTRONIC not present or SPEEDTRONIC functionality in traction system]
  • 0236 bis 0241 Fahrzeug – Code, Getriebeausstattung = NAG2 changed to Fahrzeug – Code, Getriebeausstattung = NAG [Transmission : Automatic]
When selecting a code to use via Explizite Kodierung, this is all that you have to go on;
VV220, M113, E50, EU3EU4, NAG, ART, 250 kmh, PKK, MRM, 400 600 850W EC Luefter T B.

I explained what these mean in an earlier post but here they are again for convenience.
  • VV220 = vehicle model
  • M113 = engine type
  • E50 = engine capacity (eg 5.0L)
  • EU3EU4 = country or pollution = Europe (Note oKat means without catalytic converter)
  • NAG = Transmission {Neues Automatische Getriebe} New Automatic Gearbox or 7G-Tronic
  • ART = AbstandsRegelTempomat [Distance rule cruise control] or VGB = ??
  • 210_kmh = maximum speed or Vmax.
  • PKK ??
  • MRM (part of Steering Column Module (SCM))
  • 400, 600, 850W EC Luefter T B = Engine suction fan
Consequently manual coding of each variable one by one via Implizite Kodierung is the way to go.

Every time I start the Implizite Kodierung process I see a Note “At least one coding setting is invalid. Check and correct coding settings.”

My questions; Is this important or can it just be ignored until a “proper” fault/error appears?

Anyone have any experience in correcting coding errors?

TIA Brian
 

·
W220 Moderator
Joined
·
5,658 Posts
Hi Brian,

I am following this, not ignoring you, I've just not got anything useful to offer without being there and going through it with you :(
However ................

Don't know if you are aware, but it just might help ...............

Here's how to get a better translation from Developer German to English ..............

Get the SDS into ME, "Version Coding", Screen Shot or photo and then Print it, it's all in English, and in the left Margin are the "line option numbers", now go into developer, same numbers on the left, but all text in German, Print these as well, now sit the pages side by side and there is your translations 😉

HTH, Cheers
 

·
Premium Member
Joined
·
440 Posts
Discussion Starter #45
Thanks Dave that is worth remembering although the translation via Google is very good.

Because I have a long trip coming up and the S-Class is so nice to drive compared to our C-Class I decided to reverse everything I had changed in the last two weeks. Everything went well with no faults in DAS and no malfunctions on the Instrument Cluster and I now have cruise control back and speed limiter which are essential for long trips.

Feeling very pleased with myself I went for a drive and found something is wrong with the CC and Speed Limiter. I need to set them at 117 Km/h for them to work at 60 Km/h, ie a factor of 1.9 difference. The speedometer is spot on as is the average speed in the statistics mode on the ICM.

I can live with that at the moment until I have more time to investigate. There is obviously a setting wrong somewhere. Any ideas much appreciated.

One website showing a heap of Tips and Tricks for using DAS explains how to reset the ICM so I may try that.

A maybe related issue is that I noticed in my old photos taken in August 2018 that settings;
  • 0001 bis A017 changed from "Dynamic wheel circumference Rear Axle VV/V220 255/60-16 U=2.111" to "Dynamic wheel circumference Rear Axle VV/V220 255/45 R18 U=2.152"
  • 0018 bis B029 changed from "Dynamic wheel circumference Rear Axle VV/V220 255/60-16 U=2.111 AMG V/VV220 C215 245/45-18 U=2.10" to "-" (Blank)
  • 0030 bis A046 changed from "Dynamic wheel circumference Front Axle VV/V220 255/60-16 U=2.111" to "Dynamic wheel circumference Front Axle VV/V220 255/45 R18 U=2.152"
  • 0050 bis 0062 changed from "Dynamic wheel circumference, Front Axle, VV220 255/60-16 U=2.111 AMG V/VV220 C215 275/40-18 U=2.11" to "-" (Blank)
Without all the words;
  • 0001 bis A017 Rear 255/60-16 -> 255/45 R18
  • 0018 bis B029 Rear 245/45-18 -> Blank
  • 0030 bis A046 Front 255/60-16 -> 255/45 R18
  • 0050 bis 0062 Front 275/40-18 -> Blank
Which is really strange as the rear tyres are smaller than the front, which is stupid!! I have triple checked the values as shown above.

My actual tyres are asymmetric;
  • Rear 265/40 R18 which is close to 0050 bis 0062 Front 275/40-18 (NB. An Internet Tyre Comparator shows a speedo error of 1Km/h at 70Km/h.)
  • Front 245/45 R18 which matches 0018 bis B029 Rear Blank
Yesterday when I reset all the ME codes via Implizite Kodierung there were no options available for my tyre sizes so I left the setting at the above settings ie Rear: 255/45 R18 and Blank and Front: 255/45 R18 and Blank.

It is almost as though the coding descriptions are the wrong way around ie Front should be Rear and vice versa and maybe my CC/Speed Limiter error is due to the Blanks.

Oh well another step forward and half a step backwards!!
Regards Brian

PS Just for the record here are the same coding readouts via Development data > Implizite Kodierung (results in German) whereas the above were obtained via Control unit adaptations > Coding (results in English).
  • 0001 bis A017 changed from " Dynamic Radumfang Hinterachse, Low Byte, VV/V220 255/60-16 U=2.111" to " Dynamic Radumfang Hinterachse, Low Byte, VV/V220 255/45 R18 U=2.152"
  • 0018 bis B029 changed from " Dynamic Radumfang Hinterachse, High Byte, VV/V220 255/60-16 U=2.111 AMG V/VV220 C215 245/45-18 U=2.10" to "-" (Blank)
  • 0030 bis A046 changed from " Dynamic Radumfang Vorderachse, Low Byte, VV220 255/60-16 U=2.111" to " Dynamic Radumfang Vorderachse, Low Byte, V220 255/45 R18 U=2.152"
  • 0050 bis 0062 changed from " Dynamic Radumfang Vorderachse, High Byte, VV220 255/60-16 U=2.111 AMG V/VV220 C215 275/40-18 U=2.11" to "-" (Blank)
Which match the English readout exactly, ie Hinterachse = Rear axle and Vorderachse = Front axle
 

·
Premium Member
Joined
·
440 Posts
Discussion Starter #46
One step forward and none back today so here is an update.

I managed to fix my cruise control and speed limiter error. ( had to set 200 Km/h for the car to cruise at 100 Km/h.) It was obviously caused by a wrong entry re my tyre sizes in the ME ecu. This was caused by me using Explizite Kodierung to set a particular vehicle in the ME ecu. But I now know that Explizite Kodierung automatically sets multiple variables and unless you have a good record of your original setting, it is extremely difficult to determine what got changed. Thank goodness I had photos of all my settings from one year ago. My recommendation is DO NOT use Explizite Kodierung in DAS for anything.

Just to demonstrate how clunky the DAS programme is, I find it necessary to try to set a value in Implizite Kodierung first, which then produces the error message: “Communication error 8.561.6067”. This means the ME ecu is locked and unavailable for coding. I then go back and unlock the ME ecu via the page Control unit ME-SFI 2.8 with title Steuergerät entriegein (DJ_Zugriffsberechtigung [=Control unit unlocked (DJ_Access authorization]. This time if the request to unlock has worked you will see; Result: Zugriff erlaubt, Funktionen freigegeben =[Access allowed, features enabled]. Unlocking the ME ecu first before coding a variable doesn’t work. The ecu seems to require at least two goes at unlocking it. I put this paragraph here for the record and it will only make sense if you have tried to do any ME coding and seen this error.

Now back to the issue. Once I had used Implizite Kodierung and coded the blank fields produced by Explizite Kodierung my CC and speed limiter errors went away. However it took me twenty goes at getting the codes to be saved successfully. The ME unlocking problem kept reappearing as described above, the engine definitely must be running for code changes to be saved properly as a couple of times I forgot and then had to repeat the whole process of trying a change, unlocking the ecu making the change, saving the settings which is a real pita. To top it all off some of the tyre option descriptions do not make sense and in fact I think are plain wrong. The available options in the 0001 bis A017 Rear field space do not list the wider tyres used on my car but the wider tyres are listed in the 0030 bis A046 Front field space. That is they are listed the wrong way around!

The amazing thing is that I don’t think it matters. It now seems to me that the only thing that matters is the ‘U’ value associated with each option.

These are my original settings from (August 2018) and latest settings (today August 2019) with my actual tyre sizes shown in braces (curly brackets).
  • Coding reference -> original setting -> latest setting -> {actual tyre size}
  • 0001 bis A017 -> Rear 255/60-16 U=2.111 -> 245/45-18 U=2.10 -> {245/45 R18}
  • 0018 bis B029 -> Rear 245/45-18 U=2.111 -> 245/45-18 U=2.10 -> {245/45 R18}
  • 0030 bis A046 -> Front 255/60-16 U=2.111 -> 275/40-18 U=2.11 -> {265/40 R18}
  • 0050 bis 0062 -> Front 275/40-18 U=2.111 -> 275/40-18 U=2.11 ->{265/40 R18}
My observations;
  • My original tyre settings did not match my actual trye sizes but I have been very pleased with how accurate my speedometer has been in the past.
  • I couldn’t select my actual rear tyre sizes of 265/40 R18 as they are not listed in the options even though they are shown on the car's door plate.
  • Notice how the wide tyres are shown as being on the Front (Vorderaschse) and the narrow tyres on the Rear (Hinterasche) which is rubbish.
  • All the latest U values match my original values closely and I think that is why the speedometer, CC and speed limiter still all closely match the indicated speed shown in my smart phone GPS App. The displayed speed is within 0.0 to 0.5 Km/h of my actual speed (GPS).
  • I now plan to inspect and record all the available U values in Implizite Kodierung regardless of the tyre sizes and then test how they affect the displayed speed v GPS speed. Just by casual observation I have seen U = 2.10, 2.11, 2.111, 2.15, and 2.152 so it will be interesting to see how changing the U value changes the displayed speed. Could be a way of trimming the speedometer to be more accurate.
The bottom line is that I have now got my car back to how it was before I started fiddling with DAS and that I understand the foibles of DAS much better. The downside is that I have yet to get my Distronic working and I have a long trip coming up.

Brian
 

·
Registered
Joined
·
2,400 Posts
If I remember correctly, there is an option in the dash info panel to change the tire sizes. My assumption was that was to allow the owner to change the tire sizes on the car, then enter the corrections without needing DAS.
 

·
W220 Moderator
Joined
·
5,658 Posts
Yes, but the Dash Codings and settings do not relate to the ME Codings for total wheel circumference, they are there for stuff like the Torque limitations and proper intervention from ESP etc 😉
 

·
W220 Moderator
Joined
·
5,658 Posts
The more I think about it, the more I think those settings may have been in Comand unit for the Navi System, I certainly don't have them in my Cluster
 
41 - 50 of 50 Posts
Top