GREAT WALL DCM3.7AP 3612100-ED01A, MT20U2 IMMOBILIZER EMULATOR

Immobiliser emulator for GREAT WALL GWM vehicles. Currently tested ECUs with which this emulator works include: DCM3.7AP, MT20U2.
To use this emulator, we read the synchronization bytes from the EEPROM area of this ECU and store them in the EEPROM mounted on the emulator PCB – 24C02.
We do not need to modify the flash file or the eeprom file in the ECU, so it remains in its original state.

Thanks to the immobiliser emulator, we can eliminate the following components of the immobiliser system:
- Defective immobilizer module
- Defective or lost transponder key
- Faulty electrical wiring of the power supply and K-BUS bus, the wiring harness to the immobiliser module, when the emulator is fitted inside the ECU.

MT20U2 DELPHI ECU Based on the 9S12 MCU, reading the eeprom area is needed to obtain the synchronisation bytes to adapt our emulator.

DCM3.7AP DELPHI ECU Based on the R5F72513R MCU, reading the eeprom area is needed to obtain the synchronisation bytes to adapt our emulator.
If you are an EU-based automotive electronics company, you can send us an engine control unit for assembling and testing the emulator for service – please contact us or to one of My distributors .
In order to use this solution, the customer must be qualified as an automotive electronics technician and have the necessary diagnostic tools and wiring diagrams.