PDA

View Full Version : Low-High Spark tables...



LS1_Dragster
June 26th, 2008, 06:17 AM
If you put the same numbers in both tables will the computer still monitor spark knock?

I beleive that if it did register knock that since both tables are the same the computer will not pull timing, is this correct? And will it still record knock?

The reason I'm asking is that at the track when I get on the T-brake and 2-Step the computer registered knock and it pulled timing for the entire run even though it stopped registering knock after that point. I do not want this to happen yet I still want it to record if there's any knock.

Lee

BlackGMC
June 26th, 2008, 06:32 AM
I believe you will still retard the timing, making both of those tables the same I don't think it will accomplish what you want... Check out table b6205

LS1_Dragster
June 26th, 2008, 11:03 AM
It says in power enrichment mode, I beleive that with speed density mode it never gets in PE mode, I think....

BlackGMC
June 26th, 2008, 11:11 AM
I run SD mode (cos3) and I have PE enabled.... You just have to have it enabled...

5.7ute
June 26th, 2008, 01:03 PM
Setting your low & high octane table to the same values will not prevent knock retard as such. These tables are to allow the engine to learn away from the knock threshold when bad fuel/ lower octane fuel is used. The percent of each table used can be logged with the ASPARK pid.
Knock retard is set from B6203 etc.
I would only be playing with these settings with knock phones on the dyno to prevent engine damage.

johnv
June 26th, 2008, 02:15 PM
It may pay to log all the spark retard pids to see what exactly is pulling the timeing, May be burst knock due to higher than expected airflow, which can be removed in the tune B6212.

Also increase the knock recovery rate B6207 .

charcold-bowtie
June 26th, 2008, 03:42 PM
I would go ahead and zero out burst knock at the appropriate temp range. Also what does it mean to quit registering KR. Like the scanner didnt show KR but timing was being pulled from something else?

LS1_Dragster
June 27th, 2008, 02:30 AM
Thanks guys for the help.

I changed both maps to be the same last week and when I went back to the track there was no activity on the knock sensor, KR was 0 the entire runs. So either the problem was fixed and there's no knock or by changing both maps to be the same numbers disabled the KR. Maybe tonight I'll throw more timing in and see if it registers any knock.

Lee