For example such a tach is adjusted to read for " one spark per revolution " .
Meaning that the MCU will assign
a full crankshaft revolution for every high voltage pulse that is triggering the sensor.
All good ,till the rev limiter of the coil hits ! Then our "limited coil approved " tach sensors the wide discrepancy between the measured sparks -since the rev limited coil now is powering the spark plug EVERY OTHER REVOLUTION -and automatically
readjusts the way it calculates rpms from pulses/sec ,thus the steady output mwadurement on the screen .It's an extra programming sub-routine issue and does not have anything to do with the refresh rate of one or half a sec ( which is rather slow to be used for measuring every other rev at say 14,000 rpm ...) .