From be21105b7f20f5ff26fc32f54d4e45a2f1231757 Mon Sep 17 00:00:00 2001 From: rusefillc Date: Sat, 2 Apr 2022 22:08: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 | 3 ++- 2 files changed, 3 insertions(+), 2 deletions(-) diff --git a/firmware/integration/rusefi_config.txt b/firmware/integration/rusefi_config.txt index 5549f4d3b9..97eb9a257a 100644 --- a/firmware/integration/rusefi_config.txt +++ b/firmware/integration/rusefi_config.txt @@ -1035,7 +1035,7 @@ bit unusedBitHere1 bit useFSIO5ForCriticalIssueEngineStop;Sometimes we just have to shut the engine down. Use carefully! bit useFSIO4ForSeriousEngineWarning;Sometimes we have to miss injection on purpose to attract driver's attention bit unusedBitHere2 -bit unusedBitHere3 +bit twoStroke,"Two Stroke","Four Stroke" bit skippedWheelOnCam,"On camshaft","On crankshaft";+Where is your primary skipped wheel located? adc_channel_e hipOutputChannel; diff --git a/firmware/tunerstudio/rusefi.input b/firmware/tunerstudio/rusefi.input index 6062fe2c77..a6f904f1ff 100644 --- a/firmware/tunerstudio/rusefi.input +++ b/firmware/tunerstudio/rusefi.input @@ -1907,7 +1907,8 @@ 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 = "What kind of engine", twoStroke + field = "Skipped wheel location", skippedWheelOnCam, { twoStroke == 0 } 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"