Difference between revisions of "Manual:Current Status"

From rusEfi
Jump to navigation Jump to search
(Marked this version for translation)
(Total number of engines running rusEfi: 51)
 
(122 intermediate revisions by 4 users not shown)
Line 2: Line 2:
 
<translate>
 
<translate>
 
<!--T:8-->
 
<!--T:8-->
[[Category:admin]]
+
[[Category:IntroPages]]
  
 
<!--T:9-->
 
<!--T:9-->
Line 9: Line 9:
 
|}
 
|}
  
=== Last updated 02/28/2014 === <!--T:10-->
+
=== Last updated 04/27/2017 === <!--T:10-->
 
----
 
----
  
=== GENERAL STATUS === <!--T:11-->
+
=== GENERAL STATUS: v 1.0.3 as of 5/22/2017 === <!--T:11-->
Total number of engines running rusEfi: 4
+
We are aware of 45+ engines that have been started with rusEFI. So far every engine seems almost completely different from any other. It has varied from a high rev 2 stroke single cyl, to a 4 stroke V8 truck motor. They have pretty much all used a different crank wheel decoder. Wasted spark, distributor and sequential spark have been operational. As well as MAF (Alpha-N) and MAP (Speed Density) typologies have been operational. There have been a great variety of engine technologies implemented and there will be many more technologies developed in the future. Endurance racing proven!
# http://rusefi.com/forum/viewtopic.php?f=3&t=375
 
# http://rusefi.com/forum/viewtopic.php?f=3&t=360&start=150
 
# http://rusefi.com/forum/viewtopic.php?f=3&t=537
 
# http://rusefi.com/forum/viewtopic.php?f=3&t=467&start=33
 
  
 
<!--T:12-->
 
<!--T:12-->
Numbers of cylinders run in a single engine 4 (will eventually include 1,2,6,8,12 and perhaps others)
+
Numbers of cylinders run in a single engine: 1, 3, 4, 6 and 8 (The firmware also supports 2,5,7,9,10,12 and 13)
  
<!--T:13-->
+
=== Supported Features ===
Has controlled 4 fuel channels
+
Full standalone engine control unit - spart & fuel control for two stroke and four stroke gasoline engines.
  
<!--T:14-->
+
TunerStudio integration
Has controlled 2 Spark channel
 
  
<!--T:15-->
+
Variable Valve Timing valve control
Has controlled misc devices, fuel pump (will eventually include IAC steppers, H bridge, fan motor, NOX, and more)
 
  
<!--T:16-->
+
Closed-loop fuel control
Has controlled these engine configurations
+
 
* 4 channels of port injection with 1 channel disy ignition done in 0C cold temperatures while controlling the fuel pump.
+
Alternator field PID control
* 4 channels of port injection with 2 channel wasted spark ignition
+
 
 +
SD card logging
 +
 
 +
Flexible input-output control
 +
 
 +
racing proven!
 +
 
 +
hip9011 integration
 +
 
 +
Vehicle speed sensor
 +
 
 +
Stepper idle valve
 +
 
 +
Speed Density
 +
 
 +
CAN protocol support
 +
 
 +
Sequential injection
 +
 
 +
Spark advance table lookup
 +
 
 +
Fuel table lookup based on RPM & MAF with temperature correction
 +
 
 +
Wideband O2 input
 +
 
 +
Idle Valve Control
 +
 
 +
fuel pump control
 +
 
 +
electronic throttle body work in progress
 +
 
 +
 
 +
=== FAQ ===
 +
Q: Does rusEfi support my engine?
 +
 
 +
A: rusEfi support most engines from late 1980s to early 2000s.
 +
 
 +
Frankenso and Frankenstein boards require external coil igniters or logic-level coils (LS, Miata, some Nissan). rusEfi own igniter could be populated in prototyping area.
 +
 
 +
Frankenso and Frankenstein boards can control solenoid-type idle valves (Mazda, Neon), additional stepper control module in prototyping area would be needed for stepper idle valves (Subaru Jeep RAM)
 +
 
 +
Frankenso and Frankenstein boards do not support low impedance injectors (usually found in early 80s mono-injection systems)
 +
 
 +
rusEfi can work both with manual and automatic transmissions. While rusEfi has no means for transmission control at the moment, a few installations work fine with vehicle original TCUs.
 +
 
 +
 
 +
''Rotaty engines could work but no rotary was started on rusEfi so far.
 +
At the moment rusEfi does NOT support electronic throttle bodies (some 2000s and later enginees). rusEfi hardware does NOT support direct gasoline injection (some 2010s engines)''
 +
 
 +
