Search results for:

The event recorder takes every event it gets and write one line in the .csv for it. I tried writing to a local file, but 1 minute of recording was about 200k, so tethering to the browser on PC/Phone is probably better. The code is still in there to write into a file, you could try it out by changing line 18 in custom.html to var method=2;.

HRV is calculated from RR intervals, so it should work. The BTHRV app waits for the first RR interval to be received and then buzzes ands starts keeping measurements in memory. For my belt (Wahoo TICKR X2) it takes 10-15s before anything happens, the first RR intervals get send a decent bit after the first pulse measurements. Currently the data is only written at once when the 300s measurement is complete. Maybe not a bad idea to write as the data becomes available. If you see RR values in BTHRM app, it should definitely work.

As for the behaviour with the different settings: It got a bit complex now :) I think about defining modes that encapsulate all settings in fitting combinations.

HRV app uses BT event and should work with every setting combination as long Use BT HRM is on. BTHRM app shows internal and external sensor when Replace HRM is off. If it is on, then both event types (HRM and BTHRM) normally contain the same data (both from BT sensor). Fallback to HRM decides if with the internal sensor will be enabled on disconnect. In that case, the values of HRM and BTHRM can differ, BTHRM will not be shown on disconnect, HRM enabled, then after some time BTHRM will reconnect and reappear again. Internal sensor and BT values can then mix for the Fallback timeout time as both events are emitted as HRM events.

Attribution is not that wrong, Gordon created the intial version of this app. I think he will merge on Monday, so some time left for testing and improving the pull request ;)

Bug is found and pull request is open ;)

You can try here: https://halemmerich.github.io/BangleApps­/#bthrm

After a longer walk today, the counters on both my bangles are nearly perfectly in sync, 6165 (b77) vs. 6154 (b87).

Running jeffmers harness with threshold 15 results in 6145 (b77) and 6159 (b87).

X_STEPS = 6, RAW_THRESHOLD = 7
File, Expected, Simulated, Diff, %, (Original)
HughB-walk-a10021-b10248.csv, 10021, 12672, 2651, 126.45 %, (12222)

So that creates too many step counts with this low threshold.
I will try to get a longer dataset. Is there a possibility that one threshold will not cut it for all the bangles because of sensor/electronics variation?

I have had both bangles on 2v11.53 for a few hours now (mostly sitting at desk) and the step counters are still different.
b77 has counted 167 steps, while b87 counted 667. So a bit closer together than before.

jeffmers test harness and stepcount.c yielded:

X_STEPS = 6, RAW_THRESHOLD = 15
File, Expected, Simulated, Diff, %, (Original)
halemmerich-walking-2-b77-2v11.csv, 150, 79, -71, 52.67 %, (156)
halemmerich-walking-2-b87-2v11.csv, 150, 89, -61, 59.33 %, (151)
halemmerich-stationary-1-b77-2v11.csv, 0, 0, 0, 0.00 %, (1)
halemmerich-stationary-1-b87-2v11.csv, 0, 0, 0, 0.00 %, (10)

I have had play with the RAW_THRESHOLD and got down to 7 before the results were reasonable.

X_STEPS = 6, RAW_THRESHOLD = 7
File, Expected, Simulated, Diff, %, (Original)
halemmerich-walking-2-b77-2v11.csv, 150, 150, 0, 100.00 %, (156)
halemmerich-walking-2-b87-2v11.csv, 150, 143, -7, 95.33 %, (151)
halemmerich-stationary-1-b77-2v11.csv, 0, 0, 0, 0.00 %, (1)
halemmerich-stationary-1-b87-2v11.csv, 0, 12, 12, 0.00 %, (10)

I also tried walking 150 steps. b77 counted 80 steps and b87 counted 103.

Two bangles, both on 2v11, so I assume old threshold.
Will try the same with 2v11.53 on both this evening and run jeffmers harness. Branch to use is master?

b77 was a lot better than b87, especially while both were stationary. b87 was extremely noisy between 80-180ms, 200-280ms, 450-510ms. I do not know why.

Two Bangle.js 2, 77 and 87 are part of the MAC. If I watch the b77 while walking, close to every step gets counted.

Today I have tried wearing both my bangles (2v11) on the same arm to compare the step counters. The results were as follows:
2h sitting at my desk: 0(b77) vs. 866(b87)
Lunch and rest of day sitting at my desk: 621(b77) vs. 5221(b87)

b77 seems reasonable, albeit probably some percentage points on the low side.

Surprised by the massive difference I have recorded some accelerometer data and run it through the test program:

X_STEPS = 6, RAW_THRESHOLD = 17
File, Expected, Simulated, Diff, %, (Original)
halemmerich-walking-2-b77.csv, 150, 77, -73, 51.33 %, (156)
halemmerich-walking-2-b87.csv, 150, 78, -72, 52.00 %, (151)
halemmerich-stationary-1-b77.csv, 0, 0, 0, 0.00 %, (1)
halemmerich-stationary-1-b87.csv, 0, 7, 7, 0.00 %, (10)

I have walked a counted 150 steps for the first files. The plots while walking seem ok, but the stationary b87 has a lot of "movement" for being very still and having both watches on the same arm.

I don't know if it is related, but the internal HRM also seems to be a lot better on b77 than on b87. I have not recorded data for this, but during testing the difference was often > 20bpm. Maybe some hardware issue interfering with both sensors (missing filter cap, bad solder joint somewhere)?

Can I collect some other or additional data?

https://github.com/halemmerich/
https://codeberg.org/halemmerich/