[MK3] Upgrading instrument cluster

[Steevo25]

The IPC is not too bad as they are pretty standard firmware files. The PAM was a bit more challenging. What I did was find a couple of Focus MK3.5s on eBay which had the full park assist and then looked them up on ETIS to get a VIN. Then I downloaded the AsBuilt which contains the part numbers and calibration/strategy firmware files. I then flashed mine with the same files as they had. 

Initially, my UCDS scanner would not recognise it as a Focus part so I had to tell it the car was a C-MAX before it would show any details about the module. Once I flashed it, it now shows up as a Focus MK3.5 part and I could go in to the configuration to change it.

For you it's a bit easier as there are loads of cars out there with just rear sensors. Do you know the actual car the module came out of (Focus, Kuga etc etc).

Forscan doesn't differentiate between car models it just scans the part number. But when you do update the firmware, it will provide the wrong firmware files as it will match the current calibration with it's database and come with firmware files that fit with whatever it has on it at the moment. So you have to do a custom firmware flash in Forscan. You also need the special version of Forscan which isn't available on their website. You have to contact them to get it.

[Guest]

Thanks Stephen, how do I get the correct versions?

[Steevo25]

Once you find out what they are, let me know and I can get them from UCDS. 

[Guest]

Thanks Stephen, decorating for the next few days. Will get on it later in the week.

[mark1989]

hello everyone, yesterday I installed the display of a focus st mk3.5 on my titanium focus mk3 (I have park assist but having installed the android radio it no longer worked, the parking sensors instead), the mk3.5 cluster works perfect, too the sensors on the display, the only problem is the audio of the sensors no longer goes, should I buy the control units at the top of the post? thank you

[Steevo25]

If you have changed to a MK3.5 instrument cluster, you also need to change the parking assistance module (PAM) from a MK3.5. It must match your parking sensor configuration (i.e. the PAM for just rear sensors is different to one with front/rear sensors).

You may also have to upgrade the firmware on your BCM depending on the year of your car and the current firmware level. 

Not sure what you mean by android radio. Have you installed an aftermarket headunit?

[mark1989]

yes that's right, I replaced sync 1 (no sony) and installed android cartablet, where is the pam module? just replace that one or even wiring etc? how do I figure out the correct code for me (sensors front and back).

[Steevo25]

The PAM module is in the boot on the right hand side under the trim. You will need to remove the carpet type trim on the right hand side to access the PAM, but it's very easy to replace. 

You will need one from a MK3.5. If you have front and rear then you need a PAM module that has a part number F1ET-15K866-B*.

The F1ET means a MK3.5 module and the B after the final hyphen denotes upto 12 sensors. The asterisk is just a version and doesn't matter which one (mine, for example, is F1ET-15k866-BJ). You may have to reprogram the PAM with the correct number of sensors. This can be done with Forscan or UCDS. 

But although this is required, it may still not fix your issue as you will also need the correct firmware level on your BCM. If you have an early MK3, then it's possible that the BCM cannot be updated to the correct firmware level and you would then need a new BCM. Although a used BCM is relatively cheap, unfortunately all the key and immobiliser information is stored in the BCM (and PCM), so swapping it out is not easy and will require Ford, or a specialist with access to the Ford database, to program your keys in. 

I cannot give you the correct firmware file as there are lots of them and is dependent on your BCM part number. 

Of course, you could be lucky and your BCM already has the correct firmware on it. This is more likely if you have a later MK3. Mine is a 2014 and already had the correct firmware. 

[mark1989]

ok thanks, I'll try to buy the pam control unit as you indicated, I hope it works without modifying BCM.

[TheBlueGP]

On 3/21/2021 at 9:50 PM, Steevo25 said:

One thing I have found out about these PAMs is although the physical part numbers are the same, the have slightly different firmware on them depending on the car they came out of (and they do have different finis codes).

