Free LS1 Tuning Software (all you need is TunerPro)

[LRT]

....

[LRT]

....

[LRT]

....

[LRT]

....

[windsma]

Thank You!

[brandonwh64]

Thank you!!! Also would it be possible to get these XDFs complied into a ZIP file?

*Edit* Would these XDFs work with a 4896 ECU? Its pretty much the same as a 0411

[PeteS]

Thank you for all the work you've put into these, I know how much time they take to create.

I can't wait to see where this leads us now that open source flashing is now possible.

[PeteS]

Thank you!!! Also would it be possible to get these XDFs complied into a ZIP file?

*Edit* Would these XDFs work with a 4896 ECU? Its pretty much the same as a 0411

The 512K Xdf's are OS dependent. If you have a supported OS on an 0896 there is no reason it won't work. It is a 0411 for all purposes.

[antus]

Nice work on the XDFs but it'd be nice if you had contacted me before you included versions of my checksum plugins, and provided creditation for my work. Also, you should NOT load both checksums. The 1 Mbyte should be an update to the 512kb, and carries the same internal GUID as the earlier version which needs to be unique. In fact, I think tunerpro will detect this and ignore the older one and use the 1 Mbyte plugin for all. Also grrr at whoever patched out my email address from the DLLs! :( Im not saying its you but it definately has happened. Thats nasty. I'd like to clean that up.

For the checksum plugins to work you'll need the VC2010 redist package installed on your PC else it'll fail to load, and then it wont update the checksums which will cause problems flashing. Also note that you only need the plugin for the OS Segments, and unless you have code patches (I dont think anyone has developed any yet) you can and should use the built in tunerpro checksum calculations instead as that will remove the external dependency on the checksum plugin and in turn the VC2010 plugins so that it will always work.

I'll attach my build of the 512kbyte and 1mbyte plugin. If you want to talk plugin development send me a PM.

Here is an example of checksum without a plugin for the engine calibration segment, the same applies for all segments except the OS segment:

[LRT]

....

[LRT]

....

[antus]

No, this is the first public release of the 1mbyte version, though its just a minor update. I can see that the 1mbyte dll you posted is someone elses hack of my dll as there is an extra space where someone typed over the 512kbit string.



This plug-in provides a way to calculate checksums for LS1 512k bin files.
This plug-in provides a way to calculate checksums for LS1 1Mb bin files.


The source code for the guts of it is published here but I cant post in full because of the restrictive license on the tunerpro SDK.
https://pcmhacking.net/forums/viewtopic.php?f=42&t=3845#p85328

The offical 1Mbyte support is added by duplicating the if which sets os_hack=1 and updating the end address for the extra bin range.



// if we detect its the LS1 OS range, then enable a hack to skip parts that are not included
if (pCalcInfo->dwRegionStartAddress==0 && pCalcInfo->dwRegionEndAddress==0x7FFFD) os_hack=1;
if (pCalcInfo->dwRegionStartAddress==0 && pCalcInfo->dwRegionEndAddress==0xFFFFD) os_hack=1;


Can you please update you zip with the plugin I posted above and remove the stolen copies?
If you need more proof see the filesystem string in the dlls from my server where oseplugin is mentioned, which is a completely unrelated plugin for older delco pcms on pcmhacking.net. Thats in all versions....

[antus]

LRT, you have done great work, and I understand the confusion, this hacked version has been passed around and I have just been informed someone is or was selling an ls1 flash tool on ebay, and they removed the credits and included it in the package they are selling. So that is the source of the hacked version. It is deliberately stolen work, but not by anyone here. I am happy for the real version to be passed around and I have shared how it works for the community and I have shared my ls1flash-free source and kernel with NSFW and open sourced a lot of my former work in PCM Hammer but I have a problem with this plugin. I dont think its fair to strike my name out of it. Please dont distribute the hacked version. Since we are all a community (or a couple of communities) working towards the same goal, you are welcome to distribute the one I posted above.

Now I understand whats going on, and I see how the 2 bytes of guid were hacked. The 2 stolen copies can load side by side because of the differing IDs, and they hacked the DLL twice because they couldnt add the one line of code that was needed. So they just changed 7FFFD to FFFFD in the second copy. To be very clear I am only talking about the checksum dlls, not the rest of LRTs work which is fantastic and a huge needed piece of the free flashing solution.

13633

[roughneck427]

Wow i can see this is going to be ugly in some areas. Not sure why someone would want jack with the checksum and repost it. I know i had messaged Antus awhile back pcmhacking about a 1mb checksum and he offered to to make one. And furthermore anyone thats been involved with this project its common knowledge who made them. People are going to mess up a good thing.I can see xdfs going the same way.

[LRT]

....

[LRT]

....

[antus]

I can do that - I would be happy to fix them up and send them back if your open to that. I think 1 plugin is better than 2 or more (if or when we develop more stuff in the future). Otherwise I'd need to use the same GUIDs at the hacked one too, which I guess is possible but I'd rather not base my work on the direction the hack was going. Contact me by PM and we can decide and do something out of this thread.

[NSFW]

LRT, did you also make the custom operating systems? Where can we get the bin files for those?

Thanks for all of your hard work!

[CDeeZ]

NSFW, LRT, PeteS, antus and EVERYONE else who is working to make this happen in any capacity...... Thank you all! You guys embody the spirit of hot-rodding by making this accessible to everyone.

[brandonwh64]

Regarding PCM Service Numbers ...

Sometimes people use abbreviations for these, rather than the complete service number.

4896 = Service Number 09354896
0411 = Service Number 12200411


Thank you LRT! Also would your XDF work with my 09354896 ECU? I have downloaded my bin file and when I open it in tuner pro, the values are not right. I used the 512 checksum and the 12202088 XDF.

[Sub8]

