Tag Archive: MB STAR Diagnostic Tool

Benz eCOM DoIP Description

eCOM DoIP Multiplexer for Benz is a diagnostic tool that can replace Xentry Diagnosis VCI. Benz eCOM DoIP works with Xentry, Vediamo & DTS Monaco and support DoIP for latest E and S series.

Many customers confused between Benz eCOM DoIP and Mercedes SD C4 when purchase, CnAutotool would like to share the difference between the two tools and help you get a better idea which one to choose.

Benz eCOM DoIP Description:

1. Supports DoIP protocol

2. eCOM Box Hardware Serial number starts with 2xxxxx

3. Works with Xentry, Engineering programs Vediamo and DTS Monaco.

SD C4 Description:

1. Software Version: V2019.05

2. Hardware Version: OS:2.3 CSD:2.11

3. Support Wireless / Lan Cable Connection.

how – to – update – handy – baby

Conclusion:

eCOM DoIP: Main for new vehicles, cannot use for DAS\HHT vehicles. K-Line communication may not so stable, need specially setup on any diag sw installation.

SD C4: More popular and universal for Mercedes vehicles. The only limitation is K-Line communication in Vediamo from ver5* Easy to setup. In most cases work as is.

Many thanks for your attention. If you have any better ideas or advice, please comment below. We will check and reply you as soon as possible

 

How to use Xentry DAS on AVDI passthru?

What is the AVDI recognized by Xentry?

Xentry Passthru is different from from regular Xentry openshell. Xentry passthru does not use SDconnect toolkit. When you launch the program it will give you a dropdown where you can choose which J2534 device

How to use Xentry Passthru?

If you got the Xentry Passthru installed, there is a tool which will do the dirty work for you.

Normally it is not linked or doesnt have desktop shortcut but resides (at least in my installation)
under

C:\Program Files (x86)\Mercedes-Benz\xentry\bin\SelectPTDevice

IF you have installed your passthru (would that be AVDI or anything else) with correct drivers, registry entries etc it will just present you with list of options and you select your VCI from dropdown list.

Heard good things about AVDI J2534 compatibility (real thing, don’t know about clones) so it shouldn’t be a big deal. Recently i have tried to use BOSCH KTS560 as passthru and it works perfectly okay.

For curiosity, i did also test the 20-euro MiniVCI that gets normally bundled with Toyota techstream packages. to my surprise it also works albeit slow and sometimes freezes the application. This one can be actually made to work even with old DAS like 2009, 2012….it’s just matter of proper settings in cal.ini and slave.ini

For DAS/Xentry users:

Old thread – but do not run the SetPassThruDAS.exe, as it was written for DAS/Xentry for Windows XP, and not Openshell or Xentry Passthru. All you need to do is install a fresh OS (Windows 7 Enterprise x86 or x64 SP1) ideally on a physical laptop, connect the AVDI device to the USB port and run the SetupInterface_yourserialnumber_PASSTHRU_xxxxxxx.exe and Next through the setup process. If you have a current version of the Passthru software, you will see a grayed out option for installing drivers for DAS that you cannot select, but do not be concerned about that. It will detect the AVDI, and install the appropriate J2534 dll files in the Windows\System32 directory. Then continue installing your Passthru software provided on the Blu-ray from Daimler. It will take a while to install, and once it verifies your hardware ID and installs your StartKey, launch Xentry Passthru from the icon it creates, and it will prompt you first thing as to what interface you want to use. You will see Abritus72 AVDI PT (your serial number here) in the drop down box. Select that device, and that is all their is to it. Xentry should automatically communicate with the vehicle.

How to use Sdconnect C4 do Online SCN Coding?

What you can find here:

1. SCN coding compatible hardware SCN connect c4

2. How to use SCN connect c4 to do SCN coding

3. 2. SCN coding importance

1. Question: can clone MB SD C4 support Mercedes online SCN coding?
The answer is yes. Newest MB SD C4 2019.03V / 2018.12 can perform online SCN coding perfectly as long as you have online software account or buy one-time SCN coding service.
mercedes-benz-2019-3-01

Image: MB SD C4
mercedes-benz-2019-3-02

Image: Xentry 2019.03V

Source of SCN coding account:
Source 1: MB Online SCN Coding / Online programming 1 Year Account

$2,299

Source 2:

