2016 Ford Focus Titanium TCU Retrofit Project

Ok, so with that in mind I should be setting the AB data in the TCU to utilize the CGEA 1.2 network as my Ford wiring book suggests.

I was very confused when finding information on what strategy the Focus platform used.

I searched through quite a few forums on here and got the impression from another post that I CAN and HS3 CAN where practically identical in most ways.

What I will try is setting the AB data in the TCU to be configured for CGEA 1.2 and try the initialization again to see if anything changes.

I believe it is currently set to CGEA 1.3 from what I recall.

I seriously appreciate you guys, this forum rocks!

So, before I make any changes to the AB data this morning, here is what happened last night.

I left from work last night around 2 am, I hopped into my car and decided to attempt to open Fordpass and pair one last time…

To my surprise, the prompt actually popped up this time! I clicked allow and my car showed up in Fordpass :slight_smile:

The only issue I’ve noticed is that nothing works in its current state. It doesn’t show me the estimated fuel, odometer, or even control the car.

But the car is now authorized from my Sync 3 screen.

What should I do next to get the controls to actually work? Should I still change the module to CGEA 1.2 or something else?

This is a huge step and I couldn’t have done this without your support!

Thanks!

Odds are you will never get Fordpass info from your car. It’s not in Fords database to collect that info so it will not send it to you. CGEA 1.2 vehicles did not have TCU’s in NA.

Fordpass info isn’t a huge dealbreaker for me, the only reason I wanted to start this project was to have scheduled remote start for when winter starts.

I tried swapping the AB data of the TCU to CGEA 1.2 this morning and still cannot remote start or use the unlock / lock controls.

Does it being a CGEA 1.2 vehicle mean that nothing will work entirely?

2017-2019 Focus & Escapes that got 4G TCUs from the factory were CGEA 1.2.
Odds are that you need to get the cluster firmware to a level that supports FordPass so that it can pass the data.
Not all that long ago we had someone trying to drop a TCU into a 2013 Fusion and it was a case of having to raise the cluster firmware level to get fuel/odometer and some controls to work.

I have a spare 2018 Escape IPC and when its connected to my Focus it doesn’t even power on.

I’m not sure if Ford changed some of the wiring around from Escape to Focus or if it’s a communication issue.

If I where to update my current IPC is there a specific firmware I should flash?

You can’t drop an Escape cluster in a Focus, the circuit boards aren’t the same.

IPC firmware update is a pain to be nice and usually take 2-5 hours (did a 2014 Escape once with IDS and it took 3 hours, the vbf was over 1.0Gb), so its a high risk activity.

Looking out on eBay, the 2017-2018 clusters are part number F1ET10849CTP and the labels show a software version of 10.02.03, F1ET-14C026-BBE, the ones for the Focus ST are F1ET10849ASR (no idea what the ST has vs the non-ST).
These are MPH versions, looks like the kph are F1ET-10849-CXP?

Your best bet might be to try one of those or get one off lkqonline, keep in mind that with ForScan & Ford IDS you can ONLY raise the odometer mileage, you can’t lower it.

Alright, I have another 2016 Focus Cluster I will attempt to grab from my local scrap yard and update to the latest firmware.

Something that’s a bit interesting to me is that even though I cannot see estimated fuel or control the car, I actually received a Health alert for my car this morning mentioning the oil change is required soon.

Which is accurate since on my way home from work last night the ā€œOil Change Requiredā€ message popped up on my IPC.

So there is some communication happening, but I will still attempt to swap the IPC.

I was only able to find one 2018 Cluster on eBay here in Canada. The guy has it listed for $350 CAD, which is absurd. I can buy an RS cluster for that price.

I will keep you guys posted on how everything goes!

You need Forscan 2.4x for this if you don’t have IDS.
Make sure you’re using a good adapter (like an OBDLink EX), have the car on a charger that can handle the load and have the PC/laptop on AC power.
On the MFT vehicles the OLM delivered alerts via the APIM (information screen) to your phone using the Ford SyncDestinations servers (before the app was deprecated). I’d have to go back to find the write up as far as how it was being communicated without a TCU, but one of the features was that even if you didn’t have MFT you could actually go to the SyncDestinations web site and send turn by turn directions to the cluster message center screen.
Did this more than a few times with a 2014 Focus when one of the kids got lost going somewhere, I’d just hit the site, it would give me current location for the VIN registered to the account and all I had to do was put in an address and hit the send directions button.

I have Forscan 2.4x installed and I also have IDS.

Thankfully I also own an ODBLink EX, it has been my main adapter for quite some time now.

Charger shouldn’t be an issue either since I have access to a few, but taking a peak at my current cluster with Forscan says the latest calibration level available is F1ET-10849-CXK, I’ve attached a photo below for reference.

Would this still work on this firmware since the other 2016 is probably the same Part #?

I’ll say ā€œshouldā€
The 2017s I looked at on eBay have -CXN, so a jump like that makes me wonder if the 2017 has a hardware component change like the Fusion had where the 2013-2014 clusters had a smaller ROM than the 2015-2016, with another change in the 2017-2020.

Well, I just got back from another scrap yard and was able to grab an IPC from a 2017 Focus Hatch.

It’s the proper part # and running the same firmware you had mentioned in a previous post.

I just finished installing it and programming the correct mileage and parameters to match my old IPC.

I’ve attached yet another photo below of the new IPC firmware.

Ok, I’ve waited a bit for everything to settle in and re-set up Fordpass.

I am still unable to send any commands with the new IPC.

Unless I am maybe missing a step in setting up the AB data in the TCU, I honestly am starting to believe that this project is impossible for the MK3.5 Focus.

I can attach screenshots of my AB for the TCU if needed.

I appreciate all of your support and knowledge!

Commands never showed up on my 13 Fusion either. It was recommended to try using IDS, but I chose not to. It would make sense that Ford changed something after people started retrofitting to keep it from happening on vehicles that are not supposed to have TCUs, requiring bits flipped on Ford servers that IDS would handle to enable commands displaying in Fordpass.

Not sure if it is allowed to link to other developers so I’m not going to but there are shortcuts for iOS that send the commands from the HenryLink discord or a task on Taskernet for Android. Shortcuts is free, tasker is not but there is a 7 day trial on their website. Both of those options can be setup to run items on a schedule if that’s the biggest thing you want.

Some of the items in the TCU are platform specific.
Since you got the TCU to authorize I would get the VIN for a 2019 Canadian Escape as those were still HS3, use the VIN to pull the AB from Ford website https://www.motorcraftservice.com/Asbuilt/ and then load that into the TCU followed by a module reboot.

Here’s one I pulled from a car at a dealer in Kelowna.
2019 Escape CA.ab (34.4 KB)

If Ford catches you using this stuff they will lock your account. They don’t want 3rd party apps using Fordpass. To Ford it is an information security risk.

2 Likes