Open Seizure Detector
PineTime Watch Support #70
Replies: 10 comments 12 replies
-
|
I know someone else (@MJones235) has also had a go at modifying the InfiniTime C++ operating system for PineTime to add OpenSeizureDetector support - again that will need testing to check the reliability. |
Beta Was this translation helpful? Give feedback.
-
|
I have just ordered myself a couple more PineTime watches so I can get back to working on this, because I think it is important to help make OpenSeizureDetector accessible to people on low incomes, because the Garmin watches are expensive. |
Beta Was this translation helpful? Give feedback.
-
|
@44616E said: "I like the look of a PineTime. There doesn't seem to be any dev kits available. I wouldn't mind have a crack at it. What path were you thinking of, did you plan to have an app to install on the watch or a dedicated firmware to make it a dedicated device. I would probablely be interested in the latter.I am concerned a little over long term hardware availability considering the delays in OS development." One advantage of doing our own simple firmware rather than linking too closely to infinitime would be that porting to different hardware would be easier maybe? Graham |
Beta Was this translation helpful? Give feedback.
-
|
We could also likely get better reliability and power consumption going low level. The problem is going to be with the HR sensor. |
Beta Was this translation helpful? Give feedback.
-
|
That is a good point - both the InfiniTime and WaspOS firmware have
implementations of a heart rate measurement algorithm, but I do not know
how good it is - the professional devices probably do some clever filtering
in software to get reliable readings - might need some more research to see
what is published on how best to do it.
I'd be quite interested to know how it is done, because I can tell if my
heart rhythm messes about when I am running, the indicated heart rate goes
up a lot - but I don't think that is real - more a measurement artefact.
…On Thu, 27 Jul 2023 at 12:00, 44616E ***@***.***> wrote:
We could also likely get better reliability and power consumption going
low level. The problem is going to be with the HR sensor.
—
Reply to this email directly, view it on GitHub
<#70 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AACLSYYVEGNZAC4WJDHMZKDXSJC5HANCNFSM6AAAAAATTELHO4>
.
You are receiving this because you authored the thread.Message ID:
<OpenSeizureDetector/Android_Pebble_SD/repo-discussions/70/comments/6564051
@github.com>
--
Graham Jones <http://google.com/+GrahamJones>
Hartlepool, UK.
|
Beta Was this translation helpful? Give feedback.
-
|
I have started working on PineTime again so I can compare the heart rate monitor raw data to the values I am seeing on BangleJS (I am not convinced that the BangleJS HRM is working very well). In which case my option is to write it in C/C++ like Infinitime. I shied away from the Infinitime approach last time I looked because it is written in 'modern' c++ and I was struggling to follow it (my comfort zone is old fashioned C). Will have to try to educate myself I think.... |
Beta Was this translation helpful? Give feedback.
-
|
I've just been reading through the Infinitime documentation about its BLE implementation. It looks as though the latest versions of Infinitime provide BLE services/characteristics for heart rate, battery and xyz acceleration. This should be enough to connect to OSD directly, if I add these services/characteristics into the Android App BLE data source. |
Beta Was this translation helpful? Give feedback.
-
|
I was looking through the Infinitime BLE Implementationdocumentation last night and noticed that the developers have already got it providing a heart rate and raw accelerometer data service. I'll update the V4.2.x branch of the main android app so it responds to the infinitime BLE services and see how it performs. |
Beta Was this translation helpful? Give feedback.
-
|
The Pinetime seems to be working pretty well now with the latest V4.2.x version of the OpenSeizureDetector android app, and the latest version of our custom PineTime Firmware, PineTimeSD. |
Beta Was this translation helpful? Give feedback.
-
|
I think that the major issue regarding receiving data too frequently has been resolved in V4.2.1l of the OpenSeizureDetector Android App |
Beta Was this translation helpful? Give feedback.
-
|
Comparison of Current (21 Jan 2024) version so of OpenSeizureDetector on PineTime and BangleJS, compared to Garmin devices.
Given the very promising results from PineTime (especially battery life and heart rate monitor performance) and the much lower cost than the other devices, I intend to concentrate on getting PineTime to being ready for release for general users. The first priority will be to sort out some simple installation instructions, then improve the user interface. |
Beta Was this translation helpful? Give feedback.
-
|
I have been doing some tests with older android devices to see if we can get the PineTime + Android device combination down to less than £100. I wonder if this might be to do with the bluetooth version on the different devices: Pinetime supports Bluetooth V5, whereas the Nokia 1 is Bluetooth V4.2, whereas the Samsung A20e is V5. So we might have to recommend that the Android device supports Bluetooth V5 for best performance? It seems that the most relevant difference between Bluetooth V4.2 and V5 is much longer range. Now the range of Bluetooth 4.2 should be fine for our application, but maybe it is just more susceptible to interference which is why my V5 device seems to be working better. I'll do another test on my Samsung device, just in case I damaged the antenna when I disassembled and reassembled my test pinetime watch. |
Beta Was this translation helpful? Give feedback.
-
|
The PineTime seems to work very well with the Samsung A20e. If you go out of bluetooth range and back it usually reconnects itself automatically. If you are out of range for a long time (>1 hour, but not sure how long it has to be), it may fail to reconnect automatically but shutting down and re-starting the OSD phone app gets it working ok. If you would like to try the PineTime, please see the installation instructions here: https://openseizuredetector.github.io/pages-user/pine-time-installation.html (and feed back any experiences and suggest improvements to the installation process or instructions!) |
Beta Was this translation helpful? Give feedback.
-
|
Hi! First up many thanks for all your hard work on this project! We have a son too with epilepsy and autism and it is so amazing to see a project like this. I'm hoping that I can at some point contribute too in some way. I got the PineTime watch working with OpenSeizureDetector with version 4.2.1, but it seems that the watch goes into a sleepmode or something and then stops communicating with the phone and then the app goes in to FAULT state. I'm wondering if there is some settings that I missed. The PineTime watch is running InifiTime version 1.13.0 and I did not change any settings on the watch itself. |
Beta Was this translation helpful? Give feedback.
-
|
Hi,
You need to run a custom version of infinitime that I have created to
address that issue and also make it sample the accelerometer readings fast
enough for the seizure detection algorithm.
Please see the installation instructions here:
https://openseizuredetector.github.io/pages-user/pine-time-installation.html
Let me know how you get on!
Thanks
Graham ***@***.***)
…On Sun, 3 Mar 2024, 10:54 Jeffry Sleddens, ***@***.***> wrote:
Hi! First up many thanks for all your hard work on this project! We have a
son too with epilepsy and autism and it is so amazing to see a project like
this. I'm hoping that I can at some point contribute too in some way.
I got the PineTime watch working with OpenSeizureDetector with version
4.2.1, but it seems that the watch goes into a sleepmode or something and
then stops communicating with the phone and then the app goes in to FAULT
state. I'm wondering if there is some settings that I missed. The PineTime
watch is running InifiTime version 1.13.0 and I did not change any settings
on the watch itself.
—
Reply to this email directly, view it on GitHub
<#70 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AACLSY2WJN53WZ7SFSPATFDYWL6PJAVCNFSM6AAAAAATTELHO6VHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4DMNJWG44DC>
.
You are receiving this because you authored the thread.Message ID:
<OpenSeizureDetector/Android_Pebble_SD/repo-discussions/70/comments/8656781
@github.com>
|
Beta Was this translation helpful? Give feedback.
-
|
Ah, I can't believe I missed that! The instructions on that page were super clear and I was able to install the OSD firmware onto the watch without any issues. It looks like it is all working perfectly now! Again, thank you very much! |
Beta Was this translation helpful? Give feedback.
-
|
Thanks, I am glad the instructions worked - I need to decide whether to put the effort into making the firmware update part of OSD rather than relying on Gadgetbridge. A few users have managed to do it ok using the GadgetBridge instructions, but I suspect they may be the sort of users who are happy to fiddle to get it to work, and others may not! |
Beta Was this translation helpful? Give feedback.
-
|
What a wonderfully well made guide for the PineTime! |
Beta Was this translation helpful? Give feedback.
-
|
About the PineTime. I got multiple faults where OSD Android reported the watch app as NOT running. At the same time it was still updating accelerometer data and heart rate (I observed it for a good solid 20-30 seconds) so PineTimeSD was clearly was running and sending data. I think I'll try 4.2.2, or perhaps build the latest 4.2.x branch to see if I get better results. (sorry about the giant screenshots)
|
Beta Was this translation helpful? Give feedback.
-
|
Thanks for reporting this @lundstrj. The time in the OSD app is 02:27:03, but the phone time is 02:29. The time in the app is the last time it received a 5 second data sample from the watch, so it looks like the communications did stall, so the FAULT condition is correct. I did wonder if you have got the system into the state where there are two versions of the OSD server running at once (when that is the case it alternates between OK and FAULT) - a force-stop of OSD or re-boot of the phone usually fixes that. The issue is related to stopping and starting the system - sometimes it does not shutdown properly. Do you think this is a possibility for your issue? |
Beta Was this translation helpful? Give feedback.
-
|
I mean, it is not impossible at all that it is how you suggest. I did find it odd that the displayed heart rate was updating and when I was gently shaking the watch the accelerometer graph shot up. It was like the system was in a weird state of limbo where data was flowing but OSD still warned me that the connection was broken. I haven't looked into what determines if the watch is connected or not. Is it at all possible for OSD to detect the watch as disconnected even though data is being received? |
Beta Was this translation helpful? Give feedback.
-
|
It does not really do watch connection checks - it is really a 'data received on time' check. I'll wear the watch tonight and watch more carefully what happens when I brush my teeth, which always sets it off. |
Beta Was this translation helpful? Give feedback.
-
Early in 2022 a user (@rennard) was working on making OSD run on the low cost PineTime watch using the MicroPython operating syststem.
This is really good because I want OpenSeizureDetector to work on very low cost hardware. I have not managed to get it working on my PineTime yet though - need some more time to work out what is wrong!
His version is here if anyone wants to try it: https://github.com/rennard/wasp-os-fork
Beta Was this translation helpful? Give feedback.
All reactions