9 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHHigh lambda and poor high speed hesitation
Leading reported evidence
Replace fuel pump and filter (failed
Performed · outcome unconfirmed
No successful repair reported for this finding.
0
Reported fixes
0
Unsuccessful attempts
1
Discussions
Read evidence and context
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that performed work without a confirmed outcome
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Performed · outcome unconfirmed · Original poster
I have changed the fuel pump and filter (failed to find the fuel pressure measuring point though).
Leading evidence: 'Replace fuel pump and filter (failed' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, The most frequently discussed action is 'Adjust mixture' (1 discussions). For that action, 0 discussions report a resolution and 0 report an unsuccessful attempt. No action has an explicit, attributable resolution report under the current rules. These are forum reports and suggestions, not a confirmed diagnosis.
Source reports, not a diagnosis or a success probability. Counts refer to discussions and can overlap.
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that performed work without a confirmed outcome
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Performed · outcome unconfirmed · Original poster
I have also seen that TPS only indicates 69% at full throttle which is a little weird, I therefore changed the TPS but was given the same result, still 69%
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that contain suggestions
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Suggestion · Original poster
as base and then adjust the mixture with the difference between
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that contain suggestions
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Suggestion · Original poster
I have checked the data using the Durametric monitoring and the Lambda value is generally around 1.00 as it should be but after the CEL is lit it indicates a value of 1,25.
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that contain suggestions
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Suggestion
If not within this range check the voltage directly at the TPS sensor on the signal return wire.
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Suggestion · Original poster
I have checked the data using the Durametric monitoring and the Lambda value is generally around 1.00 as it should be but after the CEL is lit it indicates a value of 1,25.
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Suggestion · Original poster
what is the effect of a stuck Variocam solenoid?, at what rpm does it activate?, the signal in Durametric indicates a solid 3.0 degrees throughout the range so no change there
Discussions that performed work without a confirmed outcome
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Performed · outcome unconfirmed · Original poster
I have also seen that TPS only indicates 69% at full throttle which is a little weird, I therefore changed the TPS but was given the same result, still 69%
Counts describe captured discussions, not unique people or a diagnosis. Author identities are not reliably stored. Exact duplicate evidence is counted once across matching discussions; one discussion counts at most once per action/state. Multiple repairs reported together remain a combination. Suggestions and failed attempts do not establish a fix. Matches cover whole discussions and can include related faults, model variants and incomplete threads.
9 eligible posts · 0 unverified posts · 1 discussions match the subject in their title or opening post.
Rennlist: 1 discussions
0 evidence records excluded for query context · 2 excluded by outcome qualification · 0 adjusted by outcome qualification.
1 acknowledgements have no verified action link; they do not establish a repair result.
Outcome without a verified action link
what is the effect of a stuck Variocam solenoid?, at what rpm does it activate?, the signal in Durametric indicates a solid 3.0 degrees throughout the range so no change there
Hej,
my 3,4 C2 have developed a severe full throttle hesitation(hick-up)above 4k rpm. Also the CEL comes on indicating Lambda out of range (lean on both banks) at very light throttle and warm running.,
I have checked the data using the Durametric monitoring and the Lambda value is generally around 1.00 as it should be but after the CEL is lit it indicates a value of 1,25. The car still runs ok at this point.
All in all the car runs ok with about 50% of the throttle but feels choked (to much air) on higher throttle openings. The engine runs stronger if you back out of the throttle (less air) at high rpm.
I have changed the fuel pump and filter (failed to find the fuel pressure measuring point though).
I have also seen that TPS only indicates 69% at full throttle which is a little weird, I therefore changed the TPS but was given the same result, still 69%
So I wonder what next?, shall Durametric display 100% TPS?
what is the effect of a stuck Variocam solenoid?, at what rpm does it activate?, the signal in Durametric indicates a solid 3.0 degrees throughout the range so no change there
:-/
Help anyone?
Low power at full throttle is normally associated with incorrect/restricted air/fuel OR restricted (stopped up) cats. Since you have some faults codes to help, start there.
Test fuel pressure.
Disconnect MAF sensor and drive ...NOTE: will set MAF faults
Monitor MAF specified valve vs actual value
Inspect MAF sensor for cobb webbs, leaves ect. Can be an issue especially after changing air filters.
ASSUMING you have E-gas, manually open butterfly and see if you get high 90's% percent throttle value( if you cable throttle just floor the pedal)
More detail for your lamda readings will be necessary for further help
I have only looked at the CATs from the exit side and they looked ok there, I'll give them a look before the cats as well.
I'll measure the fuel pressure as well.
I'll give it a go to disconnect the
MAF
Regarding the TPS (my car has mechanical throttle), it registers 69% at full throttle. I have inspected the throttle flap itself and it is fully open at 69%.
The weird thing is that when I remove the TPS and turn it by hand I still only get a max 83% which is still too low. I have tried both the old TPS and the new and they both record the same numbers so I do not think I has an issue at the TPS itself.
I will do a run and make a log
Regarding the MAT, I assume you mean that I should compare the
Actual MAF
towards the
Specificated MAF
which is the calculated number shown by Durametric right?, if so the the calculated number is way too low, (or the measured is too high)
However isn't the calculated number(Specified MAF) based the parameters of TPS, temperature and RPM? which means that if the TPS value is way wrong then the
Specified MAF
will be way wrong too?
Is the ECU dependant on the
measured MAF
or the differentiated calculation between the
MAF
and the
Specified MAF,
basically it uses the
Specified MAF
as base and then adjust the mixture with the difference between
measured MAT and specified MAT?
As I said earlier, Lambda values behaves correct for both banks at around 1.00 until something goes wrong then it becomes 1.25 which is too lean
You are exactly correct, IF the TPS is wrong, the specified MAF will be wrong also.
The DME uses TPS, Temp, and RPM, for the specified MAF table and is the predicted MAF value, but the DME uses the actual MAF value for the air/fuel ratio. IF the actual and specified values are too far apart it is supposed to set a fault code, but I have seen faulty actual MAF readings that were quite a bit off and no codes set.
The TPS should have three wires, one 5v wire, one ground, and one signal return wire. Test for 5v, and a good ground, something doesn't sound right with the TPS, should get a signal of over 90%..(above 4.5v)
I suspect you have a wiring or ground issue..
I'll check that,
I did a log this morning, it has a very low sample rate but you clearly see what I mean.
The first 15 minutes is the school run hence the low Throttle opening, it ends at about 7:53 (long idle period) after that I am picking up the pace a little.
I have sampled the MAT and specified MAT values and you can see the massive difference between the two, should these two values follow each other?.
The car runs really well with about 50% throttle(gas pedal procentage, not TPS) all the way to the red line but any more throttle opening and it feels choked.
Lambda is mostly behaving as I expect, but the Measured MAT is vey high compared to the throttle opening but this must be due to a failure in the TPS somewhere.
Still though there are a number of samples in the measurement where the RPM is around 3000, TPS is above 25% in where the Lambda is bottoming out at 1,25, a clear lean situation.
I guess to have such a situation occasionally is not a problem but when they become too persistent the ECU will log an error.
I'll measure the voltage at the TPS end tonight.
I measured the voltage at the TPS end, 0; 5 and 5,6v respectingly.
After some more logging it looks like the lambda sensors show high values (1,25) after the car is restared hot after a 10min shut off, the cat has then lowred in temperature by 200degrees to around 250C
it takes a while for it to come back up over 350-400C but then it measures correctly again.
I looked at your log, The specified MAF and actual MAF are way apart..
Also I see that your TPS % never got over 67%, that is a problem. You should be able to see the actual TPS voltage on Durametric. Typical value should be .7v-.9v at closed throttle and 4.1v- 4.5v at full throttle, and should go up smoothly as throttle is depressed. If not within this range check the voltage directly at the TPS sensor on the signal return wire.