PCM Hammer release 011

They go by many names, P01, P59, VPW, '0411 etc . Circa 1999 to 2006. All VPW OBD2 PCMs.
User avatar
Posts: 30
Joined: Fri Dec 27, 2019 2:28 am

Re: PCM Hammer release 011

Postby Jim Blackwood » Sat Feb 01, 2020 7:03 am

I must be missing something. Below is a debug log of my last attempt. I verified that all the connections in my bench harness were good, and I was able to use OBDLinkLX with LS Droid to read each of my 3 PCMs and save the read files. So then I managed to have PCH recognize the OBDLink on bluetooth by switching to COM4 and did a successful write. This makes me very happy! I think I will overwrite one of the other PCMs as well while it is working.

So this log is AllPro USB on COM3. I don't have any idea why it isn't working, it seems to me like it should but my guess is that there is just something that isn't set right but I'm out of my depth on that.

Jim


[12:44:26:691] C:\Users\Jim\Documents\MG\First Files\MGBAGHN5UB240478G.bin
[12:44:36:799] Validating 512k file.
[12:44:36:821] Start End Stored Needed Verdict Segment Name
[12:44:36:836] 00000 7FFFD 3D37 3D37 Good Operating system
[12:44:36:852] 08002 13FFF 365D 365D Good Engine calibration
[12:44:36:868] 14002 16DFF FD97 FD97 Good Engine diagnostics.
[12:44:36:883] 16E02 1BDFF 5D3A 5D3A Good Transmission calibration
[12:44:36:899] 1BE02 1C7FF 7BF9 7BF9 Good Transmission diagnostics
[12:44:36:921] 1C802 1E51F 6D0C 6D0C Good Fuel system
[12:44:36:952] 1E522 1EE9F DBD4 DBD4 Good System
[12:44:36:984] 1EEA2 1EF9F BD17 BD17 Good Speedometer
[12:44:37:015] Requesting operating system ID...
[12:44:37:037] TX: 3C0A
[12:44:37:438] Timeout during receive.
[12:44:37:453] Sending 'test device present' notification.
[12:44:37:485] TX: AT SH 8C FE F0
[12:44:37:522] Set header response: OK
[12:44:37:554] TX: 3F
[12:44:37:956] Timeout during receive.
[12:44:37:972] Sending 'test device present' notification.
[12:44:38:003] TX: 3F
[12:44:38:391] Timeout during receive.
[12:44:38:407] Sending 'test device present' notification.
[12:44:38:445] TX: 3F
[12:44:38:831] Timeout during receive.
[12:44:38:853] Sending 'test device present' notification.
[12:44:38:884] TX: 3F
[12:44:39:269] Timeout during receive.
[12:44:39:285] Receive timed out. Attempt #5, Timeout #5.
[12:44:39:316] TX: AT SH 6C 10 F0
[12:44:39:354] Set header response: OK
[12:44:39:385] TX: 3C0A
[12:44:39:779] Timeout during receive.
[12:44:39:810] Sending 'test device present' notification.
[12:44:39:842] TX: AT SH 8C FE F0
[12:44:39:879] Set header response: OK
[12:44:39:911] TX: 3F
[12:44:40:285] Timeout during receive.
[12:44:40:300] Sending 'test device present' notification.
[12:44:40:331] TX: 3F
[12:44:40:717] Timeout during receive.
[12:44:40:733] Sending 'test device present' notification.
[12:44:40:771] TX: 3F
[12:44:41:149] Timeout during receive.
[12:44:41:171] Sending 'test device present' notification.
[12:44:41:187] TX: 3F
[12:44:41:589] Timeout during receive.
[12:44:41:604] Receive timed out. Attempt #5, Timeout #5.
[12:44:41:620] Operating system request failed, checking for a live kernel...
[12:44:41:636] TX: AT SH 6C 10 F0
[12:44:41:651] Set header response: OK
[12:44:41:667] TX: 3D00
[12:44:42:031] Timeout during receive.
[12:44:42:146] TX: 3D00
[12:44:42:500] Timeout during receive.
[12:44:42:616] TX: 3D00
[12:44:42:979] Timeout during receive.
[12:44:43:101] TX: 3D00
[12:44:43:460] Timeout during receive.
[12:44:43:576] TX: 3D00
[12:44:43:930] Timeout during receive.
[12:44:44:046] Checking for recovery mode...
[12:44:44:046] TX: 62
[12:44:44:416] Timeout during receive.
[12:44:44:416] TX: 62
[12:44:44:779] Timeout during receive.
[12:44:44:779] TX: 62
[12:44:45:149] Timeout during receive.
[12:44:45:149] TX: 62
[12:44:45:519] Timeout during receive.
[12:44:45:519] TX: 62
[12:44:45:882] Timeout during receive.
[12:44:45:882] TX: 62
[12:44:46:252] Timeout during receive.
[12:44:46:252] TX: 62
[12:44:46:621] Timeout during receive.
[12:44:46:621] TX: 62
[12:44:46:985] Timeout during receive.
[12:44:46:985] TX: 62
[12:44:47:354] Timeout during receive.
[12:44:47:354] TX: 62
[12:44:47:715] Timeout during receive.
[12:44:47:721] PCM is not responding to OSID, kernel version, or recovery mode checks.
[12:44:47:721] Unlock may not work, but we'll try...
[12:44:47:737] Suppressing VPW chatter.
[12:44:47:753] TX: AT SH 6C FE F0
[12:44:47:768] Set header response: OK
[12:44:47:784] TX: 2800
[12:44:47:837] Sending 'test device present' notification.
[12:44:47:853] TX: AT SH 8C FE F0
[12:44:47:869] Set header response: OK
[12:44:47:884] TX: 3F
[12:44:47:938] Sending seed request.
[12:44:47:953] TX: AT SH 6C 10 F0
[12:44:47:969] Set header response: OK
[12:44:47:985] TX: 2701
[12:44:48:347] Timeout during receive.
[12:44:48:347] No response to seed request.
[12:44:48:363] Unlock was not successful.

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

