I have managed to get the ESP8266 board into MODEM_SLEEP mode if I use Espressif’s RTOS SDK instead of esp-open-rtos. This is a shame because I liked the esp-open-rtos sdk build system, but I don’t have time to try to modify the SDK.
Using the Espressif SDK allows us to get the current consumption down to 25mA, which should give about 6 hours with the 150 mAh batteries I have in mind for the project – a bit too short still, so may need to use 2 bateries, or think of something else to make the board sleep more – but it is looking feasible which is promising.
See update here: http://www.openseizuredetector.org.uk/?p=975
We are making slow but steady progress with making a seizure detector that will run on low cost hardware. We have all the software components for a workable seizure detector and just need to learn how to switch off the wifi radio to save power. Then we need to re-commission the 3D printer so we can produce Laura’s case design to try it out. Details at Custom Hardware Seizure Detector.
I have just released a new Beta test release of OpenSeizureDetector on Google Play Store (V2.5.1).
The only change is an improvement to handling alarms from short duration seizures. If a seizure is only detected for a short period, the previous version may only give a single set of Alarm beeps, which may be insufficient to alert a carer.
With the new version, if you enable “Latch Alarms” in the Alarms settings then when an alarm initiates, the alarm beeps will sound for the period specified in the “Latch Alarm Timer Duration” setting, even if the alarm resets quicker.
You can stop the alarm to silence the beeps earlier by pressing the Accept Alarm button. This works both on the main OpenSeizureDetector app screen, and also if you are running it on another device using Network Datasource to provide alarm annunciation in a different part of the house.
This is as a result of the seizure Benjamin had last week, when we only got a single sent of alarm beeps. This is fine if you are awake and alert, but if you are asleep it may not be enough to rouse you. More details of this event on the Real Test of OpenSeizureDetector page. A further update will follow fairly soon with an improved algorithm to detect seizures with lower frequency movement.
I have just published an update to the Beta test version of OpenSeizureDetector (now V2.3.1). This fixes two issues reported by testers:
The detection was much more sensitive than previous version, so the default Alarm Ratio Threshold setting has been increased to 50 (we use 56 for Benjamin because he is quite bouncy), so you may need a higher value, but I don’t want to make it too insensitive.
The auto-start on boot feature now works with the phone screen locked.
This release will be available to anyone who has registered as a beta tester here in the next couple of hours.
A quick bug-fix beta release (Thank you Damian for reporting it!) – if you have an incompatible version of the watch app installed it will now pop up a friendly-ish message asking you to upgrade the watch app, rather than crashing with an obscure error.
Available on for beta testing here: https://play.google.com/apps/testing/uk.org.openseizuredetector
Please note that the OpenSeizureDetector set-up that I have for my son developed a problem today and the watch app stopped talking to the phone (so the phone just gives those annoying fault ‘pips’). I do not know what has caused the problem, but I suspect that it is to do with an update to the Pebble software.
Therefore I would recommend that if you are given the option to upgrade the Pebble Software you do not upgrade it for the time being, until I work out what is wrong with mine and confirm that the upgrade will be ok for you.
Note that I have another system that is using a Pebble Time rather than the older Pebble Classic – the Pebble Time one is working ok, but my two Pebble Classics are not.
I have just publshed a beta test release of OpenSeizureDetector V2.0.4. Changes are:
– Improved handling of watch app settings.
– Changed default AlarmFrequencyMin setting to improve detection reliability.
– Install watch app directly from phone rather than using pebble store.
– Main screen graph now a bar chart showing frequency
region of interest.
Opt-in to beta testing here, then it will install from Google Play Store.
As usual, any comments or feedback to email@example.com, or facebook please!
I have just bought an Angel Sensor M1 wristband to try it out as an alternative seizure detector to the Pebble.
The OpenSeizureDetector Android App is written to allow extra ‘data sources’ to be used, so I will have a go at writing a DataSorurce that uses the angel sensor instead of the pebble. The first effort will be to repeat the same functionality as you get with the Pebble, then extend it to use the other sensors such as skin conductivity and heart rate. This should reduce the number of false alarms compared to the Pebble…If I can make it work!
The Open Source Angel Sensor Android app installed ok and said it was scanning looking for the device.
The instructions (http://angelsensor.com/start) said press the button on the device to switch it on – it was hard to see the button – there is a hard plastic blister on the top, but it doesn’t move when you squeeze it. Started to think the device is dead…..
Tried plugging it into the charger – the LEDs in the device came on, which is a good sign, but nothing else.
Waited a while…..
Now squeezing the plastic blister on the device makes it vibrate a bit – I think long and short presses do different things….
After a few presses must have managed to switch it on and the phone app connected to it – phone app displaying temperature and has placeholders for other parameters such as steps and heart rate, but they are not displaying values…. Display says battery is