pcmhacking.net

Here is what it looks like in the selector. As for it stable currently, I guess will have to see if any adjustment can be made to accommodate the max buffer size that they state the device is capable of doing and test it.

Awesome, they put their name in it ... That would make it fairly easy if one wanted to do a tool specific configuration, it is not on my list of things to do but I guess that also depends on how bored I get setting here!

It's not hard to make that simple change and test, takes 5 minutes maybe, so we'll know shortly after mine gets here, unless you want to do it, then go for it. FMI ask ...

-Enjoy

I would go ahead and do some changes and test as well as possibly a specific tool config. However I am still finding my way through the code. Getting there with it but not quite to that point yet. If I was, would definitely look into getting a start on it for testing and all.

Id say they are allocated a buffer per protocol, rather then a global shared one which is why they have varying buffer sizes. It does require thinking outside of the box.

Looks like it should be able to handle a couple hundred bytes at a time at 1x. Itll be slow but should get through it eventually.

@Tazzi I am still looking thru and learning the pcmhammer code to find where I can adjust what is needed. Gampy will likely get to it before I can find where the changes should be made in order to test.

Right here: J2534Device.cs

Change those to 238 ... Then if it works, try bumping it up from there until it crashes!

-Enjoy

Would the buffers be inherent to the chip, or just the firmware?

The chip does impose hard limits, but its mostly firmware depending on how its designed to work with what the hardware makes available and how it uses or reuses ram. Im very interested to see how this goes.

Gampy, that link to modify the code on github seems like the key to pandora's box. I played around there, but having no experience with github or software development I'll wait until you get your godiag and test with hammer. I assume there's no folder on my PC that would permit changes to the buffer limits for hammer?

So far not having much luck with different buffer size adjustments. If too low pcmhammer will not even pull the OSID and of course fails. Seems so far that I can not go below 192 or else it does not get far at all. 192 it at least goes thru and does state 0% of kernel upload but then times out after multiple tries and fails. I have some logs I am going to post shortly. I was having to use a spare pwr supply that may be sketchy. As Gampy had stated with bad power I am beating my head on wall. So I just got another supply I will try, if that doesnt change things I will set up at test with a battery.