PCM Hammer P01 and P59 flash tool v015

[vilefly]

ok. binary sent. Thanks a whole lot!

[Speedy]

Thanks to all who are developing PCM Hammer. I tested version 4, using a bench harness and AllPro USB interface connected to a P01 pcm serv#9354896, with o/s 9381344. On the bench harness, PCM Hammer successfully performed the following:
-Read Properties (P01 & P59)
-Read Full Contents (p01 & P59)
-Modify VIN (P01 & P59)

PCM Hammer repeatedly failed to perform the following functions on my '4896 P01, utilizing the .bin file read from the same PCM:
-Quick Comparison
-Test Write
-Write Calibration
-Write Parameters (Clone)

Results tab:
[07:52:37:617] Validating 512k file.
[07:52:37:631] Start End Result File Actual Content
[07:52:37:636] 0 7FFFD Good 5E0D 5E0D Operating system
[07:52:37:640] 8002 13FFF BAD 66C4 C23E Engine calibration
[07:52:37:645] 14002 16DFF BAD AAAA B24F Engine diagnostics.
[07:52:37:649] 16E02 1BDFF BAD 0000 2AB4 Transmission calibration
[07:52:37:653] 1BE02 1C7FF BAD 0000 D144 Transmission diagnostics
[07:52:37:657] 1C802 1E51F BAD 0067 0590 Fuel system
[07:52:37:662] 1E522 1EE9F BAD 4AFC 1DFC System
[07:52:37:668] 1EEA2 1EF9F BAD 4AFC CCFC Speedometer
[07:52:37:673] This file is corrupt. It would render your PCM unusable.

The Debug Log tab shows the same message, after attempts with all four failed functions. I also tried another .bin file (same os) from my other '4896 P01, same results. Has anyone tried these functions on the 1999-2000 '4896 P01?

I don't have a '0411 P01 at this time, for testing.

[antus]

Can you post up the bin? It looks like it has bad checksums. I know some of the early bins had bad checksums from the factory and the validate checksum feature was turned off. Your PCM may be old enough that is the case. We decided to require checksums be ok to protect people from bad files, and it would likely be possible to fix the checksums and either enable the checksum validation in the bin, or leave it turned off if it doesnt work, but at least pcmhammer will be able to verify the files are ok and allow the flash.

I also think the '4896 hardware is different to the '0411. Whether we are safe to treat it the same Im a little unsure of but I think its ok. I believe the pcms are not as hardy as the later '0411 but I dont have experience with them. Maybe someone else can describe the differences in more detail?

[brandonwh64]

Thanks to all who are developing PCM Hammer. I tested version 4, using a bench harness and AllPro USB interface connected to a P01 pcm serv#9354896, with o/s 9381344. On the bench harness, PCM Hammer successfully performed the following.....

It did the same on my 4896 ECUs as well. Read fine and created a .bin but had no XDFs to use to edit them in tuner pro. Do you have XDFs that work with the 4896? I know NSFW is not ready for OS flashing on PCM Hammer yet but on sloppy mechanics, there is a software being tested using the OBDlink bluetooth that WILL flash 4896 with 0411 OS (def tested and worked great). I wanted to try his software but I do not own the bluetooth version of the OBDlink (I have a USB version). I am going to wait until NSFW allows OS flashing and try on my two 4896 ECUs.

Here is where I uploaded both ECU bins for antus and NSFW to compare to a 0411

viewtopic.php?f=42&t=6080&start=170#p91991

[MudDuck514]

Unfortunately, the logs don't seem to be stored anywhere. I will have to try again the next time I have time to play with this deadbeat customer's vehicle. The XDF was what I meant. I will try the 0411 xdf to see what I can see.

Hi all,

I, too have one of these 4.3L PCM's.
Mine came from a 2001 GMC Jimmy 2WD.
OSID is 12202088.

Also have one from a 2001 Blazer 4x4 with OSID 12208322.
If I understand correctly, 2088 was replaced with the 8322.
Mike.

[NSFW]

At a minimum, the app will need new code to validate checksums for the 9381344 OS. If someone can find the right way to validate those checksums, we can add it.

Or maybe just skip the segment checksums are rely solely on the OS checksum. That one was valid, and if (if) the PCM isn't validating segment checksums then the app shouldn't either.

Then the question will be whether there is anything else that needs to change. Since reading works, it probably won't take much effort to make writing work.

I guess we should stop saying we support P01s, and just say that we support 411s, at least until/unless we get this figured out.

[MudDuck514]

Hi all,

Has anybody noticed that the AllPro KIT seems to have been discontinued?
OR that the USB cable seems to be unavailable at present?
http://www.obddiag.net/products.html

Mike

[antus]

I had not noticed that yet. Maybe hes out of stock or drowned in the amount of interest, or both. Just prior to the release of pcmhammer I let him know there would likely be a lot of interest. But he was reluctant to stock up incase what we were promising did not eventuate. Lets see what happens. I'll see if I can get hold of him fore more information.

[NSFW]

That's a little disconcerting. Hopefully he's just making a new batch...

[antus]

I just noticed the elm329 compatible board with the stn processor and the allpro bluetooth module we dont support are de-listed completely so it implies that they're coming back. I have reached out, i'll update the thread when he responds.