NickP
Member
- Messages
- 1,623
Voicey is your man
Voicey?!
Voicey is your man
I've connected using std ebay connectors with no modification
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
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 SportIt 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
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?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.
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! ChrisGood 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
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,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.