These are chat archives for nightscout/intend-to-bolus
Hi everyone. I'm new here , I'm a 59 yo Australia T1 interested in setting up a closed loop system.
3 days ago I got a libre scanner and sensor and for the first time in 35 years I can see just how wonky my sugars really are :(
Some nights I hypo and some night hit 16 or higher. Its clearly unpredictable and impossible to set hard and fast basal rates which leads me to desiring a closed loop system.
So far I have the following
An older paradymn minimed 754 running 2.6A firmware (also a 10yo 522 as a backup)
Libra freestyle sensors and a scanner.
Blucon nightrider ffrom ambrosia.com (on order 2 weeks ago ... hopefully soon)
lots of Pi Zero W 's
huawei nexus 6p + xdrip on it.
an (empty at the moment) herokuapp nightscout deployment.
I'm also about to pre order the Pi explorer hat , which I believe will complete the hardware requirements for a closed loop setup.
The explorer hat should be shipping now or soon I believe.
So from my readings my current understanding is that :
blucon device talks to xdrip+ app on phone to send bg readings from libre sensor to nightscout herokuapp site.
pi zero W communicates with night scout to receive new bg readings in real time.
pi explorer hat radio communicates with minimed 754 pump to get insulin bolos basal etc data.
openaps sofware on pi works out temp basal and or bolus adjustments and controls the 754 for delivery via comms on the explorer hat.
Am I on the right track here ?
Anything missing from this setup ?
Any caveats to this, or perhaps a better way to go ?
I hope that I can get this all working with my older 754 2.6A (current pump is also 754 but unfortunately 3.1A) until such time as a closed loop capable pumps are available in australia.,
which may be a few years yet, We don't even have the 670g here yet , best I can do is the 640g at the moment :(
Thanks in advance for any comments and/or words of encouragement.
I would be particularly interested in comments from anyone using a minimed 754 2.6A in a closed loop (any issues with it ? are bolus and temp basal both possible on this pump ?)
I'm very excited by all this and , as retired tech head T1D rpi enthusiast, this is right up my alley.
I hope that once up and running I can contribute to future development somehow. These is sure to be something that I will want to get my programmers teeth into :)
* * * * * ps aux | grep -v grep | grep -q "oref0-online AA:AA:AA:AA:AA:AA BB:BB:BB:BB:BB:BB" || cd /root/myopenaps && oref0-online AA:AA:AA:AA:AA:AA BB:BB:BB:BB:BB:BB 2>&1 >> /var/log/openaps/network.logI set up everything initially using the MAC address AA:AA:AA:AA:AA:AA (where I ran the setup script using this BT address); this was working but after adding BB:BB:BB:BB:BB:BB with this syntax, it allows the rig to pair with the phone with MAC address BB:BB:BB:BB:BB:BB but it no longer pairs with phone AA:AA:AA:AA:AA:AA. Ideally I'd like it to first try to pair with AA:AA:AA:AA:AA:AA, and if that's not available to fall back on BB:BB:BB:BB:BB:BB. Any suggestions?
Hi, I'm running 0.6.0 and was just running my oref0-runagain.sh. Everything seems to move along fine until it tries to get latest oref0:
Finished processing dependencies for decocare==0.1.0-dev /root/src/oref0/ already exists; pulling latest error: object file .git/objects/1e/e1adc33a5334fc8e44d17e1d923281f854cfd0 is empty error: object file .git/objects/1e/e1adc33a5334fc8e44d17e1d923281f854cfd0 is empty fatal: loose object 1ee1adc33a5334fc8e44d17e1d923281f854cfd0 (stored in .git/objects/1e/e1adc33a5334fc8e44d17e1d923281f854cfd0) is corrupt Couldn't pull latest oref0
what do I need to do to clean this up?
cd ~/src && git clone git://github.com/openaps/oref0.git || (cd oref0 && git checkout master && git pull)