pcmhacking.net

couldnt you add the kernel class info select to pcminfo?

I'm pretty sure we can make it work, there might just be some details to figure out first...

1) Do P01/P59 and P04 PCMs respond to the "get OS ID" query the same way? Hopefully they are the same. If not, can we just send a P01 query and try the P04 approach if the P01 query fails?

2) How many P04 OS IDs are there? Hopefully the number is small, so we can add them all to the PcmInfo lookup just once. Hopefully we don't find ourselves discovering new OS IDs on a regular basis, because we'd have to edit PcmInfo.cs and publish a new release every time someone says "PCM Hammer won't work because it doesn't recognize [whatever OS ID]." It's not that big of a deal, but it would be nice to minimize that sort of thing.

1) ive gotten it to pull osid no problem Bcc is a no go on p04.
AVT filter configured
[01:03:32:358] Loaded start.txt from network.
[01:03:32:358] Thanks for using PCM Hammer.
[01:03:32:458] Loaded credits.html from network.
[01:03:32:522] Loaded help.html from network.
[01:03:48:018] Will save to C:\Users\vampy\Documents\testreadp04.bin
[01:03:50:039] Querying operating system of current PCM.
[01:03:50:257] TX: 6C 10 F0 3C 0A
[01:03:50:320] RX: 6C F0 10 7C 0A 00 BA 2D F7
[01:03:50:320] OSID: 12201463
[01:03:50:351] Suppressing VPW chatter.

2)Ive got a huge list of p04 osids pretty sure its a complete list might be a few obscure ones still left out there but doubt many

3) p04 doesnt do modular file system like p01/p59. its like older pcms and others of its era a single OS file per vehicle any change meant a new osid even if files are the same just for different car it got new osid. P01/p59 was test bed for newer pcms that have segment files.
Upside of single segment OS is only one checksum.
like the P01 the parameter block still stays locked during writes though unless specifically unlocked for cloning or write entire

Cool, so we don't have to change the way we get the OSID or call the PcmInfo constructor. We can put a new property on PcmInfo that indicate what sort of PCM is connected.

If we use an LS Droid kernel we can use the new property to decide which reader / writer classes to use.

If we adapt the existing kernel code, we might be able to use the existing reader and writer classes, and just create two versions of the PcmExecute function (which sends the kernel to the PCM).

Here is a complete list of every P04 OSID I could find from GM its about 1400 from 98-05 also sorted them by yr and hardware found in

Nice work! Thanks for that

i May not be a master programmer, but i can find some data.

Ive got all the gm osids for most pcms if you want me to start adding them to pcminfo.cs

Vampyre wrote:Here is a complete list of every P04 OSID I could find from GM its about 1400 from 98-05 also sorted them by yr and hardware found in

I am super grateful you have shared this list! But I have a question:

I'm unable to find my hardware number in your list, but my service number shows up. Are you using the term "hardware" to mean service number? Because there is also a hardware number associated with each service number. The hardware number from my experience will let you know if it has the IAC driver, or not (it does with the P01 and P59 PCM's). The P04 I have on my bench has a service number 09380717, and hardware number 09357440.

yeah sorry should have been more specific, the service number is usually what we use to identify p04, it changed with every little revision gm did, things like place made or different part used would change the service number so it makes it easier to dentify which you have and what yr its from

Vampyre wrote:yeah sorry should have been more specific, the service number is usually what we use to identify p04, it changed with every little revision gm did, things like place made or different part used would change the service number so it makes it easier to dentify which you have and what yr its from

Well, the list you have compiled is amazing!