PCM Hammer Release 014

They go by many names, P01, P59, VPW, '0411 etc . Circa 1999 to 2006. All VPW OBD2 PCMs.
User avatar
Posts: 158
Joined: Thu Jun 07, 2018 8:15 am
Location: Fort Collins, Colorado

Re: PCM Hammer Release 014

Postby DavidBraley » Sun Jun 28, 2020 8:25 am

Hello! I hope that everyone here is safe and well during these crazy times. Both my wife and I feel super lucky to be super busy.

I was trying to read a 2004 Express Van 12586243 PCM, 1 meg AMD flash P59, this morning and I got the very same error at the end of the message that cmaje72 got. It seems to get to the very end of the read and then the error appears and there is no way to save the file. I'm using the OBDX Pro VT with a USB connection. I'm using the latest version of PCM Hammer 014. I've got good voltage, I'm on the bench reading with my bench harness. I read several other 12586243 P59's this morning with no problems at all. I've also attached the full Results and Debug Log as a .txt file to this post.

6243fail.txt
(175.88 KiB) Downloaded 3 times


So thought I would post this in the name of testing if it helps. Here is the error I get at the very end of the full read (same as cmaje72):

***********
[03:34:23:974] 0x0F0000 93% 00:14
[03:34:24:880] 0x0F1000 94% 00:13
[03:34:25:786] 0x0F2000 94% 00:12
[03:34:26:708] 0x0F3000 94% 00:11
[03:34:27:615] 0x0F4000 95% 00:11
[03:34:28:521] 0x0F5000 95% 00:10
[03:34:29:443] 0x0F6000 96% 00:09
[03:34:30:349] 0x0F7000 96% 00:08
[03:34:31:256] 0x0F8000 96% 00:07
[03:34:32:174] 0x0F9000 97% 00:06
[03:34:33:081] 0x0FA000 97% 00:05
[03:34:33:987] 0x0FB000 98% 00:04
[03:34:34:909] 0x0FC000 98% 00:03
[03:34:35:816] 0x0FD000 98% 00:02
[03:34:36:722] 0x0FE000 99% 00:01
[03:34:37:628] 0x0FF000 99% 00:00
[03:34:37:644] Read complete.
[03:34:37:660] All read-request messages succeeded on the first try. You have an excellent connection to the PCM.
[03:34:37:675] We're not sure how much retrying is normal for a read operation on a 1024kb PCM.
[03:34:37:691] Please help by sharing your results in the PCM Hammer thread at pcmhacking.net.
[03:34:37:691] Starting verification...
[03:34:37:707] Calculating CRCs from file...
[03:34:37:734] Requesting CRCs from PCM...
[03:34:37:781] Range File CRC PCM CRC Verdict Purpose
[03:34:38:844] 0F0000-0FFFFF 8D0F8F91 8D0F8F91 Same OperatingSystem
[03:34:39:902] 0E0000-0EFFFF A50F3C90 A50F3C90 Same OperatingSystem
[03:34:40:967] 0D0000-0DFFFF A50F3C90 A50F3C90 Same OperatingSystem
[03:34:42:034] 0C0000-0CFFFF A50F3C90 A50F3C90 Same OperatingSystem
[03:34:43:096] 0B0000-0BFFFF A50F3C90 A50F3C90 Same OperatingSystem
[03:34:44:174] 0A0000-0AFFFF A50F3C90 A50F3C90 Same OperatingSystem
[03:34:45:240] 090000-09FFFF 7DA5C19F 7DA5C19F Same OperatingSystem
[03:34:46:303] 080000-08FFFF CDDEAE4C CDDEAE4C Same OperatingSystem
[03:34:47:358] 070000-07FFFF D006BDC7 D006BDC7 Same OperatingSystem
[03:34:48:431] 060000-06FFFF D2B04EC0 D2B04EC0 Same OperatingSystem
[03:34:49:503] 050000-05FFFF 36511E94 36511E94 Same OperatingSystem
[03:34:50:582] 040000-04FFFF F6B0E81A F6B0E81A Same OperatingSystem
[03:34:51:643] 030000-03FFFF A97E3395 A97E3395 Same OperatingSystem
[03:34:52:716] 020000-02FFFF EE1B7BAD EE1B7BAD Same OperatingSystem
[03:34:53:774] 010000-01FFFF 67866EC2 67866EC2 Same Calibration
[03:34:54:364] 008000-00FFFF D8AFC602 D8AFC602 Same Calibration
[03:34:54:542] 006000-007FFF 85B5BB36 85B5BB36 Same Parameter
[03:34:54:730] 004000-005FFF 5081A424 5081A424 Same Parameter
[03:34:55:042] 000000-003FFF AE42598F AE42598F Same Boot
[03:34:55:058] The contents of the file match the contents of the PCM.
[03:34:55:089] Clearing trouble codes.
[03:34:56:151] Read failed: System.NullReferenceException: Object reference not set to an instance of an object.
at PcmHacking.OBDXProDevice.<FindResponseFromTool>d__56.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
at PcmHacking.OBDXProDevice.<SetVpwSpeedInternal>d__71.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
at PcmHacking.Device.<SetVpwSpeed>d__37.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
at PcmHacking.Vehicle.<ExitKernel>d__34.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.GetResult()
at PcmHacking.Vehicle.<Cleanup>d__33.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.GetResult()
at PcmHacking.CKernelReader.<ReadContents>d__4.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
at PcmHacking.MainForm.<readFullContents_BackgroundThread>d__36.MoveNext() in C:\GitHub\PcmHacks\Apps\PcmHammer\MainForm.cs:line 839
-David

