rusefi
/
rusefi-1
mirror of https://github.com/rusefi/rusefi-1.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
rusefi-1/firmware/tunerstudio
History
Matthew Kennedy e227018c85
Ts cleanup 2 (#1226) 
* remove biquad config

* fuel pump clarity

* hide stuff

* hide more stuff correctly

* more hides

* hide comparator except for kinetis

* didn't mean to change all those

* fix kinetis
 		2020-03-26 11:41:58 -04:00
..
docs docs 2018-06-04 19:49:40 -04:00
translations docs 2019-05-27 16:13:19 -04:00
.gitignore board-specific usability #808 2019-05-30 20:41:54 -04:00
readme.md skeleton & docs (#995) 2019-11-03 08:41:14 -05:00
rusefi.ini Dear Fahrenheit, it was fun! Hope to see you back one day. 2020-03-25 19:06:35 -04:00
rusefi.input Ts cleanup 2 (#1226) 2020-03-26 11:41:58 -04:00
rusefi_frankenso.ini Dear Fahrenheit, it was fun! Hope to see you back one day. 2020-03-25 19:06:35 -04:00
rusefi_kinetis.ini startStopDialog 2020-03-25 00:58:59 -04:00
rusefi_microrusefi.ini Dear Fahrenheit, it was fun! Hope to see you back one day. 2020-03-25 19:06:35 -04:00
rusefi_prometheus.ini Dear Fahrenheit, it was fun! Hope to see you back one day. 2020-03-25 19:06:35 -04:00
rusefi_proteus.ini Dear Fahrenheit, it was fun! Hope to see you back one day. 2020-03-25 19:06:35 -04:00

readme.md

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:

  1. rusefi_config.txt contains configuration region definition in proprietary text format.
  2. rusefi.input contains the UI - all the menus and dialogs. UI definition starts at menuDialog = main line - here you will see all top level menus defined with internal IDs and visible text labels.
  3. mapping.yaml is a minor detail related to how pins are named in drop downs
  4. prepend.txt is a minor detail which allows you to hide elements of the UI using @@if_XXX syntax.

The combined file is generated by ConfigDefinition.jar tool. On Windows this may be run with gen_config.bat.