Yes that is correct, you'll have to tune the pcm
Printable View
Thanks for the help.Quote:
Yes that is correct, you'll have to tune the pcm
Would I be able to save my .bin file and revert back to the 9381344 OS and the "safe tune" if I needed?
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?
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.
Using Tuner pro to tune. Have had zero problems using it with my current pcms.
Thanks mate. Any help would be appreciated.
So did you have any luck?
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.
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
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-Inj...ll=1#post73585
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.
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.
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.
'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.
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.
Attachment 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
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?
ThanksAttachment 14861
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
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.
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.
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 "?".
Attachment 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
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.
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:
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.
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.
I picked up my obdlink SX cable for $20 off Amazon. Why mess with soldering over a $20 cable.
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/125933...master/Scripts
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=r00u...tnNyoqCoqPwFLe