Originally Posted by DanH
Did it need the 75x and 10x? If so, why? What does it deliver to the user?
Might want to explain how "semi-sequential" differs from batch and sequential.
Anyway, it's a feature. What is the benefit? Why do you feel it is better than other systems?
Good questions Dan,
System32 is a migration from entry level automotive electronics designed in the 1990s to state of the art, current technology electronics designed with the reliability, redundancy, engine interface, airframe interface and pilot interface required to properly serve this market. That may sound nebulous, but that's the glossy overview.
We've been involved with microprocessor based engine electronics since the late 1980s. A lot has changed since then with microprocessors and engine management. Not unlike the change you have seen with cell phones from the Motorola brick phone to current smartphone technology. The user interface and processing capabilities available today are light years ahead of what was available 30 years ago. Coincidentally, the processor used in our legacy system was similar to what was in a Motorola brick phone (same brand even).
System32 uses a 32 bit RISC processor (that means it's extremely fast, especially with math processes), a four layer gold plated circuit board, EMI filtering on every connection to the outside world, a high end internal power supply that keeps the ECU running with input voltages from 3.5v to 40v, a high speed user interface (to the Controller) for display and control, seamless integration of two ECUs (the user manages one system).
The high speed math capability of the 32 bit processors allows us to implement fully interpolated 3D mapping for both ignition and fuel control.
This solved a couple of problems that we had with the old system. The old simple mapping causes limitations in handling detonation margins at take off for fixed pitch props and during decent with constant speed props. The new mapping fixes both of these issues and surprisingly is a much simpler scheme to work with as a user. If you Google "fuel map" and look at the images, you will see countless examples of 3D mapping. This is how all modern engine management systems work. The System32 ECUs build the curve between map points, there is no stepping from point to point as in the old simple mapping scheme. New values for fuel delivery and ignition timing are re-calculated after every ignition event (2 times per rev for 4 cyl, 3 time per rev for 6 cyl engines). You have to have a high speed processor to do this. 30 year old hobby processors are not up to this task.
Aircraft environments have a lot of radio frequency events occurring - comm transmissions, transponder transmissions, ADSB output, ignition spark events.
These are all highly energetic electrical events in a vehicle that may or may not have systems properly grounded. The more electrical noise immunity available in critical systems, the better - especially in engine management systems. System32 has extremely good EMI resistance.
System32 is a semi-sequential fuel injection system. Our original system was a batch fire system - typical in original implementations of automotive electronic fuel injection. Batch fire means that the fuel delivery is not timed to the intake valve position. Fuel squirts into the intake tract at some time and the next time the intake valve opens, the fuel gets sucked into the cylinder along with the induction air. Batch fire systems end up with different fuel timing on each cylinder - this works, but is not ideal. Semi-sequential fuel injection is timed to the intake valve opening. Full sequential systems use a crankshaft position sensor to determine which cycle the engine is on and inject fuel only on the intake stroke of each cylinder - fuel is delivered to a given cylinder once every two revolutions of the engine. Semi-sequential systems (like System32) do not include a camshaft position sensor. They deliver timed fuel on every rotation of the engine. On one rotation, the intake valve is open (intake stroke), on the next rotation the intake valve is closed (power stroke). Half of the fuel is delivered when the intake valve is open, the other half of the fuel is delivered on the opposite stroke when the intake valve is closed. The result of sequential or semi-sequential fuel delivery is that there is always fuel delivered in concert with the opening of the intake valve. This yields improved starting, smoother operation, better off-idle throttle response, and greater efficiency.
Other fun things about System32:
Firmware can be field updated with an SD card.
The system logs all system data to the Controller SD card (1, 5, or 10 second increments).
Live fuel tuning via the Controller is VERY simple.
3D maps can be viewed and manipulated in Excel.
Compatible with Tecat torque sensors for live cockpit display of torque and horsepower (turn your run-in stand or your airframe into a dyno).
Proportional and tunable ADI (methanol injection) control for highly boosted engines (Reno).
System32 can be remotely tuned and controlled (UAV).
Live telemetry interface (UAV and Reno).
**** The above functions are all included in the current firmware****
(Now you can start to see the advantages of having a powerful ECU
We had a LONG wish list of features we wished we had when we were using the old ECUs - now we have all of these features and more.