PDA

View Full Version : EFI Scripts?



dhardy1357
March 9th, 2009, 05:40 AM
Can someone explain to me what scripts are and what they are for?

GMPX
March 9th, 2009, 09:44 AM
Used to automate tuning. It simply applies whatever changes you have in the script in to a tune file. Beats cut/paste from another tune file.

Cheers,
Ross

vortecfcar
March 9th, 2009, 10:31 AM
Just a copy and paste from my support forum..


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. 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! Smile. 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 Priegnitz

joecar
March 9th, 2009, 11:04 AM
Nick, thanks...:cheers:...added to collection of links to scattered tutorials.

dhardy1357
March 9th, 2009, 11:54 AM
ok im still kind of lost. let me tell you exactly what im tryin to do to see if this helps. i have the dsp2 switch with two tunes. i downloaded a tune off the internet that has different os#'s. i cant load for comparison my dsp2 and the tune i downloaded to see the differences because of the different os#'s. is this when i would use a script? i cant find out how to see the differences to know what to change in my dsp2 tune

joecar
March 9th, 2009, 12:50 PM
No, my understanding is the tunes you want to compare must be the same OS and have the same/compatible engine codes.

The only way to see differences is if both tunes are the same/compatible os/engine codes...

if you can view differences then you can generate a script...

if they are different then they cannot be compared (my simplistic understanding is the data field offsets/locations and formats/layouts are different relative to each file).

dhardy1357
March 9th, 2009, 04:05 PM
ok. someone gave me an idea and i figured out how to make it work...

i downloaded a stock tune that had the same OS# as the race tune i wanted to put in my truck. then i was able to load for comparison to see the differences. and then i just copied and pasted. thanks guys for all the help and advice

joecar
March 9th, 2009, 04:40 PM
You got it... the key is the same OS #.

mr.prick
March 9th, 2009, 05:03 PM
A great summary of what scripts are and how they work.
I recently started making my own scripts, and if you try to just make them
on your own with notepad they can be frustrating to format and run.
It is much easier for the first time user to let the software make it for you.

This thread is a perfect walk through for that.
Ok Guys, Scripts aren't THAT scary....
(http://www.dieselplace.com/forum/showthread.php?t=194677)
And the Script_tutorial.pdf (http://www.v2-duramaxtuner.com/Scripts_tutorial.pdf) should be saved in
C:\Program Files\EFILive\V7.5\Doc\Tutorials for future reference.

Post #3 (http://forum.efilive.com/showpost.php?p=89043&postcount=3) is all you need to know about scripts, thank you vortecfcar. :phatyo:

joecar
March 9th, 2009, 05:13 PM
Ok, added link into scattered tutorial links thread, thanks...:cheers:

vortecfcar
March 13th, 2009, 06:47 PM
Nick, thanks...:cheers:...added to collection of links to scattered tutorials.

Thanks Joe,

Glad to help :):cheers:

Wolfie
January 30th, 2010, 08:48 AM
Links seem to be broken... all of them...

mr.prick
January 30th, 2010, 08:56 AM
The Duramaxtuner link in my sig has the .pdf and other links in it.

joecar
January 30th, 2010, 11:21 AM
Links seem to be broken... all of them...Thanks for the heads up, I'm looking into it...

Wolfie
January 30th, 2010, 11:33 AM
ok, now some show up, but this one... Ok Guys, Scripts aren't THAT scary.... the pics are not there, and if you click on them it says no permission.

joecar
January 30th, 2010, 11:45 AM
ok, now some show up, but this one... Ok Guys, Scripts aren't THAT scary.... the pics are not there, and if you click on them it says no permission.You mean the link in this post (in the other thread):


A great summary of what scripts are and how they work.
I recently started making my own scripts, and if you try to just make them
on your own with notepad they can be frustrating to format and run.
It is much easier for the first time user to let the software make it for you.

This thread is a perfect walk through for that.
Ok Guys, Scripts aren't THAT scary....
(http://www.dieselplace.com/forum/showthread.php?t=194677)
And the Script_tutorial.pdf (http://www.v2-duramaxtuner.com/Scripts_tutorial.pdf) should be saved in
C:\Program Files\EFILive\V7.5\Doc\Tutorials for future reference.

Post #3 (http://forum.efilive.com/showpost.php?p=89043&postcount=3) is all you need to know about scripts, thank you vortecfcar. :phatyo:

I can't see them either, my login at www.dieselplace.com (http://www.dieselplace.com/) has stopped working... :nixweiss:

8100 Power
February 2nd, 2010, 03:22 PM
Here is one I made:

http://www.thetruckstop.us/forum/showthread.php?t=19257

Chevy366
February 3rd, 2010, 12:22 PM
Yeah 'scripts' are pretty handy , made life much easier .
Simple and easy to use , and saves time .

ARZ
March 13th, 2018, 06:06 PM
Is this really the case? I didn't see anyone directly comment on this. I ran a script, and only changed the lines other than the OS, will this work? They were both from an 06 LBZ.


No, my understanding is the tunes you want to compare must be the same OS and have the same/compatible engine codes.

The only way to see differences is if both tunes are the same/compatible os/engine codes...

if you can view differences then you can generate a script...

if they are different then they cannot be compared (my simplistic understanding is the data field offsets/locations and formats/layouts are different relative to each file).