merge rusEFI wiki
This commit is contained in:
commit
4262b739bb
|
@ -5,7 +5,7 @@ The best way to configure rusEFI according to your engine setup is via Tuner Stu
|
||||||
But rusEFI is still in the phase of active development: some parts of the code are still far from final, and new configuration parameters are being added every month. Because of that, the TunerStudio project definition is still pretty volatile. Volatile TunerStudio project definition means your settings could be lost next time you upgrade the firmware, because of that we need a way to keep default configurations for each setup in a more persistent way. This is the reason why we have...
|
But rusEFI is still in the phase of active development: some parts of the code are still far from final, and new configuration parameters are being added every month. Because of that, the TunerStudio project definition is still pretty volatile. Volatile TunerStudio project definition means your settings could be lost next time you upgrade the firmware, because of that we need a way to keep default configurations for each setup in a more persistent way. This is the reason why we have...
|
||||||
|
|
||||||
|
|
||||||
Engine Type concept: we have an array of default configurations for different engines defined [right in the source code](https://github.com/rusefi/rusefi/tree/master/firmware/config/engines). Which of the configurations is used is controlled by 'engine type' field which is persisted in the internal chip flash memory along with the rest of the configuration. So, in order to get your trigger decoding parameters and your fuel & injection control strategies activated, you need to invoke the 'set engine_type X' command as described [http://rusefi.com/forum/viewtopic.php?f=5&t=210#p4038 here].
|
Engine Type concept: we have an array of default configurations for different engines defined [right in the source code](https://github.com/rusefi/rusefi/tree/master/firmware/config/engines). Which of the configurations is used is controlled by 'engine type' field which is persisted in the internal chip flash memory along with the rest of the configuration. So, in order to get your trigger decoding parameters and your fuel & injection control strategies activated, you need to invoke the 'set engine_type X' command as described [here](http://rusefi.com/forum/viewtopic.php?f=5&t=210#p4038).
|
||||||
|
|
||||||
Ford Aspire Frankenstein default configuration: `set engine_type 3`
|
Ford Aspire Frankenstein default configuration: `set engine_type 3`
|
||||||
|
|
||||||
|
|
|
@ -210,6 +210,8 @@ terminal 173681
|
||||||
![Grey connectors](Hardware/connectors/64_pin_connectors_grey.png)
|
![Grey connectors](Hardware/connectors/64_pin_connectors_grey.png)
|
||||||
![Green connectors](Hardware/connectors/64_pin_connectors_green.png)
|
![Green connectors](Hardware/connectors/64_pin_connectors_green.png)
|
||||||
|
|
||||||
|
mitsubishi colt/mirage 1991-1995 year for 1.3, 1.6 and 1.8 engine
|
||||||
|
|
||||||
See also [the 48 pin](OEM-connectors#48-pin).
|
See also [the 48 pin](OEM-connectors#48-pin).
|
||||||
|
|
||||||
For sale @ http://www.ebay.com/usr/rusefi
|
For sale @ http://www.ebay.com/usr/rusefi
|
||||||
|
|
Loading…
Reference in New Issue