Hi guys - I`m cross posting from the corvette forum here.

I ordered the AllPro USB ELM327 adaptor and have been able to read my BIN file successfully, 01Z06 with mods and a tune. Great! I think, going via the other thread that I can also write the cal changes I want, even better.

However the final piece needed is data logging. Can anyone help? I found a few LS1 tagged ADX files but none of them get anything in TunerPro from my car.

I set tunerpro to use plug-in, set plug-in to ELM327OBDII interface.

1 of the ADX files lets me connect ok but rate is ~1Hz and i'm not getting any channels coming back. 2 of the ADX files let me connect but with rolling errors and no data. The other files don't even get me connected....

[antus]

The built in plugin, as far as i can tell doesnt do anything. I use scalxl pro at this stage as ive had a license for it for years. But I do have a working elm327 adx, but a quick test this morning shows it needs some fixes to work on the allpro. If you want to help and understand the elm protocol and adx authorship i'll send it, else give me a few days and i'll see if i can get it going and release it.

[Sub8]

The built in plugin, as far as i can tell doesnt do anything. I use scalxl pro at this stage as ive had a license for it for years. But I do have a working elm327 adx, but a quick test this morning shows it needs some fixes to work on the allpro. If you want to help and understand the elm protocol and adx authorship i'll send it, else give me a few days and i'll see if i can get it going and release it.

Would be interested in the protocol but I don't expect that I can fix anything!!!!! PM'd.

[highsider]

Hi LRT thanks for the amazing work. My question is, as I am trying to enable data tracing using tuner pro, are your xdf files already set up to work with an adx file? I only ask as the guide I have tried to use mentions having to edit the xdf to suit the tracing and yours are password protected so don't allow the option to do so. Or if I am barking up the wrong tree just go ahead and slap me down. I am a noob to all this tuning stuff. Cheers.

[lsgmt400]

anyone have tips on what i need to change to run a manual trans on my 99 lm7 ecu

[PeteS]

anyone have tips on what i need to change to run a manual trans on my 99 lm7 ecu

What OS number are you wanting to use? I might have a trans segment that would work for you.

[TINBENDER59]

WOW!!! WOW!! WOW!!! To all of the gentlemen that have worked so hard to make this a reality, my hat is off to you all. well done!! I just gotta get it setup lol. I have been using EFILive for a few years now, still have mixed feelings about it. I do own a licensed version of Tuner Pro RT just hadn't worked with it much, I guess it's time to get into it shoulder deep.

Thanks again for the work past, present, and future.

[lsgmt400]

What OS number are you wanting to use? I might have a trans segment that would work for you.
What is the os number?

[sj010489]

Hi i'm new here, first of all thanks LRT for the great work, second does anyone has a 9381344 OS XDF File? I've find only one for a F body and i'm not sure it'll work in my 4.8 out of a 2000 Silverado that i'm currently swapping into my 77 2WD K5 Blazer

[Rhino1979]

Did you ever get an XDF file to work with your 09354896 ECU?

[sj010489]

No, i updated my pcm to an OS with an available xdf file and now all is working fine

[SapperRE]

Hi Im quite new to this thread and forum. Im having problems Downloading the attached files.

I got the TunerPro editing software - for LS1 type PCMs.pdf and printed it.

Im having trouble with PCM OS Checksum Plugins.zip as when I click the link and select save as it goes to save a attachment.php then Im not able to open it.

Am I doing something wrong?

[1project2many]

I believe that someone said IE does that if you're not using "compatibility mode." You can right click, "save as," then type in the file name you want.

[SapperRE]

I believe that someone said IE does that if you're not using "compatibility mode." You can right click, "save as," then type in the file name you want.

Hi Thanks for your reply. I tried file save as but had the same response. Tried also on an older laptop. Ive since manged to download the file by logging in on my Mobile Phone and clicking the lick.

[SapperRE]

Hi Guys, I have managed to the the Bin file from my PCM a OS 12212156 which came with the LS 6.0 Engine I got from a scrap yard.

I also got the .xdf file for the 2002 GM Vehicle in this thread.

The original transmission is showing as a 4L80E but I want to use my 700R4 as this has very recently been fully rebuilt.

The 6.0 LS will be going into my 1989 GMC Vandura G2500 Van.

Am I able to just change to transmission type and then save or is it more complicated? to I need to change other settings aswell.

I need to delete VATS
EGR
Cooling fans
Probably the Speedometer section with wheel size etc.
Maybe the 02 Sensors aswell. (still reading up on whats needed).

Many thanks.

[1project2many]

Hi Thanks for your reply. I tried file save as but had the same response. Tried also on an older laptop. Ive since manged to download the file by logging in on my Mobile Phone and clicking the lick.
I'm glad you've figured a way around the issue. When you "Save As" the browser suggests a filename. You can change the name of the file by typing in the name manually.

Unfortunately I can't get screenshots at this time as my browser saves the files with the correct names.

[SapperRE]

Thanks I'll give that a try aswell.

[ClayMac2000SS]

I am not finding .xdf files for 2000 LS1 cars.
I have a 2000 Camaro M6 that is using the OS 9381344.
Can anyone help or point me in the right direction?

[sj010489]

I am not finding .xdf files for 2000 LS1 cars.
I have a 2000 Camaro M6 that is using the OS 9381344.
Can anyone help or point me in the right direction?

You'll need to update your OS, i flashed another bin to my pcm and then i was able to tune my pcm

[ClayMac2000SS]

I've had my computer mail order tuned way back when I was first working on my build and was hoping to just tweak the "Safe" tune. It is very rich and has some idle issues with the A/C on. If I update the OS and flash a new .bin, I'll be back to square one... Correct?

[sj010489]

I've had my computer mail order tuned way back when I was first working on my build and was hoping to just tweak the "Safe" tune. It is very rich and has some idle issues with the A/C on. If I update the OS and flash a new .bin, I'll be back to square one... Correct?

Yes that is correct, you'll have to tune the pcm

[ClayMac2000SS]

Yes that is correct, you'll have to tune the pcm
Thanks for the help.

Would I be able to save my .bin file and revert back to the 9381344 OS and the "safe tune" if I needed?

[sj010489]

Yes that is correct, you'll have to tune the pcm
Thanks for the help.

Would I be able to save my .bin file and revert back to the 9381344 OS and the "safe tune" if I needed?[/QUOTE]

Yes, you can save your .bin file and back it up if you need to go back to that OS

[ClayMac2000SS]

Can the OS be updated by importing a new Bin File for the 12202088 OS, changing the VIN, and then write the OS and calibration to my current PCM?

[sj010489]

Can the OS be updated by importing a new Bin File for the 12202088 OS, changing the VIN, and then write the OS and calibration to my current PCM?

Yes, you update the OS with a bin file similar to what you have (example 2001 ls1 with 4l60e), first flash the stock .bin with the OS you want, then start making the changes you want

[highsider]

After some help guys. Tried flashing the 12587603 os to a p59 pcm so I can use the xdf file available for this os. Problem is even after removing vats from the bin file, engine will crank but not start in a no spark situation. Flash the pcm back to the original 12592433 os and it's fine. Wondering what I may be missing that's preventing the start. Have tried a couple of different bins with the same os but no difference. I'm guessing it might be something in the settings I'm missing but at a loss what to check next. Cheers.

[sj010489]

After some help guys. Tried flashing the 12587603 os to a p59 pcm so I can use the xdf file available for this os. Problem is even after removing vats from the bin file, engine will crank but not start in a no spark situation. Flash the pcm back to the original 12592433 os and it's fine. Wondering what I may be missing that's preventing the start. Have tried a couple of different bins with the same os but no difference. I'm guessing it might be something in the settings I'm missing but at a loss what to check next. Cheers.

What software are you using to tune the .bin file?

[highsider]

Using Tuner pro to tune. Have had zero problems using it with my current pcms.

[sj010489]

Using Tuner pro to tune. Have had zero problems using it with my current pcms.

Going to have a p59 over the weekend will do the same steps as you and will report back

[highsider]

Thanks mate. Any help would be appreciated.

[highsider]

So did you have any luck?

[midnight98ws6]

I think I am in the same boat. My ECM is from a 2000 z28 a4. My ECM is 16220610, and I think the OS is 09354896. So if I am tracking correctly, I need to use an OS from a 2001 or later right? Then find a bin file that matches that OS.

Does anyone have a bin file for a 2001-2002 fbody 5.7l m6? I checked the bin directory but couldnt find any m6 bins for 2001 or 2002.

[vamper]

Im also looking for some help. I have a 2003 silverado 2500HD 6.0 4x4 4l80E with OS 12580786 and i cant find a XDF file is their a depository or can anyone point me in the right direction or a decent replacement OS that will meet the needs of said truck

[brandonwh64]

So I have a question about COS he mentioned in the post below. I am trying to run my 2000 5.3L in speed density and been running into a road block. I seen he had XDF for two custom operating systems in that post but no BIN files. Do I need a bin or just take a stock bin of same OS as xdf and when tuner pro saves it, it becomes a COS? If anyone has a custom OS for speed density on a P01 ECU with a usable XDF, that would be amazing as well! Thanks guys


http://www.gearhead-efi.com/Fuel-Injection/showthread.php?7676-Free-LS1-Tuning-Software-(all-you-need-is-TunerPro)&p=73585&viewfull=1#post73585

[cobra30689]

Hi Guys, I have managed to the the Bin file from my PCM a OS 12212156 which came with the LS 6.0 Engine I got from a scrap yard.

I also got the .xdf file for the 2002 GM Vehicle in this thread.

The original transmission is showing as a 4L80E but I want to use my 700R4 as this has very recently been fully rebuilt.

The 6.0 LS will be going into my 1989 GMC Vandura G2500 Van.

Am I able to just change to transmission type and then save or is it more complicated? to I need to change other settings aswell.

I need to delete VATS
EGR
Cooling fans
Probably the Speedometer section with wheel size etc.
Maybe the 02 Sensors aswell. (still reading up on whats needed).

Many thanks.

Changing the transmission from a electronic to a non-electronic (or manual) trans is quite a bit more complicated....it's not as simple as *just* changing the transmission type, and there are some who say that isn't a good idea as other problems can arise. You'll have to dig through EVERY transmission DTC and turn it off.....otherwise the PCM will be looking for a TCM and start throwing codes. IMO it's easier to just reflash the PCM with a manual OS. In my case, I went on CarGurus, searched for a 4.8 pickup with a manual trans.....grabbed the VIN, went on GM's TIS website ($40 per VIN) and reflashed the PCM with my VXDIAG pass-thru. Of course you'll have to make the rest of your changes in your list.

[PeteS]

So I have a question about COS he mentioned in the post below. I am trying to run my 2000 5.3L in speed density and been running into a road block. I seen he had XDF for two custom operating systems in that post but no BIN files. Do I need a bin or just take a stock bin of same OS as xdf and when tuner pro saves it, it becomes a COS? If anyone has a custom OS for speed density on a P01 ECU with a usable XDF, that would be amazing as well! Thanks guys


http://www.gearhead-efi.com/Fuel-Injection/showthread.php?7676-Free-LS1-Tuning-Software-(all-you-need-is-TunerPro)&p=73585&viewfull=1#post73585

You will need a matching COS to use one of those XDF's. They will not work with a stock BIN file.

Since COS's from tools like HPT and EFI Live do not contain any type of calibration data you would need to find one that's been setup already(and is compatible with the XDF) as there could be settings the COS needs filled in that would not be in the XDF if you tried to populate the raw COS yourself. I'm not sure on things like the COS1 but for any of the COS's that have extended boost tables you need to do a complete OS flash every time you make a change in any of the settings as tables have been moved outside of the "OEM" calibration data range and none of the free tools avaible would correctly flash the calibration data range for a COS.

[PeteS]

I have not seen an XDF for that OS and do not know of anyone working on one for it. Your only real option will be changing the OS to the supported 12587603 and then finding a bin file for a similar setup to work from.

[THEFERMANATOR]

Changing the transmission from a electronic to a non-electronic (or manual) trans is quite a bit more complicated....it's not as simple as *just* changing the transmission type, and there are some who say that isn't a good idea as other problems can arise. You'll have to dig through EVERY transmission DTC and turn it off.....otherwise the PCM will be looking for a TCM and start throwing codes. IMO it's easier to just reflash the PCM with a manual OS. In my case, I went on CarGurus, searched for a 4.8 pickup with a manual trans.....grabbed the VIN, went on GM's TIS website ($40 per VIN) and reflashed the PCM with my VXDIAG pass-thru. Of course you'll have to make the rest of your changes in your list.

Somebody else tried changing the trans type, flashed ot in using pcmhammer, and it bricked his PCM. Tried it on another and got the same result. So don't change that setting.

[CarlsLQ9SS]

'04 Corvette M6 os12587603.bin (1.00 MB) I am looking for one that will work with a 5.3 and a nv3500. Doing a ls swap on a 66 gmc pickup and need a bin file for a manual transmission. My pcm is a blue and green service number 12589463. Will the one I pasted here work for me?

Thank you, Carl E.

[PeteS]

Somebody else tried changing the trans type, flashed ot in using pcmhammer, and it bricked his PCM. Tried it on another and got the same result. So don't change that setting.
With out knowing more about how you flashed the file I'm not going to say this will 100% work but it's very unlikely either of the PCM's are actually bricked unless you altered something in the boot sector of the bin file.

View or download the picture and you will see there is a pin I've highlighted. With the PCM turned ON ground this pin for .5-1 seconds and IMMEDIATELY attempt to re-flash the PCM. Depending on what tool your using to flash with you may need to click start a split second before you release the pin from ground to get the timing on this right. You may only have a 1- 2 second window where the the PCM will be flash-able but that depends on how bad its damaged.

If the flash chips file is only slightly damaged the PCM will boot and start sending either an OS or calibration recovery mode message and will allow you to reflash until the next time its turned off so there is no requirement here on how precise the timing needs to be. It will be in an unlocked state and allow uploading a flash kernel into the ram.

Now if the main OS is badly damaged or there is corrupted information in the boot block the data bus will only come online for a very short time and you will need to time the ground release so as soon as the flash chip resets you are unlocking the PCM and start the flash kernel upload. The flash kernel needs to be uploaded and brought online before the data bus becomes unresponsive again for this to work. The greater the damage in the boot block the less time you will have to upload the kernel.
14771

Here is a video demonstrating recovery on a dead PCM using LS Droid and what this looks like if you were viewing the data bus.
https://www.youtube.com/watch?v=NZ4Xt_ebI4M

[PeteS]

'04 Corvette M6 os12587603.bin (1.00 MB) I am looking for one that will work with a 5.3 and a nv3500. Doing a ls swap on a 66 gmc pickup and need a bin file for a manual transmission. My pcm is a blue and green service number 12589463. Will the one I pasted here work for me?

Thank you, Carl E.

OS 12587603 for a 2004 Silverado with a 5.3(LM7) setup for a manual transmission. If you plan to run flex fuel then you would want an L59 engine segment rather then the LM7. You will need to readjust things related to the speedometer such as the VSS PPM as they are still configured for an auto trans.

The engine segment is for a stock engine as far as I'm aware and still has all emissions enabled as well as torq management and is configured for a DBW throttle.

[CarlsLQ9SS]

Thank you, very much appreciated!

[silverbullet82]

Just getting started on the LS Droid, doing a junkyard 4.8, 4l60e swap. The PCM I have is displaying OS 12579405. I have tried a couple different XDFs but I keep getting an error when trying to write the calibration back to the PCM. Wondering if I need a 12579405 specific XDF?
Thanks14861
Matthew

[PeteS]

Two things....

1) The XDF and the OS number MUST MATCH. Even if the OS is 1 digit off it won't work. Unless an XDF is labeled that it supports multiple OS's it will only work CORRECTLY with the OS that it matches. Just because Tuner Pro doesn't know the difference and give you some error message doesn't mean it will work.

2) I see the file your trying to flash a file labeled as a COS. You would need to acquire a matching and complete version of that COS in bin format in order to use that XDF. You can't just use the XDF on a stock BIN and expect it to work, it's a modified operating system and is not compatible with a stock OS. The reason I say you need a COMPLETE version of the file is because the way that OS was done with the commerical software that created it was it writes the OS to the PCM then has you import your existing calibration data and instructs you to finish populating the new tables the OS created. Since tuner pro does not give you a way to import calibration data from another file and assign things at specific addresses in the bin file the only way you can use it is if you are starting with a complete version of the COS that already has all the calibration data setup.

You also can not flash a COS as a calibration regardless of how small the change you made was, it would need to be flashed as an OS+Calibration. COS's change the address mapping of calibration data and even extended calibration data outside of the area GM uses for calibration settings. Because these address changes are specific to each type of COS the only way to ensure you flash the file correctly(and completely) is by flashing the entire PCM.

If all your doing is an actual junkyard swap there is no reason to use a COS, flash the PCM with the 122112156 OS like every one else does and call it a day.

[silverbullet82]

I found a '04 C1500 5.3L os12587603_test1.bin and a OS matching XDF file Operating System 12587603 - 1Mb PCM - 2004 model year. loaded into tunerpro rt and Disabled VATs. Still getting an error when trying to do a OS_PLUS_CAL.

Here's my LSDroid WriteLog

6CF01068009F




6CF01067012B5C3E

6CF0106702344B


6CF0107F340005BAFF91229D

NODATA

6CF0107C0A00BFF24D15

6CF0107C0A00BFF24D15

Thanks
Matthew

[PeteS]

PM me a copy of the bin file you initially read from the PCM. I would say post it here but an unsupported OS isn't one we need in this thread.

[Stampede]

Hello,

I just wanted to say, that I was able to load a new OS, and XDF on to my 896 pcm. All I did for now was turn off VATS, it will be a little while longer before I have my harness done to verify.

Thank you to everyone who has put their time in to this, and making it work!!! This is a huge help to me.

Stampede.

[bigfella88]

i am also new to LS droid , im having a problem with my first attempt to even read the ecm it starts the stops very soon and only displays a "?".

14869

I have been over my harness 3 or 4 times double checking it , not sure if the computer is bricked or i have a harness issue of some sort

[S.O.B.B.]

Did anyone ever have any luck burning/reading/flashing the chips from ls pcm using tuner pro xdf/adx files.I'm asking because I didn't see a cheap cable for doing this.picked up a 0411pcm os12201281dbc for $20 from 2001 Tahoe.if it's as simple as obd1 with burning chips I plan to make a harness.have a method for 1x cam signal.possibly use BBC 24x crank ring and adapt it to my front balancer. be nice to be able to use this pcm for any engine.any advice appreciated. Thanks

[NSFW]

Did anyone ever have any luck burning/reading/flashing the chips from ls pcm using tuner pro xdf/adx files.I'm asking because I didn't see a cheap cable for doing this.picked up a 0411pcm os12201281dbc for $20 from 2001 Tahoe.if it's as simple as obd1 with burning chips I plan to make a harness.have a method for 1x cam signal.possibly use BBC 24x crank ring and adapt it to my front balancer. be nice to be able to use this pcm for any engine.any advice appreciated. Thanks

Yes, and that's what this thread is about. :)

For PCs: http://pcmhammer.org
For Android phones: http://ls-droid.com

I've flashed my C5 about 20 times now with PCM Hammer, and I have a couple of PCMs on my desk that have been flashed at least as many times. I don't advise anyone to use it on their daily driver just yet, but we're getting there.

[S.O.B.B.]

Thanks.I guess I should have been a little more specific.if I remove the chip and use an adp-019 (psop44 to dip32) to read it in my GQ4x4.then use the tunerpro xdf to make changes and reflash the chip and reinstall in pcm via surface mount zif.I ask this because I have most of this stuff already. I Do not own a cable to flash or read pcm through obd2 port.I do have a maxidiag obd2 reader that gives me o2 sensors.short and long fuel trims.iac.tps.etc so I can read live data.just want to be sure the files will work the same by reading/editing bin from the chip burner.I have a couple xdfs and looked them over.I don't have one for os 12201281which is what's on the service label.am I out of luck if I can't get that xdf.haven't seen one in searching.easy enough to go get another pcm with more supported os.lots at the yard I use.appreciate the help.:confused:

[kur4o]

To use the bin file pulled from the lifted chip you will have to byte swap the file. Swap odd and even bytes. Some chip programmers have that built in.
You will have to byte swap the bin file before opening with tunerpro and byte swap again after you save it with tunerpro.

I can only recommend chip lifting for recovering bricked pcm. An OBDLink cable is not that much and will serve you well for other pcms too. Changing to xdf supported OS is a breeze with it. And caldata write takes less than a minute.

[S.O.B.B.]

Thanks for that info.didn't know that the cable was not so expensive. But searched and found that the gq4x4 does have byte swap.I may try it this way just to see how difficult the soldering is.but thanks for your time.

[THEFERMANATOR]

I picked up my obdlink SX cable for $20 off Amazon. Why mess with soldering over a $20 cable.

[kur4o]

LRT

Can you share an unlocked version of 12587603 1mb xdf.


I am doing a disassembly of that OS and it may help me to label known stuff faster.
It will really speed up the process.

Thanks

[NSFW]

LRT

Can you share an unlocked version of 12587603 1mb xdf.


I am doing a disassembly of that OS and it may help me to label known stuff faster.
It will really speed up the process.

Thanks

An unlocked / text version would fantastic!

I've been talking with a guy who is setting up a github repository for XDF files and it would be great to have text versions of all the XDFs. That way anybody can add to them as we find and document more things.

He says he's found another '603 XDF (unlocked) that has some additional tables defined, but no comments, and he wants to combine the best of both files, and an unlocked versions of both would make that job a lot easier.

Also, I've got a script that turns (unlocked, text) XDFs into IDC script, which gives a huge head start on reverse engineering with IDA Pro.
https://github.com/LegacyNsfw/12593358/tree/master/Scripts

[Tahobra]

Does anybody in this forum have a stock 4.8 truck LS with a sloppy stage 2 cam that they don't mind sharing the .bin file for? I'm about to do the cam swap and I'd like to have a basis for building my tune and I'd really like for it to idle decent right off the first fire with the new cam. Any files or even tuning advice would be much appreciated.

[dzidaV8]

An unlocked / text version would fantastic!

I've been talking with a guy who is setting up a github repository for XDF files and it would be great to have text versions of all the XDFs. That way anybody can add to them as we find and document more things.

He says he's found another '603 XDF (unlocked) that has some additional tables defined, but no comments, and he wants to combine the best of both files, and an unlocked versions of both would make that job a lot easier.

Also, I've got a script that turns (unlocked, text) XDFs into IDC script, which gives a huge head start on reverse engineering with IDA Pro.
https://github.com/LegacyNsfw/12593358/tree/master/Scripts

Here's my XDF for '603

EDIT: deleted due to possible copyright violation

[brandonwh64]

Does anybody in this forum have a stock 4.8 truck LS with a sloppy stage 2 cam that they don't mind sharing the .bin file for? I'm about to do the cam swap and I'd like to have a basis for building my tune and I'd really like for it to idle decent right off the first fire with the new cam. Any files or even tuning advice would be much appreciated.

You can do it on your own if you are able to use tunerpro with your bin. Below is goat rope garage and he shows you how to setup your tune for a bigger cam. He uses HP tuners but honestly I have went along in his videos and compared his PID to tunerpro and they are pretty much the same (Outside of COS stuff). You should be able to follow his guide in tuner pro and get the desired idle and base setup you need

https://www.youtube.com/watch?v=r00uXQomvRI&list=PLxTMckx4RYqmTswv7LHtnNyoqCoqPwFLe

[NSFW]

Here's my XDF for '603

Fantastic, thanks! I'll pass this on to the guy who is making the repo.

[rich454mc]

Hey guys. i've searched everywhere and can't seem to find an XDF for my OS . its a 1283002. I have found a couple different COS's on the primary page but no info on the one I need. any help would be appreciated. thanks.

[LRT]

....

[Lexas]

I picked up my obdlink SX cable for $20 off Amazon. Why mess with soldering over a $20 cable.

have you managed your cable obdlink sx, to work with tunerpro? program cant see device, even if i set up correct port. or i need plugin for sx?

[LRT]

....

[stump56]

Does anyone have a good adx file for logging the ls in tunerpro. Any advice on logging would be awesome too.

[NSFW]

Does anyone have a good adx file for logging the ls in tunerpro. Any advice on logging would be awesome too.

The latest release of PCM Hammer includes a simple data logger.

You still have to edit XML by hand to change what it logs, but the format is pretty simple (nothing like ADX). It comes with a couple of example files, and I'm open to feedback about what those log.

It is effectively limited to standard SAE PIDs right now, but it does support logging values from RAM, which means that as we get operating systems reverse engineered we will be able to log anything we want.

[stump56]

Thanks NSFW i am looking into it. Where can i find the xml files ! didn't see them in the zip for ver. 11?

[NSFW]

Thanks for pointing that out - I forgot to include them in the zip file.

That might explain why so few people have been talking about the logger... I really thought there would be more interest in it. :)

I've attached them here. You'll have to remove the .txt extension, so the file names end with ".xml.profile"

[stump56]

Thanks again.

[Smittyboi]

Does tuner pro interface with 2007 L92? I'm looking to disable VATS, VVT and configure for TR6060 manual transmission.

[bigbill0679]

Hello i am New here and this is closest place i see to ask this, if i am wrong please let me know . I have a friend that has a 2000 k3500 7.4l fuel injected auto. Can this be tuned. I did put a new (used) knock module in it (Knock Codes). It did help some but motor is fresh with new heads and this thing is a dog he had a programmer on it but cant remember what it was and he sold it awhile back. Is this a em3494u pcm pcm # is 16208991, and what is needed if anything to flash back to stock or tune it please. Cant seem to find any info via google search. How can i read pcm like in ls droid or other free stuff i dont have HPTuners yet.

[LRT]

....

[bigbill0679]

It will use the older "Black Box" Vortec PCM. At this time HP Tuners is your best option to tune this PCM. Many have upgraded from the Vortec PCM to the 0411 LS1 (P01) PCM. A Google search will point you in the right direction if you choose to do this upgrade.
Ok Next question this is a complete harness swap with 0411 pcm correct i think. Any sug. On donor vech for harness trk has 4l80e

[LRT]

....

[bigbill0679]

how about Operating System 09381344 off a 4896 for a 00 silverado lm7 m30 4l60e 4x4 or swap os to 8322 0r 2088

[bigbill0679]

thanks LRT for Blackbox info i found this just before your reply and also jr from driveway engineer also provided link

[LRT]

....

[bigbill0679]

sorry 2 questions ran together the 1344 /4896 question is for a 00 silverado lm7 m30 4x4 need 1344 xdf for tunerpro or can i just do a 2088 or another bin to this 4896 pcm

[NSFW]

Punctuation would help.

Better yet, line breaks.

[bigbill0679]

Punctuation would help.

Better yet, line breaks.
So very sorry for confusion

[bigbill0679]

looking for help with bluetooth adapter like obdlink lx,mx,mx+ to connect to tunerpro /rt

[sheza65]

I have a PCM from a 2000 Silverado 1500 2wd LM7 (09354896) that I flashed with LS Droid and OBDLink LX using a TunerPro RT modified BIN. I think the original OS is 16220610 (see photo).

Since I couldn't find an XDF for the original BIN, I used '01 C1500 LM7 os12208322 from a file found on this site and the 12208322 XDF.

The engine runs, but the tach output (PCM Red # 10) doesn't seem to be working. I tried a pull-up resistor without any luck. Would the different OS cause this issue?

The motor is in a 2005 Jeep Wrangler. The tach low puses were changed in order to get the Jeep tachometer to work.

In the tune, I changed Tach Low Pulses from 6 to 1 and Tach High Pulses from 6 to 1. Is there a Pull-up / No Pull-up feature in TunerPro?

Is there a BIN & XDF available for 16220610?

[LRT]

....

[sheza65]

LRT,
Thank you for your reply and insight.

So, my 512KB 09354896 PCM with hardware 16220610 isn't compatible with 12208322 BIN and XDF? (BTW, is the hardware # 16220610 the OS #? Or are they entirely different things?)

Is this the BIN file you recommend instead?
2002 Chevrolet Silverado Truck Auto LM7 5.3L (12212156).bin
http://www.gearhead-efi.com/Fuel-Injection/attachment.php?attachmentid=5059&d=1376283443

I should use it with your "Operating System 12212156 - 512Kb PCM - 2002 model year.xdf" listed in post #2, correct?

Will you help me understand why or why not?

Previously, I used this BIN
"'01 C1500 LM7 os12208322" with your "Operating System 12208322 - 512Kb PCM - 2001 model year.xdf" XDF from post #2 of this thread.

Will you please help me understand why that was foolish? My understanding was that 12208322 is "for use with 512Kb PCMs (Service Numbers 09354896 and 12200411)".

[LRT]

....

[sheza65]

Edited #102 for clarification. This is what I did:

If you actually have flashed a 2001 OS into the PCM - 12208322 - and are using the matching XDF - then you are OK.

Are my other assumptions correct?

How do you identify the OS of a PCM? Is it the "HDW No."? I'd assume that refers to the hardware chip set, not an operating system.

[NSFW]

Hardware number (and "service number") both describe the hardware, that's correct.

To find out which operating system is installed on the hardware, you'd have to use software to connect to it and ask. With PCM Hammer, clicking the "Get Properties" button will list a few things, including the operating system ID. I'm pretty sure LS Droid has a way to do this as well but I haven't tried it myself yet.

If I remember right, the '896 hardware is a little different from the rest of the family, so it may not work with all operating systems. I don't really know though.

The best place I know of to search for bin and xdf files is here:
https://github.com/BoredTruckOwner/LS_Based_Engine_Repository

There might be other stuff that isn't in there yet, so it's still worth doing some web searching on the hardware number / service number / operating system ID plus "bin" and/or "xdf" and see if you can find anything. and if you do find something that isn't in there, please submit it to the repository, or just post it here and I'll submit it.

[sheza65]

Thanks NSFW.

My only contribution at this point is that 12208322 and 12212156 seem to load fine on my 09354896 with LS Droid in conjunction with OBDLink LX & the engine seems to run fine. I am still not able to get the Jeep's tachometer working with or without a pull-up resistor (which may be completely independent of the tune, flash, etc.).

[tf3n]

OS 12587603 for a 2004 Silverado with a 5.3(LM7) setup for a manual transmission. If you plan to run flex fuel then you would want an L59 engine segment rather then the LM7. You will need to readjust things related to the speedometer such as the VSS PPM as they are still configured for an auto trans.

The engine segment is for a stock engine as far as I'm aware and still has all emissions enabled as well as torq management and is configured for a DBW throttle.

Hey Pete. I'm running a 5.3L (LM7/Cable throttle) out of a 2000 Silverado. Would this OS/BIN work pretty well for me? I'm hoping to find a setup that I can run without too much fine tuning for now, until I get the swap sorted.

[cgw]

So what would I need hardware-wise to use this for my 02 2500HD 8.1/Allison?

[DrBob]

OS/XDF help needed.

I'm working with OS-12221588 and its xdf file in Tuner Pro...

I need to find how to enable/disable the pullup resistor on the Tach output and also how to change the throttle position setting that the 1-4 Upshift lamp (C2-47 on a 411 PCM)
operates at. (CARS_CAGS)

Bob

[Hey_Allen]

Intending to remove VATS and some emissions bits from a 5.7l 12587603.bin, I downloaded the 12587603.xdf from the BoredTruckOwner github repo linked above.
As soon as I try to select the XDF in TunerPro or TunerPro RT, the program crashes.

If I load a P01 XDF, I can poke around a 512kB bin file as expected.

Am I missing something obvious here?


edit:
Nevermind, found an old issue that resolved the problem.
It was the msvcp100.dll that was in the plugins folder. Once I renamed it I had no more issues.

[pnwsr6]

Is there anyone still adding additional features to these xdf? If so how would I go about requesting something be added? Researching and learning how to use Tuner pro and the xdf's is fairly easy. Adding things to an xdf from what I can find has a steep learning curve. The OS I am currently interested in is 12216125 because of its flex fuel capability and good coverage options for a p01 411 pcm. I'm willing to help in any way that I can.

[B52Bombardier1]

Hello,

You are better off abandoning your current tune and pursuing an OS that has what you need for Flex Fuel support and that has an already richly featured XDF file. I don't know that anybody is actively adding features to obscure OS XDF files though you might . . . might . . . talk somebody into adding something into an existing, already well supported XDF.

Have you looked at what is available for features in 12208322, 12202088, 12212156? I'm not sure if these support Flex Fuel. What engine and transmission are you needing?

Rick

[pnwsr6]

What I'm looking for is things like injector timing\phasing, for cam changes, some tcc lockup settings, and dfco settings that aren't available in the xdf for 125 os, some of which are available for other xdf's. This is the only os and xdf that has flex fuel available for the p01. Finding engine and transmission combo isn't the problem. I would gladly add the parameters myself if I knew more about how to create xdf's. Everything I have read so far on creating xdf's seems confusing.

[Stokes1114]

What I'm looking for is things like injector timing\phasing, for cam changes, some tcc lockup settings, and dfco settings that aren't available in the xdf for 125 os, some of which are available for other xdf's. This is the only os and xdf that has flex fuel available for the p01. Finding engine and transmission combo isn't the problem. I would gladly add the parameters myself if I knew more about how to create xdf's. Everything I have read so far on creating xdf's seems confusing.
I'm running 6125 on a flex fuel truck and have been wanting to figure a way to add in some parameters as well. The xdf is locked for editing too. I understand why someone would lock it, but at the same time would like to try to start from the current xdf and not from square one.

[TilmanNA]

Hello! I noticed you stated "LS" type pcms, however is that inclusive? question being I have the 411 with 2156 OS and was wondering if the .XDF listed above would allow me to change VATS and Trans on L31 with the above factory ECM with is what I pulled with the Engine? long question... opps

[pnwsr6]

Hello! I noticed you stated "LS" type pcms, however is that inclusive? question being I have the 411 with 2156 OS and was wondering if the .XDF listed above would allow me to change VATS and Trans on L31 with the above factory ECM with is what I pulled with the Engine? long question... opps

If the xdf matches your OS, then you can use it to modify your OS. If you can't find an xdf with the same number as your OS then you either have to find and use another os with an xdf,or create one from scratch. 2156 OS should have a xdf for it in the 2nd post of this thread.

[TilmanNA]

Thanks!!

[TilmanNA]

Thanks!!

Cool, I found the .XDF, however I noticed in the TorquePro RT "transmission type" it stated ** this parameter should NOT be changed ** !!!

What to do?? The 411 OS 2156 PCM states it is a 4L80E, yet I would like to change it to a manual NV3500.

[pnwsr6]

Cool, I found the .XDF, however I noticed in the TorquePro RT "transmission type" it stated ** this parameter should NOT be changed ** !!!

What to do?? The 411 OS 2156 PCM states it is a 4L80E, yet I would like to change it to a manual NV3500.

There's a couple of ways to do what you're looking for. If you are using lsdroid to flash your pcm, the newest version of that app has the ability to segment swap. I strongly recommend reading up on this thoroughly before attempting it. In the apps FAQ section, it has a link to some stock bin files that can be used for segment swaps, but a segment swap must be for the same OS. Again strongly recommend that you make sure you understand how to use the app and what segment swaps are. Lsdroid has a Facebook page to help answer questions about lsdroid. There's also a way to do it without segment swapping, but I don't know everything you need to turn off to get it to run and not throw any codes.

[yoheer]

Hey guyz! Throw me a link pls, cant find info, what hardware and software i do need to read and flash gm obd2 pcm

[pnwsr6]

Hey guyz! Throw me a link pls, cant find info, what hardware and software i do need to read and flash gm obd2 pcm

Search LS Droid and tuner pro. There's even Facebook pages about it.

[yoheer]

Search LS Droid and tuner pro. There's even Facebook pages about it.
And what about hardware?

[pnwsr6]

And what about hardware?

Guy that made lsdroid also makes a obd2 device that is designed for it. It's on the FB page.

[yoheer]

And what about standard hardware? Like elm327, or galetto or kess. Diablosport is too expensive

[pnwsr6]

There is enough info in this thread to give you a good starting point. If you search my profile and look for my posts, you will see I have asked very few questions. Participated in very few. That is because almost all the information I needed to do what I wanted to do was available to find in the forums, I just had to search for it. This is also not the only place to find info. Google is your friend. You will find most people on these forums have answered the same questions over and over again, and will ignore you if you seem to have asked questions without searching for it.

[TilmanNA]

Thanks for the reply. I missed it earlier. Yes, I am using LSDriod, OBD Link LX, and Tunerpro RT. I will do as suggested and check out the FB page. Thanks!

[TilmanNA]

Again, Thanks. I checked out LSDROID and a guy by the name of Pocono Joe said I should seg.swap the team/trans dia. & speedometer files. Darn, I should of ask how to? Any good you tube videos!? I will look on Google as well. Thanks.

[pnwsr6]

Again, Thanks. I checked out LSDROID and a guy by the name of Pocono Joe said I should seg.swap the team/trans dia. & speedometer files. Darn, I should of ask how to? Any good you tube videos!? I will look on Google as well. Thanks.

If you have your original OS, and have found a bin of the SAME OS with with the segments you are looking for, you can open lsdroid and go to the segment swap section of the app if you have already unlocked that feature. If you look through Pete's post on the FB page, he explains the reason behind the feature locks and how to enable the features. If you try to swap segments from an OS that isn't compatible, lsdroid is supposed to recognize it and not allow it I think, but I would make sure you use a matching OS and not chance that. The segment swap feature is actually pretty easy to use, just pay attention and make sure you make the names of the bins you get something you will know what they are and not get them confused and flash the wrong one.
Good Luck!

[TilmanNA]

GREAT INFO!!! Thanks!!

[sturgillbd]

I have a couple of questions regarding this xdf and the one for the 512k pcms. I noticed when viewing the VE table using this xdf file in Tuner Pro, The VE numbers range from around 1 to a little over 2. When I open the same bin file using EFI Live, There are normal VE numbers as in VE %. The conversion is approximately 48.212 * the number reported in TunerPro. I also get an out of range value when I set VATS to be disabled in Tuner Pro and open the bin in EFILive. I have an 03 GMC Sierra with a 4.8 with 4L60E. I segment swapped a 04 4.8 engine cal into an 04 5.3 bin from the same type truck and programmed a second PCM. I used EFILive to get the 03 calibration parameters such as MAF calibration and the injector data and pasted that data into the 12587603 flashed PCM. It runs fine but just playing around I noticed these differences. I am attaching screenshots of the things I see.

Maybe LRT will see this post. If anyone else knows, please chime in.

Thanks,
Brian

[LRT]

....

[sturgillbd]

Thank you for the explanation. I had read the comments and the text is almost identical to what EFILive and even had the same formulas. I did a base install of EFILive just to compare the calibrations. I didn't set any preferences on how to display the VE. There is a learning curve coming from OBD1 and flashing chips to working with the LS calibrations. I apologize for any inconvenience

[yoheer]

hi guys
1. trying to add plugins to tunerpro. Doing all by instruction. wanna add 512 and 1mb checksum plugins. they doesn't appear in help->plugins. what i'm doing wrong?
2. I have one pcm 12583659 (serv.#12586243) It is from 2005 car. It seem that I can use 12587603.xdf and 2004 bin files for it. Right?
3. What xdf should I use with 2007 4.8 engine? I'll specify PCM# a lil bit later
4. Is it possible to change operating system?

[B52Bombardier1]

Hello,

1 - I placed my checksum plugins inside the C:\Program Files (x86)\Tuner Pro RT folder. Seems to work, no problems.

2 - If your PCM's have the green / blue connectors and a 1 megabyte memory capacity, they should work.

3 - The XDF file MUST ALWAYS MATCH the operating system, NOT the model year or engine size.

4 - Most of the time, you are changing the operating system. Completely overwriting your previous OS. This is because most of us are not lucky enough to have a vehicle with an original OS that has a supporting XDF file. We most always abandon our original OS and put in an OS that has good XDF support. The 12587603 OS is such a thing.

Rick

[yoheer]

If I have 1mbyte pcm with green/blue socken and any part number then I can use 2004 OS 12587603. Right?
And the same stuff with 512k pcms?
One more question:
Is it possible to disable electronic Throttle body? Install oldschool cable-type TB and tune the pcm?

[B52Bombardier1]

You can only support drive-by-cable throttling with the following PCM's. They made P59's (1 megabyte devices) with the IAC hardware (drive by cable) up to 2007. But only in hardware (not service) numbers: 12575502, 12570558, 12583659, and 12589161. Any other 1 megabyte PCM won't do it.

Same advice applies in the red/blue P01 PCM devices. You must use mated and matched XDF files with your OS.

Rick

[yoheer]

Thank you Rick
I placed plugins(github) to tunerpro directory and duplicated to documents/tunerpro files/plugins
No result
There is only 2 plugins which present since installation. No new one
Is there any manual how to disable TB?

[yoheer]

And how to mod BIN for switching to manual transmission or th400?

Found Transmission type scalar and G1207 Vehicle platform options table in .xdf but it's written in comment that theese parameters should NOT be changed

[B52Bombardier1]

I predict a transmission "Segment Swap" for you from a similarly equipped 7603 OS. But I will also be the first to say I have never needed to do a segment swap for my PCM devices. Just lucky, I suppose.

Rick

[yoheer]

How to make segment swap? Do you mean just to copypast a part of raw data from one bin file to another? Using any HEX editor.
And i`m still confused how to make DBW to DBC mod