$85
One-time service
1. ) After ordering this service, prepare MB sd c4, car, laptop and TeamViewer.
2.) Send Teamviewer ID and Password to customer service
3. ) The engineer will access to your laptop to authorize SCN coding function.
4. ) After finish, the system will display “The SCN coding sequence has been completed successfully”.

mercedes-benz-2019-3-03

2. SCN coding importance

The move to SCN coding was *very* important. There are too many configuration items in every ECU now to have someone set options by hand whenever an ECU is changed, or to understand how changes on one device have to be done on other devices. These cars are really very very complex, and unlike your laptop, if something goes wrong can result in fatalities.

There are software dependencies between different ECUs, and actually loading software into ECUs is now needed regularly – and thus so is up-to-date diagnosis equipment and up-to-date firmware disks too. A simple example is an Audio system. If you update the firmware in the COMAND unit the firmware in every other MOST device needs also to be compatible (if you want it to work reliably) and thus they all need firmware updates. If you change one component then all components need to be updated to be properly compatible.

The latest equipment even now uses ethernet to load firmware into some ECUs (so it takes 20 minutes not 20 hours).

Without SCN coding it would take considerably longer to change any control unit, would result in mistaken configurations, and thus the cost of repair (or re-repair) would go up and up as systems got more complicated. SCN coding basically allows the correct configuration to be loaded into the car.

Imagine what could/would happen if you had to “hand code” the airbag controller after replacing it? Would you trust all of your airbags to work after the local mechanic had to set all the options correctly? I certainly would not.

Your comment that “The capital cost of the latest version, plus the monthly subscription, means it is beyond the reach of many smaller independent garages” is just wrong.

If your garage has the skills to deal with the technology (and i’d argue that if they don’t they shouldn’t be doing complex things with the newest vehicles), then it is completely affordable.

If you want to work on older cars, then most independents seem to use a clone machine and use it for limited things.

The EU competition commissioner has previously taken a good look at this market and enforced rules that mean diagnosis equipment (for newer vehicles) is available at sensible prices. This is not true in the rest of the world. Mercedes diagnosis systems in USA are more expensive, and in the far east (and I think Australia) are not available at all to independents.

Sorry to be so contradictory, and in summary, but without SCN coding there would be misconfigurations and un-reliability – possibly dangerous to life – occurring quite regularly. And if you are going to need to work on newer cars, there are very affordable Xentry diagnostics systems – you just need to talk to Mercedes.

SDconnect C4 DAS Fault (1.2)-2.503.9901 (customer solution)

Phingoc in trouble:

The laptop is a Dell D630 with a china SD Connect 4.
Xentry 03/2012
DAS 03/2012

It was all working fine last i used the machine.

So.. I connect the MUX to the car (smart 451), and then the lanwire to the mux and computer. Then i turn on the ignition.

In xentry i choose Smart -> 451 -> Diagnostic -> Das opens
in das: Identify car by control unit. After a few seconds some update thing appears and disappears followed by an error.(see att.) Fault (1.2)-2.503.9901. Cannot connect to car.

DAS-Fault-(1.2)-2.503.9901图片一张
Doesnt work with wire or wireless.

Please help me.

Rocinante Wrote:

Delete the 3 “update” folders in C:\program files\SDconnect toolkit (or rename them).. then perform a repair of your SDNetControl by pressing Start\Programs\Service\Setup SDNetControl .. it will start up and ask what you want to do, select repair.. let it do its thing and then go back and delete/rename the update folders in C:\program files\SDconnect toolkit then REBOOT when its done… that should get you up and running.. it is VERY important to REBOOT after deleting the update folders!!!

Phingoc feedback:

Thank you verry much! Big Grin that fixed the whole problem.

start laptop
Rename update folders
Run setup SdNetControl
The “repair” option wasnt displayed, but it went straight into instalation. No options, but it went automaticaly to instalation :S
Reboot after instalation

Re-delete or Rename update folders after running SDNC setup

Delete setings from the MUX
Reconfigure SDconnect
Start Xentry/das and it worked straight away. Big Grin

Benz eCOM DoIP vs. MB SD Connect C4 Diagnostic Scanner

Look here: What’s the difference between Benz eCOM DoIP diagnostic tool and MB Star diagnostic Mb Star C4 multiplexer?
Benz-eCOM-DoIP-vs-MB-SD-Connect-C4-Diagnostic-Scanner

In summary,

