Spark & timing tuning help

MBT (Minimum spark for Best Torque) is the advance at which the engine makes peak torque for a given load and RPM; push past it and you lose torque AND gain heat and knock for nothing. Borderline spark is the calibrator's safety-limited table — it's the timing the PCM will actually run when conditions are good, set below MBT by a margin that protects against knock on the design fuel.

In HP Tuners VCM Editor, the main high-octane spark table is effectively your borderline map. There's usually a low-octane table the PCM blends toward when knock is detected, plus correction tables for IAT and ECT. Adding timing everywhere because "more is more" ignores that many cells are already at or near MBT — you gain nothing but risk. TuneVault looks at the shape of your changes and flags cells where you've pushed past the realistic MBT island for that load/RPM.

VCM Scanner logs knock retard per cylinder. A degree or two of transient retard on a heavy pull on pump gas is normal; sustained multi-degree retract that pulls timing back down toward the low-octane table is the engine telling you the cells you just raised are too aggressive. The right response is to pull timing out of the specific load/RPM cells that knocked — not to globally retard the whole map and not to ignore it.

Watch out for false knock: valvetrain noise, injector chatter, and accessory noise can trip the sensors, especially at high RPM. Real knock correlates with load, IAT, and fuel quality; false knock appears RPM-locked regardless of load. TuneVault reads your knock-retard channel against load and RPM and helps you separate a genuine detonation pattern from sensor noise before you start hacking timing out of a healthy tune.

Your high-octane table assumes a fuel quality you may not always have. Run 87 where the cal expected 91/93 and the knock sensors will drag you toward the low-octane map under load. Conversely, E85 and race gas tolerate far more advance — but only verify that with knock data and a wideband, never by assumption.

Intake air temperature matters just as much. The IAT spark-retard table pulls timing as intake temps climb because hot air is more knock-prone. On boosted and heat-soaked setups this table is a primary safety device — if someone zeroed it out to chase dyno numbers on a cold engine, the car is a time bomb on a hot day in traffic. TuneVault specifically checks whether your IAT retard table still has meaningful pull-out at high temps, and warns if it's been flattened.

Boost dramatically raises cylinder pressure and knock tendency, so safe boosted timing is far less than safe N/A timing at the same airflow. A common, costly mistake is leaving the high-load region of the spark table at N/A values after bolting on a blower or turbo. As boost and load climb, timing should taper down, and the more boost, the more it tapers.

There is no universal "correct" boosted timing number — it depends on compression, fuel, intercooling, and chamber design. The disciplined approach is to start conservative, add small increments, and stop the moment knock retard appears or torque stops climbing (that's MBT). TuneVault flags high-load cells that still carry naturally-aspirated advance and reminds you that it cannot and will not promise a horsepower figure — it keeps you conservative and tells you to verify fueling with a wideband before every boost pull.

Timing is the one area where ego costs engines. Change a region, log it, look at knock retard and torque, then decide. If torque didn't move, you were at MBT and the timing was wasted risk. If knock appeared, you went too far. This loop — small change, datalog, evaluate — is the whole discipline.

TuneVault reads your before/after spark cells and your Scanner knock/torque traces from screenshots and tells you whether your last change actually bought anything or just added risk. We're a copilot for that loop, not a substitute for a professional tuner on a dyno with a knock-ear and a wideband.