12 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHP1128 P1130
Leading reported evidence
Adjust control times
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
♦ Contrary adaptation values in connection with misfiring point to incorrectly adjusted control timescheck control
Leading evidence: 'Adjust control times' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, The most frequently discussed action is 'Adjust control times' (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
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.
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
♦ Contrary adaptation values in connection with misfiring point to incorrectly adjusted control timescheck control
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.
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.
12 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 · 1 excluded by outcome qualification · 0 adjusted by outcome qualification.
0 acknowledgements have no verified action link; they do not establish a repair result.
Generation: 20261026T222516Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources
ACTUALLY, it doesnt mean its lean
it could be lean or it could be rich
without knowing if hes ablove or below limit value or without having fra/tra or rkat numbers or even looking at the airmass signal
Sorry, but I have to laugh when I read your sig: "
if you dont know, dont pretend you know, or repeat what some else thought they knew. thats called popping off and really it helps no one
"
Those codes do in fact mean that the O2 sensors have reached their maximum rich threshhold because there is too lean of a condition on both banks. A car's FTR is meaningless unless you have established what the normal correction values are. Each car is difference. As a matter of fact, my 996 corrects fuel trim by -18% on bank 1 and -7% on bank 2, which gives me a perfect F/A ratio.
Regardless of what the cause is, the engine is running lean. He either has too little fuel or too much air passing by the O2 sensors.
Obviously, we DO know he is above the limt values since the codes were thrown.
it must feel pretty good to know more then the engineers at porsche becasue they are full convinced that that fault can be casued by being to rich or too lean
DME 7.8
2469 P1128 0-116 page 1
DME 7.8
p1128
0
Printed in Germany � 4, 2002
0-116 P1128
360 Oxygen Sensing Adaptation, Idle Range, Bank 1 -
Below Limit
Diagnosis conditions
� Oxygen sensing system active
� Time elapsed after engine start-up: 250 to 350 seconds (USA)
� Time elapsed after engine start-up: 302 to 402 seconds (RoW)
� Engine temperature greater than 60 �C
Possible fault cause
♦ Incorrect signal from MAF sensor
♦ Fuel pressure too high
♦ Fuel injector leaking
♦ EVAP canister purge valve open
Affected terminals
-
Diagnosis/Troubleshooting
♦ If DTC P0445 (fuel tank vent valve - short to ground) is stored, correct this fault first. An open EVAP canister
purge valve can lead to the lean threshold being reached.
♦ For vehicles in the USA, the upper load range will probably not be reached. The only case in which a fault could
be stored is during driving while towing a trailer or caravan on a hill.
♦ Contrary adaptation values in connection with misfiring point to incorrectly adjusted control timescheck control
times and adjust if necessary.
♦ If the fuel tank reserve light is switched on, no fault is entered.
Work instruction Display OK If not OK
1 Check signal from MAF
sensor.
♦ Connect special tool 9637.
♦ Measure voltage at pin III/23
and ground
♦ Switch on the ignition.
0.9 to 1.1 V. Replace MAF sensor
♦ Start the engine. Approx. 1,4 V
2 Check fuel pressure
Note!
DME 7.8 DME 7.8
0-116 page 2 2469 P1128
p1128
0
Printed in Germany � 4, 2002
360 Oxygen Sensing Adaptation, Idle Range, Bank 1 -
Above Limit
Diagnosis conditions
� Oxygen sensing system active
� Time elapsed after engine start-up: 250 to 350 seconds (USA)
� Time elapsed after engine start-up: 302 to 402 seconds (RoW)
� Engine temperature greater than 60 �C
Possible fault cause
♦ Incorrect signal from MAF sensor
♦ Intake air system leaking
♦ Fuel pressure too low
♦ Volume supply of fuel pump too low
♦ Fuel injectors fouled
3 Check fuel pressure regulator,
vacuum connection
and fuel return line
♦ Remove vacuum hose from fuel
pressure regulator
♦ Connect special tool 9103/2 to
vacuum hose
♦ Start the engine.
♦
0.4 - 0.6 bar Check the intake air
system for leaks
and check vacuum
line to fuel pressure
regulator for restrictions.
♦ Check housing of fuel pressure
regulator for damage and deformation
Replace the fuel
pressure regulator if
it is damaged with
the result that the
spring pre-tensioning
is increased
4 Check EVAP canister
purge valve
♦ Disconnect hose from EVAP canister
purge valve to intake system
at EVAP canister purge
valve
♦ Remove connector of EVAP canister
purge valve
♦ Connect special tool 9160/1 to
EVAP canister purge valve
♦ Generate vacuum of approx. 0.7
bar
The vacuum must
not fall below 0 bar
after 10 minutes
5 Check fuel injectors for
leaks
Work instruction Display OK If not OK
DME 7.8
2469 P1128 0-116 page 3
DME 7.8
p1128
0
Printed in Germany � 4, 2002
♦ PCV valve leaks
♦ Cap of oil filler neck not closed correctly or seal is damaged
Affected terminals
-
Diagnosis/Troubleshooting
♦ Air leaks ahead of the oxygen sensors can lead to a fault in adaptation Check exhaust system for leaks.
♦ Contrary adaptation values in connection with misfiring point to incorrectly adjusted control timescheck control
times and adjust if necessary.
♦ If the fuel tank reserve light is switched on, no fault is entered.
Work instruction Display OK If not OK
1 Close cap of oil filler neck
properly or replace the
seal
2 Check signal from MAF
sensor.
♦ Connect special tool 9637.
♦ Measure voltage at pin III/23
and ground
♦ Switch on the ignition.
0.9 to 1.1 V. Replace MAF sensor
♦ Start the engine. Approx. 1,4 V
3 Check exhaust system for
leaks
4 Check for air leaks in
intake air system
5 Check PCV valve for leaks
6 Check fuel pressure
7 Check volume supply of
fuel pump
8 Fuel injectors fouled ♦ If preceding Check Points were
negative, the fuel injectors may
be fouled
♦ Clean fuel injectors (ultrasonic
cleaning device) or replace them
Note!
DME 7.8 DME 7.8
0-116 page 4 2469 P1128
p1128
0
Printed in Germany � 4,
so in this case
I
\/
is directed to you
It could also be caused by aliens hiding inside the cats sucking in everything but the oxygen, but that would be unlikely....wouldn't it?
When a 1128 and a 1130 come up together with no other codes, it is reporting that the engine is lean.
Also, I have no idea why you are quoteing from an old Factory Manual. You should get the most recent one. I would think a Porsche shop would have it.
I used to get these two error regularly, about once a month. Everytime I just reset the OBD2 and then it will come back about 3-4 weeks later.
After I cleaned the MAF with the MAF spray cleaner the error hasn't shown up in about 4 month now.
I know we all misspell on these forums as well as make grammatical errors regularly, but I have no idea what you said. I assume that English is your second language or it is your attempt to try to confuse everyone? So, I guess I'll leave it alone.