106 Problems

[MrG 3]

HI

 

Apologies for this as its not a 205 related question more about a small 2000 1.1 106 zest that my wife has.

 

Scenario is:- Engine management light comes on, we have it checked out and its a lambda sensor, but we reset it for now and its fine. 4 weeks later it comes back on, so into the garage it goes, they try to read the codes but it throws up 1, then 2 then 4, then back to 2? Their reader is on the way out so as they're getting a new one we agree to come back when its there, car seems to be OK. Then a few weeks later we get a call to come back down, so we do, light is on again and they read it, but its throwing up both sensors (post and pre cat) & a coil pack.

 

Replace a coil, not that, change the sensors, not that, so put the old ones back on & so we take it away (but still with the light on) but they didn't do the full checking as we needed the car back, slight misfire at idle appears as well?

 

So on the Monday Mrs G takes it to work only for it to break down just before she gets there, won't start and when it does it cannot get over 20mph. Tow the car back, very low (or no?) compression on No 1 and upon stripping down a valve has dropped together with some damage to the others? So a head overhaul. Fine, we don't mind as we'd rather have a car we know is all OK for the next number of years.

 

Car is back a few days and the bloody light re-appears, so we have them read again and it throws up the post cat sensor, so we have them both replaced, light is out until today when the bloody infuriating light appears on the dash? So its got to go back again and this time Mrs G is not happy at all.

 

So ideas on what it could be?

 

Car drives really nicely now to, before it smelt of fuel but not now. slightly uneven idle but that's it. Very annoying.

[welshpug 1,622]

Check the wiring.

 

I may be able to help later with wiring diagrams.

[MrG 3]

Thanks WP, well all that seems in order, no leaks to speak of but we've been advised that its quite possibly the cat as the same code is being thrown up indicating sensor or cat, and as the sensors are new (genuine items to) then the last thing is the cat? We'll leave the light on until we have the money to replace the cat.

[DamirGTI 325]

Check if the CAT is blocked .. can do that quick just with an IC temp. meter , or an vacuum gauge .

 

Ditto , id check the wiring also .. someone might cross wire up the lambda sensor wires if they're aftermarket part ie. , without the OE plug on connector on the end .

 

If it keep's on throwing the codes after a replacing the suspected part , and erasing the codes means that there's still something wrong .. so don't take diagnostic codes as a granted and off replace ASAP , it just guides you to the suspect area/component , for sure if it says "MAP sensor" could be a bad part but can also be something simple as a MAP vacuum tubing crack , or MAP wiring problem etc.

 

D

Edited February 19, 2013 by DamirGTI