I shall report here some of the problems I had while configuring the parameters (odd-fire, coil type, 3 usable prim trigger engine).
Missing primtrig pulse in the case of the coil type trig setup
I was steadily driving at 60km/h entering a tunnel in a busy trafic. At the time I switched on the lights the engine shakened badly, made big noise, big smoke behind the car, seemed to have no more power.The engine stopped when clutching off. Then the engine restarted ok when clutching on by the car still moving on.
At my parking slot, I was able to record the trigger log of what may has happened the night before.
Switching on and off the car lights, I noticed that sometimes the engine was accelerating or slowing or eventually may stop.
Here is trigger log when the engine stops. (prim trigs are 30°, 90°, 30° apart, there are 3x2 pulses on the crank wheel). One can see that Vems came out of sync but was still firing.
Here is the same log without the fire events.
It shows that one prim trig is missing (@ first complete revolution).
Indeed, to further what the Vems support has told me, with a reasonable setup like a 60-2 an extra trigger pulse or a missing pulse does not cause serious out of sync. However for a low tooth count setup such as coil type, the trigger pattern can have a high quality signal, (I scoped mine several times before), but comes to get a default, per ex. because a ground problem occurs (one does not install a non oem ecu on a new car).
I believe that an operational software should detect those trig errors and takes proper action: This does not seem to be a big fw update to check if the incoming pulse is in a good window or not, and, if it is not the case, do re-sync (per example)
At least, Vems should let people know that there is no trig error management with the coil type set up and that there is some risk of engine damage or car crash in a tunnel incoming Paris ;p)