[B52Bombardier1]

See my advice in post # 138 above. Your PCM needs to be one of those hardware numbers to have the IAC hardware. If your PCM has the IAC hardware on the internal printed circuit board, simply bolt on a DBC throttle valve and I think . . . . it will simply work.

Others around here will correct me if I'm wrong but I just looked around the 7603 OS and it appears that IAC support is already there and running in the background as dead code if using a DBW setup.

Let's see what others have to say.

Rick

[yoheer]

Tried to read 01 F-body pcm bin with hammer, using VCM2 via j2534. Failed.But test button says OK.

What about mongoose, mini vci els27?
Some other j2534?

[B52Bombardier1]

I use a Bluetooth OBDLink MX+ OBD2 module to read and write to my P01 and P59 PCM devices. Works great and I have a small, 3 amp bench power supply and a junk yard PCM wiring harness.

Rick

[yoheer]

Got mx+
I like it very much.
One question:
How to make pedal be linear with electronic throttle? Or even open the throttle wider with less accelerator pushing. Open faster and wider

[yoheer]

Everybody use 12587603 XDF with the same BIN operating system.
I tried to open 12585950 BIN and it works with that XDF perfect. It shows different parameters and tables and they seem to be correct
Now I do not understand anything. Why it is so?
As I understand, it should not work with other OS.

