9 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHProblem update: Now CEL illuminated
Leading reported evidence
Adjust fuel curves
Suggestion or failed attempt
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 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
Its more likely that the maf is failing by the random lights illuminating and causing the dme to not properly adjust the fuel curves.
Leading evidence: 'Adjust fuel curves' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, The most frequently discussed action is 'Adjust fuel curves' (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 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
The reason why people are telling you to check the MAF is because for whatever reason, on the 996, the MAF sending faulty data will trigger the PSM/ABS lights and not a CEL.
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
Two different O2 sensor parameters to check: resistance and voltage.
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
Hmmm...here is what I would do: clear the code, disconnect the battery to clear the DME/ECU, go for a drive and see if it throws another code.
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
So you probably need to replace the black wired sensor with gray connector.
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
The reason why people are telling you to check the MAF is because for whatever reason, on the 996, the MAF sending faulty data will trigger the PSM/ABS lights and not a CEL.
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 · 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: 20261027T201111Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources
For the last couple of weeks my PSM and ABS warning lights illuminates when I start the car and puts in a gear, forward or reverse.
This evening the CEL came on while
driving my car.
I therefore took my OBDII reader and checked if there was any store trouble codes and the reading showed:
�P2096
Control unit 11
Status confirmed
OBDII: Post catalytic converter fuel trim (FT), bank 1- too lean�
Any thoughts about this?
It can�t hardly be a coincidence that all these three lights illuminates in a short period of time.
Can a faulty oxygen sensor trigger the cars PSM and ABS-system or is it something wrong with the DME?
Thankful for advise, input and help
Hmmm...here is what I would do: clear the code, disconnect the battery to clear the DME/ECU, go for a drive and see if it throws another code. Could be the MAF sensor or one of the O2 sensors, post cat on Bank 1.
P2096 is a fault code or the O2 Sensor, though it is interesting that you are getting PSM/ABS lights and not a CEL for that code. The reason why people are telling you to check the MAF is because for whatever reason, on the 996, the MAF sending faulty data will trigger the PSM/ABS lights and not a CEL. I
do not believe
this is true for the O2 sensor, but I am not an expert, I am saying this because in every other instance I find for your code it is accompanied by a CEL. I had found a thread on Renntech where the problem ended up being shot catalytic converters... Not trying to send you down a rabbit hole, but I feel like at this point just throwing O2 sensors at the car is throwing parts at it before we know the solution for sure.
I'm sorry
@Bengan035
, I am finishing up a busy week and my reading comprehension obviously took a steep dive. Your thread title literally says your CEL is illuminated. *facepalm*
I'd definitely be looking at those O2 sensors in this case. The MAF might be affected by this as well and is throwing up the PSM/ABS light but it sounds like you definitely have a faulty O2 sensor. There are many guides online how to replace this yourself. It shouldn't be above your pay grade, though, those O2 sensors can be in there pretty sung and you may need to hit them with some heat and bolt-breaking fluid.
Uhg, u dont have to throw parts at it. U can graph the o2 sensors with a $20 obd2 bluetooth plug in to see if they r working. I think some of the logic is backward here. Its more likely that the maf is failing by the random lights illuminating and causing the dme to not properly adjust the fuel curves. If faulty maf data is causing a bad mix then it will trip the o2 code.
As De Jeeper says, first things first.
P2096 is the O2 sensor.
DBJoe996 is right about reset of DME to test system again. Two different O2 sensor parameters to check: resistance and voltage. See if the post cat sensor is working. If you get a resistance of, say, 64 Ohms and doesn�t fluctuate, it�s dead. Compare before and after cat readings with the other bank and same side bank. If the suspect sensor is bad, the voltage will not follow the pre cat sensor sine wave path�flat line (0) instead. So you probably need to replace the black wired sensor with gray connector. The upstream or pre-cat sensor wire is blue.
The MAF really doesn�t do much at low rpm. That OBD II fuel trim code is not one I�m familiar with, but probably is generic for �the post cat sensor isn�t working so the DME thinks it�s running lean on one bank.�
The ABS samples rpm and throttle position to send proper signals to PSM.
O2 sensors and emissions-related CEL's
Why didn't you update your original thread
https://rennlist.com/forums/996-foru...#post18364675?
Could an admin please merge?
Makes it easier to see what has been mentioned as next steps in troubleshooting.
You don't seem to respond to those suggestions and what result those yielded either which I find strange. Almost as if you like posting about it more than getting rid of it.
Of course it's harder work than posting on here but jeez man, put some effort in and get your hands dirty..
For instamce did you unplug und plug back in the MAF connector in the meantime?
Especially since your getting a CEL (the already not properly seated plug is (after further driving) only making contact intermittently and finally throws a CEL ).
I repeat what I wrote earlier: wheel speed sensors have the highest chance of being the cause for PSM and ABS light, the CEL is unrelated.
Please give us who post suggestions of next trouble shooting steps the satisfaction of hearing whether we were right (or not) by following up with the result you got by executing said step(s).
^^^ right, I agree..the feedback on steps/tests/checks/ are critical...
Sounds like two separate problems...an ABS problem and an 02 Sensor problem..
You can likely find and fix the 02 Sensor problem with a Generci OBDII scanner.. but the ABS is a separate system with its own control module and set of codes that needs a more sophisticated scanner/tester to get the codes and actual values...
This is a source reference. Confirm exact model applicability in the original material.