From e9aade821988483e5dd4d8fda6a246c05f37924e Mon Sep 17 00:00:00 2001 From: rusefillc Date: Sat, 2 Apr 2022 21:01:18 -0400 Subject: [PATCH] Trigger setup in TS is highly confusing: hide operation mode from users? #4031 --- firmware/integration/rusefi_config.txt | 2 +- firmware/tunerstudio/rusefi.input | 1 + 2 files changed, 2 insertions(+), 1 deletion(-) diff --git a/firmware/integration/rusefi_config.txt b/firmware/integration/rusefi_config.txt index 6d42cf739f..5549f4d3b9 100644 --- a/firmware/integration/rusefi_config.txt +++ b/firmware/integration/rusefi_config.txt @@ -1036,7 +1036,7 @@ bit useFSIO5ForCriticalIssueEngineStop;Sometimes we just have to shut the engine bit useFSIO4ForSeriousEngineWarning;Sometimes we have to miss injection on purpose to attract driver's attention bit unusedBitHere2 bit unusedBitHere3 -bit unusedBitHere4 +bit skippedWheelOnCam,"On camshaft","On crankshaft";+Where is your primary skipped wheel located? adc_channel_e hipOutputChannel; switch_input_pin_e acSwitch;A/C button input; diff --git a/firmware/tunerstudio/rusefi.input b/firmware/tunerstudio/rusefi.input index 623e003008..6062fe2c77 100644 --- a/firmware/tunerstudio/rusefi.input +++ b/firmware/tunerstudio/rusefi.input @@ -1907,6 +1907,7 @@ cmd_set_engine_type_default = "@@TS_IO_TEST_COMMAND_char@@\x00\x31\x00\x00" ; see also in firmware '[doesTriggerImplyOperationMode]' tag field = "Operation mode / speed", ambiguousOperationMode + field = "Skipped wheel location", skippedWheelOnCam field = "#Please use '4 stroke with cam' only if primary trigger sensor is actually on cam" field = "#Separate cam input not part of Trigger Pattern does not count here" field = "With VR sensors only rising edge has reliable position"