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!

 

2013 Galaxy 2.2 tdci starts but will not accelerate above idle -

Featured Replies

Hello all,

 

I've a galaxy 2013 2.2 PSA engine.

Have had the car 3 years with no major issues during that time - DPF was removed shortly after purchase, Catalyst replaced 5 months ago after flexi joint and mount failed.

 

Driving along at normal in town speed, and with no prior indication, the car lost all power, no dash warnings, noises etc.

 

Now the car starts up from cold, fires up perfectly first press of button, revs up like normal, and can be held at high revs for 30 seconds or so, or driven approx 400m.

Then it loses all power again, revs fall to 1k rpm and will not increase, it will sit and idle sounding perfect, but any attempt to accelerate it simply stutters and fluctuates around 1k rpm. It will happily sit idling for as long as I want, shows no sign of cutting out, but simply will not accelerate.

 

Once turned off, the car will NOT restart again, pressing the button everything lights up on dash as normal, but the starter doesn't try to engage, nothing.

Left for 40 minutes to an hour, the car will fire up perfectly, and then follow the same pattern as above.

 

Garage have looked and tried changing sensors and removing various pipes, can find nothing mechanically wrong - say its electrical.

Auto-electrician has checked electrical side and says all is in order - it must be a software issue.

Neither could find any fault codes to narrow the issue down.

 

I've bought an adaptor and downloaded Forscan which is showing the following;

 

U0126:00-8A

B1B57:11-2F

B1B58:11-2F

 

None of these would cause the above issue I'm sure (parking sensors have never been operational)

Any clues on where to start looking, or what the cause may be??

 

 

(WARN) [22:58:16.314] Checking FTDI #1:A50285BI...
(OK) [22:58:18.872] Connection to adapter has been established: FTDI #1:A50285BI
(OK) [22:58:18.873] Adapter:  ELM327 v1.5
(WARN) [22:58:18.998] The adapter is NOT recommended for this car - some FORScan functions may not be available or not work properly
(OK) [22:58:19.003] Connection to vehicle has been established
(OK) [22:58:20.851] Vehicle: Ford Galaxy\S-Max Duratorq Turbo Diesel Common Rail Injection Stage V 2.2L 2013 ( 2010.5MY ), VIN: WF0*********55625
(OK) [22:58:21.810] Found module:  PCM - Powertrain Control Module
(OK) [22:58:21.991] Found module:  OBDII - On Board Diagnostic II
(OK) [22:58:22.230] Found module:  SASM - Steering Angle Sensor Module
(OK) [22:58:22.350] Found module:  ABS - Antilock braking system
(WARN) [22:58:22.718] DTCs in ABS: U0126:00-08
(OK) [22:58:22.725] Found module:  RCM - Restraint Control Module
(OK) [22:58:24.446] Found module:  BCMii - Body Control Module
(OK) [22:58:24.551] Found module:  RHVAC - Rear Heating Ventilation Air Conditioning
(OK) [22:58:28.859] Found module:  SRM - Speech Recognition Module
(OK) [22:58:28.936] Found module:  PDM - Passengers Door Control Unit
(OK) [22:58:29.061] Found module:  DDM - Drivers Door Module
(OK) [22:58:29.191] Found module:  PAM - Parking Aid Module
(WARN) [22:58:29.538] DTCs in PAM: B1B57:11-2F, B1B58:11-2F
(OK) [22:58:29.542] Found module:  HVAC - Heating Ventilation Air Conditioning
(OK) [22:58:29.607] Found module:  RFA - Remote Function Actuator
(OK) [22:58:29.691] Found module:  ACM - Audio Control Module
(OK) [22:58:30.329] Found module:  IPC - Instrument Panel Control Module

 

?hash=a8846a5c27c08b0a10d6bff9b255f44b
 

 

 

 

 



1 hour ago, AndyPC1 said:

DTCs in ABS: U0126:00-08

I wouldn't be too quick to dismiss this. If I understand the dtc correctly it is referring to the steering angle. This can put the vehicle in to limp mode.

Have a read of this Mondeo with slightly similar issues:

https://www.talkford.com/threads/engine-malfunction-on-warm-start.312249/

Yes, I know its not exactly the same but take on board the list of problems and what the fix was at the end.

3 hours ago, AndyPC1 said:

Now the car starts up from cold, fires up perfectly first press of button, revs up like normal, and can be held at high revs for 30 seconds or so, or driven approx 400m.

Then it loses all power again, revs fall to 1k rpm and will not increase, it will sit and idle sounding perfect, but any attempt to accelerate it simply stutters and fluctuates around 1k rpm. It will happily sit idling for as long as I want, shows no sign of cutting out, but simply will not accelerate.

 

Once turned off, the car will NOT restart again, pressing the button everything lights up on dash as normal, but the starter doesn't try to engage, nothing.

Left for 40 minutes to an hour, the car will fire up perfectly, and then follow the same pattern as above.

It is a bit of a long shot, but my 1st guess was an alternator problem, causing odd voltage dips, surges or ripple on the 12v supply to all modules. A neighbor had an intermittent problem where the engine would start, but sometimes not obey the throttle at all, just sat at idle. That was fixed by changing the alternator.

The park sensors are quite likely to be easily upset by odd voltages. The ECU software can also get upset by them.

I would expect to see more error messages though. Have you tried reading DTCs in the period where it will not start. It seems like the 40min wait could be for the ECU to fully shut down, and clear some codes or an internal condition that is preventing starting.

Also check all fuses, esp ECU ones, in the engine bay fuse box. Some of these supply standby power to the ECU, etc.

 

  • 1 year later...

Have you sorted your problem? I experience exactly the same problem on my 2013 ford S max 2.2 200bhp

5 minutes ago, emanuelnistor said:

Have you sorted your problem? I

Andy probably still has the fault, it's only been a year since he was last here.

Might be a good idea to start a new thread with your problem.

  • 4 weeks later...

Hi everyone. 

Coming up with an update and the way i fixed the problem.

I had my dpf gutted in the past and been to a so called tuner to do remap. He hasnt done a very good job and the worst part he has hidden all errors that would involve exhaust gas temperatures.

Long story short. The 4th exhaust temp sensor (last one after dpf)  failed and would put the car in limp mode...but as i specified above. So ecu kicks in with the protection but would not show the error code saying the sensor failed as its been hidden previously by the tuner.....so i did written the original file back on the car...found the error code saying sensor failed. Changed the sensor and now the car revs normally amd drives normally. I then went to a proper tuner to have a profesional remap and happy days. (Also to specify...the remap i had done first would show dpf load and dpf soot 30% raising...which should be 0% with a proper dpf of remap...which turns the fisrst one was a failed remap...so be aware if you choose to gut your dpf ..make sure you do a remap with profeasionals.

 

Hope this will help other fellow Forders 🙂

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.