From fb986bcebff0b3f1e90ee5f9a273d2834310c0ce Mon Sep 17 00:00:00 2001 From: OrchardPerformance <49926376+OrchardPerformance@users.noreply.github.com> Date: Sat, 30 May 2020 04:02:52 +0100 Subject: [PATCH] Ignition FAQ first draft and start of "what we cannot do" (#58) * 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 * 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 * Create Pages_Hardware.md * Update Pages_Hardware.md * Sensor and Actuators index * Start of Ignition Index * Create Fuel_Injectors.md * Moved file * Added PNP72 jumper info * More updates + Software pages * Update MREAdapter72.md * docs * Create Roadmap_Fuel.md * Created Kit Instruction link * Dev_Hardware_Guidelines * Images and links update * Update Dev_Hardware_Guidelines.md * Update Dev_Hardware_Guidelines.md * Update .gitignore * Updated Dev_Hardware_Guidelines (markdown) * Updated Dev_Hardware_Guidelines (markdown) * Fixed pictures * Ignition FAQ and start of what we cannot do Co-authored-by: rusefi --- Dev_Hardware_Guidelines.md | 12 ++--- FAQ_Ignition.md | 89 ++++++++++++++++++++++++++++++++++++++ Pages_Ignition.md | 5 ++- What_rusEFI_Cannot_Do.md | 24 ++++++++++ 4 files changed, 122 insertions(+), 8 deletions(-) create mode 100644 FAQ_Ignition.md create mode 100644 What_rusEFI_Cannot_Do.md diff --git a/Dev_Hardware_Guidelines.md b/Dev_Hardware_Guidelines.md index 5983cd23..965ab988 100644 --- a/Dev_Hardware_Guidelines.md +++ b/Dev_Hardware_Guidelines.md @@ -44,7 +44,7 @@ http://rusefi.com/wiki/index.php?title=Manual:Hardware_Frankenso_board #### - Brain board -![alt text](images/Vyuqd8h.png) +![alt text](Images/Vyuqd8h.png) The brain board can be the off the shelf STMDiscoveryF4. However the Discovery has several circuits like the analog microphone circuits which change how a particular pin is loaded. We have noticed that this pin loading cause the injector circuits to vary pulse widths. Because of this we have developed a stripped down version of the discovery board with out the extra circuits. Both boards have the same general specifications, same clock rates, same IO headers with the same pin out's, ect. Forum thread about this PCB found [here](http://rusefi.com/forum/viewtopic.php?f=4&t=381) @@ -55,7 +55,7 @@ Forum thread about this PCB found [here](http://rusefi.com/forum/viewtopic.php?f #### - Frankenstein -![alt text](images/20140224_state.jpg) +![alt text](Images/20140224_state.jpg) Frankenstein is a combination of individual modules, such that you can make sub modules, then combine them with a script. The end result allows you to prototype a small board, then once you have verified the small board, you can combine it with the larger module. If you don't want all the features of Frankenstein, you can mix and match as you so choose. Frankenstein is a combination of the below. - Forum thread about this PCB found [here](http://rusefi.com/forum/viewtopic.php?f=4&t=359) @@ -73,11 +73,11 @@ Source file for the schematic found [here](https://sourceforge.net/p/daecu/code/ Links to misc schematics J701 NEON engine schematics -![alt text](images/120px-TPS-INJ-IAT_schematic.jpg) -[120px-TPS-INJ-IAT_schematic.jpg](images/TPS-INJ-IAT_schematic.jpg) +![alt text](Images/120px-TPS-INJ-IAT_schematic.jpg) +[120px-TPS-INJ-IAT_schematic.jpg](Images/TPS-INJ-IAT_schematic.jpg) -![alt text](images/120px-IGN.jpg) -[120px-IGN.jpg](images/IGN.jpg) +![alt text](Images/120px-IGN.jpg) +[120px-IGN.jpg](Images/IGN.jpg) Found in this thread [link](http://rusefi.com/forum/viewtopic.php?f=3&t=360&start=52) diff --git a/FAQ_Ignition.md b/FAQ_Ignition.md new file mode 100644 index 00000000..9e3ceb89 --- /dev/null +++ b/FAQ_Ignition.md @@ -0,0 +1,89 @@ +# Ignition FAQ + +One of the most common themes with rusEFI is people wanting to know more about igntion and what ignition hardware rusEFI can work with. +The topics below are an attempt to cover as many of the common key questions we get asked. + +--- + +## Will rusEFI work with my "XYZ" coils? +In theory rusEFI will work with any coils from nearly any vehicle produced since the daimler motor carriage of 1901. +In reality there are some practicalities to that mean some coils are easier than others. + +The rusEFI ignition circuits are designed to work at 5v and are not designed to resist the large currents produced when controlling an ignition coil. "Well that's is no good!" I hear you think, actually it is perfectly fine provided certain conditions are met. + +The outputs of the rusEFI hardware are able to operate an ignition coil driver (IGBT) but not the coil directly. +This means that more modern "smart" coils that have an IGBT built into the coil can be driven directly. +Older style coils will need an ignition coil driver added between the rusEFI output and the ignition coil. + +--- + +## But why did you not build the ignition control driver (IGBT) into the ECU? + +Quite simply for the same reasons modern ECUs do not have them either. +1. It reduces the number of parts needed for the ECU and thus the cost +2. It means the IGBT component is replaceable as they do sometimes fail +3. It moves the electrically noisy high current/voltage components away from the sensitive MCU +4. The shorter the physical length of these (actually quite sensitive) high current/voltage circuits the better, it reduces the total EMF signature of the vehicle, it reduces the weight of the vehicle as the wires can be smaller and most importantly it reduces the losses and means there is more energy available for the spark. + +Most more modern ignition coils are smart for these exact reasons and in order to work with these nice modern, high power low weight COP coils we have a 5v output. + +--- + +## OK you made your point but what coils do I need? + +That all depends if you want to buy new coils or already have some. In general we would advise to buy "smart coils" but we are also big fans of working with what you have or raiding the junk yard (read this as we are tight). + +--- + +## Thanks but that really did not help, please tell me exactly what to do? + +OK, ok, this question needs tackling in several parts, please pick the option you need below: + +
I want to buy new coils + +If you are looking to buy new coils then we would recommend taking a look at the list of Ignition coils that have been tried with rusEFI. +[List of ignition coils](Vault_Of_Ignition_Parts) +In general though we recommend trying to get a tried and tested solution and getting coils that are easily available in your local area. + +
+ + +
I have existing coils + +
My coils are newer smart coils + +Great, then you can wire them directly to the ECU. +However please take care to check that tht coils you have really do incorporate the ignition driver into the coil. +Having 3 or 4 connectors pins is not a guarantee that a coils is a "smart" coil. + +
+ +
My coils are older dumb coils + +Great, same as the smart coils please double check your coils are actually simple coils without built in ignition modules. +You will need to source an external ignition module to go between the ECU and the coils. +These are generally quite cheap and can be found on some cars in the junk yard. We also made our own simple module [here](fix link) + +There are some tested Ignition modules on the Ignition components list. +[List of ignition components](Vault_Of_Ignition_Parts) + +
+ +
+ +--- + +## I need an ignition module, what now? + +Most older coils will need this and some cars have them as standard. +These are not to be confused with the EDIS module that some ECUs require that is a more complex unit that does some of the functions for those simpler ECUs. + +There are several available modules some are listed on the Ignition components list. +[List of ignition components](Vault_Of_Ignition_Parts) + +--- + +## What about adding IGBTs on the board to drive coils directly? + +Actually we already have this in the form of the Prometheus and Hellen boards. +These boards are intended as all in one solutions. \ No newline at end of file diff --git a/Pages_Ignition.md b/Pages_Ignition.md index cb2894ab..e5ed491f 100644 --- a/Pages_Ignition.md +++ b/Pages_Ignition.md @@ -1,13 +1,14 @@ ## Master list of Ignition pages +### [Ignition FAQ](FAQ_Ignition) +
rusEFI Project * [rusEFI Project Ignition](rusEFI-project-Ignition)
- -details>Ignition Wiring +
Ignition Wiring * [Basic Ignition Wiring](FAQ-Basic-Wiring-and-Connections) diff --git a/What_rusEFI_Cannot_Do.md b/What_rusEFI_Cannot_Do.md new file mode 100644 index 00000000..95428959 --- /dev/null +++ b/What_rusEFI_Cannot_Do.md @@ -0,0 +1,24 @@ +# So what are the limitations? + +While we try to be as helpful as possible there are a some things we just cannot do, this page attempts to outline them and explain a little of why it is not possible. + +## Custom hardware + +We get a lot of questions along the lines of "Can rusEFI run on XYZ processor?" or "Can rusEFI use XYZ chip in its circuits?" the current status of the rusEFI project means that there is little time for + + + + +## Custom code support + + + +## Individual component/vehicle help + + + +## Installation + + + +## \ No newline at end of file