View Single Post
Old 03-28-2012, 04:39 AM   #22
teasonc
Member
teasonc knows what time it isteasonc knows what time it isteasonc knows what time it isteasonc knows what time it isteasonc knows what time it isteasonc knows what time it isteasonc knows what time it isteasonc knows what time it isteasonc knows what time it isteasonc knows what time it isteasonc knows what time it is
 
teasonc's Avatar
 
Posts: 24
Karma: 2082
Join Date: Feb 2011
Device: Kindle DXG, Kindle Keyboard 3G
If a device like this goes asynch, that's usually a sign it's overloaded (it is being asked to do too much in too short an interval).

Sounds like a symptom of underdesign -- the cheap one sounds more peppy, which makes sense from an IRQ perspective (it just reads the button, which is probably done through i2c).

The KKSO3G is definitely a lot less asynch than DXG is; DXG routinely buffers keystrokes, whereas KKSO3G seems to have plenty of spare overhead to appear to be instantly responsive (and better debouncing so it doesn't grab extra strokes).
teasonc is offline   Reply With Quote