Reading error codes on an early 3200GT

Contigo

Sponsor
Messages
18,376
Tried the KWP71 software to interrogate the ABS module today but could not get it working for love nor money. Looks like a trip to the Maserati Shed to read my ABS ECu or see once and for all if it is indeed dead and buried.
 

Massa in Perth

New Member
Messages
277
Thanks Andrea. Wonder whose idea it was not to add a search function and to put them on random order... I am getting a headache.
 

Contigo

Sponsor
Messages
18,376
Hi Massa, the 02 code could be a duff sensor but some of them appear and go and with a bit of driving will clear. I will look at the other code for you later.
 

Trev Latter

Member
Messages
1,213
I've just been having a little play with mine. I've got one of the "oddball" 3200s with a non OBD2 ecu and a 16 pin OBD socket. Very late 2000 registered car, but not sure of exact build date.

Good news! KWP2000 Unidiag works fine with a VAGcom/K-line interface plugged straight in without the need for the three pin adaptor (obviously) or a separate 12v power supply.
 

Coxy13

Junior Member
Messages
120
Hey guys,

This thread will save me a whole lotta hurt with my car I hope. At $210 per read at the dealership hopefully I can avoid them!

Ordered my leads today and will let my indy know about it too.....

Cheers lads!

Tim
 

Coxy13

Junior Member
Messages
120
Hi Steve,

This is the issue I am having....

The lead shows it is connected, as you can see:

Connected.jpg

But it won't retrieve the ECU info.....It did it the first time I tried, but never since....

Cannot get ECU Info.jpg

The first time I tried, I got a whole bunch of info about the ECU and also the fault codes, but since clearing it, I haven't been able to re-connect.
 

ledlights

Junior Member
Messages
189
Hi Tim,

It looks like your PC is using the wrong driver i.e. not the FTDI driver and that's why you're not seeing the COM port. I recommend removing both drivers, reinstalling only the FTDI one (all without the lead connected) before trying again. Which version of Windows are you using?

Cheers,

Steve
 

Coxy13

Junior Member
Messages
120
Hi Tim,

It looks like your PC is using the wrong driver i.e. not the FTDI driver and that's why you're not seeing the COM port. I recommend removing both drivers, reinstalling only the FTDI one (all without the lead connected) before trying again. Which version of Windows are you using?

Cheers,

Steve

Hi Steve,

Thanks for getting back to me, Yeah that may be worth a try. I am running 32bit windows 7.

Can you paste the link to the FDTI driver please, I must get the wrong one.....

Tim
 

redsonnylee

Member
Messages
1,540
After much trouble shooting I've used this method and finally got everything working, also it's got me out of a jam with a limp mode yesterday. For anyone else trying this out ,I made a mistake and was trying the red connector, it's the grey one.

I should have read this up a long time ago, highly recommended for any 3200 owner.

A big thanks for this posting.
 

spoutnik

New Member
Messages
3
Hello everybody,

At first sorry for my bad English :thumb1:

I have a question because I have a 3200GT build in year 2000.

I've bought a 3-pin Fiat, Lancia/Alfa adapter and this usb odb http://www.ebay.fr/itm/VGATE-USB-OBD-OBD2-ODB2-OBDII-DIAGNOSTIQUE-SCANNER-DIAG-AUTO-MULTIMARQUES-VAGCOM-/331780967430?hash=item4d3fafcc06:g:xCQAAOSwx-9WxNBp

I 've setup D2XX drivers currently available for FTDI devices here for windows 10 http://www.ftdichip.com/Drivers/D2XX.htm

Then I've connected my ODB adaptor but drivers where never detected.
So I used my drivers included with my ODB adaptor. In that case ODB adaptor is well setup on my computer but KWP2000 software don't recognize it.

Could you tell me if I bought the wrong adaptor USB-ODB or if my problem could be somewhere else ?

In advance thank you for your help.

Matej
 

redsonnylee

Member
Messages
1,540
Hello everybody,

At first sorry for my bad English :thumb1:

I have a question because I have a 3200GT build in year 2000.

I've bought a 3-pin Fiat, Lancia/Alfa adapter and this usb odb http://www.ebay.fr/itm/VGATE-USB-OBD-OBD2-ODB2-OBDII-DIAGNOSTIQUE-SCANNER-DIAG-AUTO-MULTIMARQUES-VAGCOM-/331780967430?hash=item4d3fafcc06:g:xCQAAOSwx-9WxNBp

I 've setup D2XX drivers currently available for FTDI devices here for windows 10 http://www.ftdichip.com/Drivers/D2XX.htm

Then I've connected my ODB adaptor but drivers where never detected.
So I used my drivers included with my ODB adaptor. In that case ODB adaptor is well setup on my computer but KWP2000 software don't recognize it.

Could you tell me if I bought the wrong adaptor USB-ODB or if my problem could be somewhere else ?

In advance thank you for your help.

Matej

I never got this to work on Windows 10, I borrowed an older Windows XP laptop and all connected up ok. I eventually picked up an old XP notebook for £15.00 on eBay and now use this.
 

spoutnik

New Member
Messages
3
Yes good idea :luvit: I'll test on another computer with XP I'll see if it's working better.

Thank you all ;)
 

ledlights

Junior Member
Messages
189
Hi,

Looking at your V A G adaptor, it's quite different from the one I use on my car. The important thing is that it must use the FTDI chipset that acts as a converter from USB to RS232, yours might have it but many don't (some use a generic Chinese adaptor) and if it doesn't use that chip the UNIDIAG software won't connect.

This is what mine looks like:

http://www.ebay.co.uk/itm/USB-Cable...467805?hash=item25a71cba9d:g:AdMAAOSwBahVRgew

But make sure, before you buy another, that it's not using a generic USB to COM port adaptor. Others on here have managed to get it work on later Windows laptops as long as they installed the driver before plugging the adaptor in. If you plugged it in first, Windows will search for driver software and (from my experience) won't find the right one. To recover from this, you would have to remove the relevant driver and start again.

Anyway, I hope this helps and good luck in fault finding.

Steve