Reading error codes on an early 3200GT
- Thread starter ledlights
- Start date
hodroyd
Member
- Messages
- 14,150
You could try this site: http://www.obd-codes.com/
Grinzzz
New Member
- Messages
- 925
I find this one a pretty good site for getting the codes correct.
http://www.datsc.com/Technical-Resources.aspx
It does manufacturer specific codes as well as generic ones.
http://www.datsc.com/Technical-Resources.aspx
It does manufacturer specific codes as well as generic ones.
Last edited:
Ian H
Member
- Messages
- 167
Hi Guys
Brilliant set of info guys - many thanks
Have just got my cables delivered and will try an error code download later this week.
Is there any reason not to put a cigarette lighter adopter on the power leads for the plug rather than running a cable all the way back to the battery?
Not sure whether ignition needs to be on to power the *** lighter, but even if it was I guess this wouldn't cause an issue with the code reading?
Also not sure whether I shouldn't stick a fuse in the line or stop being a nerd and just get on with it?
Cheers
Ian
Brilliant set of info guys - many thanks
Have just got my cables delivered and will try an error code download later this week.
Is there any reason not to put a cigarette lighter adopter on the power leads for the plug rather than running a cable all the way back to the battery?
Not sure whether ignition needs to be on to power the *** lighter, but even if it was I guess this wouldn't cause an issue with the code reading?
Also not sure whether I shouldn't stick a fuse in the line or stop being a nerd and just get on with it?
Cheers
Ian
CatmanV2
Member
- Messages
- 48,789
Not sure what the draw on the cigarette lighter is, but I expect it'll be enough. It's on a 15A fuse after all (in the 4200) and I *really* doubt any ODB reader will be that high.
You need the ignition on to power the lighter, but then again, you also need the ignition on to fire up the ECU so it's all good
C
ledlights
Junior Member
- Messages
- 189
Hi Ian,
I've not tried it but it should work fine. Ignition needs to be on for power anyway. Only thing is that the Laptop shouldn't be powered from the mains (to avoid discrepancies in the earth) and you must power up the interface before you try to connect to the ecu or it won't work (obviously).
Also, don't forget to take a screen dump if you are planning on deleting stored codes, so you don't forget what you had....
Happy scanning!
Steve
I've not tried it but it should work fine. Ignition needs to be on for power anyway. Only thing is that the Laptop shouldn't be powered from the mains (to avoid discrepancies in the earth) and you must power up the interface before you try to connect to the ecu or it won't work (obviously).
Also, don't forget to take a screen dump if you are planning on deleting stored codes, so you don't forget what you had....
Happy scanning!
Steve
Ian H
Member
- Messages
- 167
one step forward, two sideways a lot of standing on my head and now a bit lost
Hi all,
While my 3200 was at the Indie getting its post purchase fettling, I have been getting my head around the code reading.
I have an X reg. (2000?) so assumed it would have the pre ODBD2 3 pin plug and associated diagnostics.
So I grabbed the two requisite cables off of Ebay and a adaptor from Halfrauds and soldered my fingers together making up a cig lighter power attachment.
Fab - this morning I went down to the car to check it was the right version and checking the label on the box (hopefully 'the' box not 'a' box) it had no ref to ODB2 on the label so great, must be the old 3pin set up.
However on searching around for the 3 pin plug it is nowhere to be found. What I did find was the large multi (16?) pin plug mounted to a small bracket and after head standing and cursing it would seem this may be connected to the older style plug which was lurking almost out of sight behind it.
Tried to take some picies but i-phone couldn't cope with lighting. Upgrade to IOS7 is great for flash light app but camera went grumpy and had to reset phone
So I guess two options; either it is a later interface or someone has beaten me to it and permanently installed a 16 pin plug adapter onto the 3 pin.
Either way I am now a bit lost on how best to progress?
Any help very gratefully received..
Ian
Hi all,
While my 3200 was at the Indie getting its post purchase fettling, I have been getting my head around the code reading.
I have an X reg. (2000?) so assumed it would have the pre ODBD2 3 pin plug and associated diagnostics.
So I grabbed the two requisite cables off of Ebay and a adaptor from Halfrauds and soldered my fingers together making up a cig lighter power attachment.
Fab - this morning I went down to the car to check it was the right version and checking the label on the box (hopefully 'the' box not 'a' box) it had no ref to ODB2 on the label so great, must be the old 3pin set up.
However on searching around for the 3 pin plug it is nowhere to be found. What I did find was the large multi (16?) pin plug mounted to a small bracket and after head standing and cursing it would seem this may be connected to the older style plug which was lurking almost out of sight behind it.
Tried to take some picies but i-phone couldn't cope with lighting. Upgrade to IOS7 is great for flash light app but camera went grumpy and had to reset phone
So I guess two options; either it is a later interface or someone has beaten me to it and permanently installed a 16 pin plug adapter onto the 3 pin.
Either way I am now a bit lost on how best to progress?
Any help very gratefully received..
Ian
ledlights
Junior Member
- Messages
- 189
Hi,
There were 2 ECUs used on these cars and 3 plug combinations, some of the late (early) cars had the early ECU but with the 16 pin plug. It sounds like your car has either been modified or is a crossover model. From your ECU it looks like you should have a KKL interface, so I would try to use the V A G interface straight onto it without the 3 pin ISO adapter and set up the interface as if it was an early car.
Out of interest, I could only see the ISO to 16 pin adapter and not the V A G interface. Did you buy that too?
Steve
There were 2 ECUs used on these cars and 3 plug combinations, some of the late (early) cars had the early ECU but with the 16 pin plug. It sounds like your car has either been modified or is a crossover model. From your ECU it looks like you should have a KKL interface, so I would try to use the V A G interface straight onto it without the 3 pin ISO adapter and set up the interface as if it was an early car.
Out of interest, I could only see the ISO to 16 pin adapter and not the V A G interface. Did you buy that too?
Steve
Ian H
Member
- Messages
- 167
Hi
Here is the best picture I managed to get of the input plug.
Steve, I am still awaiting delivery of the V A G interface.
I will pick the car up in the morning and as suggested just try a direct connect with the V A G interface, assuming the postie does his bit.
Many thanks
Ian
Here is the best picture I managed to get of the input plug.
Steve, I am still awaiting delivery of the V A G interface.
I will pick the car up in the morning and as suggested just try a direct connect with the V A G interface, assuming the postie does his bit.
Many thanks
Ian
Ian H
Member
- Messages
- 167
Hi Steve
Sorry this is bit terse – the reason will be clear shortly .
Just back from a week away so gave it a go this afternoon.
First problem - clear the virus from my Windows 7 laptop courtesy of the kids surfing while I was away.
Plugged in the new USB 16 pin converter and little red light came on – good start
Tried to replace the driver with the downloaded version but Windows said the one it was using (CH341S64.SYS from winchiphead.com) was the latest and wouldn’t change it. Wasn’t brave enough to delete the existing and force new driver but suspect I should have ?
Also have a mini disk, presumably with drivers, that came with the adaptor plug.
I managed to change the com port to Com Port 2 via the Properties General tab, but when I tried to change the other baud and latency under Properties Port tab it told me ‘I must have write privileges in the registry for this device’ . Presumably this is some user admin issue but spent a long time trying to get round it with no success?
Having got stuck, thought I would at least get the Unidiag analysis app up and running. However on unpacking zip there were numerous messages that the files could only be unzipped unencrypted ?
Having unzipped KWP2000-0-5-0-11 and KWP 71-0-5-09 to folders of same name in my user directory, I tried to run the UniDiagKWP 2000 which I found in the unpacked sub directory. But I just got another error message ‘ can’t start because FTD2XX.dll is missing’.
Just for a final laugh I thought I would plug it into the car anyway in case a miracle happened. It didn’t - the 16 pin plug fitted, but just the same error messages and I then proceeded to bash the drivers door on a set of ramps while messign around.
Having had way too much fun for 1 afternoon, I went and took my frustrations out on the kids and the dog, either of whom would probably have made more progress than me.
On spending 30 mins typing this all out the first time, in a hopefully half comprehansible format, upon trying to post the internet connection went down, the whole lot vanished, so I then had to type it all again arrhhhhhhhhh.
Anyway keen to persevere if you have the patience?
Many thanks
Ian
Sorry this is bit terse – the reason will be clear shortly .
Just back from a week away so gave it a go this afternoon.
First problem - clear the virus from my Windows 7 laptop courtesy of the kids surfing while I was away.
Plugged in the new USB 16 pin converter and little red light came on – good start
Tried to replace the driver with the downloaded version but Windows said the one it was using (CH341S64.SYS from winchiphead.com) was the latest and wouldn’t change it. Wasn’t brave enough to delete the existing and force new driver but suspect I should have ?
Also have a mini disk, presumably with drivers, that came with the adaptor plug.
I managed to change the com port to Com Port 2 via the Properties General tab, but when I tried to change the other baud and latency under Properties Port tab it told me ‘I must have write privileges in the registry for this device’ . Presumably this is some user admin issue but spent a long time trying to get round it with no success?
Having got stuck, thought I would at least get the Unidiag analysis app up and running. However on unpacking zip there were numerous messages that the files could only be unzipped unencrypted ?
Having unzipped KWP2000-0-5-0-11 and KWP 71-0-5-09 to folders of same name in my user directory, I tried to run the UniDiagKWP 2000 which I found in the unpacked sub directory. But I just got another error message ‘ can’t start because FTD2XX.dll is missing’.
Just for a final laugh I thought I would plug it into the car anyway in case a miracle happened. It didn’t - the 16 pin plug fitted, but just the same error messages and I then proceeded to bash the drivers door on a set of ramps while messign around.
Having had way too much fun for 1 afternoon, I went and took my frustrations out on the kids and the dog, either of whom would probably have made more progress than me.
On spending 30 mins typing this all out the first time, in a hopefully half comprehansible format, upon trying to post the internet connection went down, the whole lot vanished, so I then had to type it all again arrhhhhhhhhh.
Anyway keen to persevere if you have the patience?
Many thanks
Ian
Last edited:
Danny
Member
- Messages
- 443
Ian, considering the port that you have (I have the same) probably the most simple solution is to buy one of these.
Advantages:
- it is plug and play (no need to install anything)
- it is rather cheap
- it knows the error codes of various car manufacturers (incl. most Maserati codes)
- contrary to a laptop, it is a small and handy device which you can just leave in your car for the odd code that will pop-up during travelling
Advantages:
- it is plug and play (no need to install anything)
- it is rather cheap
- it knows the error codes of various car manufacturers (incl. most Maserati codes)
- contrary to a laptop, it is a small and handy device which you can just leave in your car for the odd code that will pop-up during travelling
ledlights
Junior Member
- Messages
- 189
Hi Danny,
The issue of which tester can be used boils down to whether the car is fitted with an IAW4CM or an IAW4EM ECU. The 4CM is not EOBD compliant but the 4EM is. If you want to connect to an early car you need to use a V A G interface because it communicates with KWP2000 rather than the EOBD protocol. From the photos, Ian has an early car fitted with a later communications plug so the EOBD interface wouldn't work on his car.
Regards,
Steve
The issue of which tester can be used boils down to whether the car is fitted with an IAW4CM or an IAW4EM ECU. The 4CM is not EOBD compliant but the 4EM is. If you want to connect to an early car you need to use a V A G interface because it communicates with KWP2000 rather than the EOBD protocol. From the photos, Ian has an early car fitted with a later communications plug so the EOBD interface wouldn't work on his car.
Regards,
Steve