Tag Archive: MB STAR

Rent Mercedes-Benz Online SCN Account

Rent SCN code to access user name and password.

The link

You can rent login name and password monthly or annually. You can also enter it in turn (through team viewer).
Calculating Radio Anti-theft PIN Code
Online Enabling FBS4 Key

Mercedes-Benz-1 Mercedes-Benz-2

scn coding meaning:

Software Calibration Number coding, short for SCN coding is intrudes by MB around 2005. It replaced the previous coding technique with a centralized and almost automated technique to prevent incorrect coding being selected when replacing a module.

scn online coding instruction:

Here is the online SCN coding guide.

Configure MB STAR:
Come to “SDnet Control” menu>> Configuration >>Network: workshop cable network>> Place a checkmark next to “Automatically obtain IP address”
To check the active Internet connection, select Star Browser. The registration window for the after-sales platform should open. Enter the Service Name and password if request.
Connect MB STAR diagnostic system with vehicle
Start STAR DAS software program
Select Benz model and make: Vans>>V-Class >>Sprinter>>Model designation>>Vehicle recognition. If the vehicle is not recognized, enter the required data manually (e.g. Germany, Rest of World)
Entry for retrofits and modifications – Select “Online” (“networked Star Diagnosis device”)
Change or enter the vehicle equipment codes: + ED5 (PSM installed), – ED8 (PSM preinstallation).
NOTE: If the vehicle does not have a preinstallation (ED8), ED8 does not need to be changed to ED5.
Run a Quick test
Come to the EIS (electronic ignition starter switch) control unit>> Control unit adaptation >>SCN coding >>Select the “Online (networked Star Diagnosis unit)” menu option
SCN coding will start automatically (visible on the progress bar on the screen). Please strictly follow the STAR diagnostic software instructions. Otherwise the control unit may be destroyed during the coding procedure.
When the system display a comment “The coding variant has been changed”, the SCN coding is completed. The parameterization has been completely taken over in the EIS and is thus finished.

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.

V2019.05 MB SD C4 Connect Software Released!

MB SD C4 Connect Compact software has newly update to V2019.05 in www.cnautotool.com.

Latest version: V2019.05

Support languages: English, Croatian, Czech, Danish, Dutch, Finish, French, German, Greek, Hungarian, Italian, Japanese, Korean, Polish, Portuguese, Romanian, Russian; Spanish, Swedish, Turkish, Chinese.

V2019.05 Software Xentry Display:

MB - SD - C4 - Connect - Software - Released!

V2019.05 Software includes:

Xentry 05.2019

DAS 05.2019

EPC 11.2018

WIS 11.2018

SDmedia

Vediamo

Vediamo Database

Star Finder 2008 & 2016

PL73

DTS

05/2019 Mercedes Benz Das Xentry Software New Features:

Update some Benz System data

Fix bugs.

How to update?

You should buy the newest hard disk to update.

Hard disk link:

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

(Solved) SD connect C4 NOT Connected via LAN or WIFI

Here are optional solutions for those with a Sd connect C4 but cannot be connected via LAN (or wifi).
Operation system: Window 7
Static IP: 172.29.127.xxx
Battery: the 6 batteries are installed, fully charged

Error message:
when I connect it to the MUX (the 6 batteries are installed) it tries to connect but it gives up after a minute or two and I have a yellow triangle over the network icon in the taskbar.
The display on the MUX shows that its number is 00, it also displays a cable icon and a countdown timer and the message “Device not in use”
SD connect C4 NOT Connected via LAN or WIFI

The display doesn’t show the wifi option, only the cable icon.
When I start SDConnect Administration Toolkit it says the MUX is not cable accessible.

Possible solutions from users:

Option 1: LAN adapter
Open it and check the LAN adapter soldering if it gone loose

SDConnect relies on broadcasts/multicasts (like the DHCP protocol) to discover SDConnect devices.  They can be con completely different subnets and be “detected” but you cannot interrogate or configure them until you get their IP addresses configured for basic management setup.

Option 2: Toolkit
For Connection you´ll need the Toolkit.
WLAN is not seen until configured, if you reseted the SDConnect you´ll need to reconfigure it with the Toolkit.

Option 3: Battery
You may try forcing your NIC in your laptop to 100Mb/Full Duplex, as many will default and negotiate to 1Gb/s, which I don’t believe some of the SDConnects talk over too well.

