13 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHOil pressure sensor
Reported or suspected cause
youll need a crow foot
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
The only issue is youll need a crow foot on the end of a long extension to get to the nut on the sender accessing from under the engine.
Leading evidence: 'youll need a crow foot' (1 discussions report identifying this cause; no attributable repair resolution). Across 1 matching discussions, the most frequently mentioned possible cause is 'youll need a crow foot' (1 discussions; 1 report identifying it and 0 suggest it). The most frequently discussed action is 'Clean terminals' (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
Will clean the terminals before my drive to Hershey next weekend.
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 did like you first time: brake-steer-try not to fill shorts!
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 it does need replacing a good Indi should be able to do it.
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.
13 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.
I think my oil pressure sensor is about to give up the ghost. How expensive to replace? Can a good Indy shop do the work or do I have visit a P dealership?
Thanks
Gauge goes to zero, throws a code and gauge returns to normal, 2-3 restarts and code disappears. Car runs fine the entire time, assume it's the sensor. First time it happened, my heart stopped, I pulled off the road and before I could shut down the engine the gauge returned to normal. Very intermittent, only has happened a few times in last 3 months.
Car is a 2002 C4 Cab with M6 Trans.
Yup sounds about right. What did the "code" say? Mine said something to the effect of "oil sensor failure". I did like you first time: brake-steer-try not to fill shorts! 2005 996 C4S.
I did mine some years back. It's quite easy following the
Dharn
method (search threads) - essentially, with left rear wheel removed, access it with a crow's foot on a couple extensions from underneath. Helpful to have someone on topside to assist. Takes longer to get the car in position than to change it. GL w/repair.
I think I paid 100.00 or so for my sender. I had an intermittent code in reader memory but no signs of failure from gauge. The part is less than an hour of labor at my Indy so i attempted the R&R myself. It was a simple procedure and no more code. It took longer to jack the car and remove the rear wheel than it did to remove the sender. The only issue is youll need a crow foot on the end of a long extension to get to the nut on the sender accessing from under the engine. Its not a 5 minute job once you get the wheel off.
Any Indy will do. Dealer not necessary
Same issue here... Just got my new sensor from Jason at Paragon. Will clean the terminals before my drive to Hershey next weekend. If I still see the issue I will replace when I get back
its super easy to do...Get a crows foot open end wrench and back it up on some ramps and slide under the car, it is right there. The whole process takes about 30 minutes.
I took me a total of 14 mins to swap mine out and that included jacking up the car, get out the proper tools and put it back on the ground. I did not remove my wheel either.
This is a source reference. Confirm exact model applicability in the original material.
