You are reading a single comment by @Gordon and its replies. Click here to read the full conversation.
  • Yes, right now this is to be expected. Pretty much all wrist-mounted heart-rate monitors tend to have trouble when you move your arm around but generally they use the accelerometer data so they can filter out false positives and still get some useful information out.

    Espruino doesn't do this at the moment since it's trying not to use proprietary algorithms. However hopefully the current algorithm will get improved at some point.

  • I think I am just completely missing this but where is the heart rate data actually getting called from? I am looking at heart/app.js and I am not seeing the call to either subscribe to the event or get the data. Everything I am seeing looks more like logging data and drawing the graphs.

    I'd like to help try to improve this if I can. I am mostly self-taught so I just need a bit of direction if possible. Thank you.

  • retty much all wrist-mounted heart-rate monitors tend to have trouble when you move your arm around but generally they use the accelerometer data so they can filter out false positives and still get some useful information out.

    Recently I found interesting paper with some 'heavy handed' approach to this problem:
    Motion Artifact Reduction in Wearable Photoplethysmography Based on Multi-Channel Sensors with Multiple Wavelengths
    https://www.researchgate.net/figure/Syst­em-diagram-of-the-wearable-multi-channel­-PPG-acquisition-system-including-PC_fig­2_339798967
    they use four typical sensors with multiple wavelengths plus accelerometer and try to do some motion compensation with that. Full download of the paper is available so lot of interesting info related to this problem there. See also citations below for more related papers.

About

Avatar for Gordon @Gordon started