20 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHCEL - Code P2098
Leading reported evidence
Replace not only the sensor the error code pointed
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
I was satisfied then and changed not only the sensor the error code pointed to but its matching sensor on the other side.
Leading evidence: 'Replace not only the sensor the error code pointed' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, the most frequently mentioned possible cause is 'sensor or bad software' (1 discussions; 0 report identifying it and 1 suggest it). The most frequently discussed action is 'Repair manual info re p2098)' (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.
Suspected cause
I think part of OP's issue is whether the CEL is due to a bad sensor or bad software, which requires reprogramming to fix.
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
I think part of OP's issue is whether the CEL is due to a bad sensor or bad software, which requires reprogramming to fix.
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, just replace your bank2 precat O2 sensor (according to the Bentley repair manual info re P2098)
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, just replace your bank2 precat O2 sensor (according to the Bentley repair manual info re P2098)
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.
20 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.
Hi there - 2002 C2, 66,000 miles on chassis, 8,000 miles on factory reman'd engine. Got a CEL the other day, UPS guy finally showed up with my new code reader today. Code shows a P2098. After researching here and Renntech and Google etc. looks like it is most likely the/an O2 sensor.
Does the majority concur/have experience? I realize it could possibly be something else, but I figure if the vast majority of you all point to one thing, then I will take a chance on that assuming it's not too pricey/difficult.
Should be around $100~$150 Bosch so it's "cheap" enough just to replace it on a 11yr old car.
You could also reset the CEL and see if it comes back again before doing anything further.
They are very easy to get to if you need to change one. Ive taken my mufflers off 3 or 4 times and could have easily changed them if needed while I was under there.
Thanks everyone for the info, I reset it yesterday and today went well, we'll see what happens the next few days. If it comes back I will let y'all know.
O2 sensor problems have been few and far between but they can be a pain to diagnose. I went through a month or more of dealing with an O2 sensor related error. But whenever I looked at the sensor voltage with an OBD2 data viewer the voltage readings looked reasonable.
I finally caught on to when the error would appear -- after about 30 miles of driving -- and had the code reader already hooked up. I'd sneak a peak at the sensor readings at a stop light and I then saw the drop in voltage, the flattening of the high voltage reading and other changes and once or twice I was observing this on the code reader when the CEL came on.
I was satisfied then and changed not only the sensor the error code pointed to but its matching sensor on the other side.
Just a followup, it's been several months and about 2500 miles and it has not come back on. I did nothing but reset the codes. Hopefully it stays that way.
Thanks.
Well, just this evening the code came back again. Same code, just driving normally, car in warmup phase. It's been 1 year, 8 months and about 9000 miles since the last occurrence. I did just change the oil a few days ago. I reset the code again and we'll see if it comes back...
The bummer is I'm taking it on a trip to Indiana about a week from now. So about 2600 miles round trip, it'll be annoying if it comes on during the trip...If it comes on again before I leave I suppose I will try to figure out which of the four 02 sensors it is. I do not want to get stranded en route...
Edited: I just found this:
http://www.underhoodservice.com/tech...096-p2098-set/
It was published after my first occurrence of this issue. Interesting.
The article in the link has a critical error. The original TSB (available from Renntech) says "In vehicles produced before the date of introduction stated below, the Check Engine warning light may be activated by an error in the diagnosis software of the DME control module. ", which makes a lot more sense.
So if the TSB applies to your VIN, maybe a dealer visit is needed for reprogramming opf the DME. If not, just replace your bank2 precat O2 sensor (according to the Bentley repair manual info re P2098)
Thanks I found this as well which seems better and more complete:
http://workshop-manuals.com/porsche/...096/p2098_set/
As far as I can tell it would apply to any '02. Thanks for letting me know WHICH of the O2 sensors would be the one in question if reprogramming he DME did not work. Now I wonder what that costs and somehow can still find it within myself to be surprised that any manufacturer would let the customer be charged for reprogramming of something that should have been right from the get-go no matter how old the car is. It's not like software degrades over time or miles or be affected by how the car was treated or where it was serviced...
I've asked Loren and John over Renntech. Watch out for the final verdict on which O2 sensor P2098 refers to
http://www.renntech.org/forums/topic...s/#entry259389
If you have a smartphone, you can get a wireless OBDII dongle and the Torque app to monitor the O2 sensor pattern and see how the two banks compare. You may be able to see some differences. See the thread here and healthy O2 sensor signal in post #26
https://rennlist.com/forums/996-foru...mendation.html
Also good to compare signal generated by old and new sensors once installed.
BTW this is the correct pre-cat one for your car - $102, not too bad
Amazon.com: Bosch 16433 Oxygen Sensor, OE Type Fitment: Automotive
Amazon.com: Bosch 16433 Oxygen Sensor, OE Type Fitment: Automotive
Just to follow up, thanks Ahsai, and the car made it to Indiana and back with no issues, so now it's been about 3000 miles since I cleared the code, no re-occurence since. If it comes back I will inquire about a re-flash and if that's cost prohibitive, replace that one 02 sensor. My least favorite thing to do is to spend money for someone to hook up a wire and press a button for something that should just be an free patch to correct an original fault.
