* connect the 36-1 VR trigger directly

* and drive the coils directly

* and throw away (or sell) the EDIS module

The advantage of this:

* bigger ignition window (eg. for ALS and launch ignition retard )

* better control over dwell.

EDIS should work in 1.0.x branch (with genboard v3.x). Testing needed if you want EDIS with 1.1.x (I cannot see much advantage of 1.1.x with an EDIS setup though)

The reason for EDIS in old times was to drive multiple coils with the limited number of outputs (genboard v2). Genboard v3 has many outputs.

However, the code to drive EDIS (quite simple, much simpler than directly driving coils) has been there for several years.

Th most important configuration variable (from global.h):

<code>

uint8_t ign_out; // EDIS:0x0? dummy: 0x7? disable:0xff bit1: ign_dual_out bit0: invertout

</code>

That is, ign_out=00 (or 01 for inverted SAW output polarity) needed instead of ign_out=70 (that is dummy ignition)

The rest is same,

* ignchmax=03 (for 4 cyls)

** ignchmax=05 (for 6 cyls)

* set all ignition outputs to the same, digitaloutput where you connect SAW GenBoard/Manual/DigitalOut/Table

** h[2]=20 20 20 20 20 20 20 20

* ign_dwell variables shouldn't matter, maybe set 2 msec

* what output is normally used for SAW ?

** s259 (stepper) ??

** or i259 logiclevel ??

** or i259 power IGBT output ??