rusefi
/
rusefi-full
mirror of https://github.com/rusefi/rusefi-full.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Trigger setup in TS is highly confusing: hide operation mode from users? #4031

This commit is contained in:
rusefillc 2022-04-02 21:01:18 -04:00
parent 577b30c74a
commit e9aade8219
2 changed files with 2 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
firmware/integration/rusefi_config.txt
View File

@ -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;

1
firmware/tunerstudio/rusefi.input
View File

@ -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"