Reasons for CGDI MB“Load File Failed, error code: 27E1”

Here’s the issues for CGDI MB key programmer error: “Load File Failed, error code: 27E1”

Possible reasons that cause the error:

1).  Device fell on the ground and damaged

2).  Take apart the CGDI main unit manually

CGDI Prog MB host is equipped with an encrypted battery. If you disassemble the programmer, the encrypted battery will power off automatically. Benz Monster software refuses to run properly.

What’s more, the battery cannot be purchased separately nor installed by yourself.

The ONLY solution is to send CGDI back to repair.



Always read CGMB label and directions carefully before beginning use.

For more details , please feel free to contact us directly ,



How to Use CG100 Prog to Read & Write 93C66 Chip

Here show you a test report on CG100 Prog read and write 93c66 chip.It is very convenience and fast to operation.

What you Need?

CG100 Programmer

CG100 ATMEGA Adapter


Install 93C66 chip on EEPROM adapter,and install EEPROM adater on ATMEGA adapter

How - to - Use - CG100 - 1

Connect ATMEGA adapter to CG100

How - to - Use - CG100 - 2

Run CG100 software,and click “Programmer”

How - to - Use - CG100 - 3

Select “Serial Flash”àSelect “93C66”

How - to - Use - CG100 - 4

Click “Read” button to read

How - to - Use - CG100 - 5

Reading succeeded
How - to - Use - CG100 - 6 How - to - Use - CG100 - 7

And before operating writing,please save the original 93C66 data file on you compute in case data damaged.

How - to - Use - CG100 - 8

Now we change digits from 00000000 line to 00000010 line to “00”,then click “Write” button to start writing

How - to - Use - CG100 - 9 How - to - Use - CG100 - 10

Writing succeeded

How - to - Use - CG100 - 11

After then you can try to read the 93C66 data again to check if the writing operation successfully.

How - to - Use - CG100 - 12


CGDI MB OBD adds New Keys to Mercedes 2000-2019

Look here: CGDI MB key programmer reviews and tests report on Mercedes 2000-2019


CGDI MB reviews collection:

Part 1: CGDI MB and Mercedes all keys lost

Part 2: CGDI MB and Mercedes spare key add

Part 3: CGDI MB and Mercedes FBS4

in detail…

Part 1: CGDI Porg MB and Mercedes all keys lost

2009 W164:

W164 EIS type all keys lost possible only after 2009

2012 W212:

Work really good!
W212 is from 2012
Read ezs About 30mins
Upload data
Password given

Read eis info
Paste key password
Then key calculation

Part 2: CGDI MB Programmer and Mercedes spare key add

2000 G500:

BENZ G500 year 2000
Just done a Benz G500 imported from Dubai

2004 W203:

W203 2004 spare key making:
Total time about 13 minute when beginning to programming new key. Read pass NEC key by IR and calculate PSW
Key still working after get PSW.
Done in car.

2004 W203:

W203 2004 spare key making takes about 13 minute when beginning to program a new key.

Read pass NEC key by IR and calculate PSW
Key still working after get PSW.

2004 W211:

W211 2004 year add key ,10 min job!

2005 W203:

Class C W203 2005 adding key on car.
Spare key made in under 10 minutes.

2006 W164:

ML350 W164 2006: Read EZS, add key, write BE key all done in 17mn.

Really fast and i’m happy with the first try on car. Use late software
I just plug in the OBD, put key and turn ignition ON and read.

After this step, CGDI will ask only put in EZS and in CGDI.

Just all. PSW query is more longer than 209, about 12mn to get PSW.

2007 W221:

Add Key on W221 2007, i was complete in ~12min. CGDI is very fast
Upload collect data after 2 or 3 min show me PW

2007 w221:

Add key on bench
First try I use VVDI MB
But 2 time upload also failed cannot get pass
So I was change device CGDI from VVDI
1 time upload successful
Good and very fast 10min got pass

2008 W219:

Add key also 15mn OK

2009 W164:

2009 W164 ML450
Key add work
Cgdi 15min
Very good speed!!

2009 W164:

