Yes, as I know rusefi can control coil directly. EEC-IV doesn't control coil directly, but is uses EDIS. EDIS sends PIP signal (12V) to ECU which is information about engine speed. ECU replies for PIP signal and sends SAW signal to EDIS (5V). SAW Pulsewidth control timing advance.
AW Pulsewidth (usec) = 1536 - (25.6 x (desired spark advance in degrees))
Range: 64 - 1792us (57.5° BTDC to 10° ATDC)
Resolution: 4us (5/32nd of a degree)
Example:
You want 29 degrees of advance.
PW = 1536 - (25.6 * 29)
PW = 1536 - (742.4)
PW = 793.6
Without SAW signal timing is 10 degrees BTDC.
EDIT:
russian wrote:V6 is supported - you need to specify six cylinders in TS
36-1 trigger is supported - you need to specify trigger type 36/1
batch injection also supported
1-4-2-5-3-6 was not supported 30 minutes ago but I've just added 1-4-2-5-3-6 support so if you update to latest version you would be able to select 1-4-2-5-3-6 firing order in TS
We did not yet start any EDIS engines but I am sure that this would not be a problem. Once you have the hardware side ready we will take care of what could be missing if any. Supporting people with real hardware is my top priority

Thank you for support 1-4-2-5-3-6.
If you want to make something to support EDIS by RusEFI, you can use simple square wave generator witch 50% duty cycle.
5Hz signal is like 100RPM
50Hz - 1000RPM
315Hz - 6300RPM - rev limit for my engine
^^ it's for 6 cylinder. For 4 cylinders frequency should be multiply by 2/3 - (~3,33Hz - 100 RPM, 33,3Hz - 1000RPM, 210Hz - 6300RPM etc.)
For one PIP signal RusEFI should generate SAW signal, which pulsewidth depends on timing advance. EDIS also generate IDM signal for ECU, which is use for diagnose, so now, we can skip it.
I think that support EDIS is good idea, because RusEFI could be used without wiring modification - EDIS is in engine bay, ECU is under dashboard.