MembersPage/GunnarReynisson/FirmwareRequest (2012-01-10 21:49:38)

MAT / TPS ignition retard should be MAP based, or configurable ( MAP or TPS )

Agreed, working on it (more work in VemsTune than in firmware).

TPS makes sense for engines that might not have MAP sensor at all. (ITB normally aspirated).

MAP is usually better and easier to tune.

So choosable is best.

I´d like to check how this is going on?

Input for Coolant temp and air temp can be selected from non pullup analog inputs

This allows parallel installations to be done more easily.

ECU is setup for Cam sync but still runs if camsync fails.

This is easily handled by allowing configuration of outputs (ignition) in the dual config if camsync fails.

Engine operations are not affected by the loss of camsync therefore.

Idle fuel/ignition map.

Something like a 6x6 map that only is activated during idle condition (below rpm, below tps)

Y axis can be MAP or Idle control duty cycle, selectable between each no matter if main strategy is alpha-n or speed density

This is done to get an even steadier idle without fluctations as well as low engine speed low throttle conditions which may require different ignition and fuel.

VE value resolution increase

At least a half a point or more

88-89 becomes 88.0 , 88.5 , 89.0

Mass fuel option fuel table.

Ideally 0-Xms opening time curve that represents volume

multiplied by a factor for fuel density. Allow addition of fuel temperature compensation from analog input. Especially important for low resolution pulsewidth when flow is non linear to have the curve and massive injectors.

Ecu then chooses the appropriate pulsewidth based on the curve from the mass wanted from the fuel table.