Need help with a major issue / Cry for help!!! [Archive]

View Full Version : Need help with a major issue / Cry for help!!!

Rausche

June 25th, 2008, 10:39 AM

Okay, so before I begin this, I want to make it perfectly clear that I am in no way trying to bash anybody, I just want to get this problem solved. I am telling this story as I remember it, and as it appears to me through my perspective.

I own a 2003 Silverado SS, complete with the LQ9 engine. I joined SilveradoSS.com, and went to the track with them. While I was there, I had a member of that forum (PladdPezzPunk) tune my truck for me. The tune file was written by Brian @ PCMForLess, and PladdPezzPunk did some minor adjustments at the track. While at the track, just after I had the truck tuned, my VATS went haywire. The truck would still start and run, but only if the key was turned to "crank" after sitting in the "on" position until the VATS light went out. We tried to do a re-learn, but no luck. We decided that it was the key sensor in the ignition that had gone bad. I thought it was a little odd how coincidental it was for that happen right after my truck's computer had been messed with, but whatever.

We tuned the truck several times at the track (I shaved almost a full second off my 1/4 mile time from tuning alone). After I got home, I was so pumped about the tuning I did loads of research, read a few books, and decided I wanted to try my hand at it. I bought EFILive V2, and went to hook up to my truck...

Bad news. My V2 wouldn't communicate with the truck's computer. It would start to get connected, then fail. After some tinkering, I could only get it to go as far as the final stage of loading the bootloader, then the PCM would re-arm. I called PladdPezzPunk to see if the tune was locked. He assured me that it wasn't (I believe him, I was looking over his shoulder the whole time when he tuned it, nothing was ever done to lock the PCM through the tune). After another month or so, I had him come down and try and restore me to defaults, so I could start fresh. Now he cannot get into my PCM. He encounters the same issues I do.

I had tried every suggested seed key, tried using the original cable that was tuned to truck, used different versions of EFILive to get in (a new version was released a little while after my truck was tuned), and tried almost every option in every menu I can think of.

PladdPezzPunk is at a loss, he has tuned plenty of vehicles before and never run into an issue such as this. He is telling me that there are bad checksums in the PCM somehow. My thought is that my VATS being screwed up has something to do with this, although I can't even perform the manual re-learn successfully. The only combination of things I haven't tried is using the original cable with the original version of EFILive that it was tuned on (although I doubt that would make a difference).

I need some help here people... I have a bunch of toys ready to go on the truck that I want to be able to tune the PCM to in order to get the most out of them, but I need to get into my tune first! I do not want to be stuck with having to get a new PCM!!! I am open to any suggestions you have, but I am at the end of my rope here...

TAQuickness

June 25th, 2008, 11:37 AM

Rausche - Welcome to the forum.

Have you tried getting a dealer to reset your PCM back to stock with the tech 2?

Rausche

June 25th, 2008, 01:31 PM

Rausche - Welcome to the forum.

Have you tried getting a dealer to reset your PCM back to stock with the tech 2?

I have heard that the Tech2 can work miracles sometimes, but I have two concerns here:

1) I don't think there is a single "technician" at my dealership, they're all "mechanics", if you know what I mean. That being said, I like to keep my truck away from there as much as I can. They see my camaro plenty though...

2) The truck is still under warranty. Asking them to do this is admitting that I've had it messed with, and there goes my entire powertrain warranty. I had though about fabricating some story and having them just try to fix the VATS and seeing what happens... That is along the lines of a last resort for me... It's actually beyond buying a new PCM...

Lextech

June 25th, 2008, 01:42 PM

Rausche

June 26th, 2008, 12:00 AM

Go to your dealership and talk to the tech that you like the best. A fellow hotrodder/tech is your best bet. A fellow hotrodder in need carries alot more weight than a customer who doesn't want to pay dealer prices!!! Drop it off at 8:00AM and give him the keys/50.00/your cell number.

Jeff

From what I have been seeing with EFILive, I think the T2 will run into the same issues that I am having. I do not even have the ability to read the tune, the PCM always re-arms before EFILive gets fully situated.

ScarabEpic22

June 26th, 2008, 09:03 AM

Rausche

June 28th, 2008, 01:13 PM

This is an interesting problem, havent heard of this before...

I would try to use the latest version of EFILive (7.5.4 build 63) and firmware 2.04.72 (non BBL beta fw) or (2.05.17(0622) BBL beta). Select the LS1 99-08 controller, and check "Try Alt Keys". Also, if this doesnt work please copy/paste the info that the status window spits out when it fails.

