de e1280s super ECU

Hardware:
-12 Injector outputs, which can be used as aux outputs instead
-8 Ignition outputs
-8 Aux outputs, which can drive high or low
-8 digital inputs, with configurable internal pull-up / pull-down resistors
-5 trigger inputs, configurable as reluctor or digital
-4 VSS inputs, configurable as reluctor or digital
-16 general purpose analogue inputs, of which 4 can be configured for temperature sensing, and 2 are suitable for oxygen sensors
-Roughly 400kB of onboard logging memory
-USB flash drive interface for virtually limitless logging to a USB stick
-Headphone output for listening to knock, and it will make beep sounds when the ECU 'learns' values
-Serial or USB laptop interface
-2 more serial ports for devices such as wideband EGO sensors
-High speed programmable logic device (PLD) for most calculations, with a microcontroller only doing tasks such as data flow
-One large loom connector, same as R33 Skyline

Software/firmware/PLD:
-The Super ECU introduces a whole new level of configurability! This has been made possible by the use of an FPGA (a type of PLD / programmable logic device) rather than a microcontroller, for a majority of the calculations.
-The best way to describe this new functionality is as follows...ECUs currently on the market, including the e420c, can be viewed as having fixed 'equations' built into their microcontroller, with a firmware upgrade needed to change anything more than some constants and gains. The Super ECU on the other hand, allows the user to change the actual equations and logic at any time (no firmware change needed), so if the default configuration doesn't do everything you need, you can make the necessary changes yourself using the software!

Now onto the software...

-For those of you who have used any computer programs that utilise block diagrams to implement certain functions, that is what you can expect from the Super ECU software. If you don't know what I mean by a block diagram, it looks like a bunch of blocks with different properties, all linked together with arrows to represent data flow.

-When you first go to set up the ECU with the software, you will be presented with a startup wizard, where you will be asked about your vehicle setup (eg. engine type, sensors being used, control valves being used, what functions you do/don't need etc).

-After completing the wizard, you will see a block diagram representation of the entire logical configuration inside the FPGA. The block diagram is separated into a number of 'pages'  which can be selected from a list.

-The blocks (which we call 'elements') in the diagram could include the following, and more: adders, multipliers, logical operators, comparators, general purpose 2D and 3D tables, general purpose PID controllers, timers, delays, stepper motor blocks, and gauges. There are also 'dedicated elements' for the trigger inputs, analogue inputs, digital inputs, aux outputs, injector outputs and ignition outputs.

-The block diagram represents the equations and logic that are implemented in the FPGA chip, and at any time you can add, remove, or modify any elements on the block diagram. This means that you can have as many 2D and 3D tables as you want (memory permitting) with arbitrary axes and size! And if there is something that we haven't considered or implemented in the default ECU configuration, you can freely add any elements you need to make it work for you.

-Also, you can do closed loop control, of anything by using as many PID controllers as you need.

-Regarding memory usage, we have currently used less than half of the configuration memory, with a very feature-packed default configuration.

-Another very useful feature relates to the injector and ignition outputs. Every ignition and injector output is treated as an independent unit, and parameters such as dwell time, firing angle, and injector duration are all fed to the outputs straight from the block diagram. This means that every cylinder can have entirely different injection and ignition parameters if you choose to do so.

-Finally, there is a built in scope function in the software, which has all the same features as a real oscilloscope, and allows you to observe what the FPGA is seeing on its inputs etc (you can even observe crank/cam sensor signals, and injector/ignition outputs).