MPVI2 Unable to detect the vehicles diagnostics protocol 2013 Camaro ZL1

[sbelyo]

Hi All..

I bought an MPVI2 about three years back to tune a car. I never got around to it. I recently purchased a 2013 Camaro ZL1 and would like use it to log some data on it. I created a HPtuners account and registered the device. I resynched it and the message said synch was complete. I didn't get any errors or anything bad. I'm running windows 11 with the latest MPVI2 drivers and VCM Scanner 5.0.4 When I plug the interface in to the ODBII port it gets power. I put the key in the on position (I tried the 1st and 2nd position). I open VCM Scanner and click connect to vehicle, the interface connects but when it tried to read the vehicle it says "Unable to detect the vehicles diagnostics protocol".

The vehicle is a 2013 Chevrolet Camaro ZL1 with the LSA engine

Here's the log:

6/11/2023 12:44:43 PM
VCM Suite Product: VCM Scanner 5.0.4

Operating System: Windows 11 (build 22621)
Microsoft .NET: 4.0.30319.42000, 4.7.1 or later
CPU: 11th Gen Intel(R) Core(TM) i3-1115G4 @ 3.00GHz
Available Memory: 3,912 MB


Device ID: (I removed it)


ConnectionMethod: USB
ID: (I removed it)
HardwareVersion: 1.4.0
ManufactureDate: 7/23/2019 3:27:57 PM
PartNumber: 6230
FirmwareVersion: 2.0.123
PoweredOnTime: 00:31:48
VehicleConnectedTime: 00:31:48
VehicleDiagnosticConnector: 1


Unable to detect the vehicles diagnostics protocol

I opened a support ticket 103923, not sure what went wrong here. Any thoughts?

[sbelyo]

Support actually got back to me on a Sunday! Now that's customer service!

It needed a firmware update. It works like a charm

Disconnect your MPVi2 or MPVI2+ from your laptop.
Below the BT LED there is a button hidden in the dark square area
Hold this button down.
Now while holding this button down connect to the laptop.
Check for a flashing PWR light. If flashing you can release the button and now open
VCM Editor or Scanner and perform an VCM suite information log
by clicking the HELP then VCM suite information log.

It opens a new dialog box. Click the blue circle with the "I" in it.
This should start the firmware updating process.

[thomspeed]

Support actually got back to me on a Sunday! Now that's customer service!

It needed a firmware update. It works like a charm

Disconnect your MPVi2 or MPVI2+ from your laptop.
Below the BT LED there is a button hidden in the dark square area
Hold this button down.
Now while holding this button down connect to the laptop.
Check for a flashing PWR light. If flashing you can release the button and now open
VCM Editor or Scanner and perform an VCM suite information log
by clicking the HELP then VCM suite information log.

It opens a new dialog box. Click the blue circle with the "I" in it.
This should start the firmware updating process.

Thank you.... saved me

[Carldude]

Hi All..

I bought an MPVI2 about three years back to tune a car. I never got around to it. I recently purchased a 2013 Camaro ZL1 and would like use it to log some data on it. I created a HPtuners account and registered the device. I resynched it and the message said synch was complete. I didn't get any errors or anything bad. I'm running windows 11 with the latest MPVI2 drivers and VCM Scanner 5.0.4 When I plug the interface in to the ODBII port it gets power. I put the key in the on position (I tried the 1st and 2nd position). I open VCM Scanner and click connect to vehicle, the interface connects but when it tried to read the vehicle it says "Unable to detect the vehicles diagnostics protocol".

The vehicle is a 2013 Chevrolet Camaro ZL1 with the LSA engine

Here's the log:

6/11/2023 12:44:43 PM
VCM Suite Product: VCM Scanner 5.0.4

Operating System: Windows 11 (build 22621)
Microsoft .NET: 4.0.30319.42000, 4.7.1 or later
CPU: 11th Gen Intel(R) Core(TM) i3-1115G4 @ 3.00GHz
Available Memory: 3,912 MB


Device ID: (I removed it)


ConnectionMethod: USB
ID: (I removed it)
HardwareVersion: 1.4.0
ManufactureDate: 7/23/2019 3:27:57 PM
PartNumber: 6230
FirmwareVersion: 2.0.123
PoweredOnTime: 00:31:48
VehicleConnectedTime: 00:31:48
VehicleDiagnosticConnector: 1


Unable to detect the vehicles diagnostics protocol

I opened a support ticket 103923, not sure what went wrong here. Any thoughts?