Re: PCM Hammer release 011

Postby DavidBraley » Sat Feb 01, 2020 7:44 am

Jim,

Your posts about this have been helpful to me. I have an AllPro USB (the only interface device I own at the moment) and I'm having the same kinds of issues. I'm thinking now that I must have buggered it up somehow. Hope that Pete's interface will be released soon! I might still cough up the $300+ for an AVT-852 as well. I read it's a solid device.
-David

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

Posts: 106
Joined: Mon Feb 11, 2019 12:48 pm
Location: DFW, Texas

Re: PCM Hammer release 011

Postby jlvaldez » Sat Feb 01, 2020 8:02 am

I'll throw out that i'm using a VX Diag nano that can be picked up for ~$100 on amazon. It's a J2534 device and you can use it for tech2win (tech 2 support on your computer). it support 4x VPW as well.

Site Admin
User avatar
Posts: 6281
Joined: Sat Feb 28, 2009 8:34 pm

Re: PCM Hammer release 011

Postby antus » Sat Feb 01, 2020 1:50 pm

Jim, TX means transmit, RX means receive. There is nothing coming back from the car. Test your connection any other way you can to narrow down if the problem is with the interface or the vehicle wiring / power
Have you read the FAQ? For lots of information and links to significant threads see here: viewtopic.php?f=7&t=1396

User avatar
Posts: 30
Joined: Fri Dec 27, 2019 2:28 am

Re: PCM Hammer release 011

Postby Jim Blackwood » Sun Feb 02, 2020 6:14 am

Antus: Yep, I see that. No return.
Well, it works with the OBDLink LX so the bench harness is OK. Did a full write on two PCMs, so that works.
The tests of the AllPro all come back good so that works.
What's left, the wires between the board and the OBD connector in the AllPro? OK I could buy that but Scott said he tested it on his system and it worked fine.
Something doesn't compute.

Is there anything that could cause a breakdown in the bridge even if the hardware is testing good? Apparently so. I'm just guessing it has to be some detail in the configuration that is not right. I won't be able to dig into the details of the comm protocol to fix that. I'm doing well to recognize that it even exists.

Jim

User avatar
Posts: 2218
Joined: Thu May 17, 2012 8:53 pm
Location: WA

Re: PCM Hammer release 011

Postby Tazzi » Sun Feb 02, 2020 12:20 pm