[LRT]

....

[rocketmench]

Hello, not sure if this is the best place to post this question but here goes.
I am going to be swapping a 2004 junkyard LM7 into a 1968 K20 GM truck. I'd like to enable analog AC request. As I understand it, only those PCM's with DBC IAC transistors in the PCM will have the circuitry to handle an analog AC request.

So I used PeteS's excellent LSDROID Ver. 0.2.2B and OBDX Pro VT bluetooth device to download my OS from the PCM. My original PCM is a Service No. 12586242 with OS ID 12606960. According to LT1SWAP.COM, my PCM does not have the circuitry for analog request but PCM's with Service No. 12576106 are among those that have the IAC hardware internally and which can handle analog AC request. So I went back to the junkyard and found one. Opened it up, and sure enough the IAC transistors are on the board.

So here's my question. Can I use TunerPro to enable the analog AC request? I am not finding that parameter anywhere so I'm guessing it's not been defined in the xdf. Speaking of which I am using "Operating System 12587603 - 1Mb PCM - 2004 model year.xdf". I do have a PCM with that OS so I tried that first and could not find the AC request parameter, so I don't think the issue is not matching the xdf with the OS. According to this post on PCMHacking,

https://pcmhacking.net/forums/viewtopic.php?f=42&t=6734&start=10

