3200GT DTCs

Kevgta

Junior Member
Messages
93
Morning, does anyone have any tip on how to clean brake pedal switch? And where can I find it?
Is it the same as brake light switch confused.
Got error 1665
Cheers
 

Chris Eggleton

Junior Member
Messages
65
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.
[/QUOTE
 

Chris Eggleton

Junior Member
Messages
65
Good evening gentlemen,
I have read this thread with some interest, but have a more fundamental issue than the DTC. My problem is the scanner won't connect with the car to get to the DTC step. Any advice on connectivity issues, and possible solutions to fault find this issue greatly appreciated.

Background -
I recently drove from Canberra to Newcastle circa 450kms and had an intermittent temperature as per sdlangford 3200GT Temperature Gauge Issues (this forum) with exactly the same symptoms. During this drive the CEL came on upon start but was easily cleared by a ignition key off/on.
However, after several weeks short trip normal driving, where the temperature problem didn't recur, I now have a constant CEL, and can't communicate with the two scanners I have, which are as follows:
a. CAN OBD2 Code Reader Viecar VC309; and
b. Vident iLink 400 AU Scan tool;
c. Incidentally, I have previously used an old generic 16 pin scanner (in Darwin, NT, Australia) and was able to communicate and clear the saved DTC in the ECU: various spurious ones based on a faulty oil pressure sensor (no surprises there), and some intermittent coils which needed replacing. I used a manufacturer agnostic selection on this scanner which seemed to work fine.

Fault finding -
I have only tried the two scanners I have available, and am unsure if they are compatible with the 3200GT (2000);
I was unaware the car had individual ECU connections so have only used the 16 pin plug connection;
I have done a power off master clear of the car using a battery disconnect, brake pedal depress (discharge capacitance in system) methodology;
I have checked the DLC for loose pins/connections using a multimeter - OK;
I have checked the power/earth pins on the DLC for voltage, and earth connectivity back to the battery, and chassis. They appear to be iaw the diagram above- OK;
I have checked battery voltage - OK;
Car starts perfectly, but of course with the CEL on is in reduced power mode.

Again any thoughts, tips, experiences very much appreciated.
Regards,
Chris
 

davy83

Member
Messages
2,809
It communicates on the KWP2000 protocol and so if your readers don't support this it won't work. There are a whole bunch of different ODBII protocols, its a pest. I have an Autel Maxiscan MS309 which talks to it no problem, and it was pretty cheap too
 

Chris Eggleton

Junior Member
Messages
65
It communicates on the KWP2000 protocol and so if your readers don't support this it won't work. There are a whole bunch of different ODBII protocols, its a pest. I have an Autel Maxiscan MS309 which talks to it no problem, and it was pretty cheap too
Thanks davy83, the two scanners I have both support the KWP2000 protocol, in fact during the search for the car in just OBD2 mode the scanner scans all the different protocols and sits there for a while thinking about it when it gets to the KWP2000, then moves onto several others scanning through them quite quickly, and then comes up with the 'Can't Communicate' alert: both scanners. Interestingly the Vident Scanner is purpose built for the family of Maserati and Fiats stretching from the 3200GT to the Gran Sport
Reading exstensively in Google Maserati Forums (fora?) I think I have a hard fault/earth/short in a lambda sensor which is creating a problem for the ECU. I have the Maserati 3200GT manual, and I'm going to try the Scanner repeatedly after isolating each sensor in turn until I find the faulty one. Apparently the brake sensor is a common fault, but I also know my Temperature sensor, and Oil pressure sensor are suspect so I'm going to give them a try as well.
 

davy83

Member
Messages
2,809
Thanks davy83, the two scanners I have both support the KWP2000 protocol, in fact during the search for the car in just OBD2 mode the scanner scans all the different protocols and sits there for a while thinking about it when it gets to the KWP2000, then moves onto several others scanning through them quite quickly, and then comes up with the 'Can't Communicate' alert: both scanners. Interestingly the Vident Scanner is purpose built for the family of Maserati and Fiats stretching from the 3200GT to the Gran Sport
Reading exstensively in Google Maserati Forums (fora?) I think I have a hard fault/earth/short in a lambda sensor which is creating a problem for the ECU. I have the Maserati 3200GT manual, and I'm going to try the Scanner repeatedly after isolating each sensor in turn until I find the faulty one. Apparently the brake sensor is a common fault, but I also know my Temperature sensor, and Oil pressure sensor are suspect so I'm going to give them a try as well.
UUURGH - The ECU should communicate on the ODBII system regardless of the sensor errors it is experiencing I would have thought? I suspect you have a problem there causing this, and not a faulty reader either. I wonder if there is any hardware between the ODBII port and the ECU? you know a bridge unit of some sort, or does the ECU sit on the CAN bus structure directly? If the ECU is direct to the ODB port then you only have wiring faults or the ECU itself is faulty. anything remotely dodgy been connected to the ODB port?
 

Chris Eggleton

Junior Member
Messages
65
Good evening Gentlemen,
Many thanks the support and dialogue.
Swedish Paul - great idea. I checked the fuse for the diagnostic link connector (5 amp) unfortunately it was intact. Just in case my owner's handbook and the car were different, I also checked all the fuses (5, 7.5, 10 Amp) in the area of the DLC fuse - all good. I didn't check the 20, and 50 Amp fuses as I figured they were a complete overkill for the DLC. Having said that I did ensure that the bigger fuses were consistent with the legend in the owner's amnual, they protected things like the starter motor, A/C etc. The fuses are under a plate in the passenger side foot well, and difficult to access (see picture).
davy83 - That's a good point regards the comunication and the state of the sensors, what I was checking for was a short to chassis which may load down the logic level to an ambiguous level that the ECU can't determine if it is Lo or Hi: still that shouldn't affect connectivity?
I am trawling through the electrical diagrams to see if there is any hardware between the DLC and the main ECU (if I can ever find it). I think I may have an old version of the technical manual, because there is no reference to the DLC 16 pin connector, just a swag of ECU connecting all sorts of metrics to somewhere. Once I have found the DLC I can work back to the other ECU or even the main ECU and start fault finding.
I agree your assessment of the problem if the ECU is a direct connection, it will start to look a lot like a defective ECU (really looking forward to shelling out for a new one of those). Nothing dodgy connected to the DLC at all. I have repaired the drivers window lift mechanism, changed a fuel filter, changed the oil and filter, recently but I can't imagine they had any effect on the ECU.
The latest major fault , as I mentioned above, was the temperature sensor going rogue which really upset the car big time. I was driving interstate at vast speed when the temp guage dropped to zero, which made the car do all sorts of wierd stuff. Revs dropped off/car was surging, and when I got into traffic around Sydney, I barely kept it running by using nuetral and keeping the revs up. Back on the freeway it didn't have as much effect as the gauge worked most of the time and as I was doing 120kph the momentum kept me going through the fault condition. Once I was back in Newcastle, the fault didn't reappear, although I am changing out the temp sensor first opportunity I get. The big issue is getting the car running again tout suite, so I need the CEL out, and the DTC cleared soonest.
Thanks again for your help/ideas. Much appreciated.
Chris
 

Attachments

  • Resized_20210621_162131.jpeg
    Resized_20210621_162131.jpeg
    44.3 KB · Views: 18

buzzjunkies

New Member
Messages
4
Today i was try connect 3200GT and read DTC from engine ECU - Unidiag KW2000 works fine and everything is ok.
Then i tried KW71 to connect with airbag but with no luck.

Is anybody here who did it? Or somebody could confirm my assumptions?

Firstly: i have no adapter for Fiat, just KKL cable for dieselgate brand. For engine ECU i just make correct pins: K,L, bridged chasis and signal ground and +12V from battery. It's work correctly. Now my questions:
Has airbag diagnostic plug a yellow insulation with only two pins and one free slot? I found this plug close to transmission selector and tunnel with the second black plug, for AC i guess, but i'm not sure about what pins i have to connect to airbag plug. Diagram for 3 pin Fiat diagnostic plug show me there is only L-line and ground but i'm not sure about it - tommorow i would check what kind of diagnostic line is there by oscilloscope.
 

Chris Eggleton

Junior Member
Messages
65
Good evening Gentlemen,
Many thanks the support and dialogue.
Swedish Paul - great idea. I checked the fuse for the diagnostic link connector (5 amp) unfortunately it was intact. Just in case my owner's handbook and the car were different, I also checked all the fuses (5, 7.5, 10 Amp) in the area of the DLC fuse - all good. I didn't check the 20, and 50 Amp fuses as I figured they were a complete overkill for the DLC. Having said that I did ensure that the bigger fuses were consistent with the legend in the owner's amnual, they protected things like the starter motor, A/C etc. The fuses are under a plate in the passenger side foot well, and difficult to access (see picture).
davy83 - That's a good point regards the comunication and the state of the sensors, what I was checking for was a short to chassis which may load down the logic level to an ambiguous level that the ECU can't determine if it is Lo or Hi: still that shouldn't affect connectivity?
I am trawling through the electrical diagrams to see if there is any hardware between the DLC and the main ECU (if I can ever find it). I think I may have an old version of the technical manual, because there is no reference to the DLC 16 pin connector, just a swag of ECU connecting all sorts of metrics to somewhere. Once I have found the DLC I can work back to the other ECU or even the main ECU and start fault finding.
I agree your assessment of the problem if the ECU is a direct connection, it will start to look a lot like a defective ECU (really looking forward to shelling out for a new one of those). Nothing dodgy connected to the DLC at all. I have repaired the drivers window lift mechanism, changed a fuel filter, changed the oil and filter, recently but I can't imagine they had any effect on the ECU.
The latest major fault , as I mentioned above, was the temperature sensor going rogue which really upset the car big time. I was driving interstate at vast speed when the temp guage dropped to zero, which made the car do all sorts of wierd stuff. Revs dropped off/car was surging, and when I got into traffic around Sydney, I barely kept it running by using nuetral and keeping the revs up. Back on the freeway it didn't have as much effect as the gauge worked most of the time and as I was doing 120kph the momentum kept me going through the fault condition. Once I was back in Newcastle, the fault didn't reappear, although I am changing out the temp sensor first opportunity I get. The big issue is getting the car running again tout suite, so I need the CEL out, and the DTC cleared soonest.
Thanks again for your help/ideas. Much appreciated.
Chris
Situation Report: Car CEL still on, however, the Scanner that does communicate with this variant of the 3200GT is the G scan 2 (picture supplied) in Demo Mode as there is no Maserati on the venicle types. I remain optimistic that we can clear the CEL with a scanner that actually can 'talk'to the ECU, and identify the underlying issues. Stay posted! Chris
 

Attachments

  • FullSizeR (002).jpg
    FullSizeR (002).jpg
    104.7 KB · Views: 12

buzzjunkies

New Member
Messages
4
Hello there again.

After many attempts I was able to connect with ABS - I will post a manual how to connect, step by step, with ECU and ABS. But still i've got a problem with SRS and i suppose the airbag ecu is dead.

In SRS diagnostic connector is there only two pins - middle (ground) and the second one - diagnostic line. My SRS module doesn't send a logical 0 (~12V) this line - still have got 0V. So there are two ways - airbag ecu is dead or airbag ecu still trying to "talk" by this line, without success.

Could anyone measure electrical voltage at the diagnostic pin for me? The SRS plug is on passenger side close to transmission tunel and got a yellow insulation.
 

MRichards

Member
Messages
278
I had an unusual problem with a CEL. The CEL was checked by a mechanic with a WiFi diagnostic tool & indicated worn clutch & faulty throttle body. Both these faults were fixed,however,the CEL was still there & causing limp mode. A power-down removed the CEL,but it reappeared on the next start. After spending about three weeks checking everything possible with a Leonardo diagnostic tool to no avail we finally checked under the dash where there were two Bluetooth modules. Disconnection of the modules fixed the problem ! I can only conclude that the error codes were received by the in car Bluetooth modules & stored from the mechanic's WiFi diagnostic tool.
I'll leave it to the experts to figure out how this can happen.
 

buzzjunkies

New Member
Messages
4
I had an unusual problem with a CEL. The CEL was checked by a mechanic with a WiFi diagnostic tool & indicated worn clutch & faulty throttle body. Both these faults were fixed,however,the CEL was still there & causing limp mode. A power-down removed the CEL,but it reappeared on the next start. After spending about three weeks checking everything possible with a Leonardo diagnostic tool to no avail we finally checked under the dash where there were two Bluetooth modules. Disconnection of the modules fixed the problem ! I can only conclude that the error codes were received by the in car Bluetooth modules & stored from the mechanic's WiFi diagnostic tool.
I'll leave it to the experts to figure out how this can happen.


If u want to be sure You should check wires from this modules - where was plugged in and what are did in the car. It's a little bit of chance it was connected to throttle body wires\ECU K-line inside of car. There is no other reason imo - this car haven't got CAN-bus line so it's impossible to make noise between control modules or send fake DTCs.
 

Chris Eggleton

Junior Member
Messages
65
I had an unusual problem with a CEL. The CEL was checked by a mechanic with a WiFi diagnostic tool & indicated worn clutch & faulty throttle body. Both these faults were fixed,however,the CEL was still there & causing limp mode. A power-down removed the CEL,but it reappeared on the next start. After spending about three weeks checking everything possible with a Leonardo diagnostic tool to no avail we finally checked under the dash where there were two Bluetooth modules. Disconnection of the modules fixed the problem ! I can only conclude that the error codes were received by the in car Bluetooth modules & stored from the mechanic's WiFi diagnostic tool.
I'll leave it to the experts to figure out how this can happen.
Good afternoon MRichards, could you identify the year of manufacture of your Maserati please. Many thanks,
Chris
 

spkennyuk

Member
Messages
5,930
Any part numbers , markings or perhaps you have a picture of the modules. Im assuming its not a 3200 you have but which car do you have ?
 

MRichards

Member
Messages
278
Chris and "spkenyuk" Maserati 3200GT August,year 2000
Has SD2 electronics.
The modules are: Nokia Type HF-5 (OW3HF-5) The module which caused the trouble is unbranded,dated 9/06 with a serial #6101086. It appears to be a signal receiver since it has a short wire aerial. Has a power supply & a twenty-pin outlet. Trust this helps.