== Total number of engines running rusEfi: 51 ==
 +
 
 +
See https://github.com/rusefi/rusefi_documentation/wiki/List_of_engines_running_rusEfi
  
 
=== STATUS NOTE === <!--T:17-->
 
=== STATUS NOTE === <!--T:17-->
It is important to mention that as of April 2014 rusEFI is still pretty immature. The hardware platform at this time is screwed to a board, with many wires under screw terminals. There are absolutely no warranties, and there are likely major bugs. This is currently a developers platform. However the goal is to make it much more user friendly given time to mature.
+
It is important to mention that as of July 2016 rusEFI is still in need of additional real world testing. At this point we are pretty happy with the current hardware platform, and the software is well-tested but mostly on a bench so far. Engine applications have been positive so far.
  
=== Features === <!--T:18-->
+
Pretty much any crank wheel decoder can be supported, we have a very flexible engine angle decoder, and about any new sensor setup can be supported. The above engines have all had different decoders, that have gone up to 60 tooth crank wheel.
* Fuel Injection: batch & sequential
+
 
* Ignition control
+
There are absolutely no warranties, and there are likely major bugs. This is currently a developers platform. However the goal is to make it much more user friendly given time to mature.
* Idle control
 
* Fuel pump control
 
* TunerStudio integration
 
* character LED support
 
* Basic CAN integration
 
* Basic GPS integration
 
* Basic CAN integration
 
  
 
=== #1 1996 Ford Aspire === <!--T:19-->
 
