Most of the time when a shop calls me in for a diagnostic job, there’s a pretty cut and dry fix. Every once in a while, a job comes along that becomes a challenge and all too often makes me wonder why I do what I do. But that’s a story for another time.
In this case, the vehicle in question is a 2001 Lincoln Town Car. The complaint is that the car will not start. The shop stated that there wasn’t any communication with the Powertrain Control Module (PCM). One of the first things I do when it comes to a control module that isn’t communicating is to test and see if there are any other modules that aren't communicating as well. I performed a network test, which is kind of like a roll call. I wanted to find out if all the modules were reporting for duty.
After performing the test with the scan tool, all the modules reported for duty except the PCM. I did visually check to see if the PCM was there (don’t laugh, I’ve seen stranger things) and that the connector was plugged in, which it was. The next step is to see if the PCM is getting the proper powers and grounds to make it functional. Remember, when working on a network problem it is essential that a good wiring schematic is available. When looking at the schematic of the PCM, I looked for the power feeds going to it. Using a wire schematic feature I highlighted the two power circuits in question. The PCM is located beneath the brake booster, by the bottom of the firewall, which is not an easy place to access.
The next step is to check the ground circuits. These circuits are Terminals 3 and 25 along with Terminals 77 and 103. All four terminals checked out fine and passed the headlight test. So, I have good power and grounds at the PCM. It’s time to check to see if the network circuits are shorted or open. This particular vehicle uses a Standard Corporate Protocol (SCP) network. Every module on this network communicates with each other except the Restraint Control Module (RCM). The RCM is on another network called the ISO 9141 or International Standards Organization network. Both networks are read at the Diagnostic Link Connector (DLC) by the scan tool.
A couple of days later, I come back to program the PCM. I hook up my scan tool and guess what? No communication with the PCM. This is every mobile techs nightmare. I misdiagnosed this vehicle. I promptly rechecked my previous diagnosis and came up with the exact same results. This PCM has got to be faulty. By all circumstances this PCM should be alive. Now what? I plug the PCM connector back into the PCM and start to reread my wiring schematics to see if I am missing anything. I also did a quick search on Identifix and iATN to see if anybody else has had the good fortune to come across the same problem as I have. No luck there either.
I went back to the Idle Actuator motor and plugged it back in. The noise was back and my PCM communication was gone. I did this a couple of times to make sure I was seeing things correctly. Sure as ever, this IAC motor was pulling down communications that caused the problem with the PCM. I went back and reviewed my schematic to see how the IAC plays a part in the communication network of the PCM. I noticed that the IAC motor shares the same power as the PCM on Terminal 71. I checked the circuit again at the PCM and at the IAC motor. Both connectors had 12 volts. Now I realized my mistake. Remember, I said that I disconnected the PCM connector to check my voltage at my two power terminals because access to the PCM connector was in a hard to reach area? In doing that I took all loads off the circuit. So, with the PCM harness pulled out of the way and having access to the old PCM, I plugged in the harness and checked for my powers on circuit 55 and 71. Terminal 55 had 12 volts but terminal 71 only had 7 volts. The IAC motor was shorting internally and robbing (that is, causing a voltage drop) the PCM of the correct voltage to properly power it up.
Replacing the IAC motor and installing the original PCM fixed this car. Luckily the shop was able to return the PCM because it wasn’t programmed. Having these painful learning experiences can sometimes help make a good tech a better tech.
Subscribe to Motor Age and receive articles like this every month…absolutely free. Click here