Nick
11-09-2008, 01:43 AM
I titled this thread to match the phrase that a frustrated user might search.
It's not usually a good idea to change operating sytems, and is often impossible (LBZ,LMM,'06LLY).
Here's some helpful information that should lessen the confusion.
What is an operating system? An operating system is the infrastructure of the tune, the skeleton that defines the code that processes the calibration and sensor inputs into something the truck can run (or operate) off of. The operating system is the most basic aspect of the tune file. Changing the operating system can only be done on LB7/LLY trucks with a full reflash, and cannot be done on the LBZ/LMM/'06LLY's unless you use a tech 2 or Mongoose cable. The operating system cannot be seen by the user. Note: Changing operating sytems may result in wierd codes (loss of communication), odd running behavior (ac, 4X4 not working, cruise, ect.), or no-start conditions. Avoid if possible.
What is a calibration? The calibration is the part of the tune that is displayed on EFILive's user interface. Notice that the size of the tune you load into the truck is significantly smaller in size than the one you read off the truck. That size difference is the operating system, and bunch of lame tables that Ross and Paul have kept behind the scenes to minimize the clutter and speed up reflashes. Essentially the calibration is the 'editable' part of the tune. The only part we see. The calibratoin is the part of the tune that defines how the truck runs as far as this basic tutorial is concerned.
What is a script? A script is a simple text file that defines a change summary. It's built by comparing one calibration (stock) to another (modified). The trick is that this comparison must be made between like operating systems. This simple file holds all of the information on how 'X-O.S./A-.cal' can be converted to 'X-O.S./B-.cal', or why the modified tune runs differently than the stock tune.
I want to use my friends tune! What you mean is that you want to apply your friends calibration to your operating sytem. Luckily this is a simple process. All you need to do is create a script of your friends tune and apply that change summary (run script) over your stock tune. Of course this only works for birds of a feather. Both trucks must share engine codes (LBZ/LBZ, earlyLLY/earlyLLY, LB7/LB7, LMM/LMM, and also '06LLY/LBZ).
Here are some links to using scripts. -> 1... (http://www.dieselplace.com/forum/showthread.php?t=194677)(full rundown) 2... (http://www.duramaxtuner.com/sites/default/files/Scripts_tutorial.pdf)(running scripts) 3...(8594LMM specific) (http://www.tutorials.duramaxtuner.com/New_OS_Changeover.html)
Things to look out for. Because you're dealing with two different operating systems, you may be dealing with a script that contains a summary of a table that doesn't exist in your tune. If this happens, one of two things could happen.
1. While running the script you get an error that says 'table xxxx not found' and then the script stops. To solve this, open the script file and delete the description row that contains all of the information about the table that caused the error. Then resave the script file and rerun it over your stock file. Rinse and repeat if necessary
2. While running the script you get an error that says 'table xxxx not found' and the script continues to run. If this happens the the changes to that table will not be applied to your tune from the original modified tune.
In the case of either of 1 or 2:
You'll need to do a manual comparison of the tunes to determine the utility of the table that didn't copy over, and if there is a similar table in your tune (possibly under a different name). With your newly scripted tune and the original modified tune open get clever and find that table! :). Copy it from the modified tune by hand and paste it into your recently scripted tune, adjust to fit if necessary. The axis' may not match up, or said table may not even be that important, it comes down the user to make the call.
I hope this information is helpful for new users, it's long - but comprehensive. If you get stuck on issues related to this thread, please post here so we can update things and make the process as smooth as possible.
Thanks,
Nick
It's not usually a good idea to change operating sytems, and is often impossible (LBZ,LMM,'06LLY).
Here's some helpful information that should lessen the confusion.
What is an operating system? An operating system is the infrastructure of the tune, the skeleton that defines the code that processes the calibration and sensor inputs into something the truck can run (or operate) off of. The operating system is the most basic aspect of the tune file. Changing the operating system can only be done on LB7/LLY trucks with a full reflash, and cannot be done on the LBZ/LMM/'06LLY's unless you use a tech 2 or Mongoose cable. The operating system cannot be seen by the user. Note: Changing operating sytems may result in wierd codes (loss of communication), odd running behavior (ac, 4X4 not working, cruise, ect.), or no-start conditions. Avoid if possible.
What is a calibration? The calibration is the part of the tune that is displayed on EFILive's user interface. Notice that the size of the tune you load into the truck is significantly smaller in size than the one you read off the truck. That size difference is the operating system, and bunch of lame tables that Ross and Paul have kept behind the scenes to minimize the clutter and speed up reflashes. Essentially the calibration is the 'editable' part of the tune. The only part we see. The calibratoin is the part of the tune that defines how the truck runs as far as this basic tutorial is concerned.
What is a script? A script is a simple text file that defines a change summary. It's built by comparing one calibration (stock) to another (modified). The trick is that this comparison must be made between like operating systems. This simple file holds all of the information on how 'X-O.S./A-.cal' can be converted to 'X-O.S./B-.cal', or why the modified tune runs differently than the stock tune.
I want to use my friends tune! What you mean is that you want to apply your friends calibration to your operating sytem. Luckily this is a simple process. All you need to do is create a script of your friends tune and apply that change summary (run script) over your stock tune. Of course this only works for birds of a feather. Both trucks must share engine codes (LBZ/LBZ, earlyLLY/earlyLLY, LB7/LB7, LMM/LMM, and also '06LLY/LBZ).
Here are some links to using scripts. -> 1... (http://www.dieselplace.com/forum/showthread.php?t=194677)(full rundown) 2... (http://www.duramaxtuner.com/sites/default/files/Scripts_tutorial.pdf)(running scripts) 3...(8594LMM specific) (http://www.tutorials.duramaxtuner.com/New_OS_Changeover.html)
Things to look out for. Because you're dealing with two different operating systems, you may be dealing with a script that contains a summary of a table that doesn't exist in your tune. If this happens, one of two things could happen.
1. While running the script you get an error that says 'table xxxx not found' and then the script stops. To solve this, open the script file and delete the description row that contains all of the information about the table that caused the error. Then resave the script file and rerun it over your stock file. Rinse and repeat if necessary
2. While running the script you get an error that says 'table xxxx not found' and the script continues to run. If this happens the the changes to that table will not be applied to your tune from the original modified tune.
In the case of either of 1 or 2:
You'll need to do a manual comparison of the tunes to determine the utility of the table that didn't copy over, and if there is a similar table in your tune (possibly under a different name). With your newly scripted tune and the original modified tune open get clever and find that table! :). Copy it from the modified tune by hand and paste it into your recently scripted tune, adjust to fit if necessary. The axis' may not match up, or said table may not even be that important, it comes down the user to make the call.
I hope this information is helpful for new users, it's long - but comprehensive. If you get stuck on issues related to this thread, please post here so we can update things and make the process as smooth as possible.
Thanks,
Nick