Camsync is necessary for

* 5cyl (where wasted spark is not a good solution)

* Also necessary for real sequential ignition (properly used COP).

Cam-sync has been used with coil-type (primary-)trigger (which means ncyl evenly spaced pulses per camrot) for a long time. However, many likes to use camsync with 60-2 crankwheel, which is now possible.

AdvancedIgnition will finally take over (development branch), that also supports odd-fire-6.

----

notes for users

Implemented with 60-2 since 1.0.25 (experimental! uploaded to firmware dir but not released yet! use at your own risk!)

* another_trigger_tooth=18 (decimal 24)

* tooth_wheel=3A (decimal 58)

* don't forget to read, understand and apply GenBoard/Manual/InputTriggerCamSync

----

developer notes

The trick is when the missing tooth is detected.

* if cam_sync3 bit was flagged, reset tooth_cnt=0 and act as TW_MISSING

* otherwise (camsync not flagged), tooth_cnt+=3 (instead of +=1 or resetting). This is necessary to make up for the 2 teeth at the 60-2

That way tooth_cnt count up to almost 120.

----

Design decisions

Might be done in

* multitooth.c : independent of the current, operational coil-type + camsync code. This was implemented. Unfortunately multitooth.c was involved a bit with camsync processing, but the code is not too tangled.

* or timing.c : possibly merged with the current, operational coil-type + camsync code

might be configured in

* maybe in tooth_wheel upper 2 bits (not optimal, if we want the 135-crankteeth later)

* or in a dedicated secondary_trigger bit