If I advance the timing using Tweecer,should I increase Fuel Press or set richer?

Pokageek said:

No one responded to Methodical's question...

Searched on of Grady's posts:

"For a stable or consistent spark curve do this:

dizzy at 10
global scalar at 0
use base spark table only for tuning
kill altitude, borderline, & mbt spark tables
don't mess with any other spark tables at all

Just have several baseline dlogs of light load, mid load, & wot test runs before you make any changes. By baseline, I mean those dlogs will be what you compare your tweeced dlogs to.

I'd pull more than 2 out as that might not be enough to make a difference and if you pull too much you ain't gonna hurt anything but loose a bit of power. Try 6 and if that kills the ping thing, you may wanna put 2 more back in and try again ...... and maybe add in 1 or 2 more and try again..... you get the idea.

Just tune to what your combo likes .......
thats the Custom Tune part of Self Tuning."


..also, what is the timing after 5k rpm?

Click to expand...

I posted this about the 40*+ thing up top

in regards to the 40 or so degrees at idle and such, yes timing can be high at idle like if free revd'. I think the high mid load timing is also part of the timing strat. to use the EGR tables or be close to them assuming they work (and why the GT has a ping issue esp. with the EGR dissconnected but not turned off in the eec.).


after 5k I believe it is held to the same value as the 5k table...so if its set to 24* then you will have 24* at 6, 7, and 8k rpms...notice how the MAF value and others flatline at 5 or so and give ref. to 16k.

Pokageek said:

"kill altitude, borderline, & mbt spark tables" Does this mean ALL of the bdln tables? Just want to be sure you didn't meaN just the one. Thx.

Click to expand...

There is one main table that the others are based off, think of a ven(sp?) diagram that is sorted by only the numbers stored with all tables in use, the number used is the lowest value (the eec uses the lowest value)...soooo if table 1,2, and 3 are controled by a "master" table in that group of tables(they are) then the one table killed for each group is only needed to be killed or turned off...in a vague nut-shell.

base alt. the mbt spark, and boarderline you only need to kill the one table in each (or depending on what number of tables you are going to kill). The sub tables will be left out of the eec's process.

This post don't make sense ... even though I wrote it

the below info is ok and accurate

Pokageek said:

No one responded to Methodical's question...

Searched on of Grady's posts:

"For a stable or consistent spark curve do this:

dizzy at 10
global scalar at 0
use base spark table only for tuning
kill altitude, borderline, & mbt spark tables
don't mess with any other spark tables at all

Click to expand...

from this part of the post it seems like something is lost or missing

almost looks like someone has a prob with the ping thing, lol

Just have several baseline dlogs of light load, mid load, & wot test runs before you make any changes. By baseline, I mean those dlogs will be what you compare your tweeced dlogs to.

I'd pull more than 2 out as that might not be enough to make a difference and if you pull too much you ain't gonna hurt anything but loose a bit of power. Try 6 and if that kills the ping thing, you may wanna put 2 more back in and try again ...... and maybe add in 1 or 2 more and try again..... you get the idea.

Just tune to what your combo likes .......
thats the Custom Tune part of Self Tuning."


..also, what is the timing after 5k rpm?

Click to expand...

Grady

All you gotta do to kill the table is put the value of 55 in all cells

or

put 55 in all columns and all rows.

As for which tables you work with ........ do it like you quoted me to do in the above post.

Did that make sense? ......... lol

Grady

Everything about working with spark tables is in this very thread.

Just the basic info from this thread but never the less, here is a direct copy from the following peeps:

Greg

To use the base spark tables alone you will have to kill (or enter 55's into all cells) Alt. table, MBT table, and Boarderline table.

Dave

Only need to change one table -- the base spark table (leave the spark adder stuff alone). The values in the base spark table are for total timing -- they assume that you have set the distributor to 10* initial, I'd make sure you have it right at 10* before playing with the table values. For power tuning, you really just need to pay attention to the top row of values, for the highest load, because that's what will be used at WOT. Adjusting with the low-load values can have benefits but you really need to have a handle on what they're doing or it'll just get messy.

Grady

"For a stable or consistent spark curve do this:

dizzy at 10
global scalar at 0
use base spark table only for tuning
kill altitude, borderline, & mbt spark tables
don't mess with any other spark tables at all

Three different peeps basically saying the same thing.

Don't worry about adders, sub tables, or anything other than the big, main four spark tables.

Grady