the 12606960 OS in my original PCM is an exact match for the 12587603 from the IAC equiped PCM I found. So I'm hoping that an XDF mis-match is not the issue here. Sorry for such long post.

[Neukam]

The IAC drivers are for the Idle Air Control stepper motor used on drive by cable throttle bodies. All of the PCMs use the A/C request input to control the A/C relay output. Different calibrations handle A/C control differently depending on what sensors or switches were used on the vehicle. I am not aware of an XDF for 12606960, which replaced 12587603 as a service update. The PCM can be flashed back to 12587603, and I would recommend doing that as it is probably the best supported OS for the P59.

[rocketmench]

Thank you for such quick response. I realize that the IAC drivers are unrelated to the AC request function. However, according to LT1SWAP.com, only PCM's with IAC hardware will allow for the Analog AC request function (as opposed to the serial). My old truck don't know from serial, so I'd like to switch to the analog, 12V AC request mode. What I'm asking is since most OS's in the 2004 years expected to use serial, don't I need to configure the OS to use Analog? And if so, can that be done in TunerPro?

[rocketmench]

Quick follow up. The relevant section of lt1swap.com/airconditioning.htm is:

"A/C Request: This is a signal input to the PCM indicating the drivers request for a/c activation. There are two ways this is done from GM, a physical wire, a 12v+ positive signal on Pin 17 on C2 PCM connector, and a serial data request over databus. RED/BLUE pcms used 1999-02 all support 12v+ positive signal a/c request. BLUE/GREEN 2003-07 the only pcms that will work with physical a/c request are: Service Numbers: 12576106, 12581565, 12586243, 12589462, 12602801. If your PCM Service number is different from these listed, a/c request input WILL NOT WORK."

