fullymatted.
Back to search
Rennlist

Indicator Failure?

Add to repair workspace
Open repair workspace
Original source
7 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW

Discussion summary

YOUR RESEARCHIndicator Failure?

Reported or suspected cause

sender

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

same exact thing happened to me too......it was the sender

Original post Read captured discussion
Indicator Failure?
Frequently discussed work

Use crow's foot method posted by dharn/doug

No successful repair reported for this finding.

0
Reported fixes
0
Unsuccessful attempts
1
Discussions
Read evidence and context
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

Change it using the crow's foot method posted by Dharn/Doug.

Original post Read captured discussion
Indicator Failure?
Read full discussion summary

Leading evidence: 'sender' (1 discussions report identifying this cause; no attributable repair resolution). Across 1 matching discussions, the most frequently mentioned possible cause is 'sender' (1 discussions; 1 report identifying it and 0 suggest it). The most frequently discussed action is 'Use crow's foot method posted by dharn/doug' (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.

Read captured replies

1 matching discussions · 7 captured posts examined · 0 partial discussions

Compare 1 other evidence results

Use crow's foot method posted by dharn/doug

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

Change it using the crow's foot method posted by Dharn/Doug.

Original post Read captured discussion
Indicator Failure?
Frequently discussed actions (1)

These are separate views of the same evidence. Frequency alone does not establish a fix, and these counts must not be added together.

Use crow's foot method posted by dharn/doug

No successful repair reported for this finding.

0
Reported fixes
0
Unsuccessful attempts
1
Discussions
Read evidence and context
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

Change it using the crow's foot method posted by Dharn/Doug.

Original post Read captured discussion
Indicator Failure?
Reported and suspected causes (1)

These are separate views of the same evidence. Frequency alone does not establish a fix, and these counts must not be added together.

sender

No successful repair reported for this finding.

1
Identified cause
0
Suspected cause
0
Reported fixes
Read evidence and context
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

same exact thing happened to me too......it was the sender

Original post Read captured discussion
Indicator Failure?
Coverage and how to read this overview

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.

7 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: 20261027T003124Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources

POST 1 / ORIGINAL POSTEROriginal post

Anyone ever have their oil pressure gauge bottom out, then the dash computer go "DING" and display "Indicator Failure", then before you can do anything, the pressure gauge pegs to 5bar+, the alarm clears, then everything settles back to normal? I can tell you, it brought a cold chill down my spine! I'm assuming the gauge is not hard wired, but part of the dash assembly, and just lost something, before e-synching. Only time I've ever seen that, or heard of it. Anybody?

POST 2Original post

Could be a possible sender issue. Perhaps a lead is loose on the sender. It's easy to check - on the passenger side of the engine with two wires that push onto the little tabs. - check to see if they pull off too easy or are dirty. As far as the gauges: they either work or they don't and it's a rare failure where they go wonky and then work again unless there is a bad connection at the backside. Usually a bad connection takes the whole dash display out if that happens. https://rennlist.com/forums/996-foru...ement-diy.html

POST 3 / ORIGINAL POSTEROriginal post

Thanks...yep, that's it for sure. Found another thread, too, not a bad fix, if I need to do it.

POST 4Original post

Yes - the senders seem to fail around 10 years or so ... I was going to DIY mine - but I needed 60K service anyway - so had the indie do it when he was in there for the plugs - and it ended up costing me less than $50 over the cosdt of the part ....so that might be another option if you don't have time for DIY (or don't like skinned knuckles) ....

POST 5Original post

same exact thing happened to me too......it was the sender

POST 7Original post

It's the sender. Change it using the crow's foot method posted by Dharn/Doug. easy fix.

This is a source reference. Confirm exact model applicability in the original material.