This is a way to setup the PIWIS 2 software as a virtual machine (VM) inside Oracle’s VirtualBox, which is free VM software.
Videos of the setup process and using PIWIS are at the bottom of this post.
Link to programming options in development mode here:
Programming: - PIWIS 2: coding using development mode
Software setup
The setup procedure below is for the PIWIS software only. To connect to your car and do diagnostic procedures you will need to purchase the hardware (cable). You can just setup the VM and use the simulation mode in PIWIS to have a play prior to purchasing the hardware if you like.
To the people who made originally did the work to make this available, I take my hat off to you. There was clearly a lot of effort from some very smart people that allowed someone like me to get access to the software.
Background info:
PIWIS 2 runs natively in Windows XP. XP is no longer supported, and it is difficult to acquire an old computer that runs XP and keep it running. Using the software in a VM, whilst slower, will ensure you are able to keep the software forever regardless of the computer you use. I use a laptop that was pretty slick back in 2014, but is pretty slow by today’s standards. It takes a few minutes to get the VM loaded, but after that it’s as fast as any diagnostic software I’ve used in the past on other car types.
A while ago I was fortunate enough to stumble on a link to PIWIS 2 as a bunch of files that, through a specified process got software loaded and licensed on either an XP computer or a VM. Not having an XP computer, I went down the road of creating a VM.
Once the VM was created and the software licensed, it was a simple process of making a backup of the VM. This backup can then be imported to VirtualBox on any computer as an XP image with the PIWIS software already installed. There are only a few things that need to be done once the VM is created so that it’s good to go. It’s a surprisingly simple process.
Requirements:
For those who don’t know what a VM is, Google it and do some reading. Very simply you are creating a separate computer (guest) within your computer (host). You allocate resources from your host (RAM, etc.) and run the guest within a window on your normal desktop.
Here’s how to set it up.
1. Google ‘VirtualBox downloads’. Go to the download page and download the latest version of VirtualBox for the platform you use (PC, mac, etc.). On the same page, download the extension pack. The extension pack isn’t platform specific and is the same file for all operating systems.
![Image]()
2. Log into your computer into the administrator account. Install VirtualBox. Once installed, open the program and then install the extension pack. You can’t install the extension pack unless you are logged in as an administrator. Installing the extension pack needs to be done from the preferences window of the VirtualBox program. If required, Google for how to do this. There are lots of videos how. Image below is what it should look like after the extension pack is installed. If not installed, it won’t be listed. Click the + button (red circle), find the extension pack file you downloaded and select it to be installed.
![Image]()
3. Once VirtualBox and the extension pack have been installed you can log out of the administrator account if you want and login where you normally work.
4. Download the .ova file from the following link. It’s about 12.3 GB. This is the backup file of the VM. Depending on the browser you use, it might sometimes give a network error, and you will have to start again. Try another browser if you are getting this error. Also, when you ask to download the file, google drive will give you a warning that the file size is too large to virus scan. The machine where I created the file uses up to date virus scanning software. I’m confident it’s clean, but only you can make the decision of whether to download. I’ve downloaded the file to other machines and created the VM with no problems. Many thousands have downloaded the file with no adverse feedback.
PIWIS VM.ova
5. Open VirtualBox. Go to file, then import appliance. Go to the .ova file you just downloaded and select this. There are a few clicks of OK, and then allow the new VM to be created. It will take a few minutes.
6. If you have a cable, don’t connect it yet, we’ll do that later.
Update: For some reason after a few years the imprint for the tester expires and you will get blank menus, rendering the PIWIS diagnostics useless. KlausS98 came up with a very elegant solution, which is to start from a batch file that starts the VM and resets the date back to 2019, which stops the blank menu problem. Instead of starting the VM as described below in step 7, start Virtualbox, then click on the batch file. This will start the PIWIS VM and reset the date. I have saved the batch file to my desktop so it's easy to access. Note this only works for Windows platforms.
Update: Nov 22. The batch file isn't doing what it used to unfortunately. Klaus is looking into it. Until then I've found a workaround that is simple, but needs to be done each time you start the machine. Look at the video titled 'More PIWIS information' at the bottom of this post for the workaround.
Link to batch file:
PIWIS start window platform.bat
Link to thread explaining the problem:
PIWIS 2 virtual machine troubleshooting
7. Start the VM (should be called PIWIS) by either clicking the batch file as described above, or by selecting PIWIS in the left pane and then click start. It will now start Windows XP. This will take a few minutes for the virtual machine to fully load.
8. Right click on the ‘shortcut to praegeng.xml’ file and open in notepad. Go to the line that has ‘validationstring’ and change the ‘x’ to ‘9999’. This will now give the software a license validation time of 9999 days. Save then close.
![Image]()
9. Click on the PIWIS shortcut on the desktop (the car icon). When PIWIS starts, select diagnosis and then select the car you have. If you don’t have a cable connected it will tell you this and give you the option of using simulation mode to continue.
10. PIWIS is setup to operate in ‘V’ mode (after sales mode), which is what is used in the dealership. You can change to either of the other modes, E = developer, or P = production. When you initially open the program and you get the first page with the picture of the Cayman, click settings, then diagnostic configuration and then choose the model line. Click the mode tab at the top, and now you can go down to ‘operating mode’ and change the mode of the software. Save. Close. Now open the diagnostics for your car type and you should be in the new mode.
![Image]()
The vast majority of stuff you will want to change will be available in V (after sales) mode.
NOTE 1: The developer mode is in German only.
NOTE 2: Production mode doesn’t seem to work and locks you out of the program. I would suggest not using this. If you accidentally do select this, delete the VM (from the VirtualBox software window) and then create a new VM from the ova file you downloaded.
Connecting the cable
There are a few things that need to be understood prior to connecting the cable.
1. Open VirtualBox but don’t start the VM.
2. Have both cables connected to the interface, then plug into OBD port. Wait a few bananas.
3. Plug cable into computer.
4. Go to VirtualBox, Settings, USB. Click the small USB button on the right with the +, and then select the cable. Picture below shows what it should look like once done.
![Image]()
5. Now start VM, preferably by using the batch file (link above). When the VM starts it should see the new hardware and try and automatically install the driver. Be patient. It will take a few minutes for the VM to completely boot and detect the new hardware. One the wizard opens, ask it to search for the driver and let it install. This will take a few minutes. If this doesn't happen, go to Control panel/System/Hardware/Device manager then click on the + next to LibUSB Win32 devices. If you see "HSX interface" then all is good. If you see 'unknown device' right click and select 'update driver'. The wizard should now run to do this.
6. Now start the PIWIS program by clicking on the icon. It should update the firmware on the cable hardware when opening. I've had a problem sometimes on first connection where the interface firmware is updated. Immediately afterwards the interface won't connect to PIWIS and it wants to start in simulation mode. If this happens, close down the VM and start the process again. The interface driver and firmware won't need to be updated and the interface should now connect correctly and start in full diagnostic mode.
7. Once PIWIS is open and you have the window with the picture of the Cayman on it, you can use any part of the program. However to do diagnostics (select 'diagnostics' then your car type) you will now need the ignition on. If you don't have the ignition on the program will open OK but you won't be able to do anything as the CAN bus and control units aren't fired up. With the key out I've found it just hangs when you try and interrogate a control unit. If the key is in only but not turned on it tells you to turn the ignition on.
8. Next time you use the software all the drivers will be loaded, but ensure you connect everything in the same order as described above (except the bits that are clearly for installing stuff).
NOTE: Every time I use PIWIS, prior to starting the VM, I conduct step 5 to check the cable has been recognized by VirtualBox. I simply click on the + and see what USB devices VirtualBox can see at that moment. The Samtec interface should be in the list that immediately appears. If you haven't done everything in the correct order, you will see 'unknown device'. If this is the case, start the process again. I find that if I do this, I don't go through the whole process of starting the VM and then PIWIS to find out it hasn't connected correctly.
Once the VM is open you can hover over the USB symbol at the bottom of the VM window and you should see 'HSX interface'.
I also go through the last bit of step 5 above in control panel to see that I see 'HSX interface' in device manager. Then I know the interface is working fine and the VM has recognised it correctly.
Interface hardware options
When you purchase the interface you don’t need a hard drive with the software loaded, which they will most likely try and sell you as well. I bought the obd2.market cable and it has failed three times. The first time it was replaced under warranty, the second I had to pay a substantial amount to have it fixed. Third time, less than 12 months after the previous failure the seller wants to fleece me again for another fix. These units from obd2.market are clearly pretty fragile, so I wouldn't recommend this interface due to the quality of the product and the attitude of the business. I'm not sure if all of these aftermarket devices are made in the same factory, so I don't know if the other vendors sell a device of different quality.
Update: I just purchased another interface, this time from obd2store.com. Purchase experience was a good one and it works perfectly.
Interestingly I sent them photos of my old interface's circuit board and asked if they could fix it. They replied that it looked nothing like what they sold and so they didn't have the confidence to attempt a fix. This tells me there are interfaces of differing architecture on the market, and they don't all come from the same manufacturer. Hopefully this one will last a little longer
For different options internet search 'PIWIS 2 samtec interface'.
Thread dedicated to feedback of experience with different interfaces here:
PIWIS 2 interface failures
Additional VM information
Other details of the VM for those interested.
Guest additions doesn’t need to be installed as it is already in the ova file.
Two cores have been selected for processing. I initially used one and via Task Manager could see it was running at 100% for a lot of the time. Changing to two had it below 100% nearly all the time so I stuck with that. It was also noticeably faster when using two cores.
The most RAM I saw being used was about 950 MB. I’ve selected 1.5 GB to ensure it covers this easily. If you are short on RAM, you may want to tweak this.
Videos
Video of the setup process here:
Video of PIWIS use here
Having had two failures of the interface I fitted a USB fan to keep it cool and hopefully stop the failures. Video here.
Videos of the setup process and using PIWIS are at the bottom of this post.
Link to programming options in development mode here:
Programming: - PIWIS 2: coding using development mode
Software setup
The setup procedure below is for the PIWIS software only. To connect to your car and do diagnostic procedures you will need to purchase the hardware (cable). You can just setup the VM and use the simulation mode in PIWIS to have a play prior to purchasing the hardware if you like.
To the people who made originally did the work to make this available, I take my hat off to you. There was clearly a lot of effort from some very smart people that allowed someone like me to get access to the software.
Background info:
PIWIS 2 runs natively in Windows XP. XP is no longer supported, and it is difficult to acquire an old computer that runs XP and keep it running. Using the software in a VM, whilst slower, will ensure you are able to keep the software forever regardless of the computer you use. I use a laptop that was pretty slick back in 2014, but is pretty slow by today’s standards. It takes a few minutes to get the VM loaded, but after that it’s as fast as any diagnostic software I’ve used in the past on other car types.
A while ago I was fortunate enough to stumble on a link to PIWIS 2 as a bunch of files that, through a specified process got software loaded and licensed on either an XP computer or a VM. Not having an XP computer, I went down the road of creating a VM.
Once the VM was created and the software licensed, it was a simple process of making a backup of the VM. This backup can then be imported to VirtualBox on any computer as an XP image with the PIWIS software already installed. There are only a few things that need to be done once the VM is created so that it’s good to go. It’s a surprisingly simple process.
Requirements:
- A reasonably fast computer. Most modern laptops will easily do the job.
- A minimum of 1.5GB of excess RAM (this is what is going to be allocated to the VM). Use Task Manager to see what is normally used. 8GB of RAM on a standard Windows 10 install should easily have enough to spare. 4GB probably won’t.
- A minimum of 20 GB of spare hard drive capacity. This is what VirtualBox and the VM will take once installed.
For those who don’t know what a VM is, Google it and do some reading. Very simply you are creating a separate computer (guest) within your computer (host). You allocate resources from your host (RAM, etc.) and run the guest within a window on your normal desktop.
Here’s how to set it up.
1. Google ‘VirtualBox downloads’. Go to the download page and download the latest version of VirtualBox for the platform you use (PC, mac, etc.). On the same page, download the extension pack. The extension pack isn’t platform specific and is the same file for all operating systems.
2. Log into your computer into the administrator account. Install VirtualBox. Once installed, open the program and then install the extension pack. You can’t install the extension pack unless you are logged in as an administrator. Installing the extension pack needs to be done from the preferences window of the VirtualBox program. If required, Google for how to do this. There are lots of videos how. Image below is what it should look like after the extension pack is installed. If not installed, it won’t be listed. Click the + button (red circle), find the extension pack file you downloaded and select it to be installed.
3. Once VirtualBox and the extension pack have been installed you can log out of the administrator account if you want and login where you normally work.
4. Download the .ova file from the following link. It’s about 12.3 GB. This is the backup file of the VM. Depending on the browser you use, it might sometimes give a network error, and you will have to start again. Try another browser if you are getting this error. Also, when you ask to download the file, google drive will give you a warning that the file size is too large to virus scan. The machine where I created the file uses up to date virus scanning software. I’m confident it’s clean, but only you can make the decision of whether to download. I’ve downloaded the file to other machines and created the VM with no problems. Many thousands have downloaded the file with no adverse feedback.
PIWIS VM.ova
5. Open VirtualBox. Go to file, then import appliance. Go to the .ova file you just downloaded and select this. There are a few clicks of OK, and then allow the new VM to be created. It will take a few minutes.
6. If you have a cable, don’t connect it yet, we’ll do that later.
Update: For some reason after a few years the imprint for the tester expires and you will get blank menus, rendering the PIWIS diagnostics useless. KlausS98 came up with a very elegant solution, which is to start from a batch file that starts the VM and resets the date back to 2019, which stops the blank menu problem. Instead of starting the VM as described below in step 7, start Virtualbox, then click on the batch file. This will start the PIWIS VM and reset the date. I have saved the batch file to my desktop so it's easy to access. Note this only works for Windows platforms.
Update: Nov 22. The batch file isn't doing what it used to unfortunately. Klaus is looking into it. Until then I've found a workaround that is simple, but needs to be done each time you start the machine. Look at the video titled 'More PIWIS information' at the bottom of this post for the workaround.
Link to batch file:
PIWIS start window platform.bat
Link to thread explaining the problem:
PIWIS 2 virtual machine troubleshooting
7. Start the VM (should be called PIWIS) by either clicking the batch file as described above, or by selecting PIWIS in the left pane and then click start. It will now start Windows XP. This will take a few minutes for the virtual machine to fully load.
8. Right click on the ‘shortcut to praegeng.xml’ file and open in notepad. Go to the line that has ‘validationstring’ and change the ‘x’ to ‘9999’. This will now give the software a license validation time of 9999 days. Save then close.
9. Click on the PIWIS shortcut on the desktop (the car icon). When PIWIS starts, select diagnosis and then select the car you have. If you don’t have a cable connected it will tell you this and give you the option of using simulation mode to continue.
10. PIWIS is setup to operate in ‘V’ mode (after sales mode), which is what is used in the dealership. You can change to either of the other modes, E = developer, or P = production. When you initially open the program and you get the first page with the picture of the Cayman, click settings, then diagnostic configuration and then choose the model line. Click the mode tab at the top, and now you can go down to ‘operating mode’ and change the mode of the software. Save. Close. Now open the diagnostics for your car type and you should be in the new mode.
The vast majority of stuff you will want to change will be available in V (after sales) mode.
NOTE 1: The developer mode is in German only.
NOTE 2: Production mode doesn’t seem to work and locks you out of the program. I would suggest not using this. If you accidentally do select this, delete the VM (from the VirtualBox software window) and then create a new VM from the ova file you downloaded.
Connecting the cable
There are a few things that need to be understood prior to connecting the cable.
- When you plug into the car, ensure you push hard so it clicks in. The cable should have a wire screwed on one side. This is what clicks over a clip at the back of the fuse panel that keeps it in place so you can drive and have it bump around and not dislodge.
- The cable gets two power sources from the car. Terminal 30 (on all the time), and terminal 15 (on when the ignition is turned on)
- The interface uses terminal 30 to make it run, and I'm assuming uses terminal 15 power to indicate the car ignition is on. This means the interface will work fine with the ignition off and key removed, but to do diagnostics the ignition needs to be on so the car's control units and CAN bus are active.
- The cable interface is like a computer by itself, and will only work and be recognized by your computer when the plug is connected to the car.
- When you start the VM, the cable needs to be powered, and the VM needs to be setup to immediately recognize the cable and mount it as the VM starts. If it doesn’t do it when it starts, you won’t be able to connect it afterwards once the VM is running.
- You can go through the entire connection process all the way to opening the diagnostic program with the ignition turned off, but the plug must remain connected to keep the terminal 30 power to the interface. If you unplug the cable from the car at any stage you will power it down, and so to get it connected again you will need to start the connection process from the beginning.
- Some control units you can interrogate with the ignition off, some will need the ignition on.
1. Open VirtualBox but don’t start the VM.
2. Have both cables connected to the interface, then plug into OBD port. Wait a few bananas.
3. Plug cable into computer.
4. Go to VirtualBox, Settings, USB. Click the small USB button on the right with the +, and then select the cable. Picture below shows what it should look like once done.
5. Now start VM, preferably by using the batch file (link above). When the VM starts it should see the new hardware and try and automatically install the driver. Be patient. It will take a few minutes for the VM to completely boot and detect the new hardware. One the wizard opens, ask it to search for the driver and let it install. This will take a few minutes. If this doesn't happen, go to Control panel/System/Hardware/Device manager then click on the + next to LibUSB Win32 devices. If you see "HSX interface" then all is good. If you see 'unknown device' right click and select 'update driver'. The wizard should now run to do this.
6. Now start the PIWIS program by clicking on the icon. It should update the firmware on the cable hardware when opening. I've had a problem sometimes on first connection where the interface firmware is updated. Immediately afterwards the interface won't connect to PIWIS and it wants to start in simulation mode. If this happens, close down the VM and start the process again. The interface driver and firmware won't need to be updated and the interface should now connect correctly and start in full diagnostic mode.
7. Once PIWIS is open and you have the window with the picture of the Cayman on it, you can use any part of the program. However to do diagnostics (select 'diagnostics' then your car type) you will now need the ignition on. If you don't have the ignition on the program will open OK but you won't be able to do anything as the CAN bus and control units aren't fired up. With the key out I've found it just hangs when you try and interrogate a control unit. If the key is in only but not turned on it tells you to turn the ignition on.
8. Next time you use the software all the drivers will be loaded, but ensure you connect everything in the same order as described above (except the bits that are clearly for installing stuff).
NOTE: Every time I use PIWIS, prior to starting the VM, I conduct step 5 to check the cable has been recognized by VirtualBox. I simply click on the + and see what USB devices VirtualBox can see at that moment. The Samtec interface should be in the list that immediately appears. If you haven't done everything in the correct order, you will see 'unknown device'. If this is the case, start the process again. I find that if I do this, I don't go through the whole process of starting the VM and then PIWIS to find out it hasn't connected correctly.
Once the VM is open you can hover over the USB symbol at the bottom of the VM window and you should see 'HSX interface'.
I also go through the last bit of step 5 above in control panel to see that I see 'HSX interface' in device manager. Then I know the interface is working fine and the VM has recognised it correctly.
Interface hardware options
When you purchase the interface you don’t need a hard drive with the software loaded, which they will most likely try and sell you as well. I bought the obd2.market cable and it has failed three times. The first time it was replaced under warranty, the second I had to pay a substantial amount to have it fixed. Third time, less than 12 months after the previous failure the seller wants to fleece me again for another fix. These units from obd2.market are clearly pretty fragile, so I wouldn't recommend this interface due to the quality of the product and the attitude of the business. I'm not sure if all of these aftermarket devices are made in the same factory, so I don't know if the other vendors sell a device of different quality.
Update: I just purchased another interface, this time from obd2store.com. Purchase experience was a good one and it works perfectly.
Interestingly I sent them photos of my old interface's circuit board and asked if they could fix it. They replied that it looked nothing like what they sold and so they didn't have the confidence to attempt a fix. This tells me there are interfaces of differing architecture on the market, and they don't all come from the same manufacturer. Hopefully this one will last a little longer
For different options internet search 'PIWIS 2 samtec interface'.
Thread dedicated to feedback of experience with different interfaces here:
PIWIS 2 interface failures
Additional VM information
Other details of the VM for those interested.
Guest additions doesn’t need to be installed as it is already in the ova file.
Two cores have been selected for processing. I initially used one and via Task Manager could see it was running at 100% for a lot of the time. Changing to two had it below 100% nearly all the time so I stuck with that. It was also noticeably faster when using two cores.
The most RAM I saw being used was about 950 MB. I’ve selected 1.5 GB to ensure it covers this easily. If you are short on RAM, you may want to tweak this.
Videos
Video of the setup process here:
Video of PIWIS use here
Having had two failures of the interface I fitted a USB fan to keep it cool and hopefully stop the failures. Video here.
