Results 1 to 8 of 8

Thread: VCM Scanner always says: "Erase Logs Failed"

  1. #1

    Exclamation VCM Scanner always says: "Erase Logs Failed"

    Everytime I erase my logs from the MPVI Pro Interface, the dialog's status bar tells me, "Command: Erase Logs Failed". it does this everytime, regardless of how many logs there are or how large the logs are, and also when no logs are present. The logs do seem to erase though.

    Also, I occasionally get the "ERR" LED when I try to start recording. This morning, it refused to log at all, giving me a "ERR" everytime. Power cycling did not help.

    Since arriving at work, I've done another "Erase Logs" step and will try recording again tonight when I leave work.

    Regards,
    -Mike

  2. #2
    HP Tuners Support
    (foff667)
    Bill@HPTuners's Avatar
    Join Date
    Jun 2004
    Location
    Hailing from Parts Unknown
    Posts
    28,273
    What software version are you running? Can you post a .hpt file of the vehicle in question so we may try and recreate it?
    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

    Arrow

    I am running version 2.2.0.0.

    It doesn't seem to matter which HPT file I have loaded into the ECU. Nor does it matter which CFG I have laoded into the interface. Attached are my latest HPT and CFG.

    Here's what I do.

    1) Get in car
    2) Connect MPVI pro interface to OBD-II cable.
    3) Verify power on interface
    4) Start car
    5) Press and hold record until record LED illuminates
    6) drive to destination
    7) Press and hold stop
    8) Wait for BUSY LED to stop blinking
    9) Disconnect interface from OBD-II cable
    10) shut off car
    11) Connect interface box to PC and fire up VCM scanner
    12) Read/Save log
    13) Perform "Erase Logs" command
    14) Get "Erase Logs Failed" message

    Thanks,
    -Mike

  4. #4
    HP Tuners Support
    (foff667)
    Bill@HPTuners's Avatar
    Join Date
    Jun 2004
    Location
    Hailing from Parts Unknown
    Posts
    28,273
    People should take notes from that post on how to recreate something

    I'll try and test it out on my car later today with 2.2.0 to see if I can recreate it.
    It doesn't have to be perfect, it just needs to be done in two weeks...

    A wise man once said "google it"

  5. #5
    Advanced Tuner Pro Street's Avatar
    Join Date
    Aug 2006
    Location
    806
    Posts
    244
    I had the erase fail this weekend one time out of about 7 logs.I just tried it again and it erased with out error.
    2018 GMC Denali A8 6.2L
    2016 CTS-V
    2016 C7 Z06 A8
    2016 C7 Z06/Z07 A8 vert
    2015 Chevy SS 6.2 LS3 A6
    1996 Impala SS LT1 CAI
    1995 Chevy 1500 5.3 CAI Z06 cam
    1957 Chevy vert

  6. #6
    HP Tuners Support
    (foff667)
    Bill@HPTuners's Avatar
    Join Date
    Jun 2004
    Location
    Hailing from Parts Unknown
    Posts
    28,273
    Try this for S's & G's

    1) Get in car
    2) Connect MPVI pro interface to OBD-II cable.
    3) Verify power on interface
    4) Start car
    5) Open vcm scanner
    6) Click the connect icon
    7) Delete any unsupported PID's showing
    8) Click Scan-MPVI Pro Data Logging
    9) Click Write Config
    10) Disconnect usb from interface & laptop

    11) Press and hold record until record LED illuminates
    12) drive to destination
    13) Press and hold stop
    14) Wait for BUSY LED to stop blinking
    15) Disconnect interface from OBD-II cable
    16) shut off car
    17) Connect interface box to PC and fire up VCM scanner
    18) Read/Save log
    19) Perform "Erase Logs" command

    It may or may not do anything but I cannot recreate the failure so we'll try something different to get you so you can't create it.

    Also are you able to erase them without issue following the help guides quick erase procedure?

    When not logging, hold the record and stop buttons for 2 seconds to erase the logs without the laptop. The Busy LED will blink until all logs are erased.
    It doesn't have to be perfect, it just needs to be done in two weeks...

    A wise man once said "google it"

  7. #7
    You may be onto something there, Mr. Bill...

    The MPBI Pro does NOT like to play right with an unsupported PID written to it, especially for stand alone logging.

    Been there, done that, too many times!
    ____________________________________

    Good engineering is simply finding the right wrench to pound in the correct screw.



  8. #8
    Thanks Bill, I will give both of those a try.

    -Mike