Ls Droid P01/P59 Segment Swap Utility

[160plus]

I don't have the time to get over here very often as I maintain posts for Ls Droid on a number of forums and Facebook. However I'm in need of some help testing a new feature I've added in Ls Droid before I'm comfortable releasing it. This is the type of testing that's more then what the average person is going to be capable of testing. I've created a segment swap utility that allows changing segments of the calibration between the same base OS numbers. This would allow for things like turning an auto trans bin into a manual trans bin, changing out a 4l60E segment for a 4l80E and even changing engine size with out needing to manually copy over dozens of tables.

For example, take a 2002 F body bin file and change the transmission segments from a manual trans to a 4l80E.

Take a 2003 Corvette 5.7 file that's had a LQ9 swapped into it and copy the engine segment from the Yukon XL the engine came from into the Corvettes bin file with out needing to manually change a ton of parameters and rebuild the VE/Spark tables.

Maybe you need to change vehicle or fuel segments to work with your gas gauge in the perfect bin file you've found for your swap.

The possible uses are endless, now this is not the same as tuning but this does go hand in hand with tuning when your running a setup that would not have been created from the factory. The reason this needs to be tested by those with a bit more knowledge then your average Joe is there is the possibility that some segment or Os number may not work correctly. There are hundreds of possible combinations you could create and I just don't have the time to spend testing this from every possible way imaginable. Verifying segments were swapped correctly is very easy to do with commercial tuning tools and may even be possible using demo versions as all you would be doing is verifying the segment numbers are correct and the checksums are valid. Commercial tools will red flag a corrupted bin file as soon as it's opened.... where Tuner Pro doesn't know what its looking at and won't tell you if things are wrong. Files can also be verified manually using a HEX editor that all the data for a given section was copied over correctly and that the checksums all match up correctly between the bootblock and the segment(s) that were copied over.

Assuming every thing matches up the final test is flashing the new file as a calibration to a PCM. The reason you want to flash it only as calibration other then to save time is that IF for some reason there was an issue it's pretty simple to recover the PCM. If you write the entire OS and there is an error in the app with an odd ball segment that resulted in data going somewhere it shouldn't have recovery would be a lot more difficult.

This could also be verified using a BDM to write the altered file to the PCM, if there is an issue with the segment swap after the file is written the PCM would either fail to boot or would not be able to respond to mode 1 pid requests making it pretty clear that something isn't right.

I've personally built and flashed a couple dozen variations of some common OS's with out any issues so I'm fairly confidant that every thing is working correctly but its one of those things that if there is an error it's likely going to be a HUGE error that ends up bricking a PCM.

[PeterTremonti]

I was hoping this would come out before I get my new to me Yukon registered next year. I swapped in a 5.3 in for the blown 6.0 and just used the original intake and injectors. Everything else externally was swapped over as well. The engine seems to be running fine around the parking lot but I'm sure it'll be an issue on the highway once everything is ready to go. I'm assuming this would be a possible use of your software which has already helped recover a PCM or two of mine that I've been playing around with.