New car: eCom DoIP
eCom – laboratory\development tool. Most cheap and light. Can’t be used with DAS\HHT vehicles. Need luck with kline communication. Need to be specially setup on any diag sw installation.

Normal: Clone SDConnect C4
SDConnect – workshop\robust tool. Most universal in use. The only limitation is kline communication in Vediamo from ver5* Easy to setup. In most cases work as is.

Good to know:

Actia eCOM DoIP Box Multiplexer Kit supports DoIP for the latest E and S series, and it’s perfect for Mercedes COMAND NTG5, NTG5s1, NTG5s2, NTG5.5

ECOM is the diagnostic and swipe communication interface used by daimler-benz’s production and r&d department. It supports the after sales diagnostic software Xentry, Vediamo, and the Monaco DTS, the exclusive development software, with higher access rights than SDconnect (C4).

ECom supports the CAN/DoIP network, which CAN be used for the diagnosis and brushing of new car audio and video entertainment systems. Vediamo for Mercedes engineers is an engineering software used by Mercedes engineers to develop diagnostic software, that is, Xentry and DAS now in use is developed based on Vediamo and delivered to general after-sales dealers. For this reason, using the Mercedes super engineering version is open to all diagnosis /coding/retrofit/flashing programming features. It is possible to add or reduce SA codes freely without going through VEDOC(the process of the original factory applying for modifying the equipment code), so as to achieve the purpose of modifying the vehicle equipment, such as adding SA500 electric rearview mirror.

Xentry and DAS Developer mode, commonly known as: exploit data engineering version after 2010, has added many restrictions on functions. Therefore, people may encounter that the vehicle version is too new to enter the control unit, or they cannot make any special modifications after entering the control unit. For example, the w204/212 2012 meter may need to be configured in the regional language, or turn on other convenience functions.

The database of diagnosis /coding/retrofit/flashing for the Mercedes engineer version USES the Xentry database, so the Mercedes engineer version is dependent on the Xentry version. As long as the database is new, the Mercedes engineer version can use the V4.00 version on the new model, and compact3 & SDconnect does not support the ODX document. The latest V5.00 supports ODX files with eCom. It is recommended to use eCom with DoIP function, which is faster and more stable.

How to make Xentry PassThru work for New Models (Euro5/6, W205, W213, W222)

Something good to help you to make Xentry PassThru on Windows 10 x64 support new Mercedes models (Euro5/6, W205, W213, W222). Done with VAS5054A PassThru Driver
Xentry PassThru needs to be installed on Windows x64 to support new models, such as Euro5/6, W205, W213, W222 … However, VAS5054A didn’t work on 64bits as passthru. There is 64bits device driver for VAS5054A but there is no PassThru driver working on 64bits. You may try Actia driver instead but this is a patched 32bits PassThru API files with 64bit device drivers working on Windows 10 x64. Xentry recognizes it and works with W205 (confirmed), etc.
WARNING: Use it on your own risk, only for test purpose.
What you need:
(1) VAS5054A Bluetooth hardware. (genuine and good clone… both ok)
(2) (option) VAS5054A EDIC_PDU_API 1.20.4x driver installation file. You can find it somewhere on this forum.
(3) (option) New firmware. The firmware included here is version 1.20.41 for better compatibility, not 1.20.42.
(4) Softing_VAS5054A_PassThru_Driver_x64_v3.zip (attached here)
(5) 64bit Windows 10
(6) (option) DC 12V power adapter, 2 jumper wires for temporary power.
Pre Installation:
(1) Install Xentry PassThru and do all patches.
(2) (option) Install EDIC_PDU_API 1_20_42 driver (or EDIC_PDU_API 1_20_41). It’s for installing .NET framework or VC++ redistribution files.
If you are going to do clean install on fresh Windows 10, you might want to install the EDIC_PDU driver first. It installs .NET framework, VC++ files, some EDIC DLLs on /Windows/System32 or SysWow64. Other files will be overwritten by the below manual installation.
Installation:
(1) Copy “Program Files (x86)\Softing\*” to your HDD “C:\Program Files (x86)\Softing\*”
(2) Copy “Program Data\D-PDU API” to your HDD “C:\Program Data\D-PDU API”.
(3) Double click on “Softing_VAS5054A_PassThru_1_20_042.reg” and install it.
(4) Make a shortcut of “SftngCM.exe” on Desktop.
(5) Right click on “C:\Program Files (x86)\Softing\EdicDriver\win7\softingedic7_ntamd64.inf” and install.
(6) Connect the VAS5054A hardware using an USB cable. Connect it to a temporary power(12V DC adapter) or OBD-2 port.
(7) Check “Control Panel/Devices Manager/Softing…”. If not installed correctly, update the device driver manually.
(8) Make a shortcut of “EDICConfig.exe” on Desktop.
(9) (option) If you have newer version than EDIC_PDU_API 1_20_42 driver and genuine VAS 5054A hardware, you may install the API driver now.
Post Installation:
(1) Connect the VAS 5054a to a temporary power(12V DC adapter) or ODB-2 port.
(2) Run “SftngCM.exe” on desktop as administrator. Make a “C:\Temp” directory if not exists. This is for saving log files. If not exists, SftingCM.exe will cause error when doing test.
(3) Choose “VAS5054A” and type the serial number (maybe 0821xxxxx).
(4) Select “Test” and click on “Start Test”.
– RED dot : PC <-> VAS5054A does not communicate. Something wrong on your driver.
– YELLOW dot : PC <-> VAS5054A communicates.
– GREEN dot : PC <-> VAS5054A <-> Vehicle communicates.
Tip:
(1) “.NET Framework 2.0/3.0/3.5” needs to be installed if not installed automatically. You can install it by selecting on “Control Panel/Programs and Features/Turn Windows features on or off/.NET Framework 3.5(includes .NET 2.0 and 3.0)”. You also need to install VC++ redistributions if not done yet. (MSVCR100.dll, mfc100.dll, … errors)

