Hi In Desktop 2 v1.0.4, did you consider the debounce as keyboard buttons were pressed or released? How long is the debounce confirming time? Thanks.
Jeffery
Hi In Desktop 2 v1.0.4, did you consider the debounce as keyboard buttons were pressed or released? How long is the debounce confirming time? Thanks.
Jeffery
Hi Jeffery,
The default debounce (or polling rate as it's named in the keyboard) is 15 ms. It's setup with this define in m_keyboard.h: M_KEYBOARD_DEFAULT_POLLRATE
How this happens is that the keyboard uses the GPIOTE PORT event as a wakeup source. When the device is awake, it starts a timer, and when it times out, it scans the matrix.
When the button is released (see: matrix_scan_timeout_handler), the timer is stopped and a "release" command is sent. Then it's back to sleep.
Best regards Håkon
Hi Jeffery,
The default debounce (or polling rate as it's named in the keyboard) is 15 ms. It's setup with this define in m_keyboard.h: M_KEYBOARD_DEFAULT_POLLRATE
How this happens is that the keyboard uses the GPIOTE PORT event as a wakeup source. When the device is awake, it starts a timer, and when it times out, it scans the matrix.
When the button is released (see: matrix_scan_timeout_handler), the timer is stopped and a "release" command is sent. Then it's back to sleep.
Best regards Håkon