Technical 2008 Fiat Ducato 2.3 L multi jet 130 ECU fault-Yellow anti theft LED present

Currently reading:
Technical 2008 Fiat Ducato 2.3 L multi jet 130 ECU fault-Yellow anti theft LED present

PaulR387

Member
Joined
May 23, 2024
Messages
11
Points
56
Location
Staffordshire
Hi, any help will be much appreciated on this matter, set off on holiday with our Swift Voyager695EL Motorhome that has a 2008 Fiat Ducato 2.3 L multi jet 130 diesel engine, after a couple of minutes I noticed the rev counter was not working then 30 miles on start coming back to life but not reading what it should have been(only half the engine revs) then on the motorway the vehicle cut out completely and we were a dead duck.
I was in a live lane so couldn’t get out the vehicle, I cycled the battery power and plugged in my OBD2 diagnostic tester to reset faults leaving me with a yellow antitheft and mobiliser LED on but still preventing the engine to fire, thankfully Highways arrived and towed me to the hard shoulder ***my advice to anybody in this situation is if you break down in a live lane immediately call 999***
The engine turns over but with the ECU having the yellow antitheft and mobiliser LED on it won’t fire.
Vehicle has gone off to my local garage who are normally pretty good but couldn’t get to the bottom of this so it’s come back and will be going to a FIAT approved repairer next month, being an electrician I can do a bit and working through what I can including removing and cleaning connectors, testing cable looms, and removing components down to PCB level.
I’d be grateful if anybody has had this problem before and can shed any light on the issue, thank you.
 
Last edited:
You have more than one problem going on .

I suggest you get multi ecu scan software and cables to connect to ecu.

Basic obd code reader will not give enough info.

In meantime check ground wires/connections. Check ring around ignition lock that reads key.

Check wire behind headlight that rubs on a metal stay
 
I agree with jackwhoo.

The x250s are known for earthing problems and water ingress into cable looms, connectors and sometimes even modules. It's all well described on the forum.

About the MultiEcuScan and interface: I've got myself a bluetooth interface dedicated to FIAT (EDIT: vscan STN1170, there's a new version 21xx or 22xx available now). It connects to all modules (so no need to have a cable + several adapters) within MES and then I'm using it with the Torque app on the road if a quick error check or reset is needed.

I had myself a couple of weeks ago a strange problem with the body module, disconnecting all connectors from it for some time helped :D Last year did the same with the engine module and magically somme recurring errors were also gone :D All connectors were dry and clean.

All CAN equipped cars (which in case of a Ducato starts with the x250) have to be considered as computers... Attached is how the interior of the BCM looks like...

I assume that resolving the problem with the BCM or its cabling shall resolve the immobiliser issue.
 

Attachments

  • 2024-05-01 17.12.22.jpg
    2024-05-01 17.12.22.jpg
    6 MB · Views: 63
  • 2024-05-01 17.12.34.jpg
    2024-05-01 17.12.34.jpg
    5.4 MB · Views: 67
Last edited:
You have more than one problem going on .

I suggest you get multi ecu scan software and cables to connect to ecu.

Basic obd code reader will not give enough info.

In meantime check ground wires/connections. Check ring around ignition lock that reads key.

Check wire behind headlight that rubs on a metal stay
Thanks for the help, got the passenger headlight out and checking the cable loom at the moment as an ex Fiat technician college tutor else has suggested this, ECU also removed and noticed some slight corrosion, will carry on tomorrow testing the wiring loom, cheers again
 

Attachments

  • IMG_4392.jpeg
    IMG_4392.jpeg
    2.8 MB · Views: 92
  • IMG_4393.jpeg
    IMG_4393.jpeg
    1.2 MB · Views: 63
Well done cracking on with it.

You will need multi ecu scan software
And cable/s

Several people on forum have bought from gendan and reported they were very good.
 
Thanks for everybody’s advice, looks like the OBD Autel reader was on the Money telling me the problem was with no communications to the ECU(U 1701)), sent the ECU off to Car tech who sent me a plug and play ECU and we are now all good, cheers, Paul.
 
Thanks for everybody’s advice, looks like the OBD Autel reader was on the Money telling me the problem was with no communications to the ECU(U 1701)), sent the ECU off to Car tech who sent me a plug and play ECU and we are now all good, cheers, Paul.
Please note that this change may have insurance implications. You need to talk to your insurers. Fitting an aftermarket alarm/immobiliser may mitigate the situation.
 
Back
Top