18 s
keys: R replay · Space pause · H record mode · arrows step · URL: ?rec&dur=18&paused&loop

The deadzone and the actuation point stack.

Two runs in EPOMAKER Driver's key test screen · 2026-09-07 · travel drawn to scale, 3.4 mm total
Actuation set
0.5mm
measured from where the deadzone ends
Fired at
–mm
where the key test registered it
One key, pressed slowlyschematic press, real numbers
The rulethey add
Run 1deadzone +0.5actuation =–mm
expected0.5or1.0· neither fired
Run 2deadzone +0.5actuation =–mm
The deadzone is measured from the top. Your actuation point is measured from wherever the deadzone ends. The depth you press to is always the two added together.
So the published range has strings attached. 0.1 mm at the top needs the top deadzone at zero. 3.3 mm at the bottom needs the bottom deadzone at zero, and the app warns you off that setting.
TO REACH 0.1 mm: TOP DEADZONE 0 TO REACH 3.3 mm: BOTTOM DEADZONE 0 · THE APP WARNS AGAINST IT
Run 1: actuation 0.5 mm, top deadzone 1.0 mm, registered at 1.5 mm. Run 2: 0.5 and 0.5, registered at 1.0 mm. Read in EPOMAKER Driver's key test screen, which reports the depth at which a press registers.
Deadzones exist because a magnetic sensor is least trustworthy at the ends of its travel; the finding is that they qualify the actuation point rather than sitting alongside it · CK Tech Check