![]() Disconnected the brand new USB cable from interface, heard the disconnect chime, reconnected cable, heard the connect chime. ? Re-downloaded the latest full version of VCM Suite (4.4.2), and re-installed. I did not try disconnecting and reconnecting the USB cable at this time. All I can do is click the Close button here. Clicking the Retry button does not alter the progress bar. ? When connected to the internet and not the PCM (I can?t physically do both simultaneously), choosing the Resync interface option, the window only offers Retry & Close, and the progress bar only says Reading from interface. VCM Suite Product: VCM Scanner 4.3.603 Beta ? Installed beta 4.3.603, received same error ? Unable to detect the vehicles diagnostics protocol ? Operating System: Windows 10 (build 17763) ? Installed VCMSuite 3.6.26 (the latest 3.x build I have archived), seems to recognize interface and licenses, but still receive same error: Appeared to obtain the Application key and interface serial number but couldn?t validate cable licenses. ? I figured it wouldn?t work, but tried anyway to install and use build 2.24. ?ĝevice Manager: Confirmed that both channel icons are dimmed when the interface is not connected, and black when the interface is connected. ?ĝevice Manager: Confirmed the MPVI channel A & B devices are listed ?ĝownloaded and installed the latest MPVI drivers (2.08.28 at this time) (Right-click. ? Uninstalled MPVI device drivers, and chose to delete the driver files. Details are below if interested, I probably could have started with a later version of VCMSuite than what I did, but part of it was curiosity. Is there anything else I can do to rule out what's causing the software to not detect the PCM protocol? I just sent a ticket to Support, hoping to get quicker ideas here.Ĭliff Notes: At this time, I'm no longer getting the error and I'm able to scan the PCM. I'm trying to get hold of another local known good OBD2 cable to rule out the cable. Re-seated all cable connections multiple times, no change. I bought and tried a new USB cable, no change. I removed 4.4 and re-installed 4.0.12, no change. I disconnected my HPTuners OBD2 cable and connected my bluetooth OBD2 adapter, and my Android using Torque was able to scan the PCM fine. ![]() It seems slower to detect the interface also. After that, both Scanner and Editor cannot detect PCM protocol. ![]() Last night, I connected to scan the vehicle and VCMScanner froze during scanning with key on engine off. I scanned the PCM successfully yesterday morning on the way to work but didn't save the log. 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. That overwrote 4.0.12 and also seems to have uninstalled the beta. After vacuum leaks were fixed, I noticed that 4.4 was being advertised as an upgrade in the application, so I installed it. I had some vacuum leaks that caused me to go in circles, so I installed the beta version also. 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.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |