29 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHCEL issues
Leading reported evidence
Clean maf and still get the codes and rough idle
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 cleaned the Maf and still get the codes and rough idle.
Leading evidence: 'Clean maf and still get the codes and rough idle' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, the most frequently mentioned possible cause is 'oxygen sensors' (1 discussions; 0 report identifying it and 1 suggest it). The most frequently discussed action is 'Clean maf and still get the codes and rough idle' (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
Thanks, I did use that site when I ordered/replaced my MAF.
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 suspect a cause
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.
Suspected cause
The computer DOES NOT think the problem is with the O2 sensors.
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.
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
I have the print out of mine (from the Porsche diagnostic thingy that hangs from the steering wheel) before replacing the 02 sensor left bank ahead of cat and after.
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
I have the print out of mine (from the Porsche diagnostic thingy that hangs from the steering wheel) before replacing the 02 sensor left bank ahead of cat and after.
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
Tippy I just finished using the Durametric had some fault codes which it does narrow down your troubleshooting time, I had on o2 sensor fail which showed an almost infinite resistance and the other was my MAF voltage went flat at .97V at any throttle setting, so changed it out.
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.
29 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 · 0 excluded by outcome qualification · 0 adjusted by outcome qualification.
0 acknowledgements have no verified action link; they do not establish a repair result.
Generation: 20261027T035758Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources
Could a hole in the oil separator breather hose cause fault codes p1124 and p1126? I have cleaned the Maf and still get the codes and rough idle. I noticed that I have a hole in this line because it has been rubbing on the intake system.
Thanks
To tell if you have a hole in the oil separator, remove the oil cap and see if the engine runs rough or dies. Also, place your hand over the filler tube opening and see if there is a strong vacuum pull. If you have the symptoms, the diaphram has cracked or ruptured.
Here are the correct indications:
P1124
Oxygen Sensing Adaptation Area 1 (Cylinders 1 - 3) - Rich Threshold
P1126
Oxygen Sensing Adaptation Area 1 (Cylinders 4 - 6) - Rich Threshold
You are running lean on both banks which could be caused by intake leak, wrong MAF signal, vacuum leak, bad plugs, low fuel pressure, leak in exhaust system, fouled injectors and other possabilities.
The errors are generated at idle.
hmmmm...those codes are right out of the workshop manual? This is DME 7.8.
Also same info as I posted from Renntech
RennTech P1124
P1124 167 Fuel pump relay output stage - Below Limit, 167 Fuel pump relay output stage - Above Limit, 167 Fuel pump relay output stage - Open circuit
Well since the car was just purchased the dealer is taking car of this problem. So when I get it back I will let you all know what he did to fix it. Thanks for the advice...
With those codes, I bet that the MAF is dead causing a lean condition.
According to 2 mechs and 2 service advisors, anytime they get 02 issues, it is always the MAF that is dead and the OBD II thinks it is the 02 sensors that are the issue since the 02 sensors will below min value. This was the case with my car.
The computer DOES NOT think the problem is with the O2 sensors. It is simply reporting that the sensors are working properly and that you have a lean condition in the exhaust of both banks. Cause could be any of a dozen number of things or combination of them. Any problem that allows more air into the engine or to the O2 sensors that is not reported to the computer or any problem that allows for less fuel to be delivered than the engine calls for.
Ok, based on what you said, it is a lean condition. 2 mechs and 2 service advisors told me that the MAF dying would cause codes from the 02 sensors If the 02 sensors are dead or simply out of range. Apparantly, the OPs MAF was not the case. But to others who have these issues, I have been chasing a similar lean condition for a week now and that is the reason I stated the MAF may be a possible cause. I will know tomorrow.
For the price you paid for the MAF, you could have purchased a scanner or scanning software for your PC. Why diagnose blind when there are the tools available for you to see?
From what I was told, a scanner or diagnostic machine can not actually pinpoint a problem component, only tell what is out of range possibly indicating the fault.
You have been told wrong. Voltage and voltage range along with temperature reading and calculated load is all you need to know if it is working. Nothing mystical about the sensor.
You might try cleaning the MAF first. Here is what I had when I sorted mine.
http://heelix.multiply.com/journal/i...is_on_update_1
http://heelix.multiply.com/journal/i...ack_of_the_MAF
http://heelix.multiply.com/journal/i...the_MAF_sensor
...
I have the print out of mine (from the Porsche diagnostic thingy that hangs from the steering wheel) before replacing the 02 sensor left bank ahead of cat and after. What are the parameters for the MAF?
I would like to know before I install the new MAF and waste my money.
Tippy I just finished using the Durametric had some fault codes which it does narrow down your troubleshooting time, I had on o2 sensor fail which showed an almost infinite resistance and the other was my MAF voltage went flat at .97V at any throttle setting, so changed it out. It is a must have for me.
OK It turns out that the CEL came on because of a leak in the brake booster hose. That part is not in the US and it has to be ordered from Germany. Oh well a week or so and we will see if that was the problem.
If any one wants to buy a MAF let me know.....
Thanks, I did use that site when I ordered/replaced my MAF. Great information!
This is what that site says:
So is the hot film MAF and the MAF two separate devices? Or is the component called the
hot film mass air flow
sensor and
mass air flow
sensor later used in the paragraph means those two terms are interchangeable?
Durametric shows two readable values, air mass and hot film MAF. My air mass at idle is ~13.25 kg/h and my hot film MAF at idle is ~1.33 V. Not sure how to apply the kg/h, but my voltage being 1.33 V should relate to what, the 9-7 V range of the operating voltage or the 0-5 V range of the output sensor?
get a tube in one ear and go along the brake booster cable with the other end of the tube and pin point the leak. Then tape around it at that point until your new part arrives from Germany. At least you will know in advance if you wasted your money sending off for as part that you may not have needed. Good luck.
hah! My guess is that the CEL never got fixed, or the fix did not last over 2 to 3 months...., but a few thousand $$ were spent b4 giving up.
I'd like to see a follow up also, if for no other reason than to reverse my pessimism.
This is a source reference. Confirm exact model applicability in the original material.