w164 after 2009
I did for testing 2 types of programming _ have got EZS with both programmed keys because customer claimed sometimes EIS works sometimes doesn’t – I have found that connector for immo aerial was desoldered from PCB so when I fixed it – EIS became fully working again – and then I started testing CGDI and made 2 types of programming (all programming on bench – EZS + GATEWAY EMULATOR)
1) programming in case one key is available and adding spare key – ALL OK!
2) programming in case of ALL KEYS LOST – ALL OK!

spare key programming was pretty fast
AKL scenario takes circa 80minutes to get data from EIS and You have to plug in and out emulator key every 5 seconds – I have bought VVDI POWER ADAPTER to pass all hassle on to adapter so You don’t have to watch whole process and move key in and out manually – but it doesn’t work with CGDI – seems adapter works only with VVDI MB and software drives it by adressed pin to switch connection off and on between ezs and key emulator – maybe CGDI TEAM could write a code to their SW and make VVDI POWER ADAPTER useful for all their customers.

2010 W207:

C300 W207 2010 spare key without problem and in 2 minute

(exiting key is BE, so no need server query PSW)

2010 W204:

W204 2010 adding key on bench
Total time about 15mn.

2014 W246:

W246 2014 FSB3: Add key successful in 15mn

2017 W906:
generate a password in Sprinter W906 2017 year.

Part 3: CGDI MB and Mercedes FBS4

No tool can do FBS4 key?

No.  With genuine xentry and daimler fbs server.  Makes FBS4 every day via OBD very fast and easy.

Diagspeed announced the dates of FBS4 solution. But not confirmed yet. The Diagspeed has the reputation of being the best in the Mercedes world to make keys, Reset ECU’s and trouble shoot problems that a normal scan tool can not.  It is worth to take a gamble.

CGDI MB can read FBS4 keys and knows if it’s in a working status or key is damaged

VVDI-MB-TOOL-full-package-2 VVDI-MB-TOOL-full-package-3


CGDI MB is a good Mercedes key programming tool, as good as VVDI MB TOOL.

It can do a lot for Mercedes like key programming, EIS/EZS functions, key data generation, infrared key abilities, etc.

And it covers many models, including

Obd mode:

W164 / W216

W164 / W221 (-2009)

W16 / W197 / W212 / W212 (old)


W172 / W204 / W207 / W209 / W211

W202 / W203 / W208 / W210 / W463 / W639

Platform mode: (quick collect)

W164 / W216

W164 / W221 (-2009)

W172 / W204 / W207 / W209 / W211

W202 / W203 / W208 / W210 / W463 / W639


Note: More will be updated here…

How to Repair Mercedes W211 Rolling Code with CGDI MB?

How-to: repair Mercedes W211 original EIS rolling code with CGDI MB MB Benz key programmer.
Rolling code :
A rolling code (or sometimes called a hopping code) is used in keyless entry systems to prevent replay attacks, where an eavesdropper records the transmission and replays it at a later time to cause the receiver to ‘unlock’. Such systems are typical in garage door openers and keyless car entry systems.
Why need repair W211 rolling code?
Most of keys are too fast to be inserted and removed,  the track code does not roll, resulting in code rolling, so the key and the EIS cannot be matched properly. CGDI MB has the ability to repair Mercedes rolling code.
Tools required:
Analog key data collector
OBD connector
USB cable
Follow main steps below:
1. First you need a key password
2. Calculate the track code of the key
3. Read the EIS, fill in password and save data
4. Calculate the erase password and erase it
5. Load the EIS data with the password
6. Click “Allow modification of data”
7. Change the track code of the key position to the track
code of the key.
8. Write data
9. Learn key
Step-by-step procedure:
1. Read key password. If there is no key,you can calculate the password by doing all keys lost
Calculate password
2.Calculate the track code of the key. Press Read Key/Chip and read current key information
Fill in the password

Click to get the track code
Confirm that the key has been inserted into the CGDI MB and check that the key password is correct.
The track code calculated by the wrong password is invalid.
Calculate key track code success
3.Read EIS, enter password and save data
4.Calculate the erase password ad erase the EIS.
cgdi-mb-repair-w211-rolling-code-12 cgdi-mb-repair-w211-rolling-code-13
Press Wipe the EIS to erase EIS

