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.Originally Posted by cobra30689
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.
1995 GMC K2500 SUBURBAN 2001 LB7 DURAMAX/ALLISON swap, mostly stock, tuned by me with EFILive
1999 Tahoe 2 door 2X4, 5.7l with 0411 swap, and marine intake
'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.
Last edited by CarlsLQ9SS; 11-04-2019 at 05:09 AM.
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.
Thank you, very much appreciated!
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
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.
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
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.
Last edited by tf3n; 04-20-2020 at 02:54 AM.
So what would I need hardware-wise to use this for my 02 2500HD 8.1/Allison?
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
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.
Last edited by Hey_Allen; 06-23-2020 at 09:41 AM.
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.
P01_P59_Ground 1 second to recover.jpg
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
Posting Permissions
Reply With Quote
Bookmarks