General updates and Fuel index, also killed the old X-tau page as we have a new one (#52)
* Fix for Home page and future features page added * Update Acceleration_Compensation.md * Update Fuel_Overview.md * More fuel info * More X-tau * Ongoing Tasks list Free for all list for people to update as they change track * Update Ongoing_Tasks * Hidden names on pages and multi-spark page * Update X-tau_Wall_Wetting.md * Update * Update AlphaN.md * Update Speed_Density.md * Fuel control overview improvement, added wide band page * Update Wide_Band_Sensors.md * Update Fuel_Overview.md * Update MAF.md * Update MAF.md * Update rusEFI_console_directory.png * pin #1 * project -> other * docs * Created HOWTO set rusEfi Online authentication token (markdown) * docs * Created Mazda PRC Valve (markdown) * Small format edit * Stronger wording on the Trabant clause and readability improvement. * Updated HOWTO_join_slack_channel (markdown) * Updated Fuel_Overview (markdown) * Delete rusEFI_console_directory.png * Delete wall_wetting.md * Fuel Index + Formats Also old wall wetting page kill * Update Pages_Fuel.md * Update Pages_Fuel.md Co-authored-by: rusefi <rusefillc@gmail.com> Co-authored-by: rusefi <rusefi@users.noreply.github.com>
This commit is contained in:
OrchardPerformance
GitHub
parent
d623fa2aa7
commit
9bb6769210
Binary file not shown.
|
After Width: | Height: | Size: 26 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 1.4 KiB |
|
|
@ -1,8 +1,9 @@
|
|||
# Fuel control overview
|
||||
|
||||
The Air Fuel Ratio (AFR) is controlled by how much fuel is delivered to the cylinder for combustion. There are many factors and many sensors that come into play when trying to determine how much O2 is in the cylinder. RusEFI collects this information and makes a guess about how much O2 is in the cyl, then rusEFI has to determine how much fuel is needed to get the expected AFR and deliver that fuel charge. Below is a graphic that shows some common differences in AFR for a particular Toyota engine. Other engines are similar to this, but may have a different peak power area, or peak efficiency area, etc. To know this information for your particular setup you would need to run it on a Dyno, and determine the exact AFR's.
|
||||
The Air Fuel Ratio (AFR) is controlled by how much fuel is delivered to the cylinder for combustion. There are many factors and many sensors that come into play when trying to determine how much O2 is in the cylinder. rusEFI collects this information and makes a guess about how much O2 is in the cyl, then rusEFI has to determine how much fuel is needed to get the expected AFR and deliver that fuel charge. Below is a graphic that shows some common differences in AFR for a particular Toyota engine. Other engines are similar to this, but may have a different peak power area, or peak efficiency area, etc. To know this information for your particular setup you would need to run it on a Dyno, and determine the exact AFR's.
|
||||
|
||||
Airfuel.jpg
|
||||
|
||||
[//]: # "Add picture"
|
||||
|
||||
Original graphic found here [1]
|
||||
|
|
@ -10,7 +11,7 @@ Original graphic found here [1]
|
|||
Most people who are installing tune-able ECU's like rusEFI are looking for more power at the track. However your fuel weight advantage is also commonly important. So it is common that an engine will be tuned for peak power when over a certain load, and peak economy when at a cruise load. OEM's are often concerned with minimal environmental impact, so they may tune to a different AFR. Once you have decided on what your AFR strategy is going to be, you'll have to tune rusEFI to deliver that strategy. As well you will probably use an wide band oxygen sensor to measure your AFR and ensure that your are meeting your desired AFT plan.
|
||||
|
||||
# Supported fuel control algorithms
|
||||
RusEfi supports mono, individual/sequential and batched fuel injection using one of the following fuel control algorithms:
|
||||
rusEFI supports mono, individual/sequential and batched fuel injection using one of the following fuel control algorithms:
|
||||
|
||||
1) MAF-based or MAP-based table fuel lookup with interpolation - these algorithms are pretty rough since they do not account for ambient air temperature but not many sensor are required to run.
|
||||
|
||||
|
|
@ -22,15 +23,17 @@ Wideband Oxygen Sensor is pretty much a requirement for both manual and auto-tun
|
|||
|
||||
|
||||
T4dv3ed.png
|
||||
|
||||
[//]: # "Add picture"
|
||||
|
||||
Within each fuel calculation mode there is coolant temperature correction ("warm-up mode"), battery voltage correction and injector open time ("injector lag") correction.
|
||||
|
||||
|
||||
rusEfi could be used with MAF sensors sending out voltage (like Mazda Miata) or current (like Ford Aspire).
|
||||
rusEFI could be used with MAF sensors sending out voltage (like Mazda Miata) or current (like Ford Aspire).
|
||||
|
||||
|
||||
NXe9uWH.png
|
||||
NXe9uWH.png
|
||||
|
||||
[//]: # "Add picture"
|
||||
|
||||
(also some content at http://rusefi.com/forum/viewtopic.php?f=2&t=1124)
|
||||
|
|
|
|||
|
|
@ -25,12 +25,12 @@ This Kg/h value is then processed into a required fuel quantity by the following
|
|||
cylinder Airmass = airPerRevolution / half Cylinder number
|
||||
|
||||
In rusEFI we use a correction factor table to modify this measured air mass to allow correction of any errors in the measurement due to dynamic air flow effects.
|
||||
To do this we to have a "load" value that allows us to have a Load Vs Speed fuel table.
|
||||
To do this we need to have a "load" value that allows us to have a Load Vs Speed fuel table.
|
||||
|
||||
StandardAirCharge = engine displacement / number of cylinders * 1.2929
|
||||
|
||||
This produces the air mass for cylinder filling at 100% VE under standard SAE conditions.
|
||||
Using this we can relate our cylinder air mass back to a standardised 100% cylinder filling and this we have a "load" value to use when tuning.
|
||||
Using this we can relate our cylinder air mass back to a standardised 100% cylinder filling and thus we have a "load" value to use when tuning.
|
||||
|
||||
airChargeLoad = 100 * cylinder Airmass / Standard AirCharge
|
||||
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
# Speed Density
|
||||
Speed density is the most popular fuel control system employed by rusEFI users at present. This is due to its simplicity of tuning and its suitability for turbocharged cars.
|
||||
Speed density is the most popular fuel control system employed but rusEFI users are present. This is due to its simplicity of tuning and it's suitability for turbocharged cars.
|
||||
It is due to this widespread use that it is the most well developed fuel control method and is the primary recommendation for fuel control at present (27/4/2020).
|
||||
|
||||
# The detail
|
||||
|
|
|
|||
|
|
@ -0,0 +1,3 @@
|
|||
In order for your rusEFI console to upload your tune to rusEFI online you will need to configure rusEFI console authentication token.
|
||||
|
||||
Please open your rusEFI Forum profile, "Your Vehicles" tab - and you will fix the auth token value there. Copy it from the forum profile into rusEFI console settings - and now your local console can upload to the website!
|
||||
|
|
@ -4,6 +4,11 @@ Tunerstudio is a tuning application that might be needed while working with rusE
|
|||
|
||||
|
||||
|
||||
|
||||
In order to create a rusEFI project you need a rusefiSOMETHING.ini file from you [rusEFI bundle](https://github.com/rusefi/rusefi/wiki/Download).
|
||||
|
||||
|
||||
|
||||
After clicking on the link you'll see this:
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -1,8 +1,8 @@
|
|||
# Joining the rusEFI slack channel
|
||||
|
||||
#### What is slack and whi should I be there?
|
||||
#### What is slack and why should I be there?
|
||||
|
||||
Slack in a business messenger that can be accessed through your browser or as an application on your PC.
|
||||
Slack in a group messenger that can be accessed through your browser or as an application on your PC.
|
||||
|
||||
#### Joining the channel
|
||||
|
||||
|
|
|
|||
|
|
@ -15,30 +15,33 @@ As of March 2020 Frankenso board is sold as mostly as a DIY kit.
|
|||
| [Proteus](Proteus) | rusEfi if you have lots of hardware or cylinders | 2020 | 12 cylinder, dual electronic throttles |
|
||||
|
||||
|
||||
Q: How to select a board?
|
||||
### Q: How to select a board?
|
||||
|
||||
A: History shows that fully assembled boards are the safest way to start. History shows
|
||||
that 80% of the kits are never assembled. As of March 2020 we have many microRusEfi [in stock](https://rusefi.com/shop/) and
|
||||
very remaining [old stock assembled Frankenso](https://www.tindie.com/stores/russian/). New fabrication of the assembled Frankenso board is
|
||||
currently not planned.
|
||||
|
||||
Q: What else matters?
|
||||
### Q: What else matters?
|
||||
|
||||
A: Types and total count of crank and camshaft positions sensors is the next
|
||||
important question. microRusEfi unfortunately only supports one VR shaft input maximum with two inputs total.
|
||||
|
||||
Frankenso supports up to 2 VR or 2 Hall shaft position sensors. Prometheus supports TBD. Proteus supports TBD.
|
||||
|
||||
Q: why stm32?
|
||||
### Q: why stm32?
|
||||
|
||||
A: [selecting_open_source_ecu_microcontroller](selecting_open_source_ecu_microcontroller)
|
||||
|
||||
|
||||
Q: This is all very cool but you guys do not have a Plug&Play for my Trabant. I think I will go and make a new rusEFI board just for Trabant!
|
||||
### Q: This is all very cool but you guys do not have a Plug&Play for my Trabant. I think I will go and make a new rusEFI board just for my Trabant!
|
||||
|
||||
A: Building a full, brand new rusEFI board from scratch is probably an exercise in insanity. We already have too many different hardware configurations, and are running a bit thin to support it all. Please consider basing your P&P design on Hellen, Proteus, or microRusEfi - either as an adapter board, or at least as a custom PCB with shared schematics.
|
||||
A: At rusEFI we love cool new projects, but we are a really small team and only have so much time to work on rusEFI.
|
||||
We already have lots of different hardware configurations and we would suggest using one of the existing wire in versions.
|
||||
Nobody is stopping you from making your own board, but we cannot guarantee any support for that board or assistance with building it.
|
||||
If you proceed then please consider making a P&P adapter board design based on Hellen, Proteus, or microRusEFI.
|
||||
|
||||
Q: What EDA are you guys using for your open source hardware?
|
||||
### Q: What EDA are you guys using for your open source hardware?
|
||||
|
||||
A: rusEFI preference at the moment is KiCad 5. A few legacy pieces are still using KiCad 4. While many EDAs have many cool features KiCad gives rusEFI uniformity and consistency.
|
||||
|
||||
|
|
@ -46,11 +49,11 @@ See also https://rusefi.com/wiki/index.php?title=Hardware:Boards_Comparison
|
|||
|
||||
See also https://github.com/rusefi/rusefi/tree/master/hardware
|
||||
|
||||
Q: What pin do I use for tachometer output?
|
||||
### Q: What pin do I use for tachometer output?
|
||||
|
||||
A: There is no single right answer. It really depends on what kind of electrical signal is your tachometer expecting. Is it low-side driven? +5v logic signal driven? +12v logic signal driven?
|
||||
|
||||
Q: What are these four status LEDs close to main processor?
|
||||
### Q: What are these four status LEDs close to main processor?
|
||||
|
||||
A: Many rusEFI boards have four status LEDs. All four LEDs blink on start-up just to confirm life.
|
||||
|
||||
|
|
@ -61,7 +64,7 @@ Red CRITICAL (previously known as FATAL) error means you have a CRITICAL error,
|
|||
|
||||
Green LED on many rusEFI boards is RUNNING. Off if engine is stopped, blinks if engine is cranking, solid if engine is running.
|
||||
|
||||
Q: what about many other LEDs which seem to be blinking in sync with injectors or coils?
|
||||
### Q: what about many other LEDs which seem to be blinking in sync with injectors or coils?
|
||||
|
||||
A: Following Frankenso tradition, Injector LEDs are RED. Ignition LED are blue, power LED are green.
|
||||
|
||||
|
|
|
|||
|
|
@ -65,6 +65,8 @@ Each pin has a *Type ID*, which can be used to look up in the following tables w
|
|||
|
||||
In some cases without "main relay output +12v" both pins #1 and #5 should be connected to the single source of +12v.
|
||||
|
||||
Pin #1 feeds ETB H-bridge, battery voltage sense, gp5 & gp6 high-side +12v, TLE8888 H-bridges.
|
||||
|
||||
# Pin Types
|
||||
|
||||
These tables provide technical information about the different types of pin found on microrusEfi.
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
Q: I have an amazing ideas, let's do X! I bet it's possible with existing rusEFI software and hardware! Why not start right now:
|
||||
### Q: I have an amazing ideas, let's do X! I bet it's possible with existing rusEFI software and hardware! Why not start right now:
|
||||
|
||||
A: Let me answer this universal question with a universal answer, in two parts:
|
||||
|
||||
|
|
|
|||
|
|
@ -119,4 +119,5 @@ https://youtu.be/6IZcHCQl8yo
|
|||
Case compatibility:
|
||||
|
||||
Toyota Camry 89661-3T270
|
||||
89661-06691
|
||||
|
||||
Toyota Camry 89661-06691
|
||||
|
|
|
|||
|
|
@ -0,0 +1,7 @@
|
|||
Some Mazda engines have a solenoid valve on the vacuum line that goes to the fuel rail.
|
||||
This is used to raise the fuel pressure on a hot restart and avoid fuel vapor in the fuel rail.
|
||||
|
||||
This valve is not really needed with rusEFI and can be removed, in it's place a longer than normal "prime duration" should be set in the "fuel pump" dialogue. (suggest 4-6 seconds).
|
||||
|
||||
Engines known to have this valve:
|
||||
- MX5, 323 and protege B series
|
||||
|
|
@ -2,13 +2,11 @@ This is a quick list of what people are trying to tackle at the moment and the i
|
|||
Feel free to update or modify this list as needed, it is only intended as an aid to organization.
|
||||
|
||||
- Matt -> Current priority MRE bugs that are causing users problems.
|
||||
Has just ordered some Proteus assemblies from JLC which are being distributed among the group
|
||||
|
||||
- Jimmy -> Working on a page list for the Wiki and a guide to what pages we need to update first
|
||||
Testing multi spark
|
||||
- Jimmy ->
|
||||
|
||||
- Simon -> Currently writing content for the wiki, focus on fuel side of things at the moment.
|
||||
- Simon -> Currently writing content for the wiki, focus on fuel and vvt at the moment.
|
||||
|
||||
- Andrey -> has been working on NB miata trigger issues and will be testing the current MAF code shortly
|
||||
- Andrey ->
|
||||
|
||||
- Shaun -> Writing some info on multi spark for the wiki
|
||||
- Shaun ->
|
||||
|
|
@ -9,4 +9,6 @@
|
|||
|
||||
See [HOWTO upload tune](HOWTO_upload_tune)
|
||||
|
||||
See [HOWTO set rusEfi Online authentication token](HOWTO-set-rusEfi-Online-authentication-token)
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -0,0 +1,43 @@
|
|||
## Master list of fuel pages
|
||||
|
||||
<details><summary><u>rusEFI Project</u></summary>
|
||||
|
||||
* [rusEFI Project Fuel](rusEFI-project-Fuel)
|
||||
|
||||
</details>
|
||||
|
||||
<details><summary><u>Fuel Algorithms</u></summary>
|
||||
|
||||
* [Fuel Overview](Fuel/Fuel_Control/Fuel_Overview)
|
||||
* [AlphaN](Fuel/Fuel_Control/AlphaN)
|
||||
* [Speed Density](Fuel/Fuel_Control/Speed_Density)
|
||||
* [Mass Air Flow](Fuel/Fuel_Control/MAF)
|
||||
|
||||
</details>
|
||||
|
||||
<details><summary><u>Acceleration</u></summary>
|
||||
|
||||
* [Overview](Fuel/Fuel_Control/Acceleration/Acceleration_Compensation)
|
||||
* [X-Tau Wall Wetting](Fuel/Fuel_Control/Acceleration/X-tau_Wall_Wetting)
|
||||
* TPS. - Coming Soon
|
||||
|
||||
</details>
|
||||
|
||||
<details><summary><u>AFR measurement</u></summary>
|
||||
|
||||
* [Wide Band Sensors](Fuel/Wide_Band_Sensors)
|
||||
* [Do I need a wideband](FAQ/do_i_need_wideband_oxygen_sensor)
|
||||
* [Old WBO2 page](WBO)
|
||||
|
||||
</details>
|
||||
|
||||
<details><summary><u>Fuel Hardware</u></summary>
|
||||
|
||||
* [Converting from Carb](FAQ/how_to_convert_from_carburetor_to_EFI)
|
||||
* [GDI Status](FAQ/GDI_Status)
|
||||
|
||||
* Fuel injectors - Coming Soon
|
||||
|
||||
</details>
|
||||
|
||||
|
||||
|
|
@ -1,6 +1,6 @@
|
|||
rusEfi is a community-driven free open source project. It comes with zero warranty and zero promises.
|
||||
rusEFI is a community-driven free open source project. It comes with zero warranty and zero promises.
|
||||
|
||||
rusEfi has zero stuff and most of rusEfi contributors all over the globe have day jobs and other obligations.
|
||||
rusEFI has zero stuff and most of rusEFI contributors all over the globe have day jobs and other obligations.
|
||||
|
||||
https://rusefi.com/forum/ is the primary free support channel.
|
||||
|
||||
|
|
@ -8,8 +8,7 @@ https://rusefi.com/forum/ is the primary free support channel.
|
|||
Q: Matt and Andrey are on Facebook, shall I message Matt or Andrey directly?
|
||||
|
||||
A: Unfortunately we do not have resources for technical support via Facebook direct messages.
|
||||
Same about forum private messages. Please use public channels to have a higher chance of a response from the community. The more effort you make to ask a good question,
|
||||
the better response you would get. See also [HOWTO_ask_questions](HOWTO_ask_questions)
|
||||
Same about forum private messages. Please use public channels to have a higher chance of a response from the community. The more effort you make to ask a good question, the better response you would get. See also [HOWTO_ask_questions](HOWTO_ask_questions)
|
||||
|
||||
Q: how do I attach logs to my forum post? Looks like forum does not allow .msl files?
|
||||
|
||||
|
|
|
|||
|
|
@ -1,16 +0,0 @@
|
|||
|
||||
todo: more explanation of what this is all about
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
This is about 1 second worth of log, during a 2-3-4 shift at low-ish RPM, but near wide open throttle. Worst case scenario for AE!
|
||||
|
||||
The yellow trace on the top graph, AfrRatio, is a ratio of target vs. actual. If the engine is lean, it goes below 1, and rich above 1. Graph is scaled to +-20%. I'm using this because my actual AFR target varies from 14.7 all the way down to around 11.5. This swing causes the AFR signal to look like the ECU is doing a poor job, when in fact the setpoint is moving by nearly 30%.
|
||||
|
||||
There's a bit of a spike rich-then-lean during the shifts, but it's not bad (results in a nice burble out of the exhaust :lol:), and resolves once back on the throttle. Some of this is caused by the phase shift between the AFR target and measured AFR, but some of it is real.
|
||||
|
||||
[Sample log](2019-01-01_19_modified.msl)
|
||||
|
||||
Based on [https://rusefi.com/forum/viewtopic.php?f=5&t=1481](https://rusefi.com/forum/viewtopic.php?f=5&t=1481)
|
||||
Loading…
Reference in New Issue