My PAM is F1ET-15K866-BJ. They fit that to a Focus MK3.5, a Kuga and a C-MAX (and probably some others). My one came out of a C-MAX and when I first installed it, my UCDS scanner would not even detect it as a valid Focus part. I had to find out what firmware was used on the Focus MK3.5 version and then flash it with that firmware. Before I did that, I didn't get any chimes and although it did kind of work, it didn't work fully until I did the firmware and then config. 

Hi Stephen (and everyone else, becasue it's my first post in this forum 🙂 )

I've got Focus MK3 ('11) and I've decided to change my IPC and PAM into facelift versions (I've already install Sync II). I flashed my Mk3 IPC with a Mk3.5 frimware and installed F1ET-15K866-BJ PAM. However now I have problems with PDC that you described above. I would like to use your solution but I don't have any clue which of the files listed in as built file are the firmware for PAM module. Can I asku you to write what exactly files you used to flash PAM module? 

 

[JW1982]

The type of BCM of a 2011 Focus MK3 is too old to support the MK3.5 PAM module. This type of BCM is not compatible with the software of the newer type of BCM that is required to support the MK3.5 PAM module.

To make it work you will have to replace the BCM. Since the BCM is part of the PATS immobilizer system the PATS system needs to be reprogrammed by someone who has (licensed) access to the PATS programming functionality of the Ford FDRS diagnostic system.

[TheBlueGP]

Thanks, I know the procedure of BCM replacing and due to necessity of rewriting the keys in PATS system, I still haven't change it (although I've got one which is from 2013).  😉 

However, I'm not really sure that my BCM may be a problem. I have updated my BCM's firmware and after installation of mk3.5 PAM (which I did before reflashing IPC firmware) I reprogrammed it to change i.e. number of installed sensors (from 12 to 10), type of car (the module was put out of Kuga mk2) and the module basically worked - there was no sound form PDC, what is obvious, but visualization of obstacle at the rear was shown properly. The front sensors also worked what I checked in Forscan (by checking correct PIDs), and the PDC visualization appeared on APIM screen when the car was closing to obstacle in the front. The issue was that front sensors zones visualized on the screen remained all the time grey and didn't change it color when the car was closing to the obstacle. At that time, I didn’t change in the APIM settings the type of PDC architecture, as it’s said above, it should be done.

Now I’m going to try to reflash the PAM module. I’ll see what happens…  

[Steevo25]

I very much doubt the PAM module is your issue here. This sounds more like the APIM configuration. 

If you have enabled the correct number of sensors and setup in the PAM, and are not getting any DTCs, and also set the correct options in the BCM, then the APIM takes care of the rest for visualisations. 

I, also, very much doubt you will get the sound working with a 2011 BCM. Although you have flashed the latest firmware to it, that will almost certainly be the latest firmware for that model of BCM and not the latest firmware required for the parking sensor beeps. 

I would firstly check that the APIM is correctly setup. 

Firmware for the PAM, I just used whatever Forscan (actually UCDS, but it was the same as Forscan) suggested as the latest PAM firmware. 

[mark1989]

a strange idea, if I leave the electronics of the mk3, change the bottom, hands and display of the mk3.5 framework everything should work correctly (in theory) correct?

[Steevo25]

Depends what you are trying to achieve. If you are wanting the digital speedo then no it won't work. The digital speedo is in the firmware and not the hardware. The MK3 and MK3.5 instrument clusters are technically the same hardware wise. It's the firmware that is different between the two. 

A MK3 cluster can be upgraded to a MK3.5 just by flashing firmware and nothing else. 

[mark1989]

considering the sensor sound problem I thought of leaving the mk3 electronics, but putting the red hands, dial and if it has the same connector also the color display of the mk3.5, so to have an aesthetic of the mk3.5 ST, digital odometer no I don't serves, I would be happy if the ST logo remains at the car opening

[Deano1234]

On 10/29/2020 at 9:43 AM, JW1982 said:

I want to perform this modifications myself on my car. Next time I have to order spare parts for my car I also order the parts to retrofit the MK3.5 PAM module.

I currently use a modified version of the latest MK3 instrument cluster software with animated RS logo

