5 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHError Code P1119 and K&N CAI-Please ADVISE
Reported or suspected cause
same p1119
Reported cause
No successful repair reported for this finding.
1
Identified cause
0
Suspected cause
0
Reported fixes
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 report identifying 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.
Reported cause · Original poster
At this point I had the code read and it was the same P1119.
Leading evidence: 'same p1119' (1 discussions report identifying this cause; no attributable repair resolution). Across 1 matching discussions, the most frequently mentioned possible cause is 'same p1119' (1 discussions; 1 report identifying it and 0 suggest it). The most frequently discussed action is 'Check any open or loose hoses' (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 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.
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 · Original poster
Was I not smart by continously resetting the comp and driving the car??
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
The first time after 1450 miles I spoke to K&N directly and they told me to disconnect the battery and reset the computer.
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.
5 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.
1 acknowledgements have no verified action link; they do not establish a repair result.
This is the error code I have as possibly caused by the K&N CAI I had installed. The code reader stated "Manufacturer Controlled Fuel and Air Metering".
I have had this error code three times. The first time after 1450 miles I spoke to K&N directly and they told me to disconnect the battery and reset the computer. The CEL returned the second time after 490 miles. I again disconnected the battery but the CEL returned again after 488 miles. At this point I had the code read and it was the same P1119. Since I was out of town and had to drive back home I disconnected the battery again(I know I know) and the CEL returned after 95 miles.
I will be taking the car back to my mechanic to have a look over and reinstall the stock intake while also speaking to K&N for tech support and/or refund.
SO, is this code related to the CAI??????
Was I not smart by continously resetting the comp and driving the car??
Any other advice?
Thanks for your time and help.
The P1119 indicates a problem with the heating of the before cat O2 sesor and not the fuel control. Check the wiring and make su re it is not cut or frayed. To determine if it's actually the sensor, switch bank 1 with bank 2. If you get a P1117 code, then the problem followed the sesnor and it needs replacing. If it continues to generate a P1119, it must be in the wireing or DME.
You can't clearly tell what is going on with the codes only as they are only a guide line. While the code may call for a O2 sensor many things can set it off beside a bad O2 or bad wire. Given the fact that you have a K&N I can suspect that you car may have a vacum line loose or disconected. Make sure to check any open or loose hoses. Also K&N may have got some oil on your MAF which can alter fuel mixture leading to the lean conditions to set off the code. I suspect since you have you stock intake back it would be wise to see in a few hundread mile if the code set off. If it does not then you know it has something to do with the intake. IMO intakes only improvements are to lighten your wallet. There is minimal or no improvements on a stock car.
Thanks for your help 1999Porsche911 and Jetskied. I have switched the sensors from bank 1 to bank 2. If I get the P1117 code I know it was the sensor.
At this time we have not yet reinstalled the stock intake. We will see if the CEL returns before the next step.
doesnt dound related to the cai, fault is thrown from a fult in the o2 sensor heater circut as previously stated, if the dealer reads the fault with a pst2/piwis they will have more information from it as to what the casue of fault is above limit/below limit/open circut/implausable signal ect
This is a source reference. Confirm exact model applicability in the original material.
