Interesting. So now that I know that it's using the accelerometer, I've gotten some more data. I had noticed some strange stuff when messing with the "tap" event a while back, and I just tested it a little more.
Setting HRM: always
Then in the console:
>Bangle.on('tap', (data) => {console.log(Date().getSeconds()+" "+data.dir);})
=undefined
3 top
4 right
5 right
6 back
8 right
8 front
8 top
10 bottom
11 front
12 bottom
13 top
15 left
16 right
17 right
18 top
It throws events all over, sometimes multiple times per second. The HRM seems to stop if I take the watch off and lay it on my desk, so I have it on my wrist but I'm holding extremely still.
As soon as the HRM is off, the onTap seems to work perfectly fine. It registers directions just fine, and only when I tap it deliberately.
I loaded up accelgraph while the HRM was off/on, but there didn't seem to be any difference that I could tell.
Espruino is a JavaScript interpreter for low-power Microcontrollers. This site is both a support community for Espruino and a place to share what you are working on.
Interesting. So now that I know that it's using the accelerometer, I've gotten some more data. I had noticed some strange stuff when messing with the "tap" event a while back, and I just tested it a little more.
Setting HRM: always
Then in the console:
It throws events all over, sometimes multiple times per second. The HRM seems to stop if I take the watch off and lay it on my desk, so I have it on my wrist but I'm holding extremely still.
As soon as the HRM is off, the onTap seems to work perfectly fine. It registers directions just fine, and only when I tap it deliberately.
I loaded up accelgraph while the HRM was off/on, but there didn't seem to be any difference that I could tell.