7 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCH996 Error Code readers
Reported or suspected cause
aswell as presenting an error code
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 · Original poster
Ah yes, the Durametric is my 1st choice but really all I'm looking for is 'some' capability to plug in and check so that at least when speaking to my Independent or OPC I can at least verbally describe what the problem is aswell as presenting an error code.
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
Ah yes, the Durametric is my 1st choice but really all I'm looking for is 'some' capability to plug in and check so that at least when speaking to my Independent or OPC I can at least verbally describe what the problem is aswell as presenting an error code.
Leading evidence: 'aswell as presenting an error code' (1 discussions report identifying this cause; no attributable repair resolution). Across 1 matching discussions, the most frequently mentioned possible cause is 'aswell as presenting an error code' (1 discussions; 1 report identifying it and 0 suggest it). The most frequently discussed action is 'Check so' (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 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.
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 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
Ah yes, the Durametric is my 1st choice but really all I'm looking for is 'some' capability to plug in and check so that at least when speaking to my Independent or OPC I can at least verbally describe what the problem is aswell as presenting an error code.
These are separate views of the same evidence. Frequency alone does not establish a fix, and these counts must not be added together.
Check so
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
Ah yes, the Durametric is my 1st choice but really all I'm looking for is 'some' capability to plug in and check so that at least when speaking to my Independent or OPC I can at least verbally describe what the problem is aswell as presenting an error code.
These are separate views of the same evidence. Frequency alone does not establish a fix, and these counts must not be added together.
aswell as presenting an error code
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 · Original poster
Ah yes, the Durametric is my 1st choice but really all I'm looking for is 'some' capability to plug in and check so that at least when speaking to my Independent or OPC I can at least verbally describe what the problem is aswell as presenting an error code.
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.
Porsche Club GB: 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: 20261026T142254Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources
they all do pretty much the same thing, when you have a fault they give you a p code , you then cross refer this to a generic p code list and take it from there, they also clear the engine fault if required...
so it really up to yourself dependng on what you want it to do...
Welcome Steve!
What model/year was the car you tried it on?
Mike -
I think I have said this before, but the early RoW 996's with mechanical throttle were equipped with Bosch Motronic DME version 5.2.2. Whereas the US cars were fully OBD2 compliant, the RoW cars weren't. Most OBD2 code readers should be able to read a present fault code, but might not read a pending code. For example, with my 1998 C2 I used to get fault codes P1123 and P1125 when I connectd the car to a PST2. At that time (before I had a PST2 of my own) I had a hand-held code reader/scanner, and when I connected that, it did not show any faults. (The problem was the MAF sensor, by the way). P1123/25 will trigger the CEL on a US car with DME5.2.2, but not a UK car. I think there must be two fault registers for the different types of code.
If you can stretch to it, consider the Durametric tester. It is much more versatile than a simple code reader, and will allow you to interrogate the other systems on the car - not just the DME. If you think this may be your first of many Porsches it's a worthwhile investment - and they also have a good resale value on eBay if not!!
Ah yes, the Durametric is my 1st choice but really all I'm looking for is 'some' capability to plug in and check so that at least when speaking to my Independent or OPC I can at least verbally describe what the problem is aswell as presenting an error code.
I was hoping to find a mid range device that could do this.
My birthday is coming though so I may leave subtle hints for wife and kids [
]
Hi Richard
Thanks for the welcome!
I'm currently looking for a 996 Turbo at the moment and had a Boxster in the past. The reader worked on the wifes 2002 Rav4, as had to change one of the oxygen sensors. I seem to remember UK cars were not ODB2 complient till 1999.
This is a source reference. Confirm exact model applicability in the original material.
