11 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHPanic moment, should I worry???
Reported repair
Clean contacts
Reported resolution
1
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 report a fix
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 fix
Try cleaning the contacts on the sender and put some dielectric grease on them...that fixed it for me.
Leading evidence: 'Clean contacts' (1 discussions report resolution; 0 report an unsuccessful attempt). Across 1 matching discussions, the most frequently mentioned possible cause is 'sending unit' (1 discussions; 0 report identifying it and 1 suggest it). The most frequently discussed action is 'Clean contacts' (1 discussions). For that action, 1 discussions report a resolution and 0 report an unsuccessful attempt. The most frequently reported fix is 'Clean contacts', supported by resolution reports in 1 discussions. 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 report a fix
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 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.
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.
Suggestion
Flicked the oil check light when under 800 rpms, went away when i added a little gas.
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 tell him to install it and if it is NOT the culprit and the problem persists then not only do they not have to file it under warranty repair but that I will pay for it out of pocket and I will pay DOUBLE whatever the retail price on the part is and double the book rate for labor.
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.
11 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.
Outcome without a verified action link
Of course later that morning I got a VERY APOLOGETIC call and was told that the sending unit fixed the problem.
Driving to the airport the other day, about 15 minutes from my home (so the car is fully warmed up), and everything is fine. Suddenly, I get an indicator on the dash, with very scary wording, about the oil pressure. The oil pressure gauge was reading 0, but the RPMs, speedometer, and temperature guages were all normal. I engaged the clutch and began to decide where I would pull off to wait for the tow truck, when suddenly the warning went away and the oil pressure guage jumped back to normal range.
Having a scheduled departure imminently, and the car showing absolutely no symptoms of problems, I drove the remaining 5 minutes to my parking garage. No more warnings, all guages showing normal, no bad sounds, nothing. I got there, got under the car, no leaks, no smells, nothing.
I flew off, and by the time I returned I had TOTALLY forgotten about it. I didn't remember until I returned from another trip yesterday. In the meantime, I did an autocross (first in class, woot!) and put ~500 miles on the car, all perfectly normal.
I'm assuming I just had an instrument or sensor hiccup? Has anyone ever had this happen? Is this a warning sign of bad things in my future? Should I get it to a mechanic to read the computer, or can I safely ignore this?
Probably the sending unit.
If you truly lost oil pressure, your lifters would tick, rod bearings would clack, and the main bearings would knock. Maybe not at all once but at least one is going to make a noise.
I had the exact same thing happen to me. Bad oil pressure sensor was the culprit. In my case it was covered under warranty, but I think it was rather inexpensive anyway.
Michael
Sending unit. Had the same problem in my GT3. Fixed under warranty.
I agree thought, scary as crap to see that message and then the oil pressure gauge read 0.
I've had this happen numerous times. Took it to the dealer and they didn't know what it was. I'll take it back now that you guys have given a clue as to what it is.
My dealer said they couldn't find the problem and the "computer" they hooked up (PIWIS) showed no problems either so they fixed nothing. Further they said they couldn't duplicate the problem. WTF? So I drove the worthless tech around the block and REPLICATED the problem to which he said "that's normal". WTF? Normal to get the needle to drop like a lead weight to the zero? Normal to get the error message? WTF? So I ask.....do you have a sending unit in stock? Well they do. So I make a deal with the service manager. I tell him to install it and if it is NOT the culprit and the problem persists then not only do they not have to file it under warranty repair but that I will pay for it out of pocket and I will pay DOUBLE whatever the retail price on the part is and double the book rate for labor. Of course later that morning I got a VERY APOLOGETIC call and was told that the sending unit fixed the problem.
Problem with mine, and I expect others, is that it happens very sporadically but in clumps. I may go 1-2 months with it not happening at all, then it could happen three times in 10 miles. Since my CPO ends the end of the year I will take it in and be rather persistent that they fix it.
I had mine towed to the dealer the first time it happened to me. Of course they were unable to reproduce the problem. I've seen it a total of three times now.
Try cleaning the contacts on the sender and put some dielectric grease on them...that fixed it for me. For some dumb reason the connections are not protected against dust and the weather.
This happened to my '03. It would show no oil pressure, then a few moments later--it's back. Unnerving. The dealer could find no error codes. Happened several times over the course of a year. No relation to going over a bump or anything else I could identify that was related. So they said, the next time it happens, if possible, don't turn it off, drive it directly to the shop & let them read the codes. Well....I did, they did...still nothing conclusive. So, they replaced the sender. Hasn't happened since.
Mine did it once on a hot day. Flicked the oil check light when under 800 rpms, went away when i added a little gas. Never happened again. I took my car in for some other issues and the dealer couldn't get the car to repeat any of its idiosyncrasy... I swear this thing is alive....
This is a source reference. Confirm exact model applicability in the original material.
