PCM Hammer 2 Preview

[2002Monaro]

added some 12730xx osids. https://github.com/PcmHammer/PcmHammer/ ... 0217901819

I tried again and now I get "The connected Undefined PCM is not supported."
Here is the debug log.

[email protected]

[antus]

It looks like in my haste I just added them to the list of OSIDs that might exist but without enough data to know what they are so that achieved nothing but getting it a little further.
I've now revisited this with a bit more of what i've learnt over the last few years and added some code to use pattern matching to try and do the right thing. There is no public list of OSIDs, but from searching around the net and comparing notes they do seem to follow a consistent pattern so the code uses the inferred logic. My workshop PC has blown up since I last used it so this is completely untested and written on another pc, but it compiles, so it must work, right? Let me know how you go. https://github.com/PcmHammer/PcmHammer/ ... 0408962868

The main logic is that first digits are 12, next is type, next is version (1 seems to have custom keys, 2 and 3 do not, but I am unsure about this, its more of a hunch). Next is always 0. Next is 0 for P01, 5 for P59, and the last one is version of the patch and changes for different underlaying factory OSID. PCMHammer uses the static values to identify a COS, the version to decide if it uses the old, mostly untested lookups or the new logic, and the 6th digit to decide if its P01 or P59. If my guesses are right, it should cover all version 2 and 3 COS now. As these are commercial COS you will need to ensure you only use this only in ways you are entitled to.

Edit: had p01 as 1m, fixed and updated actions link.

[2002Monaro]

Still getting the same error. Debug log attached

It looks like in my haste I just added them to the list of OSIDs that might exist but without enough data to know what they are so that achieved nothing but getting it a little further.
I've now revisited this with a bit more of what i've learnt over the last few years and added some code to use pattern matching to try and do the right thing. There is no public list of OSIDs, but from searching around the net and comparing notes they do seem to follow a consistent pattern so the code uses the inferred logic. My workshop PC has blown up since I last used it so this is completely untested and written on another pc, but it compiles, so it must work, right? Let me know how you go. https://github.com/PcmHammer/PcmHammer/ ... 0408962868

The main logic is that first digits are 12, next is type, next is version (1 seems to have custom keys, 2 and 3 do not, but I am unsure about this, its more of a hunch). Next is always 0. Next is 0 for P01, 5 for P59, and the last one is version of the patch and changes for different underlaying factory OSID. PCMHammer uses the static values to identify a COS, the version to decide if it uses the old, mostly untested lookups or the new logic, and the 6th digit to decide if its P01 or P59. If my guesses are right, it should cover all version 2 and 3 COS now. As these are commercial COS you will need to ensure you only use this only in ways you are entitled to.

Edit: had p01 as 1m, fixed and updated actions link.

[antus]

Ahh there was an off by one when parsing the OSID, fixed here: https://github.com/PcmHammer/PcmHammer/ ... 0449846357

[2002Monaro]

I can now confirm that I can read and write my P01 pcm that has a HPTuners custom OS tune on it.
I can write just the tune now instead of having to overwrite the OS each time when using LSDroid.
Thanks antus!

[Supercharged111]

So if I've read this correctly the Blackbox, P01, and P59 are pretty solid with this build? Looks like at least one person did a BB in vehicle (those have almost nothing on the network)?

[antus]

use the one from github actions above if you can.

[Supercharged111]

That was my intent, it's just that this is a beta/development version as it sits. But it looked like the 3 I'm interested in seemed pretty stable?

[antus]

pcmhammer 2 and newer are all alpha (not yet beta). But the newer you go, the more stable they are. Except I need to stop adding new platforms and put an official release. That is why I am saying avoid P05 at this stage. Other than that its got more small fixes than any other 2.x. If you want the most stable go back to the prior gen. Black box never had any problems, though. It just worked. Must be because its older and more simple.

[xetura]

Successful flash on a P04 for me. 2001 Buick Park Avenue Ultra pcm. I found a 2000 Pontiac Grand Prix bin, edited for my swap and got it flashed onto the pcm. Everything seems like it's working as intended. I just need to finish my swap harness before I can test fire it to 100% confirm. Thanks for all your hard work on this. Very much appreciated.