HPT interface stopped connecting to PCM
Thread Starter
Joined: Jan 2002
Posts: 4,069
Likes: 74
From: Casselberry FL
HPT interface stopped connecting to PCM New motor as of late last week, began tuning it with the existing 4.0.12 that I had installed along with the MPVI Pro. I had some vacuum leaks that caused me to go in circles, so I installed the beta version also. After vacuum leaks were fixed, I noticed that 4.4 was being advertised as an upgrade in the application, so I installed it. That overwrote 4.0.12 and also seems to have uninstalled the beta. As soon as I connected the interface to the laptop with the software running, I recall it automatically upgrading the interface without being given an opportunity to decline and allow me to continue to use older versions of the software.
So I used 4.4 for a few days. I scanned the PCM successfully yesterday morning on the way to work but didn't save the log. Last night, I connected to scan the vehicle and VCMScanner froze during scanning with key on engine off. I had to force close the application. After that, both Scanner and Editor cannot detect PCM protocol. It seems slower to detect the interface also. I disconnected my HPTuners OBD2 cable and connected my bluetooth OBD2 adapter, and my Android using Torque was able to scan the PCM fine.
I removed 4.4 and re-installed 4.0.12, no change. I bought and tried a new USB cable, no change. Re-seated all cable connections, no change. I'm trying to get hold of another local known good OBD2 cable to rule out the cable. Is there anything else I can do to rule out what's causing the software to not detect the PCM protocol?
So I used 4.4 for a few days. I scanned the PCM successfully yesterday morning on the way to work but didn't save the log. Last night, I connected to scan the vehicle and VCMScanner froze during scanning with key on engine off. I had to force close the application. After that, both Scanner and Editor cannot detect PCM protocol. It seems slower to detect the interface also. I disconnected my HPTuners OBD2 cable and connected my bluetooth OBD2 adapter, and my Android using Torque was able to scan the PCM fine.
I removed 4.4 and re-installed 4.0.12, no change. I bought and tried a new USB cable, no change. Re-seated all cable connections, no change. I'm trying to get hold of another local known good OBD2 cable to rule out the cable. Is there anything else I can do to rule out what's causing the software to not detect the PCM protocol?
Thread Starter
Joined: Jan 2002
Posts: 4,069
Likes: 74
From: Casselberry FL
Seems to be fixed for now, don't want to re-type it all though. The steps I took are in the link below.
https://forum.hptuners.com/showthrea...653#post569653
https://forum.hptuners.com/showthrea...653#post569653
