2015.12V SD Connect C4 offline programming aborted solution

One of the user feedback that he had problem to carry out offline programming by using MB Star diagnosis 2015.12V DAS. Here is the error analysis.

Problem:

He has ordered the Setting Up Offline Mode In Old DAS service to open offline programming function. He uses SD Connect C4 2015.12V DAS software.

After open the authorization, he then access to control module programming, but the DAS display error message “The procedure was aborted by the user”

Reason:

Offline programming requires to work with old DAS pre-2014.7. Newer DAS will not perform offline programming.

Sorry, you have wasted your money.  Please DO contact the technician before you order online/offline programming service.

http://blog.mbstartool.com/2016/11/09/2015-12v-das-procedure-aborted-when-do-offline-programming/

V2015.9 up MB Star C3 Mux Initialization Failed Solution

Here is the mbstartool.com engineer solution to MB Star C3 V2015.9 up DAS Xentry multiplexer initialization failed problem.

Error message:

Initialization of diagnosis multiplexer failed.

Possible causes:

The link between the diagnosis multiplexer and the diagnostic socket is interrupted.

The link between the diagnostic multiplexer and the diagnostic unit is interrupted.

The voltage supply at the diagnostic socket (circuit 30 and (or) circuit 31) is faulty.

Note:

When using SDconnect,check the connection status using the Toolkit.

Solution:

1. First check if you use the correct software for Star C3 not SD Connect C4, you do not modify software by yourself and it passes self-test.

If all these are okay, replace the Config file in c:\program\mecredes-benz\config

Config file

https://mega.nz/#!vhFEXBiL!jeFN5y38eCEH3ZitnQ2lvOGKBn3hJTWb4KsZ70I537k

2.If still not work, check device and vehicle communication

3. Otherwise send your MB Star C3 and software back to repair.

http://blog.mbstartool.com/2016/11/08/mb-star-c3-v2015-9-up-multiplexer-initialization-failed-solution/

SD connect DAS Fault (1.2)-2.503.13011 Solution

It’s a customer solution to Mercedes MB Star diagnosis DAS fault (1.2)-2.503.13011 error. Here is what he talked about the SD connect error and the solution helps.

I have two SD connect c4 multiplexer here and both show me the same problem. Fault (1.2) 2.503.13011

Error message:

Initialization of diagnosis multiplexer failed.

Possible causes:

The link between the diagnosis multiplexer and the diagnostic socket is interrupted.

The link between the diagnostic multiplexer and the diagnostic unit is interrupted.

The voltage supply at the diagnostic socket (circuit 30 and (or) circuit 31) is faulty.

Note:

When using SDconnect,check the connection status using the Toolkit.

How to solve DAS fault (1.2)-2.503.13011:
1. Go to c:\program files…\mercedes-benz\DAS\bin

2. rename gbf folder to gbf_ori

3. copy the 07-2016 gbf to the DAS\bin

Attachment:

Gbf.rar: https://mega.nz/#!MxsByaLA!jh-jRUBKKcI84FALLPn9Ax8hK3kN2tcT4cUsM_CXbwE

http://blog.mbstartool.com/2016/11/07/sd-connect-c4-das-fault-1-2-2-503-13011/

2016.9 Xentry fault occurred when change language

2016.9 MB Star diagnosis Xentry “A fault has occurred”  error solution.

Q: When I change 2016.9V Xentry software language, it displayed an error message “A fault has occurred”

A: Change laptop time/date to 2016.09.05.

http://blog.mbstartool.com/2016/11/04/2016-9-xentry-a-fault-has-occurred-when-change-language/

How to install MB Star HHT-WIN on Win7 32-bit

It’s an instruction on how to get Mercedes MB Star diagnosis HHT-WIN software work on Windows 7 32 bit system. Enjoy. Info below is shared by users. Try at your own risks.

HHT-Win FOR WINDOWS 7 32-BIT ITS WORKING.

