You are reading a single comment by @Graham_Jones and its replies.
Click here to read the full conversation.
-
But something is also wrong with it :D, like it gets stuck often. Or wanders into weird hrm territory for no reason.
I found that I was getting occasional I2C errors when reading registers from the HRM device. In the end I caught these errors and re-set the HRM device when it occurred - that seems to have stopped my problem with logging freezing (https://github.com/OpenSeizureDetector/BangleSD/blob/master/apps/hrmtest/app.js#L240)
Graham_Jones
I have just tested a garmin heartrate strap compared to the Heart Rate Monitor app of Bangle2. The readings are Way off, so far that the strap was reading 120 and the app 60. This was whilst being on a gym bike. So I don't know what to call the current HR reliability, its almost non-existent I would imagine.
It has also shown 120, whilst the strap shows 80. Considering the watch is fed accel data, would the faulty readings(spikes noticed with onTap) affect it?
Part of the reason the first test was super bad for me was because riding a stationary gym bike doesnt' trigger accel changes, so automatic sportsMode didnt' kick in. After using
Bangle.setOptions({hrmSportMode: 1}), it improved, but sometimes in a bad way, like above.I will try hrmSportMode 2, for bike. Ok results: I was actually surprised how
wellit keeps up with the hrm in sportsMode 2, seriously. It seems to struggle going above 100, if eg. the strap says 130, it can remain at 100.But its accuracy within 70-100 is really
good. So its doing something right!But something is also wrong with it :D, like it gets stuck often. Or wanders into weird hrm territory for no reason.
Btw its fair to assume hrmSportMode 1==2, as gordon pointed out previously, haven't noticed a difference between the two yet.