This is from the "PCM Security" screen:

22:08:46.469: Scanning for EFILive FlashScan V2 USB
22:08:46.563: Interface firmware version: 2.4.70
22:08:46.578: Current protocol set to: "SAE J1850 VPW"
22:08:49.703: Interface firmware model: FS2
22:08:49.734: Interface firmware version: 2.4.70
22:08:49.750: Interface firmware date: Dec 10, 2007
22:08:49.766: FlashScan serial number: 003645445482
22:08:49.797: FlashScan license number: 003645445482
22:08:57.844: Disconnecting ...
22:08:57.906: Disconnected
22:08:58.547: Scanning for EFILive FlashScan V2 USB
22:08:58.750: Interface firmware version: 2.4.70
22:08:58.766: Current protocol set to: "SAE J1850 VPW"
22:08:59.859: Current protocol: "SAE J1850 VPW"
22:08:59.906: Interface firmware model: FS2
22:08:59.922: Interface firmware version: 2.4.70
22:08:59.953: Interface firmware date: Dec 10, 2007
22:08:59.969: FlashScan serial number: 003645445482
22:08:59.984: FlashScan license number: 003645445482
22:09:00.094: Getting status...
22:09:00.141: Status: OK.
22:09:00.141: Request GM VIN...
22:09:00.266: VIN: 2GCEK19N931392795
22:09:00.828: Request serial number...
22:09:00.938: Serial number: 000000000000
22:09:01.484: Request GM operating system...
22:09:01.531: GM operating system: 12593058
22:09:02.000: Request GM BCC...
22:09:02.047: GM BCC:
22:09:02.516: Request GM VAT/IGN Cycles...
22:09:02.547: GM VAT/IGN cycles: 0
22:09:03.016: Analysing security...
22:09:03.063: Not ready, waiting 1 second for retry...
22:09:04.328: PCM seed is: $00FF
22:09:04.328: Unlock attempt 1 of 1
22:09:04.719: Security analysis complete.
22:09:04.734: Ready
22:09:09.063: Attempting to unlock PCM...
22:09:09.063: Request GM VIN...
22:09:09.188: VIN: 2GCEK19N931392795
22:09:09.750: Request serial number...
22:09:09.859: Serial number: 000000000000
22:09:10.406: Request GM operating system...
22:09:10.453: GM operating system: 12593058
22:09:10.922: Request GM BCC...
22:09:10.953: GM BCC:
22:09:11.422: Request GM VAT/IGN Cycles...
22:09:11.469: GM VAT/IGN cycles: 0
22:09:12.250: Bootloader version: LS1B_v1.3L (0742-27D9)
22:09:12.250: Preparing PCM for locking/unlocking...
22:09:12.297: PCM seed is: $00FF
22:09:12.297: Unlock attempt 1 of 1
22:09:40.297: Attempting to unlock PCM...
22:09:40.297: Request GM VIN...
22:09:40.422: VIN: 2GCEK19N931392795
22:09:41.000: Request serial number...
22:09:41.109: Serial number: 000000000000
22:09:41.672: Request GM operating system...
22:09:41.719: GM operating system: 12593058
22:09:42.203: Request GM BCC...
22:09:42.266: GM BCC:
22:09:42.734: Request GM VAT/IGN Cycles...
22:09:42.781: GM VAT/IGN cycles: 0
22:09:43.563: Bootloader version: LS1B_v1.3L (0742-27D9)
22:09:43.563: Preparing PCM for locking/unlocking...
22:09:43.609: Not ready, waiting 1 second for retry...
22:09:44.891: Not ready, waiting 1 second for retry...
22:09:46.156: Not ready, waiting 1 second for retry...
22:09:47.422: PCM seed is: $00FF
22:09:47.438: Unlock attempt 1 of 4
22:09:47.844: Unlock attempt 2 of 4
22:09:48.250: Not ready, waiting 1 second for retry...
22:09:49.516: Not ready, waiting 1 second for retry...
22:09:50.797: Not ready, waiting 1 second for retry...
22:09:52.063: Not ready, waiting 1 second for retry...
22:09:53.328: Not ready, waiting 1 second for retry...
22:09:54.594: Not ready, waiting 1 second for retry...
22:09:55.875: Not ready, waiting 1 second for retry...
22:09:57.141: Not ready, waiting 1 second for retry...
22:09:58.422: Unlock attempt 3 of 4
22:09:58.844: Unlock attempt 4 of 4
22:09:59.250: Not ready, waiting 1 second for retry...
22:10:00.516: Not ready, waiting 1 second for retry...
22:10:01.797: Not ready, waiting 1 second for retry...
22:10:03.063: Not ready, waiting 1 second for retry...
22:10:04.328: Not ready, waiting 1 second for retry...
22:10:05.609: Not ready, waiting 1 second for retry...
22:10:06.875: Not ready, waiting 1 second for retry...
22:10:08.141: Not ready, waiting 1 second for retry...
22:10:09.422: Initializing PCM...
22:10:10.250: Initializing PCM, step 1 of 4
22:10:10.250: Initializing PCM, step 2 of 4
22:10:11.094: Initializing PCM, step 3 of 4
22:10:12.672: Initializing PCM, step 4 of 4
22:10:12.953: PCM lock has been re-armed, attempting to unlock PCM again...

