A poor earth would cause the lambda sensor (amongst other things) to not be 100% efficient.

DarrenClark said:

Would the stored info of the lambda sensor cause the new one we fitted to not be 100% efficient?

Click to expand...

No. Stored codes will not affect any component.
Usually after 3 good starts/operations, any fault light will extinguish, but stored codes could remain indefinitely.

We need to know what is happening now, so the codes need to be cleared, then see if they reappear. That will show whether they are history or current.

Current operation of the temp sensor and lambda would be most helpful, not just pass/fail.

I had cleared the codes the other day and they haven't come back, I have had car running on and off a few times and the lambda and sensor have been changed.

The only option it gave me on the Iaw2 was pass or fail.

Iv had it connected up today and used the graph function to get some results to see if it shows anything to me most seem ok but not sure to be honest.
I took a few videos to get some information however they not the best as the light on the laptop screen was reflecting.

When I started the car it sounded a bit raspy in the exhaust and had a bit of water coming out of the exhaust pipe, also got video with revving to. don't know if it may help or not.

I have attached a video of the lambda probe graph when its cold and then another one after the engine had been running for a little bit.

Then there was also the water temp graph which shows the change in water temp when its warming up.


The only other thing I check was the battery voltage which with-
only engine running was at 14.10-14.25v
everything electrical on - 12.0-12.2v
with everything on when revved it went to 13.7-13.9v then dropped back down to the 12.2v
didn't know if it would be relevant to anything such as earthing or something.
for some reason my files aren't uploading , saying its invalid will try to sort as soon as i can

worked out had wrong file type needed to be a zip file, so hopefully the should work now.

Ok so some of the files seem to be to big even zipped,
The lambda probe correction when first started was reading at 1.00
When warm it was reading up and down between 1.05 and 1.02 the graph was continually changing making alterations between the readings and everything in between.

I have had a look at car again today and noticed the exhaust was smoking a bit excessively , when I looked under the bonnet I could see some coolant leaking around the head so I'm guessing the head gasket has gone. Would this effect emmisions if it was on its way out ?

Any coolant or oil into the combustion chambers will affect the emissions. So this needs sorting first.

We cleaned out the engine and put the new gaskets on , have taken it to mot centre and the Co2 reading is still high 4.01

Surely that's the CO reading, not CO2?

A high CO reading says running rich, or catalyst not working.

If the engine had been pumping burnt oil, or unburnt oil, or coolant into the catalyst, it may well be contaminated and needs replacing.

This thread is now getting very long, and therefore more difficult to follow the string of events. Re-reading the whole thread is tedious. Now might be the time to close this one, gather together the important details, in chronological order and start a new post, which would be clear and easier to follow. However, following the readings of temp and O2, and possibly fuel use, as the engine warms up would be very useful, but that would need the full version of MES.

If you have got access to an infra red temp sensor gun thing, try taking the car for a run or you could leave it idle for god knows how long (maybe 1/2 hour) and measure the temperature of the cat before and after.
The temperature should be hotter at the back than the front, so if the temp is less than roughly 75 degrees at the back of the cat it is mostly likely not working efficiently so will need to be replaced and would cause high CO as my cat is rattling (and almost non-existent) and has high CO
Hope this helps

crazySnublz said:

If you have got access to an infra red temp sensor gun thing, try taking the car for a run or you could leave it idle for god knows how long (maybe 1/2 hour) and measure the temperature of the cat before and after.
The temperature should be hotter at the back than the front, so if the temp is less than roughly 75 degrees at the back of the cat it is mostly likely not working efficiently so will need to be replaced and would cause high CO as my cat is rattling (and almost non-existent) and has high CO
Hope this helps

Click to expand...

even gauging the temps of the 4 x exhaust manifold branches could help pinpoint poor combustion,
Charlie

Thanks for the help , I don't really want to risk taking it out but could try it on drive as have access to an infared temp sensor from work.
I have purchased the full version of multiecuscan so hopefully I can get the information needed from this.
Yes sorry did mean co not co2 my mistake.

I will have a look at getting the temp , O2 and the fuel use as you mentioned.
What I could do is edit the first post to include all information and to tell people to skip to what will hopefully be my results at the end. Many thanks the for help

Ok im a bit baffled by something on multiecuscan. The engine speed doesnt seem to be reading right as its showing the idle rpm of 62880000000rpm ???

Where as on the IAW scan 2 the rpm seems to be right at 943rpm on idle does anyone know what could be the cause of this , many thanks

DarrenClark said:

Ok im a bit baffled by something on multiecuscan. The engine speed doesnt seem to be reading right as its showing the idle rpm of 62880000000rpm ???

Where as on the IAW scan 2 the rpm seems to be right at 943rpm on idle does anyone know what could be the cause of this , many thanks

Click to expand...

Either you've selected the wrong ECU or there is a bug in their program (they have had this issue with other ECUs in the past...).

There was only one option for a 899cc seicento on Multiecuscan