(2) Temporary power to VAS5054A for test purpose : Ground to either pin 4 or 5. 12V DC to pin 16.

(3) You can upgrade the EDICDriver in “Program Files (x86)\Softing\EDICDriver” if you have newer version. Update the device driver on control panel.

(4) If you installed newer version EDIC_PDU_API driver than 1.20.42, edit the *.reg and change the number 1_20_42 to your number (for example, “EDIC_D_PDU_API_1_20_042” to “EDIC_D_PDU_API_1_20_0XX”). After editing, double click on it and install it again.

(5) If your device has different serial number but SftngCM.exe doesn’t allow the change, edit the *.reg file with text editor, double click on it and install it again.

How to

Download:

Softing_VAS5054A_PassThru_Driver_x64_v3.zip

My findings MB Variant coding tweaks & throttle delay

4-1

[[I am copying this post from the one I made on CnAutotool as well, I figure both forums should see it, especially considering MrScott belongs to this one!]] This post assumes you have some knowledge of the software used. I’m not entirely comfortable making a full walk-through for beginners, as this is potentially risky.

After spending quite some time tinkering with and learning about Mercedes Benz Diagnostic Tool, I believe I’ve almost completely solved my issues with throttle lag on my car. Since owning the car I’ve noticed that depending on how the car is driven, like through heavy traffic or on country roads, the throttle response to the gas pedal does not seem to stay consistent. For example, if I start off driving the car in stop and go traffic, the pedal seems to become “lazy”; next time I mash on the gas, there’s a very noticeable delay in throttle input and sometimes the car doesn’t shift down when it should, either in C or S mode. It was quite annoying, and on a few occasions, kind of risky. Aside from that there’d be a very noticeable difference in the way the car performed on a day to day basis, sometimes it felt sluggish, and other times it felt pretty quick. I really didn’t like how it was unpredictable.

This is discussed in a threads like this, and it appears that ECU adaptations are the cause for this. I’m sure the adaptations would be effective in some cases, but where I live and how I drive, the adaptation process seems to have a difficult time calibrating the throttle response, and the result has been pretty undesirable to me. It seems others have the same issue, and have tried solving it doing the simple TCU reset. This reset does work, very temporarily. Every time I tried it, it’d help for a few drives but then it’d revert to sluggishness. I went over 10,000km after pulling the car battery and doing the TCU reset to see if the car needed a long time to “learn”, and it did improve, but the inconsistency/unpredictability of the throttle input, and delay, still remained an issue.

I’m very glad to have spent the money getting a diagnostic multiplexer, as it’s allowed me to learn quite a lot about how these cars operate. On top of that, I’ve done a bunch of tweaking to get things to how I’d like. If you have access to one, or know someone who does, the following tweaks have solved these problems for me. This could likely be accomplished in Xentry rather than Vediamo, but I was unable to get access to the necessary settings through Xentry myself. I Please note, I have no idea the effect this will have on warranty, as my car is completely out of any warranty..

