pcmhacking.net

Gatecrasher wrote:Is the label still legible on the spare PCM? I might be able to tell you which OS it had if you can post the numbers from the label.

The contents of both new and old labels would be ideal.

Here's the pics of labels, 1st one is junkyard PCM
2nd one is the stock PCM.

Mine has exactly the same numbers except for the broadcast code, mine is YDZY, mine is from a 2004 Chevrolet TrailBlazer 4dr 4WD EXT LS, mine has OsID 125 84 594

Anyone know what the two unlabeled numbers are, I'm suspect one is hardware, the other is calibration, which ones which ??

-Enjoy

It seems I'm not as smart as I thought I was.

The top number is hardware. The bottom right number is the end model part number. That number is the combination of the hardware, OS, and all the calibrations present at the time the part was manufactured. Those end item parts are available for older controllers like the P04 that used a single blob of code. Looks like they abandoned it when they went to segmented calibrations. I can't find a cross reference for it.

It probably wouldn't matter anyway if the module had been programmed between the time it was manufactured and now. The label would be out of date. It'd be better to pull the current calibration info from diagnostics.

I'm not completely useless though. The part number that Vetteyog mentioned, 12588430, is an engine operation calibration. Not an OS. That's why you can't find an XDF for it.

Gampy's OS is the first one available for this hardware. Here's the flow of OSes from oldest to newest:

12584594
>12587608
>>12589825
>>>12590965
>>>>12597031

My half assed guess is your new and old controllers had different versions of software on them. You inadvertently mismatched something, like Antus said.

I'd start over with the working module. Use diagnostics or something like Universal Patcher to find out which OS is on it, and see if you can find an XDF for it. Then do a full clone onto the donor part and make your changes from there.

Gatecrasher wrote:It seems I'm not as smart as I thought I was.

The top number is hardware. The bottom right number is the end model part number. That number is the combination of the hardware, OS, and all the calibrations present at the time the part was manufactured. Those end item parts are available for older controllers like the P04 that used a single blob of code. Looks like they abandoned it when they went to segmented calibrations. I can't find a cross reference for it.

It probably wouldn't matter anyway if the module had been programmed between the time it was manufactured and now. The label would be out of date. It'd be better to pull the current calibration info from diagnostics.

I'm not completely useless though. The part number that Vetteyog mentioned, 12588430, is an engine operation calibration. Not an OS. That's why you can't find an XDF for it.

Gampy's OS is the first one available for this hardware. Here's the flow of OSes from oldest to newest:

12584594
>12587608
>>12589825
>>>12590965
>>>>12597031

My half assed guess is your new and old controllers had different versions of software on them. You inadvertently mismatched something, like Antus said.

I'd start over with the working module. Use diagnostics or something like Universal Patcher to find out which OS is on it, and see if you can find an XDF for it. Then do a full clone onto the donor part and make your changes from there.

Is there a 12587608 OS out there? I think that is the one on the stock PCM.

Yeah. It's the 2nd one in the list I posted.

12584594
>12587608 <---
>>12589825
>>>12590965
>>>>12597031

Gatecrasher wrote:Yeah. It's the 2nd one in the list I posted.

12584594
>12587608 <---
>>12589825
>>>12590965
>>>>12597031

I saw that, I was wondering where I could download it from? I've looked in all usual places and haven't found one.

Can't help you there. You'd have to hope someone has a matching PCM they can dump.

You know, I wonder what it would take to build a portable PCM dumper? Maybe power it off a jumpstart pack. It'd be interesting wandering around Pick N Pull dumping old PCMs.

You can get a low end windows tablet from < $100 on aliexpress that'd do it. But then again a full size laptop in a carry bag wouldnt be heavier than a regular tool kit.

My supplier allows me to come read any PCM any time I want, even supplies me a workbench with A/C ...
At the time I only had the Sparkfun STN1110 at 1k, a 1m read takes just over 20 minutes, so I didn't do a lot of reading, it's also a two hour round trip so a day gets eaten up quick.

I don't have the energy to do it anymore.

-Enjoy

Gatecrasher wrote:Can't help you there. You'd have to hope someone has a matching PCM they can dump.

You know, I wonder what it would take to build a portable PCM dumper? Maybe power it off a jumpstart pack. It'd be interesting wandering around Pick N Pull dumping old PCMs.

THIS is exactly what I am wanting to do.

I have an OLD camp power source that uses a 12v, 7AH Sealed Lead Acid Battery.
Has 2x cigarette lighter sockets on the front (one is voltage selectable).
A lamp on the back with a switch to turn it on/off, and a switch on the front that controls all power.
Thinking about mounting an OBD2 socket ton the back, along with a 5-pin "Microphone socket" that will have a mating plug that has the PCM plug connected to it.
Will use the light switch for IGN.
Should allow me to power up a PCM at the JY!
I have a 13" laptop (8th gen Intel Core i3) that has Win10 on it so should be able to run PCMHammer just fine.

Mike