fullymatted.
Back to search
Rennlist

Reference for interpreting scanner info (NT530)

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

Discussion summary

YOUR RESEARCHReference for interpreting scanner info (NT530)

Reported or suspected cause

easiest

Suggestion or failed attempt

No successful repair reported for this finding.

0
Identified cause
1
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 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

Typical reason for this is a vacuum leak but there are many other things that can cause that as well but the vacuum leak is probably the easiest to rule out first.

Original post Read captured discussion
Reference for interpreting scanner info (NT530)
Frequently discussed work

Recommend max value by porsche (+- 6.0)

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

Yours is -5.75 which is just below the recommended max value by Porsche (+- 6.0).

Original post Read captured discussion
Reference for interpreting scanner info (NT530)
Read full discussion summary

Leading evidence: 'easiest' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, the most frequently mentioned possible cause is 'easiest' (1 discussions; 0 report identifying it and 1 suggest it). The most frequently discussed action is 'Recommend max value by porsche (+- 6.0)' (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 · 6 captured posts examined · 0 partial discussions

Compare 2 other evidence results

Recommend max value by porsche (+- 6.0)

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

Yours is -5.75 which is just below the recommended max value by Porsche (+- 6.0).

Original post Read captured discussion
Reference for interpreting scanner info (NT530)

Run ", and mine has a value of 15.2

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 · Original poster

For example, one of the DME actual values is called "Rough running", and mine has a value of 15.2, but I have no idea what that means.

Original post Read captured discussion
Reference for interpreting scanner info (NT530)
Frequently discussed actions (2)

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

Recommend max value by porsche (+- 6.0)

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

Yours is -5.75 which is just below the recommended max value by Porsche (+- 6.0).

Original post Read captured discussion
Reference for interpreting scanner info (NT530)

Run ", and mine has a value of 15.2

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 · Original poster

For example, one of the DME actual values is called "Rough running", and mine has a value of 15.2, but I have no idea what that means.

Original post Read captured discussion
Reference for interpreting scanner info (NT530)
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.

easiest

No successful repair reported for this finding.

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

Typical reason for this is a vacuum leak but there are many other things that can cause that as well but the vacuum leak is probably the easiest to rule out first.

Original post Read captured discussion
Reference for interpreting scanner info (NT530)
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.

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

POST 1 / ORIGINAL POSTEROriginal post

Can anybody point me to a good reference for the data values you get in the NT530 scanner? For example, one of the DME actual values is called "Rough running", and mine has a value of 15.2, but I have no idea what that means. Thanks in advance, and have a Safe, Happy, Holiday! Mike

POST 3 / ORIGINAL POSTEROriginal post

Yes, that's helpful to understand the "normal" ranges. Thanks!

POST 4 / ORIGINAL POSTEROriginal post

There are a lot more parameters than those two screenshots, so I took screenshots from the FoxAssist app, since it won't allow me to print the live data (?), just the other reports. For those who are more knowledgeable than me, which of these values would be the most critical to investigate first? Thanks! Mike

POST 5Original post

There's one that needs an "as soon as possible" fix -> Camshaft deviation 1 Yours is -5.75 which is just below the recommended max value by Porsche (+- 6.0). That means that the camshaft wear pads are worn out and needs to be replaced. Jake has an excellent description of the issue on Youtube You Tube Your FRA fuel trims are also a bit high at 1.19 and 1.17. Those should be close to 1.00. That means that the engine is running lean so it's adding fuel to the air/fuel mixture. Typical reason for this is a vacuum leak but there are many other things that can cause that as well but the vacuum leak is probably the easiest to rule out first.

POST 6 / ORIGINAL POSTEROriginal post

Thanks for reviewing the data and providing some guidance! I've got an appt with a good local indy shop to help get things sorted, but was just wanting to get a feel for how much might need attention. Thanks again for taking a look! Mike

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