MrScott52, a very helpful member of Benzworld posted a youtube guide on how to enable a few parameters to increase responsiveness of a diesel variant in an earlier version of DAS; these tweaks seem to make a difference with my 2.5L V6 M272 w204 as well. (I’ll link the video in a following reply.)

Attached below are the necessary parameter changes for the ME 9.7 ECU in Vediamo, which solved my issues with throttle delay (many listed in MrScott52’s video), and here are the descriptions of each:

#1 (Lastschlagdaempfung) This is the most important one. This parameter seems to be the main culprit for the inconsistent feeling throttle response and sluggishness, and I believe it causes the wonky throttle bodyadaptations which I find so awful. Disabling it has removed most, if not all delay in throttle input. It is referred to as “load-reversal damping” in Vediamo (german), but it is the “Throttle Change Damping” parameter in Xentry. I changed this parameter about a month after the others, and it definitely had the most significant impact on throttle response, and now the throttle is very consistent in performance. I believe this parameter is more directly related to the actual throttle body than the gas pedal, unlike the next parameter.

#2 (Pedalkennlinie) This is the pedal curve parameter. My car had KLD4 as default. You can play with this, and possibly leave it at KLD4. However, I changed it to KLD2. From what I understand, KLD2 is meant for cars with a manual transmission, and as such, I’d expect the pedal curve to be the most “natural” feeling to the driver. In contrast, I believe KLD4 is more responsive, but “jumpier” (more erratic in terms of throttle input). Combining KLD4 with disabling the throttle change damping parameter may be undesirable in terms of comfort/consistency.

#3 (Momentenbegrenzung) This is the torque limit parameter. The main effect I’ve observed from disabling this is that the car doesn’t reduce throttle/torque as much while cornering anymore, and the car seems to accelerate slightly faster from a standstill than before. May not be necessary to fix throttle delay, but I find it favourable.

#4 (Momentenerhoehung Getriebe) This parameter is supplementary to #3 . Like MrScott describes in his video, it allows the engine ECU to monitor torque output and send it to the transmission, but keeps it within safe/comfortable limits. I find this parameter to improve gear shifts very slightly; torque input and acceleration remains very steady throughout gear shifts. I believe it very slightly improves acceleration, even compared to only having the torque limiter disabled. Do not change this to the GSG setting. Doing so resulted in some very uncomfortable shifting. I’m not sure if there’d be a long term effect on the gearbox here, so just don’t as a precaution. The Benz diagnostic tool highlighted in black is the default setting – the ECU is not allowed to increase torque to the gearbox depending on measurement.

With all these parameters changed, I have my car performing the way I’d like it to. It’s performance remains far more consistent, there’s significantly less throttle lag, and it does actually accelerate faster (I’ve measured), but only very slightly. Starting off in C mode on an incline also no longer feels like as much of a strain. Now, all of this being said, if you have the tools and such to do this yourself, or know someone who can, you do so at your own risk. I’ve driven over 10,000km already without any negative effects of this, but I just don’t want to be responsible if anything goes wrong. I can’t imagine anything would, though. If you are willing to do this yourself, please be aware that there are many ecu parameters that are difficult to understand, and modifying them at all could potentially cause irreversible damage. I do not recommend making adjustments to any other unknown parameters without thoroughly researching their function and/or purpose.

p.s the screenshots were taken in simulation mode, I didn’t think to screenshot anything while I was actually connected to my car. The highlighted values are still of course relevant.

Attached Images

1 Throttle Damping.jpg
4-1

2-Pedal-Curve

4-2

3-Torque-Limiter

4-3

4-Torque-Increase-Allowance

http://www.cnautotool.com/category-172-b0-MB+Star+C4.html

MB SD Connect C4 firmware v2.30 Update Guide

1. Prepare 6 AA5 batteries according to Instruction for how to install MB SD C4 Batteries.
Note: Please do use brand new batteries with sufficient electricity; otherwise, you will fail to update the firmware.

Then, select the green cable to connect to your laptop and MB SD Connect Compact 4 diagnostic multiplexer, and use OBD cable to connect to Mb Star Connect C4 multiplexer and your vehicle. (If the vehicle cannot be connected, select OBD 12V power instead.)

