![]() |
SDS EM-6 EFI ECU
We've got 10 new features planned for the new EM-6 which will commence hardware development sometime in April it looks like now. We have 3 other optional ideas to explore as well and we've explored and discarded 2 other ideas already.
While we won't be able to make the design process on the EM-6 as open and interactive as on the CPI2 ignition system due to other players in the field, we are very interested in having customer input on features they'd like to see in the new ECU. We often find that great ideas come from outside. I won't be able to confirm much of what will be new for sometime but we'll listen to your feedback for the next 30-60 days or so before we freeze the wish list and get down to full scale hardware and software development. We hope to release the EM-6 in the late 4th quarter of 2020 but that depends on how many new features are incorporated and how long they take to develop and properly test. We see one possible avenue, if adopted, may extend the development time past this date. Development time available is also impacted by our order backlogs for EM-5, CPI/ CPI2 and our other aviation and automotive products. This varies considerably with the time of year. We have to take good care of our customers and keep money flowing in the door to finance the new R&D projects. As I mentioned previously in another SDS thread, we have the well proven EM-5 EFI/EI systems currently available and all FULL AVIATION system buyers (complete EFI kits) in 2018-20 will be eligible to receive a free EM-6 ECU when they are available. This way, there is no delay in getting your project flying but you can enjoy the additional features of the new ECU when it's released. |
I probably won't be ready to buy for at least another year, but...
Some form of closed-loop mode (with a toggle switch to enable?) and selectable AFR would be really neat. RPM and MP defining an array of fuel and timing values instead of independent lists would maybe give a way to automatically go lean at certain conditions? Basically, I'd just be looking for a way to avoid having to deal with mixture at all. Not having actually used your system yet I can't really think of anything else. |
ideas
Hi Ross,
just spitballing here but.. how about eliminating the need to manually select injectors AorB and the associated relays for this IF an ECU goes out? maybe better said... a full up autonomous running system if an ECU goes south. Thanks for requesting the input from the field! |
I second dual systems with no external relays, and no required pilot intervention to maintain power after a system failure.
Human pilots will never correctly diagnose a power loss and flip the right switches 100% of the time, in particular at low altitude. |
EM-5 switches
![]() For those not sure about this conversation, the areas circled in red are the necessary switches for an EM-5 setup. My electrical system is very similar to a Nuckells Z-14. ECU 1 runs 4 sparkplugs ECU 2 runs the other 4. In order to lose all ignition I’m having a really really bad day, As such I don’t have an inflight ignition emergency checklist. The plan is put it on the ground ASAP. The switch in question on this thread is on the far right, “INJ”. The fuel injectors can only be run by one ECU at a time. Engine runs rough: 1) Swap fuel tanks - assumes starvation or single tank contamination. 2) Flip the three yellow switches - assumes bad fuel pump or bad INJ power, I don’t really care which one at this point. 3) Engine runs good, yay! engine still bad, look outside and land. I could eliminate this procedure with two changes: 1) Automatic fuel pressure sensing and redundant pump engagement. 2) Automatic fuel INJ switching as suggested in this thread. If the above enhancements are included, I would really like it to trigger the red Error Message LED and send a notification to the controller screen. NOTE: Error message LED and Controller screen not shown in the picture above. Also not shown are the two coil switches only used for preflight. |
Nice clean layout Marvin.
With regards to auto switching of fuel pumps and injectors. We've considered this before and it comes back to a lot more hardware in between the controller and device. To have a true backup, you need to isolate the dead or shorted component or it's useless. This almost always involves relays which adds more wiring and connections. If we take the case of the CPI2 where we went down this path, it more than doubled the size of the PCB and component count to do the OV and auto switchover and tripled the development time. You start to question if this is really more reliable than having the pilot flip a switch, especially when historically, these events are exceedingly rare. I'm not saying we won't investigate these ideas but we'll be taking a harder look on benefits vs. complexity weighting after the CPI2 experience. One of the reasons why we've had such good reliability on our hardware for a couple of decades is that it was simple. The first word in SDS. Components which aren't there can't fail. Is it wise to add many layers of complexity for events which almost never happen? |
"Simple" for who? The builder/supplier or the operator/pilot?
"Is it wise to add many layers of complexity for events which almost never happen?" It depends on your prespective. |
Thanks Ross
Quote:
|
Quote:
|
Quote:
|
| All times are GMT -6. The time now is 02:52 AM. |