@live4sw that, or enter carbs via ifttt to NS
@popcornpam_twitter remember maxiob is a total unit amount, not rate per hour. If you're wanting OpenAPS to do more and it's being limited by maxiob, you can consider increasing that.
I don't totally understand what it is using for that calculation, because if I have a bolus of 3 units, isn't that already past my maxiob of .9? Cause it will still temp rate me over 1 unit
Remainingcarbscap should be either 0, or a number like 60 or 90, not a decimal. Remaininfcarbsfraction is a decimal. I'd leave that at the default 0.7 since you're dealing with other issues
Maxiob is max units of net insulin OpenAPS can give you. Not a rate.
ohh.. so maybe that is whats messing me up? So if my highest carb snack (higher carbs in snacks then meals for me) is 50 or 60 on a high carb day, maybe it should be 50?
Maxiob says "how much extra insulin do I want to allow OpenAPS to give me". 1u is fairly small, so it'll only give you 1u additional. If you're riding at 250, that may not do much.
I would set remaining carbs fraction and cap back to defaults
I would also re-read this page and make sure you understand a variable before changing it
@PopcornPam_twitter If you want input on it, I would post your full preferences file here as @Kdisimone suggested so we're not playing telephone on exactly what it contains.
Defaults + changing your maxiob would be best bet to start.
ok, ill start there
@danamlewis, you bet!
So I am trying to set it up and have the watch connected to Edison successfully...but issuing a notify command gets me a timeout ala:
root@obi:~/explorer-aps# openaps use pebble notify "hello" "testing"
Traceback (most recent call last):
File "/usr/local/bin/openaps-use", line 6, in <module>
exec(compile(open(__file__).read(), __file__, 'exec'))
File "/root/src/openaps/bin/openaps-use", line 63, in <module>
app( )
File "/root/src/openaps/openaps/cli/__init__.py", line 51, in __call__
self.run(self.args)
File "/root/src/openaps/bin/openaps-use", line 57, in run
output = app(args, self)
File "/root/src/openaps/openaps/uses/__init__.py", line 92, in __call__
return self.method.selected(args)(args, app)
File "/root/src/openaps/openaps/uses/__init__.py", line 31, in __call__
return self.method(args, app)
File "/root/src/openaps/openaps/uses/use.py", line 45, in __call__
output = self.main(args, app)
File "/root/.local/lib/python2.7/site-packages/pancreabble/pebble.py", line 28, in main
pebble.run_async()
File "/usr/local/lib/python2.7/dist-packages/libpebble2/communication/__init__.py", line 103, in run_async
self.fetch_watch_info()
File "/usr/local/lib/python2.7/dist-packages/libpebble2/communication/__init__.py", line 324, in fetch_watch_info
self._watch_info = self.send_and_read(WatchVersion(data=WatchVersionRequest()), WatchVersion).data
File "/usr/local/lib/python2.7/dist-packages/libpebble2/communication/__init__.py", line 286, in send_and_read
return queue.get(timeout=timeout)
File "/usr/local/lib/python2.7/dist-packages/libpebble2/events/threaded.py", line 81, in get
raise TimeoutError()
libpebble2.exceptions.TimeoutErrorI'm going to reboot the edison and repair and see if that helps
And good to see the info about the urchin watchface in the new docs, I was going to suss that out...
279 grams of carb today and 108 average with 0% highs and 1% lows. Oref1. That greatly exceeds my expectations as to the max amount of carb one can eat and get good results. I was thinking it would have to be about 90 grams of carb a day to do this.
i am facing a diffciltiy in pairing with Samsung S8, it connects for a sec and disconnects, out of many trys once i was able to connect for 5 mins
OK...need to update BT version on the edison looks likely...new docs already helping!
how can i know were is the openaps is taking the BG data from ?, i redid the setup for BT, but i see it is still getting the info, and have entered empty link for nightscout
@rsilvers129 awesome! :) what target range are you measuring against?
@scottleibrand My target is 90.
Every time I connect my pebble to the edison, forget the pebble and then rerun a scan, I get a new MAC address for my pebble...which seems VERY strange to me...I would think the MAC address should be fixed.
@rsilvers129 no, I mean what are your high and low thresholds for calculating 0% high and 1% low
60/180
k
@rsilvers129 if you target 100/120, what are those stats?
@applehat what do you mean by "target 100/120"?
I've never seen anyone use a range that small to calculate time-in-range numbers, so not sure if you're suggesting that or something else...
I meant to type 140 there
80/140
my brain farted when I said 100/120
80% in range.
Nice.
80% in range for 279carbs is something I could be OK with for days where i just cant eat low carb.
Tho I like that the top end was still 180 on yours. Thats better then 80% in range, but also it spiked to 300 once =P
@joannestevens,@PieterGit,@betluis,@scottleibrand
I'm at the same spot where you folks were with Pancreabble. I have a Pebble connected to an Edison and when I run:
root@obi:~/explorer-aps# openaps use pebble notify "please" "work"
usage: openaps-use pebble [-h] USAGE ...
openaps-use pebble: error: argument USAGE: invalid choice: 'notify' (choose from 'shell')
root@obi:~/explorer-aps# openaps use pebble -h
usage: openaps-use pebble [-h] USAGE ...
optional arguments:
-h, --help show this help message and exit
## Device pebble:
vendor openaps.vendors.process
process - a fake vendor to run arbitrary commands
USAGE Usage Details
shell run a process in a subshellSo I try docs of (note the pebble2 to avoid name collisions):
# in your openaps directory:
openaps vendor add pancreabble
openaps device add pebble2 pancreabble /dev/rfcomm0
root@obi:~/explorer-aps# openaps use pebble2 notify "hello" "testing"
Traceback (most recent call last):
File "/usr/local/bin/openaps-use", line 6, in <module>
exec(compile(open(__file__).read(), __file__, 'exec'))
File "/root/src/openaps/bin/openaps-use", line 63, in <module>
app( )
File "/root/src/openaps/openaps/cli/__init__.py", line 51, in __call__
self.run(self.args)
File "/root/src/openaps/bin/openaps-use", line 57, in run
output = app(args, self)
File "/root/src/openaps/openaps/uses/__init__.py", line 92, in __call__
return self.method.selected(args)(args, app)
File "/root/src/openaps/openaps/uses/__init__.py", line 31, in __call__
return self.method(args, app)
File "/root/src/openaps/openaps/uses/use.py", line 45, in __call__
output = self.main(args, app)
File "/root/.local/lib/python2.7/site-packages/pancreabble/pebble.py", line 28, in main
pebble.run_async()
File "/usr/local/lib/python2.7/dist-packages/libpebble2/communication/__init__.py", line 103, in run_async
self.fetch_watch_info()
File "/usr/local/lib/python2.7/dist-packages/libpebble2/communication/__init__.py", line 324, in fetch_watch_info
self._watch_info = self.send_and_read(WatchVersion(data=WatchVersionRequest()), WatchVersion).data
File "/usr/local/lib/python2.7/dist-packages/libpebble2/communication/__init__.py", line 286, in send_and_read
return queue.get(timeout=timeout)
File "/usr/local/lib/python2.7/dist-packages/libpebble2/events/threaded.py", line 81, in get
raise TimeoutError()
libpebble2.exceptions.TimeoutErrorI also took a look at: ~src/oref0/bin/peb-urchin-status.sh
It references everything as pbbl but I'm guessing that is just the name being old.
All I'm really looking for is to see if there is an easy way to confirm that the Urchin watchface would work...The notify command seems like it would be a good indicator but if there is something else, I'd definitely try it.
Also, documentation for this is in the process of being updated here:
https://github.com/Aaybob/docs/blob/a6b5303faf284399fabd19ef696e283f10d083c4/docs/docs/walkthrough/phase-1/offline-looping-and-monitoring.md
If this doesn't work, I'm thinking of setting up a simple webserver on the edison with a static IP and output all the OpenAPS stuff that way...Would rather have the lovely Urchin Pebble config, though.
Thanks in advance!
Followed all the directions for setting up with BT support for OpenAPS per the new docs...When I do this:
root@obi:~/explorer-aps# bluetoothd --version
5.23
root@obi:~/explorer-aps# ps -aux | grep bluetoothd
root 14248 0.0 0.1 5948 1796 ? S 18:44 0:00 sudo /usr/local/bin/bluetoothd --experimental
root 14256 0.0 0.2 5084 2056 ? S 18:44 0:00 /usr/local/bin/bluetoothd --experimental
root 26898 0.0 0.0 4320 892 pts/0 S+ 19:16 0:00 grep bluetoothd
Stymied! Thanks!
You have the old bluez
do you want the new one?
YES! How do I get the new bluez?
Trying "apt-get purge bluez"
well, I’m only going off the setup script part as a guide…I’ve never just plain upgraded it would the set-up script.
# Install Bluez for BT Tethering
echo Checking bluez installation
if ! bluetoothd --version | grep -q 5.37 2>/dev/null; then
cd $HOME/src/ && wget https://www.kernel.org/pub/linux/bluetooth/bluez-5.37.tar.gz && tar xvfz bluez-5.37.tar.gz || die "Couldn't download bluez"
cd $HOME/src/bluez-5.37 && ./configure --enable-experimental --disable-systemd && \
make && sudo make install && sudo cp ./src/bluetoothd /usr/local/bin/ || die "Couldn't make bluez"
oref0-bluetoothup
else
echo bluez v 5.37 already installed
fi
I don’t understand bluez well enough to know about the need for the
--enable-experimental stuff that goes in there too.
BUT, if you want it to all be added automatically, you just need to run the setup script for your loop with the
--btmac=AA:BB:CC:DD:EE:FF
Yeah, I thought the set up script would have upgraded...Yes, included the btmac as part of the setup script but this snippet should hook me up
I just purged and then installed...5.23 again!
This should hook me up...Thanks, @Kdisimone !
yeah, the more I look at it, the clearer that code looks. Whew
BTW, that code if from master. I believe dev branch is fetching 5.44
Ahhh....I'll go looking in there...thanks!
# Install Bluez for BT Tethering
echo Checking bluez installation
bluetoothdversion=$(bluetoothd --version || 0)
bluetoothdminversion=5.37
bluetoothdversioncompare=$(awk 'BEGIN{ print "'$bluetoothdversion'"<"'$bluetoothdminversion'" }')
if [ "$bluetoothdversioncompare" -eq 1 ]; then
killall bluetoothd &>/dev/null #Kill current running version if its out of date and we are updating it
cd $HOME/src/ && wget https://www.kernel.org/pub/linux/bluetooth/bluez-5.44.tar.gz && tar xvfz bluez-5.44.tar.gz || die "Couldn't download bluez"
cd $HOME/src/bluez-5.44 && ./configure --enable-experimental --disable-systemd && \
make && sudo make install && sudo cp ./src/bluetoothd /usr/local/bin/ || die "Couldn't make bluez"
oref0-bluetoothup
else
echo bluez v ${bluetoothdversion} already installed
fi
I have 5.37 making now...see if it finishes and installs ok
Weird...I would have thought the setup script should have done this for me...I did a clean install into a new dir...but we'll see how this goes...takes awhile. Appreciate it!
Hi folks - newbie here - had some questions on starting up.
First, is nightscout necessary? (I'm happy to set it up, but medtronic connect isn't available outside of the US and I haven't been able to find the apk online - I'm on android)
nightscout is not necessary…but it is useful. However…I’m not sure why you wouldn’t be able to do it. The setup is off the phone using heroku.
Lol. If the Bluez code in the dev branch doesn't work.... its probably my fault O:-)
Also @logichammer if you get it working, let me know. Currently the PEB_BT part of oref0-setup is completely broken -- and the instructions are only sort of there.
I've been playing with getting it working for a little bit now with very little luck
Huh, I was going to try pebble stuff in a couple weeks...
Im working on it. When / if I get it figured out, I'll try and fix all the documentation
Thanks, @applehat ! That makes sense and I am on dev...good to know what is going on...I may switch to master if can't get it fixed...looks like I need to kill bluez and uninstall...got a "text file busy" error. More to come and thanks for the info! Really helps!
I am starting bluetooth tethering and I have successfully completed the install dependencies step. For the next step for bluetooth setup it indicates to Restart the Bluetooth daemon to start up the bluetooth service, does this mean to sign on still as root for programming to proceed? sorry I dont know what daemon is and google is not much help for my non tech brain.
A daemon is a unix application that runs like a service, in the background.
You don't need to be root...You should be able to do this:
sudo systemctl restart bluetooth.service
ok so I can just input that command with this prompt
yep...might ask for your password but you should be good
Good version of bluetooth and you are already root...but that command should work
So @logichammer / @Kdisimone - For Pebble Integration right off the rig - are you guys wanting it to work the exact same as the current integration with a phone? Like graph history, ect? I'm thinking about forking the project and just making it about status messages - and then letting it also be used for oref1 messages. -- I already have an android wear watch and xDrip, so I find myself way more interested in the pebble just showing me current loop integrity more then any status about diabetes
@Kdisimone / @applehat :
yah!
Good to see my commits in the code didn't destroy everything.
I did the install manually for bluez so I can't attest to that :)
@logichammer ok thanks!!!
Ideal scenario for me would be @ELUTE 's skyloop where you get current bg, temp, last time it talked, etc:
but I'll take what I can get...especially in the wild!
@logichammer if my putty does not look exactly like the example do I need to restart from the begining?
You look good...you have more commands to run...like scan on, I think
I'm actually doing this myself
@logichammer yes thanks jsut wanted to double check before kept going :)
you are good!
when i get to the step where on my android phone I need to pair it with the adapter bluetooth, where do I figure out what the adapter bluetooth number is? last time I did it there were multiple discover able bluetooth devices to choose from on my phone
might be the first mac address you see when you run: bluetoothctl
Mine is:
[NEW] Controller 58:A8:39:01:33:22 obi [default]
obi is the name of my edison...yours is daisy...but that's the mac address the 58 number...
look for that maybe on the phone
I'm not doing that part...trying to connect to pebble...and failing
ok thanks!... hmmmm dont think this last command was successful
Default agent doesn't return anything :)
@applehat, I am connected to the pebble...command I can run with base openaps to confirm connection?
Anything to convince myself they are talking?
@logichammer I'm in a weird situation where I am not wanting to wear the pebble as a watch, but instead just as a display for my rig.
Follow the pancrabble docs for that
Got this back...and for awhile the prompt had the watch as part of the prompt:
[bluetooth]# trust B0:B4:48:F5:0A:4A
[CHG] Device B0:B4:48:F5:0A:4A Trusted: yes
Changing B0:B4:48:F5:0A:4A trust succeeded
[bluetooth]# pair B0:B4:48:F5:0A:4A
Attempting to pair with B0:B4:48:F5:0A:4A
[CHG] Device B0:B4:48:F5:0A:4A Connected: yes
[CHG] Device B0:B4:48:F5:0A:4A Modalias: bluetooth:v005Ep0001d0112
[CHG] Device B0:B4:48:F5:0A:4A UUIDs: 00000000-deca-fade-deca-deafdecacaff
[CHG] Device B0:B4:48:F5:0A:4A UUIDs: 00001200-0000-1000-8000-00805f9b34fb
[CHG] Device B0:B4:48:F5:0A:4A ServicesResolved: yes
[CHG] Device B0:B4:48:F5:0A:4A Paired: yes
Pairing successful
[CHG] Device B0:B4:48:F5:0A:4A ServicesResolved: no
[CHG] Device B0:B4:48:F5:0A:4A Connected: no
You can make sure it's installed and add it as a vedor and add the pebble as a device then try an
openaps use pebble notify "test" "test"
Yeah, when I run them, they still time out
Yah...I might do another reinstall with master this time
Using dev everything right now
script and branch
Did you use oref0-setup with pebble flags?
If so you need to undo the stuff it adds and do everything manually most likely.
let me confirm / redact my params
Remove any previous pebble stuff you have using
openaps remove _____
Then try following pancrabble's install instructions
Once I get this all sorted myself I'll fix oref0-setup
oref0-setup --dir=/root/explorer-aps --serial=xxx --cgm=G4-upload --ns-host=https://xxx.azurewebsites.net --api-secret=xxx --tty=/dev/spidev5.1 --enable=' autosens autotune meal ' --radio_locale='US' --btmac=6E:92:1F:5F:86:F1
That's fine - you didn't do any dumb oref0 pebble stuff then :p
Is it normal for your pebble MAC address to change? It shouldn't in my opinion...feel like I am doing something wrong there...great ideas for all of that
Your probably seeing the pebble address and the pebble LE address
Yeah...noting both of those and they both change if I connect, forget, and then rescan
Check your pebble MAC under settings and device info
AHHHH
And use that
The output of the bluetoothcli is confusing
BEAUTY!
Those MACs flying by can be other devicing probing
Settings --> System -->Information
I know my office is flooded with BT. Lol
Yeah there you go.
Perfect! Just what I wanted
@logichammer sorry I cant help with yoru problem with pebble :( should I jsut repeat this command as is not prompting anything to happen?
Sorry, I already stopped working on it tonight and I'm going off memory haha
Lots of things to try...thanks for your help, man! I'm going to start fresh with master, I think
@laurathiessen what command?
@logichammer keep bluez
The newer version installed by Dev is compatible with master
No reason to recompile and downgrade.
She's trying to figure out on her phone what the edison's device should be
BT device on the Edison to connect to the phone...
@laurathiessen I'm on my phone so gitter history is not great. Mind asking your question again?
and yes, I figure master won't explicitly downgrade me so I should be good...ah, and get what you were saying about it being backwards compatible.
Or forwards compat...
Master most likely won't try a downgrade... Tho I'm not sure what swapping back to master over dev will really help.
@applehat I’ve been installing using the 5.44 for awhile now…all have gone just fine. you’re good. @logichammer YES
@Kdisimone good to hear. I figure if it wasn't I'd have heard about it by now :p
@applehat I am doing the bluetooth tethering step on bluetooth setup... i am at the point where you llaunch the bleutooth control program ... the last line "default-agent" comes back with nothing after it just goes back the the bluetooth # which is differeent then the exampe shown
Just continue on
So the dev script and branch should be good? Wonder what I am doing wrong...I'll start with a new dir and see what happens
@laurathiessen the outout of bluetoothcli can be very erratic.
show screen shots @laurathiessen that helps a lot
or copy the lines in your window and paste them here.
ok i will repost them one sec :)
@logichammer what is not working that you are expecting to work?
Just the notify command...times out:
root@obi:~/explorer-aps# openaps use pebble2 notify "hello" "testing"
Traceback (most recent call last):
File "/usr/local/bin/openaps-use", line 6, in <module>
exec(compile(open(__file__).read(), __file__, 'exec'))
File "/root/src/openaps/bin/openaps-use", line 63, in <module>
app( )
File "/root/src/openaps/openaps/cli/__init__.py", line 51, in __call__
self.run(self.args)
File "/root/src/openaps/bin/openaps-use", line 57, in run
output = app(args, self)
File "/root/src/openaps/openaps/uses/__init__.py", line 92, in __call__
return self.method.selected(args)(args, app)
File "/root/src/openaps/openaps/uses/__init__.py", line 31, in __call__
return self.method(args, app)
File "/root/src/openaps/openaps/uses/use.py", line 45, in __call__
output = self.main(args, app)
File "/root/.local/lib/python2.7/site-packages/pancreabble/pebble.py", line 28, in main
pebble.run_async()
File "/usr/local/lib/python2.7/dist-packages/libpebble2/communication/__init__.py", line 103, in run_async
self.fetch_watch_info()
File "/usr/local/lib/python2.7/dist-packages/libpebble2/communication/__init__.py", line 324, in fetch_watch_info
self._watch_info = self.send_and_read(WatchVersion(data=WatchVersionRequest()), WatchVersion).data
File "/usr/local/lib/python2.7/dist-packages/libpebble2/communication/__init__.py", line 286, in send_and_read
return queue.get(timeout=timeout)
File "/usr/local/lib/python2.7/dist-packages/libpebble2/events/threaded.py", line 81, in get
raise TimeoutError()
libpebble2.exceptions.TimeoutError
pebble2 is the new device I gave it using Mark's device add...since using the setup script already installs a device called pebble
or if I use the one the oref script set up, I get this:
@logichammer did you do the part where you bound the pebble to hci0 using
rfcomm bind hci0 MACHEER?
root@obi:~/explorer-aps# openaps use pebble notify "hello" "testing"
usage: openaps-use pebble [-h] USAGE ...
openaps-use pebble: error: argument USAGE: invalid choice: 'notify' (choose from 'shell')
I have a few times but I can't be certain with this current installl
will run through again to be sure
@laurathiessen you are posting the instructions. YOu aren’t posting YOUR screen. We need to see YOUR screen
I'm going to reconnect using the BT mac address from the pebble...basically do Mark's docs again and see
back in 5!
yes was trying to post which instructions I was at :)
@laurathiessen try running
default-agent again
yes, you should have gotten confirmation message for default-agent on.
run it again like @applehat suggests :smile:
command to disconnect ?
Failed to pair: org.bluez.Error.AlreadyExists
[CHG] Device 6E:29:4C:5A:D8:F8 RSSI: -38
[CHG] Device 6E:29:4C:5A:D8:F8 AdvertisingFlags: 0x02
[CHG] Device 6E:29:4C:5A:D8:F8 AdvertisingFlags: 0x00
[bluetooth]#Already forgot on pebble but edison says we're paired, dude!
quit
or disconnect the pairing?
disconnect the pairing
sorry
that wasn't clear on my part
Remove
perfect
did the trick...repairing
@applehat @Kdisimone it keeps running with more and more lines... and on my phone when I pick anything to pair it says i cant connect
Paired and then:
root@obi:~/explorer-aps# sudo rfcomm bind hci0 B0:B4:48:F5:0A:4A
Can't create device: Address already in usetrying notify
guessing it has been over 3 minutes... so if I redo the last default -agent will it make it discoverable again to pair and I should retry?
quit bluetoothctl and start over
Best to post a screenshot too when you get the successful messages too so that we all agree you’re where you need to be. Troubleshooting this part if you had something go wrong earlier is kind of fruitless. This section is a bit touchy
WOOOOHHOOOOOOOO!!!!!
OH HELL YEAH
Got it, baby!
Thanks so much Katie and Cameron
notifications on my watch via the edison
Had to release rmcomm
and then rebind
and viola...connection!
no reinstalls needed
Haha. Now add that bind into /etc/rc.local
So it rebinds.
Yes, I see that in the docs...so Marks pebble notify works...but you can't use the device that gets installed by openaps for notify, correct?
WIll the openaps pebble work for urchin, etc?
The OpenAPS device stuff is broken
Got it
The stuff oref0-setup installs
fix it please? :)
I plan to fix all that @scottleibrand
so if if I want to feed urchin data the best way to do that would be...
I love the applehat!
@applehat :+1:
My favorite words to hear @applehat :D :clap:
@Kdisimone just restart the bluetoothctl or restart from the actual beginning with sudo killall bluetoothd
Looks like the first part of mark's docs are the way to go then?
@logichammer either follow marks guide and attempt to get that working, or just wait for me to get it all sorted :p
Ha...leaving in two weeks and will be off the grid for three so I might try to get something kludged together...any testing I can do to help you?
There's an issue with the actual pancrabble code in that it needs a "display_time" in the monitor/glucose.json, but it doesn't exist for me. I didn't dig anymore past that tho.
I believe USB Dexcom stores a "display_time" field, but my xDrip / NS setup does not.
@scottleibrand might have a little more insight there.
correct. we've seen that with other things as well (autotune I think)
there are some easy jq one-liners for creating the field
I need to sit down and learn OpenAPS report engine a bit better
and the /etc/rf.local in the docs is a typo...should be rc.local, yes?
Yep
tanks and airplanes!
@applehat at some point we need someone to do some work on porting some openaps aliases over to proper shell scripts. that might be a good opportunity to learn how they all work
@scottleibrand mention me on GitHub if you got anything like that and I'll try and jump on it.
we haven't even gotten that far yet
we converted the pump-loop alias to oref0-pump-loop.sh, but that's all so far
Having default aliases as bash scripts would make the whole system a lot easier to understand for sure.
yep. pretty much any time we want to touch an alias from now on, we should convert it to a script
The whole alias system is a little hard to chew through since the only way I can edit my OpenAPS.ini is in vi
you can use
openaps (report|alias) add commands to do that too
That's it from me tonight...thanks for the help and let me know if you want me to test anything....I'll be get urchin actually set up on Friday. Night, folks!
I mean to review what the existing ones are doing
openaps alias show or openaps report show foobar.json --cli
@Kdisimone just restart the bluetoothctl or restart from the actual beginning with sudo killall bluetoothd
@scottleibrand TIL
this stuff is in the docs too. :)
@laurathiessen beginning
k thanks! will start and come back and post when I get towards the end
I'm a developer! I don't read docs until I'm stuck then k search them :angel:
:-p
I swear I've read through every page of the docs tho... Just retention of all that information... Not so much.
::subtracts those words from @applehat's previous total of nice words ;) ::
Haha. It's a lot
I don't tend to retain info unless I am hands on with it.
@laurathiessen I believe I strongly suggested posting at interim parts to make sure you are really getting the right results before proceeding ahead
@danamlewis new oref1 feature? "nice words onboard"
LOL
if you get to the end of this and say “It’s not working”…it is very difficult to know if you really had the beginning parts right without seeing them. This part is touchy
I did want to build a gitter bot...
I wish slack was more-free then it is.
Gitter makes my phone hot.
@danamlewis speaking of bots.... We have a slack bot a work that responds to
cakewith a determination if I'm allowed to have any based off my latest NS reading.
I know so many people who would get violently offended by that idea... :-)
The idea of cake-bot?
@Kdisimone success o the setup
@danamlewis
the idea of someone telling them whether they're allowed to eat (or do anything, really) based on their blood sugar
you set it up for you, though, so... :-)
@laurathiessen looks great! keep going
power off successfull
@scottleibrand Nope. I showed a co-worker that NS had a json api and it just happened.
@Kdisimone @danamlewis its now going crazy again
heh. that's what you get for sharing your NS URL I guess. :)
@scottleibrand the URL is too good not to share.
yes…it is actively scanning…you will see a lot of stuff go by. just keep working
ok on to the next step then, thanks!
think power on was successfull.....
discoverable on sucessfull @Kdisimone
@danamlewis @Kdisimone discover able successful
:+1:
:+1:
@Kdisimone scan on not successfull :(
guessing restart from the begining again?
quit first then
no
it was already started successfully…look back a couple screenshots
you already did scan on once before
keep going
ok so because it was succefull no need to redo it.... so then I need to just try the unsucceful one again?
k thanks!:)
it depends on where you are in the process.
yes, when things are successful, you don’t redo it
but, again, it depends on where it fails
ok ... to keep going i need to run the scan on again?
no. your scan is on. keep going
ok
agent on not sure if successfull
keep going or redo?
redo
ok successfull this time
:+1:
default agent successfull
:+1:
darn cpy and pasted the last line but I will try adn pair
dammm all things my phone wont pair with
you have an iphone or android?
android
Sorry can't figure out how to lost a screen shot from my phone to show u what was discoverable
Well, sorry…I don’t have an android so I can’t help you on that last step.
ok i can ask on facebook... so I "quit" an then start again from the beginning tomorrow
I don’t think there will be much more help on fb without additional information. Basically you know how to do all the way until the last part. And the last part is dependent on your phone and your cell provider (if they allow BT tethering hotspot) So, before you ask for help…make double sure that bt tethered hotspot is allowed by your cell provider, and enabled on your phone
ok I will make sure @Kdisimone thanks for all your double checks much appreciated! im off to sleep :)
:+1: good job, youre almost there
@ecc1 hi, could you please tell me in details what did you do to fix the BT
How can enforce the BT to connect to the mobile
I reset the SMC, the computer still can not recognize EDISON,
Lost Glucose Readings for 6 hours last night and now my loop keeps failing because monitor/iob.json is empty. Any clue how to resolve this?
@applehat how do they come in when they work? Via dexcom to share to NightScout bridge to OpenAPS? If so:
Try to ssh into OpenAPS
Or use cable
Try ping 8.8.8.8
If that fails, you have connectivity issues
Btw iob.json being empty suggests maybe pump communications failing
Try a fresh pump battery
Type '''l''' (that's "ell" or "L" lower case )
Watch the logs
I've been watching my logs, that's how I know the error is happening :p
And yeah they normally come in from Nightscout (or xDrip APS)
K
Also try '''curl -v https://xxxcgmsite.azurewebsites.net/api/v1/experiments/test --header "api-secret: <api-secret>“'''
Which confirms that your NightScout can send current BG values. Of course plug in correct NS URL
Doesn't appear to be a NS or Internet connectivity issue.
Hmm
Wish I could help more
openaps ns-loop seems to be failing around "refresh temp targets"
Does it look like its reading pump data?
Pump data is fine. It pulled in a blood glucose check I did a few minutes ago.
That's showing up in NS
@laurathiessen you aren't by chance on Rogers wireless (in Canada) are you? I'm on android with rogers and they don't allow BT tethering. I'm currently working on a work-around for this involving "rooting" my phone but need a bit of time to get that all sorted out. I don't know of other carriers but some just don't allow BT tethering
Invoking
monitor/iob.json throws a "can't set property "lastBolusTime" of undefined"
After digging more it looks like it's maybe having issuing getting my iob, carb ratios, ECT... No idea how to actually fix that tho beyond rerunning oref0-setup possibly.
If no one has any ideas, I'll just do that in an hour or so when I am at work.
You could '''killall -g openaps'''
Then cd to OpenAPS directory
openaps use pump mmtune
Then get the pump history - I forget the command- and status, etc
But I don't know this part cold
I'll try that. Thanks.
My rig was not looping in the middle of the night. I looked at looplog, and it said Indexerror: byTearray index out of range. Also I had problems with radio range. Was the error just a function of poor pump communication?
is xdrip work for G5...or do you need xdrip+....what's the difference exactly? xdrip vs. xdrip+?
@rsilvers129 did you try checking / replacing pump battery?
@mhaeberli No, but my battery is 1.47v now.
And I just tested three different pumps, and all had similar signal strength.
I think my Explorer signal strength is poor. Last night I woke up and saw that the loop was not working. I looked at the logs, and had the error about the radio may be out of range. It was 3-4 feet away from the pump.
I just did extensive testing with three pumps to rule out the pump. From 109cm away, I got -99, -99, and -99. From 69 cm away, I got -99, -99, -99. From 0cm away (side by side), I got -86, -83, and -85. In case my enclosure and battery were effecting it, I took off the case and pulled away the battery and from 69cm, I got -99 still. In case this was a cross-polarization effect, I stood the pump upright, and at 69cm I got -99. I then put the original pump in my pocket with the rig, and got -80.
The trace on my board is cut for 915 mhz. I just looked at it under a microscope, and it looks as I wold expect.
What are some signal values other people get?
I just did extensive testing with three pumps to rule out the pump. From 109cm away, I got -99, -99, and -99. From 69 cm away, I got -99, -99, -99. From 0cm away (side by side), I got -86, -83, and -85. In case my enclosure and battery were effecting it, I took off the case and pulled away the battery and from 69cm, I got -99 still. In case this was a cross-polarization effect, I stood the pump upright, and at 69cm I got -99. I then put the original pump in my pocket with the rig, and got -80.
The trace on my board is cut for 915 mhz. I just looked at it under a microscope, and it looks as I wold expect.
What are some signal values other people get?
Our traces are cut but I believe the excess wire was removed , too...
We have seen -85 maybe a yard or so away but no science
@scottleibrand @danamlewis In my pizza experiments, I have decided that at the 3-4 hour mark after high-fat foods, I spike. Research shows that high-fat large meals need, on average, 42% more insulin than normal meals per unit of carb. remainingCarbsFraction is defaulted to 0.7 and the docs say to probably not change it. Is my pizza testing evidence, that for me, I may be better off with remainingCarbsFraction set to 0.5 or 0.6?
@JELCRAWFORD I think that's resolved (redid ns site and reran Oref0 again). Thanks
Another question for anyone who's available. I've been looping for a few days but am still having issues. I'm getting temp basals about 1-3x/hour but not consistently. When I follow the logs it states that the loop is being closed, but like I said, no temp basals are enacted. I think we're having connectivity issues with the internet, which we're working on. Is this my problem? Anyone know what it could be? Thanks for the help. I hope to one day be able to help others as much as you all have helped me!
@garykidd xDrip+ is the way to go. xDrip is really out of date and not maintained as far as I can tell.
thx. Just saw that dexcom app works with android now too and available on play store for download....
@applehat are you using G5 with android via xdrip+?
yes I am
xDrip+ lets me run sensors past 7 days and transmitters past their life too (when self-replacing batteries)
It also actually seems MORE accurate then the Dexcom algo
So... per my rig being dumb.
autosense-loop is doing this:
Jun 08 08:26:14 openaps autosens-loop.log: reporting settings/autosens.json
Jun 08 08:27:16 openaps autosens-loop.log: Thu Jun 8 10:27:04 CDT 2017
Jun 08 08:27:16 openaps autosens-loop.log: /root/src/oref0/lib/profile/isf.js:20
Jun 08 08:27:16 openaps autosens-loop.log: isf_data = _.sortBy(isf_data.sensitivities, function(o) { return o.offset; });
Jun 08 08:27:16 openaps autosens-loop.log: ^
Jun 08 08:27:16 openaps autosens-loop.log: TypeError: Cannot read property 'sensitivities' of undefined
Jun 08 08:27:16 openaps autosens-loop.log: at Function.isfLookup (/root/src/oref0/lib/profile/isf.js:20:33)
Jun 08 08:27:16 openaps autosens-loop.log: at detectSensitivityandCarbAbsorption (/root/src/oref0/lib/determine-basal/cob-autosens.js:122:24)
Jun 08 08:27:16 openaps autosens-loop.log: at Object.<anonymous> (/root/src/oref0/bin/oref0-detect-sensitivity.js:80:5)
Jun 08 08:27:16 openaps autosens-loop.log: at Module._compile (module.js:571:32)
Jun 08 08:27:16 openaps autosens-loop.log: at Object.Module._extensions..js (module.js:580:10)
Jun 08 08:27:16 openaps autosens-loop.log: at Module.load (module.js:488:32)
Jun 08 08:27:16 openaps autosens-loop.log: at tryModuleLoad (module.js:447:12)
Jun 08 08:27:16 openaps autosens-loop.log: at Function.Module._load (module.js:439:3)
Jun 08 08:27:16 openaps autosens-loop.log: at Module.runMain (module.js:605:10)
Jun 08 08:27:16 openaps autosens-loop.log: at run (bootstrap_node.js:423:7)
@applehat thx. Just curious what type of phone are you using and are you having good results with connectivity/ missed readings?
and pump-loop is repeating this:
Starting supermicrobolus pump-loop at Thu Jun 8 10:26:21 CDT 2017 with 20 second wait_for_silence:
Jun 08 08:26:21 openaps pump-loop.log: Waiting up to 4 minutes for new BG: glucose.json newer than pump_loop_completed
Jun 08 08:26:44 openaps pump-loop.log: Radio ok. Listening: .No pump comms detected from other rigs
Jun 08 08:27:16 openaps pump-loop.log: Preflight OK. Old pumphistory, waiting for 20 seconds of silence: Radio ok. Listening: .No pump comms detected from other rigs
Jun 08 08:27:37 openaps pump-loop.log: RefreshError: carb_ratio undefined out of bounds
Jun 08 08:27:37 openaps pump-loop.log: ed pumphistory
Jun 08 08:27:53 openaps pump-loop.log: Old settings refreshISF of null is not supported
Jun 08 08:27:53 openaps pump-loop.log: ed. glucose.json newer than pump_loop_completed.
Jun 08 08:28:01 openaps pump-loop.log: Temp refresh at startup (bootstrap_node.js:147:9)
Jun 08 08:28:01 openaps pump-loop.log: ed
Jun 08 08:28:14 openaps pump-loop.log: Could not parse input data: SyntaxError: /root/myopenaps/monitor/iob.json: Unexpected end of JSON input
Jun 08 08:28:14 openaps pump-loop.log: at JSON.parse (<anonymous>)
Jun 08 08:28:14 openaps pump-loop.log: at Object.Module._extensions..json (module.js:588:27)
Jun 08 08:28:14 openaps pump-loop.log: at Module.load (module.js:488:32)
Jun 08 08:28:14 openaps pump-loop.log: at tryModuleLoad (module.js:447:12)
Jun 08 08:28:14 openaps pump-loop.log: at Function.Module._load (module.js:439:3)
Jun 08 08:28:14 openaps pump-loop.log: at Module.require (module.js:498:17)
Jun 08 08:28:14 openaps pump-loop.log: at require (internal/module.js:20:19)
Jun 08 08:28:14 openaps pump-loop.log: at Object.<anonymous> (/root/src/oref0/bin/oref0-determine-basal.js:98:24)
Jun 08 08:28:14 openaps pump-loop.log: at Module._compile (module.js:571:32)
Jun 08 08:28:14 openaps pump-loop.log: at Object.Module._extensions..js (module.js:580:10)
Jun 08 08:28:14 openaps pump-loop.log: Traceback (most recent call last):
Jun 08 08:28:14 openaps pump-loop.log: File "/usr/local/bin/openaps-report", line 82, in <module>
Jun 08 08:28:14 openaps pump-loop.log: app( )
Jun 08 08:28:14 openaps pump-loop.log: File "/usr/local/lib/python2.7/dist-packages/openaps/cli/__init__.py", line 51, in __call__
Jun 08 08:28:14 openaps pump-loop.log: self.run(self.args)
Jun 08 08:28:14 openaps pump-loop.log: File "/usr/local/bin/openaps-report", line 75, in run
Jun 08 08:28:14 openaps pump-loop.log: output = app(args, self)
Jun 08 08:28:14 openaps pump-loop.log: File "/usr/local/lib/python2.7/dist-packages/openaps/cli/subcommand.py", line 52, in __call__
Jun 08 08:28:14 openaps pump-loop.log: return self.method.main(args, app)
Jun 08 08:28:14 openaps pump-loop.log: File "/usr/local/lib/python2.7/dist-packages/openaps/reports/invoke.py", line 48, in main
Jun 08 08:28:14 openaps pump-loop.log: reporters.Reporter(report, device, task)(output)
Jun 08 08:28:14 openaps pump-loop.log: File "/usr/local/lib/python2.7/dist-packages/openaps/reports/reporters/__init__.py", line 33, in __call__
Jun 08 08:28:14 openaps pump-loop.log: self.blob = self.serialize(data)
Jun 08 08:28:14 openaps pump-loop.log: File "/usr/local/lib/python2.7/dist-packages/openaps/reports/reporters/__init__.py", line 31, in serialize
Jun 08 08:28:14 openaps pump-loop.log: return self.method.serialize(render(data), self)
Jun 08 08:28:14 openaps pump-loop.log: File "/usr/local/lib/python2.7/dist-packages/openaps/vendors/process.py", line 56, in prerender_json
Jun 08 08:28:14 openaps pump-loop.log: return json.loads(data)
Jun 08 08:28:14 openaps pump-loop.log: File "/usr/lib/python2.7/json/__init__.py", line 338, in loads
Jun 08 08:28:14 openaps pump-loop.log: return _default_decoder.decode(s)
Jun 08 08:28:14 openaps pump-loop.log: File "/usr/lib/python2.7/json/decoder.py", line 366, in decode
Jun 08 08:28:14 openaps pump-loop.log: obj, end = self.raw_decode(s, idx=_w(s, 0).end())
Jun 08 08:28:14 openaps pump-loop.log: File "/usr/lib/python2.7/json/decoder.py", line 384, in raw_decode
Jun 08 08:28:14 openaps pump-loop.log: raise ValueError("No JSON object could be decoded")
Jun 08 08:28:14 openaps pump-loop.log: ValueError: No JSON object could be decoded
Jun 08 08:28:14 openaps pump-loop.log: Error, retrying
Jun 08 08:28:14 openaps pump-loop.log: Waiting for 30s silence before mmtuning
Jun 08 08:28:48 openaps pump-loop.log: Radio ok. Listening: .No pump comms detected from other rigs
Jun 08 08:29:47 openaps pump-loop.log: Listening for 30s silence before mmtuning: .No pump comms detected from other rigs
Jun 08 08:29:47 openaps pump-loop.log: mmtune: "916.516", 5, -76 waiting for 32 second silence before continuing
Jun 08 08:30:13 openaps pump-loop.log: No pump comms detected from other rigs
@garykidd Nexus 6, and most days I have about 95% capture rate
newer phones would probably do better
@applehat there's an entire section in the docs for troubleshooting this. You really should read it. :smile:
@rsilvers129 can you explain your reasoning why you think a lower remainingCarbsFraction would help with going high? I've only seen people raise it.
Also, I've seen a few people w the iob out of bounds crop up. Usually self resolves, or resolves w manual runs of things. But no one has reported back, so welcome any theories on why it happens in case it's something we can build a fix for
Thanks for the doc link @danamlewis
Yeah, we definitely need people doing the digging in manual troubleshooting and reporting back what they find for root cause if we're going to be able to do an automated fix.
I'll report back after I get it fixed
:+1:
@scottleibrand on a related note..regarding the Troubleshooting section on cannot get rfspy state or version error....will do some morer toubleshooting but is there anything that I can provide that might help the good of the cause. I'm fully expecting to happen again. This is the error (perhaps among others) that cuases the two small LEDs to illuminate next to the UART port.
@scottleibrand The docs say "remainingCarbsFraction
This is the fraction of carbs we’ll assume will absorb over 4h if we don’t yet see carb absorption." So lowering it would assume less carbs will absorb in the first four hours, leaving more of the carbs floating that need to be taken care of after the first four hours.
This is the fraction of carbs we’ll assume will absorb over 4h if we don’t yet see carb absorption." So lowering it would assume less carbs will absorb in the first four hours, leaving more of the carbs floating that need to be taken care of after the first four hours.
If you have 2 explorer rigs and you charge them both overnight and then unplug for use at the same time, and one is now at 8% battery left and the other is at 61% is it likely have a lipo problem on the 8% one, or maybe a charging issue I am not aware of? Both have 2500mah lipos
Ugh. Getting into my rig on my work computer is proving difficult. At home, if I plug into the "OTG" side (i have my edison still configured as a host device) it shows up as a network adapter... not so much at work
@davidkeddydb on the 8% one, do you get both red lights all night? on mine, I got two red lights for a few minutes but the micro-usb cable wiggled and dropped the 2nd (charging) light evidently. Noticed it losing charge on NS so investigated. I had to switch micro-usb cables to get a good/consistent fit
if you're getting both lights all night, then I'd suspect the battery yes
@rsilvers129 ah, that logic makes sense, but isn't actually correct. future predictions about carb absorption don't directly affect later retrospective assessments of what actually happened. those are entirely driven by how much carb absorption is actually observed in BG deviations.
so at, say, 3h into your meal, you have a certain amount of COB (regardless of remainingCarbsFraction), and you're most likely projected to absorb it all within another 4h (because current deviations are high enough). if not, then any remainingCarbs scheduled to absorb past the 4h (7h) mark can be added in as well to trigger more high temping, but only if remainingCarbsFraction is high enough to include them. in reality, remainingCarbsFraction really only kicks in when you have minimal observed carb absorption, so it just determines how aggressively to SMB for any carbs you enter but haven't fully bolused for in the ~30 minutes it takes observed carb absorption to ramp up.
@scottleibrand / @danamlewis - Think I have my issue sorted. Rerunning my loop now to see if my change fixes it.
@annettemvalle We had the same situation overnight, was caused by /tmp being full. What does it look like if you run:
df -h /tmp
nevermind.
Any ideas on why openAps not helping with temp basals? Pictures to follow.
Hover over the OpenAPS pill and it will tell you what its wanting to do
Sorry @danamlewis - I tried stepping back through the code and tracking down what was going on, but couldn't find the break point. Ended up having to wipe away
myopenaps completely and rerun oref0-setup =/
K. Thanks for trying to dig. Can you also when you get a chance poke at your database and see if you see any wonky pump records from around then?
I backed up my old installation that was wonky so I should be able to dig. Had to get back to real work tho. Realized it was 1pm and I had been doing beetus stuff all day
I got lucky today while my rig was down. Managed to stay in range with just my base basal. :P
dears I have one more question about oref0-setup. If I decide to re-run this script, what will happen with my old settings, i.e. autotune profile? will it be erased?
I got an insulinReq 3.49 pushover. Does that mean I should manually dose that? I dind't see the message as I was ignoring my pushovers due to too many unnessesary urgent warnings. But I noticed that the next two SMBs were 0.7 and 0.2. If it wanted 3.49, and I didn't provide it, why wouldn't the next two SMBs be at maxBolus?
@rsilvers129 at that moment, it thought you needed 3.49U of insulin, but the maxBolus was 0.7U, so it only gave that. something changed with the next CGM reading that made it change its mind, and decide you only needed ~0.6U of insulin, so it gave 1/3 of that (0.2U). you definitely should not blindly dose the insulinReq from the Pushover: if that were safe, we would have SMB do so automatically. but if you know that there's a lot more insulin needed (maybe you haven't bolused for your meal yet) and want to do a manual bolus, that pushover is a reminder to do so. if not, you can just keep an eye on SMB and make sure it's properly doing its thing.
Ok. I get it. My max is set to 1.0, but I get what you are saying.
@rsilvers129 please read the pushover section under oref1 page
what is the best way to test the range of pump and explorer board?
I know there is a way but I am having problems finding it on the openaps.readthedocs page
You can run setup again and it will give the signal strength.
oref0 setup?
killall -g openaps /etc/init.d/cron stop openaps mmtune
kill openaps, stop it from running in cron, then run openaps mmtune to get signal strength at different distances.
awesome
now should I start cron again after I am done?
Make sure to
/etc/init.d/cron start after your done if you want the rig to loop again
LOL :sweat_smile: yeah
thank you very much
The signal strength is in -dBm, so 0 would be
FULL SIGNAL and -100 would be WEAK
thank you again
No problem!
back again, trying to figure out why my rig won't connect to the internet, neither with wifi nor USB...network.log didn't reveal the issue, so I looked at the system log, but I can't find any smoking gun...can someone take a look at this and let me know if they see anything indicative?
Jun 7 17:41:47 localhost systemd[1]: Starting D-Bus System Message Bus...
Jun 7 17:41:47 localhost CRON[355]: (root) CMD (python /root/.xDripAPS/xDripAPS.py)
Jun 7 17:41:47 localhost CRON[356]: (root) CMD (reset_spi_serial.py)
Jun 7 17:41:47 localhost CRON[357]: (root) CMD (cd /root/APS && oref0-delete-future-entries)
Jun 7 17:41:47 localhost systemd[1]: Started D-Bus System Message Bus.
Jun 7 17:41:47 localhost avahi-daemon[334]: Successfully called chroot().
Jun 7 17:41:47 localhost avahi-daemon[334]: Successfully dropped remaining capabilities.
Jun 7 17:41:47 localhost avahi-daemon[334]: No service file found in /etc/avahi/services.
Jun 7 17:41:47 localhost avahi-daemon[334]: Joining mDNS multicast group on interface usb0.IPv4 with address 192.168.2.15.
Jun 7 17:41:47 localhost kernel: [ 47.145083] EXT4-fs (mmcblk0p5): warning: mounting unchecked fs, running e2fsck is recommended
Jun 7 17:41:47 localhost kernel: [ 47.146054] EXT4-fs (mmcblk0p5): mounted filesystem without journal. Opts: (null)
Jun 7 17:41:47 localhost avahi-daemon[334]: New relevant interface usb0.IPv4 for mDNS.
Jun 7 17:41:47 localhost avahi-daemon[334]: Network interface enumeration completed.
Jun 7 17:41:47 localhost avahi-daemon[334]: Registering new address record for 192.168.2.15 on usb0.IPv4.
Jun 7 17:41:47 localhost avahi-daemon[334]: Registering HINFO record with values 'I686'/'LINUX'.
Jun 7 17:41:47 localhost systemd[1]: Started Avahi mDNS/DNS-SD Stack.
Jun 7 17:41:47 localhost systemd[1]: Starting Login Service...
Jun 7 17:41:47 localhost systemd[1]: Starting LSB: Start busybox udhcpd at boot time...
Jun 7 17:41:47 localhost CRON[339]: (CRON) info (No MTA installed, discarding output)
Jun 7 17:41:47 localhost systemd[1]: Starting LSB: Advanced IEEE 802.11 management daemon...
Jun 7 17:41:47 localhost systemd[1]: Starting LSB: Start NTP daemon...
Jun 7 17:41:47 localhost systemd[1]: Starting ACPI event daemon...
Jun 7 17:41:47 localhost systemd[1]: Started ACPI event daemon.
Jun 7 17:41:47 localhost systemd[1]: Starting LSB: Run /etc/init.d/galileod.sh if it exist...
Jun 7 17:41:47 localhost udhcpd[376]: Starting very small Busybox based DHCP server: udhcpd.
Jun 7 17:41:47 localhost udhcpd[390]: udhcpd (v1.22.1) started
Jun 7 17:41:47 localhost acpid: starting up with netlink and the input layer
Jun 7 17:41:47 localhost acpid: 1 rule loaded
Jun 7 17:41:47 localhost acpid: waiting for events: event logging is off
Jun 7 17:41:47 localhost galileod.sh[387]: Starting galileod
Jun 7 17:41:47 localhost systemd[1]: Started System Logging Service.
Jun 7 17:41:47 localhost systemd[1]: Started remote_syslog2.
Jun 7 17:41:47 localhost ntpd[393]: ntpd 4.2.6p5@1.2349-o Fri Jul 22 17:48:00 UTC 2016 (1)
Jun 7 17:41:47 localhost ntp[379]: Starting NTP server: ntpd.
Jun 7 17:41:47 localhost systemd[1]: Started Permit User Sessions.
Jun 7 17:41:47 localhost ntpd[408]: proto: precision = 2.333 usec
Jun 7 17:41:48 localhost ntpd[408]: Listen and drop on 0 v4wildcard 0.0.0.0 UDP 123
Jun 7 17:41:48 localhost ntpd[408]: Listen and drop on 1 v6wildcard :: UDP 123
Jun 7 17:41:48 localhost ntpd[408]: Listen normally on 2 lo 127.0.0.1 UDP 123
Jun 7 17:41:48 localhost ntpd[408]: Listen normally on 3 usb0 192.168.2.15 UDP 123
Jun 7 17:41:48 localhost ntpd[408]: Listen normally on 4 lo ::1 UDP 123
Jun 7 17:41:48 localhost ntpd[408]: peers refreshed
Jun 7 17:41:48 localhost ntpd[408]: Listening on routing socket on fd #21 for interface updates
Jun 7 17:41:48 localhost systemd[1]: Started LSB: Start busybox udhcpd at boot time.
Jun 7 17:41:48 localhost systemd[1]: Started LSB: Advanced IEEE 802.11 management daemon.
Jun 7 17:41:48 localhost systemd[1]: Started LSB: Start NTP daemon.
Jun 7 17:41:48 localhost systemd[1]: Started LSB: Run /etc/init.d/galileod.sh if it exist.
Jun 7 17:41:48 localhost libmraa[360]: libmraa version v1.6.1 initialised by user 'root' with EUID 0
Jun 7 17:41:48 localhost libmraa[360]: gpio214: init: Failed to write to 'export': No such device
Jun 7 17:41:48 localhost libmraa[360]: edison: Arduin
Jun 7 17:41:47 localhost CRON[355]: (root) CMD (python /root/.xDripAPS/xDripAPS.py)
Jun 7 17:41:47 localhost CRON[356]: (root) CMD (reset_spi_serial.py)
Jun 7 17:41:47 localhost CRON[357]: (root) CMD (cd /root/APS && oref0-delete-future-entries)
Jun 7 17:41:47 localhost systemd[1]: Started D-Bus System Message Bus.
Jun 7 17:41:47 localhost avahi-daemon[334]: Successfully called chroot().
Jun 7 17:41:47 localhost avahi-daemon[334]: Successfully dropped remaining capabilities.
Jun 7 17:41:47 localhost avahi-daemon[334]: No service file found in /etc/avahi/services.
Jun 7 17:41:47 localhost avahi-daemon[334]: Joining mDNS multicast group on interface usb0.IPv4 with address 192.168.2.15.
Jun 7 17:41:47 localhost kernel: [ 47.145083] EXT4-fs (mmcblk0p5): warning: mounting unchecked fs, running e2fsck is recommended
Jun 7 17:41:47 localhost kernel: [ 47.146054] EXT4-fs (mmcblk0p5): mounted filesystem without journal. Opts: (null)
Jun 7 17:41:47 localhost avahi-daemon[334]: New relevant interface usb0.IPv4 for mDNS.
Jun 7 17:41:47 localhost avahi-daemon[334]: Network interface enumeration completed.
Jun 7 17:41:47 localhost avahi-daemon[334]: Registering new address record for 192.168.2.15 on usb0.IPv4.
Jun 7 17:41:47 localhost avahi-daemon[334]: Registering HINFO record with values 'I686'/'LINUX'.
Jun 7 17:41:47 localhost systemd[1]: Started Avahi mDNS/DNS-SD Stack.
Jun 7 17:41:47 localhost systemd[1]: Starting Login Service...
Jun 7 17:41:47 localhost systemd[1]: Starting LSB: Start busybox udhcpd at boot time...
Jun 7 17:41:47 localhost CRON[339]: (CRON) info (No MTA installed, discarding output)
Jun 7 17:41:47 localhost systemd[1]: Starting LSB: Advanced IEEE 802.11 management daemon...
Jun 7 17:41:47 localhost systemd[1]: Starting LSB: Start NTP daemon...
Jun 7 17:41:47 localhost systemd[1]: Starting ACPI event daemon...
Jun 7 17:41:47 localhost systemd[1]: Started ACPI event daemon.
Jun 7 17:41:47 localhost systemd[1]: Starting LSB: Run /etc/init.d/galileod.sh if it exist...
Jun 7 17:41:47 localhost udhcpd[376]: Starting very small Busybox based DHCP server: udhcpd.
Jun 7 17:41:47 localhost udhcpd[390]: udhcpd (v1.22.1) started
Jun 7 17:41:47 localhost acpid: starting up with netlink and the input layer
Jun 7 17:41:47 localhost acpid: 1 rule loaded
Jun 7 17:41:47 localhost acpid: waiting for events: event logging is off
Jun 7 17:41:47 localhost galileod.sh[387]: Starting galileod
Jun 7 17:41:47 localhost systemd[1]: Started System Logging Service.
Jun 7 17:41:47 localhost systemd[1]: Started remote_syslog2.
Jun 7 17:41:47 localhost ntpd[393]: ntpd 4.2.6p5@1.2349-o Fri Jul 22 17:48:00 UTC 2016 (1)
Jun 7 17:41:47 localhost ntp[379]: Starting NTP server: ntpd.
Jun 7 17:41:47 localhost systemd[1]: Started Permit User Sessions.
Jun 7 17:41:47 localhost ntpd[408]: proto: precision = 2.333 usec
Jun 7 17:41:48 localhost ntpd[408]: Listen and drop on 0 v4wildcard 0.0.0.0 UDP 123
Jun 7 17:41:48 localhost ntpd[408]: Listen and drop on 1 v6wildcard :: UDP 123
Jun 7 17:41:48 localhost ntpd[408]: Listen normally on 2 lo 127.0.0.1 UDP 123
Jun 7 17:41:48 localhost ntpd[408]: Listen normally on 3 usb0 192.168.2.15 UDP 123
Jun 7 17:41:48 localhost ntpd[408]: Listen normally on 4 lo ::1 UDP 123
Jun 7 17:41:48 localhost ntpd[408]: peers refreshed
Jun 7 17:41:48 localhost ntpd[408]: Listening on routing socket on fd #21 for interface updates
Jun 7 17:41:48 localhost systemd[1]: Started LSB: Start busybox udhcpd at boot time.
Jun 7 17:41:48 localhost systemd[1]: Started LSB: Advanced IEEE 802.11 management daemon.
Jun 7 17:41:48 localhost systemd[1]: Started LSB: Start NTP daemon.
Jun 7 17:41:48 localhost systemd[1]: Started LSB: Run /etc/init.d/galileod.sh if it exist.
Jun 7 17:41:48 localhost libmraa[360]: libmraa version v1.6.1 initialised by user 'root' with EUID 0
Jun 7 17:41:48 localhost libmraa[360]: gpio214: init: Failed to write to 'export': No such device
Jun 7 17:41:48 localhost libmraa[360]: edison: Arduin
Sorry, I couldnt get all of the log in the comment field, see APSsyslog.txt above :)
Seems like since carbsRequired is in place, you have the perfect hooks to later add glucagon support to oref2 or 3.
If anyone else is already in San Diego for D-Data / NS Hack / ADA SciSessions, we just arrived downtown and would be up for meeting up for dinner.
👍🏻👍🏻
@rsilvers129 we just did a PR that will remove the "run mmtune during oref0-setup" thing, as it causes radio errors for people who already have a pump-loop running in cron and don't delete and stop it first
Can the docs have a "radio test" command? I would do it, but I could not get it to work when I ran mmtune on its own, even stopping cron and killall. I think the port reset command has to be done. Maybe it could be done of the standard aliases. So radio_test SERIALNUM
openaps mmtune also does the radio reset
which mmtune command were you running?
I did /usr/local/bin/mmtune.py --port /dev/spidev5.1 —serial XXXXXX
openaps alias show mmtune
mmtune ! bash -c "oref0_init_pump_comms.py; find monitor/ -size +5c | grep -q mmtune && cp monitor/mmtune.json mmtune_old.json; echo {} > monitor/mmtune.json; echo -n \"mmtune: \" && openaps report invoke monitor/mmtune.json; grep -v setFreq monitor/mmtune.json | grep -A2 $(json -a setFreq -f monitor/mmtune.json) | while read line; do echo -n \"$line \"; done"