Insert the CGDI Prog IR adapter into the EIS within 30 seconds.
Erase EIS success
Read EIS and check current status
The EIS is erased
5. Press Load EIS data to load  saved data previously with key password
cgdi-mb-repair-w211-rolling-code-19 cgdi-mb-repair-w211-rolling-code-20
View the key position (key position is 1) and copy the track code
Click on Allow data modification
7.Modify the track code of the key position to the track code of the key
8.Write the EIS data
Recommend to write the VIN first, then write the EIS data
Insert the IR adapter into the EIS within 30 seconds
Write EIS data successfully

Read EIS data to check current key status

Insert the original car key into EIS to learn key, the EIS can be activated

Insert the key, wait 1-5 seconds, the ELV responds,  the EIS is activated and the key learnt successfully
Read EIS data again

W211 EIS original rolling code is repaired by CGDI MB successfully.

CGDI MB ajoute Benz ancienne clé Kline W202 W208 W210 via OBD

CGDI MB ajoute l’ancienne clé Mercedes Benz K-line clé de programmation. Voici le guide sur l’ajout de nouvelles clés au w202 w208 w210 kline MB voiture à 38 pin de 1997 à 1998 via OBD (clé de voiture d’origine)


Nouvelle clé à programmer


étape 1: Calculer le mot de passe
Connecter l’CGDI avec un ordinateur portable et un véhicule
Ouvrez le logiciel CGDI MB


Aller à EIS-> Read EIS data
Sélectionnez Computer Password-> Copy key with key-> Collect data


Suivez les 7 étapes ci-dessous pour collecter des données
1. Insérez la clé d’origine dans EIS et appuyez sur OK
Ceci est un EIS k-line, le fonctionnement est différent de l’EIS ordinaire.


2. Insérer la clé dans l’CGDI et attendre la collecte.
3. Insérez la clé de voiture dans les EIS 10 et retirez-la.
Assurez-vous que la clé est en position ON et que vous allumez instantanément. Si vous n’avez pas réussi à le faire, tirez l’?il et essayez à nouveau. Appuyez sur OK pour continuer.
4. Insérer la clé dans EIS


5. Retirez la clé pendant 5 secondes, puis insérez-la dans EIS.
6. Insérer la clé dans l’ICDG MB.
7. Enregistrez les fichiers générés


8.Enregistrez le fichier avec succès. Téléchargez les données pour calculer le mot de passe.

Télécharger les données avec succès. Appuyez sur Résultats de la requête pour calculer la réussite – terminé


Copiez et collez le mot de passe dans la zone du mot de passe de la clé EIS, puis enregistrez-le.


Sélectionner Generate EE->V051-> Load EIS file


Télécharger le fichier EIS que vous venez de sauvegarder -> Appuyez sur Generate Key File -> The key
le fichier a été généré avec succès

Aller à Read/Write Key->IR —>read the key/chip




La clé intelligente choisit le format 41, la clé commune et le format BE Key.
Ecrire le succès clé.
Sélectionnez un fichier de clé et écrivez-le


écrire laclé avec succès


Testez la nouvelle clé. Fonctionne bien

CGDI Prog Key Programmer read BMW CAS3 ISN by OBD

Here is the easy steps to read BMW CAS3 ISN by using CGDI Prog BMW MSV80 key programmer via OBD.


Connect CGDI Prog Key Programmer with laptop and vehicle (shown as picture below)


Open CGDI Prog software on desktop

Select BMW Read DME ISN function



Click on Read CAS ISN


Reading data

Please remove the key from the ignition


The CAS ISN data was read successfully.

CGDI Prog MB Read EZS, Calculate Password, Write Erase Key W220

Finally receive the Tool, CGDI Prog MB Key Programmer! Wait of DHL express!

Customer experience today:

W220 2003 facelift

Mercedes SL 2006 AMG

Read Write Erase Key

