When you click on links to various merchants on this site and make a purchase, this can result in this site earning a commission. Affiliate programs and affiliations include, but are not limited to, the eBay Partner Network.
PCM - Communications with the module have been lost
Hi all,
I have an iCarsoft 930 for diagnostics but it has never read the PCM properly and will only read in OBDII mode. This isn't useful because there are other codes in the PCM that I want to see.
I bought an old laptop and installed IDS/SSD v1.31 (the last version that doesn't need Topics account) and I bought a Mongoose cable from eBay which I believe is a clone. I have connected up and can read all modules in the car except for the PCM. Here I get an error "Communications with the module have been lost" message. As I said, every other module seems to be read aside from this one.
Does anyone have any suggestions as to why IDS will not read only from my PCM? The car starts and drives great and voltage on the battery is fine.
The car is an X202 S-Type R.
Cheers,
Rob
Last edited by MrDeBruce; Feb 2, 2025 at 12:02 PM.
Technically there is no PCM in the X202.
The X200 has a PCM (Powertrain Control Module) for both the engine and gearbox.(combined unit, no CAN bus)
The X202 has a CAN bus for separate ECM and TCM.
Lost communication info might be in ADMIN TSB 1-186 and a Jaguar TECH TIP document issued a few decades ago.
Read through the info for clues to your problem?
Last edited by motorcarman; Feb 2, 2025 at 01:43 PM.
At work, PCM is used specifically to refer to the Powertrain Control Module (i.e. Engine Control Module), and TCM for Transmission Control Module. This is distinct from ECM which is used to refer generically to an Electronic Control Module, of which there are many.
Thank you for your advice! Actually it was user error. The software instructs you when to turn on and off the vehicle ignition. I had just left the ignition on continuously and the PCM didn't seem to like this. I followed the on-screen prompts and it worked successfully.
I did also switch from using the Clone drivers for my cable to using the ones for a genuine cable, so this could also have been the cause although I am quite sure this is not a genuine cable.
Last edited by MrDeBruce; Feb 2, 2025 at 02:21 PM.