Also, FWIW, I have been getting an error 750 when trying to communicate to the SDConnect recently.  The connection seems very unstable. I have only used a direct Ethernet connection.  I have not investigated it very much, but I have resorted to the C3 for right now, which has never failed with 1.2012.
I reset it back to factory settings as well.  I have not had an opportunity to investigate it to any extent, so I am unsure what the problem may be, but SD NetContol is stating a Network Error to the SD Connect. It is all connected via CAT6 and no WiFi.
It is best practice to remove the batteries form the SDConnect when not changing firmware or leave them in there?  I have quality rechargeable batteries I use and typically leave them in when changing firmware, but I have left them in for a longer period.  When I removed the first set, the batteries clearly leaked but didn’t appear to damage the SDConnect and I throughly cleaned it and it has worked since them. For more information,please visit our website www.cnautotool.com

6-1

How to Slove MB SD C4 Cannot Access OBD2 Port

​When using china clone mb sd connect compact 4 Multiplexer, it could not link to the car computer, MB SD Connect C4 offered a message, saying like “check cable connection / turn ignition on”. Then tried again, clone SDconnect compact 4 multiplexer cannot access OBD2 port

According to customer’s feedback that he failed to access to the diagnostic OBD port when tried to use sd connect c4 read errors code from Benz SRS system. The system prompted an error message “check cable connection/turn ignition on”.
Possible Reason:

The error lies on the SD Connect C4’s battery.
​Solution from CnAutotool.com:

1) Check and record your MB SD Connect C4 multiplexer battery
2) Hook up a digital multimeter to set it to the direct current
3) Get two t-pins and plug them into the OBD socket at PIN 5 and PIN17 position
4) Put your positive lead to PIN16 and negative lead to PIN5.
5) Write down the voltage on the digital multimeter
6) Check if the voltage you from PIN16 and PIN 5 is same in step 1.
7) Find the light green wire with a blue tracer band of PIN10 of the OBDII connector.
8) If the voltage differs in step 1 and step 6, the problem is probably with your battery.
9) If the battery is damaged or broken, please replace your battery.

MB SD Connect C4 C5 Xentry Start Key Activatio

MB SD Connect C4 C5 Xentry Start Key Activation

Here is the steps to teach you how to activate XENTRY:

Step 1: Double Check the icon name ” ConfigAssist” which on the computer desktop.

Step2: Select ” SDconnect”

Step3: Select ” Configure”.

Step 4: Select the icon as picture.

13-4

Step5:

Step 6 and 7 :

Step 8 , 9 and 10.

13-7

Step 11: Successful to Activation MB SD Connect C4 C5 MB Star Diagnostic Tools
13-8

If you are interesting in buy MB Star Diagnostic Tools , Please contact our sales via www.cnautotool.com

Clone Xentry Connect C5- Good & Bad Things

I bought “Original Clone Xentry Connect C5” from China’s retail store in 2017/12.

Good thing:

1. Unlike bad products of mercedes diagnostic tool C5 type C4 motherboard, texture is good
2. DoIP specification

Bad thing:

1. Because it is VM system + 32bit, the reaction is slow (SSD though …)
2. Vediamo can be used, but feeling like driving with DELL D 630 (unsuitable)
3. The DTS Monaco software is installed but the connection with the vehicle is NG (currently retail stores and manufacturer engineers are thinking about how to fix it)
4. Passwords are applied to each drive, making it hard to customize
5. Retail shops and manufacturer engineers lack knowledge (take time to support)

My thoughts

I think purchasing this product is still early.

There are too many trouble elements.

I’ll report it when the situation changes.

What I currently use (stable and comfortable)

New car: eCom (64 bit)
Normal: Clone SDConnect C4 (64 bit)
Old car: Star C3

Best regards

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

Solution about MB STAR C4, MB STAR C5 Update and can not test vehicles problems

Make sure your computer hardware version is higher the Car Diagnostic Scanners Tools mb star c4 or mb star c5 version, otherwise, CSD will show update failed . Bootimage can update successfully. The following picture show how to check the mb star c4 or mb star c5 version1
3-1
The following picture is show your computer hardware HDD software version66
3-2
If their software is not same, it no need update ( because factory has upgraded the latest version of the mb star c4 or mb star c5 machine)

If customer not use our HDD software, it will appear read vehicle failed problems.

Solution as following

(1) Mb star c4 or mb star c5 supply power to confirm the machine was turn on, like the following picture ( If now show the three icon, it means the mb star c4 or c5 main unit is broken)

3-3

(2). connect LAN with computer, confirm computer IP change to172.29.127.118, like the following picture :

3-4

(3)  change of software using pattern (Because you modify the software for the firmware upgrade mode, the software is not test the vehicles)The following picture is show the software is upgrade mode

3-5

The following picture is show test read vehicle mode.
3-6

Three files name Update_automaticx , Update_manualx ; Update_SpecialxThis is read vehicle mode, if can not read vehicle, please change files name, then restart computer