rusefi
/
rusefi_documentation
mirror of https://github.com/rusefi/rusefi_documentation.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #356 from mi-hol/master 

fix MD hierarchy
This commit is contained in:
mi-hol 2023-01-05 21:13:08 +01:00 committed by GitHub
parent 9f84235009 8476b13044
commit 35b4544933
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
3 changed files with 12 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
HOWTO-Start-An-Engine.md
View File

@ -20,7 +20,7 @@ Cranking - Step one.
## Verify your crank sensor reads the trigger wheel
This can be done before setting anything in the ECU and should be the first test done.
To do this go into tuner studio and disable the fuel injection and the ignition under each of the settings tabs.
To do this go into TunerStudio and disable the fuel injection and the ignition under each of the settings tabs.
- Insert picture of each of the settings tabs
Next go into the high speed logger and simply crank the engine. I recommend the rusEFI console for this job as it has a really good logger in the "engine sniffer" tab.

18
MAF.md
View File

@ -1,20 +1,20 @@
# MAF
# Current Status
## Current Status
The MAF based fueling of rusEFI is still undergoing development, the current status has the fueling functioning correctly but presents a few tuning challenges due to TunerStudio integration and the Spark Table still being reliant on the old engine load math.
This is an evolving situation at present and thus MAF fueling is still considered experimental.
**Please only use for development work at your own risk.**
# MAF fuel theory - The detail
## MAF fuel theory - The detail
The implementation of the MAF in rusEFI is intended to replicate the functionality of OEM systems and as such is more complex than some other systems.
The foundation of the MAF system is the Mass Air Flow sensor itself, this is a device using a hot wire, hot film or vane to directly measure the flow of air into the engine.
Obviously this sensor does not give out an airflow value, it gives us a voltage, current or PWM signal that represents the flow. rusEFI can interpret a voltage or current MAF at this time via a transfer function table.
[//]: # "Insert the MAF transfer function screen shot"
[//]: # "todo: Insert the MAF transfer function screen shot"
The Transfer function table is used to convert the raw MAF sensor reading into a Kg/h (Kilogram Per Hour) airflow.
@ -48,27 +48,27 @@ The required fuel is now simply corrected by adjusting the measured air by the v
Using this method rusEFI is able to directly measure the air flow into an engine and calculate the required fuel with minimal tuning.
# MAF fuel tuning - The quick version
## MAF fuel tuning - The quick version
To tune rusEFI using the MAF is probably the quickest and easiest method provided you have a working MAF sensor and the correct information to input in the Transfer Function Table.
The first thing to do is input the voltage (or current) to Kg/h information into the Transfer Function Table in tuner studio.
The first thing to do is input the voltage (or current) to Kg/h information into the Transfer Function Table in TunerStudio.
Secondly you will need to decide what Air/Fuel ratio you would like your engine to run at and input this into the AFR table in tuner studio.
Secondly you will need to decide what Air/Fuel ratio you would like your engine to run at and input this into the AFR table in TunerStudio.
For a first start a value of 14 is perfectly acceptable for gasoline.
This table is the primary source of the desired fuel mixture, it will be this table that is tuned to decide the engines target AFR.
A future update will make this fueling table dynamic so that an input % of ethanol in the main fueling dialog will change the fuel density and thus the required fuel mass injected. The result of this will be that users can leave this table tuned as though it were for pure gasoline (14.7:1 stoiciometric) and the % ethanol input will make sure the fuelling stays at the same Lambda value.
This has the advantage of working well with aftermarket wideband controllers that generally work in AFR using pure gasoline as the standard.
[//]: # "Add AFR table picture"
[//]: # "todo: Add AFR table picture"
Before starting the engine for the first time it is wise to ensure the Fuel Table is filled with values of "100", a value of 100 means that the fuel calculation uses 100% of its measured air mass to decide on the fuel injection pulse.
Tuning this table will adjust for dynamic airflow effects that happen in the inlet of an engine and will allow small (or large but hopefully not) corrections to the fuel injection which may be required to have the engine meet it's desired air/fuel target.
This table should only be tuned if the engine is not meeting the desired air/fuel target under relatively steady state conditions (i.e. without any acceleration enrichment or overrun fuel cut).
If a different air/fuel ratio is desired at a specific load or RPM then the AFR Table is the correct table to adjust instead.
[//]: # "Add VE table picture"
[//]: # "todo: Add VE table picture"
Some useful MAF sensor maths in [this link](https://www.efunda.com/designstandards/sensors/hot_wires/hot_wires_theory.cfm)
[//]: # "OrchardPerformance"
[//]: # "todo: OrchardPerformance"

4
Try-It.md
View File

@ -95,6 +95,6 @@ rusEFI has a virtual option. This runs same code with same RTOS in Windows, Linu
You can compile the firmware, making changes and submitting bug fixes. See [HOWTO Contribute to Firmware](HOWTO-contribute-to-firmware)
### Experiment with java based dev console, tuner studio, etc
### Experiment with java based dev console, TunerStudio, etc
You can develop the tunerstudio (TS) or dev console, and you can test these java programs against the virtual rusEFI.
You can develop the TunerStudio (TS) or dev console, and you can test these java programs against the virtual rusEFI.