15 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHPIWIS 3 No Communication
Leading reported evidence
Check on
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.
Leading evidence: 'Check on' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, The most frequently discussed action is 'Check on' (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 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
Make sure that you disconnect the device from the host and attach it to the VM.
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
You could also unplug it, plug it back in (while the VM is running) and VMWare should prompt you to do the same.
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.
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
I'm not a Computer Guru, but I have noticed viewing some Chat on PIWIS 3 clones, that there are different software/firmware numbers of the VAS 6154 and some only work with specific PIWIS 3 clones set-ups ...
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
I'm not a Computer Guru, but I have noticed viewing some Chat on PIWIS 3 clones, that there are different software/firmware numbers of the VAS 6154 and some only work with specific PIWIS 3 clones set-ups ...
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.
15 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 · 1 excluded by outcome qualification · 0 adjusted by outcome qualification.
0 acknowledgements have no verified action link; they do not establish a repair result.
Generation: 20261027T173940Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources
Hi, I got a PIWIS 3 clone from a reputable seller and when I go into modules I am not getting any Communication. Works no issues on my Macan recognizes car once it's plugged in. On my 2000 996 I have to enter it manually. Has anyone ran into this issue with a 996 before?
Thanks
Looks like your problem is in the VCI and not the PIWIS software...
What VCI are you using ??
When you chose 996 in the PIWIS menu it should tell the VCI to configure for 996 interface...then the PIWIS screen should have 996 in the upper left and not "911" ...
Looks like the VCI is not able to configure to 996 .....( Macan uses CANBUS Protocol)
Make sure that you disconnect the device from the host and attach it to the VM. It's under the VM option in VMWare. You could also unplug it, plug it back in (while the VM is running) and VMWare should prompt you to do the same.
I'm not a Computer Guru, but I have noticed viewing some Chat on PIWIS 3 clones, that there are different software/firmware numbers of the VAS 6154 and some only work with specific PIWIS 3 clones set-ups ...
So what I am saying is that not all VAS 6154 VCI's are the same and compatible with all PIWIS 3 clones...
