rusefi-1/firmware/tunerstudio
rusefi 54d1dd359a preparing for #979 2019-10-15 15:03:19 -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 docs 2019-06-09 20:36:29 -04:00
rusefi.ini preparing for #979 2019-10-15 15:03:19 -04:00
rusefi.input preparing for #979 2019-10-15 15:03:19 -04:00
rusefi_frankenso.ini preparing for #979 2019-10-15 15:03:19 -04:00
rusefi_kinetis.ini Kinetis files (pre-alpha) (#890) 2019-07-27 09:52:01 -04:00
rusefi_microrusefi.ini preparing for #979 2019-10-15 15:03:19 -04:00
rusefi_prometheus.ini preparing for #979 2019-10-15 15:03:19 -04:00

readme.md

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.

rusefi.ini file is generated by ConfigDefinition.jar tool. On Windows you simply invoke gen_config.bat