Read ezs and pw and calculate keys

First, see how this CGDI Prog MB Read Write Erase Key:

Read key

Write key
CGDI-Prog-MB-Read-Write-Erase-Key-W220-4 CGDI-Prog-MB-Read-Write-Erase-Key-W220-7 CGDI-Prog-MB-Read-Write-Erase-Key-W220-8

Reset key (erase key)

CGDI-Prog-MB-Read-Write-Erase-Key-W220-9 CGDI-Prog-MB-Read-Write-Erase-Key-W220-10 CGDI-Prog-MB-Read-Write-Erase-Key-W220-11 CGDI-Prog-MB-Read-Write-Erase-Key-W220-12

Second, i read ezs and pw and calculate keys with CGDI MB

Read EIS


Calculate password

CGDI-Prog-MB-Read-Write-Erase-Key-W220-16 CGDI-Prog-MB-Read-Write-Erase-Key-W220-17  CGDI-Prog-MB-Read-Write-Erase-Key-W220-19 CGDI-Prog-MB-Read-Write-Erase-Key-W220-21

Copy & paste password, then save EIS data

CGDI-Prog-MB-Read-Write-Erase-Key-W220-22 CGDI-Prog-MB-Read-Write-Erase-Key-W220-23 CGDI-Prog-MB-Read-Write-Erase-Key-W220-24 CGDI-Prog-MB-Read-Write-Erase-Key-W220-25
Generate EE

CGDI-Prog-MB-Read-Write-Erase-Key-W220-26 CGDI-Prog-MB-Read-Write-Erase-Key-W220-27 CGDI-Prog-MB-Read-Write-Erase-Key-W220-28

Job’s done!

Also tested on Mercedes  W212

Read EZS —> OBD work Fine
Calulating PW from EZS —> Work fine Online Server
Key Calculating —> v041 & v051 Work fine online Server

Another customer tested w212 ALL KEY LOST by OBD in car!!!
Work realy realy good!
W212 is from 2012
Read ezs About 30mins
Upload data
Password given
Read eis info
Paste key password
Then key calculation

CGDI PROG MB key programmer works perfect.

I’m satisfied.




How to do BMW CAS DME Sync After New Programmed Key Failed to Start Car?


I’ve done 1x CAS2 with CGDI BMW – 2006 E90 Diesel

ELV sync was OK

CAS sync failed, ERROR and would not start

car did not start until i used another tool to do the CAS sync.


Every tool can cause cas/ews/dme/dde synch issues on BMW, particularly diesels and you need a good solution to resynch. A very experienced key guy had the same problem on an E91 that had lost synch using AVDI. It’s nothing to do with the tool used, it’s the process.

problem is not to fix synchro, after cgdi you will have synchronize problem with all devices.

They need change data reading algorithm, because after this procedure cas is near dead.


I know CGDI isn’t perfect, but it is, in my experience, a useful tool and good value for money.

I don’t even try to use a key tool to resynch ews/dme. Use a good BMW diagnostic and, more importantly, know how to do it.

To synchronize the blank DME to your car, you’ll need a BMW Compatible scanner which has the function to “Align” or “Synchronize” our DME to your CAS.

Below is a list of the most popular BMW Scanner that we know for sure, have the function to do this procedure.


* GT1 / DIS

* Autologic

* Launch X-431


* PA-Soft

There might be other BMW compatible scanners, but you will have to check with the manufacturer if they have the function to synchronize the DME to the CAS.

Every scanner has different steps that you need to follow in order to do the alignment. However, in general, this is how it is done:

1. Make sure that your car’s battery is fully charged. (This is important because the voltage cannot drop below 12 Volts during the synchronization.)

2. Connect the scanner to the car either through the OBD2 port or, if the car has a Round Plug connector under the hood, use that one.

3. DO NOT start the car, but turn the key to the ON position.

4. Follow the steps in the scanner to select the model and year of your car.

5. Then go to DME or ECU. (This is usually the section where you check for fault codes.)

6. There should be an option available for “DME-CAS alignment” or “synchronization” or “calibration”.

