Hey folks, I'm a Ford Focus owner from China hoping to get some advice on a frustrating issue. Just want to be upfront: English isn't my first language (I'll rely on translation tools for your replies), and I apologize if my explanation isn’t perfectly clear—please bear with me! Really appreciate any insights from those who might have seen something similar!

I drive a 2017 China-market Focus hatchback (MK3.5) with the 1.6L naturally aspirated engine and dual-clutch automatic (DCT). Originally it had the basic blue monochrome instrument cluster, but I upgraded to the higher-spec full-color LCD screen.

After the swap, I started having this weird problem: Sometimes when I turn on the ignition (not even starting the engine, just powering up), the cluster will suddenly go completely black for a split second, then light back up like it’s rebooting. When this happens, it wipes all trip computer data—both trip meters (Trip 1/2), average fuel economy, distance to empty—everything gets reset to zero. The only thing it doesn’t touch is the main odometer reading. It feels like the cluster is doing a factory reset on itself randomly.

I’ve dug through Chinese forums and found a few theories, but none seem to fit:

1. Some said clusters auto-reset trip data after 1,000 or 2,000 km/mi. Mine made it to 3,400 km without resetting, but other times it’ll reset after just 50-100 km. It seems completely tied to that split-second power glitch during ignition, so the mileage threshold theory is out.

2. I’ve tried everything to replicate the issue—different ignition timings, simulating voltage drops, you name it—but it’s totally random. Sometimes it behaves for 1-2 months straight, other months it’ll reset 10+ times. No pattern with driving time, distance, or conditions.

3. Others blamed weak batteries. I installed a brand-new OEM battery, and there are no other low-voltage symptoms (Sync 3 stays bright during cranking, headlights don’t dim). So battery’s ruled out too.

4. Here’s the real head-scratcher: I even swapped in a second identical cluster unit—and the problem still happens. That should eliminate a faulty cluster itself, right?

At this point, I’m truly at a loss. I’ve ruled out the obvious suspects, and the randomness makes it impossible to pin down. Where would you look next? Could it be a CAN bus glitch? BCM compatibility? Wiring gremlins? Any diagnostic tips or similar experiences would mean the world to me. Thanks so much for your help!

If it occurs randomly, you should look at the connectors welding 

Might be a firmware clash

On 8/22/2025 at 2:13 PM, mougly said:

If it occurs randomly, you should look at the connectors welding 
如果问题随机出现，你应该检查连接器的焊接情况

I've already tried replacing the entire instrument cluster module, but the problem still persists. Are you suggesting I should check the wiring connections between the cluster and the ECU or PCM?

On 8/22/2025 at 2:46 PM, DaveT70 said:

Might be a firmware clash
可能是固件冲突

I believe your suggested direction is likely correct. Could you elaborate on where this firmware conflict typically happens? Specifically:

1. Which versions are most prone to conflicts?
2. What is the cluster firmware conflicting with? Is it with SYNC 3, the BCM (Body Control Module), PCM, or another module?

For context on our regional firmware setups:

• Here in China, only two firmware versions exist for this upgraded cluster:
  • "12 Firmware" (designed for 2012 MK3 Focus)
  • "15 Firmware" (optimized for 2015 MK3.5 Focus)
• Both firmwares can be flashed onto either hardware (2012 or 2015 cluster units).
• Visually, the only difference I’ve observed is font style – no obvious functional issues appear after cross-flashing.
• This makes me question whether firmware compatibility is truly the root cause, but I’d value your insights based on experience in your region.

 

MK 3.5 Dashboard

MK3 Dashboard