caused by german air ???
Discussion
Hi,
a German T350C driver needs interpretation of different lambda signals at idle-speed.
Could someone help me?
The heart starts only up with a throttle-kick and runs until warm up with 700 rpm.
Is one of the lambda-sensors damaged?
Cheers from Germany and thank you for your answers from Siegmar.
a German T350C driver needs interpretation of different lambda signals at idle-speed.
Could someone help me?
The heart starts only up with a throttle-kick and runs until warm up with 700 rpm.
Is one of the lambda-sensors damaged?
Cheers from Germany and thank you for your answers from Siegmar.
Edited by tvr2367t on Tuesday 30th March 17:01
Edited by tvr2367t on Tuesday 30th March 17:02
Is it possible for you to show the whole screen in a picture, not only the graph?
If you dont show the graph legends in the picture, it´s hard to see which graph is lambda 1 and lambda 2.
On my Cerbera SP6 the lambdas are on 0 volts most of the time and jumps up to 1.5-1.8 volts about every half second, looks like spikes in the signal. That is how it should be.
If you dont show the graph legends in the picture, it´s hard to see which graph is lambda 1 and lambda 2.
On my Cerbera SP6 the lambdas are on 0 volts most of the time and jumps up to 1.5-1.8 volts about every half second, looks like spikes in the signal. That is how it should be.
Hi Siegmar.
This is what it says in the diagnostic handbook:
These faults are shown if the lambda sensor signal rises above 1.7V. If it occurs the MIL lamp will be turned on. Correct operation of the lambda sensors is best checked by viewing the real time logging screen. The sensor signal should alternate between 0 V and 1-1.5 V and never stay at a mid voltage (0.4-0.7V) position.
Lambda 1 is the front set of cylinders (ie. 1,2&3) and lambda 2 is the rear set (ie.4,5&6).
Lambda fault can be caused by:
1. Water ingress into the lambda sensor’s connector or wiring.
2. Mechanical damage to sensor or wiring , causing a short between the supply and signal wires.
3. Faulty sensor
That should help. If one lambda is freezed at one voltage it is probably knackered.
Regards,
Björn.
This is what it says in the diagnostic handbook:
These faults are shown if the lambda sensor signal rises above 1.7V. If it occurs the MIL lamp will be turned on. Correct operation of the lambda sensors is best checked by viewing the real time logging screen. The sensor signal should alternate between 0 V and 1-1.5 V and never stay at a mid voltage (0.4-0.7V) position.
Lambda 1 is the front set of cylinders (ie. 1,2&3) and lambda 2 is the rear set (ie.4,5&6).
Lambda fault can be caused by:
1. Water ingress into the lambda sensor’s connector or wiring.
2. Mechanical damage to sensor or wiring , causing a short between the supply and signal wires.
3. Faulty sensor
That should help. If one lambda is freezed at one voltage it is probably knackered.
Regards,
Björn.
Hi,
thank you for reply.
The hight of the peaks is between 1 and 1,1 Volts,
but the regulating frequency between lambda 2 (turquoise)
and lambda 1 (gray) is totally different.
The lambda 2 shows slower intervention as lambda 1.
If Peppe is right the lambda 2 signal must be faulty,
because lambda 1 shows intervention every second,
the signal of lambda 2 shows intervention breaks up to 5 seconds.
Does someone can show a picture of his speedsix lambda-sensor intervention times?
Thank you.
Siegmar
thank you for reply.
The hight of the peaks is between 1 and 1,1 Volts,
but the regulating frequency between lambda 2 (turquoise)
and lambda 1 (gray) is totally different.
The lambda 2 shows slower intervention as lambda 1.
If Peppe is right the lambda 2 signal must be faulty,
because lambda 1 shows intervention every second,
the signal of lambda 2 shows intervention breaks up to 5 seconds.
Does someone can show a picture of his speedsix lambda-sensor intervention times?
Thank you.
Siegmar
Edited by tvr2367t on Thursday 1st April 06:04
It seems as both lambdas work. Have you done a proper set up of the engine?
Looks as the rear half of the engine is running a lot leaner than the 3 front cylinders. Start with balancing the throttles with a syncrometer and then use the software to reset throttlepots and adaptives.
Some years ago I wrote how to do this in a topic.
//Peter (Sweden)
Looks as the rear half of the engine is running a lot leaner than the 3 front cylinders. Start with balancing the throttles with a syncrometer and then use the software to reset throttlepots and adaptives.
Some years ago I wrote how to do this in a topic.
//Peter (Sweden)
Hi Peter,
while the lambda-sensor2 output signal is low,
the ecu extends the injection period, so the rear cyliders are getting rich.
then the lambda-sensor must notice, that the AFR is rich and have to send
a low signal in time.
In my meaning the lambda-sensor2 don´t notice the rich AFR in time,
the intervention seems too slow.
Is the lambda signal at idle speed of interest for the ecu in general?
I reckon a electronic, not a mechanic fault, because the problem came overnight.
Cheers
Siegmar
while the lambda-sensor2 output signal is low,
the ecu extends the injection period, so the rear cyliders are getting rich.
then the lambda-sensor must notice, that the AFR is rich and have to send
a low signal in time.
In my meaning the lambda-sensor2 don´t notice the rich AFR in time,
the intervention seems too slow.
Is the lambda signal at idle speed of interest for the ecu in general?
I reckon a electronic, not a mechanic fault, because the problem came overnight.
Cheers
Siegmar
Edited by tvr2367t on Thursday 1st April 15:19
Edited by tvr2367t on Thursday 1st April 15:23
Edited by tvr2367t on Thursday 1st April 15:26
Edited by tvr2367t on Thursday 1st April 15:27
tvr2367t said:
Hi Peter,
while the lambda-sensor2 output signal is low,
the ecu extends the injection period, so the rear cyliders are getting rich.
then the lambda-sensor must notice, that the AFR is rich and have to send
a low signal in time.
In my meaning the lambda-sensor2 don´t notice the rich AFR in time,
the intervention seems too slow.
I have never heard about a lambda sensor that has become slow but maybe it can happen. They usually work or not work at all, not "half" working.while the lambda-sensor2 output signal is low,
the ecu extends the injection period, so the rear cyliders are getting rich.
then the lambda-sensor must notice, that the AFR is rich and have to send
a low signal in time.
In my meaning the lambda-sensor2 don´t notice the rich AFR in time,
the intervention seems too slow.
tvr2367t said:
Is the lambda signal at idle speed of interest for the ecu in general?
The closed loop emision control that is run by the ECU works from idle speed to 3500-4000rpm, above that there is no use of the lambdas from the ECU. The lambdas are also disconnected when you push the throttle down fast. That is measured by the rising time of the throttle values, if the slope is steeper than a certain value the closed loop control is switched off.tvr2367t said:
I reckon a electronic, not a mechanic fault, because the problem came overnight.
What is the problem? Is it lumpy idle? Hesitation? Loss of power? Smell of fuel?
Have you checked how the throttle pots work?
How do the adaptive maps look?
Cheers
Peter
Edited by Peppe on Thursday 1st April 22:43
Gassing Station | Speed Six Engine | Top of Page | What's New | My Stuff