Hi mate could you message me please 

[Eri789]

On 26/12/2021 at 19:07, Deano1234 said:

Ciao amico, potresti scrivermi per favore 

Buongiorno  anche io ho aggiornatto il software del ipc con il restyling del focus mk3.5 con il tachimetro digitale. Ho un focus dell 2012 pero mi da un problema.  I valori del ipc  dei quatro quadrnti si azzerano da soli a quasi 6 o 7 acenzioni della machina. Qualche aiuto per favore

[DG1966]

I have 2014 Focus SE, sync1 (just updated to 4.6 finally 😳)

so can you buy like 2015/2016 digital screen from the IPC and swap it? Is that where firmware is located?

or I need to buy full cluster with the screen?

thanks.

[shawstvs1]

Hi all

I upgraded my Focus mk3 zetec instrument cluster to larger display mk3 (Titanium spec). Mileage was less so easily changed in Forscan. All functions worked on steering wheel but after upgrading to mk3.5 wheel my buttons on left (after upgrade) contolling trip computer do not work.

Is this a programming issue or something else?

Thanks

[unofix]

Could this be related ?

On 5/14/2021 at 9:05 AM, JW1982 said:

The type of BCM of a 2011 Focus MK3 is too old to support the MK3.5 PAM module. This type of BCM is not compatible with the software of the newer type of BCM that is required to support the MK3.5 PAM module.

To make it work you will have to replace the BCM. Since the BCM is part of the PATS immobilizer system the PATS system needs to be reprogrammed by someone who has (licensed) access to the PATS programming functionality of the Ford FDRS diagnostic system.

 

[rd457]

8 minutes ago, shawstvs1 said:

Hi all

I upgraded my Focus mk3 zetec instrument cluster to larger display mk3 (Titanium spec). Mileage was less so easily changed in Forscan. All functions worked on steering wheel but after upgrading to mk3.5 wheel my buttons on left (after upgrade) contolling trip computer do not work.

Is this a programming issue or something else?

Thanks

Did you actually do proper programming/cloning or did you just adjust the mileage specifically? If the latter then there's your problem, you need to properly copy across your vehicles config data in full. (Presuming software compatibility).

[shawstvs1]

5 minutes ago, rd457 said:

Did you actually do proper programming/cloning or did you just adjust the mileage specifically? If the latter then there's your problem, you need to properly copy across your vehicles config data in full. (Presuming software compatibility).

Ah

Wasn't aware of the need to program it just adjusted milage!

Copy config data from? to? in Forscan?

Thought it was too easy

[shawstvs1]

13 minutes ago, unofix said:

Could this be related ?

 

Has been done with no issues apparently with Mk3 cluster and Mk3.5 wheel/clockspring

[rd457]

23 minutes ago, shawstvs1 said:

Ah

Wasn't aware of the need to program it just adjusted milage!

Copy config data from? to? in Forscan?

Thought it was too easy

I haven't looked at any of the details of doing this specific thing your doing, but computer modules generally have a block of configuration data specific to the vehicle they are installed in; if you replace a unit you need to copy across that config data. The config data can include the vehicle's VIN number, hence why it's a general thing to do regardless of part number compatibility. The config data is used by the software to operate correctly and the fact that your replacement instrument cluster came from a different vehicle model and you've not configured it fully for your vehicle is probably why peripheral controls in your vehicle are not functioning fully. Note that it is not always possible to even adjust mileage, sometimes blocks are put in place to prevent changing to a lower value than already clocked up on the unit. I've even heard of blocks being put in place to prevent changing the VIN number held in the config as a means of manufacturers blocking reuse of old units such that they can make more money selling brand new ones. Then on top of this when you're transplanting a unit from a different model you've got to consider whether or not the software that runs of this different unit will actually be compatible with the software and hardware it needs to interact with - The programmers who created the software for a specific model of instrument cluster would have been primarily concerned with just making it compatible with vehicle models they planned to put that cluster model into, not making sure it could be transplanted to other vehicles.