At least in the source code version I have, it is defined as 200 system
ticks - which, going by the comments in the code, should be about 20ms.
That shouldn't create a problem in and of itself.
--
Rune / 5Q5R
toggle quoted message
Show quoted text
On Mon, 9 Sep 2019 at 13:30, Larry Rothman <ac293@...> wrote:
Rob,
I just had a look at the code - debounce is defined as 200mS which I think
is the culprit.
I think if someone could build the F/W with a debounce of 100mS (or
75mS?), that would solve the problem.
Regards,
Larry
