
injconf.c should be configured according to the 
diagram at the bottom of:
http://www.x-dsl.hu/genboard/eventqueue/

-----------
Say the ms is running with the eventqueue. Engine spinning at 6000rpm <=> 5 ms between ignition pulses/fuel injections. Injector dutycycle cant be >100% so max opening time is 5ms. Throttle is quickly pressed thereby activating acc. enrichment pw=normal_pw+acc_enrich=x where dutycycle(x) can be greater than 100%.... 
Instant message from 14692717:
hmmm... now I got pretty confused myself!

Well, the first ign-event will schedule a long pulse (normal+acc), and since dutycycle is > 100% the injector-closing will be after the next ign-event. The second ign-event don't see the acc and schedules a normal injection. This injection will cancel the acc. enrichment.

We keep a inj_open_till variable, and always know if inj is still firing.

When you execute (dispatcher) inj1start, you schedule inj1stop and next inj1start.
If next inj1start happens to be before inj1stop (>100%), we can skip inj1stop (what
about pwm?) 

msg# No problem here, if inj1stop>=next inj1start, we simply drop inj1stop
msg# inj1start is still needed, since that will schedule later events...


//-------------- dont_stop_me_now NOT NEEDED if the offending inj1stop is dropped
msg# If you see at injstart (examining the firing flag) that previous 
msg# inj is still firing (we can also have scheduled_stop_time), you
msg# set a dont_stop_me_now flag, so that injstop knows that it should not stop.
//---------------------------
