f305db2575
* save changes * save changes * save changes * fix mistakes * try adding empty method * copy simpleTransmissionController to GM 4L6X controller * Import 4l6x header * add to makefile * fix whitespace * try enum class * change field name * change field name in rusefi.input * check for gear controller mode * add mode fields to catch if mode was changed |
||
|---|---|---|
| .. | ||
| docs | ||
| generated | ||
| translations | ||
| .gitignore | ||
| readme.md | ||
| rusefi.input | ||
| upload_ini.sh | ||
readme.md
TunerStudio
This directory contains the initialization and configuration files for the rusEFI interface to TunerStudio.
The primary contents are a set rusefi*.ini initialization files, used to
configure TunerStudio to setup and monitor a specific ECU board. These are
the only files a typical end user needs.
The translations directory contains non-English-language translations
for TunerStudio.
The initialization files are automatically generated from a combination of input files located both in this directory and in the board-specific directories .
rusefi*.ini files are generated based on the following four inputs:
rusefi_config.txtcontains configuration region definition in proprietary text format.rusefi.inputcontains the UI - all the menus and dialogs. UI definition starts atmenuDialog = mainline - here you will see all top level menus defined with internal IDs and visible text labels.mapping.yamlis a minor detail related to how pins are named in drop downsprepend.txtis a minor detail which allows you to hide elements of the UI using@@if_XXXsyntax.
The combined file is generated by ConfigDefinition.jar tool.
On Windows this may be run with gen_config.bat.
Q: how do I offer my changes to TS project?
A: please PR only rusefi.input. Once merged, gen_config.bat would be executed automatically and results would be pushed by automation.