topblog Ivoire blogs


KTAG 14P600KT06 GPTcable Pinout for DIY users

MED GPT cable 14P600KT06 is necessary to be used with Ktag for Bosch MED17 GPT ECUs reading. So, how to make it your self & how to use it for connection? Here you go.



What is Ktag 14P600KT06 GPT cable:

It is used for BOSCH MED17 GPT ECUs

How to make a Ktag GPT cable yourself:


I take 144300t105 rainbow cable and remake to GPT cable

(or u can use 26 pin connector , may some one will be handful)

for 05 cable:








the pinout


correct pin out of ori Cable 14P600KT06 GPT:

yellow pin3- yellow

orange pin 4-organge

yellow pin 13-green

orange pin 14-white


WARNING: Incorrect or poorly made connections may damage the ECU, often beyond repair. In no event shall we be liable for any damage caused to the ECU by wrong connections. If not equipped with enough knowledge and tech, you’d better spend a bit to buy one and use it with security. Look here:


it was tested a lot:

MED 17.7.2 Mercedes GPT 2015


How to connect & use Ktag GPT cable for MED17 GPT ECU reading:


  • Plug-in 689: MED17.5.2 IROM TC1767



The pins Boot can be found on the right side of the ECU (in red in the picture).

The programming pads where to set the board adapter are located at the bottom right (in yellow).


Material needed:


a.Solder a wire joining the two pins Boot shown in the picture;

b.Solder a wire to pin CNF1 shown in the picture;Ktag-GPT-cable-read-MED17-GPT-4

c.Connect cable 14P600KT02 and cable 14P600KT06 to the ECU connector according to the pinout below:


d.Remove the soldered wires before re-installing the ECU on the vehicle.

09:11 Publié dans Blog | Tags : ktag ecu | Lien permanent | Commentaires (0)


How to online update Xprog 5.5.5 to Xprog Box 5.7.6

This is XPROG 5.5.5 to 5.7.6, software and firmware update internet active


  1. Unzip the zip file, run XProgDestop.exe 
    2. Press the Help -> Hardware Info and update the firmware
    3. Do not press the Update Certificate


Says it works 100%.


But unluckily, i have no luck.


I was thinking about upgrading my xprog box so I thought I would have little to lose by following instructions given to see what happens.

Everything appears to go smoothly see pictures below.

However, you cannot read or write any chips without being locked into a certificate error loop. see pics.

Rolling back to 5.5.5 all authorisations are gone hardware registration ID is blank and unit wont read or write.
xprog-5.7.6-update (1) xprog-5.7.6-update (2) xprog-5.7.6-update (3) xprog-5.7.6-update (4) xprog-5.7.6-update (5) xprog-5.7.6-update (6) xprog-5.7.6-update (7)


So for the benefit, my advice is don’t use this


