Reading error codes on an early 3200GT

[alfatwo]

Sounds like a nightmare guys,I feel for you... glad I bought into Maserati's later 2001 EOBDII version

Dave

 

[Contigo]

Can someone help me with this please? I already have a OBD VAGcom cable and know it works as I used it on the Audi and mates VW. I ordered the 3 pin Lancia/FIAT cable and made a longer 12 v croc clip. I downloaded the drivers and installed as per this thread and it says they are indeed installed. I then connected as in this thread including the 12v cable and the blue LED is lit on once it is connected to the 3 pin connector under the drivers column. I launch the UniDiag app and it does not show me a COM port which I have defined for the USB serial cable but dispays a ex code like 0x00000052. Any idea why I can't get any comms to the car?

I tried changing com port numbers in device manager but i wonder if the VAGcom software is causing a conflict.

 

[ledlights]

I've not come across this problem myself. The only things I can think of are:

Are you using the FTDI drivers? If not, remove the driver that Windows has used and download the relevant one from their website. The address is shown in this thread about 4 or 5 posts back.

Is the com port within Unidiag's range? From memory, it has to be less than com 8 (it's in the manual).

One question, do you have the com port drop down box as per the photos on the first post?

Steve

 

[Contigo]

Yes there is a drop down box but it doesn't have the COM port number written in it. It say 0x00000052.

I tried installing it on a different laptop and it does the same thing.

I plugged the usb *** cable into a clean laptop. it detects the USB<Serial> device but won't allow me to select a driver like detailed in the document for installing FDTI. Do I need to have an FDTI cable? OR will any VAGCOm ebay blue cable do?

 

[Contigo]

Here is the screenshot from unidiag.

 

[Contigo]

Looking at pic in first post I am connecting to a black cable with yellow and red rather than grey! Hmmmmmm

 

[ledlights]

Okay, you should install the ftdi driver before plugging the interface in. Once Windows does the auto-detect it's too late. I think you need to remove the existing driver and start again using the correct one but I'm using an old laptop so I can't suggest how you might do that. It's certainly possible on my old Vista machine but the detail on how to do it on yours will be different. The blue interface should work fine, the ftdi chip is built into all of them. Here are the installation guides for the ftdi driver:

http://www.ftdichip.com/Support/Documents/InstallGuides.htm

On the plug issue, definitely use the grey plug. If your car is right hand drive it is behind the triangular piece of carpet on the right hand side of the pedals in the footwell.

Hope this helps,

Steve

 

[Contigo]

Thanks mate, have reinstalled it on a clean computer and it appears as per the docs on com3. I will make sure I locate the grey connector as you mention and then let you know!

 

[Contigo]

This is after clearing a good few codes stored which I will post later. First suspicions were Throttle Body but not too sure now. Removed TB and cleaned it up and now those have gone.

Anyone any idea what boos sensor this refers to?

 

[ledlights]

I had the manifold absolute pressure error when my TB was playing up, if it helps.

 

[Contigo]

Cheers Ledlights. I finally got it working once I connected it to the grey connector

So this could still point to TB issue then it seems.

Interesting.

 

[Contigo]

Thaks ledlights. It could well be TB issue and I am tempted to get a contactless on immediately anyway!

Here are the DTC's prior to clearing them.

 

[Contigo]

So I replaced the RPM sensor and also linked the two wires on the PP. Car ran really sweet, full boost etc for a good hour and then I hit a slight bump in the road and Check Engline light came on and power was cut. Will run a new scan on it but would you say it points to TB now?

 

[Contigo]

Scanned after the Check Engine.

 

[ledlights]

As I said, I had an absolute pressure code when mine was playing up, however, you might have another problem...

 

[Ian H]

Eureka !!!!

Yippeee
After weeks of head scratching and numerous dumb questions to Steve I have finally got it all working.

Key takeaways:

1 I seems to have a car with the old ECU but new style 16 pin plug installed - a cross over hybrid.

2 Don't buy the cheapest USB to 16 pin converter plug you can find on EBAY - it will probably have the wrong chipset and not work. The system is set up to work with the FTID chipset - many of the cheaper plugs have a Chinese chipset http://wch-ic.com/product/usb/ch340.asp
When using these cable even with the drivers correctly installed the drivers will not be used since they do not recognize this different chipset.
I got my (third!) cable direct from Sander who wrote the Unidiag software and is super helpful. This plug even has a dip switch so you can start to explore the airbag and ABS but that's way too much fun for me right now. Its only EU33 and would have saved me 3 weeks of messing around !!!!!!

3 FTID were also super helpful in debugging someone else's chipset. They provided a great tool to check the characteristics of any connected USB devices http://www.ftdichip.com/Support/Utilities/usbview.zip and a great guide to get things reset and reinstalled if you get into a complete tailspin. ( to continue inept IT trend can't get doc to attach !!)


4 Turn the ignition on before you connect the laptop and with the latest software version it automatically select the correct definition file to use.



So what did I finally discover - well 3 error messages

P0110 Intake Air Temperature Circuit Malfunction -fault present
0x1172 item not found in list - fault this cycle
P0500 Vehicle speed sensor malfunction - test inhibited

Anyone seen these before / know what 0X1172 is / in which system the vehicle speed sensor resides?

Do you take these as issues to fix or clear them off the system and see if they recur on the basis that it may have just been a bad day when they appeared?

I assume hitting the clear DTC's button on the Diagnose tab will actually wipe these errors off the ECU and re instate the test cycles?

Delighted to have such a great tool - just need to decode the comms now.

Many thanks once again to Steve for having the software made available and fielding all the dumb questions

Ian

PS
The lovely 3 pin to 16 pin converter I made up with the *** lighter power plug is now not needed so available to a good home ......

 

[Ian H]

ah bit worrying when you start answering your own posts, but quick goggle of 0X1172 took me straight back to this post with suggestion of idle compensation error related to the good old lambda sensors.

 

[hodroyd]

Ian,
Very well done and 10 out of 10 for perseverance. I would clear the faults after taking note of the codes and then run again and see what comes up..!!
Cheers
R

 

[ledlights]

Hi Ian,

Sounds like you've got a lambda just starting to fail, a temperature sensor problem (I think this is the one adjacent to the TB and I don't know where the speed sensor is!

Glad you've got it working.

Steve

 

[Bart3200GT]

Flipping great