Spark Timing Adjustments Based on Data Logs
I plotted my spark knock retard events from my data logs. Below is RPM vs MAP (kPa) x Spark Knock Retard (degrees). The plot contains over 15,000 data points from my log of over 30,000 data points (i.e., over half of my data points contain knock retardation).
Based on this info, from 50-85 kPa and 2000-3500 RPM, I am getting between 2-3 degrees of knock retardation. Therefore, should I retard my timing in that region by the corresponding degrees of knock retard (i.e., the timing advance number would be smaller)? Or perhaps, retard the timing by half of what is indicated in those regions?
Am I thinking about this correctly? Or should I just leave it alone and let the ECM sort it out?
This is with E10 91 octane. This graph gets off the charts (each retard event is about 2 degrees higher, max of around 6 degrees) on non-ethanol 87 (the only non-ethanol in my town).
FWIW, the rear cylinder has about half the degrees of retard as the front cylinder.
As far as ensuring VE tables are calibrated, all I have done is "auto tuned" 4 sessions (~30 minutes each) in a row one afternoon. I did as many sessions as were necessary to achieve <5% max change. Out here in BFE, TX, in one session I'm able to get 99 hits on every conceivable cell I need to out on public roads and never see another vehicle. So, I got 99 hits on 99% of cells in a session, load that auto tuned tune, and repeat for a total of 4 times to achieve <5% change.
How do you know if pulled out too much timing? What are the consequences/effects off pulling out too much timing?

Trending Topics
The Best of Harley-Davidson for Lifelong Riders
I haven’t loaded the tune. Just played around in Powercore.
Last edited by BrandonSmith; Feb 20, 2024 at 09:25 AM.