Can’t make HHT-Win work under x64 win 7

HTTwin of XDOS work in 32bit only:
win7,
win8,
win10

It’s for XP in old xentry(12_2015-01_2016)
Setup for HTT-WIN working:

COPY HHT Folder :C:program files>Mercedes-Benz>hht
and folder HHTwin in userdata,>config>hhtwin

and change slave=PARTT2
HHT WORKING GOOD

I run the SD connect C4 both on Windows XP(Xentry) & Win7 32bit (XDOS)(with HHTWin12.2015) .
Running Xentry on Win7 32 bits without HHTWin limits one seriously. cant go into specific ML modules without HHTWin . It sucks……32bit is so much faster………..
The speed workaround is using SSD’s. It’s like HTT-WIN 2015.12 from mbstartool.com. If you are new to this, i recommend to buy SSD with pre-installed software. (will avoid lots of issues)

http://blog.mbstartool.com/2016/11/01/get-hht-win-work-on-windows-7-32-bit/

How to make Starfinder work on Windows 7 64-bit

Have spent a few hours trying to combat Mercedes Benz MB Star diagnosis StarFinder on Windows 7 x64 operation system. Googling… reading… And i found a simple way. Hope it works for you too
Instructions are vary simple….

NO NEED for CAD/SVG viewer software to be installed, too view wiring diagrams

so far tested on following versions 2008/v2/2010/2015/2016

Steps to run St finder using Internet Explorer 11 or 10 with Windows 8 and 7

1) Visit http://facinfo.okstate.edu/floor-plans.aspx and select a building ANY ANY ANY ANY

2) You receive notification at the bottom of the browser window to install �Autodesk WHIP ActiveX Control for IE.

3) You will be prompted with a Windows User Account Control dialog to authorize the installation.

Click Yes

and now you are done !!!!

4) Starfinder is ready for use.

    It downloads whip.cab and then places files in following folders\@WINDIR@\Downloaded Program Files\

whip.inf

whip.ocx

\@SYSWOW64@\

dllongw.

dllgdifontw.

hdigdiw.

hdiheidiw.

dllmtlw.

dllrblastw.

hdiszbw.

hditexturew.

dllwhipcrak.

wavwhiptkw.dll

Crack ST Finder 2016 can be received from http://www.mbstartool.com/

http://blog.mbstartool.com/2016/10/31/get-starfinder-work-on-windows-7-64bit/

DAS not recognize all ECUs through 38 pin cable solution

DAS is working perfect on any car with the 16 pin cable and Xentry also is working perfect. But when DAS is connecting with the w210 car through 38 pin cable, DAS only recognize 3 ECUs then nothing, i changed the 38pin cable gives me the same result.


i used windows7 ultimate x64bit with Xentry openshell 5.2016, all patches and fixes are applied.



I changed the old cable with another HQ 38 pin cable, but the same problem!

tried on different car, same problem,
same car tested on old system (MUX MB Star C3 + Windows XP) works perfect



HHT-win system, simply a message said:" HHT-WIN is not available on this system"
but as per the photo only few ECUs are detected, then nothing....





User suggestion on this topic:

Depends on which W210 it is facelift or pre-facelift with FBS3 or older system? For facelift version have to working shortest through DAS. Pre-facelift version/older model is automatically switched to HHTWin. For example as I remember W168 model year 2003-2004? /I forgot/ is full short test in DAS and then if you click on some ecus then is switched to HHTWin. Facelift W210 model have to working full short test in DAS. This is not HHTWin problem. Maybe your hardware have problem with connection to older cars.



Professional advice from mbstartool engineer:

It’s normal. DAS / HHTWin does recognize some ECUs only through 38 pin cable. And there is not ECUs in old cars as many as new cars.



On a side note, no need 38 pin cable if obd connection is ok

http://blog.mbstartool.com/2016/10/24/solved-das-not-recognize-all-ecus-through-38-pin-cable/