ARM based Unidentified Fueling Object - developer info!
The primary application for this board has changed as a result of the ArmEfi growing out of the EC36 connector and the box. The ArmUfo will use the 120X40X2.5mm box and the EC36 connector instead, while the ArmEfi is postponed until we find suitable connector and box.
This board is meant to be the right size for most cars in a standalone application and also scale well when used as a building block in a larger system.
Specification:
Case: Aluminium with 120x40x2.5mm profile.
Connector: AMP Econoseal III 36 pin.
Internal MAP: 4 bar sensor with a 5x3mm pneumatic connector on the front plate.
CAN: 1 internal, and 1 included in the EC36 connector as part of the VEMSLink interface.
WBo2: 1 channel
Sensor Inputs: IAT, CLT, TPS.
Trigger Inputs: 2 VR/Hall channels.
Power outputs 16..17 (limited by EC36-pins)
4 push/pull outputs (e.g. stepper motor) - we don't have enough EC36 pins for 8, and we roll a nice solution (VEMS-link) for connecting devices.
AND
11..13 (likely 12) DPAK outputs sound right (including WBO2 heater).
- all of them are flyback capable, except 2..3:
- 1 FET for WBO2 heater
- 1..2 HV IGBT output that can drive relay or small solenoid
- flyback for max 3 can be throughole (or simple SMB diode)
8 channels that are capable of controlled flyback (with PNP darlington DPAK)
- exactly 8 DPAK outputs can be high-freq PWM-ed (64usec, for injectors). The rest can be soft-PWM-ed, like 30 Hz for boost solenoid
- and 5 DPAK outputs can be IGBT HV (for ignition coil). 6 might be possible, but 5 is important.
As you see (8+5=13), so either we have
- 13 DPAK-s
- or 12 DPAKs, but than 1 channel is hibrid: HV capable with optional controlled flyback (not populated in certain configurations)
optionally - likely DROPPED: 1 lowside driver with 350mA rating, limited to fuel pump relay or small solenoid SOT23 NPN should be fine. protection:
- Some flyback gizmo (BAW56?)
- something that can handle the current with some margin, having a polyswitch to protect it would be nice.
This is a space-saving thing, so the 350mA driver can be left off if(DPAK>=12) => so the 16 EC36 output pins (this includes stepper) cannot decrease. Makes little sense, an IGBT without flyback should be better for almost same footprint
Usage
- For a V8, a CDI board would be used or injection would be 4 banks and 4 ign outputs for wasted spark.
- For a I5, 5 inj + 5 ign + 1 WBO2 + 0..2 outputs for other stuff (boostcontrol, etc...) This is the most demanding configuration that is likely to be supported by the limited EC36 pincount
- For an I6, 6 inj + 3 ign with wasted spark
Note that above setups would use boards populated different way: differentiated at PNP-time.
Case relevant issues
It is very important to have IO buttons (how many?) on the box, having a keyboard in the car at all times is not practical. This also makes it possible to make a compact hand held tuner that can tune the ArmEfi and other VEMS frontier products. I guess it is the question of a free digital or analog input(s), and the rest is mechanical (case) issue.
MMC slot ?
- I think the MMC can live inside, without the possibility of removing (maybe soldered)
- anyone insisting on removable MMC slot ?
This (armufo??) is a multi application board, it can be used for the following applications:
With (external ?) display and buttons:
- MAF replacement / MAF tuner.
- WBo2 Lambda meter (? why would someone use this instead of a standalone? maybe this is ment logger box with internal WBO2 controller )
- Boost controller.
- Exhaust temp meter.
- Additional fuel controller.
- Handheld tuner for ArmEfi and the other CAN enabled boards. I highly doubt that this would work. A logger and control board can be merged reasonably. A UI (user-interface) board cannot. (well, apexi makes profit from boost controllers made this way, but separated UI and controller is remarkably better).
- Entry level engine management system with integrated display (how?) and user interface.
See also
- VemsFrontier/Boards is the family where this belongs