Page 5 of 5
Re: P01 and P59 Operating Systems
Posted: Wed Nov 27, 2019 12:50 pm
by PeterTremonti
DavidBraley wrote:
Made a mistake in my post. Corrected below:
The first P59 pcm you call the "Junkyardspare.bin" is a drive by wire from a (I posted this earlier):
2005 GMC Yukon XL 4dr 1500 SLT
VIN: 3GKEC16Z35G26***
Engine L59 5.3LGas V8
Trans: M30 4L60E
The second P59 pcm you have (2003 Suburban) is a drive by wire, so no IAC hardware needed to convert to drive by cable.
For a drive by cable P59, you want to look for a hardware (not service) numbers: 12575502, 12570558, 12583659, and 12589161.
If it also helps, they made drive by cable P59's up to 2007.
This is excellent info! I have no interest in DBC and these PCMs seem like they will all work for the various vehicles we have at work. Everybody i work with has a gm with a 5.3 in it between 2001 and 2005 and they're all DBW.
If it is possible to clone an original bin between all of these hardware numbers we're in good shape if anybody has issues. I'll be reading all the PCMs i can ger my hands on by the end of next week hopefully. I need to practice looking at these files.
Re: P01 and P59 Operating Systems
Posted: Mon Dec 02, 2019 12:03 pm
by Gampy
2004 GMC Savana Cargo Van 1500, 4.3L (LU3), Automatic (M30) (4L60E)
Service Number: 12586243
Hardware Number: 12583659
Operating System Number (OsID): 12585950
Flash Chip: AMD Am29F800B 1Mbyte (00012258)
[edit] Changed to Windows line endings.
Re: P01 and P59 Operating Systems
Posted: Mon Dec 02, 2019 12:10 pm
by DavidBraley
Gampy wrote:Flash Chip: AMD Am29F800B 1Mbyte (00012258)
Gampy,
I know how to get the chip id number using the BDM, but how do you get it using PCM Hammer?
Re: P01 and P59 Operating Systems
Posted: Mon Dec 02, 2019 12:29 pm
by Gampy
I don't use PcmHammer for that, however PcmHammer includes it in the logs from certain actions like Quick Compare, there are others unfortunately CRS has me at the moment!
Re: P01 and P59 Operating Systems
Posted: Tue Dec 03, 2019 6:02 pm
by NSFW
For release 8, it only prints the chip ID during comparisons and writes, and at the very end of a read (because it does a comparison when it finishes reading), but the next release will print it at the start of a read as well.