I have read everything in this post https://www.thirdgen.org/forums/diy-...on-lv8-vs.html and I am still not understanding why my ARAP $6E bin is like it is(this table is as it was when downloaded, I haven't changed it). It doesn't seem to follow the logic in the referenced post and I need to understand what if anything it is doing to the main SA. Bottom line, I don't want it to do anything right now while I am working on the Main SA table. Already zeroed PE spark and I need to know what this table is doing. I lowered the disable temp but am not sure if that disables input from this table or not.

 

You're likely seeing cold spark (which is different than coolant correction). Cold spark pulls the spark advance from main table's high load column and coolant correction may still be applied to this new value. Most $6E bins have uncoordinated cold spark and coolant correction leading to weird spark behavior during warm up.

Note: the cold spark disable parameters are often mislabeled:
SCALAR: Cold Spark Disable Temp 130.10 Deg F

You can see an example of both cold spark and coolant correction happening here: https://datazap.me/u/tequilaboy/apyp...mark=1728-1799

Cold spark is acting to reduce the spark advance while coolant correction is adding spark advance (which is screwy). A huge surge occurs when the cold spark is disabled just above 130.10 °F (due to the sudden increase in spark advance) just before the coolant correction ramps down to zero at 134 °F.

 

I will look at the scalar you mentioned. Is there a way to stop "spark correction lv8 vs coolant table" from making changes. I would have thought from the other post that I would simply enter 20.4 in all of the cells to match the bias and it basically makes the table inactive but was confused that the cells didn't match what RBob explained. Looking at your data log raises another question, my adv vs crank angle is smooth but I noticed that when there is knock induced retard that it isn't reflected in the data trend for spark like assumed it would be. That made me think I might not be able to see the change in timing reported in the data log trend, but from looking at yours I should. I do see changes in timing just not knock related retard.BTW I am not totally new to tuning but definitely low on the learning curve. Thanks for the help.
This one? \/

 

First topic: Setting the (raw) coolant correction table to the bias value (20.04) across the board should zero the coolant temperature based spark correction (not considering start-up spark advance vs coolant temperature). Note: this item may be xdf dependent. If the xdf is subtracting off the bias value (as it appears to be in your table), then set the table to zero. Check the xdf conversion tab.

Second topic: There are two parameters for disabling cold spark (ARAP values shown below):

;--------------------------------------------------
; DISABLE COLD SPARK
;--------------------------------------------------
LC02B FCB 113 ; If coolant temperature > x, DISABLE cold spark
; ((Val+ 40)*256/192)
LC02C FCB 255 ; If coolant temperature differential from start up coolant temperature > x, DISABLE cold spark
;(Val * 256/192)

Cold spark is equal to the main table's 208 load column value for a given rpm.

Third topic: There is no knock retard present in the data that I have posted. What you see is the effect of cold spark (main spark 208 load dependent and rpm dependent), and coolant compensation (coolant temperature dependent and load dependent). Note: the main spark advance table has been edited a bit from the APYP base, so the data is not 100% reflective of original APYP settings.

Here's another log showing the effect of cold spark/main spark only with no coolant correction (with cold spark disable temperature set to 112.55 °F like ARAP): https://datazap.me/u/tequilaboy/cold...mark=1297-1403

 

Thank you! This fills in the blanks in my understanding. I have some adjustments to make to my tune now!.

 

Regarding the bias (20.04), check your xdf file to see if the bias is subtracted off in the conversion tab, or if the table is displaying the raw value without bias and edit accordingly in order to zero. This may be another source of confusion.

 

Here is the conversion tab. Wasn't obvious to me what it is referencing.