Skip to content
View in the app

A better way to browse. Learn more.

Ford Owners Club - Ford Forums

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.



Join the Independent Ford Owners' Club

Our community has been built by enthusiasts, for enthusiasts, and proudly run by Ford owners' for over 18 years. As an independent, non-official club, everything you’ll find here, advice, support, and opinions, comes directly from members with genuine Ford ownership experience.

Join our friendly community... it's Free!

 

2017 S -Max 2.0L Zetec TDCI - Engine shut down at high load

Featured Replies

Hi All, Hope you can offer some guidance and assistance. I have issue with my 2017 S -Max 2.0L Zetec TDCI. The car has done 42k and has an issue with complete power loss at high load. It happens during acceleration and cuts the car off completely. The dash then shows the red battery light and the orange spanner light. The car will then not turn over (it tries put won't fire) or restart until the car is cycled completely. it will then work fine until it cuts again under load. This only happens at high speed with load on the engine in a high gear but its so dangerous with 3 kids in the car and no option but to idle to the hard sholder and power cycle the car. I took it to a garage who replaced the fuel filter as the cheapest easy fix but this has not solved the issue. I just wanted to ask advice before I end up down some expensive rabbit holes.

I have a cable arriving tomorrow to run a (Forscan) scan for codes but i'm not hopeful as everyone who has scanned has come back with no stored codes.

The only other thing to note is i have noticed the car has a start/stop system and this has never worked, its active but the system never triggers

Ill update tomorrow after the scan but any ideas or anyone with previous experience of this. I have seen a few forum posts around the internet but never a full resolution etc

 

Many thanks



There should be stored codes but you need to read them correctly

On 2/5/2024 at 2:49 PM, DaveT70 said:

There should be stored codes but you need to read them correctly

I now have my cable and forscan installed. Can someone please just give me a very quick overview of what to do. I have scanned tonight and the DTC’s are all clear. 
 

the total loss of power last happend while motorway driving in October. I was planning on taking the car for a long drive up the motorway this weekend to get it into shut down orange spanner mode and then scan before I cycle the car. 
 

is there anywhere I’m missing scanning

 

many thanks all

If you are positive you have connected to the vehicle properly then it looks like the codes for this issue are live codes, which clear immediately and will only appear when the vehicle is in fault state.

The only way to fully find out what is going on is to carry the laptop around in the car and when the car goes into fault mode read the codes then

Wasn’t able to replicate the car cutting out today despite heavy load in high gear for a good 40 min motorway driving. So god knows what’s going on with this car. I’ll keep you posted. Fingers crossed it’s gone 

  • 4 weeks later...

Any update on this? I had a similar issue, but mine was like I was running out of fuel, engine struggled, starved and shutdown. But restarted without a problem every time. My suspicion was supermarket biodiesel clogging the filter in cold weather.

A clogged fuel filter cannot be the reason for this fault.

  • 3 weeks later...

Hello, this issue came back today after i thought it had been resolved but this time I have codes. any assistance is greatly appreciated before I speak with a garage. Codes attached in full detail but top line for both PCM faults are

 

Code: P02FA - Intake Air Flow Position Sensor Minimum/Maximum Stop Performance

Additional Fault Symptom (:99):
 - Exceeded Learning Limit

Status (-68):
 - Previously Set DTC - Not Present at Time of Request
 - Malfunction Indicator Lamp is Off for this DTC
 - Test not complete

 

Code: P228C - Fuel Pressure Regulator 'A' Exceeded Control Limits - Pressure Too Low

Status (-68):
 - Previously Set DTC - Not Present at Time of Request
 - Malfunction Indicator Lamp is Off for this DTC
 - Test not complete

 

 

smax codes.txt

My thoughts would be a problem with the high pressure fuel pump.

  • 5 months later...
On 3/24/2024 at 9:30 PM, Guest said:

Hello, this issue came back today after i thought it had been resolved but this time I have codes. any assistance is greatly appreciated before I speak with a garage. Codes attached in full detail but top line for both PCM faults are

 

Code: P02FA - Intake Air Flow Position Sensor Minimum/Maximum Stop Performance

Additional Fault Symptom (:99):
 - Exceeded Learning Limit

Status (-68):
 - Previously Set DTC - Not Present at Time of Request
 - Malfunction Indicator Lamp is Off for this DTC
 - Test not complete

 

Code: P228C - Fuel Pressure Regulator 'A' Exceeded Control Limits - Pressure Too Low

Status (-68):
 - Previously Set DTC - Not Present at Time of Request
 - Malfunction Indicator Lamp is Off for this DTC
 - Test not complete

 

 

smax codes.txt 5.76 kB · 2 downloads

Did you get a fix for this problem ?

2 hours ago, blacksmithsteve said:

Did you get a fix for this problem ?

The 'original poster' is no longer a member of the forum.

Hi guys, 

did anyone else have this problem or possibly the solution? It is happening to me as well (2016 2.0 TDCI).
I have a sense that in best case scenario it is the pressure sensor, worst case it's high pressure pump.

I've done a test run with forscan and values like pressure desired, pressure that was being supplied, voltage of the sensor....everything matches. All injectors are getting the same amount of fuel. The lines on the graph all correspond to my throttle input ( fuel required ).

Thing is that I cannot reproduce this fault as it occurs occasionally. For example, it happend on an uphill road while driving around 60mph in 5th. So when I try to reproduce the fault on the same road, 10 times over with different throttle input and gearing, it will fly over it like it's nothing XD.

What variables in forscan live data would you recommend to test today as I would like to see if it will show me something?

Thanks

Edited by Mario04
typo

Just an update. replaced the sensor and the car is driving normally now. 
Hope it helps.

What sensor did you replace @Mario04

  • 4 weeks later...
On 9/8/2024 at 8:44 AM, Mattw2692 said:

What sensor did you replace @Mario04

I'd like to know as well? Was it the high pressure fuel rail sensor?

I had a similar fault condition on an Mk5 VW golf TDI that turned out to be a short on one of the PumpDuse fuel injectors. It turned everything off, headlights and all with zero lights on the dash until I cycled the key once we'd stopped. Car drove fine for 2 more months before it happened again, but this time it would not restart afterwards. 

The short in the injector apparently put 45,000 volts to chassis, so the ECU shutdown everything to protect itself and the rest of the car! My wife and I might have died mind, 2350 at night in late November approaching an unlit roundabout at 60mph! If it hadn't been for a car 250m ahead of us, we would likely have crashed! 

Curious on this fault as well! 

Latest Deals

Ford UK Shop for genuine Ford parts & accessories

Disclaimer: As the club is an eBay Partner, The club may be compensated if you make a purchase via the club

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

The "Digestive"






Background Picker
Customize Layout

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.