Digital Immigrant

what your looking for is *spark advance *
-Spark: spark advance = this is what the engine is actually running
-spark: base = the base table with no modifiers
-spark : you can find alot of the spark modifier tables in the datalog

I just looked and at WOT you are commanding 33* of advance thats too much if your not running premium

Since you are just starting out I figured i would help you out a bit... hope you dont mind.

When you load this tune in it will give you a chance to look at the differences between the two.... you will notice most of the changes are to how the tables are laid out in the rpm colums and kpa rows.... I moved them around to give you more detail in the areas you are in most as you drive. I also loaded in an ignition table I use in my base tunes.

Its pinging under low load? As in cruise conditions? If this is the case we need to verify your base timing.
I left my PC at work I will take a look again tomorrow and see what may need changing.

It appears that you are never getting above 45% TPS or no more than about half throttle, if this is the case great. If you are planting your foot to the floor and only getting 45% then the TPS sensor needs to be recalibrated.
I attempted to find an ignition load table from a truck ecu for you but i could not seem to find one.... I simply removed timing to give a total of about 26* in the high load areas of your ignition map to stop the pinging... this is good and gives me a baseline for 87 octane tunes once we get it figured out.
While i was making the changes and looking through the log files I also played with the idle settings to try and steady the idle more for you, I made two versions of the tune. Both are REV 1.1.0 however one tune is setup for closed loop idle and the other open loop [you will see open loop on the file name]

in case you dont have MLVHD i figured i would share some of the things i look at when judging a tune...


This is a Histogram, I am currently looking at what 'cells' or blocks your engine was running in. This table is setup exactly like your VE1 fuel table, i did this by importing your table after i loaded your tune into MLVHD. The Z axis on this table is set to AFR ERROR this is a custom field i created to see how far off your fuel is in each cell, it divides AFR1/AFR TARGET1 to give me a multiplier value. This value can then be used by multiplying into the VE table to reach the desired AFR, less than 1 gives you a smaller VE number reducing fuel and greater than 1 increases the VE value. This is the method i use to adjust fuel on High powered engines where a guess could be catastrophic.



This is a scatterplot, it takes all the information and lets you plot it out on a graph... I love this tool, on the left i am viewing the effective used area of the engine. Notice that there are areas that the plot never reaches, this allows me to figure out where to focus my attention when tuning a fuel map.
The plot on the right is how i determine a decent tune from a rough one, once the parameters are set i also turn all the filters on to get rid of the abnormal events. This should look like a straight line from one corner to the other, based on this information your tune is in great shape! only a little bit of work left to do to the fuel and your good to go.

Thats looking better, however there is an issue with the way the idle advance is setup in your tune. I changed it in this version if you want to check the difference out.

Hey i was gonna take a look and suggest some changes but i think you uploaded the wrong tune file to go along with the datalogs. Alot of gains to be made still with some timing {increase} and AFR table changes. the tune looks close its just the final touches now.

Have you been using autotune?

What do you have it set to? At this point it should be 'very hard'.

Ok so try this one out and dont do any auto tune, Just drive it and datalog get a good long log file and send it to me with no changes.

look in on the thread i made for the new channel and give some input on what you want to see! thanks

yes roughly 20+ mins of driving the longer the better, even if you get multiple files i can load them all as one file