Yanhua Emulator, DP4 or CG Pro for BMW 35128WT

 What is the best emulator to get for BMW FEM/BDC Bosch cluster with 35128WT eeprom mileage correction?

You have 3 options for this bosch 35128wt:

1.Yanhua emulator eeprom with their new adapter and very tricky to solder good and have good results. Read/write is no problem. and put id7 filter behind cluster for BDC.

Three short VINs are located in the EEPROM. It is necessary to change them to FF.

Emulator (35128)from YANHUA only work with VDO cluster. We did program many without any results.

Example:

Yanhua Mini ACDP Virgin 35128WT V2 G01 Cluster

 

2.Write eeprom with DP4(bmw7/G program) and add id7 can filter behind cluster. also no problem read/write. If give you only message after successfull write and read: “Unknown eeprom” but everything was good.

You can use DP4(elpro) without emulator for Bosch 35128WT (it will say “Unknown eeprom” after but write is ok, no need ID/Data separation, just C12 clip). But you need can filter if it is BDC system. There are some good updated plugin can filters for ID7 cluster, no-black screen. So need to take out SKF stopper.

One of our customers has used this method for BMW G 7-serie 2019 and worked well.

 

 

3. CG Pro. read/write with cg pro also no problems, only check first if correct read mileage, you have 3 options for 35128wt. need id7 filter for bdc also.

 

CG Pro cannot read chip ID, but can read/write complete EEPROM size (0x0000h – 0x3FFFh).

CG Pro has no issues with with writing with bosch, with other then bosch we had only 1 time success writing directly. also 1 time write only to existing eeprom.
for all others, you can use yanhua emulator eeprom and solder with microscope because the solderings from the legs overlap and short sometimes.

VVdi Prog is good programer but for reset this eeprom CGprog is better.

Example with CGPro

CG Pro 9S12 BMW F Series Instrument Reset With 35160WT Adapter

BMW 35128 Mileage Correction by VVDI CGPro or Yanhua?

 What is the best tool to do mileage correction on BMW F and X series? How to Virgin BMW F or G series cluster m35128? Is it difficult to erase 35128 eeprom om BMW cluster? Which device is better, vvdi prog, cg por, r270 or Yanhua emulator?

For 35128WT only a few devices claim that they can do this chip. Here comes the clue:

 

Xhorse VVDI Prog:

with Xhorse 35160DW Chip.

VVDI prog and M35160DW work really well for replacement 160d0wt/wq. They have replacement eeproms which allow you to write the id on the chip.

At first you must read ID sector from original 35160 and write it to VVDI chip.

When using vvdi pro to read & write 35160DW Chip, read the original eeprom, then rewrite to xhorse 35160wt chip and replace original one. It doesn’t need the dedicated adapter.

(How to virgin cluster with vvdi prog and 35160dw chip)

but it DOES NOT work as a replacement for the M35128WT found in newer BMW clusters from 2016 onward. VVDIprog can read/write 35128 but not do mileage on it. if you erase the data and rewrite, dash will show red dot.

After 2015 there are eeproms in bmw cluster must changed you cannot rewrite on it.

 

CG Pro 9S12 & 35160 Adapter

 

CG Pro is the tool that can do 35128 chip.

For 35160WT, vvdi prog is better than cg pro. Sometimes can be erased, sometimes not.

But CG Pro can do 35128 chip.

If you need a tool to read and write 35128, this tool will work without problem. People have done many times.

You don’t need to touch mileage is car mileage is higher than the instrument.

CG Pro cannot read chip ID, but can read/write complete EEPROM size (0x0000h – 0x3FFFh).

CG Prog (also hextag) can read full DUMP to clear VIN. You need to replace VIN in eeprom with 0000000

To change eep vin any eeprom programer which support 35128 will doit. Only first 2 lines in eep are protected

Related Instruction:

CG Pro 9S12 BMW F Series 35160WT Instrument Reset With 35160WT Adapter

CG Pro 9S12 Read & Write 35160WT Dashboard EEPROM: Confirmed!

 

Yanhua Mini ACDP and 35XX Emulator

35128 have 2 versions.

Version 2 can be done by Yanhua Mini ACDP and M35080 adapter.

Version 1 only possible with yanhua 35xxx simulator.

Check what version it is when only after read, because you have to see file structure.
The mileage could be saved in different location. Please see bellow. V1 could be made to 0 only with simulator, v2 could be made via a standard adapter (35080 160 adapter for ACDP).

m35128 version 2 instruction with Yanhua ACDP

http://blog.obdii365.com/2021/10/27/yanhua-acdp-virgin-35128wt-v2-g01-cluster/

m35128 version 1 instruction with Yanhua 35xx emulator

http://blog.obdii365.com/2018/10/24/change-m35xxx-mileage-using-yanhua-35160-35080-emulator/

R270 BDM Programmer

Confirmed that R270 can only read part of what is inside 35128WT using 160/35160 MCU setting.

R270 cannot read it properly.  If Dash has 35128WT you cant do anything with R270. there you need some better tools, or in most cases a eeprom emulator for mileage.

 

Usprog:

Usprog can erase 35160 and 35128 but some chips can take 4 hours.

 

 

In a nutshell,  there is no solution for 100% of chips. Only working solution is for changing chips, or use emulator or just leave it.

