Hi Guys,
I'm getting close to the finish line of implementing the software of the VeeCU. I'd like to bounce some ideas off you guys.
A little background. Listening to Jeff's pod cast on SDS EFI is what sent me off on this adventure.
Ref.:
http://www.sonexflight.com/58/index.html I wanted to implement an EFI system with the AeroInjector as a backup. I started studying the available solutions and,
since I knew nothing about fuel injection, I was somewhat intimidated. So I started studying EFI and envisioning what I wanted. What kept popping into my head was simple. I want it to be safe and simple.
Here is what I came up with: As currently designed the cockpit interface to the VeeCU consists of four miniature momentary SPDT toggle switches for cylinder fuel trim. A store push button to transfer user settings and fault codes to non-volatile memory. A potentiometer to adjust mixture setting. And finally a status LED to indicate operating status. That's it.
User settings consist of:
Fuel Flow Trim (%) used to make fine adjustments to the simulated Red Cube output.
Four cylinder trim (%) [-15.0 to 15.0] used to balance fuel flow between cylinders.
Prime Strength [0-5] is a multiplier for the first injection pulse during engine start to prime the engine.
Accelerator pump sensitivity (mBar). Wanting to keep the number of sensors to a minimum, I don't want to add a Throttle Position Sensor. Instead, manifold pressure change is used to sense increased load and the need for a little extra fuel. The Accelerator pump sensitivity is a threshold below which a MAP change will not trigger any extra fuel.
Accelerator pump gain [0-5]. A scaler for How much fuel to add during an accelerator pump event.
A set of fault codes. Any fault code, even if it clears, that occurred during the last flight is retained and displayed again at engine shutdown. Since all that is available is a LED to flash codes, a press of the store button saves the codes in non volatile memory so the pilot can shut down and go find the list of codes to see what happened. All user data is retrieved when the unit is powered again. The codes are then stepped through/cleared by toggling one of the trim switches with the engine shut down. Another press of the store button will permanently clear the codes. A bit of a pain but it eliminates the cost and complexity of a display. BTW, No changes are made permanent without a press of the store button.
So what do you guys think? Am I crazy? Do you have to have a display to have fuel injection? There isn't one in my pickup :-)
And here's a decision that I've been postponing. One of the aux outputs is intended to drive a fuel pump relay. The intent is to disable the fuel pump in the event of a mishap. Exactly what logic should be used to disable the pump. One thought is to enable the relay at power up and disable it after RPM has been above maybe 2400 and then returns to zero. I'm open to suggestions.
Edit: BTW, here is what Ross from SDS has to say about it in his EM5 manual.Optional Fuel Pump Relay
SDS units can be equipped with an optional output to control a relay to switch the fuel pump off when the engine
is not turning over. This feature is designed to prevent the pump from emptying the tank in a serious accident.
The pump relay is energized for 2.8 seconds when power is turned on to pressurize the fuel rail until the EM-5
detects crank rotation. If the engine stalls the EM-5 will shut off the relay in 2.8 seconds. There is nothing
programmable for the fuel pump relay.
More on the "Tune" later.
Thanks,
Wes