Hi,
I am trying to solve a problem with an AGU engine 1.8t with r-tech map.
In 3rd when accelerating at about 4000 rpm it seems all boost and power just cuts out, like the turbo stops. and generally the engine feels down on power throughout the rev range.
recently i had a new cambelt and they also replaced a split vacuum pipe between the inlet manifold and somewhere just in front of the block.
Before this, engine would pull like a train, very very strong.
I have checked for fault codes and it keeps throwing up 2 codes but not all the time, i clear them and then drive a bit and eventually come back:
00575 - Intake Manifold Pressure
11-10 - Control Limit Not Reached - Intermittent
and
00561 - Mixture Adaptation14-00 - Adaptation Limit (Add)
only other thing to mention is that when revved to 3k, I then let it idle, when this happens the lambda reaches -17% this seems v.high compared to what i have read, could i have a dodgy lambda sensor, or maf? maybe n75?
anyone have any ideas what i can do, i have a few logs from vag-com, I am not sure if i have logged the correct things. Can get new logs if it helps.
log 1 - hard drive (max i could do)
log 2 - idling lambda measurements
Kind Regards and thanks for any help in advance
Aaron
I am trying to solve a problem with an AGU engine 1.8t with r-tech map.
In 3rd when accelerating at about 4000 rpm it seems all boost and power just cuts out, like the turbo stops. and generally the engine feels down on power throughout the rev range.
recently i had a new cambelt and they also replaced a split vacuum pipe between the inlet manifold and somewhere just in front of the block.
Before this, engine would pull like a train, very very strong.
I have checked for fault codes and it keeps throwing up 2 codes but not all the time, i clear them and then drive a bit and eventually come back:
00575 - Intake Manifold Pressure
11-10 - Control Limit Not Reached - Intermittent
and
00561 - Mixture Adaptation14-00 - Adaptation Limit (Add)
only other thing to mention is that when revved to 3k, I then let it idle, when this happens the lambda reaches -17% this seems v.high compared to what i have read, could i have a dodgy lambda sensor, or maf? maybe n75?
anyone have any ideas what i can do, i have a few logs from vag-com, I am not sure if i have logged the correct things. Can get new logs if it helps.
log 1 - hard drive (max i could do)
log 2 - idling lambda measurements
Kind Regards and thanks for any help in advance
Aaron