rusefi-1/firmware/tunerstudio
Matthew Kennedy 701f7fd7aa
Accelerator pedal with new sensors (#1208)
* add pedal sensor

* update status loop

* add bit to ts

* fix math

* divide at config time

* this used a little bit of ram
2020-03-22 17:09:46 -04:00
..
docs
translations
.gitignore
readme.md skeleton & docs (#995) 2019-11-03 08:41:14 -05:00
rusefi.ini start/stop 2020-03-20 20:45:35 -04:00
rusefi.input Accelerator pedal with new sensors (#1208) 2020-03-22 17:09:46 -04:00
rusefi_frankenso.ini start/stop 2020-03-20 20:45:35 -04:00
rusefi_kinetis.ini start/stop 2020-03-20 20:45:35 -04:00
rusefi_microrusefi.ini start/stop 2020-03-20 20:45:35 -04:00
rusefi_prometheus.ini start/stop 2020-03-20 20:45:35 -04:00
rusefi_proteus.ini start/stop 2020-03-20 20:45: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.