[Neukam]

Interesting, I was not aware of that. I don't believe the difference is related to the IAC drivers, but that doesn't mean that those service numbers don't have additional hardware differences in addition to the IAC drivers. The relevant parameter would be "A/C System type". I don't know if any of the 12587603 XDFs have that parameter defined. I have an XDF for 12212156 (P01) that has that parameter, but that doesn't help you. I believe HP Tuners has that parameter for 12587603. If you have access to one of their dongles, you can read the PCM without licensing it to verify how it is configured if you just want to check it. What vehicle was it removed from? Be very cautious using the 12587603 XDF for 12606960. I know for certain that the 12587603 XDF doesn't align fully with 12606960. I wouldn't recommend using it.

[rocketmench]

I'm not sure that there is a 100% correlation between IAC and analog AC request hardware installation in the Blue/Green PCM's. My reading of various forums says that there is at least a significant overlap. Meaning IAC equipped is a good predictor of analog AC equipped. In any case, I think I have a PCM that should work from the hardware perspective, now it's just a matter of the programming aspect.

The vehicle that provided the engine was a 2004 Sierra 4x4 with ls 5.3 LM7. The vehicle that provided the PCM with the IAC driver is a 2003 Avalanche 4x4 also with the ls 5.3 LM7.

And thanks for your suggestion of just swapping in the complete 12587603 OS. I'd already figured that was going to have to happen. But no, I don't have any HP Tuners hardware or software. Was hoping to avoid all that. Really prefer the DIY approach using community-based tools!

