Another detect protocol fail post

[the Noob]

Greetings tuners,

Having more trouble than I was expecting figuring out this tuning game. I cant even connect! Was worried about VE tables and spark, but I cant read my PCM....

Rundown: 1970 ford F100- LQ4/tr6060/borg S475 controlled by a P59. (not running yet, tune on pcm is for e85)

Keep getting detect protocol fail when trying to connect.
Here is what I have tried so far:

Checked grounds-all clean and tight. PCM grounds attach to rear of cylinder head.
Checked pin outs that require grounds and 12V. All good. Hooked up my scangauge and it reads all sensors like normal.
Charged battery
Resynced my MVPI2. Added to my devices on HPtuners.com and although it doesn't have any credits, it says disabled, could this be a factor or does that just mean it doesn't have any credits? Purchased it new in the package.
Tried to connect the MPVI2 to my 2008 F350 6.4l and received the same message.
Lap top in use is a think pad with windows 10. Have tried the beta VCM suite also.
Getting power to USB port

here is the info when connected:
3/9/2019 1:29:11 PM
VCM Suite Product: VCM Editor 4.2.12

Operating System: Windows 10 (build 16299)
Microsoft .NET: 4.0.30319.42000, 4.7.1 or later
CPU: Intel(R) Celeron(R) CPU N2940 @ 1.83GHz
Available Memory: 1,385 MB


Device ID: 2045080799
Credits Purchased: 0
Credits Used: 0
Credits Available: 0
Licensed Features:


ID: 2045080799
HardwareVersion: 1.4.0
ManufactureDate: 10/1/2018 3:04:15 PM
PartNumber: 6230
FirmwareVersion: 2.0.120
PoweredOnTime: 00:01:27
VehicleConnectedTime: 00:01:27


Unable to detect the vehicles diagnostics protocol


Any help with this will be GREATLY appreciated.

Thanks! Josh

P.S. I submitted a help ticket but figured it cant hurt to get some ideas rolling before Monday when HPT opens up.

[96gt4.6]

Josh, where you able to get this issue resolved? I am having a similar issue.

[JimMueller]

I just started having the same issue last night. Rarely used the product between versions 2.24 & 4.0, then went direct to 4.4. a couple of days ago, when it upgraded the MPVI firmware. I find the timing of the 4.4 upgrade, interface firmware upgrade, and the error suspicious.

[Bill@HPTuners]

I just started having the same issue last night. Rarely used the product between versions 2.24 & 4.0, then went direct to 4.4. a couple of days ago, when it upgraded the MPVI firmware. I find the timing of the 4.4 upgrade, interface firmware upgrade, and the error suspicious.

Do you own an MPVI1 or an MPVI2? Original poster owns an MPVI2 and this post is from several months ago so if you have an MPVI1 and are having issues now it really has nothing to do with this thread.

[JimMueller]

Ahh, overlooked that he has an MPVI2, I have MPVI1, sorry.

[Bill@HPTuners]

Ahh, overlooked that he has an MPVI2, I have MPVI1, sorry.

Software, including firmware, is only as perfect as the people writing it and unfortunately we live in an imperfect world. I would suggest opening a support ticket if you are having issues as troubleshooting those types of issues via the forum is nearly impossible.