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:
Box: Aluminium profile 120X40X2.5mm
Connector: AMP Econoseal III 36 pin.
Internal MAP: Yes, 4bar sensor.
CAN: Yes, 1 internal and 1 on EC36 combined with VEMS link.
WBo2: Yes, 1 channel with PnP capability.
Ignition power stages: Yes, 2. Both can be configured for low voltage flyback if external power stages are used. Current limiting for protection of coils when engine stalls? How?
Injector outputs: 6, high or low impendance with switched flyback. How do we protect against short circuit?
Trigger: 1VR/Hall channel and 1 Hall only Note, no VR chip. VR analysis made in software after beeing sampled with ADC
Basic sensors: IAT, CLT, TPS.
Pushpull outputs: Yes, 8. Why this many? - Because there are well protected stepper chips and they are suitable for fuelpump relay, boost solenoid, variable cam timing, variable intake, stepper idle motor, tachometer output and even for driving external ignition modules.
VemsLink: Yes (VEMS link is a high speed CAN and two open collector trigger signals that can be configured as input or output.)
Description of old ArmUfo, move functionality to other board if it doesn't work together with the new specification above.
This is a relatively simple, cheap, minimalistic board, 2 steps below GenBoard/VerThree functionality, somewhere near (not yet existing) ultramegasquirt complexity.
Main idea is to cover mass-applications (that require only simple installation instructions and configuration) with unbeatable cost.
A similar, but more powerful board is VemsFrontier/ArmEfi - make sure to study that deeply.
- max 1 LM 1815 VR interface + 1 square wave input.
- Internal MAP sensor ?Yes very important -Jörgen
- CLT, IAT and TPS sensors.
- 6 DPAK IGBT's with optional simple hole mount flyback. Used for IGN and INJ. HighZ or LowZ capable. You'll know why the flyback is hole mount after soldering a SMD component to a board with 20 wires attached:)
- 1 Bosch LSU Wbo2 sensor controller
- just 1 L293 Stepper driver IC's configured as 4 push pull outputs or as a stepper driver. Can be used to trig up to 4 external ignition modules.
- just 1 CAN bus
- max 2*Knock sensor input (ARM-processed), definitely no TPIC8101
- NO EC36 connector (flying loom is OK)
- 1 EGT input (eg. with AD597AR)
- PS2 and LCD connection planned-in
- 6 buttons for IO interface.
Cost of last 2 must be evaluated during routing. There is a little wrestling going on here :-)
Notes:
I think that 6 open collector drivers is enough, all of them can be ign capable since we use flying lead. It takes up very little board space. The multi channel ignition capabilities opens up ignition expander & ignition driver applications.
I also think that the flyback diodes should be hole mount since this makes it simpler for end user to configure. Soldering SMD on a board with wires attached sucks.
It is very important to have IO buttons 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.
This is a multi application board, it can be used for the following applications:
With display and buttons:
- MAF replacement / MAF tuner.
- WBo2 Lambda meter.
- Boost controller.
- Exhaust temp meter.
- Additional fuel controller.
- Handheld tuner for ArmEfi and the other CAN enabled boards.
- Entry level engine management system with integrated display and user interface.
Sealed box without display:
- Ignition expander & ignition module. (without display)
- EMS with flashed (what does this mean?) calibration or for use with handheld tuner.
See also
- VemsFrontier/Boards is the family where this belongs