Horsepower determines the speed you hit the wall. Torque determines the size of the hole you make.

User avatar
Posts: 575
Joined: Sat Dec 15, 2018 7:38 am

Re: PCM Hammer Release 014

Postby Gampy » Sun Jun 28, 2020 8:28 am

@In-Tech, Does this help: EFI Live tun collection.
I'm not angry, I'm a blatant, driven, passionate individual that is extremely intense!

User avatar
Posts: 158
Joined: Thu Jun 07, 2018 8:15 am
Location: Fort Collins, Colorado

Re: PCM Hammer Release 014

Postby DavidBraley » Sun Jun 28, 2020 11:27 am

Well, I think I might have found my problem from my last post about the P59 PCM that would fail at the very end of a full read.

I decided to try and read it again. Twice to make sure. Both times is read perfectly. So what was different? This time, the USB cable that runs between the OBDX Pro VT and the computer was NOT lying across the top of my bench top power supply. My bench top power supply is a crusty old analog thing that kind of makes a fair amount of noise. So I'm guessing that the USB cable was picking up some unwanted signal. I need to find a better bench top power supply...
-David

Horsepower determines the speed you hit the wall. Torque determines the size of the hole you make.

Posts: 173
Joined: Mon Mar 09, 2020 4:35 pm

Re: PCM Hammer Release 014

Postby In-Tech » Sun Jun 28, 2020 1:21 pm

Gampy wrote:@In-Tech, Does this help: EFI Live tun collection.

Hiya Gampy,
I don't have the ability to convert those efilive files to .bin files. Thanks though.

User avatar
Posts: 575
Joined: Sat Dec 15, 2018 7:38 am

Re: PCM Hammer Release 014

Postby Gampy » Sun Jun 28, 2020 2:59 pm

@In-Tech,

There are a couple bin's in the Stock LB7 Duramax collection ...
15166853-Duramax-LB7-2002-Auto.bin
15189044-Duramax-LB7-2004-Auto.bin

They are 512k files, no clue if they are what you're looking for or not ...
I'm not angry, I'm a blatant, driven, passionate individual that is extremely intense!

Previous

Return to GM LS1 512Kbyte and 1Mbyte

Who is online

Users browsing this forum: No registered users and 4 guests