2. Open the software “2012.09 DAS”.
Go to C:\ program files \ SDconnect Toolkit to check whether there are the three following files as the pic below shows.
Update_automatic;
Update_manual;
Update_Special.
If the files’ names are different from the pic shows, please correct the names the same as the pic shows.
Mb Star C4 with EVG7 Tablet

14-1

3. Restart your computer.

4. Start to update the firmware according to how to update MB SD connect4 MUX.

2016 MB Star SD Connect C4 Hardware and XENRTY DAS FAQ

Here are the most frequently-asked questions from MB Star diagnosis SD connect C4 diagnostic scanner users and professional answers from engineers working for CnAutotool Hopefully, it helps those in trouble.

Q: How to change the Xentry language?
A: Go to Setup, select Setting language, then choose a language and click on Accept.

Q: How to setup the DAS language?
A: Go to DAS Properties. In the Target, change the last two letters (which is the first two letters of the language). Then click on OK.

Q: Xenry language error: A fault has occurred.
A: Change the PC date and time to be the same as the Xentry version.E.g. Your Xentry is version 2015.09, you need set up 2015.09.05 on your PC.

Q: Fault (30.3) pops up after DAS activation. No valid DAS license; DAS will now be closed.
A: Go to local disk C:/programme files/Mercedes-Benz/StartKeyCenter2; find our StartKeyCenter.exe.
If DAS doesn’t expire, just change the bin file in C:/programme files/Mercedes-Benz/DAS
If DAS expires, you need Lan-id to activate DAS

Q: Xentry cannot run, the icon displays then disappears.
A: Change the PC date and time to be the same as the Xentry version;
If it does not work, replace the bin file in C:/programme files/Mercedes-Benz/DAS (the bin file differs from Xentry versions)
If all above fails, send the Mercedes software hard disk to the vendor to re-copy files.

Q: Mb Star C4 firmware files are lost and WIFI cannot be set up.A: It means your sd connect firmware files are deleted and you need update sd c4 firmware.
Files need to update (ORDER!!!!!!):
02_CSD_2_10.zip
01_Boolimage_2_3.zip
03_PmPic29_Cpld23.zip
Sd connect c4 firmware update manual:
Step 1: Install battery
Step 2: Change file name
Step 3: Update SD Connect C4 firmware

Note: please prepare new batteries and an OBD cable for use; if it fails to connect to the vehicle, replace it with the OBD 12V power; otherwise, it would pop up error 662 (update fails.)


Q:  MB STAR SDconnect Tool kit appears Error 749 in Administration.Due to network problems, no connection to the SDconnect can be establish (749)No SDconnect is selected or the desired SDconnect cannot be selected
A: It results from incorrect IP setup. Please go to the network connect to WLAN set up IP: 172.29.127.119

Q: Xentry error 2221-45: No access authorization code![2221-45] No access authorization for XENTRY diagnostics was found on the server. You must contact the user help desk.
A: Go to C:/programme files/Mercedes-Benz/Xentry/fusoko/eclipse/plugins; delete the file “com.damler.xentry.diagservice_1.6.0.201607181047”

Q: Xentry cannot open for use even reopen Xentry or restart the PC after activation.No access authorization code! You must contact the user help desk.
A: Go to C:/programme data/LicDir; delete lic-key2.dat
Open StartKeyCenter on Desktip; activate Xentry
Get a new lic-key2.dat after Xentry activation; copy and paste lic-key2.dat; then rename it as “lic-key2.x4711” (setup the file properties to Read Only)

Q: EWA-NET file cannot start. HTTP Status 500-Servlet execution threw an exception.
A: Go to the Start menu, then EWA-NET Admin ToolIn EWA Admin Tool, Server, EPC, WIS all should start (if they have started yet, pls. stop and restart)Server, EPC, WIS restart, reboot the PC, then open EWA-NET to login


Q: Xenry Error (1.2)-2.503.13003:Initialization of diagnosis multiplexer failed
Possible causes:
The link between the diagnosis multiplexer an the diagnostic socket is interrupted
The link between the diagnosis multiplexer an the diagnostic unit is interrupted.
The voltage supply at the diagnostic socket (circuit30 and (or) circuit31)is fault.

Note:When using SD connect c4 multiplexer, check the connection status using the Toolkit.
A: check the connection of the cable and the car;
Then check the wired&wireless IP setup
Then check the Mercedes software; it’s MB SD C4 software, not Star C3
If all ok, it may result from the SD connect c4 mux or the cable

BIG THANKS to engineers at cnautotool.com.