tuning help?

[sprattzvx]

Hey drift. You sure yous didnt change anything else and forget? Theres a few other tables that affect this like pe spark correction i think. You should load the last good bin before you changed the advance in the compare bin function and compare all the spark related funtions. Just a thought.
Theres gotta be a basic logical explanation shit just doesnt happen by itself.

[drift-it]

yer i;ve done that. the only factor i've changed is the timing in main advance. i had 8degrees and it was 12-13 degrees. so i've put it back to what it was and ill go for another log tomorrow and see if it occurs again.

i found the knock detected bitmask in the dash function and when k/r occurs in the older logs i dont get actual knock. so thats a bonus i guess.

[The1]

ive had other trouble before with timing with other tunes where the low and high tables were set differently, ive always set them the same, so perhaps after 5000 set both low and high the same and slowly work up, see if it follows. it looks like it's the same apart from up top in the stock bin.

[drift-it]

it will be safe to set it the same just aslong as i keep my eye on k/r?

[The1]

id setup a history table to log the spark map, run the log with stock tables and kr, check the min or avg spark timing history table at the end and if it looks ok use that as a base spark map for hi/low and tune from there.

[drift-it]

i just thought of something i changed. may affect it may not. i modified the columns in both spark advance main tables to go up to 950mgc instead of 850. this automatically adjusted timing to 45degrees in the new columns but i adjusted it down to follow the timing pattern (i guess is a good description of it).

i've adjusted timing back to where it was to start with and will start again.

[VL400]

Editing/adding a column in the XDF does not give you extra code features If I understand correctly, what you have done is actually just edited data from the next table in memory. I would suggest downloading the original XDF and start again with a standard bin.

[drift-it]

so what happens past 800 or 850mgc? im going to do exactly that but im not sure what it will be say at 880mgc if the last known
column is 850?

[drift-it]

all back to normal. i just took 2 degrees of timing out of the area where i got the kr before.

[The1]

it just runs from the last column, also looking at your bin in the OP it's a bit messed up so yeh id be starting again, always compair your tune to a stock bin so you can verify what's changed and there are no errors.