=== #1 1996 Ford Aspire === <!--T:19-->
Here is a video of engine 1. [http://rusefi.com/forum/viewtopic.php?t=375 1995 Ford Aspire 1.3]
+
[http://rusefi.com/forum/viewtopic.php?t=375 1995 Ford Aspire 1.3]
 
{| aligh="right"
 
{| aligh="right"
| http://rusefi.com/images/forum_posts/rusefi_hardware_v3.jpg
 
 
| {{#ev:youtube|M-qqHQ-quFg}}
 
| {{#ev:youtube|M-qqHQ-quFg}}
 
|}
 
|}
Line 63: Line 100:
 
{{#ev:youtube|neGVmxol0Gc}}
 
{{#ev:youtube|neGVmxol0Gc}}
  
=== #3 Mazda BP === <!--T:20-->
+
=== #3 Ford Festiva/Mazda Protege BP === <!--T:20-->
 
[http://rusefi.com/forum/viewtopic.php?t=537 1993 Ford Escort GT inside a Ford Festiva]
 
[http://rusefi.com/forum/viewtopic.php?t=537 1993 Ford Escort GT inside a Ford Festiva]
  
Line 69: Line 106:
 
{{#ev:youtube|t2y3h8rGKXQ}}
 
{{#ev:youtube|t2y3h8rGKXQ}}
  
=== Engine #4 === <!--T:24-->
+
=== #4 1999 Mazda Miata === <!--T:24-->
 +
 
 +
 
 
{{#ev:youtube|5wkH4HVtc50}}
 
{{#ev:youtube|5wkH4HVtc50}}
 +
 +
=== Engine #5 ===
 +
1995 Honda Accord - this one really needs a better fuel map :)
 +
 +
{{#ev:youtube|TWYU1SngT5w}}
 +
 +
=== #6 Mitsubishi ===
 +
 +
=== #7 Miata ===
 +
 +
=== #8 Citroen ===
 +
 +
=== #15 Dodge Ram 5.2 Magnum V8 ===
 +
 +
{{#ev:youtube|qghT6uhH6_I}}
 +
 +
=== #20 1991 Miata Hunchback ===
 +
 +
{{#ev:youtube|owg1SdErA7I}}
 +
 +
=== #27 2003 VVT Miata  ===
 +
 +
{{#ev:youtube|Vy2c9egWSto}}
  
 
=== Next Engine should be yours ===  <!--T:25-->
 
=== Next Engine should be yours ===  <!--T:25-->
Line 76: Line 138:
  
 
<!--T:26-->
 
<!--T:26-->
At this point some soldering would be required: you would need to solder either your connector or your harness to the board.
+
<strike>At this point some soldering would be required: you would need to solder either your connector or your harness to the board.</strike> Some plug & play boards are [http://rusefi.com/wiki/index.php?title=Hardware:For_Sale already available]
  
 
<!--T:27-->
 
<!--T:27-->
No, you would not need to be a coder: you would not need to read or write the code. If any code is missing it would be our job to add it, what you would need to provide would be the tune and specs on all the sensors. Your would be configuring rusEfi using either TunerStudio or our own console application.
+
You do not need to be a coder: you do not need to read or write the code. If any code is missing it would be our job to add it, what you would need to provide would be the tune and specs on all the sensors. Your would be configuring rusEfi using either TunerStudio or our own console application.
 +
 
 +
== Logos ==
  
 +
Artwork / logo / style files available at
  
 +
http://rusefi.com/style/ (created with https://gimp.org/)
  
  
 
</translate>
 
</translate>

Latest revision as of 20:55, 10 June 2019

Other languages:
English • ‎русский

Last updated 04/27/2017


GENERAL STATUS: v 1.0.3 as of 5/22/2017

We are aware of 45+ engines that have been started with rusEFI. So far every engine seems almost completely different from any other. It has varied from a high rev 2 stroke single cyl, to a 4 stroke V8 truck motor. They have pretty much all used a different crank wheel decoder. Wasted spark, distributor and sequential spark have been operational. As well as MAF (Alpha-N) and MAP (Speed Density) typologies have been operational. There have been a great variety of engine technologies implemented and there will be many more technologies developed in the future. Endurance racing proven!

Numbers of cylinders run in a single engine: 1, 3, 4, 6 and 8 (The firmware also supports 2,5,7,9,10,12 and 13)

Supported Features

Full standalone engine control unit - spart & fuel control for two stroke and four stroke gasoline engines.

TunerStudio integration

Variable Valve Timing valve control

Closed-loop fuel control

Alternator field PID control

SD card logging

Flexible input-output control

racing proven!

hip9011 integration

Vehicle speed sensor

Stepper idle valve

Speed Density

CAN protocol support

Sequential injection

Spark advance table lookup

Fuel table lookup based on RPM & MAF with temperature correction

Wideband O2 input

Idle Valve Control

fuel pump control

electronic throttle body work in progress


FAQ

Q: Does rusEfi support my engine?

A: rusEfi support most engines from late 1980s to early 2000s.

Frankenso and Frankenstein boards require external coil igniters or logic-level coils (LS, Miata, some Nissan). rusEfi own igniter could be populated in prototyping area.

Frankenso and Frankenstein boards can control solenoid-type idle valves (Mazda, Neon), additional stepper control module in prototyping area would be needed for stepper idle valves (Subaru Jeep RAM)

Frankenso and Frankenstein boards do not support low impedance injectors (usually found in early 80s mono-injection systems)

rusEfi can work both with manual and automatic transmissions. While rusEfi has no means for transmission control at the moment, a few installations work fine with vehicle original TCUs.


Rotaty engines could work but no rotary was started on rusEfi so far. At the moment rusEfi does NOT support electronic throttle bodies (some 2000s and later enginees). rusEfi hardware does NOT support direct gasoline injection (some 2010s engines)

Total number of engines running rusEfi: 51

See https://github.com/rusefi/rusefi_documentation/wiki/List_of_engines_running_rusEfi

STATUS NOTE

It is important to mention that as of July 2016 rusEFI is still in need of additional real world testing. At this point we are pretty happy with the current hardware platform, and the software is well-tested but mostly on a bench so far. Engine applications have been positive so far.

Pretty much any crank wheel decoder can be supported, we have a very flexible engine angle decoder, and about any new sensor setup can be supported. The above engines have all had different decoders, that have gone up to 60 tooth crank wheel.

There are absolutely no warranties, and there are likely major bugs. This is currently a developers platform. However the goal is to make it much more user friendly given time to mature.

#1 1996 Ford Aspire

1995 Ford Aspire 1.3

#2 Dodge Neon 2.0

1995 Dodge Neon 2.0

#3 Ford Festiva/Mazda Protege BP

1993 Ford Escort GT inside a Ford Festiva

#4 1999 Mazda Miata

Engine #5

1995 Honda Accord - this one really needs a better fuel map :)

#6 Mitsubishi

#7 Miata

#8 Citroen

#15 Dodge Ram 5.2 Magnum V8

#20 1991 Miata Hunchback

#27 2003 VVT Miata

Next Engine should be yours

Get an engine running, then insert your name here! After all, this is all pretty simple :)

At this point some soldering would be required: you would need to solder either your connector or your harness to the board. Some plug & play boards are already available

You do not need to be a coder: you do not need to read or write the code. If any code is missing it would be our job to add it, what you would need to provide would be the tune and specs on all the sensors. Your would be configuring rusEfi using either TunerStudio or our own console application.

Logos

Artwork / logo / style files available at

http://rusefi.com/style/ (created with https://gimp.org/)