Results 1 to 7 of 7

Thread: First attempt... Fail... Help??

  1. #1

    First attempt... Fail... Help??

    I know I should have done "write entire"... I messed up. This is the situation: Started with a 411 pcm from a 2001 Chevy Express 3500 5.7L31 / 4l80e, VIN 1GCHG39R111176861. Read just fine in the vcm suite. Wrote just the calibration file from 411 pcm from a 2002 Chevy Express 1500 5.7L31 / 4l60e, VIN 1gbfg15r421139312. Seem to go fine... until I tried to read it, "Detect Protocol Failed". If I try to write to it, "Controller Unlocker: Timed Out". I bought credits to unlock the 2001 Express tune that I wanted to use, then after everything failed, I bought credits and unlocked the original tune to the pcm I was trying to write to. So now I have $200 into it and nothing. These two pcm's should be identical, but I see one difference: The 3500 has o/s 12208322 and the 1500 has o/s 12212156. Does this effect it?? Is it possible to recover this and if so how?? I know if I would have done write entire, all would have been fine. I tried killing power to pcm for 1/2 hour... Same results. Did I brick it??

  2. #2
    HP Tuners Support
    (foff667)
    Bill@HPTuners's Avatar
    Join Date
    Jun 2004
    Location
    Hailing from Parts Unknown
    Posts
    28,261
    what is your ticket number through support so we can assist you further?
    It doesn't have to be perfect, it just needs to be done in two weeks...

    A wise man once said "google it"

  3. #3
    Hey Bill. The ticket I'm referring to is #139821 - Which I sent the wrong harness pic on, I'm using Blue PCM 60 to OBDII 4&5, Blue PCM 20 to OBDII 16 - 12v Unswitched, Blue PCM 19 to OBDII 16 - 12v Switched, Blue PCM 58 to OBDII 2. I tried to write entire on another 411 PCM today and it failed mid write and now I have the same issues with it. That's $300 in credits and $200 in PCM's.

  4. #4
    Oh and Bill, Cory has been helping me. I am now downloading BETA and the latest drivers for mpvi2 (which I just installed two weeks ago). I'll see how that goes.

  5. #5
    And an update... BETA and drivers didn't help. Same errors. I'm out so much time and money that I'm physically ill.

  6. #6
    Also forgot to mention (I think) that I have tried this from another laptop running windows 10 and USB 3.0 with the same exact results. K, think you're all caught up. You're turn.

  7. #7
    Potential Tuner
    Join Date
    Sep 2018
    Posts
    6
    Did you get this solved? what was issue?

    I am having similar issue...support ticket in...