What could cause timing to be pulled with no KR detected?

[ArKay99]

I was at the dyno yesterday and was tuning in my PE. I was geting some knock detection ~4.5 degrees so I added some Torco. The knock detection went to 0 and stayed there. However, I am showing between 25.5 and 26 degrees of timing in PE until rev limit. I have my high octane table at 28 degrees in the PE area and the low octane table is at 24 degrees. Intake temps were in the 32C range and that is zero in that area. Burst Knock Delta is set to 0. I was in cell 22 when monitoring this.

Any ideas?

[rally1]

Hi there, where you monitoring you Adaptive octane scalar pid ? if you have had knock it will more the likely be below 100% you can copy your high map into your low map and recheck to see if that was the cause, our use COS3 to set the scalar to 100%.

[ArKay99]

I was thinking something like that could be happening, but I wasn't sure what pid if any would show me. I am using a 2002 Z06 OS. I know there is an adaptive spark pid, but I wasn't sure how it monitored the tables. I thought that it just told you if you were in the high or low octane table, but if holds some value as an upper limit that would explain that.

If that is the case the next question would be, how would I go about 'zero-ing' this value since I was no longer monitoring knock due the use of additional octane?

[rally1]

The adaptive spark pid indicates where the timing is being calculated between the high and low spark maps (interpolation) 100% means it using the high map, 0% its using the low map, 50% is half way between the two etc etc.

If you no longer have knock and the adaptive spark is below 100% just reflash the tune and it will reset to 100%

Or you can install a custom operating system and then command 100%, the down side to this is you then have no adaptive spark and only knock retard

[ArKay99]

Hmm, I was reflashing as I was tuning in the PE. Well, We'll never know because I wasn't logging that pid anyway.
However I will be going back in the early fall to do some more tweaks and I can monitor it then.

[Kevin Doe]

If you set burst knock delta to zero, wouldn't that cause you to always have burst knock active? It says if the delta value is exceeded then burst knock will be active. If you set it at zero, any throttle movement will cause it to be in burst knock. I think you need to increase this value, not set it to zero.

[ArKay99]

If you set burst knock delta to zero, wouldn't that cause you to always have burst knock active? It says if the delta value is exceeded then burst knock will be active. If you set it at zero, any throttle movement will cause it to be in burst knock. I think you need to increase this value, not set it to zero.

Again, It seems misread the explaination, but the values in that table are from the OEM LS6 calibration. I didn't put them there. According to the pid description this must have been what was causing the lower than commanded timing.

I'm going to have to look at this pid while logging on the dyno to see what different values do.

[azzhauler]

I have a similar question. I already set my high and low timing tables the same, and set my wot region to a flat value (14) and set my base spark in gear also (20). In my logs with the EST pids selected it shows 14.2* base spark, 9.x* Brake Torque Retard, 4* EQ ratio spark (wtf is this btw?), and 18.2* for run spark. The timing for cylinder 1 shows 17.5* though, and none of this matches the tables in the tune. Any ideas how to find my timing?


Side question: any ideas for reducing the lean spike on tip-in?