7. After you go through that process you have to turn the key to the OFF position for at least 25 seconds.

8. Then start the car.

When you are finished synchronizing the DME to your car, it is very important to delete all the fault codes and reset all the adaptations in the DME. Otherwise, you may get an incorrect fault codes or a check engine light.

Ista-D is ideal, but it’s hardly a 10 second process.

How to use ISTA-D to do a Sync after battery reset?

Clear dme/dde fault codes

Disconnect battery.

Wait 20 mins. Count it. Don’t be impatient.

Reconnect battery.

Ideally, connect battery support unit.

Check no fault codes. Do not try to start car.

Do cas/ews to dme/dde resynch.

Ista D – service functions. Just follow the instructions.

Click on Function Selection, then under Service Function select Drive, Engine Management (ME9/MED9), select Adjustment in the middle column, DME-CAS in the right hand column, then the middle < > double arrow a list pops up and on the list “Note: S1214 NGCAS / Start Value Status”.

There is a description of the error, then press right arrow.

Option 2 to reset the code (Start Value calibration), then the right-hand arrow

Switch on terminal 15 is shown (which means put the key in and switch on the ignition, but without the engine running (well seeing as the car wouldn’t start that was a no brainer!) Right arrow again, and it popped up, scarily, with 2 errors with a numbers like: <00062538> with <0000000> below it, which I assumed were the mis-matched data from the control module/key – cancelled both these and it then reset the codes, and asked to turn off the ignition (Terminal 15 is off), wait for the main relay to drop out (so left it 20 mins), then the car should start, which it did.

Locked it up and left is another 20mins and the tested starting again to be sure and it worked!
bmw-cas-align-ista-d-1 bmw-cas-align-ista-d-2 bmw-cas-align-ista-d-3 bmw-cas-align-ista-d-4
bmw-cas-align-ista-d-5  bmw-cas-align-ista-d-7 bmw-cas-align-ista-d-8

Working experience:

I’ve done many e60 cas2 no issues, more than i can remember. only 2 times crank no start and needed resync. 1 vehicle is because power died from bad battery customer did not tell me battery dies after few minutes, and 2nd time i did add key and got error, i usually never do add key and always just generate and works good, so maybe that caused.

both times fixed by disconnected battery both + and – and let sit for 20 minutes, reconnected battery and used ista/d to resync. car starts right up after sync.

Can I use OBDSTAR X300 DP on BMW CAS2 CAS3 CAS4 via OBD?

Is it possible to add one key to BMW CAS2/CAS3/CAS4, using OBDSTAR X300DP PLUS yellow version?
On cas 2,3 we use tools like usually VVDI2, CGDI BMW.
On cas 3+ with working key!! If it is AKL (all keys lost), you need to pull ISN code on dde or dme!!!! for registry a key you need downgrade the cas, register key and after backup.
On cas 4 Obdstar x300 dp is not working on obd !!! Just to Block or activate key !!!!
OBDSTAR X300 DP Key Master DP BMW Car List:

Disable and Enable keys:
Enable keys
Disable keys
Read keys infomation
Keys ID
Keys status
Current ignition key NO.
Enable keys
Disable keys
K Line
Read version infomation
Read keys infomation
Keys ID
Keys status
Remote battery status
Current ignition key NO.
Enable keys
Disable keys
Key programming
Key information
Key programming processing
Key adding
Key detect
Function introduction
Operation guide
Other functions

CGDI MB v2.2 Solved Bug with AKL W204 and ELV Function

CGDI Prog MB Mercedes Benz key programmer released new update with software Benz Monster Version 2.2. CGDI MB 2.2 is the best with bug solved and ELV function.

1) Fix bug issue with AKL W204

It seem now the bug is really solved after some users testing for key lost w204. Time collect data still 60 minutes. But password get quickly.

ELV seem also work, but need renew EZS and sync with ELV.






Today I tried again password calculation for my W204 with CGDI MB. Week ago this operation wasn’t succeed with 2 tries waiting 10 minutes both. Today after update, it was calculated in 1 second . Generate keys and write new BE key, all working fine. Happy for this working.