3200GT DTCs

Biturbista

New Member
Messages
20
@Ledlights: In order to connect to your engine ECU, did you use one of Sander's modified cables or did you use a standard one bought on eBay?

By the way, is it correct that all ECU's in the pre-OBD 3200GT's each have their own diagnostics connector and that only two wires run up to each of these 3 pin connectors?

So far I conclude that:
- the diagnostics connector for the engine ECU is located on the right hand side of the footwell on the right side (ie. driver's side on UK spec cars) of the car
- the diagnostics connectors for the ABS/ASR ECU and airbag ECU are located on the left hand side of the footwell on the right side of the car, near the transmission tunnel
- the diagnostics connector for the suspension ECU is located in the boot near the battery compartment

Can anybody confirm that the above is correct?
 
Last edited:

dunnah01

Member
Messages
648
@Ledlights: In order to connect to your engine ECU, did you use one of Sander's modified cables or did you use a standard one bought on eBay?

By the way, is it correct that all ECU's in the pre-OBD 3200GT's each have their own diagnostics connector and that only two wires run up to each of these 3 pin connectors?

So far I conclude that:
- the diagnostics connector for the engine ECU is located on the right hand side of the footwell on the right side (ie. driver's side on UK spec cars) of the car
- the diagnostics connectors for the ABS/ASR ECU and airbag ECU are located on the left hand side of the footwell on the right side of the car, near the transmission tunnel
- the diagnostics connector for the suspension ECU is located in the boot near the battery compartment

I've connected using std ebay connectors with no modification
suspensionecuconnector.jpg

ECU's all over the car on early 3200's - each has a 3-pin connector with 3 wires to at least the engine and ABS ECU's not sure about the others though.
Locations for ECU's sounds right for a RHD car although suspension ECU is on nearside of boot with battery on offside.
 

Biturbista

New Member
Messages
20
@dunnah01: Thanks a lot for the excellent diagram! It matches exactly with what I have measured on the ODB-II to 3 pin cable and what I found within the blue USB interface that I have.

To which ECU's have you been able to connect? And what baud rate did you use for both the interface and the software to connect to these ECU's? Today I only managed to connect to the airbag ECU and managed to clear the error codes I had. Maybe tomorrow I will try the other ECU's, but rather than dealing with an application that only provides access to some standard stuff I would like to 'talk' directly to the ECU's through a terminal application.
 

rotorheadcase

Junior Member
Messages
415
You can connect to the Engine ECU and read/clear error codes. You are correct that it is on the RHS of the driver's footwell. There are several 3 pin connectors and the one you're looking for has a rubber shroud around the wires leading up to the connector. The 5 baud slow init works.

Regards,

Neil
 

dunnah01

Member
Messages
648
Biturbista

I've only tried the engine ECU and connected to that no problems - I do it the same way as Ledlights describes in his excellent How To Guide using the Unidiag software. The trickiest bit is finding the correct COM port but using Windows Device Manager and some trial and error I get there eventually. As the guide, you also need to set the software to 5 baud rate to get handshake.

I read and cleared several codes yesterday from various tinkerings with knock sensors and other bits. I need a decent run out now to see if any reappear.

I'll be trying the ABS/ASR and Airbag ECU's soon now that I know it's possible to connect.

I did try the suspension ECU without any luck - then again, even an SD2 tester couldn't speak to that so there may be deeper issues there.
 

Biturbista

New Member
Messages
20
@dunnah01: I am curious what you find when you connect to the airbag ECU. This weekend I had a go at this ECU but for some reason it does not allow me to read bytes from its memory, despite the fact that it confirms successful receipt of the command (after a while it returns a message indicating I am requesting something that is not allowed). The communication back and forth does work correctly however.

As far as the engine ECU is concerned, I can connect but sometimes I receive garbage during the session. It does return error codes when asked for them, but I am reluctant to experiment more as long as the communication is not 100% stable. So my priority here is to figure out how to stabilize the communication. I briefly tried connecting to the ECU of the airconditioning / climate control, but was not successful at all. It seems this ECU is using a slightly different protocol than the other ECUs...

The main thing I wish I had is an application that allows direct entry of the commands required by the various protocols. This would allow me to fully interrogate all ECUs as currently all software I have is too restrictive. The functionality is mostly limited to reading & clearing error codes, reading memory locations and reading values from A/D converters. For the interfaces that are based on the ELM-32x range of ICs this is widely available, but to my knowledge these interfaces do not work on the early 3200GTs (the engine ECU might be the only exception, I will try this sometime soon).
 
Last edited:

javier

New Member
Messages
33
I tried an old ELM327 (old firmware version) with no success... perhaps it does not do the 5-baud init, but I must confess that I did not tried too hard :) The ABS unit is a TRW, I think that common with other Fiat/Alfas, so it should be feasible to communicate with it, although I've not tried
 

Biturbista

New Member
Messages
20
@javier: To my knowledge the ABS/ASR ECU and airbag ECU's do not work with the ELM32x series. Today I received the latest ELM327 based interface from Gendan. I will have a try with it as it does support the slow init mentioned by you. The slow init was only introduced in version 1.4 (which is the current version) of the ELM327, however I still have my doubts whether it will support the protocols used by the ABS/ASR ECU and the airbag ECU. The engine ECU might be a different matter as it uses a different protocol.

If you want to be able to talk to the ABS/ASR ECU and airbag ECU, get yourself a cheap blue ***-COM (=V*A*G-COM) interface from eBay. It should only cost you 10-15 Euro...
 
Last edited:

saintetienne

Junior Member
Messages
242
I have been using kkl lead with unidiag for while now but have was not aware of the possibility to connect to abs/asr ecu - has anyone done this successfully yet ?
 

ledlights

Junior Member
Messages
189
I haven't tried it but I think most of the Fiats and Alfas have to use KWP71 protocol for this. Has anyone else had a go?
 

saintetienne

Junior Member
Messages
242
I did try a while ago with kwp71 with no success , hoping someone else had mastered it , from memory think you need to change various settings
 

ledlights

Junior Member
Messages
189
If someone will let me know what the relevant ECUs are I'll ask on the Unidiag forum.

Regards,

Steve
 

rotorheadcase

Junior Member
Messages
415
Hey guys,

I've been getting a CEL for the last couple of weeks and the error codes that show up on KWP2000 indicate an O2 sensor but two others as well that show up with a hex code and "item not found in list". The two hex codes are 0x1171 and 0x1665. Is anyone able to shed any light or have some of the proprietary hex codes and their explanation?

Thanks,

Neil
 

Biturbista

New Member
Messages
20
The two hex codes are 0x1171 and 0x1665. Is anyone able to shed any light or have some of the proprietary hex codes and their explanation?

@rotorheadcase: 0x1665 should be the brake pedal switch. If I am not mistaken the switch contains two circuits which work in the opposite way (eg. one is open if the pedal is depressed, the other one if it is pressed) . As far as 0x1171 is concerned, I am unable to help at this moment.