22:10:12.984: PCM seed is: $00FF
22:10:12.984: Unlock attempt 1 of 4
22:10:13.391: Unlock attempt 2 of 4
22:10:13.781: Not ready, waiting 1 second for retry...
22:10:15.047: Not ready, waiting 1 second for retry...
22:10:16.297: Not ready, waiting 1 second for retry...
22:10:17.563: Not ready, waiting 1 second for retry...
22:10:18.828: Not ready, waiting 1 second for retry...
22:10:20.094: Not ready, waiting 1 second for retry...
22:10:21.359: Not ready, waiting 1 second for retry...
22:10:22.609: Not ready, waiting 1 second for retry...
22:10:23.875: Unlock attempt 3 of 4
22:10:24.266: Unlock attempt 4 of 4
22:10:24.672: Not ready, waiting 1 second for retry...
22:10:25.938: Not ready, waiting 1 second for retry...
22:10:27.203: Not ready, waiting 1 second for retry...
22:10:28.469: Not ready, waiting 1 second for retry...
22:10:29.750: Not ready, waiting 1 second for retry...
22:10:31.000: Not ready, waiting 1 second for retry...
22:10:32.266: Not ready, waiting 1 second for retry...
22:10:33.531: Not ready, waiting 1 second for retry...
22:10:34.797: Initializing PCM...
22:10:35.547: Initializing PCM, step 1 of 4
22:10:35.547: Initializing PCM, step 2 of 4
22:10:36.797: Initializing PCM, step 3 of 4
22:10:38.359: Initializing PCM, step 4 of 4
22:10:38.656: PCM lock has been re-armed, attempting to unlock PCM again...

22:10:38.813: Initializing bootloader...
22:10:38.922: Error: Failed. Controller has returned to normal operation, please retry the operation.
22:10:39.156: Initializing bootloader, step 1 of 4
22:10:39.172: Error

Rausche

June 28th, 2008, 01:15 PM

This is an interesting problem, havent heard of this before...

I would try to use the latest version of EFILive (7.5.4 build 63) and firmware 2.04.72 (non BBL beta fw) or (2.05.17(0622) BBL beta). Select the LS1 99-08 controller, and check "Try Alt Keys". Also, if this doesnt work please copy/paste the info that the status window spits out when it fails.

This is from the "Read PCM Calibration Window", I assume that it's mostly the same data:

22:13:38.234: Scanning for EFILive FlashScan V2 USB
22:13:38.328: Interface firmware version: 2.4.70
22:13:38.344: Current protocol set to: "SAE J1850 VPW"
22:13:39.438: Current protocol: "SAE J1850 VPW"
22:13:39.469: Interface firmware model: FS2
22:13:39.500: Interface firmware version: 2.4.70
22:13:39.516: Interface firmware date: Dec 10, 2007
22:13:39.531: FlashScan serial number: 003645445482
22:13:39.563: FlashScan license number: 003645445482
22:13:39.656: Getting status...
22:13:39.703: Status: OK.
22:13:40.609: Disconnecting ...
22:13:40.672: Disconnected
22:13:41.297: Scanning for EFILive FlashScan V2 USB
22:13:41.391: Interface firmware version: 2.4.70
22:13:41.438: Interface firmware model: FS2
22:13:41.453: Interface firmware version: 2.4.70
22:13:41.484: Interface firmware date: Dec 10, 2007
22:13:41.500: FlashScan serial number: 003645445482
22:13:41.516: FlashScan license number: 003645445482
22:13:41.547: Disconnecting ...
22:13:41.609: Disconnected
22:13:42.250: Scanning for EFILive FlashScan V2 USB
22:13:42.344: Interface firmware version: 2.4.70
22:13:42.359: Current protocol set to: "SAE J1850 VPW"
22:13:43.453: Current protocol: "SAE J1850 VPW"
22:13:43.484: Interface firmware model: FS2
22:13:43.516: Interface firmware version: 2.4.70
22:13:43.531: Interface firmware date: Dec 10, 2007
22:13:43.563: FlashScan serial number: 003645445482
22:13:43.578: FlashScan license number: 003645445482
22:13:43.688: Getting status...
22:13:43.719: Status: OK.
22:13:44.641: Bootloader version: LS1B_v1.7R (04DA-6638)
22:13:44.656: Preparing PCM for reading flash...
22:13:44.688: PCM seed is: $00FF
22:13:44.703: Unlock attempt 1 of 4
22:13:45.109: Unlock attempt 2 of 4
22:13:45.531: Not ready, waiting 1 second for retry...
22:13:46.797: Not ready, waiting 1 second for retry...
22:13:48.078: Not ready, waiting 1 second for retry...
22:13:49.344: Not ready, waiting 1 second for retry...
22:13:50.609: Not ready, waiting 1 second for retry...
22:13:51.875: Not ready, waiting 1 second for retry...
22:13:53.156: Not ready, waiting 1 second for retry...
22:13:54.422: Not ready, waiting 1 second for retry...
22:13:55.688: Unlock attempt 3 of 4
22:13:56.078: Unlock attempt 4 of 4
22:13:56.484: Not ready, waiting 1 second for retry...
22:13:57.750: Not ready, waiting 1 second for retry...
22:13:59.016: Not ready, waiting 1 second for retry...
22:14:00.297: Not ready, waiting 1 second for retry...
22:14:01.563: Not ready, waiting 1 second for retry...
22:14:02.859: Not ready, waiting 1 second for retry...
22:14:04.125: Not ready, waiting 1 second for retry...
22:14:05.406: Not ready, waiting 1 second for retry...
22:14:06.672: Initializing PCM...
22:14:07.500: Initializing PCM, step 1 of 4
22:14:07.516: Initializing PCM, step 2 of 4
22:14:08.344: Initializing PCM, step 3 of 4
22:14:08.344: Initializing PCM, step 4 of 4
22:14:08.641: PCM lock has been re-armed, attempting to unlock PCM again...

22:14:08.688: PCM seed is: $00FF
22:14:08.703: Unlock attempt 1 of 4
22:14:09.109: Unlock attempt 2 of 4
22:14:09.516: Not ready, waiting 1 second for retry...
22:14:10.781: Not ready, waiting 1 second for retry...
22:14:12.047: Not ready, waiting 1 second for retry...
22:14:13.328: Not ready, waiting 1 second for retry...
22:14:14.594: Not ready, waiting 1 second for retry...
22:14:15.859: Not ready, waiting 1 second for retry...
22:14:17.141: Not ready, waiting 1 second for retry...
22:14:18.406: Not ready, waiting 1 second for retry...
22:14:19.672: Unlock attempt 3 of 4
22:14:20.078: Unlock attempt 4 of 4
22:14:20.469: Not ready, waiting 1 second for retry...
22:14:21.750: Not ready, waiting 1 second for retry...
22:14:23.016: Not ready, waiting 1 second for retry...
22:14:24.281: Not ready, waiting 1 second for retry...
22:14:25.563: Not ready, waiting 1 second for retry...
22:14:26.828: Not ready, waiting 1 second for retry...
22:14:28.094: Not ready, waiting 1 second for retry...
22:14:29.375: Not ready, waiting 1 second for retry...
22:14:30.641: Initializing PCM...
22:14:31.484: Initializing PCM, step 1 of 4
22:14:31.484: Initializing PCM, step 2 of 4
22:14:32.313: Initializing PCM, step 3 of 4
22:14:32.328: Initializing PCM, step 4 of 4
22:14:32.609: PCM lock has been re-armed, attempting to unlock PCM again...

22:14:32.766: Initializing bootloader...
22:14:33.000: Error: Failed. Controller has returned to normal operation, please retry the operation.
22:14:33.234: Initializing bootloader, step 1 of 3
22:14:33.250: Error
22:14:33.250: Disconnecting ...
22:14:33.313: Disconnected
22:14:34.563: Done!

dc_justin

June 28th, 2008, 01:31 PM

Hey Alex,

Shoot me a PM, I'll see what I can do for you.

Justin