7 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHUnhappy with PIWIS diagnostics on my 996
Leading reported evidence
Use epoxy
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 · Original poster
For all 3, I cut out the body a little to relieve pressure on the connector and used epoxy to glue it down solidly.
Leading evidence: 'Use epoxy' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, the most frequently mentioned possible cause is 'virtual machine, or the old os' (1 discussions; 0 report identifying it and 1 suggest it). The most frequently discussed action is 'Run on windows 11' (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 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 · Original poster
It's likely the virtual machine, or the old OS that the PIWIS 3 uses.
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
The latop is rather old, around 10 years, because I couldn't get the VM to run on Windows 11.
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
I got the Acronis-based version of PIWIS 3 running on Windows 11 native, not on a virtual machine.
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
I did manage to set my newer laptop set up with dual boot so I could run the PIWIS software BUT then a later Win 11 release killed that.
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.
911uk: 1 discussions
0 evidence records excluded for query context · 0 excluded by outcome qualification · 0 adjusted by outcome qualification.
1 acknowledgements have no verified action link; they do not establish a repair result.
I am trying in vain to fix multiple problems with my 2001 996. I have
1) enthusiast level Durametric
2) Autel Mk905
3) PIWIS 3 clone
4) low-level Foxwell
The Autel's data logging capabilities are bad. You can save a log, but then there's no good way to process the data. The PIWIS is clunky. I might have got what I wanted, but to hard to tell. Usability is lacking.
The Durametric might have good logging capabilities, but not for the transmission in 2001. It has zero ability and generally sucks in the transmission area.
Any clue at to what tool actually works? Lots of money and time, crap for results.
Sorry but sounds like user error, my piwis 3 clone was pretty easy to figure out. Maybe if you post your problem and piwis screenshots someone on here can help.
It certainly could be. It also depends on what year you have and what you're doing. The 2001 TipTronic has limited information going through the bus and the data rate isn't fast. The PIWIS only seems to allow 5 data types to be logged at a time, and I'm wanting to watch every bit of data I can to rule out and narrow down the issues.
Selecting data elements is touchy. It's likely the virtual machine, or the old OS that the PIWIS 3 uses. I have both a mouse, a touchscreen, and a trackpad on the laptop I have dedicated to this. Somehow, the VM is getting some of those input sources confused or making them inaccurate. The latop is rather old, around 10 years, because I couldn't get the VM to run on Windows 11. It has an SSD and at least 16 GB. I did manage to set my newer laptop set up with dual boot so I could run the PIWIS software BUT then a later Win 11 release killed that.
I bought 3 of the VCIs. The first worked but soon stopped and showed invalid device (showed VID/PID of zero). This is at the Windows level, below the VM. The 2nd one didn't work at all. The 3rd has a very loose connector internally. For all 3, I cut out the body a little to relieve pressure on the connector and used epoxy to glue it down solidly.
What model are you using it on?
996.2 manual on a 10 year old laptop on windows 10.
I've heard people complain about the interface breaking but this hasn't happened to me, I'm careful not to kink or tug the cable. I found the image for free from PDKpirates. Closing and reopening the VM takes a lot of time so if I'll be using it a few times within days I'll just close the lid to send the laptop to sleepand when I open it the VM and PIWIS are still running.
It's not fast by any means, but are any of these interfaces? I coded my old Giulia and Multiecuscan was not only just as slow, it was not connecting reliably either
Do you recall where you got the VAS6154? There are many available, but only 1 of the 3 I bought from AliExpress work. The connector on the one that does is sketchy. The other two seem to have gotten their flash corrupted because the USB Vendor and Product IDs are 0 - so Windows can't recognize them. They're alive and talking, but drunk and disorderly.
I am going to download the PDK Pirates version and do a binary compare with the one I already have to see if it's any different. I'm also going to try and create a bootable partition from this VM image so I am running it directly. There are functions that seem to be missing or don't work, but maybe that's because of the unruly transmission from 1999-2001. It's not very extroverted and doesn't like to talk.
I will post a more detailed write-up later, but I have made great progress.
I got the Acronis-based version of PIWIS 3 running on Windows 11 native, not on a virtual machine. I also bought a Topdon Rlink X7 dongle and got it working with PIWIS. It is constructed a lot better than the 6154 cheap clones, and doesn't have any restrictions on being connected to the Internet. In fact, it prefers to be connected.
I don't know if it has any limitations yet.
