* This is my preliminary design to convert the 18-0 to 18-1 for the crank trigger.

** I missed that you use HALL (and the shatter-wheel drawing below), and assumed VR: asked to detail how you plan to do the mechanical conversion, simply grinding a tooth (fully) gives bad waveform. You only want to grind off 30..40% of the tooth, and fill in at the sides. Than record waveform with soundcard or scope to see the waveform, particularly tooth amplitudes.

** are you about to do the trick in the electronic domain with gates ?

** it seems to me that the 1 campulse (rising edge) + 18 crankpulse (rising edge seems better), (no missing tooth, and 3 crankpulses not used) should work perfectly with InputTrigger/AudiTrigger config

*** HW set up for HALL primary and HALL secondary to match your sensors, but no other HW or firmware mod.

*** tooth_wheel=87 # decimal 135 : needed to enable the auditrigger code, otherwise not used

*** another_trigger_tooth=06 # 36 tooth per camrot, so one event every 6th tooth

*** trigger_tooth=00 # I reviewed auditrigger code and it seems to support trigger_tooth=00 (just make no sense for the audi trigger system, but good for this). Apparently this means ign_tdcdelay= 75 degrees in this case. (better than 45 which is a bit too low -> limits ignadv to max 44 degrees)

* I also decided to drop the rapid start feature (3 different width cam-pulses) for the time being.

** thinking: maybe 3 crankpulses would work with the fiatstilo bit enabled for camsync ? no, not in original form

* Is the factory position of the CAM trigger shown below acceptable to current firmware?

** cam falling edge is appr 25 ATDC, so kindof acceptable (outside the 50 BTDC .. 20ATDC window that is useful for spark; 30 ATDC might be useful for aggresive ALS)

** cam rising edge appr 55ATDC=65BTDC, so perfect for camsync

** it should be only one pulse per cam, otherwise firmware mod is needed

** some table-testing (stim from PC soundcard, and display with a few LEDs) is recommended. If the crankwheel is fine, it shouldn't be too problematic to get this working. Just keep documenting your plans / efforts/ measurements (with used firmware,config,connections,etc...) and we'll help so it'll work out.