By the way, my follow up question was going to be, once I swap in the 12587603 OS, would I need to segment-swap in the engine calibration from the original donor PCM, or is the new OS likely to run the LM7 just fine? I will also use the 4l60E. Would I need to segment swap something in for the transmission as well? Complete newbie here, so...

[yoheer]

How to disable post cat o2 sensors in the right manner? Just disable DTC or there would be impact on fuel trims or smth like this. Cat deleted, so the sensors 2 can be removed.

[Neukam]

I'm not sure that there is a 100% correlation between IAC and analog AC request hardware installation in the Blue/Green PCM's. My reading of various forums says that there is at least a significant overlap. Meaning IAC equipped is a good predictor of analog AC equipped. In any case, I think I have a PCM that should work from the hardware perspective, now it's just a matter of the programming aspect.

Sometime in the (probably distant) future, I'd like to examine the hardware, and verify that there is in fact a difference. It seems unlikely to me that GM would omit hardware for an input, unless they wanted to repurpose that pin as an output. It is possible that the input is there, and the difference is in software, and the information is out of date. I'm not saying that is the case, but until I see it for myself, I'm not ruling anything out. If there is a hardware difference, it could be as simple as a few omitted components that could be added to regain that functionality, as is the case with the IAC driver.


The vehicle that provided the engine was a 2004 Sierra 4x4 with ls 5.3 LM7. The vehicle that provided the PCM with the IAC driver is a 2003 Avalanche 4x4 also with the ls 5.3 LM7.

And thanks for your suggestion of just swapping in the complete 12587603 OS. I'd already figured that was going to have to happen. But no, I don't have any HP Tuners hardware or software. Was hoping to avoid all that. Really prefer the DIY approach using community-based tools!

I totally agree. I do have HP Tuners. If you want to upload the bins you have, I can flash them into a spare PCM and read them out and upload them in HPT format. That way you can look through them and compare.


By the way, my follow up question was going to be, once I swap in the 12587603 OS, would I need to segment-swap in the engine calibration from the original donor PCM, or is the new OS likely to run the LM7 just fine? I will also use the 4l60E. Would I need to segment swap something in for the transmission as well? Complete newbie here, so...

Either should run the LM7 just fine. If the Avalanche had a 4L60E, you should be able to run that calibration. If not, you should be able to segment swap the transmission segments. The post you referenced indicated that most segments, including the trans segments align.

[rocketmench]

Thanks so much with your offer to read the bins. Hopefully my attachments work here. Note: the bin labeled "2GTEK.bin" is the one from the donor truck. When I read it, I found the vin didn't match the truck so maybe the PCM was replaced at some time. It's very similar though, a 2004 Silverado LM7. This is the one supposedly without analog AC request, Service number 12586242 with OS ID 12606960.

The bin labeled "3GNEK.bin" is the one from the IAC enabled pcm with Service number 12576106 and OS ID 12579405.

I did try to trace the pins on the IAC enabled pcm but couldn't find any connection from C2 Pin 17 to anything else on the board. I'll see if there's a difference to the other PCM in that location and let you know.

[rocketmench]

So I opened up both PCM's and looked for differences near C2 pin 17, which is the input for the 12V analog AC request. As you can see in the attached pdf, there are 2 resistors in the Service No. 12576106 (with the IAC) that are missing in the 12586242 PCM (without the IAC). There is a 100 kohm resistor on the backside, and a 3 kohm resistor on the front side that is missing.

There are some other minor differences, so I don't know if it's simply a matter of populating those missing resistors to restore the ac request functionality. In the 12576106 PCM, on the backside, immediately to the right of the 100 kohm resistor there appears to be a capacitor to gnd. In the other PCM, immediately to the right of the missing 100 kohm resistor there is instead another resistor.

I still could not find where pin 17 leads to ultimately. Presumably, at some point it finds its way to the main CPU.

The IAC board uses an Intel flash, whereas the non-IAC board uses an AMD flash.

[Neukam]

Nice work. I don't have the time to convert the bins for you today. I'll try to get them for you tomorrow

[rocketmench]

Updated my document a bit to clarify a little. I also added the actual circuit for analog AC request as I now know it. I was able to find the "destination" of the C2 pin 17. It goes a chip labelled "203 466", pin (I think) 8. Without a data sheet, which I could not find, I have no idea what the function of that chip is but it has the same foot print of the 11124 466 chip which is apparently a "datalink controller" at this PCM hacking link: https://www.thirdgen.org/forums/diy-prom/507563-pcm-hacking-101-step.html.

To sum up, if one were daring, one could populate the missing 3k and 100k resistors, find out the value of the missing capacitor, and replace the 10k resistor with the cap to restore ac request functionality to the pcm's without that capability.

[Neukam]

