Technical ECU Fault codes?? HGT Engine cutting out

Currently reading:
Technical ECU Fault codes?? HGT Engine cutting out

metalgod23

New member
Joined
Feb 13, 2008
Messages
12
Points
3
recently had problems with my Bravo HGT 2.0 155 cutting out while running/driving usually when slowing down or about to stop. Left it in a garage who have changed the battery as it was duff (expected as I was planning to change in soon). Now they ran diagnostics and 3 fault codes have appeared.
P0130
P0335
P1653
of which the last one cleared and the firt 2 remain. The engine is still cutting out.
"Does anyone know what the fault codes mean?? " I found these online.
P0130
Ox Sensor Circuit Malfunction (Bank 1 Sensor 1)
P0335 </SPAN>
Crankshaft Position Sensor A Circuit Malfunction but some say this is 'Engine speed sensor' or 'rpm sensor' fault.

</SPAN>any ideas why the engine is cutting out?

They have suggested replacing the SPEED SENSOR which costs about 25 quid... but that is not guaranteed to fix the problem!! Could the speed sensor cause a engine cut out and bring up these fault codes??:confused:

Any help much appreciated as am afraid the bills are going to run on :((... and the problem hasnt gone away... :cry:

Many thanks fellow users.
 
if they are proper EOBD codes then these descriptions are accurate, but they may not be, it depends on the scanner that was used. the lambda and crank sensor are common faults, but get them to check the wiring to the lambda sensor and make sure the connector is ok, and the ECU is responding to its output, i.e. switching from rich to lean. probably best to replace the crank sensor, they can become intermittent.
 
Hi stylers, thanks for your reply. I will talk to the garage about your suggestions. The Speed sensor is about 25 quid but the crankshaft sensor is about £150 apparently!! which is why am fretting a bit.... can the speed sensor throw up the same error codes as the crankshaft sensor? i.e. P0130
or P0335??
Cheers.
 
the crankshaft sensor is the only one you should be worried about. some might call it a speed or RPM sensor but thats incorrect. maybe they are thinking of the vehicle speed sensor (VSS). it is also fed to the ECU, but that would cause a different fault code, and would be unlikely to stop the engine. concentrate on the lambda and crank sensor. hopefully they are not just throwing parts at this. I doubt a crank sensor is so expensive, but you could look it up on eper.
 
Some call it an engine speed sensor or rpm sensor as this is one of its functions. by timing the speed of the crankshaft, you can get the engine rpm. Its primary function however, is to figure out the position of the crankshaft (and so camshaft) at any given moment for timing injection and ignition. If it is getting a bad signal from the crankshaft sesor, its possible the disruption to igniton and injection could cause the lambda to think the engine is running lean and give bad readings.

Firstly i'd try clean the sensor - they often get dirty and so can't 'read' the notches on the crankshaft. Also check for damage to the wiring to the sensor. If this doesn't work replace the sensor and reset the ECU. try run it then. if lambda still comes up after a while, you might have to empty your wallet :(
 
the crankshaft position sensor is the problem, people call it many different things, but to prevent confusion make sure the sensor they change is the sensor that reads the flywheel.

since your lambda sensor fault is a circuit malfunction then the lambda may be faulty too (rather than simply reading out of range due to the crank sensor issue)
 
Last edited:
Problem sorted!! It was the 'CRANKSHAFT SENSOR'!!! Cost about £28, and as soon as it was replaced both faults went away. Looks like the lamba sensor fault in the manifold was a direct result of the crankshaft sensor fault. The car is back on the road now. New battery, new sensor = not much. Labour = rip-off!! atleast I know more about the potential problems and so have some confidence to tackle any issues in the future myself. Am thinking of investing in a ECU diagnostics/reader. Any suggestions??
Many many thanks chaps for all the guidance.... top stuff!!:slayer:(y)
 
a diagnostic code reader is a bit of a hassle on your car, it is not eobd compatible so you need special software that can use the fiat protocol, plus it doesnt even have an obd connector, it has 3 pin connectors so you would need to use some lengths of wire to physically connect your interface to the car.
 
Last edited:
a diagnostic code reader is a bit of a hassle on your car, it is not eobd compatible so you need special software that can use the fiat protocol, plus it doesnt even have an obd connector, it has 3 pin connectors so you would need to use some lengths of wire to physically connect your interface to the car.

Hmm so it seems, I havent had any success finding a EODB or ODB2 connecter inside the car. Found the 3 pin Fiat diagnostics connection though.
I thought petrol cars made 2001 and later have the EODB/ODB2 connector under the steering wheel/fusebox/pedals??

The previous fault with the crankshaft sensor was read out by a private garage.. wonder how they managed to diagnose it without the EODB/ODB2 socket in the car.. any ideas?

Fiat Bravo HGT 155, Registered 2001 August.

Cheers.
 
Last edited:
many garages have universal readers that can use any protocol (and even switch the protocol automatically to suit), some of these kits even come with a variety of connectors to suit any car, but even without the connector adapter you can easily connect an obd connector to the car's 3-pin connector using some wire. alternatively they may have a colllection of seperate readers for most makes, this is the more expensive option, but its easier to get brand specific readers because there are so few universal ones available.
 
could anyone tell me if this the same problem as with what is happening to my 1.8 hgt punto? it has been on the diagnostic cpu, but no faults appear! the engine jus doesnt hold its revs when no throttle is applied. ive been told it could be the tdc sensor??? would this show up on cpu?
 
a TDC sensor (aka crank sensor to avoid confusion) fault usually does not show up during a diagnostic, however a fault with this sensor prevents the sparkplugs from sparking so i do not think it can be your problem.

first i would clean inside your throttlebody and replace the idle speed controller (on the throttle body) with a scrapyard part. both these issues are common and can result in the car stalling at idle.
 
hi, my bravo 2.0 hgt wont spark, had diagnostics done and the garage said they cant read anything from it. have had new camshaft, knock and crank sensor fitted, new leads and spark plugs and still nothing. do you have any ideas why the ecu is not responding to the diagnostics machine.
 
hi, my bravo 2.0 hgt wont spark, had diagnostics done and the garage said they cant read anything from it. have had new camshaft, knock and crank sensor fitted, new leads and spark plugs and still nothing. do you have any ideas why the ecu is not responding to the diagnostics machine.

Take it Fiat for a diagnostic, my guess it was done elsewhere and not Fiat. Could be ECU gone faulty but thats rare.
 
hi, my bravo 2.0 hgt wont spark, had diagnostics done and the garage said they cant read anything from it. have had new camshaft, knock and crank sensor fitted, new leads and spark plugs and still nothing. do you have any ideas why the ecu is not responding to the diagnostics machine.
the bravo is not eobd/obdII compatible so most diagnositc machines will not be abe to communciate with the ecu, and even if they could most garages dont know how to connect to the car's 3 pin connector or even which connetor to use.

on your bravo is the orange key code light remaining lit when you try to start? if it is then your immob is the problem, and it can usulaly be fixed by wiggling the wires inbetween the ignition switch aerial and the codebox behind the dash. failing that check the immob fuse and its fuseholder for rust.
 
Last edited:
hi, i know its not the ecu as i've had a new one fitted along with new transponder, locks and ignition barrel. the diagnostics was done by a former fiat employee and he just cant get any info from the ecu. spent to much money on this car now so i dont want to give up. please some-one help me.:bang:
 
the bravo is not eobd/obdII compatible so most diagnositc machines will not be abe to communciate with the ecu, and even if they could most garages dont know how to connect to the car's 3 pin connector or even which connetor to use.

on your bravo is the orange key code light remaining lit when you try to start? if it is then your immob is the problem, and it can usulaly be fixed by wiggling the wires inbetween the ignition switch aerial and the codebox behind the dash. failing that check the immob fuse and its fuseholder for rust.

the key code light goes out but the injector light flashes and relay clicks. there is fuel pumping throu but no spark.
 
if we assume the ex-fiat employee is doing everything correctly, and the ecu is definately ok, then realistically the only problem can be a fault on the 3 wires that go from the obd connector to the ecu. if that is not the case then either the ecu is faulty or the method of diagnosis is not correct.


which connector is he trying to use? (what is its position?)
 
:worship:
Hi,

I was hoping my fault is similar to these.

I have a Fiat Ullysee 1999 2.0 petrol.. The engine management light comes on and shuts down the engine, although sometimes it just drops rev's completely then restarts.

I have had a diagnostic done on it and it showed the MAS air flow sensor, which I replaced but same fault, we then cleared the fault codes and tested again which then showed it required a MAD sensor and Crankshaft timing sensor.

I fitted the MAD sensor but to no avail, still same fault. I now have the crank sensor (12.50 by the way) but can not locate it to change it !!!

Any one got a red dot so I can stick it where i need to be looking please ?

Many thanks
 
ullysee is a eurovan so it uses the PSG XU10 engine (from peugeot).


lucky i have done a crank sensor on a citroen xantia with the same engine. it is a very common problem on the XU10 engine.

the sensor is fitted to the gearbox bell housing. it is roughly in line with the flywheel- meaning it is right up close to the engine.
 
Back
Top