Hacking Your Mouse To Fix The Misclick Of Doom

Page 3 - Seeking answers? Join the Tom's Hardware community: where nearly two million members share solutions and discuss the latest tech.
Status
Not open for further replies.
Daniel, while your SPST debouncing algorithm works, it does add some latency.
I would poll the input and accept a state change immediately, and then ignore any changes for the next few cycles.
 

I already mentioned that below the flowchart: "Since there is no uncertainty surrounding a 'make' event, you can omit debouncing that transition to reduce input latency there and focus debouncing on the break event"
 
Even more robust: With a few more resistors and/or a capacitor, I can almost visualize a modification to the SR debounce circuit that might allow it to still work (with a small additional latency) if either the NO or the NC contacts failed (to close), but obviously not both (which should bias it to NO, if that double-fail occurred).

Might have to get out my old CSC Proto-Board...
 

By the time you manage to get that working, I suspect you will be looking at a double SPST analog debounce circuit that is still vulnerable to bounces or has an extremely long time constant relative to fresh switches' settling time.

Once an SPDT switch is worn to the point that it fails to make even momentary contact on position changes, I doubt its remaining working contact would be of much use either.

If you think you can get that to work despite not being very practical, kind of like my SPDT hack here, have fun trying!
 
Disabled ABP for site. FANTASTIC ARTICLE. This is the reason why my Logitech G100s failed. Lost respect for Logitech really.
First comment here 😛
 
Status
Not open for further replies.