Hello peeps.....

Just fitted a full turbo back blue flame system yesterday (100 cel) and on my way to and from the Talbot all was well. However on my way to work this morning, the car 'lurched' (for want of a better description, almost like a few seconds of missfire) a couple of times and now my engine management light is on.....:confused: could this purely be as a result of fitting the sports cat (others have mentioned no problems/lights with this) or could i have damaged the lambda or something while fitting...????

I can't get to a vag com to look for codes until monday/tuesday unless someone in the cambs area has one sometime over the weekend... Any ideas????:(

I have a fancy exhaust on mine (not sure what type, I didn't fit it) but it brings the Engine Management light on regularly.

Mine has no cat, and one of the two probes is taped-up under the body.

Are both yours fitted into the exhaust system?

If I have the fault code cleared - (16804 P0420 Catalyst System, Bank 1 - Efficiency below threshold) - it comes back, sometimes after a day or so, sometimes it takes a week or more.

You should have bought a Supersprint or Miltek system infinitly better engineered

Sorry but they are

100 cel shouldn't bring up any errors or warning lights, unless its not properly fitted, so I don't think its to do with the exhaust, might have just been a coincidence and is something else.

@ HKPhooey - You have a straight through, 2.5" turbo back exhaust which in turn, brings up the warning light as there is a lack of a cat in there.

We spoke the other night, and as you know I have the turbo back Blueflame with the 100cel sports cat, and I have never had a problem with it.

If you had a misfire first, then try the coil packs, as one of those might be starting to break down and that can cause the misfire and warning light.

Pimpster, how's the hairdressers car???

Not sure if it is actually a missfire, just on steady cruise every ten seconds or so the car runs sort of rough for a second or two then ok again... Also at tickover the car will idle fine then revs will drop slightly and then pick up again (only talking 1-200 rpm). If you put ya foot down, all 'seems' well........ beats the **** out of me....

Should be able to hook it up to vag-com on monday or tuesday :confused: .

Just had vag on it and it has come up with code 16517, lambda slow to respond.....:confused: so is the lambda probe fubar or does the car need remapping to sort it....?? By the way, i cleared the code while i was at it and the light hasn't come back on.................YET.

Could be. Or what I have seen before is a poorly welded in boss for the probe meant the end of the probe wasnt even in the exhaust stream and therefore unable to rear the mixture content,

Does anyone know the p/n of a octy 02 vrs lambda sensor then??? might try out a new one anyway.....:(

A bit expensive just to try, id have a look at the exhaust first (unless they buggered the sensor fitting it).

If you have access to Vagcom, look at block 031 under varying driving conditions - this will show the "target" and "actual" Lambda value from the front sensor, so you can see if the sensor is behaving (the two readings should match pretty closely)

If you have access to Vagcom, look at block 031 under varying driving conditions - this will show the "target" and "actual" Lambda value from the front sensor, so you can see if the sensor is behaving (the two readings should match pretty closely)

Ta... i'll give that a go.

Doh...! My mates vagcom is unregistered so i can't use block 31 :(

any how a new fault code of 16514 'sensor malfunction' has just appeared so looking more likely to be the sensor.

OK, car is still running like a dog and is off to Jabba on Tuesday to try and sort. If it turns out i need a remap to 'tweak out' the problem, can i get a custom map and then add a fmic later? Or will this require 'tuning in' (if you understand)?? and therefore another remap coz i'm only wantin' to pay once.....!

Of course it may just need a sensor or summut....:confused:

Well it's been to Jabba today and their stumped too........:thumbdwn:

They said they would have changed the lambda probe to solve it (but i had changed it already) so their not sure......:confused:

all readings are as they should be/expexted so i/we are kind of screwed as to what to do to fix it..... maybe try another lambda? look at wiring (although ecu is seeing readings ok and probe heater works) so i just don't know.....

HELP!!!!!!!

If you have the old zorst put that back on, bit of a pain I know but at least it will point you in the right direction, zorst or summit else

If you have the old zorst put that back on, bit of a pain I know but at least it will point you in the right direction, zorst or summit else

Fair point mate ,,,,, but I didn't save the old "zorst" when I got the Blueflame Stainless System fitted. Who would & why?

You should have bought a Supersprint or Miltek system infinitly better engineered

Sorry but they are

i got a jetex on mine and its brilliant , i know cars with millteck and they prefere my system

Just had vag on it and it has come up with code 16517, lambda slow to respond.....:confused: so is the lambda probe fubar or does the car need remapping to sort it....?? By the way, i cleared the code while i was at it and the light hasn't come back on.................YET.

I had that code once and it was caused by a boost leak, also caused very rough running. It was the hose that has the metal sleeve on which you can get to from under the car. It looks fine to the casual glance as it pops in and out of the sleve on and off boost.

Cheers for all the replies but it's now sorted...... the 2 sensors were fitted the wrong way round (front in back and vice versa) .

Ah well, live and learn.........