Jim Blackwood wrote:Antus: Yep, I see that. No return.
Well, it works with the OBDLink LX so the bench harness is OK. Did a full write on two PCMs, so that works.
The tests of the AllPro all come back good so that works.
What's left, the wires between the board and the OBD connector in the AllPro? OK I could buy that but Scott said he tested it on his system and it worked fine.
Something doesn't compute.

Is there anything that could cause a breakdown in the bridge even if the hardware is testing good? Apparently so. I'm just guessing it has to be some detail in the configuration that is not right. I won't be able to dig into the details of the comm protocol to fix that. I'm doing well to recognize that it even exists.

Jim


Must make sure you have the following connected at the OBD connector:
Pin 2 - VPW
Pin 4/5 - Ground
Pin 16 - 16volts

If the Allpros 8v regulator has failed, then you will not be able to write information to the bus.

You can confirm this by using the LX, open up a terminal and do:
ATSP2
ATMA

This will set the protocol to VPW, and then will begin monitoring all data and display on screen

Then attempt to use the allpro with pcmhammer and see what happens. This is what I was doing when testing with the obdxpro to verify frames being sent/received with multiple devices.
Image

User avatar
Posts: 30
Joined: Fri Dec 27, 2019 2:28 am

Re: PCM Hammer release 011

Postby Jim Blackwood » Tue Feb 04, 2020 5:17 am

More info for the operation of PC Hammer: Bench supply requirements.
I use a small 12v wet cell and a 15v power brick. With the battery fully charged and the brick either on or off communication with the PCM using OBDL-LX and PCH works reliably.
Having left the bench harness connected and the power brick unplugged, the battery ran down to the point where the power-on led was dim. Plugging the brick back in, the voltage came back up to 14.7vdc. This configuration did not supply adequately stable power to be able to communicate with the PCM. After the battery was recharged comms were once again stable.

Conclusion: the PCM and/or the OBDL-LX is susceptible to power supply ripple and cannot be expected to maintain stable communications without some level of filtering.

You're welcome,

Jim

User avatar
Posts: 30
Joined: Fri Dec 27, 2019 2:28 am

Re: PCM Hammer release 011

Postby Jim Blackwood » Wed Feb 05, 2020 7:43 am

Is there such a thing as a stock xdf for the 12202088 OS?
It seems like all the ones I'm seeing are derived from Dimented24x7's xdf which I'll grant you is pretty great, but am I not right in saying that he deleted all the flags except for an even dozen?

I'd like to use the DTCs for troubleshooting but without the flags I don't see just how that would be possible. So is there a relatively simple way to put the flags back that a non-programmer like myself might be able to do?

Jim

Posts: 699
Joined: Sat Dec 15, 2018 7:38 am

Re: PCM Hammer release 011

Postby Gampy » Mon Feb 10, 2020 10:16 pm

Mr. Jim Blackwood,

If you are interested in trying a custom test build with your All-Pro, please PM me.

I had pretty much given up on the AllPro until a bit over a week ago when I woke from a morphine induced stupor with a thought, obviously unable to do anything with it I had a nurse take a note to remind me.
The reminder worked, I tried something and got this result,
[06:29:41:065] All write-request messages succeeded on the first try. You have an excellent connection to the PCM.
Obviously the wording is a bit confusing considering it was reading.

It's not a viable solution, but it may just possibly lead to one ...
Temporary is a permanent problem!

Posts: 24
Joined: Thu Feb 07, 2013 1:49 pm

Re: PCM Hammer release 011

Postby roughneck427 » Thu Feb 13, 2020 3:40 am

Jim Blackwood wrote:Is there such a thing as a stock xdf for the 12202088 OS?
It seems like all the ones I'm seeing are derived from Dimented24x7's xdf which I'll grant you is pretty great, but am I not right in saying that he deleted all the flags except for an even dozen?

I'd like to use the DTCs for troubleshooting but without the flags I don't see just how that would be possible. So is there a relatively simple way to put the flags back that a non-programmer like myself might be able to do?

Jim


this is the structure for E92E92A which should be same or close


DTC mask
no error=00
mil on 1 =01
mil on 2 =02
no mil=03
no error flag checked=04
mil on 1 flag checked= 05
mil on 2 flag checked = 06
no mil flag checked=07

PreviousNext

Return to GM LS1 512Kbyte and 1Mbyte

Who is online

Users browsing this forum: Stokes1114 and 1 guest