Free LS1 Tuning Software (all you need is TunerPro)

[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?
ThanksScreenshot_20191201-161343.jpg
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 "?".

Screenshot_20191203-142715.jpg

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