Merge remote-tracking branch 'technical-git/master' into best-wiki-git-local

This commit is contained in:
rusefi 2020-06-25 10:52:49 -04:00
commit 12d9c00a14
5 changed files with 50 additions and 2 deletions

View File

@ -17,8 +17,7 @@ We probably would not articulate the guiding principles better than https://gith
#### Last but not least
Since 2012 until today, this is just a hobby project with zero paid employees. Test PCBs, forum hosting,
damaged hardware and etc. costs money
Since 2012 until today, this is just a hobby project with zero paid employees. Test PCBs, forum hosting, damaged hardware and etc. costs money
There are two ways to help financially:

BIN
Images/SkyactiveCoils.PNG Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 91 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 64 KiB

3
ProteusAdapter72.md Normal file
View File

@ -0,0 +1,3 @@
# This is a version of the 72 pin adaptor board for the Proteus
# It shares 90% of its features with the MRE version so the information [here](MREAdapter72.md) is still valid with a few additional notes as shown below

46
START_HERE.md Normal file
View File

@ -0,0 +1,46 @@
# This page is intended to help ease a new user into the world of rusEFI
## First things first
It is important for a new user to understand some things about rusEFI before jumping into the hardware or software.
RusEFI is a community project, everyone here is giving there time for free and have normal day jobs, this limits the amount of direct support we can give.
This means that the wiki and forum should be the first port of call for any questions. Most things are covered within these two resources.
With this in mind it is important that new users take a quick look at the [D is for distration](D_is_for_DISTRACTION.md) page and the [What rusEFI cannot do](What_rusEFI_Cannot_Do.md)
RusEFI is an advance system, many of the features of rusEFI are things you will only find on high end or OEM ECUs. This means that users will need to take time to understand the systems they are working on and the principals behind them, a lot of the information provided is based on the concept of "helping you to help yourself".
You will be expected to put in the time to find information on the sensors you are using and any vehicle specific requirements of your install. (Though the team will always help where they can).
RusEFI is also still very much in development, the dev team provide no guarantee that any of the current features are fully working. It is important that users take a good look at the [current development status](Dev_Status.md) page. This is what we consider the most comprehensive list of the status of all the features of the rusEFI system.
## Identifying your hardware requirements
Every one coming into this p
You are going to need to know
Hall or VR
High or low impedance injectors and flow rate
Trigger style
NTC sensor curves
MAF
MAP
Ignition coils
## What rusEFI board is correct for your engine?
## Getting help
[xxx](HOWTO_ask_questions.md)
## Where to search for information
[xxx](HOWTO-Search-on-rusEFI-wiki.md)