pcmhacking.net

I've spent the past few weeks trying to find the maps for the p10, p12, and p12b PCMs, and I am happy to report that I believe I have found them. I have attached a zip file that contains the bins, bins broken down by segment, whole bin maps, and maps broken down by segment for each operating system for all three PCMs. The maps are just the raw maps. I do not know how to translate into data pids, dtcs, calibration etc. I need help with that part. All maps are saved in both .csv and .json formats. Hopefully I did not miss anything. I did everything I could to keep it all neat and organized. double check me and see how well I did.

darkman5001 wrote:I've spent the past few weeks trying to find the maps for the p10, p12, and p12b PCMs, and I am happy to report that I believe I have found them. I have attached a zip file that contains the bins, bins broken down by segment, whole bin maps, and maps broken down by segment for each operating system for all three PCMs. The maps are just the raw maps. I do not know how to translate into data pids, dtcs, calibration etc. I need help with that part. All maps are saved in both .csv and .json formats. Hopefully I did not miss anything. I did everything I could to keep it all neat and organized. double check me and see how well I did.

I went ahead and took a look at the P10 12587430 OS that you have posted and manually built the tables from the information you has in the CSV file. While I was there I also defined a few parameters that were easy to find. The parameter name are laid out in the following way:

14922 D2004 - Trans Abuse Mode Torque Reduction vs. RPM (15400)

- 14922 is the HEX address
- D2004 is the EFI Live number
- Trans Abuse Mode Torque Reduction vs. RPM is the parameter name
- (15200) is the HPT number

Not all the parameters have the EFI and HPT numbers, but they will all have the HEX address. There are several that I could not figure out, so hopefully this could be a good starting point for others to help and contribute.

EDIT 6/13/22: Defined several spark table.

Thanks Phoenix. What software did you use to set up this .xdf? I hope others will chime in to help. I am trying to learn but not an easy task for me.

darkman5001 wrote:Thanks Phoenix. What software did you use to set up this .xdf? I hope others will chime in to help. I am trying to learn but not an easy task for me.

I used Tunerpro and created the individual parameters from the information that was made available in the CSV file you posted. For other tables I had HPT open and looked for patterns where a table could be and used math that I had used on P01/P59 controllers to see if the tables would come out and make sense.

How do you look at the information and determine if they are DTCs, calibration, etc? Is there some sort of standard for this?

darkman5001 wrote:How do you look at the information and determine if they are DTCs, calibration, etc? Is there some sort of standard for this?

I've pretty much finished mapping the 12597604 OS and after looking at the HEX so many times I'm beginning to recognize patterns of what looks like a table. Also a lot of the different OS versions are very similar as parameters are added and deleted, but not really changes, so that also helps.

Staring at all that HEX is like looking at the Matrix. I give you a lot of credit for being able to do that.

Phoenix wrote:I've pretty much finished mapping the 12597604 OS

Typo ??
Did you mean 125 87 604

Gampy wrote:

Phoenix wrote:I've pretty much finished mapping the 12597604 OS

Typo ??
Did you mean 125 87 604

Yes, fat fingered that one.

Added version 1.2 where I defined several spark tables.