PCM Hammer Release 014

They go by many names, P01, P59, VPW, '0411 etc . Circa 1999 to 2006. All VPW OBD2 PCMs.
Posts: 17
Joined: Thu Jan 19, 2017 11:09 pm

Re: PCM Hammer Release 014

Postby Stokes1114 » Thu Apr 23, 2020 8:28 am

So I swapped the"new" 0411 and first did the write OS,cal and boot. They were different OS. Total time was 3min 32 sec. Then I did the parameters and it blew by at 9.32 seconds. I can get screen shots if needed but everything went on first try in my truck with the Xpro. Just what I wanted so I can make changes, but always have my original PCM stored away. Thanks fellas

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

Re: PCM Hammer Release 014

Postby Tazzi » Thu Apr 23, 2020 12:44 pm

Stokes1114 wrote:NSFW, or anyone else.. Have you tried in vehicle flash with the xpro with ver 14 yet?


I havent personally in car but I had an entire car that runs on VPW setup on my bench and it worked great.
Image

Posts: 17
Joined: Thu Jan 19, 2017 11:09 pm

Re: PCM Hammer Release 014

Postby Stokes1114 » Thu Apr 23, 2020 12:58 pm

Tazzi wrote:I havent personally in car but I had an entire car that runs on VPW setup on my bench and it worked great.


Ya it worked perfectly! Crazy how fast it is. I'm going through my bin and making some adjustments tonight, then I'll reflash it tomorrow. You guys really kicked ass on PCM hammer, and your Xpro is awesome Tazzi!

User avatar
Posts: 437
Joined: Fri Feb 02, 2018 3:13 pm

Re: PCM Hammer Release 014

Postby NSFW » Thu Apr 23, 2020 2:56 pm

Sweet, I love hearing success stories. :)

No worries about the screenshots, those are really only needed when things go wrong.
Please don't PM me with technical questions - start a thread instead, and send me a link to it. That way I can answer in public, and help other people who have the same question. Thanks!

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

Re: PCM Hammer Release 014

Postby Jim Blackwood » Mon Apr 27, 2020 2:41 am

Tried connecting PCMLogger using the OBDLinkLX with the results shown in the Debug log below:

Jim
Attachments
PCMLoggerConnectFailOBDLinkLX.jpg

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

Re: PCM Hammer Release 014

Postby Gampy » Mon Apr 27, 2020 3:00 am

Jim,

A Screen shot does not give the full log, we need the full Text of the log.

Please do this,
. Select the Debug tab
. Hover your mouse over the Text of the log
Select: Right Click
Select: Select All
. Hover your mouse over the Selected Text of the log
Select: Right Click
Select: Copy

Open Notepad
Select: Edit
Select: Paste
Select: File
Select: Save As
Save and remember what and where ...

Then post that saved Text file as an attachment here.

There is a simpler method in the works, some other things need to happen first.

Thank you.
Temporary is a permanent problem!

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

Re: PCM Hammer Release 014

Postby Jim Blackwood » Tue Apr 28, 2020 1:33 am

Unfortunately there is no more. However in an attempt to get you more to work with I have tried connecting on com5 after a duplicate attempt to connect on com4. This gives a different result that might be helpful. Again it is a screen shot and I won't know if it will be visible enough to work with until I post it but I'm going to try. If you can see it, look at the bottom quarter of the log below "ELM Initialization starting" and pay attention to the elapsed time numbers and there you will see that it took between 200 and 300 ms between each transmission (It seemed like a lot longer than that). The log is grayed out because eventually it timed out and posted "not responding" at which point I could not copy anything and a screen shot was the only other option.

As near as I can figure, on comm4 it hangs at one point in the log and never completes the process so there is never any device selected. On comm5 it never makes the connection at all and times out on each transmission. And that's at the very limit of my knowledge and abilities regarding terminal comms so that's about all the help I know how to give. I hope it was. Helpful I mean.

Jim
Attachments
PCMLoggerConnectFailOBDLinkLX2.jpg

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

Re: PCM Hammer Release 014

Postby Gampy » Tue Apr 28, 2020 3:31 am

Looks like port issues.

I cannot read the image, my eyes gave up years ago, however I do recognize what it looks like so I'll assume it states something like:
Unauthorized Access Exception: Access to the port 'COM?' is denied.
It is what it is, either the tool is not found on that port, or that port is broke, including not having the permissions to use it!

What port is your Tool on ??

If PcmHammer (or PcmLogger) has remembered a port that is now gone or broken, and it's crashing PcmHammer (or PcmLogger) on startup (It shouldn't), you can delete the file:
PcmHammer.exe.Config
or
PcmLogger.exe.Config
in the PcmHammer folder.

[edit]
Awe, but it does crash once in awhile ... See following post.
[/edit]

If you have damaged or unmanaged Windows ports you can clean them with the following steps,

Find the "Command Prompt" shortcut and Right-Click on it,
Select: Run as administrator
At the command prompt type (or copy paste) the following two commands,
set DEVMGR_SHOW_NONPRESENT_DEVICES=1
devmgmt.msc
When Device Manager opens,
Select: View
Select: Show hidden devices
In the Device Manager Tree view,
Expand: Ports (COM & LPT)
On any ports you want to remove,
Select: Right Click
Select: Uninstall
In the Confirm Device Uninstall dialog,
Un-Check: Delete the driver software for this device
Select: Ok

The next time you plug the device in, it will re-install.

You can close the Command Prompt anytime after Device Manager opens ...

I personally Uninstall them all and just allow them to reinstall in the specific order I plug the devices back in ... That way I get what I want on the ports I want them on.
Temporary is a permanent problem!

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

Re: PCM Hammer Release 014

Postby Gampy » Tue Apr 28, 2020 6:38 am

Ok, After trying several times I did finally get it to crash and is reproducible in v14.

And when I say crash, I mean the process dies!

If you open PcmHammer and the Port is valid but the tool is not there it will crash ... But not always!

This can be replicated on a desktop that has a RS232 port that has no device.
Select the RS232 port (Typically COM1)
Close PcmHammer
Open PcmHammer
Wait for it to enable the Select Device button
If it has not already crashed ...
Select: Select Device
Change the Serial Port
Change the Device type (select the same device or not)
If it hasn't crashed yet, it's likely going to survive ...
Select: Ok
Wash and Repeat ...

It is random ...
Temporary is a permanent problem!

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

Re: PCM Hammer Release 014

Postby Tazzi » Tue Apr 28, 2020 11:20 am

Its a bluetooth thing.

Same thing can occur using the OBDX Pro VT. You need to ensure the device is connected to the bluetooth first before trying to connect with software otherwise windows will hang, waiting for a valid comport connection to occur (As the bluetooth is not actually properly connected).
Image

PreviousNext

Return to GM LS1 512Kbyte and 1Mbyte

Who is online

Users browsing this forum: Google [Bot] and 1 guest