Subpage of Tools menu

• type is normally 1 letter (lower or upper case are inverse polarity) and 3 digits (interpreted as 3 digits or 2+1)
• c004: coiltype with 4 cyl
• c008: coiltype with 8 cyl
• c270: auditrigger (1 sectrig pulse for every 270 primtrig pulse)
• c...: 3 digits (number of primtrig pulses between 2 following sectrig pulses)
• m582: missingtooth 60-2 (58 tooth and 2 missing)
• m351: missingtooth 36-1 (35 tooth and 1 missing)
• m231: missingtooth 24-1 (23 tooth and 1 missing)
• m071: missingtooth 8-1 (7 tooth and 1 missing)
• m031: missingtooth 4-1 (3 tooth and 1 missing)
• m(2 digits for number of teeth)(1 digit for nr of mission teeth)
• g582: (or g...) similar to m... but double-pulse camsync (magneti-marelli)
• f000: fiatstilo
• e324: Lotus Elise (Rover-K type 36-1-1-1-1 pattern)
• s060: Subaru EJ series (6+7 type)
• s362: Subaru and Suzuki 36-2-2-2 type
• l008: Lancia/Cosworth 4 crank + 2 cam
• z000: (or z122 or number does not matter?) maserati odd-fire V6 ...30,90,30,90... type trigger with double sectrig pulse
• h000: (or h121 or number does not matter?) Honda extrapulse trigger.
• NOTE: there might be more types, if you get hint from wiki page or your expert, use that

Note: capital-letter means reverse polarity (eg. "M582"); might be necessary depending on soundcard.

• Enable primary trigger, secondary trigger (and possibly third trigger in Motorsport / Camshaft angle control) if necessary
• burn and reboot
• In "Play trigger" dialog, set the trigger type (see list above)
• Start "Play"
• Verify that the controller sees the expected pattern. See Analyze/record trigger log. Even if the controller is misconfigured (or configured for different pattern), the input trigger pulses should show up for all the enabled trigger inputs, but than spark event might appear at bad position or not appear at all (naturally, ignition transformers should not be connected at this stage or fuses removed !)
• If the controller is configured for the correct trigger pattern (configlets in primary trigger dialog might help a lot), check that RPM is measured correctly, if there are trigger-errors and see triggerlog again for spark-event positions.