VemsFrontier/ArmUfo (2006-03-16 04:43:08)

ARM based Unidentified Fueling Object - developer info!

ufo.gif

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..18 EC36-pins

11..13 DPAK outputs sound right (including WBO2 heater)

4 push/pull outputs (e.g. stepper motor)

1 lowside driver with 350mA rating, limited to fuel pump relay or small solenoid SOT23 NPN should be fine. protection:

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.

Usage

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 ?


This (armufo??) is a multi application board, it can be used for the following applications:

With (external ?) display and buttons:


See also