MicroHacker Forum

Hello, does anyone know if the PCM can be easily replaced by another hw version or it must be strictly the same?
By easily I mean plug and play and then some vbf loading with UCDS (I have chinese one) or initialization through Forscan.
My PCM is BG91-12A650-RC (2011 85kw manual trans) and I do not have keyless.

BG91-12A650-R* is Ford P/N; this describes a combination between HW plus certain software.
Look for P/N of HW of manufacturer - Bosch / Siemens / Delphi

In your example the software is at revision code "C" which means is the 3rd one.
The HW is Delphi: DCM 3.5, E2U9E or G2614
The same HW is used with different software to have Ford P/N: BG91-12A650-S* or N* / P* / FF* / FG* / FH*, AV41-12A650-C* or D*
The same HW can also be found on Peugeot & Citroen on their DW10C engines

Thanks for your reply.
If I get it correctly it means that it should work without problems right?
I do not have physical picture of my PCM yet but the replacement PCM is BG91-12A650-FGE (2014 103kw) as seen on screenshot.

Does it also mean that it is plug and play and then just PCM initialization through forscan or is there more to do?

First you have to put the right software - I would go with UCDS and not ForScan. For FG* version it should be easy. If it was AV41 version, you would have to use "Dead Module" option as this one is for Kuga that uses other CAN signaling.
Then you have to do PATS - Module Initialisation. You can do this with ForScan, but you need Incode.

Why do you want / need to replace PCM? I didn't find any Delphi DCM 3.5 to be HW defective, only wrong software.. unless it was "touched" in a car accident

Well a friend of mine tried to do some "chiptuning" with kess and fucked it up so now I am left with dead PCM which could not be restored through UCDS nor with IDS in Ford (I do not know if they even tried though).
I replaced the PCM then tried PCM init with forscan but it is not enough. "Imobiliser active" is still coming up on the dash and there is a DTC (P242A:85-24) for some egr sensor which wasnt there normally so I hope it is not due to some difference in wiring or in the PCM itself.

The "new" PCM is from Mondeo 2014 103kw so how do I know which software should I upload? My VIN is WF0GXXGBBGAR05621
About the PATS it is the procedure done over BCMII called PATS programming? Where can I get the Incode?

Attaching more info (my dead PCM, DTCs and info about new PCM in UCDS)

Just a note, I cannot see PCM PATS Init in forscan procedures that's why I was asking about BCMII PATS Init.
Attaching list of possible procedures.

Yes, in ForScan it is at BCMII PATS Programming.

If the failed tuning procedure was done by OBD port then there are 95% chances that the PCM can be restored by IDS / UCDS and maybe ForScan.

Do you have any UCDS Update Wizzard session with the car before the failed flash procedure? If yes, then load it and then choose to update PCM. See if it works.
If not, then write down the files it needs and go for a VBF Loader were you put the same files, but also select car and mark "dead module" option.. and follow the instructions.

You can use the above procedure also to flash the "new" PCM with the needed files.

With Kess I think you can also resolve the PATS problem by copying the contents of the EEPROM of the original PCM to the new PCM.. if they had it backed up before messing with it.
If you have the backed up file and upload it here I can tell you what files you need to flash.

Unfortunately I do not have update wizard backup before failed flash and I do not know what you mean by session but the bad PCM cannot be seen in any program (UCDS, Forscan) and the only thing from update wizard before the fail I have is screenshot
It was done through OBD port and I have tried dead module programming in vbf loader but it did not work (tried hw number BG91-12A650-RC and F113) as you can see on the attached pictures. Tried it many times always (also with disconnecting battery) with the same result. Maybe the SBL is wrong as I have used AG91-14C273-AA and BG91-14C204-DP vbf.

What are the needed files for the new PCM? Or I just have to do the PCM update through Update Wizard as it says there is newer version.

I have also attached the backup from Kess if it is for any use.

EDIT: found that I do have saved session from 3. 5. 2021 so I will try to use it.
EDIT2: loaded up the session copied the files to Downloaded folder as the UCDS won't download them from internet, checked dead module but still the same result "Cannot upload bootloader". Note: the SBL and VBF that UCDS wanted were the same I was trying to upload earlier.

AG91-14C273-AA is SBL for Focus 2 / Kuga / C-Max for 2.0TDCi DW10C Euro5
AG91-12B684-DA is SBL for Mondeo 4 / S-Max / Galaxy 2 for 2.0TDCi DW10C Euro5

They are for the same Delphi DCM 3.5, but they differ in CAN signaling... but even like this, it should have at least allow you to upload SBL to PCM with "dead module" option as in this procedure the CAN signaling is the same.

If you have an ELM327 or ELS adapter, try to have both UCDS and ELM/ELS adapters connected to HS CAN and use ELMConfig in Sniffer Mode with filter for 7xx CAN IDs on HS CAN and see if you have any answer from PCM on UCDS requests when you try with VBF Loader and "Dead module" option.
PCM listens on 0x7E0 ID so a diagnostic equipment has to talk on this ID
PCM answers on 0x7E7 ID.. so a diagnostic equipment has listen on this ID

If you see any messages with 7E7 then the PCM still boots and you should be able to flash it with the correct software.


The attached BIN file contains only the "maps data" - I don't know if this is how Kess is working or if it had an error on reading the entire flash.
Also, the EEPROM data is missing - again, don't know if this data can be read or not by Kess.
If you compare the BG91-14C204-DP.vbf file with this BIN file you will see that the VBF file has more data. I do it like this: