Problem with Chevy ECM downloads.(Unable to detect the vehicles diagnostics protocol)

Hello I'm New to the forums. I currently have a open ticket and we are working thru the situation but i thought i would see if anyone else is having the same problem.
I have VCM Suite Product: VCM Editor 4.0.6 With the New MPVI2 device.

Operating System: Windows 10 (build 17134)
Microsoft .NET: 4.0.30319.42000, 4.7.1 or later
CPU: Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz
Available Memory: 11,760 MB

I have not been able to connect or download the following 2 bench ECU,s 200X 5.3 and 6.0 Chevy trucks.
a 2007 Chevy 1500 Pickup or a 2003 Chevy Monte Carlo. the 2 vehicles have same problem. (Unable to detect the vehicles diagnostics protocol)

I have connect fine to a 2012 Chevy Pickup, 2014 Dodge Challenger SRT8 and a 2017 Chevy Malibu these vehicles connect and download fine.

Anyone else having the same issue :doh:

Same exact situation you?re in man, I?ve emailed them, waiting on response, I?m using an 01 tahoe pcm and harness and get the same message as you, and it hooks right up to my 15? Chevy Cruze, have you made any progress figuring the problem out?

No Progress yet I was asked to download the Beta version and try. I did a clean install and same problem I expect another email tomorrow and will post any updates.
The next option was to send my interface and a PCM for testing @hptuners.

The Desktop Harness I am using is setup like this. Anyone please correct if I am wrong.

Blue Pin 1,40 (Black) Ground
Blue Pin 19 (Pink) 12 V Switched
Blue Pin 20 (Orange) 12 V Constant Power
Blue Pin 58 (Green) ODB2 Data

ODB2 Connector
Pin 2 ODB2 Data
Pin 4 Ground
Pin 5 Ground
Pin 16 12 V Constant Power

12 Volt 3 Amp Power Supply

Thanks Ken

They emailed me and said they?re working on a firmware that should be done by the end of the day today and are sending it to me to try, hopefully it works!

Quote:

---

Originally Posted by Rd3

They emailed me and said they?re working on a firmware that should be done by the end of the day today and are sending it to me to try, hopefully it works!

---

Dont forget about me ticket#132961 lol

Well I downloaded the latest firmware.

HardwareVersion: 1.4.0
ManufactureDate: 5/8/2018 6:36:08 PM
PartNumber: 6230
FirmwareVersion: 2.0.79

No Joy Same problem so i just have no idea.

Has anyone figured this out?

Quote:

---

Originally Posted by wilding111

Has anyone figured this out?

---

We are working to resolve the issue. If he already have not done so please email support if you are having an issue.

Bill, what does the issue seem to be? Something in the software? Just curious is all not rushing or anything.

Quote:

---

Originally Posted by Rd3

Bill, what does the issue seem to be? Something in the software? Just curious is all not rushing or anything.

---

We're hoping a firmware update will be able to fix everybody up.

Quote:

---

Originally Posted by Bill@HPTuners

We're hoping a firmware update will be able to fix everybody up.

---

Sounds good, hopefully the issue is resolved after, I?m eager to play with the program!

i think we are allll dying for them to fix this... sucks that i got my first HP tuners setup today... AND THIS... talk about a bad first impression

Update for everyone following, my mpvi2 is in transit for hp tuners now to get the problem fixed, they tried to put see if an update would work with no luck, bug in the hardware, but they?re backing it up and fixing it, so stand up guys in my book.

They just requested my mailing address to ship mine back for testing. Havent even got to use it yet. Working on this car for 2 months and ready to start it. smh

Quote:

---

Originally Posted by Kelly Norsworthy

They just requested my mailing address to ship mine back for testing. Havent even got to use it yet. Working on this car for 2 months and ready to start it. smh

---

I just purchased mpvi2 and am having same issue detect protocol failed . I'm using a new painless performance bench harness . I can connect to wife's 2003 mustang but not my 2002 camaro . Hopefully good news coming soon

In for the fix. Ticket 134174. Just got mine this evening and same issue. 2002 Chevrolet Express 5.7 (0411 ECM) that worked 100% with the MPVI system. Sent it back to the owner and ordered the MPVI2 just to have the same luck tuning as I had without it. Thanks in advance! :(

Same issue they want me to send mine in to test it. Glad im not the only one but it also sucks.

Quote:

---

Originally Posted by Dirtydeeds

I just purchased mpvi2 and am having same issue detect protocol failed . I'm using a new painless performance bench harness . I can connect to wife's 2003 mustang but not my 2002 camaro . Hopefully good news coming soon

---

Please email support.

As far as I can tell it looks like class 2 serial is screwed up, every other protocol seems to work fine.

Yeah, from out testing it's mainly vpw applications and only in vehicle, we we're unable to easily reproduce the issues on our bench harness.

Quote:

---

Originally Posted by Bill@HPTuners

Yeah, from out testing it's mainly vpw applications and only in vehicle, we we're unable to easily reproduce the issues on our bench harness.

---

Bill, can I purchase a second interface unit that you guys will test and confirm to be a GOOD unit?? and ill return my first one!! I'm dead in the water and need my truck!! I asked this yesterday on my open ticket, have yet to get a response..

Quote:

---

Originally Posted by Bill@HPTuners

Yeah, from out testing it's mainly vpw applications and only in vehicle, we we're unable to easily reproduce the issues on our bench harness.

---

It was working fine out of the box for vpw, once the firmware updated that's when the issue started, I guess I would compare current firmware with the one the unit shipped with as that one seemed to work perfect.

Quote:

---

Originally Posted by nightjoker7

It was working fine out of the box for vpw, once the firmware updated that's when the issue started, I guess I would compare current firmware with the one the unit shipped with as that one seemed to work perfect.

---

Would there be a possibility of pushing the orignal firmware for the module out and allowing us to try that? It very well could be the issue. I didn't get the chance, and I'm sure not many others did, to try the firmware that the modules are shipped with.

Quote:

---

Originally Posted by Bill@HPTuners

Yeah, from out testing it's mainly vpw applications and only in vehicle, we we're unable to easily reproduce the issues on our bench harness.

---

I should also mention yesterday when it had the out of box firmware it was able to communicate with every single computer I tested it with on the bench using a setup I have programmed thousands of computers with using tis2web, tis2000, tunercats and FORD IDS, both Gmlan and class2. As soon as the firmware updated class2 doesn't work on the bench or in the vehicle. If I use my mpvi1 it's completely fine. Seems like an absolute certainty its the new firmware causing the issue. Unless it's a hardware issue with the class2 circuit and its just a coincidence it started when updated, since others are having the same issue that seems doubtful to me.

Update I downloaded beta and it started working again. However I know the next time I use it, it won?t work. It?s definately a software issue. I?d have no problem uninstalling and installing drivers everytime if it guaranteed me being able to write a tune.

It's not a firmware issue, we are working directly with our customers on resolving the issue.

Brought some computers home with me and my bench setup, it looks like its only certain class2 serial computers. tried a 411 wouldn't work, then tried a P12 from a 06 colorado, that works fine. Also tried a p10 in a trailblazer that wouldn't work either so it's kinda hit and miss for some reason.

Is it a batch of bad MPVI2s? Or is the MPVI2 just not capable of reading certain PCMs that the previous MPVI could? I'm getting a "detect protocol failed" on my 2005 Sierra. Had a bullydog tune loaded, tried returning to stock, and it didn't read either time. When I resync the interface in VCM editor, it does not show my available licenses either...

(Support) Ticket ID: 134262

6/17/2018 9:37:55 AM
VCM Suite Product: VCM Editor 4.0.2

Operating System: Windows 7 Service Pack 1
Microsoft .NET: 4.0.30319.42000, 4.7.1 or later
CPU: Intel(R) Core(TM) i5-3340M CPU @ 2.70GHz
Available Memory: 2,398 MB


Device ID: 2030285121
Credits Purchased: 2
Credits Used: 0
Credits Available: 2


ID: 2030285121
HardwareVersion: 1.4.0
ManufactureDate: 5/31/2018 3:07:40 PM
PartNumber: 6230
FirmwareVersion: 2.0.79
PoweredOnTime: 00:00:22
VehicleConnectedTime: 00:00:22


Unable to detect the vehicles diagnostics protocol

I have emailed support ticket #133698 c.o. William Henn and sent vehicle logs and debug.datt files on June 13 2018 . Have yet to hear a reply from support. Assume there working on it

Quote:

---

Originally Posted by Dirtydeeds

I have emailed support ticket #133698 c.o. William Henn and sent vehicle logs and debug.datt files on June 13 2018 . Have yet to hear a reply from support. Assume there working on it

---

I sincerely apologize our hardware designer was off thurs/friday for his wedding so it was sitting in his work in queue. I'll respond right now.

Quote:

---

Originally Posted by Bill@HPTuners

I sincerely apologize our hardware designer was off thurs/friday for his wedding so it was sitting in his work in queue. I'll respond right now.

---

I have an open ticket (134028) and haven?t gotten a response back, after multiple attempts. I asked on here and in the emails if I could purchase a second interface that is known to be good, and I?ll return the one I have to cut down on ?down time?... if that?s not an option then I?ll overnight the interface I have and pay for expedited shipping back.. but I NEED to get a response to get to the bottom of this!!

Quote:

---

Originally Posted by boostlag

I have an open ticket (134028) and haven?t gotten a response back, after multiple attempts. I asked on here and in the emails if I could purchase a second interface that is known to be good, and I?ll return the one I have to cut down on ?down time?... if that?s not an option then I?ll overnight the interface I have and pay for expedited shipping back.. but I NEED to get a response to get to the bottom of this!!

---

Corey responded to your email on the 15th, here was his response "Hello,

I would like to test the interface here on the bench. Please Verify your shipping information (where the interface will be picked up) including Interface serial number, phone number, and email address. We will send a shipping label via UPS so you can send in the interface. Sorry for the inconvenience.

Thank You"

We are still waiting for you to send us your shipping address, not the other way around.

Ok so I tried to use it on my gfs car and it?s back saying unable to detech protocol. I was given a ticket to send it a little over a week ago but I didn?t because I downloaded beta and it worked. I don?t understand how it lets you make one change every blue moon then stop working.

Just got my mpvi2 back from hp tuners after sending it in on a ticket and it works awesome reads and writes and does everything it's supposed to . Only took a few days but well worth it

Quote:

---

Originally Posted by Dirtydeeds

Just got my mpvi2 back from hp tuners after sending it in on a ticket and it works awesome reads and writes and does everything it's supposed to . Only took a few days but well worth it

---

Awesome, glad we could help you out! :)

Quote:

---

Originally Posted by Bill@HPTuners

Awesome, glad we could help you out! :)

---

Bill and Corey Thanks for all of the assistance.

UPDATE: After awhile of working thru this issue I would like to thank Corey Clayton with HP Tuners Support, The issue has been resolved it was with a communications Protocol that was being used. I sent My MPVI2 and My ECU and bench harness to Corey he attacked the issue and got it resolved very quickly an sent it back now everything works great. So if you are still having this issues contact support immediately they are very responsive and will resolve it in a quick manner. They are very professional and courteous and will get it resolved have patience. :yay::yay::yay:

Ticket 136082 submitted for same issue.

7/2/2018 4:56:31 PM
VCM Suite Product: VCM Editor 4.0.12

Operating System: Windows 10 (build 15063)
Microsoft .NET: 4.0.30319.42000, 4.7
CPU: Intel(R) Core(TM) i7-5600U CPU @ 2.60GHz
Available Memory: 3,455 MB


Device ID: 1351246741
Application Key:33VB7-7OSM2-I7M4M-7FMMI-CW6GT-N2GQM-3NSMO


Device ID: 2030267534
Credits Purchased: 2
Credits Used: 0
Credits Available: 2


ID: 2030267534
HardwareVersion: 1.4.0
ManufactureDate: 5/31/2018 7:30:08 PM
PartNumber: 6230
FirmwareVersion: 2.0.84
PoweredOnTime: 00:00:33
VehicleConnectedTime: 00:00:00

Sent my MPVI2 back and they got it back to me very quickly but still has the same problem lol

Any updates on this. I have 2 MPVI2s that both come up with Detect Protocol failed when trying to read a 05 GM 5.3 ECU 12589463. Both units have been fully updated and I ran Both the current Beta and latest software with no luck.

My MPVI original reads and writes just fine......