-
-
I love it. Not 100% sure about going back. I think more aesthetically than practically.
The numbers work as I personally expected - I had been wondering about modifying the alarms app to be like that because I find it fiddly at the moment, but if you're changing the menu system like this then it is covered!
The only thing I miss from the current menu system is the tap anywhere to activate the highlighted item. I am clumsy with touchscreens and it is a feature I really appreciate. Only thing as previously mentioned is that I currently find the scroll direction backwards.
Oh, I agree with @rigrig that a boolean should be a checkbox, the radio confused me.
But I would keep the multiple choice as is.edit: looked again and on second thoughts, completely agree with @rigrig on that -
-
@Mi I just haven't had the energy. I'll get to it.
Python is my first choice for trying things out. For step counter experiments I used Python and then translated the best option into C, but it would be awesome if we could be language agnostic for testing algorithms - that way people can contribute whatever language they prefer and the algorithm can be translated to C afterwards.
-
I've used it on my phone, it works, but I then failed to get jupyter or similar running on my phone to look at it properly.
Exactly as @Mi said: for evaluation recorder files plus similar from another device, for development the raw signal (ideally and accelerometer) are needed.
@Mi I have bought a pulse oximeter for immediate personal needs but will be useful when we work on the SPO2 functionality.
-
-
So reporting approx half the actual rate @HughB? Half the actual rate is actually better than I expected for while running (although looking back you said all over the place), and is what I am still sometimes seeing when absolutely still.
Seems to happen when the heart goes over a certain rate, because I was consistently getting readings in the 40s when my heart was going over 90bpm but I get an accurate reading when it is in the 70s. -
Regarding the gauge question, somewhere in a thread I posted code for drawing a ring. It used the Andres circle algorithm. I have some variations for drawing partial circles (for a gauge) on my computer. It worked wonderfully in the emulator but when I got my hands on the real thing it was too slow, so it is on my to do list to redo in C. I notice that there is already code in Espruino to draw a thick ring (filled annulus) but doesn't seem to be exposed in JavaScript, so that could be a starting point for a different approach, but in current form doesn't deal with the "partial" bit.
-
Guesstimate might be a little bit on the pessimistic side, but certainly there is work to put in both for implementation and validation. I think I remember there is a constant in the calculation that is specific to the PPG device involved, so we will probably need to experiment to determine this, and it may not be the same for the two versions of the HRM.
-
Yes. There is a thread open about what we can get from the PPG sensor (heart rate sensor). I know there are already comments in the firmware regarding SPO2 so Gordon might have made a start, but essentially my understanding is SPO2 is calculated using ratios of the AC and DC components of the PPG signal.
-
Yes, sorry, when we get there we can discuss in the PPG thread.
On topic for this thread, I just realised I didn't get an email notification when the new bangles came in (I had put my email in to be notified). Maybe you haven't sent them yet as you have enough to deal with from people seeing the forum, but if you have, it might be worth double checking they've gone.
-
@radswid it could work, but as you say it only works if the phone is present and connected. If you've always got a phone in your pocket, you could argue that you might as well just use that for step counting (in all but the biggest pockets fewer degrees of freedom and they pretty much all have an accelerometer). Personally my Bangle and phone are not connected unless I am uploading an app, and one of my reasons for getting a watch was to not need my phone to track run distance.
-
What we need ideally is the raw hrm signal, the accelerometer, and the values from your other hrm. I don't think we have the means to get all of this yet. I'd hold off doing any recordings at the moment. What do you say @Mi?
-
I would say wear it as you usually do, unless you usually wear it very loose so that it slides around your wrist. I know that for some (probably cheaper) watches people do say they need to wear them very tight, but that isn't what we should be aiming for I don't think.
I will let someone who has more experience with the actual monitors answer about the format, but I suspect CSV is going to be fine.
Information that will be helpful: which Bangle (the hardware in the kickstarter and non-kickstarter bangle 2 is slightly different), which reference device. What activity and terrain etc. might be useful but not as useful as the reference data itself.
-
-
-
-
Excellent. Thanks. That was (besides price) one of the things giving me qualms.
I'll think about it further before getting one, maybe there are enough people who can provide data already and the last 2 weeks I have been too busy with work (and now being ill) to spend the time I want with the Bangle. Hopefully that is going to improve soon. -
Article I linked from other thread: https://asp-eurasipjournals.springeropen.com/articles/10.1186/s13634-020-00714-2
Here is another good overview article: https://www.ncbi.nlm.nih.gov/pmc/articles/PMC6426305/
-
@Mi (trying to keep the HRM chat in one place, although follows on from the run app thread): is it easy to extract data from the H10? Would I be able to use it to record data and then extract it to a Linux computer easily enough, or do I need to connect it to something to live transfer it?
-
Oh I hadn't seen that. @halemmerich seems like you should be in this thread.
-
-
-
I am definitely on 2v12. I can't say for certain that my issue is the same as @dukky described though, I haven't checked. It could just be that my barometer is returning a value out of the range for the app.