custom skipped wheel could be located on camshaft fix #4377

firmware/CHANGELOG.md

@@ -35,6 +35,7 @@ Release template (copy/paste this for new release):
  - Many drop downs menues are now sorted #4339
  - rusEFI TS plugin launcher fixed
  - Console autoupdate error dialogs #4352
+ - custom skipped wheel could be located on camshaft #4377
 
 ### Removed
  - ICU trigger input logic since it is unused in any current ECU #639

firmware/tunerstudio/rusefi.input

@@ -1976,7 +1976,7 @@ cmd_set_engine_type_default					= "@@TS_IO_TEST_COMMAND_char@@\x00\x31\x00\x00"
 
 		; see also in firmware '[doesTriggerImplyOperationMode]' tag
 		field = "What kind of engine",                  twoStroke
-		field = "Skipped wheel location",               skippedWheelOnCam, { twoStroke == 0 && (@@TRIGGER_TYPE_WITHOUT_KNOWN_LOCATION@@) }
+		field = "Skipped wheel location",               skippedWheelOnCam, { twoStroke == 0 && (trigger_type == @@trigger_type_e_TT_TOOTHED_WHEEL@@ || @@TRIGGER_TYPE_WITHOUT_KNOWN_LOCATION@@) }
 		field = "With VR sensors only rising edge has reliable position"
 		field = "use only rising edge",					useOnlyRisingEdgeForTrigger    
 	    field = "!Reminder that 4-stroke cycle is 720 degrees"

java_tools/configuration_definition/src/main/java/com/rusefi/trigger/TriggerWheelTSLogic.java

@@ -46,6 +46,10 @@ public class TriggerWheelTSLogic {
 
         });
 
+        /*
+         * these are templated into rusefi.input file
+         * note that TT_TOOTHED_WHEEL is not mentioned in the meta file, we handle it manually right in rusefi.input file
+         */
         variableRegistry.register(TRIGGER_TYPE_WITHOUT_KNOWN_LOCATION, triggerTypesWithoutKnownLocation.toString());
         variableRegistry.register(TRIGGER_TYPE_WITH_SECOND_WHEEL, triggerTypesWithSecondWheel.toString());
         variableRegistry.register(TRIGGER_CRANK_BASED, triggerTypesCrankBased.toString());