Thanks for the feedback! So, I'm thinking Lambda challenges..
After the driving yesterday I didnt see any soot in the exhaust. So today I drove it via the local inspections office and managed to get a free soot check on the vehicle - plugging it in to the same machine that failed the vehicle before the remap of injectors. This time it passed the standard "official" test they are doing (connect plug to exhaust then one quick push full throttle). I had the multiecuscan connected and noticed that the second Lambda wasnt showing real values but instead only displayed "100%" - instead of following the first lambda.
At this time the inspection guy tried a new exhaust tester they are prototyping which measures particles on idle engine. Since the second lambda still was showing 100% test result was "4 million particles" - approved measures is max 1 million with this prototype test tool. We waited a minute - the secondary lambda suddenly started showing "normal values" and we did this test again - and test results was just above approved limit if 1.4 million.
Questions:
A - Now when I display multiecuscan on off engine I can see the two lambda sensors displaying different values. One i 100% and one is 0%. I believe this is a sign that the post dpf-lambda is broken/glitchy?
B - Should I simply give the engine more time to warm up secondary lambda sensor or change it right away?
C - Noticed software is 0028 - is it worth changing to 0032 even if the lambda thing above might solve sooting?
D - The potential differences on desired air intake graphs in the previous message - what can I do/check more on that one?
After the driving yesterday I didnt see any soot in the exhaust. So today I drove it via the local inspections office and managed to get a free soot check on the vehicle - plugging it in to the same machine that failed the vehicle before the remap of injectors. This time it passed the standard "official" test they are doing (connect plug to exhaust then one quick push full throttle). I had the multiecuscan connected and noticed that the second Lambda wasnt showing real values but instead only displayed "100%" - instead of following the first lambda.
At this time the inspection guy tried a new exhaust tester they are prototyping which measures particles on idle engine. Since the second lambda still was showing 100% test result was "4 million particles" - approved measures is max 1 million with this prototype test tool. We waited a minute - the secondary lambda suddenly started showing "normal values" and we did this test again - and test results was just above approved limit if 1.4 million.
Questions:
A - Now when I display multiecuscan on off engine I can see the two lambda sensors displaying different values. One i 100% and one is 0%. I believe this is a sign that the post dpf-lambda is broken/glitchy?
B - Should I simply give the engine more time to warm up secondary lambda sensor or change it right away?
C - Noticed software is 0028 - is it worth changing to 0032 even if the lambda thing above might solve sooting?
D - The potential differences on desired air intake graphs in the previous message - what can I do/check more on that one?
Attachments
Last edited: