This block indicates the type of coil combinations that can be used with this firmware. Some firmware programs will allow the user to select between the different coil combinations on his engine. Note: If you have an intermediate or lower hardware class ECU, you may only use single coil with distributor. Most COP coil per cylinder engines are fired in wasted spark configuration and each coil will have its own driver. (See the wiring diagrams for connections.)

The combo files can be loaded into intermediate, advance or ultimate ECU’s. In an intermediate ECU only the single Distributer option will be available. In an advance ECU the tuner my select between single and wasted spark. Ultimate also has Full Sequential spark on some firmware.

Note! On the Rotary programs the tuner may select between coil per cylinder or wasted spark. If the engine has the three coil setup where the leading spark plugs are on a wasted spark coil and the trailing are on coil per cylinder, this value is set on wasted spark. The two leading coil trigger wires must be tied together on the wasted spark coil negative. (See the connection diagrams). The charge time for the leadings will combine without overlapping and destroying the coil. Note that on high RPM’s the leading spark will become weaker due to less time available to charge the coil. It has to charge twice per revolution.

Dual distributor
Two ignition coil outputs will be activated and phased to run a dual distributor system as found on the Lexus 1uz-fe and BMW V12,

Single distributor
Only one ignition coil output will be activated and phased to run a single distributor. Old school engines use these types.

Wasted spark coil pack
Coil outputs equal to half the number of cylinders will be activated to run a wasted spark ignition coil. This is a very popular choice on smaller engines.

Wasted spark coil per cylinder
Coil outputs equal to the amount of cylinders, will be activated to COP coil per cylinder. They are fired in wasted spark sequence.

Full Sequential coil per cylinder
Coil outputs equal to the amount of cylinders will be activated to coil per cylinder. They are fired in full sequential mode. This requires a home pulse from a cam signal. This is the preferred method for NOZ systems that has fuel in the intake manifold.

Full Sequential Spark
This feature can do full sequential spark on the gear type triggers. Note that there is a driver for each coil. Should you select wasted spark COP, then the coils are still wired one coil per driver and not externally paired like the Ver 3.5A firmware. With this selection, two pairs of drivers will be pulsed together. To sink the spark over the two revolutions, requires a setting of the Gear Teeth. This setting can now adjust twice as many teeth as the crank gear has. This will cover the 2 revolutions. So a 36-1 gear can be adjusted for 72 teeth. This will determine if it fires on compression or exhaust stroke. This is universal firmware and for some engines it may be on rev one, and other ones it may be on rev two after the cam pulse was read. It depends on where and how the cam teeth are situated.

Example:

If you use the 36-1 gear and your timing mark is on 14 then it could also be on 14+36=50. A simple way to test will be to select COP wasted spark.

Now crank and start the engine. You may need to advance the timing if it wants to backfire through the intake. Use gear teeth settings from 1 to 36. If it starts and idle, then calibrate timing with a timing light then save the map. Now select full sequential mode and save again.

Now start the engine. If it starts, then you have the sink pulse right. If not, add 36 to your current gear teeth value and save. Crank again and it should start now.

Note that this program needs to find the home signal first before it will start the engine. This will prevent backfire through the intake.

Note that full sequential and wasted spark systems has no performance difference as both types will have a full load on the coil so spark is the same energy. It is merely required for overlap cams and NOS systems Also make sure that firmware is available for your application.