trigger central: slice 9007 to 9007/9008 erorrs

CUSTOM_PRIMARY_BAD_TOOTH_TIMING_EARLY
CUSTOM_PRIMARY_BAD_TOOTH_TIMING_LATE

Author: dron0gus

firmware/controllers/algo/obd_error_codes.h

@@ -2150,7 +2150,9 @@ enum class ObdCode : uint16_t {
 	CUSTOM_PRIMARY_DOUBLED_EDGE = 9006,
 
 	// A trigger tooth arrived at an unexpected time
-	CUSTOM_PRIMARY_BAD_TOOTH_TIMING = 9007,
+	CUSTOM_PRIMARY_BAD_TOOTH_TIMING_EARLY = 9007,
+	CUSTOM_PRIMARY_BAD_TOOTH_TIMING_LATE = 9008,
+
 
 	/**
 	 * This is not engine miss detection - this is only internal scheduler state validation

firmware/controllers/trigger/trigger_central.cpp

@@ -739,6 +739,8 @@ bool TriggerCentral::isToothExpectedNow(efitick_t timestamp) {
 			angleError += cycle;
 		}
 
+		// positive value - tooth received earlier than expected
+		// negative value - tooth received later than expected
 		triggerToothAngleError = angleError;
 
 		// Only perform checks if engine is spinning quickly
@@ -768,7 +770,8 @@ bool TriggerCentral::isToothExpectedNow(efitick_t timestamp) {
 			// TODO: configurable threshold
 			if (isRpmEnough && absError > 10 && absError < 180) {
 				// This tooth came at a very unexpected time, ignore it
-				warning(ObdCode::CUSTOM_PRIMARY_BAD_TOOTH_TIMING, "tooth #%d error of %.1f", triggerState.currentCycle.current_index, angleError);
+				warning((angleError > 0) ? ObdCode::CUSTOM_PRIMARY_BAD_TOOTH_TIMING_EARLY : ObdCode::CUSTOM_PRIMARY_BAD_TOOTH_TIMING_LATE,
+					"tooth #%d error of %.1f", triggerState.currentCycle.current_index, angleError);
 
 				// TODO: this causes issues with some real engine logs, should it?
 				// return false;