Question Regarding Keyboard Debounce
Posted: 06 Jun 2015, 20:54
Does debounce delay the initial key press i.e.: [Button pressed]--[<5MS Debounce]--[Signal Proccessed]?
Who you gonna call? The Blur Busters! For Everything Better Than 60Hz™
https://forums.blurbusters.com/
It shouldn't, but in many cases it does. It's also often over 5ms. It's kind of a crapshoot, mainly because it's not something the normal reviewers test for.Ghilbi wrote:Does debounce delay the initial key press i.e.: [Button pressed]--[<5MS Debounce]--[Signal Proccessed]?
What did steelseries say about the apex model? I'd like to compare it to the WASD V1 and a cheapo rubber dome keyboard measured here: http://forums.blurbusters.com/viewtopic ... =10#p13473. As for actuation force and key travel, I assume lighter and shorter is going to be faster, but eventually you'll hit a tradeoff of hitting keys accidentally.Ghilbi wrote:I see. I'm considering making a chart including all the possible factors outside of the users reaction time that will show input delay for various keyboard models and was curious. My plan right now is to contact manufacturers for the information, I'll include asking them to investigate if the debounce time is before or after. I 've inquired about two already and received some usable numbers from Steelseries about their Apex model.
I still need some pieces for the whole picture to come together, immediately two questions come to mind I'm not knowledgeable in: if all else is the same, would there be any difference between a key requiring 60g of actuation force and one of 30g? Would muscle memory slim the differences even further? Is there a formula that could approximate a plausible difference?
Lastly, what's the formula to compare different actuation distances?
As for measuring differing actuation force what do you think of this quote from an ocn user:Apex:
scan time 200 us
3mm throw
4ms debounce (not 100% sure that one is accurate)
(60g vs 30g)
given constant acceleration and distance, time can be calculated as t = sqrt(2 * d / a).
In this case:
td = sqrt(2 * .002m / (30 * 9.81 ms-2)) - sqrt(2 * .002m / (60 * 9.81 ms-2)) = 1.08 ms
I think somebody pulled those acceleration figures out of thin air. Ideally you'd measure that with a high speed camera, and keyboards with various actuation forces and travel distance. I can press a single key about 10 times per second(Cherry MX brown). 2mm actuation point is about half the travel distance, so assuming the downstroke is half the cycle time, the first half of the downstroke would be about 25ms. A single press might be different, but it certainly isn't 23x faster.Ghilbi wrote:As for measuring differing actuation force what do you think of this quote from an ocn user:Apex:
scan time 200 us
3mm throw
4ms debounce (not 100% sure that one is accurate)(60g vs 30g)
given constant acceleration and distance, time can be calculated as t = sqrt(2 * d / a).
In this case:
td = sqrt(2 * .002m / (30 * 9.81 ms-2)) - sqrt(2 * .002m / (60 * 9.81 ms-2)) = 1.08 ms

this estimate is good enoughSparky wrote: I think somebody pulled those acceleration figures out of thin air. Ideally you'd measure that with a high speed camera, and keyboards with various actuation forces and travel distance. I can press a single key about 10 times per second(Cherry MX brown). 2mm actuation point is about half the travel distance, so assuming the downstroke is half the cycle time, the first half of the downstroke would be about 25ms. A single press might be different, but it certainly isn't 23x faster.