I finally gave it up and spent some dollars with a new one (Xprog box 5.7.6, it’s from


It adds new authorization:
















Other ECU ->Chrysler-DodgeJeep->BCM-GRAND_CHEROKEE_WK_2014_Flash

Other ECU ->GM ECU->SAF-XC164CS-16F

Other ECU ->HONDA Bikes->CB650F 2015_Code_Flash

Other ECU ->Renault ClioOther ->EPS_ST10F269

Other ECU ->Renault Modus ->ECU_SAK-XC164CS-32F



Xprog 5.7.6 has all authorization:


AUTH-0001 Motorola HC05 family authorization (allows to read/write EEPROM)

AUTH-0002 Motorola HC08 family authorization (allows to read/write EEPROM)

AUTH-0003 Motorola HC11 family authorization (allows to read/write EEPROM)

AUTH-0004 Motorola HC12, 9S12 family authorization (allows to read/write EEPROM and flash memory)

AUTH-0005 Texas Instruments TMS370/TMS374 family authorization (allows to read/write EEPROM)

AUTH-0006 Motorola HC05Bxx and HC05Xxx family bypass security authorization (allows to read/write secured EEPROM and flash memory)

AUTH-0007 ST M35080 authorization. Read/Write/Erase device to delivery state.

AUTH-0008 BMW EWS3 authorization

AUTH-0009 ATMEGA family authorization (allows to read/write EEPROM and flash memory)

AUTH-0010 MB ZGS001 authorization

AUTH-0011 Motorola HC11EA9/E9 bypass security authorization (allows to bypass security bit and read EEPROM and RAM memory)

AUTH-0012 National CR16 authorization (allows to read/write EEPROM memory)

AUTH-0014 ST7, ST10 family authorization (allows to read/write internal flash)

AUTH-0015 MPC5xx authorization (depending on device program automatically detects MPC5xx, M95xxx device type, flash, external flash and configuration memory size)

AUTH-0018 Motorola HC12, HC912, MC9S12, MC9S12X bypass security authorization (allows to read/write secured EEPROM and flash memory)

AUTH-0020 ARM (Micronas, …) Family authorization (allows to read/write internal flash and external serial EEPROM)

AUTH-0021 ARM (Micronas, …) Family bypass security authorization (allows to read/write secured and non-secured internal flash and external serial EEPROM, view/change mileage, Chassis number (VIN), serial number and PIN code).

AUTH-0023-1 MAC7xxx

AUTH-0023-2 XC23xx

AUTH-0024-1 MC9S12Cxx

AUTH-0024-2 MC9S12XE


AUTH-0024-4 MC9S12HA/HY/P

AUTH-0025-1 MPC/SPC5xxx Authorized 11/4/2014


Now, it works perfect:



xprog-box-5.7.6-1 xprog-box-5.7.6-2 xprog-box-5.7.6-3 xprog-box-5.7.6-4
xprog-5.76-HC912D60-review-1 xprog-5.76-HC912D60-review-1



Xentry DAS Developer Mode Manual

Here is MB Star Diagnosis Xentry/DAS Developer Mode User Manual,incl three part:

What you need for Xentry/DAS Developer Mode?

When & why you should use Developer Mode?

How to use Developer Mode step by step?

THE MOST IMPORTANT NOTE: you are trying on your own risk!!!!!!!!

Be very careful when using the Developer functions! Many of them can cause irreversible damage to the components of the vehicle and may cause personal injury! Please be aware that modification to some specific systems (airbags, braking systems) may make the vehicle unsafe for on road use and may violate the local highway laws, rendering the car not roadworthy in the legal aspect.

This is especially true for the SRS modules, where unintentional usage of developer options may cause deployment of airbags/tensioners and other aggressive restraint systems.

IMPORTANT NOTE: what do you need for Xentry/DAS Developer Mode?

- original Mercedes diagnostic tools like Super mb star c3 or HQ clone like SDconnect C4 china clone mux

DAS/XENTRY with good installation

- a laptop running with Windows XP better

IMPORTANT NOTE: why & when should you use Xentry/DAS Developer Mode?

As a presumed DAS user you have probably learned already that there are number of functions that would logically belong to the software options, but they

are missing from the regular DAS installations. These include recoding (variant coding) the control units without SCNs (Software Calibration Numbers), de/activation of commercially sensitive options (in-motion video of tv/dvd), recoding the configuration of airbag units, seat belt reminders, changing the configuration of instrument clusters, restoring damaged EEPROM contents for Comand/APS and other ECUs and many more. There is also an additional benefit: sometimes control units record a DTCs (error codes) that are filtered out by the production software. Developer kit allows unfiltered view on the module's error memory, therefore allowing to see all stored trouble codes, including the masked ones.

The reasons for disabling these functions in the DAS setups seen at the dealership are very simple: firstly, risk associated with using them is too high to open these tools to (very often) under trained and rushing technicians; secondly, there are several legal obligations that put restrictions on what the dealer can do and what he can not - for instance, recoding tv-in-motion, airbags and emission-re lated systems fall into this category. Thirdly, electronically damaged components very often result in replacement, therefore repairing (recoding) would have adverse effect on spare parts revenue.

Here is how to : clean ASSYST Plus Memory

Firstly, you need the mentioned Developer key made according to your LAN ID. Before scrapping your old key, take note of the LAN ID (there are some cases when it changes ie. when reconfiguring the hardware) and the current License Key in the DAS. Both information can be found in the licensing menu of Star Utilities. Then replace your current key with Developer key, save and restart DAS. After selection of vehicle class there should be now a new screen (in German, except V-Series and W221 where it comes in English) informing you about dangers associated with using Developer Kit. You are good to go now.

In Developer mode : (tested version 11-2010)

Steuergerate (Control units) ->F3

Aufbau (Body) ->F3

ZGW (CGW) ->F3

Entwicklungen (Development data) ->F3

Steuergerate - Anpassungen (Control unit adaption) ->F3

Programmieren (Update) von Steuergeraten (Control module programming) ->F3

Steuergerat programmieren (Auswahl) (Program control unit (Selection)) ->F3

Now we have 2 options to flash the ZGW/CGW with, choose the correct one

Don't panic ! if you choose the wrong file , it terminates process and you can do it over again

Confirm Flash pop-up with Ja (Yes)

After that it says : "Das Steuergerate wurde erfolgreich programmiert"

->"OK" it ask for a reset -> JA (Yes) ->

ECU Reset (FN_ECU_Reset) ->F3 again ->F3

Now you Complete full History wipe

Enable Comand DVD/TV in Motion (W211 W219) and OTHERS


In Developer mode :

Audio, Video, Navigation und Telematik ->F3

a screen might pop up with all kind of settings, ignore and press F2

New screen with ESD warning ->F3 COMAND /AUDIO -AUDIO 50 oder COMAND ->F3

Entwicklungsdaten ->F3

Steuergerate-Anpassungen ->F3 Steuergerate-Anpassungen (Variantencoderierung) ->F3

HU Parameter ->F3 scroll down to line: Driving speed is more than 0 kph and

Driving speed is more than 10 kph and BOTH enable them and ->F3 to confirm coding

Now you be able to watch DVD/TV when car is in motion

Uprate the speed limited in a gasoline (ME-series controller) engine control unit

Log on to DAS, connect to the car, select:

Control Units -> Drive -> ME-SFI 28 -> Development Data.

Then select the Control Unit Adaptations -> Explizite Kodierung


This option works quite the same in Diesel engine models, however i found it more difficult to use (quite frequently modules are replying with an error message to the attempt of recoding). I was able to successfully remove the speed limiter on a CDI2 series module from the W210 model and some others as well.


Addrear airbags to the AB control module

Control Units -> Body -> Airbag (AB) -> Development Data -> Control Module Adaptations -> Variant Coding -> Fahrzeugausstatung Kodieren

(the last menu entry can be slightly d ifferent in various module variants)

Select the drop-down list in the field Airbag Hinten Rechts and Airbag Hinten Links – set to YES. Back up to the main Airbag menu, reset the fault codes, cycle ignition, reset fault codes again and cycle the ignition for 2nd time (this step is very important).



Addfog lamps to function as a cornering aid

Select Body, then Driver Side SAM -> Development Data -> Control Unit Adaptations -> Variant Coding -> Abbiegelicht set to ON (“ja”).

Then go to the Passenger SAM (if present, for example in 211/219 model series) and similarly, perform the same coding in the second SAM unit. I have found that quite often cars manufactured prior to year 2003 have the relevant cornering lights option available in the left sam, however right sam is missing it. Not a big problem since these are readily and cheaply available from the second-hand market.

For all the onboard systems to recognize the new function you will also need to recode the CGW or EZS and mark the appropriate factory option in the adaptations.

Hidden error codes

For W211/W219/W230 series with SBC system, go to the Chassis-> Sensotronic Brake Control (SBC) then enter Development Data then call up Fault Codes. Most likely, a car that has been driven for some time will have a code “Event: ABS Bremsung” stored. This Fault/Event is not normally shown in the general menu of DAS – it is being filtered. It actually

does not represent an actual error, just a specific condition (hard braking with ABS activation). You will find many modules that actually filter out some more or less useful fault codes.

This menu is also very useful when evaluating vague fault codes (ie: “Hydraulics fault” in the general version in the developer menu can be drilled down to something more meaningful like “rear left release valve stuck in closed state” – this will come in German though).

Adapting the SRS control unit to a new car (different configuration, different VIN).

First of all erase all present error codes in the unit if possible. If there are current faults the airbag module might not get properly reinitialized.

Then proceed to the menu control unit adaptations -> special functions -> Control Unit is released.

From this point do not turn the ignition off or reset the control module. Proceed to the menu option “initial startup” where the current configuration will be reinitialized and new VIN can be written to the control unit.

Please pay attention to the specified configuration (ie. Does the car have rear side airbags?) otherwise you will end up with a controller that does not recognize airbags installed in the vehicle.

After completing the initial startup, reset the control module (cycle ignition) and erase all fault codes resulting from the startup process.

Extend SBC life


Make sure engine is running !!!

In Developer mode you need to go to Entwickelingsdaten - > ansteueringen -> Gesamstliste aller Ansteuerungen

to see how many times brake has been pressed there is a line that says: Bremsenzahler (DJ_GetBrLive)

then 1 line down there you see Bremsenzahler aktualisieren und Lebensdauerzahler F neu berechenen -> click it !

Parameter uINBR = 0

then click F3

1 line down Bremsenzahler auf beliebigen Wert setzen (DJ_SetNBr) -> click it

Parameter uINBR = 0

then click F3

then scroll down untill you see the line's :

Lebensdauerzahler F neu berechenen (DJ_CalcLiveTime)

Parameter uINBR = 0

then click F3

Lebensdauerzahler F neu berechenen und schreiben (DJ_BuildAndWriteF)

Parameter uINBR = 0

then click F3

Log out of SBC !!

log out of verhicle !!

let engine run at least 10 minutes or drive at least 10 minutes

If no coils are damaged , SBC fault code is not AKTUEL no more

Desactivate seat children and ocuppancy seat in mercedes ml270 cdi


Warning !! Warning !!

After completing this procedure

NEVER use a child seat in this seat again

Warning !! Warning !!


In Developer mode , you have to Disable AKZE in passenger seat.

When you disable this feature, passenger airbag in Dashboard, will work ALLWAYS when crash signal come's from the front of the car , even if no passenger is sitting in this chair . So in an accident from the front, you allways have to buy a new Dashboard + dash airbag as well

Important !!

After you disabled AKZE in SRS unit ,you will notice you can't erase the fault , or another fault came back (fault coding).

To complete procedure , you have to unplug the Yellow AKZE connector under passenger seat, so SRS can't measure anything connected on this input port.

Now you can erase Fault codes in SRS , and your SRS light in Instrumentcluster will go off


Warning !! Warning !!

After completing this procedure

NEVER use a child seat in this seat again

Warning !! Warning !!


Activate this secret function as litres, datum, bigger pictures/symbols of some check controls on all models
like W211




AGAIN! DISCLAIMER: The author takes no responsibility for any damage caused by use of the Developer Kit of DAS. This option is a very powerful tool but must be used responsibly and with extreme caution. If in doubt, please do not blindly try the menu options – several of them will cause EEPROM or FLASH memory damage, requiring the module to be disassembled and reprogrammed using external tools - this is a troublesome and risky operation. Unintentional actuation of components may cause mechanical failures or even risk of fire - please remember, that in Developer Mode DAS will do exactly what you command, all safety checks and interlocks are bypassed!