fullymatted.
Back to search
Planet-9

DME Scan

Add to repair workspace
Open repair workspace
Original source
5 captured repliesPartial discussion capture · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW

Discussion summary

YOUR RESEARCHDME Scan

Leading reported evidence

Replace by more recent range 1 and 2 records

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

The very brief Range 3 hit had to go up and down through Ranges 1 and 2 to get to Range 3, but the Range 1 and 2 records of that hit have been replaced by more recent Range 1 and 2 records.

DME Scan
Frequently discussed work

Check math

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

Otherwise, you can just check my math.

DME Scan
Read full discussion summary

Leading evidence: 'Replace by more recent range 1 and 2 records' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, The most frequently discussed action is 'Check math' (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 · 5 captured posts examined · 1 partial discussions

Compare 3 other evidence results

Use range 1 midpoint of 7400 rpm

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

To calculate time in Range 1, I use the Range 1 midpoint of 7400 rpm, which is 123 revs per sec (rps).

DME Scan

Check math

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

Otherwise, you can just check my math.

DME Scan

Replace by the more recent records

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

There could have been more, but, if so, that record has been replaced by the more recent records.

DME Scan
Frequently discussed actions (4)

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

Check math

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

Otherwise, you can just check my math.

DME Scan

Replace by more recent range 1 and 2 records

No successful repair reported for this finding.

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

The very brief Range 3 hit had to go up and down through Ranges 1 and 2 to get to Range 3, but the Range 1 and 2 records of that hit have been replaced by more recent Range 1 and 2 records.

DME Scan

Replace by the more recent records

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

There could have been more, but, if so, that record has been replaced by the more recent records.

DME Scan

Use range 1 midpoint of 7400 rpm

No successful repair reported for this finding.

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

To calculate time in Range 1, I use the Range 1 midpoint of 7400 rpm, which is 123 revs per sec (rps).

DME Scan
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.

5 eligible posts · 0 unverified posts · 1 discussions match the subject in their title or opening post.

  • Planet-9: 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: 20261026T205155Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources

POST 1Original post

I have received the following DME data from the dealership: Range 1: 999 129.6h Range 2: 115 128.2h Range 3: 9 18.1h Range 4: -- -- Operating hours counter 139.2 Miles: 4200 I did a search on this. But I still don't know how to calculate Time at Over Rev. Can anybody help? Thanks

POST 2Original post

By my calculations, total time spent over redline is about 3 seconds; about 2.7 seconds in Range 1, about .3 of a second in Range 2, and about .02 of a second in Range 3. I've posted my calculations procedure for this several times here, but no one has called me out on it yet. Maybe this time. Otherwise, you can just check my math. There are 3 ignitions for each revolution of the engine (one half of the 6 cylinders fire each revolution). To calculate time in Range 1, I use the Range 1 midpoint of 7400 rpm, which is 123 revs per sec (rps). 123 rps X 3 ignitions = 369 ignitions per second. 999 Range 1 ignitions divided by 369 igns per sec yields about 2.7 seconds in Range 1. Doing the same for the 115 ignitions in Range 2 (using the Range 2 midpoint of 7600 rpm), I got about .3 seconds in Range 2. Repeating that for the 9 ignitions in Range 3 (midpoint = 7800 rpm), I got about .02 of a second. Thus, combined time over redline was estimated to be about 3 seconds. If you see any problem with my calculations, let me know. Math was my most worstest subject.

POST 3Original post

Jim, Also worth noting that these numbers are cumulative so it didn't have to happen all at the same time. I don't see anything out of the ordinary here, someone just banged the rev limiter, you can easily get these kinds of readings from that alone. I believe your math is a good approximation.

POST 5Original post

Ken: I agree. From the three different operating hours given, it appears that there were at least 3 "trips" past redline. There could have been more, but, if so, that record has been replaced by the more recent records. The very brief Range 3 hit had to go up and down through Ranges 1 and 2 to get to Range 3, but the Range 1 and 2 records of that hit have been replaced by more recent Range 1 and 2 records. For sticklers to the advised break-in period, the Range 3 hit apparently occurred before the end of that period. Otherwise, these data don't show anything to be concerned about.

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