Top 5 Tools to Repair BMW FRM3

Car model and year: BMW Mini E81 / E71 with FRM3 (BMW Footwell Module).

Purpose: repair BMW FRM3

Possible Tools to repair FRM3:

1.Xhorse VVDI Prog

2. Yanhua Mini ACDP

3. CG Pro 9S12

4. Hextag programmer

5.Xprog M Box

VVDI PROG repair FRM3: confirmed

I have not had any trouble yet with my VVDI prog.

When using vvdi prog, you must first write partition (choose dflash 0kb) and ALSO write your new eeprom file. Function Write partition does not write your .bin eeprom file.

Step-by-step procedure:

BMW E-series E71 for example.

Step 1: Read Dflash

Connect FRM module with VVDI-prog

Open VVDIprog software

Select MCU->Motorola -MC9S12->9S12XEQ384 unsecured

If vvdi prompts “Partition information error, please select the partition size manually”

Select the partition size EEE:0 sector, DFlash: 128 sectors (32K), press OK

Read and then save Dflash, i.e E71 xe

Step 2: Dflash to Eeprom 

Open Dflash to EEE for FRM3 Software, upload Dflash data just read

Then convert Dflash to eeprom.

(You can use free online FRM3 D-Flash to EEPROM converter here as well:

http://tlvps.tomvanleeuwen.nl/frm/

Save eeprom, i.e: eee_L508991.bin

Step 3: Write EEPROM

Back to VVDI Prog software, select Type 8-Others->BMW->FRM E-series XEQ384

Click Write Partition (will erase Dflash and eeprom data)

Write EEPROM partition to 16 sectors (4K), DFLASH: 0 sector

Open EEPROM data just converted from Dflash.

Click Write tab to write eeprom

Reset FRM success.

Install FRM module back to vehicle.

BMW FRM 2M25J/3M25J(9S12XEQ384) pinout to VVDI-Prog.

BMW FRM F-series 2M25J (MC9S12XET512) pinout to VVDIProg.

You can use VVDI BMW to do coding.

Yanhua Mini ACDP

ACDP Mini+ FRM adapter repair FRM3: confirmed

It depends on the chip types.

Connect the Yanhua Mini ACDP device and BDM adapter with the FRM unit.

Backup data before operation.

Run Mini ACDP app on a mobile

Select BMW->FRM Programming->ICP MC9S12XEQ384 MASK: 3M25J

Select FRM Data Recovery (Automatic mode)

Detect pins and probe connection

Reading chip data

Read and display chip data

Check the data. If reads D-Flash as 32K, the FRM module data is corrupted.
If reads EEPROM data as 4K , FRM module data is not corrupted.

Uploading data

Auto saved D-flash to Yanhua Mini ACDP file folder

Show programming data

Verifying data

FRM data recovery completed.

CG PRO 9S12

CG Pro repair BMW FRM: confirmed

Procedure:

1: Check car model

Car model: BMW E series

Module: FRM

Chip: 9S12XEQ384

2: Turn off the ignition switch and remove the FRM module from the driving left foot of the car

3: Disassemble FRM module and confirm the SN, type and chip

4: Open CG PRO software

Select type, car make and model

Follow the corresponding wiring diagram to connect FRM module to CG PRO 9S12 programmer via DB25 adapter

5: Read EEPROM data and save

6: Write the data has been read or new data after partition operation

After finishing repair the data, install the FRM module back to the car, and set code for FRM by CGDI BMW key programmer.

HexTag repair a module FRM3: confirmed

You don’t have to buy AutoHex, you can buy HexTag separately.
Step-by-step procedure:

Go to Microtronik HexProg main menu, software 1.0.6 for example.

Click on “On Bench Programmer”-> “BMW”-> “FRM”-> “FRM3 E Series”

Click on “Wiring” to follow it to connect.

Click on “Read” and get message “ Error on reading EEPROM shows the files in FRM3 is corrupted”.

Click on “P-FLASH” and then “Read”.

To check the communication with FRM you can try to read the P-flash.

Click on “EEE” -> “Read” again, Click on “Repair” and get message “This function is used to repair corrupted FRM EEPROM data. It will try to recover the original data from D-Flash, if it failed please contact Microtronik for help”, go on click on “Repair”.

FRM EEPROM data has been repaired.

When it shows the FRM Repair prompt again, just close it.

Now we can read EEE shows FRM is back to normal state.

You are advised to code FRM using AutoHex after repair.

Xprog M repair FRM3: Need Luck

Xprog M box (UPA as well) is the cheapest device to read fault FRM3 data. But it is not stable as other programmers.

Some will have these kinds of issues a lot when use Xprog clone to repair FRM’s.

You can hook the frm back to the xprog and made a backup of the EEE and pflash. Then perform coding using WinKFP/Ncs expert.

Check guide here:

Xprog m+WinKFP fix dead FRM3 on BMW R56

FYI:

There are several devices you can used to perform FRM coding job:  BMW ICOM Engineering software Ncs expert, Launch X431 V,  VVDI BMW, CGDI BMW, Autel Maxisys Pro MS908P etc

To be upgrading…

www.obdii365.com

http://blog.obdii365.com/2020/03/25/top-5-bmw-frm3-repairing-tool-reviews-procedure/