Hi Guys, as a new 3200GT owner I thought I might update this old thread with my recent experiences getting UNIDIAG to work and write a quick guide on this as of 2026. So here goes, will try to make this as short as possible while still having all details.
**images and final edit to come**
What you will need:
1. A windows laptop. I don’t believe there is any need for this to running Window XP or anything like that, mine is on Windows10 and worked just fine.
2. A V.A.G. “Vagcom” clone OBD2 cable with an FTDI chip (not a CH340 chip - more on this below) These are available cheaply on Ali Express, EBay, Amazon etc. As a longtime owner of a 2001 Audi S4 I happened to already have one, and one with the CH340 chip.
3. A OBD2 to Fiat 3 pin adapter. Again available cheaply on Ali Express, EBay, Amazon etc. It needs to have red +ve lead in addition to the main cable. If it has a black -ve lead as well that is ok but not required.
4. UNIDIAG software, download this from https://www.maserati3200.net/ under “OBDII resources”
5. A wire to run from the battery +ve terminal to connect to the red lead on the three pin adapter. About 3-4m long with small alligator clips on either end.
Steps:
1. Once you have downloaded the zip file as above extract it to a suitable location on your computer, I used “ C:\Program Files\OBDII resource” Then open the folder “UniDiagKWP2000_0_5_0_11/UniDiagKWP2000_0_5_0_11” and look for the application “UniDiagKWP2000”, this is what you will run to diagnose your engine ECU. Right click on it and select “create shortcut” then move this shortcut onto your desktop screen so you has easy access to it.
2. Connect your OBD2 cable to one of the laptop’s USB ports. Windows should recognise it as a new device and automatically install drivers for it.
3. (Optional step). Go to Device Manager on your computer to check that you have the correct cable, that drivers are installed correctly and that the cable is configured to the correct port. Right click the start menu and select “device manager”, then scroll down to “Ports (COM & LPT)” where you should see something like this…
If you have a CH340 chip it will say “USB Serial CH340 (COM1)
Click on the line for USB Serial Port and it will bring up this:
Notice it says manufacturer is FTDI. If it says CH340 instead of FTDI you have the wrong cable and it won’t work, order a FTDI cable.
Under the ports settings>advanced you can select what port you want the cable assigned to. I believe COM1-4 can work but would recommend COM1, that was the only available port on my computer and was what worked for me. I found modifying the other advanced settings as detailed earlier in this thread was unnecessary, mine worked fine with the defaults.
4. Start UNIDIAG. Select the connect tab. In the window on the left of the screen under the connect button it should ideally show the port selected above, i.e. Comm 1, but it may just show a string of hexadecimal numbers that represents this port i.e. 0x00000011, either is fine.
But if there is nothing in this window the software is not recognising the cable, probably because you have a CH340 cable, and there is no point going any further before you remedy this. Manually writing COM 1 into this field will not work, you will get and error message as below.
5. Go to car and locate the grey three pin adapter for the engine ECU above the right side of the drivers footwell (rhd car). This may require pulling the carpet out from around the bonnet release lever.
Connect your computer to this via the 3 pin adapter cable and OBD2 cable. Now open the boot and run your wire direct from the battery +ve terminal to the footwell and connect it to the red lead on the 3-pin adapter. Be very careful not to short it out on any exposed bodywork. I tried taking a positive feed from the cigarette lighter but this did not work, I have no idea why not, my advice is eliminate a variable and take a direct feed from the battery.
6. Turn the ignition on (no need to start the engine). Open UNIDIAG and under “init type” select 5 baud, you need to do this manually each time. Now select “Start + ID” or “Start Comm 2000”. Once you have done this you should get some numbers in “Keyword Recieved” field. This indicates that it has established communication. Now you can go to the diagnose tab and click “Read DTC by Status” to get your fault codes.
**images and final edit to come**
What you will need:
1. A windows laptop. I don’t believe there is any need for this to running Window XP or anything like that, mine is on Windows10 and worked just fine.
2. A V.A.G. “Vagcom” clone OBD2 cable with an FTDI chip (not a CH340 chip - more on this below) These are available cheaply on Ali Express, EBay, Amazon etc. As a longtime owner of a 2001 Audi S4 I happened to already have one, and one with the CH340 chip.
3. A OBD2 to Fiat 3 pin adapter. Again available cheaply on Ali Express, EBay, Amazon etc. It needs to have red +ve lead in addition to the main cable. If it has a black -ve lead as well that is ok but not required.
4. UNIDIAG software, download this from https://www.maserati3200.net/ under “OBDII resources”
5. A wire to run from the battery +ve terminal to connect to the red lead on the three pin adapter. About 3-4m long with small alligator clips on either end.
Steps:
1. Once you have downloaded the zip file as above extract it to a suitable location on your computer, I used “ C:\Program Files\OBDII resource” Then open the folder “UniDiagKWP2000_0_5_0_11/UniDiagKWP2000_0_5_0_11” and look for the application “UniDiagKWP2000”, this is what you will run to diagnose your engine ECU. Right click on it and select “create shortcut” then move this shortcut onto your desktop screen so you has easy access to it.
2. Connect your OBD2 cable to one of the laptop’s USB ports. Windows should recognise it as a new device and automatically install drivers for it.
3. (Optional step). Go to Device Manager on your computer to check that you have the correct cable, that drivers are installed correctly and that the cable is configured to the correct port. Right click the start menu and select “device manager”, then scroll down to “Ports (COM & LPT)” where you should see something like this…
If you have a CH340 chip it will say “USB Serial CH340 (COM1)
Click on the line for USB Serial Port and it will bring up this:
Notice it says manufacturer is FTDI. If it says CH340 instead of FTDI you have the wrong cable and it won’t work, order a FTDI cable.
Under the ports settings>advanced you can select what port you want the cable assigned to. I believe COM1-4 can work but would recommend COM1, that was the only available port on my computer and was what worked for me. I found modifying the other advanced settings as detailed earlier in this thread was unnecessary, mine worked fine with the defaults.
4. Start UNIDIAG. Select the connect tab. In the window on the left of the screen under the connect button it should ideally show the port selected above, i.e. Comm 1, but it may just show a string of hexadecimal numbers that represents this port i.e. 0x00000011, either is fine.
But if there is nothing in this window the software is not recognising the cable, probably because you have a CH340 cable, and there is no point going any further before you remedy this. Manually writing COM 1 into this field will not work, you will get and error message as below.
5. Go to car and locate the grey three pin adapter for the engine ECU above the right side of the drivers footwell (rhd car). This may require pulling the carpet out from around the bonnet release lever.
Connect your computer to this via the 3 pin adapter cable and OBD2 cable. Now open the boot and run your wire direct from the battery +ve terminal to the footwell and connect it to the red lead on the 3-pin adapter. Be very careful not to short it out on any exposed bodywork. I tried taking a positive feed from the cigarette lighter but this did not work, I have no idea why not, my advice is eliminate a variable and take a direct feed from the battery.
6. Turn the ignition on (no need to start the engine). Open UNIDIAG and under “init type” select 5 baud, you need to do this manually each time. Now select “Start + ID” or “Start Comm 2000”. Once you have done this you should get some numbers in “Keyword Recieved” field. This indicates that it has established communication. Now you can go to the diagnose tab and click “Read DTC by Status” to get your fault codes.
Attachments
Last edited:
