|Planning Your DIY EFI Project
|Page 1 of 1|
|Author:||Fred [ Mon Dec 05, 2011 12:54 pm ]|
|Post subject:||Planning Your DIY EFI Project|
Properly planning your project will give you a much better chance of it being successful and of you being satisfied with the final result. Conversely, failure to properly plan your project is likely to lead to disappointment and possibly outright failure.
The first thing to do is determine your fundamental resources:
You should be realistic about all of these things up front; there is no point in lying to yourself about any of them, it will only lead to disappointment later down the road.
The second set of things to determine are the details of your goals:
You should be realistic about this too. It's more reasonable to do things in stages such as "Control the fuel injection only" and then "Add full ignition control" and then "Add a turbocharger system" etc.
The third thing to do is determine what is required to achieve your desired outcome:
The posts in this guide thread will attempt to assist you in working out what is required to achieve your goals. This thread is not FreeEMS specific and will suggest that you choose another system if FreeEMS can't meet your needs in an acceptable way when measured by your own requirements.
|Author:||Fred [ Mon Dec 05, 2011 3:00 pm ]|
|Post subject:||Choosing A System|
The number one most important thing to decide for an engine control project is which EMS solution you're going to use. There are literally dozens of options available, but in terms of DIY, there are only a few choices each with distinct advantages and disadvantages.
No matter which system you choose there are two important all encompassing rules that should guide your choice:
In other words, don't make your decision on EMS hardware a year before you plan to start installing it, wait until you have to start committing and buying things. And don't wait for products that are promised as coming soon, and yes, that includes FreeEMS firmware features and hardware implementations.
At this point, before proceeding further, you need to know your goals, desired outcome, desired results, acceptable timeframe and budget. These requirements will quickly and accurately dictate which system you choose, or perhaps that you need to rethink some of your goals to better match your timeframe and budget.
In terms of engine control requirements the fundamentals are as follows:
Each of these things requires support in both firmware and hardware, assuming that you have the physical engine hardware required in the first place.
The main things that need to be considered are outputs and output style. For example, the following limitations apply to each listed system type:
To understand how these limitations apply see this excellent thread which explains what you can and can't do with FreeEMS at this time. Note, having only 6 output channels is a temporary restriction, but remember the two rules above (decide later, it could have changed, don't wait, it may take longer than you think). Support for more channels than you could ever hope to need is planned for early 2012 in release 0.4.0 of the firmware.
Some general (and obvious) considerations:
The system also has to be able to handle your inputs properly. The critical sensors are the RPM and position sensors whose style varies significantly with each requiring custom and specific support. Each system listed below supports a varying number of systems at this time, and some are expanding daily.
Support for more than two position sensors is limited in most designs, as is cam angle measurement and control.
Temperature sensors are usually straight forward, and not to be worried about. Likewise for load sensors, most MAP, MAF and TPS are easily supported.
If you have devices to control that aren't core engine control items then you'll need some way of handling those too. I'll run through each listed system with pros/cons in this regard.
MS1 - Common devices are supported, but implementations are usually crude, there aren't enough pins to run them all at the same time, there is no code space to add new stuff without removing other stuff anyway, and that would imply having the skill set required for assembly programming.
MS2 - A good selection of devices are supported, but implementations often carry regressions and faults that remain unfixed for, quite literally, years, there aren't enough pins to run them all at the same time, and the C code is really quite dirty and fragile and therefore difficult to modify without breaking it in the process.
MS3 - An excellent selection of devices are supported, the implementations, at the time of writing, are mostly exactly the same as MS2 and carry the same flaws and risks, but with an additional downside of not being able to fix them or customise them or add new features at all due to it being completely closed source. On the brighter side MS3 has sufficient pins to run almost everything at the same time, assuming the software is suitably flexible.
FreeEMS - Absolutely no accessory code exists at the time of writing (early December 2011) however it is straight forward to add such things as new user requirements pop up with new installs. Custom functionality not available in any of the MegaSquirt family of products can be added freely and custom hardware to cleanly (without masses of jumper wires and hacks) can be designed to support such functionality. This is not permitted with the MegaSquirt family of products.
Aside from having no accessory code and limited injector/ignition outputs for the time being, there are some other differences to consider.
Speed-density basics-only implementation: This is only temporarily true, however for the time being there is very little in the way of basic normal run-of-the-mill features that you'd expect to find on almost any system. Things like rev limiters, transient enrichments, idle control, GP outputs, The reason is that such code only gets in the way while working on other aspects of the system and thus they are being left out until needed by an actual user who is installing or has installed FreeEMS on their vehicle.
Alpha development status: Due to the fresh clean-sheet implementation and limited testing all users of FreeEMS will need and want to be actively involved in the development community in terms of testing new code, new hardware and providing feedback and issue reports for developers to more efficiently improve the system. This is not for everyone. Testing new code that relates to your ignition timing and AFR really is dangerous and this will be done entirely at your own risk. The same can be said about MS2 and MS3 (MS1 is pretty mature and stable with known manageable weaknesses), with two key differences:
I believe the above is a fair representation of the truth and I hope it helps you in deciding which direction to go in for your project, whatever that may be!
|Author:||Fred [ Mon Dec 05, 2011 5:44 pm ]|
|Post subject:||Time, Skills And Costs For FreeEMS|
Time, Skills And Costs For FreeEMS
|Author:||Fred [ Mon Dec 05, 2011 6:19 pm ]|
|Post subject:||The Waiting Game|
The Waiting Game
Even though I put the "rules" in a larger font, I believe that this warrants its own section too.
Never wait to start your project.
Never ever wait for projects that will be "ready soon", FreeEMS included. You could be waiting years, or even grow old and die before you see the likes of UltraMegaSquirt, which is still described online as though it's a current project. In professional software development as a service for big corporates it is common practice to take a programmer's estimate and multiply it by a fudge factor to make it more realistic. It may or may not surprise you to find out that that factor isn't +10%, but more like +150%, or times 2.5. So something that the developer says will take one year could take three years or even more!
On the other hand, to ensure that you have the best possible product for any given project...
Always wait to make your decision.
Always wait till the last possible minute to make a final commitment to use a certain product as a lot can change between when you start investigating what to use and when you actually need to place an order and get on with making the project happen. Thus waiting until you're really truly ready to start the install before you make your decision is beneficial and allows you a maximal choice of the best range of options with the lowest possible price and best technology.
Ignore the advice in this post at your peril! :-)
|Page 1 of 1||All times are UTC [ DST ]|
|Powered by phpBB® Forum Software © phpBB Group