InputTrigger/NewSimpletrigger

More powerful simple trigger

In cases where the stock trigger arrangement can't be used for some reason there is a need for a simple to install triggersystem.

The 60-2 trigger wheels are very unsuitable for retrofitting as you basically need a machine shop to center the wheel careful enough. There are also an array of other problems involved in retrofitted multitooth triggerwheels. Things like badly designed wheels or sensors badly matched to the wheel has all caused large support loads.

I recommend simple trigger with one large tooth per ignition event and the use of the Honeywell 1GT101 Hall sensor for most applications where a retrofitted trigger arrangement is needed. The Honeywell sensor is self adjusting and forgiving, in reality it triggs reliably from two,three or four M8 screws installed in the balancer.

The problem is that this does not work on all engines. For example odd fire and I5 engines can't run on this as their trigg points is different depending on which turn the engine is in. As the Audi I5 engine has a trigger system that is very special and because the cars seem very individual we get problems with the Auditrigger in many cases and need a simple to fit trigger system.

As a temporary fix I want a way to just skip every other trigg comming in on the primary trigger input, I want it to read the first tooth after the secondary trigg, ignore the next, read the next, ignore the next and so on until it see the cam sync again and start over. I consider this to be a very important improvment and I would love it it got some priority as there is lots of people out there that has problems with auditrigger.

Suggestion for permanent solution:

There are basically two types of triggers we can see for an odd fire engine. The ones where we have evenly spaced teeth where only some are trigged from, for example 12 teeth evenly spaced around a wheel. These cause no problems.

Then we have the wheels where only the teeth actually trigged on are left. As these are not evenly spaced in an odd fire application I suspect that these can cause some problems as we have to tell the ECU which teeth to use for the rpm calculation. I can't come up with any engines where it is not enough to only do the rpm calculation on every other teeth, but being able to do the rpm calc every trigger tooth could make a difference on some engines and maybe I have missed engines which have a trigger pattern that repeat it self at an interval other then every two triggs.

The trigger wheel model would unfortunately have to be a 720deg represenation of the triggerwheel in some applications. For example if an odd fire distributor is used as a trigger source. But for all crank trigger applications we only need a 360 deg represeneation of the triggerwheeel as it repeat itself after that. The more bits we have in this mask the more advanced the triggerwheel can be. As an example 12 bits would be enough for a Chevy odd fire engine with a crank trigger and 8 bits would be enough for a Harley with a 2-tooth crank trigger.

As a complement to the above we need a skip mask which tell the ECU which triggers to ignore. This would have quite a few skips for the wheels with evenly spaced teeth but would basically skip every other trigg on the wheels where only the actual trigger teeth are found on the triggerwheel.