History of GenBoard/Manual/InputTriggerCamSync
Older Newer
2007-08-06 16:35:53 . . . . MembersPage/MarcellGal [note about simpler condition in 1.1.x]
2007-06-26 09:18:44 . . . . MembersPage/TonciLoncar [request for explanation on sequential ignition]
2007-05-30 00:22:10 . . . . 89-172-125-206.adsl.net.t-com.hr [5 cylinder 'wasted spark']
2006-05-30 19:54:49 . . . . MembersPage/MarcellGal [note on other 2 types of camsync]
2005-10-16 08:00:56 . . . . MembersPage/MarcellGal [minor corrections: the condition was not true; since firing order starting cyl i]
2005-10-15 22:38:15 . . . . MembersPage/MattiasSandgren [Added example of cam pulse timing]
2005-09-26 20:45:49 . . . . MembersPage/MarcellGal [notes about twidth1.. twidth2...]
2005-07-20 07:31:42 . . . . MembersPage/MarcellGal [note about the camsync implementation]
2005-03-27 18:26:05 . . . . MembersPage/MarcellGal [corrected errors]
2005-03-27 04:00:53 . . . . modemcable176.254-81-70.mc.videotron.ca
2004-11-05 02:40:01 . . . . MembersPage/MarcellGal [answered cam-only question]


Changes by last author:

Changed:
The camsync-active-edge must be between given 2 cyls' spark event! In other words, if the camsync pulse overlapd the used ignition advance range of a cylinder (sometimes spark comes before, sometimes after the camsync-active-edge), it's currently not supported. For a 4 cyl, this means that if ignition advance is set to 8..45 degree BTDC, than the chosen camsync trigger pulse (the edge that is configured to trigger the processor) must be outside of that 37 crankdegree window (out of 180 crankdegrees) plus some safety margin.
In 1.0.x firmware the camsync-active-edge must be between given 2 cyls' spark event! In other words, if the camsync pulse overlapd the used ignition advance range of a cylinder (sometimes spark comes before, sometimes after the camsync-active-edge), it's currently not supported. For a 4 cyl, this means that if ignition advance is set to 8..45 degree BTDC, than the chosen camsync trigger pulse (the edge that is configured to trigger the processor) must be outside of that 37 crankdegree window (out of 180 crankdegrees) plus some safety margin.
Changed:
This is not a hardware limitation, just a firmware shortcoming, that's planned to be improved anyway (just noone asked for it yet).

The exact reason is the simplified operation:

This is not a hardware limitation, just a firmware shortcoming, not required in 1.1.x firmware.

The exact reason is the simplified operation in 1.0.x:

Added:

Even in 1.1.x, you want to make sure that the

* secondary trigger (chosen edge) does not race with the tooth after the missing tooth (in case of missing tooth)

* secondary trigger (chosen edge) does not race with any tooth (in case of "coil-type" trigger)