rusEFI consists of a wide group of people working on a common interest in electronic engine control. In the rusEFI community, you will find a wide range of talents and interests. Some people are looking to get better performance at the track on race day, others are trying to make small engine(s) like go-carts, snow blowers, generators and other applications better, while others are trying crack pot science experiments.
The community includes people from several languages and people from all around the world with a wide variety of talents and interests. This community includes a forum where people can post about technical details and specific installations. Generally the goal is to keep the forum with a high level of content oriented discussion. After a thread has gotten to a particular maturity, we hope to boil the threads content down into wiki pages, like this. There are members who will help others with any technical questions, and others that are developers who would prefer that a user figure it out themselves. Feel free to join the forums, introduce yourself and ask questions. The group there is generally friendly and helpful.
Here is a brief explanation of where rusEFI originated from. The founding member couldn't help but feel that the existing aftermarket engine control units were lacking and he felt the time has come for a simple, clean and usable EFI project. He saw that the world has embedded processing boards that can be purchased for under $20 running at speeds above 100MHz, we also have some great real-time operation systems that can make a very simple and usable Electronic Fuel Injection (EFI) system possible.
This project's goals are to create control options for experimental engines, like those used at a race track or closed stage, small engines like lawn mowers, go carts, and snow blowers as well as crack pot science experiments. We aim to offer a variety of hardware and software building blocks that can be used to control what ever engine you are trying to control. We are focusing our aiming at some of the most popular setups, as it allows this project to reach the masses quickest. If there are other configurations or older engines that are being modified for electronic control, we are interested, so feel free to chat it up on the forums. This project is not intended for pollution or safety controlled systems like street bound automobiles.
BRIEF DESCRIPTION OF HARDWARE
At the time of writing this, rusEfi is currently a standalone ECU including both hardware and software that can control a wide array of potential motor configurations. The code controls fuel injectors, ignition, fuel pump and idle air valve solenoid. Input signals include CRANK and CAM for engine rotational position, MAF signal, fuel and timing are adjust-able via Tuner Studio which allows you to program the look up tables. The main goal of this project is to have perfect code - no hacks, just a straightforward understandable implementation. This combined with open hardware design should really make the next generation of aftermarket engine control units!
- 12 injector drivers, 8 Ignition drivers, all the common analog and digital IO.
- TunerStudio integration - online tuning!
- 16x16 fuel, VE, timing tables
- Cold start correction
- Spark control: distributor, wasted & sequential options.
- Fuel Injection: batch & sequential options.
- Idle control - solenoid or stepper
- Character LCD support
- Basic CAN integration
- Basic GPS integration
Devices not yet supported: electronic throttle body
BRIEF TECHNICAL OVERVIEW
Here's a basic technical overview:
- stm32f407 32-bit ARM Cortex-M4F core, 168MHz, 1 MB Flash, 192 KB RAM processor with floating-point unit. No more horrors of fixed point math.
- ChibiOS/RTreal-time operating system is used. Don't let the devils of peripheral programming hurt you.
- Both GCC/Eclipse and IAR toolchains are supported.
- KiCad EDA is used to design the circuit boards.
Here's video that shows rusEFI running a test engine.
rusEfi has chosen to be an open source hardware and software project and currently has over a dozen of contributors already! The official licences(s) are of course in the source files. However see copy of license here
If you are still interested and we hope you are, please feel free to use the navigation page to the left and find more about the content you are interested in.