Received my new PIWIS III
#1981
42.400.xxx is V/E I would forget about P as you should never use it. For your year cars V38 or V40 is sufficient.
Forget belauto, @rnlst_log is your go to person. NOT recommended by some but by most if not all.
siberian
Forget belauto, @rnlst_log is your go to person. NOT recommended by some but by most if not all.
siberian
The following users liked this post:
JB911 (09-01-2024)
#1982
#1984
#1985
Sorry to jump in here if it's inappropiate, but I have a PIWIS III V41.5/38.250 and now a V42.3/38.250 image. I can't get them to program EU2 emissions on my 996, regardless if I use a VNCI PT3G or a VAS6154a. The VAS6154a will read the vehicle modules (after manual selection), but the VNCI has trouble, even if I bridge pins 3 and 7 on the OBD port.
I can sell the VNCI PT3G (its from VXDAS) if anybody wants it. I'm thinking of getting the Tabscan, or if any Tabscan folks want to loan/rent me the device, that works. I'll be happy to pay a deposit in addition to the rental, just like the rental PIWIS guys on eBay.
This could be a good option for a little side Porsche income.
I plan on uploading the V42 image to the internet archive, but you will need to use a keygen for the imprint, since the serial numbers of the PC will change.
I can sell the VNCI PT3G (its from VXDAS) if anybody wants it. I'm thinking of getting the Tabscan, or if any Tabscan folks want to loan/rent me the device, that works. I'll be happy to pay a deposit in addition to the rental, just like the rental PIWIS guys on eBay.
This could be a good option for a little side Porsche income.
I plan on uploading the V42 image to the internet archive, but you will need to use a keygen for the imprint, since the serial numbers of the PC will change.
Last edited by Justin Browning; 09-25-2024 at 12:11 PM. Reason: add information/corrected version numbers
#1986
The link to the Internet Archive upload is https://archive.org/details/PIWIS4v42.3. Give it about 8 or so hours and it should be processed on the IA side. It is a clonezilla image, so you will need to download clonezilla and boot from USB to copy the image to a partition. You can do this all within a VM, just place the files on media that you can access, use clonezilla in image mode and restore from image to disk. Make sure to specify the location of the files as your repository for clonezilla.
If you wanted to do this completly in a VM, mount the clonezilla ISO, create two disks, one at 256GB (the one you are restoring to) and another at least 60GB (the repository). Copy the downloaded files into the 60GB disk image and restore it to the 256GB disk image.
You may be able to do it mounting the folder that houses the data as a shared folder (if you are using VMWare, Virtualbox might do it as well), and using that as a SAMBA share. Then you would need to adjust the configuration slightly.
To avoid source disk image creation, you could place the files on a USB drive/stick greater than 60GB and then mount that to the VM (detaching from the host in software) and use that as the repository. Which now as I type it, is a way simpler proposition.
If you wanted to do this completly in a VM, mount the clonezilla ISO, create two disks, one at 256GB (the one you are restoring to) and another at least 60GB (the repository). Copy the downloaded files into the 60GB disk image and restore it to the 256GB disk image.
You may be able to do it mounting the folder that houses the data as a shared folder (if you are using VMWare, Virtualbox might do it as well), and using that as a SAMBA share. Then you would need to adjust the configuration slightly.
To avoid source disk image creation, you could place the files on a USB drive/stick greater than 60GB and then mount that to the VM (detaching from the host in software) and use that as the repository. Which now as I type it, is a way simpler proposition.
The following 2 users liked this post by Justin Browning:
David Borden (09-27-2024),
rainer (09-30-2024)
#1987
I have read that the VNCI VCI has issues with the 9x6 series that are yet to be resolved.
I'd recommend PIWIS 1 or PIWIS 2 for the 9x6/9x7 series seems to work a bit better. When you say emissions, what are you trying to do? What year is your 996 and what DME does it have? The early Bosch 5.2.2 need a +5v signal to program them. I don't think the clone tools account for this.
I'd recommend PIWIS 1 or PIWIS 2 for the 9x6/9x7 series seems to work a bit better. When you say emissions, what are you trying to do? What year is your 996 and what DME does it have? The early Bosch 5.2.2 need a +5v signal to program them. I don't think the clone tools account for this.
Last edited by dan_189; 09-25-2024 at 07:30 PM.
#1989
Looking to update my PIWIS 3 setup. Currently on 38.200.017 with a VAS interface. I have not been able to pull DME reports from a 996 Turbo and 997 base that I tested, although I can on a 997 turbo. It does not seem to communicate properly with some of these cars.
I am looking at purchasing a T6P3G and updated PIWIS 3 software. The three options I see so far are:
42.400.050 V/E modes, Full Engineering + 38.250 V/E/P models, Full Engineering Windows 11 from Bell Auto, whom I got the last software from. He has provided good service thus car.
The other option is from mhx_log recommended by some here which is 42.400.037 (not sure on the specifics of the build V/E/P)
In the past, I have read that is is beneficial to have the earlier version, 38.xxx along with the later versions 42.xxx as the 38 version has some capabilities that were removed in the later versions. I dont remember the specifics though.
I deal with earlier 996, 986, 997, 987, 991, 981 cars mostly, but would like the ability to pull DME reports, check and clear codes, troubleshoot cars up to 2020 and possibly newer down the road. I would like to be able to code and possibly program modules if needed on all these generations.
Currently, what is best option? Is getting 38.250 with V/E/P models still beneficial?
They are similarly priced.
I am looking at purchasing a T6P3G and updated PIWIS 3 software. The three options I see so far are:
42.400.050 V/E modes, Full Engineering + 38.250 V/E/P models, Full Engineering Windows 11 from Bell Auto, whom I got the last software from. He has provided good service thus car.
The other option is from mhx_log recommended by some here which is 42.400.037 (not sure on the specifics of the build V/E/P)
In the past, I have read that is is beneficial to have the earlier version, 38.xxx along with the later versions 42.xxx as the 38 version has some capabilities that were removed in the later versions. I dont remember the specifics though.
I deal with earlier 996, 986, 997, 987, 991, 981 cars mostly, but would like the ability to pull DME reports, check and clear codes, troubleshoot cars up to 2020 and possibly newer down the road. I would like to be able to code and possibly program modules if needed on all these generations.
Currently, what is best option? Is getting 38.250 with V/E/P models still beneficial?
They are similarly priced.
VNCI PT3G claims to work with 1996-2022 cars, but I've read mixed reviews about that one. YMMV, as they say.
http://blog.vxdiagshop.com/2024/01/0...-vs-vnci-pt3g/
PIWIS2 clone is ~$500 just for the VCI, laptop + software additional. I used to have one, worked well. Supposedly even works with OBD1 pre 96 cars with the right adapters.
#1990
Whatever path you choose, @rnlst_log is the way to go. On my 992 the T6P3G is lightning fast compared to the VAS. And yes for those models you don't need anything past 38.x
siberian
siberian
#1991
The link to the Internet Archive upload is https://archive.org/details/PIWIS4v42.3. Give it about 8 or so hours and it should be processed on the IA side. It is a clonezilla image, so you will need to download clonezilla and boot from USB to copy the image to a partition. You can do this all within a VM, just place the files on media that you can access, use clonezilla in image mode and restore from image to disk. Make sure to specify the location of the files as your repository for clonezilla.
If you wanted to do this completly in a VM, mount the clonezilla ISO, create two disks, one at 256GB (the one you are restoring to) and another at least 60GB (the repository). Copy the downloaded files into the 60GB disk image and restore it to the 256GB disk image.
You may be able to do it mounting the folder that houses the data as a shared folder (if you are using VMWare, Virtualbox might do it as well), and using that as a SAMBA share. Then you would need to adjust the configuration slightly.
To avoid source disk image creation, you could place the files on a USB drive/stick greater than 60GB and then mount that to the VM (detaching from the host in software) and use that as the repository. Which now as I type it, is a way simpler proposition.
If you wanted to do this completly in a VM, mount the clonezilla ISO, create two disks, one at 256GB (the one you are restoring to) and another at least 60GB (the repository). Copy the downloaded files into the 60GB disk image and restore it to the 256GB disk image.
You may be able to do it mounting the folder that houses the data as a shared folder (if you are using VMWare, Virtualbox might do it as well), and using that as a SAMBA share. Then you would need to adjust the configuration slightly.
To avoid source disk image creation, you could place the files on a USB drive/stick greater than 60GB and then mount that to the VM (detaching from the host in software) and use that as the repository. Which now as I type it, is a way simpler proposition.
Thanks for this. Where did you get the VAS6154a? I can't find any recent links on this thread. Also, is there a separate software to access the Porsche parts catalogue?
#1992
Whatever path you choose, @rnlst_log is the way to go. On my 992 the T6P3G is lightning fast compared to the VAS. And yes for those models you don't need anything past 38.x
siberian
siberian
#1993
he has been a huge help but recent experience with his recommended guy to buy the T6PT3G from has been a bit of a nightmare for me. my unit failed and @rnlst_log spent a lot of time helping me, but i had to collect all sorts of videos repeatedly to convince the T6 dealer there was an issue, and then send it back to China for repairs. it's been a month and the thing is probably lost in customs, tracking hasnt moved since the 7th. i've had to purchase a new one from aliexpress.
#1994
@bigkraig sorry to read of the mishaps, though @rnlst_log doesn't make or sell the dongles it's just someone he deals with or has dealt with that he's had good experiences with. Sh*t happens even with OEM parts that either get lost or don't fit. I wouldn't write him off due to something beyond his control.
@djdonte are you running with an SSD, maxed out the memory, gotten the latest laptop rather than something that's been in your basement for years waiting for a new role...? Also keep in mind that unless you have an EV any version above 41 is probably not needed for your vehicle.
siberian
@djdonte are you running with an SSD, maxed out the memory, gotten the latest laptop rather than something that's been in your basement for years waiting for a new role...? Also keep in mind that unless you have an EV any version above 41 is probably not needed for your vehicle.
siberian
#1995
Another vote for VCX SE here. Works great, quicker than the PIWIS2 clone I had, much quicker than the VAS6154.
VCX SE has had a PIWIS offering for years, can be expanded by purchasing licenses for other brands with the same VCI. Tabscan is the new kid around the block, and I had no interest in being an early adopter for them.
@djdonte you do NOT need a powerful computer to run PIWIS3. I have an i5-5300U, 8GB RAM, 256GB SSD - runs like a champ.
Also, may depend on which vehicle you're trying to scan. A 957 is on a slow architecture while 958 and newer Cayenne respond much faster to the same VCI.
VCX SE has had a PIWIS offering for years, can be expanded by purchasing licenses for other brands with the same VCI. Tabscan is the new kid around the block, and I had no interest in being an early adopter for them.
@djdonte you do NOT need a powerful computer to run PIWIS3. I have an i5-5300U, 8GB RAM, 256GB SSD - runs like a champ.
Also, may depend on which vehicle you're trying to scan. A 957 is on a slow architecture while 958 and newer Cayenne respond much faster to the same VCI.