Results 1 to 4 of 4

Thread: Interface stopped connecting to PCM

  1. #1
    Advanced Tuner
    Join Date
    Oct 2004
    Location
    Orlando FL
    Posts
    709

    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 multiple times, 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? I just sent a ticket to Support, hoping to get quicker ideas here.
    Last edited by JimMueller; 2 Weeks Ago at 12:58 PM.
    1998 NBM Camaro Z28
    LS3 motor
    Mod list

  2. #2
    Advanced Tuner
    Join Date
    Oct 2004
    Location
    Orlando FL
    Posts
    709
    Cliff Notes: At this time, I'm no longer getting the error and I'm able to scan the PCM. 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. YMMV.

    ? Uninstalled all versions of VCM Suite
    ? Uninstalled MPVI device drivers, and chose to delete the driver files. I did not note the driver version.
    ? Downloaded and installed the latest MPVI drivers (2.08.28 at this time) (Right-click .inf file, install)
    ? Device Manager: Confirmed the MPVI channel A & B devices are listed
    ? Device Manager: Confirmed that both channel icons are dimmed when the interface is not connected, and black when the interface is connected.
    ? I figured it wouldn?t work, but tried anyway to install and use build 2.24. Appeared to obtain the Application key and interface serial number but couldn?t validate cable licenses.
    o Operating System: Win32NT 6.2.9200.0
    o Microsoft .NET: 4.0.30319.42000
    o CPU: Intel(R) Core(TM) i5-6300U CPU @ 2.40GHz
    o Available Memory: 7,336 MB
    o
    o VCM Suite Product: VCM Scanner 2.24.1170
    o VCM Suite Key: Snip
    o VCM Suite ID: Snip
    o
    o Get credit information failed. Error: F0
    o
    o Get license info failed. Error: F0
    o
    o Get licenses failed. Error: F0
    o
    o No Vehicle Licenses
    o
    o ID: Snip Date: 08/08/06
    o Hardware: 121 Firmware: 121
    ---snip---
    ? Uninstalled 2.24
    ? Installed VCMSuite 3.6.26 (the latest 3.x build I have archived), seems to recognize interface and licenses, but still receive same error:
    ? 5/4/2019 12:52:47 PM
    ? VCM Suite Product: VCM Scanner 3.6.26
    ?
    ? Operating System: Windows 10 (build 17763)
    ? Microsoft .NET: 4.0.30319.42000
    ? CPU: Intel(R) Core(TM) i5-6300U CPU @ 2.40GHz
    ? Available Memory: 7,191 MB
    ?
    ?
    ? Device ID: Snip
    ? Application Key:Snip
    ?
    ?
    ? ID: Snip
    ? Hardware: 0121
    ? Firmware: 0121
    ---snip---
    ? DetectedProtocols: None
    ?
    ?
    ? Unable to detect the vehicles diagnostics protocol

    ? Uninstalled 3.6.26

    ? Installed 4.0.12, results the same

    5/4/2019 12:56:10 PM
    VCM Suite Product: VCM Scanner 4.0.12

    Operating System: Windows 10 (build 17763)
    Microsoft .NET: 4.0.30319.42000, 4.7.1 or later
    CPU: Intel(R) Core(TM) i5-6300U CPU @ 2.40GHz
    Available Memory: 7,102 MB


    Device ID: Snip
    Application Key:Snip

    [Vehicle Type]
    1998 Chevrolet Camaro (8 cyl), (GM: 6)

    [Specific Vehicle Enhancement]
    1998 Chevrolet Camaro (8 cyl), [snip], [2bar upgrade], (GM: 2)


    ID: Snip
    Hardware: 0121
    Firmware: 0121
    ---snip---
    DetectedProtocols: None


    ? Unable to detect the vehicles diagnostics protocol

    ? Uninstalled 4.0.12

    ? Installed beta 4.3.603, received same error

    5/4/2019 12:58:42 PM
    VCM Suite Product: VCM Scanner 4.3.603 Beta

    Operating System: Windows 10 (build 17763)
    Microsoft .NET: 4.0.30319.42000, 4.7.1 or later
    CPU: Intel(R) Core(TM) i5-6300U CPU @ 2.40GHz
    Available Memory: 7,142 MB


    Device ID: Snip
    Application Key:Snip

    [Vehicle Type]
    1998 Chevrolet Camaro (8 cyl), (GM: 6)

    [Specific Vehicle Enhancement]
    1998 Chevrolet Camaro (8 cyl), [snip], [2bar upgrade], (GM: 2)


    ID: Snip
    Hardware: 0121
    Firmware: 0121
    ---snip---
    DetectedProtocols: None


    ? Unable to detect the vehicles diagnostics protocol

    ? 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. Clicking the Retry button does not alter the progress bar. All I can do is click the Close button here. I did not try disconnecting and reconnecting the USB cable at this time.

    ? Uninstalled beta 4.3.603

    ? Re-downloaded the latest full version of VCM Suite (4.4.2), and re-installed. Resync behaved the same way. Disconnected the brand new USB cable from interface, heard the disconnect chime, reconnected cable, heard the connect chime. Resync now reports backup successful.

    ? Connected laptop to PCM, busy slight intermittently blinks on interface, and connects to PCM, and scanner currently works. Odd that it says Detected Protocols: None, and right below that it lists the detected Protocol Info:

    ? 5/4/2019 1:17:53 PM
    ? VCM Suite Product: VCM Scanner 4.4.2
    ?
    ? Operating System: Windows 10 (build 17763)
    ? Microsoft .NET: 4.0.30319.42000, 4.7.1 or later
    ? CPU: Intel(R) Core(TM) i5-6300U CPU @ 2.40GHz
    ? Available Memory: 6,813 MB
    ?
    ?
    ? Device ID: Snip
    ? Application Key:Snip
    ? Available Credits: GM 0/8, Ford 0/0, Dodge 0/0
    ? Available License Slots: 406/409
    ?
    ? [Vehicle Type]
    ? 1998 Chevrolet Camaro (8 cyl), (GM: 6)
    ?
    ? [Specific Vehicle Enhancement]
    ? 1998 Chevrolet Camaro (8 cyl), [Snip], [2bar upgrade], (GM: 2)
    ?
    ?
    ? ID: Snip
    ? Hardware: 0121
    ? Firmware: 0121
    ---snip---
    ? DetectedProtocols: None <--------------------------
    ?
    ?
    ? Protocol Info: SAE J2178, J1962: VPW <-----------------------
    ?
    ? ECM: 10, VPW - V8_97_98, GM Gen3 V8
    ? VIN: Snip - 1998 Chevrolet Camaro Sport Coupe & CONV., 5.7 L, 8 Cyl, GM_V8_97_98
    ? Serial: Snip
    ? Basic PIDs: 22
    ? Trouble Codes:
    ? P0803 - Upshift / Skip Shift Solenoid Control Circuit (Pending, Current)
    ? Controller Type ID By VIN: 4030
    ? Diagnostic Requirements: None
    ? Scanning Methods: ISO 15031-5 Mode 0x01 Functional, ISO 15031-5 Mode 0x01 Physical, SAE J2190 Mode 0x22, SAE J2190 Mode 0x23, GM Mode 0x2C 0x2A
    ?

    Further testing is delayed due to a low laptop battery. Both the old and the new USB cables have slight play when plugged into the interface, both lateral and vertical. This is one reason I prefer legacy connectors (like thumbscrews) over slip-fit connectors (USB), but I understand the compatibility challenges.
    1998 NBM Camaro Z28
    LS3 motor
    Mod list

  3. #3
    HP Tuners Support
    (foff667)
    Bill@HPTuners's Avatar
    Join Date
    Jun 2004
    Location
    Hailing from Parts Unknown
    Posts
    26,073
    4.4 is the newest version of software, we no longer support older versions, so if its working with the newest version 4.4 then it is working as intended.
    It doesn't have to be perfect, it just needs to be done in two weeks...

    A wise man once said "google it"

  4. #4
    Tuner in Training
    Join Date
    Nov 2009
    Posts
    47
    Quote Originally Posted by Bill@HPTuners View Post
    4.4 is the newest version of software, we no longer support older versions, so if its working with the newest version 4.4 then it is working as intended.
    So basically yall updated the cable to where it will no longer work with 2.24 or older software version's?
    I haven't made a million post's so im not a super tooner