Updated my document a bit to clarify a little. I also added the actual circuit for analog AC request as I now know it. I was able to find the "destination" of the C2 pin 17. It goes a chip labelled "203 466", pin (I think) 8. Without a data sheet, which I could not find, I have no idea what the function of that chip is but it has the same foot print of the 11124 466 chip which is apparently a "datalink controller" at this PCM hacking link: https://www.thirdgen.org/forums/diy-prom/507563-pcm-hacking-101-step.html.

To sum up, if one were daring, one could populate the missing 3k and 100k resistors, find out the value of the missing capacitor, and replace the 10k resistor with the cap to restore ac request functionality to the pcm's without that capability.

My guess is the resistor that is in place of the the capacitor is there just to keep the unused input low. The 3k is a pull down and the 100k resistor and capacitor are probably for debounce. I think there's a very high probability that adding those components will enable the functionality. I'm still surprised that they weren't all populated the same. It's probably less than $.02 worth of components. I'd try it but I don't have a vehicle to test on. My van is 0411 swapped, but I haven't done a 24x crank trigger yet and I haven't installed A/C yet. The plan is to install the 24x reluctor, LS coils, P59 and DBW. So many things on the to do list.

[Neukam]

It looks like I'm not going to be able to get those bins converted to HPT today. I can't find my HPT dongle. I think it may have fallen out the door of my step van :(

[Neukam]

It looks like I'm not going to be able to get those bins converted to HPT today. I can't find my HPT dongle. I think it may have fallen out the door of my step van :(

Nope, I found it. Yay!

[Neukam]

I think you may have sent me the wrong file. The 2GCEK file is from a 2003 Silverado with a 4.8L and both files have OS 12579405

[rocketmench]

Yes, you are right. I messed up. I have 4 PCM's and bin's and I mis-read the name. Here's the one from the 2004 Sierra that provided the engine I want to put in my 68. Now, what I found from TunerPro is that it's not a 2004 Sierra VIN, it's a 2004 Silverado VIN in the OS. Not sure if the PCM got replaced at some point or if the guy who undid the vats changed something on me.

[Neukam]

Here you go

[Neukam]

I found an XDF for 12587603 on NSFW's Github (https://github.com/LegacyNsfw/12587603) that has the A/C System type defined. I haven't checked it to know if the checksum is calculated properly. Be sure to verify it before flashing.

[rocketmench]

Well, this is great! If that xdf is good it solves all my problems!!! Thank you!

I'll try to set up an experiment to determine the value of that unknown capacitor. The engineer in me is itching to see if I can actually convert a "no analog ac request" pcm. Since I have an extra unit from the junkyard...

[Neukam]

I'm pretty sure it's just for debounce, so I don't think the exact value is critical. Maybe something between 0.2uF and 0.5uF? You could probably just add the resistors to test the input. Let us know what you find. It might be a good idea to start a thread detailing the hardware differences to make the information easy to find.

[flaco]

I've tried to delete my vats on a 2005 PCM OS#12592122 and cannot find any Xdf that match it. does anyone know where i can find one or if anyone has the same os# with any success any information is appreciated.

[notb]

A 2000 model year 7.4L would have been paired with a 4L80 transmission, and would have used the older "Black Box" Vortec PCM. This was the final model year for the 7.4L, and they never used the later LS1 (P01) PCM - sometimes referred to as an 0411 PCM - so there is no OEM wiring harness available that had a P01 PCM.


This brings up a question re my 2000 Camaro PCM, which according to the hptuners scanner is a P01 (it says "ECM: 10, VPW - P01"). This is the original PCM that came with the car (which I bought new in 2000, so it's definitely original). But supposedly 2000's did not have the 0411 PCM, so wondering what I really have. I was considering getting a 0411 just for the supposedly faster cpu (compared to the 99-00 PCMs). It is running the correct OS for 2000 (9381344), which I plan to replace with an 02 OS (12212156).

[B52Bombardier1]

I have no definitive proof but I've heard that the only difference between a P01 "896" PCM and a P01 "0411" PCM is that the 0411 runs streaming PID's for logging a little faster. I have several of each here and yea, I guess I can see that but it can't be much of a difference.

They both seem to be about the same. What does the hardware sticker on your PCM say? Look at the last three or four numbers.

Rick

[notb]

OK thanks, that clears it up, so P01 can mean different actual generations of boards, and I must have an 896 not an 0411.

[Gus1958]

I found an XDF for 12587603 on NSFW's Github (https://github.com/LegacyNsfw/12587603) that has the A/C System type defined. I haven't checked it to know if the checksum is calculated properly. Be sure to verify it before flashing.

Guys, i downloaded this XFD, i would like to use my ECM to control my AC, however comparing this xdf with the one used on this site 12587603 the values in the VE table show up different using the same BIN file. Am i missing something??

[kur4o]

Guys, i downloaded this XFD, i would like to use my ECM to control my AC, however comparing this xdf with the one used on this site 12587603 the values in the VE table show up different using the same BIN file. Am i missing something??

Check here (http://www.gearhead-efi.com/Fuel-Injection/showthread.php?9616-New-LS1-Tuning-Tool-Universal-Patcher)

and don`t forget to add a review when you are done.

[cb_cyclone]

*** Moderator *** - please sticky this thread so that people may more readily find it

Over two years ago, I posted a couple of XDF files for use with TunerPro editing software, specific to the LS1 type PCM. Below is a link to my original thread:

http://www.gearhead-efi.com/Fuel-Injection/showthread.php?6086-TunerPro-comprehensive-XDF-for-0411-PCM-with-Checksums

I am not going to revisit the comments made in the original thread, nor the number of times that “free” LS1 flashing software has failed to materialize. I am cautiously optimistic that this may finally be on the horizon. Please read the thread linked below:

http://www.gearhead-efi.com/Fuel-Injection/showthread.php?7068-Opensource-LS-Flashing(It-s-Closer-Than-You-Think)

A hard working group of enthusiasts is attempting to bring a no cost LS1 Flash Tool into existence. Given this development, I went back to creating more XDF files for LS1 type PCMs. These XDFs are based on the original work of Dimented24x7, and the disassembly that he shared freely.

This disassembly allowed me to create a template for basic tuning (enough functions for an enthusiast to tune their own PCM). Each subsequent XDF was based on this template and disassembly - the same way that commercial tuning software companies would have developed their product.

The attached instructions (PDF) below have been updated from the 2016 version.

A new feature is the “Operating System” button, near the bottom of the Parameter Tree. This will show you the Operating System of the LS1 type PCM BIN file that you have opened. No matter which of the accompanying LS1 XDFs that you have currently selected for use with TunerPro, the Operating System will ALWAYS be correctly displayed - for all 512Kb and 1Mb LS1 type PCMs.

This feature will help ensure that you select the correct XDF for editing your BIN file. This is how commercial tuning software works. It determines the Operating System in use, and then automatically loads the corresponding editing file. You must load the corresponding XDF manually - but the concept is the same.

Please read the attached instructions. Then download both of the Checksum Plugins (512Kb and 1Mb), and place them into the TunerPro folder on your computer, as described in the instructions.

After this has been done, download the XDF files from the posts below.

*** Note: I will update posts #2, #3, and #4 below with new XDFs as these are developed. ***

Thx LRT, I've been able to read, edit, & save my bin after following these tips. Going to write now. Thx again.

[jay94]

this is a big save for me thank you

[kur4o]

In case anyone needs the NOW missing files.

I think they all come from this thread.

Too bad the captain abandone the ship. So don`t expect any support for the files. Use at your own risk.

If LRT wants the files down, I will post them in another thread.

Good news is once something is uploaded on the web, you can`t take it down[delete] like it or not, it stays there.

Pay respect to the author and give him some credits for the hard work.

[NSFW]

Thanks, kur4o.

I think LRT's XDFs were all mirrored to GitHub as well. Two people have been maintaining repositories of every XDF they could find:

https://github.com/Snoman002/Engine-Tune-Repository-TunerPro-EFIlive-TunerCat/tree/master/General%20Motors

https://github.com/BoredTruckOwner/LS_Based_Engine_Repository

I haven't compared them against the files that LRT posted here, but I'm pretty sure I saw LRT's XDF for my C5Z in both repos.

Anyone know why he deleted his posts?

[brainanderson26]

Hey new to the tuning with tuner pro just here to say hey I reckon this is what I have to do to keep my account up