14 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHTroubleshooting PIWIS 3 on 996
Reported or suspected cause
sai or emissions related due
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
Bonus - my next step once I get it to see the codes will be to do a ROW flash assuming the problem is the SAI or emissions related due to the fabspeed system.
Leading evidence: 'sai or emissions related due' (1 discussions report identifying this cause; no attributable repair resolution). Across 1 matching discussions, the most frequently mentioned possible cause is 'sai or emissions related due' (1 discussions; 1 report identifying it and 0 suggest it). The most frequently discussed action is 'Use but' (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 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
I use my el-cheapo OBDII reader (<$40 AutoZone) to clear out the stupid SAI codes that pop up from time to time.
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 · Original poster
When I use the latest version, and select 9x6_DME_ME7_8 from the Overview menu, then go to Fault Memory...
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
This conclusion is based off of multiple others using the same image and devices I�m using but with different/newer cars.
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
To help in the PIWIS 3 functions you have to know that 99 c2 uses DME 5.2.2 .......99C4 and all 2000 -2001 uses DME 7.2 ....2003 up 996 uses DME 7.8....
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
To help in the PIWIS 3 functions you have to know that 99 c2 uses DME 5.2.2 .......99C4 and all 2000 -2001 uses DME 7.2 ....2003 up 996 uses DME 7.8....
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
To help in the PIWIS 3 functions you have to know that 99 c2 uses DME 5.2.2 .......99C4 and all 2000 -2001 uses DME 7.2 ....2003 up 996 uses DME 7.8....
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
To help in the PIWIS 3 functions you have to know that 99 c2 uses DME 5.2.2 .......99C4 and all 2000 -2001 uses DME 7.2 ....2003 up 996 uses DME 7.8....
These are separate views of the same evidence. Frequency alone does not establish a fix, and these counts must not be added together.
sai or emissions related due
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
Bonus - my next step once I get it to see the codes will be to do a ROW flash assuming the problem is the SAI or emissions related due to the fabspeed system.
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.
14 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: 20261026T144035Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources
I attempted to search this, but came up null. I have a 2001 996.1 narrow body convertible, just got my PIWIS3, got it activated, and have had a few issues that I am hoping someone can either tell me I am just stupid and missed a step or maybe help me identify that the PIWIS isn't set up properly or something.
Pre-Read: This Porsche has no records, so I am unsure if it's ever been flashed or anything. It does have the full fabspeed intake/full exhaust upgrade. The CEL is on.
The Problem: The PIWIS 3 shows no faults, no codes, nothing to indicate that the CEL is on and it's driving me insane. I am pretty sure I am able to connect, it doesn't autodetect though so I have to manually select 911 / 996 but I would assume this is normal for a 2001. When I use the latest version, and select 9x6_DME_ME7_8 from the Overview menu, then go to Fault Memory... nothing it just says the control unit name and under description it says "? 10000". If I go back to overview and select all control units, then go to Fault Memory... nothing, now every computer just says the control unit name with description as "? 10000". I tried using the older version (I think it's 38.XX...) and it's the same, just that my control unit names are simplified, i.e. instead of 9x6_DME_ME7_8 it simply says DME.
I can pull more screenshots, upload a video of exactly what I am doing from the time I plug in PIWIS until I get to these screens. Let me know what I can do to help troubleshoot. I hope this is just a user error
Selecting 9x6_DME_ME7_8 -> Fault memory
Trying again but selecting all control units
-> fault memory on all control units
Bonus - my next step once I get it to see the codes will be to do a ROW flash assuming the problem is the SAI or emissions related due to the fabspeed system. I tried to skip to that step now just for giggles and it said something along the lines of no programs available to flash.
This seems overly complicated for a CEL. Why not take a simple OBDII reader, plug it in and read/erase the error code. I use my el-cheapo OBDII reader (<$40 AutoZone) to clear out the stupid SAI codes that pop up from time to time.
OP said there are multiple issues. I doubt they are just attempting to clear codes. The biggest issue being this PIWIS problem which needs to be solved.
So where did you get the PIWIS3 software? Is it a knockoff...because a true Porsche PIWIS version is only available to Porsche dealers and cost like $25K per year to lease. Durametric would be a better choice. IMO
To help in the PIWIS 3 functions you have to know that 99 c2 uses DME 5.2.2 .......99C4 and all 2000 -2001 uses DME 7.2 ....2003 up 996 uses DME 7.8....
No, what I'm saying is that the OP says "he" selected DME 7.8..... DME 7.8 was also used on 997 models, and his version of PIWIS ( China boot-leg) may not have the earlier models..
I retired from Porsche before PIWIS 3 was introduced , we were still using PIWIS 2 ( in 2014) and the menu is a little different but if diagnosing a 2001 996 DME 7.2 you would not "select DME 7.8".....
For me to give any more detailed info I would have to have the tester in front of me to go through the menue and see whats there ( and what is not there)
I have a genuine PIWIS 3 and it works with all my 9x6 and 9x7 cars and Cayennes and I don't need to select the DME type it already knows.
If you have a clone/fake PIWIS 3 then the cheaper/early ones will only work with cars that are from 2011>>
If you want a clone tool that works with the 9x6 and 9x7 range you need a PIWIS 2 - be aware again there are 2 versions a cheap one that is so so and a true clone one which works very well
OP if you post a pic of the VCI (hardware that plugs into the car) I should be able to tell you if it's real or not
*Update on my situation* in addition to the autel MaxiFlash Elite, I�ve now tried a VCX SE. It appears that passthru device will not function with 9x6 vehicles. They just do not communicate with any of the modules. This conclusion is based off of multiple others using the same image and devices I�m using but with different/newer cars. I�ve ordered a PIWIS 2 VCI (hopefully the last device) when it arrives next time some week hopefully, I�ll post an update.
Hate it when you get to the end of a thread and someone says "ill post an update"..
It's like bumping into a mate you haven't seen for ages "yeah, we'll go out for a drink some time" you know you won't even call.
And no one ever updates their thread!
@simRen
So true !!! And when you invest interest in helping narrow down the issue , it is even more disconcerting !!
Rennlist should have an " AI nag algorithm " to pester members who leave diagnostic type threads open ended...
This is a source reference. Confirm exact model applicability in the original material.
