topblog Ivoire blogs


SD connect C4 PCB rework for Mercedes 24V 12V cars

Have any idea why MB SD connect C4 mux works only with 24V but no connection to 12V?   Customer solution... Here you go.   Try on your own risk!   some of the NEC Chips are Broken 4 PCs and same the small board power chip i Change it and now they work on 12V too i change the first line from left side sd-connect-c4-pcb-rework-1 Replace the chip sd-connect-c4-pcb-rework-2 SD connect C4 china clone with boards of high quality:   mb-sd-connect-compact-4-star-diagnosis-hdd-d-new-pcb-1 mb-sd-connect-compact-4-star-diagnosis-hdd-d-new-pcb-2 mb-sd-connect-compact-4-star-diagnosis-hdd-d-new-pcb-3 mb-sd-connect-compact-4-star-diagnosis-hdd-d-new-pcb-4 mb-sd-connect-compact-4-star-diagnosis-hdd-d-new-pcb-5 mb-sd-connect-compact-4-star-diagnosis-hdd-d-new-pcb-6 Source:   SD connect mux with PCBs above is confirmed to work no issues with Mercedes 12 and 24 volt cars.  

09:40 Publié dans Blog, Shopping, Web | Tags : sd connect c4 | Lien permanent | Commentaires (0)


(Solved) VCM2 clone ok for IDS v96 but NOT ok for JLR SDD

How to get Ford IDS & JLR SDD work perfectly in/with one VCM2 clone… Here is a good case for reference: how to solve if VCM2 clone ok for IDS v96 but NOT ok for JLR SDD.


i have a clone vcm 2 that works ok for ford v96.02

i have installed jlr sdd v139 on an other computer but the vcm 2 is not recognized by jlr sdd program

in the device manager the vcm 2 is shown as ETAS VCI USB RNDIS device

that was after i ran the ford setup prog

before that no driver was installed



Here is a good tip of how to set up files to get VCM2 to work OK with Ford IDS & JLR SDD


if you have 96.02 Working with your VCM2 clone , then take the file from

c:/program files/Ford motor company/IDS/Runtime/Istall3rdparty

(Program files (x86) if 64bit windows


there is folder called ETAS, That is what you need



!!!!!!!!!! Note: sometimes, Ford IDS & JLR SDD cannot work well in one VCM2 unit just because of the firmware version issues. That is, the software of Ford and JLR (Jaguar & Land Rover) has the corresponding VCM2 firmware versions. Software and firmware should be in sync. For example, IDS V86 is compatible with vcm fw: A, and SDD v135 also with vcm fw: A. But if you install IDS v98 for use, then the vcm firmware version would turn B, but the corresponding vcm firmware version remains A, as for SDD v135. The firmware version of IDS and SDD is different. When you convert IDS to SDD, or SDD to IDS, the system would pop up info as below like “VCMII software update”… To ask you to match the firmware with the software.

  ford-ids-with-jlr-sdd (5)

ford-ids-with-jlr-sdd (1)


ford-ids-with-jlr-sdd (2


ford-ids-with-jlr-sdd 3


ford-ids-with-jlr-sdd (4


ford-ids-with-jlr-sdd (5

ford-ids-with-jlr-sdd (4)

So for sake of compatibility, to update software.

For vcm2 units, Ford ids v86 had better work with JLR sdd v135,

ids v98 with sdd v140,


For the vcm unit, it’s not allow to update. It’s a must.


This aricle support by technical serivce:


All goto tool in here


03:33 Publié dans Blog, Web | Lien permanent | Commentaires (0)


2017.03 SDconnect C4 Xentry/DAS Questions and Answers (FAQ)

Here are the most frequently-asked questions from SD connect C4 users and professional answers from engineers working for 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 in 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: SD connect c4 firmware files are lost and WIFI cannot be set up.

A: It means your sdconnect firmware files are deleted and you need update sd c4 firmware.

Files need to update (ORDER!!!!!!):


Sd connect c4 firmware update manual:


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: SD connect 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:


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”



xentry-error-2221-45-solvedQ: 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)



Q: EWA-NET file cannot start.

A: Go to the Start menu, then EWA-NET Admin Tool

In 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


xentry-no-access-authorization-code-solved-1xentry-no-access-authorization-code-solved-2Q: 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 multiplrxer an the

diagnostic unit is interrupted.

The voltage supply at the diagnostic socket (circuit30

and(or) circuit31)is fault.


When using SDconnect, 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 SD C4 software, not C3

If all ok, it may result from the SD connect c4 mux or the cable


09:41 Publié dans Blog, Shopping, Web | Tags : sdconnect c4 | Lien permanent | Commentaires (0)