These are chat archives for nightscout/intend-to-bolus

19th
Jul 2017
tepidjuice
@tepidjuice
Jul 19 2017 00:04
@colinlennon It seems I just needed to wait while it cleared out the back log of cgm data :) Looks like it might be working now.
katie disimone
@Kdisimone
Jul 19 2017 00:09
Yes
@dirkgastaldo
Dirk Gastaldo
@dirkgastaldo
Jul 19 2017 00:11
@Kdisimone I deleted the blank/placeholder network lines in my wpa_supplicant file (I had ssid="" and we changed to ssid="abc"), and as soon as I saved the changes the rig popped onto my work WiFi.
katie disimone
@Kdisimone
Jul 19 2017 00:12
Good to hear. I wondered it that would be it
Dirk Gastaldo
@dirkgastaldo
Jul 19 2017 00:17
But obviously other people are doing it because it's in the docs as a suggestion. I wonder why those lines shut my rigs down?
Scott Leibrand
@scottleibrand
Jul 19 2017 00:18
please PR in a fix to the docs to use abc or something safer as a placeholder
Dirk Gastaldo
@dirkgastaldo
Jul 19 2017 00:18
I will put a PR in...
I had both "" and "abc" and both disabled my wifi
maybe having ssid and psk both the same is bad
or caused the problem
Scott Leibrand
@scottleibrand
Jul 19 2017 00:19
no, that should be fine
I could see a null ssid being an issue
or a null psk
or possibly (but less likely) two networks with the same ssid
Dirk Gastaldo
@dirkgastaldo
Jul 19 2017 00:19
okay, for my rigs, "abc" also caused wifi not to function
ohhhh, right
Scott Leibrand
@scottleibrand
Jul 19 2017 00:20
did you note what the wpa_supplicant error was in syslog?
was it anything specific, or just a generic error about not being able to load the config?
Dirk Gastaldo
@dirkgastaldo
Jul 19 2017 00:20
no, sorry, i could search for it, in my normal pump log?
Scott Leibrand
@scottleibrand
Jul 19 2017 00:20
no, in /var/log/syslog probably
search that for wpa_supplicant
Dirk Gastaldo
@dirkgastaldo
Jul 19 2017 00:21
will do
katie disimone
@Kdisimone
Jul 19 2017 00:26
@dirkgastaldo the docs don't say to leave those values blank. The docs say to put in placeholders. Look at the screenshot example...they aren't blank. I've been running mine like this for a long time without issue
If you think the wording is confusing, we could change that...but they aren't empty in the screenshot
Dirk Gastaldo
@dirkgastaldo
Jul 19 2017 00:31
@Kdisimone yes, I know. I changed the nulls to "abc" and my rigs would not attempt to connect to wifi
I didn't mean to infer the docs said to make them null. I put text in the "" ("abc") and it would not connect. That's what I'm referring to. Not the nulls.
If you think it's clear I definitely won't PR it.
katie disimone
@Kdisimone
Jul 19 2017 00:42
@dirkgastaldo I thought you said it did connect?
Oh you mean after you deleted them.
Dirk Gastaldo
@dirkgastaldo
Jul 19 2017 00:43
yes, it did, once I deleted the ssid="abc" lines
katie disimone
@Kdisimone
Jul 19 2017 00:43
Had you tried rebooting after changing it to abc?
I haven't had any problems running it with them as shown in screenshot
Dirk Gastaldo
@dirkgastaldo
Jul 19 2017 00:43
sorry, don't follow that question
katie disimone
@Kdisimone
Jul 19 2017 00:44
After you changed all of you "" to instead have "abc", did you save the changes and reboot the rig?
Dirk Gastaldo
@dirkgastaldo
Jul 19 2017 00:44
yes...
after I changed to "abc", saved changes and rebooted, I could not connect to wifi
but now I don't recall if "" also caused me to not connect. I'll do a little more testing tonight.
francesc0-cgm
@francesc0-cgm
Jul 19 2017 01:09
0
Sebastien Lussier
@SebastienLussier
Jul 19 2017 02:03
Hello! I'm trying to understand why the purple prediction dots are always off initially when we do a meal bolus... The first iteration of pump-loop looks like this:
Jul 17 09:16:11 pump-loop.log: {"carbs":0,"boluses":0,"mealCOB":0,"currentDeviation":-3.58,"maxDeviation":0,"minDeviationSlope":0} Jul 17 09:16:11 pump-loop.log: {"iob":2.229,"activity":0.0031,"bolussnooze":2.088,"basaliob":0.134,"netbasalinsulin":0.25,"hightempinsulin":0.45,"microBolusInsulin":0,"microBolusIOB":0,"time":"2017-07-17T13:15:12.000Z","lastBolusTime":1500297044000} Jul 17 09:16:11 pump-loop.log: {"delta":-4,"glucose":100,"short_avgdelta":-3.89,"long_avgdelta":-2.97} Jul 17 09:16:11 pump-loop.log: {"duration":26,"rate":0.15,"temp":"absolute"} Jul 17 09:16:11 pump-loop.log: Autosens adjusting basal from 0.35 to 0.4; Temp Target set, not adjusting with autosens; sens from 173.6 to 162.2 (autosens ratio 1.07) Jul 17 09:16:11 pump-loop.log: min_bg unchanged: 80; target_bg unchanged: 80; max_bg unchanged: 80 Jul 17 09:16:11 pump-loop.log: Carb Impact: -1.5 mg/dL per 5m; CI Duration: 0 hours; remaining 4h+ CI: 0 mg/dL per 5m Jul 17 09:16:11 pump-loop.log: Accel. Carb Impact: 10 mg/dL per 5m; ACI Duration: 0 hours Jul 17 09:16:11 pump-loop.log: UAM Impact: -1.4 mg/dL per 5m; UAM Duration: 0 hours Jul 17 09:16:11 pump-loop.log: minPredBG: -262 minIOBPredBG: 39 avgPredBG: -262 COB: 0 carbs: 0 Jul 17 09:16:11 pump-loop.log: BG projected to remain above 80 for 25 minutes Jul 17 09:16:11 pump-loop.log: bgUndershoot: 41 zeroTempDuration: 30 zeroTempEffect: 29 carbsReq: 2 Jul 17 09:16:12 pump-loop.log: determine-basal://text/shell/enact/suggested.json Jul 17 09:16:12 pump-loop.log: reporting enact/suggested.json Jul 17 09:16:12 pump-loop.log: {"temp":"absolute","bg":100,"tick":-4,"eventualBG":-270,"snoozeBG":238,"insulinReq":0,"reservoir":null,"deliverAt":"2017-07-17T13:16:11.502Z","minPredBG":999,"predBGs":{"IOB":[100,96,92,86,81,74,67,60,52,44,39,39,39]},"COB":0,"IOB":2.229,"reason":"COB: 0, Dev: -8, BGI: -2.51, ISF: 9.0, Target: 4.4, minPredBG -14.6, IOBpredBG 2.2; 2 add'l carbs req + 25m zero temp; Eventual BG -15.0 < 4.4, bolus snooze: eventual BG range -15.0-13.2; setting current basal of 0.4 as temp. ","carbsReq":2,"duration":30,"rate":0.4}
Hmm sorry let me try that again
Jul 17 09:16:11 pump-loop.log: {"carbs":0,"boluses":0,"mealCOB":0,"currentDeviation":-3.58,"maxDeviation":0,"minDeviationSlope":0}
Jul 17 09:16:11 pump-loop.log: {"iob":2.229,"activity":0.0031,"bolussnooze":2.088,"basaliob":0.134,"netbasalinsulin":0.25,"hightempinsulin":0.45,"microBolusInsulin":0,"microBolusIOB":0,"time":"2017-07-17T13:15:12.000Z","lastBolusTime":1500297044000}
Jul 17 09:16:11 pump-loop.log: {"delta":-4,"glucose":100,"short_avgdelta":-3.89,"long_avgdelta":-2.97}
Jul 17 09:16:11 pump-loop.log: {"duration":26,"rate":0.15,"temp":"absolute"}
Jul 17 09:16:11 pump-loop.log: Autosens adjusting basal from 0.35 to 0.4; Temp Target set, not adjusting with autosens; sens from 173.6 to 162.2 (autosens ratio 1.07)
Jul 17 09:16:11 pump-loop.log: min_bg unchanged: 80; target_bg unchanged: 80; max_bg unchanged: 80
Jul 17 09:16:11 pump-loop.log: Carb Impact: -1.5 mg/dL per 5m; CI Duration: 0 hours; remaining 4h+ CI: 0 mg/dL per 5m
Jul 17 09:16:11 pump-loop.log: Accel. Carb Impact: 10 mg/dL per 5m; ACI Duration: 0 hours
Jul 17 09:16:11 pump-loop.log: UAM Impact: -1.4 mg/dL per 5m; UAM Duration: 0 hours
Jul 17 09:16:11 pump-loop.log: minPredBG: -262 minIOBPredBG: 39 avgPredBG: -262 COB: 0 carbs: 0
Jul 17 09:16:11 pump-loop.log: BG projected to remain above 80 for 25 minutes
Jul 17 09:16:11 pump-loop.log: bgUndershoot: 41 zeroTempDuration: 30 zeroTempEffect: 29 carbsReq: 2
Jul 17 09:16:12 pump-loop.log: determine-basal://text/shell/enact/suggested.json
Jul 17 09:16:12 pump-loop.log: reporting enact/suggested.json
Jul 17 09:16:12 pump-loop.log: {"temp":"absolute","bg":100,"tick":-4,"eventualBG":-270,"snoozeBG":238,"insulinReq":0,"reservoir":null,"deliverAt":"2017-07-17T13:16:11.502Z","minPredBG":999,"predBGs":{"IOB":[100,96,92,86,81,74,67,60,52,44,39,39,39]},"COB":0,"IOB":2.229,"reason":"COB: 0, Dev: -8, BGI: -2.51, ISF: 9.0, Target: 4.4, minPredBG -14.6, IOBpredBG 2.2; 2 add'l carbs req + 25m zero temp; Eventual BG -15.0 < 4.4, bolus snooze: eventual BG range -15.0-13.2; setting current basal of 0.4 as temp. ","carbsReq":2,"duration":30,"rate":0.4}
Carbs are missing, but the bolus IOB appears
Carbs do show up on the next iteration
Jul 17 09:20:48 diabetor pump-loop.log: {"carbs":48,"boluses":2.1,"mealCOB":48,"currentDeviation":-0.77,"maxDeviation":0,"minDeviationSlope":0}
Jul 17 09:20:48 diabetor pump-loop.log: {"iob":2.21,"activity":0.004,"bolussnooze":2.061,"basaliob":0.123,"netbasalinsulin":0.25,"hightempinsulin":0.45,"microBolusInsulin":0,"microBolusIOB":0,"time":"2017-07-17T13:19:42.000Z","lastBolusTime":1500297044000}
Dana Lewis
@danamlewis
Jul 19 2017 02:04
where do you enter carbs? pump, or NS?
Sebastien Lussier
@SebastienLussier
Jul 19 2017 02:04
Always using the pump bolus wizard
katie disimone
@Kdisimone
Jul 19 2017 02:20

@SebastienLussier this page has some tips on how to format long copy paste into Gitter.

http://openaps.readthedocs.io/en/latest/docs/Understanding%20OpenAPS-Overview/communication-support-channels.html#gitter

Sebastien Lussier
@SebastienLussier
Jul 19 2017 02:23
great!
thanks @Kdisimone :smile:
katie disimone
@Kdisimone
Jul 19 2017 02:24
🤣😜
Michael Spradling
@M1Sports20
Jul 19 2017 02:30
I was at work when having issues that I described earlier so I just did a quick reinstall of myopenaps dir. It started working fine for another 6 or so hours. Now its back to not tracking my bolus wizard entries. I have time to look at this now
Michael Spradling
@M1Sports20
Jul 19 2017 02:35
Not related, but this is new "Edison battery level not found. Pumphistory-24 < 20m old" battery levels use to report
Katie Aldridge
@kcrcgm
Jul 19 2017 02:58
How does one turn off Autotune if it's already set up to run nightly?
Steve Lund
@902Lund
Jul 19 2017 03:01
Hi All, I've been struggling a bit with my new rig. I managed to get it flashed with Jubilinux. Then used the instructions at the following link -http://openaps.readthedocs.io/en/dev/docs/Build%20Your%20Rig/OpenAPS-install.html - after running the script the first time, it identified my wifi network and I proceeded to enter my wifi name and password...I then got the following text at which point I'm wondering if the script failed so I tried to rerun it but, now it doesn't seem to find my wifi network at all. Hoping someone can point me in the right direction as to what steps to follow next.

Sorry - here is the text I got after running the script and entering my wifi and password. /etc/network/interfaces:

auto lo
iface lo inet loopback

auto usb0
iface usb0 inet static
address 10.11.12.13
netmask 255.255.255.0

auto wlan0
iface wlan0 inet dhcp
wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf

/etc/wpa_supplicant/wpa_supplicant.conf:

ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev
update_config=1
network={
ssid="Weenus"
psk="xxxxxxxxxxxxxxx"
}

Attempting to bring up wlan0:

Killed old client process
Internet Systems Consortium DHCP Client 4.3.1
Copyright 2004-2014 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

Listening on LPF/wlan0/90:b6:86:08:4d:6f
Sending on LPF/wlan0/90:b6:86:08:4d:6f
Sending on Socket/fallback
Internet Systems Consortium DHCP Client 4.3.1
Copyright 2004-2014 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

Listening on LPF/wlan0/90:b6:86:08:4d:6f
Sending on LPF/wlan0/90:b6:86:08:4d:6f
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5
No DHCPOFFERS received.
No working leases in persistent database - sleeping.

Wifi SSID: root@jubilinux:~#

Michael Spradling
@M1Sports20
Jul 19 2017 03:16
just curious what does iwconfig show?
Michael Spradling
@M1Sports20
Jul 19 2017 03:21
@902Lund What does dhclient wlan0 show on the command line?
Katie Aldridge
@kcrcgm
Jul 19 2017 03:25
@scottleibrand I ran tail -f ~/myopenaps/monitor/glucose.json and tail -f ~/myopenaps/xdrip/json. There's nothing in my xdrip/glucose file (it says [ ]) because I don't have my phone bt tethered to the rig. And my monitor/glucose file is running and not being truncated. So that's a win win, right? ;) Thank you again.
Michael Spradling
@M1Sports20
Jul 19 2017 03:31
When my setup is broken it appears my monitor/meal.json file is always an empty file. I believe this is where my bolus from the bolus wizard should be entered correct?
Steve Lund
@902Lund
Jul 19 2017 03:31
@M1Sports20 I'm re-flashing now and will run the script again in just a few minutes. I'll share more info as soon as I try it again. Thanks!
Scott Leibrand
@scottleibrand
Jul 19 2017 03:48
@M1Sports20 have you tried running the report manually yet?
Michael Spradling
@M1Sports20
Jul 19 2017 03:48
@scottleibrand as in oref0-report? I haven't, I don't know how to do that
Scott Leibrand
@scottleibrand
Jul 19 2017 03:48
@kcrcgm sweet! I think we licked it.
Search the docs for the drill down troubleshooting section.
Michael Spradling
@M1Sports20
Jul 19 2017 03:49
ok thanks
I noticed my uploaded-entries.json file has mongo error messages in it
I will look. I forget that section even existed. I will read it and get back
Steve Lund
@902Lund
Jul 19 2017 03:50

@M1Sports20 here is what iwconfig shows. And please forgive my ignorance...puTTy and all of this stuff is really new to me...I'm not sure what you mean by "What does dhclient wlan0 show on the command line?" .
root@jubilinux:~# iwconfig
wlan0 IEEE 802.11abgn ESSID:off/any
Mode:Managed Access Point: Not-Associated Tx-Power=31 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:on

sit0 no wireless extensions.

lo no wireless extensions.

usb0 no wireless extensions.

Michael Spradling
@M1Sports20
Jul 19 2017 03:54
@902Lund I was wondering if you were getting any tx or rx errors. But it looks like you are never connecting. I know these are going to sound like basic questions. Are you sure your ssid is correct? I believe they are case sensitive. Same with passphrase in psk setting
Steve Lund
@902Lund
Jul 19 2017 04:02
@M1Sports20 Basic is good for me with my limited experience. I'm really confident that both the SSID and passphrase are entered correctly. I copy/pasted the pass phrase directly from my computer network settings.
Dana Lewis
@danamlewis
Jul 19 2017 04:06
@902Lund if you want, you could try with your phone hotspot on for the initial setup, and go back and investigate home wifi later if that works to get it going
Michael Spradling
@M1Sports20
Jul 19 2017 04:07
@902Lund You could always trying bringing up wifi manually with "iwconfig wlan0 essid WifiAccessName key password"
after running that run just "iwconfig" You should see essid: not being off anymore.
This is my my one time debugging and won't fix the underlying problem with it autoconnecting. I am just seeing if you can get it to connect
Question on my issue. I always see a bunch of prints such as files stuff being to old such as "Profile less than 60m old" in logs. When running manual openaps commands I also see them. Is this normal
Steve Lund
@902Lund
Jul 19 2017 04:13
@danamlewis Thanks! This is working on my hotspot. @M1Sports20 Thanks as well! I'll try out your suggestion after I get setup to see if I can get it to connect to my home wifi.
Dana Lewis
@danamlewis
Jul 19 2017 04:15
@M1Sports20 yes that's normal to tell you that files are fresh enough to loop on
Michael Spradling
@M1Sports20
Jul 19 2017 04:17
openaps report invoke monitor/clock.json                                                                                                                                                                          ~/myopenaps  {2}
pump://JSON/read_clock/monitor/clock.json
monitor/clock.json  raised  No acknowledgement from pump on wakeup. Is it out of range or is the battery too low?
Traceback (most recent call last):
  File "/usr/local/bin/openaps-report", line 82, in <module>
    app( )
  File "/usr/local/lib/python2.7/dist-packages/openaps/cli/__init__.py", line 51, in __call__
    self.run(self.args)
  File "/usr/local/bin/openaps-report", line 75, in run
    output = app(args, self)
  File "/usr/local/lib/python2.7/dist-packages/openaps/cli/subcommand.py", line 52, in __call__
    return self.method.main(args, app)
  File "/usr/local/lib/python2.7/dist-packages/openaps/reports/invoke.py", line 40, in main
    output = task.method(args, app)
  File "/usr/local/lib/python2.7/dist-packages/openaps/uses/use.py", line 44, in __call__
    self.before_main(args, app)
  File "/usr/local/lib/python2.7/dist-packages/openaps/vendors/medtronic.py", line 64, in before_main
    self.check_session(app)
  File "/usr/local/lib/python2.7/dist-packages/openaps/vendors/medtronic.py", line 141, in check_session
    self.session = self.get_session_info( )
  File "/usr/local/lib/python2.7/dist-packages/openaps/vendors/medtronic.py", line 104, in get_session_info
    fields = self.create_session( )
  File "/usr/local/lib/python2.7/dist-packages/openaps/vendors/medtronic.py", line 129, in create_session
    self.pump.power_control(minutes=minutes)
  File "/usr/local/lib/python2.7/dist-packages/mmeowlink/handlers/stick.py", line 222, in power_control
    raise CommsException("No acknowledgement from pump on wakeup. Is it out of range or is the battery too low?")
mmeowlink.exceptions.CommsException: No acknowledgement from pump on wakeup. Is it out of range or is the battery too low?
Dana Lewis
@danamlewis
Jul 19 2017 04:17
Did you killall before you started drilling down
Michael Spradling
@M1Sports20
Jul 19 2017 04:17
The battery on my pump has two bars with no warnings
@danamlewis Yes, I did. I also commented out my crontab
ps also shows no openaps processes running
Pump and rig are about an inch apart
Dana Lewis
@danamlewis
Jul 19 2017 04:21
2 bars? Lithium? If so I'd go ahead and swap
Michael Spradling
@M1Sports20
Jul 19 2017 04:21
No its alkaline. I switched just to eliminate that variable
same error.
Dana Lewis
@danamlewis
Jul 19 2017 04:22
You switched to a 2 bar battery? I'd only switch to a fresh battery
Michael Spradling
@M1Sports20
Jul 19 2017 04:22
I guess I will reboot the rig. Maybe SPI bus with radio???
No I switched to a fresh battery and got the same error
Dana Lewis
@danamlewis
Jul 19 2017 04:23
Ah, gotcha
Michael Spradling
@M1Sports20
Jul 19 2017 04:23
2 bars was before the switch. Sorry if that was confusing
Even a reboot doesn't fix the problem. I do have another pump... Guess I could try that
Dana Lewis
@danamlewis
Jul 19 2017 04:26
So you are not looping currently? What do regular full logs say if so?
Michael Spradling
@M1Sports20
Jul 19 2017 04:28
I was looping, as in I had a temp basal(not anymore since I switch cron off)
Starting pump-loop at Tue Jul 18 23:54:24 EDT 2017:
Waiting up to 4 minutes for new BG: glucose.json newer than pump_loop_completed
Radio ok. Listening: .No pump comms detected from other rigs
Profile less than 60m old. glucose.json newer than temp_basal.json. Temp refreshed
{"carbs":47,"boluses":23.5,"mealCOB":9,"currentDeviation":17.32,"maxDeviation":20.23,"minDeviationSlope":-0.398}
{"iob":2.963,"activity":0.0276,"bolussnooze":1.658,"basaliob":-0.014,"netbasalinsulin":-0.55,"hightempinsulin":0.55,"microBolusInsulin":0,"microBolusIOB":0,"time":"2017-07-19T03:54:10.000Z","lastBolusTime":1500435493000}
{"delta":6,"glucose":155,"short_avgdelta":5.78,"long_avgdelta":5.53}
{"duration":17,"rate":1,"temp":"absolute"}
Basal unchanged: 1; target_bg unchanged: 90; sens unchanged: 41 (autosens ratio 1)
min_bg unchanged: 80; target_bg unchanged: 90; max_bg unchanged: 100
Carb Impact: 11.4 mg/dL per 5m; CI Duration: 0.5 hours; remaining 4h+ CI: 0 mg/dL per 5m
Accel. Carb Impact: 10 mg/dL per 5m; ACI Duration: 0.6 hours
UAM Impact: 11.2 mg/dL per 5m; UAM Duration: 2.3 hours
minPredBG: 75 minIOBPredBG: 91 minCOBPredBG: 59 avgPredBG: 75 COB: 9 carbs: 47
BG projected to remain above 80 for 105 minutes
bgUndershoot: -13 zeroTempDuration: 105 zeroTempEffect: 72 carbsReq: -30
determine-basal://text/shell/enact/suggested.json
reporting enact/suggested.json
{"temp":"absolute","bg":155,"tick":"+6","eventualBG":103,"snoozeBG":205,"insulinReq":0,"reservoir":null,"deliverAt":"2017-07-19T03:55:25.783Z","minPredBG":999,"predBGs":{"IOB":[155,160,164,167,168,169,169,168,166,163,158,153,147,141,136,131,126,122,119,115,112,109,106,103,101,99,97,95,94,93,92,91],"aCOB":[155,158,160,160,159,156,152,147,141,135,129,122,116,110,105,100,96,92,88,85,81,78,75,73,70,68,66,65,63,62,61,61,60],"COB":[155,159,161,162,160,157,152,146,140,134,128,122,116,110,104,99,95,91,87,84,81,78,75,72,70,68,66,64,63,61,61,60,60,59]},"COB":9,"IOB":2.963,"reason":"COB: 9, Dev: 69, BGI: -5.66, ISF: 41, Target: 90, minPredBG 75, IOBpredBG 91, COBpredBG 59; 103-75 in range: no temp required, temp 1 ~ req 1U/hr. "}
enact/enacted.json: {"insulinReq":0,"bg":139,"reservoir":null,"temp":"absolute","snoozeBG":205,"rate":1,"predBGs":{"IOB":[139,144,148,151,154,155,155,155,153,151,147,143,137,131,126,120,115,111,106,103,100,97,94,91,89,86,84,82,81,79,78,77,76,75,75,74]},"minPredBG":999,"IOB":3.018,"reason":"COB: 0, Dev: 71, BGI: -5.82, ISF: 41, Target: 90, minPredBG 74, IOBpredBG 74; 86-74 in range: no temp required; setting current basal of 1 as temp. . Setting neutral temp basal of 1U/hr","COB":0,"eventualBG":86,"recieved":true,"duration":30,"tick":"+6","timestamp":"2017-07-18T23:41:21.879150","deliverAt":"2017-07-19T03:41:16.440Z"}
glucose.json newer than pumphistory. : RefreshInterpolated [ date: 1500432788527, glucose: 90 ]
ed pumphistory
{"carbs":47,"boluses":23.5,"mealCOB":9,"currentDeviation":12.98,"maxDeviation":17,"minDeviationSlope":-0.762}
{"iob":2.558,"activity":0.0271,"bolussnooze":1.649,"basaliob":-0.408,"netbasalinsulin":-0.95,"hightempinsulin":0.15,"microBolusInsulin":0,"microBolusIOB":0,"time":"2017-07-19T03:54:29.000Z","lastBolusTime":1500435493000}
{"delta":6,"glucose":155,"short_avgdelta":5.78,"long_avgdelta":5.53}
{"duration":17,"rate":1,"temp":"absolute"}
Basal unchanged: 1; target_bg unchanged: 90; sens unchanged: 41 (autosens ratio 1)
min_bg unchanged: 80; target_bg unchanged: 90; max_bg unchanged: 100
Carb Impact: 11.3 mg/dL per 5m; CI Duration: 0.5 hours; remaining 4h+ CI: 0 mg/dL per 5m
Accel. Carb Impact: 10 mg/dL per 5m; ACI Duration: 0.6 hours
UAM Impact: 11.1 mg/dL per 5m; UAM Duration: 1.3 hours
minPredBG: 91 minIOBPredBG: 107 minCOBPredBG: 76 avgPredBG: 91 COB: 9 carbs: 47
BG projected to remain above 80 for 135 minutes
bgUndershoot: -28 zeroTempDuration: 135 zeroTempEffect: 92 carbsReq: -38
determine-basal://text/shell/enact/suggested.json
reporting enact/suggested.json
{"temp":"absolute","bg":155,"tick":"+6","eventualBG":118,"snoozeBG":219,"insulinReq":0,"reservoir":null,"deliverAt":"2017-07-19T03:56:10.336Z","minPredBG":999,"predBGs":{"IOB":[155,
Dana Lewis
@danamlewis
Jul 19 2017 04:30
Ah, gotcha - sorry, unclear what's being troubleshooted then
Seeing now back through history
Michael Spradling
@M1Sports20
Jul 19 2017 04:31
When I was looping. I was getting temp basals. However, Bolus wizard inputs don't seem to be taking effect. For example, I don't see IOB go up when I perform a bolus wizard entry.
Just to be clear "openaps report invoke monitor/clock.json" should always work? (assuming no other openaps process is running and using the rf radio) Guessing it just returns the clock...
Steve Lund
@902Lund
Jul 19 2017 04:33
Hi guys - I have a question about NA and WW pumps. In the setup guide ( http://openaps.readthedocs.io/en/dev/docs/Build%20Your%20Rig/OpenAPS-install.html ), it says that WW pumps have a WW in the serial number and non-USA pumps have NA in the serial number. My pump is a MMT-522LCAS (Canadian pump) and doesn't have WW or NA in the serial number at all. Does anyone know if Canadian pumps are NA or WW?
Michael Spradling
@M1Sports20
Jul 19 2017 04:37
@902Lund: Unless someone else chimes in(I am not an expert in this area). I would just run with NA first. You can always rerun the setup scripts and choose WW if needed.
Steve Lund
@902Lund
Jul 19 2017 04:39
@M1Sports20 Cool will give it a try. Thanks!
Michael Spradling
@M1Sports20
Jul 19 2017 04:47
@danamlewis So it seems any "openaps use pump <command>" works. However, the openaps report invoke commands do not
sorry, i know I am jumping around a lot. I am just debugging while also trying to learn whats going on at the same time. So I may be telling you stuff that doesn't matter
Well I take that back. sometimes it does have errors. I think I have a radio issue
This run was interesting:
```
root@mds_openaps# openaps use pump suspend_pump ~/myopenaps {0}
^[[ATraceback (most recent call last):
File "/usr/local/bin/openaps-use", line 63, in <module>
app( )
File "/usr/local/lib/python2.7/dist-packages/openaps/cli/init.py", line 51, in call
self.run(self.args)
File "/usr/local/bin/openaps-use", line 57, in run
output = app(args, self)
File "/usr/local/lib/python2.7/dist-packages/openaps/uses/init.py", line 92, in call
return self.method.selected(args)(args, app)
File "/usr/local/lib/python2.7/dist-packages/openaps/uses/init.py", line 31, in call
return self.method(args, app)
File "/usr/local/lib/python2.7/dist-packages/openaps/uses/use.py", line 45, in call
output = self.main(args, app)
File "/usr/local/lib/python2.7/dist-packages/openaps/vendors/medtronic.py", line 382, in main
result = super(suspend_pump, self).main(args, app)
File "/usr/local/lib/python2.7/dist-packages/openaps/vendors/medtronic.py", line 334, in main
return getattr(self.pump.model, name)(**self.get_params(args))
File "/usr/local/lib/python2.7/dist-packages/decocare/models/init.py", line 26, in call
self.validate( )
File "/usr/local/lib/python2.7/dist-packages/decocare/models/init.py", line 17, in validate
data = self.response.getData( )
File "/usr/local/lib/python2.7/dist-packages/decocare/commands.py", line 310, in getData
received = True if self.data[0] is 0 else False
IndexError: bytearray index out of range
Michael Spradling
@M1Sports20
Jul 19 2017 04:52
The command was succesful, but it looks like the verify suspend failed. "My pump actually did suspend
hmm, now everythng is working again....
Sorry, I am so verbose. Thanks for helping me debug. I guess maybe mmtune or making sure I clearly cut the trace
Dana Lewis
@danamlewis
Jul 19 2017 04:58
Yea, if you suspect radio errors I'd watch your mmtune and see if you're getting reasonable results there first
LilDucky
@LilDucky
Jul 19 2017 05:01
@PieterGit still the same issue.
Michael Spradling
@M1Sports20
Jul 19 2017 05:04

@danamlewis

root@mds_openaps# openaps mmtune                                                                                                                                                                                                    ~/myopenaps  {0}
mmtune: pump://JSON/mmtune/monitor/mmtune.json
reporting monitor/mmtune.json
"916.636", 0, -99 #

:worried:

Michael Spradling
@M1Sports20
Jul 19 2017 05:09
"916.588", 1, -86. Seems to go in and out.
Michael Spradling
@M1Sports20
Jul 19 2017 05:19
Switched from my 515 to a 523. Much better readings
"916.684", 5, -38
thank you. Kindof said my 515 isn't working the best
francesc0-cgm
@francesc0-cgm
Jul 19 2017 05:51
Jul 19 07:50:53 edisonhost pump-loop.log: Temp refresh at Module.load (module.js:356:32)
Jul 19 07:50:53 edisonhost pump-loop.log: ed
Jul 19 07:50:57 edisonhost pump-loop.log: Could not parse input data: [SyntaxError: /root/myopenaps/monitor/iob.json: Unexpected end of input]
Still having this issue
Oref0 seems crashed. No succesfull loop
francesc0-cgm
@francesc0-cgm
Jul 19 2017 06:12
Solved rerunning oref0 setup
Don't know if there is an easier and quicker method
But it seems quite annoying. If i leave my son with grandparents or his mother it will be a big problem if it might happen again
Michael Spradling
@M1Sports20
Jul 19 2017 06:21
Kindof a dumb question. How can I tell my pump about insulin that is in my body that was never entered through the pump interface. For example here I gave myself a bolus then switched to a different pump.
To rephrase. I want to add IOB that wasn't done from the pump currently looping? Is this even possible with openaps.
PieterGit
@PieterGit
Jul 19 2017 07:14
@M1Sports20 The Nightscout Careportal has several Boluses, such as Snack bolus, Meal bolus and Correction bolus. You need to use dev branch, because that will use that that in your openaps loops, see openaps/oref0@207e59d
LilDucky
@LilDucky
Jul 19 2017 07:15
@PieterGit no luck with your suggestions
LilDucky
@LilDucky
Jul 19 2017 07:21
@PieterGit cleaned it up - thanks for the pointer on how to format.
PieterGit
@PieterGit
Jul 19 2017 07:21
@LilDucky : please comment both out and retry, just like I suggested. Now that I'm awake I realize that the 2>/dev/null probably hides the output for reset_spi_serial.py
LilDucky
@LilDucky
Jul 19 2017 07:23
have done that and still getting import error and waiting with ad-nauseum dots
editing /usr/local/bin/oref0-pump-loop. added a custom comment and it shows in logs to confirm I am attacking correct code
PieterGit
@PieterGit
Jul 19 2017 07:25
the error is really coming from an python import . the only instances I can find is https://github.com/openaps/oref0/blob/master/bin/oref0-pump-loop.sh#L319-L320
LilDucky
@LilDucky
Jul 19 2017 07:26
yep, those 2 lines are commented out and my custom comment was in the next echo line
PieterGit
@PieterGit
Jul 19 2017 07:27
the import error is caused by a import spi_serial. Since you don't have the spi_serial module (and don't need to), you get the error
LilDucky
@LilDucky
Jul 19 2017 07:27
makes sense.
just did the killall and cleared the log. def both lines commented out
and still doing it
tepidjuice
@tepidjuice
Jul 19 2017 07:30
@colinlennon @tim2000s yes it's definitely working now. I think there was something wrong with the installation of flask. The lesson... if somethings's wrong go nuclear :)
PieterGit
@PieterGit
Jul 19 2017 07:32
@lilducky can you post an example (i don't mind the custom comment)
LilDucky
@LilDucky
Jul 19 2017 07:33
Starting pump-loop at Wed 19 Jul 17:29:04 AEST 2017:
MDT CGM configured; not waiting
ImportError: No module named spi_serial
Listening for 30s silence before mmtuning: .................................................................

# reset radio, init world wide pump (if applicable), mmtune, and wait_for_silence 60 if no signal
function mmtune {
    # TODO: remove reset_spi_serial.py once oref0_init_pump_comms.py is fixed to do it correctly
#    reset_spi_serial.py 2>/dev/null
#    oref0_init_pump_comms.py
    echo -n "Listening for 30s silence before mmtuning: "
    for i in $(seq 1 800); do
       echo -n .
code from /usr/local/bin/oref0-pump-loop
I am learning...
sans the sarcastic comment
PieterGit
@PieterGit
Jul 19 2017 07:38
if it's safe with your blood sugars. can you stop the loop /etc/init.d/cron stop and after the pumploop has ended issue a oref0-pump-loop from the command line
LilDucky
@LilDucky
Jul 19 2017 07:39
it is only a test rig - no CGM source yet
PieterGit
@PieterGit
Jul 19 2017 07:39
ok, even better.
LilDucky
@LilDucky
Jul 19 2017 07:39
and I am the geek not the T1D
although I will probs wear the rig for a few days with an enlite to make sure its safe, but loaded with saline only...
francesc0-cgm
@francesc0-cgm
Jul 19 2017 07:41
saline hurts just a bit...
LilDucky
@LilDucky
Jul 19 2017 07:41
@francesc0-cgm thanks for the heads up. maybe sterile water
PieterGit
@PieterGit
Jul 19 2017 07:41
even if your the geek, you should check if the T1D is ok if you're not using a test rig. Even with a test rig I always check if the T1D is ok and don't fiddle when the production rig is preventing a hypo
francesc0-cgm
@francesc0-cgm
Jul 19 2017 07:41
now it is ok :smile:
LilDucky
@LilDucky
Jul 19 2017 07:42
this is the alpha test - only on pump at the moment with CGM. awaiting edison and CGM transmitter
@francesc0-cgm Thanks
and we have a complete spare setup - he is using a 640G at the moment
francesc0-cgm
@francesc0-cgm
Jul 19 2017 07:43
yw
LilDucky
@LilDucky
Jul 19 2017 07:43
with a 754 for looping
skubesch
@skubesch
Jul 19 2017 07:43
Question about a new openaps setup. I'm using an Edison/Explorer rig, and the logs show decisions are being made and the logs, pump, and nightscout show temp basal rates being set. Oddly though, in my NS site OpenAPS says "unknown", Pump "Device undefined", and the openaps purple prediction lines (which are enabled in my heroku app settings) are not a checkable option. Any ideas on why that data isn't present in nightscout?
LilDucky
@LilDucky
Jul 19 2017 07:45
@PieterGit yes, ordered yesterday after we managed to source an older enlite transmitter
PieterGit
@PieterGit
Jul 19 2017 07:46
Does a oref0-pump-loop from the command line also show the erorr?
LilDucky
@LilDucky
Jul 19 2017 07:47
will run now
identical behaviour
PieterGit
@PieterGit
Jul 19 2017 07:55
@LilDucky Ok, i must stop for now. I hope I can spend some time working on "option 3" as mentioned in the issue. Because that would make the oref0 code much easier. You can safely ignore this error on the rpi2. You won't see this on the explorer board, because that has the spi_serial module installed.
can you update the issue, with the output (or create link to the gitter comment). Gitter is not good for searching and documenting.
LilDucky
@LilDucky
Jul 19 2017 08:00
will update comment. no stress as this is pre-production only. I dont know where I would be without all you gurus in here!
Christian Driver
@DriverNightscout
Jul 19 2017 08:32
What's the recommended way of entering carbs and insulin data when using OpenAPS? I just built a rig for my 12 year old, and she is just getting used to the Medtronic 722 we have obtained for looping (having previously been on a Accu-Chek Insight). She's used to using the bolus wizard built into her Insight. I had it in mind from reading it somewhere that using the wizard on the Medtronic isn't the recommended method of entering carbs and insulin, but I now can't find where I read that. I've tried searching here and couldn't find a definitive answer...
tepidjuice
@tepidjuice
Jul 19 2017 08:33
In my openaps logs I have "COB: undefined" and my eventual bgls are NaN.
francesc0-cgm
@francesc0-cgm
Jul 19 2017 09:05
@francesc0-cgm
yesteday i had a chat with @scottleibrand because cob decayed in a few minutes from 20 to 0...we thought it was a Timezone problem...i edited openaps.ini thanks to his advice. Today at breakfast it was even worse...it lost iob in a couple seconds...from 0.6 of iob to negative iob...seems it lost last bolus time from the log...it seems much more dangerous! here is the log:
it happened about 2.5 hours after the bolus (made at 08.22 am CEST)
'''
Jul 19 10:34:45 edisonhost pump-loop.log: {"iob":0.626,"activity":0.0124,"bolussnooze":0,"basaliob":-0.169,"netbasalinsulin":-0.25,"hightempinsulin":0.05,"microBolusInsulin":0,"microBolusIOB":0,"time":"2017-07-19T08:34:15.000Z","lastBolusTime":1500445991000}
Jul 19 10:34:46 edisonhost pump-loop.log: minPredBG: 70 minIOBPredBG: 73 minUAMPredBG: 66 avgPredBG: 72 COB: 0 carbs: 22
Jul 19 10:34:47 edisonhost pump-loop.log: enact/smb-suggested.json: {"insulinReq":0,"bg":133,"reservoir":"88.675","temp":"absolute","snoozeBG":93,"rate":0,"predBGs":{"UAM":[133,133,133,132,130,128,125,122,117,112,107,101,96,91,86,82,79,76,73,71,69,68,67,66,66,67,67,67,68,68,68,68,68,68,68,68,68,68,68,68,68,67],"IOB":[133,133,133,132,131,129,127,124,121,117,113,108,103,98,93,89,86,83,80,78,76,75,74,73,73,74,74,75]},"minPredBG":999,"IOB":0.626,"reason":"COB: 0, Dev: 73, BGI: -11.16, ISF: 180, Target: 105, minPredBG 70, IOBpredBG 75, UAMpredBG 67; Eventual BG 93 < 100, naive_eventualBG < 40. ","COB":0,"eventualBG":93,"duration":30,"tick":"+1","deliverAt":"2017-07-19T08:34:45.852Z"}
Jul 19 10:34:57 edisonhost pump-loop.log: enact/smb-enacted.json: {"insulinReq":0,"bg":133,"reservoir":"88.675","temp":"absolute","snoozeBG":93,"recieved":true,"predBGs":{"UAM":[133,133,133,132,130,128,125,122,117,112,107,101,96,91,86,82,79,76,73,71,69,68,67,66,66,67,67,67,68,68,68,68,68,68,68,68,68,68,68,68,68,67],"IOB":[133,133,133,132,131,129,127,124,121,117,113,108,103,98,93,89,86,83,80,78,76,75,74,73,73,74,74,75]},"minPredBG":999,"deliverAt":"2017-07-19T08:34:45.852Z","duration":30,"rate":0,"COB":0,"eventualBG":93,"timestamp":"2017-07-19T10:34:55.776304","reason":"COB: 0, Dev: 73, BGI: -11.16, ISF: 180, Target: 105, minPredBG 70, IOBpredBG 75, UAMpredBG 67; Eventual BG 93 < 100, naive_eventualBG < 40. ","tick":"+1","IOB":0.626}
Jul 19 10:36:00 edisonhost pump-loop.log: {"iob":-0.167,"activity":-0.0018,"bolussnooze":0,"basaliob":-0.167,"netbasalinsulin":-0.25,"hightempinsulin":0.05,"microBolusInsulin":0,"microBolusIOB":0,"time":"2017-07-19T08:35:30.000Z","lastBolusTime":0}
Jul 19 10:36:01 edisonhost pump-loop.log: minPredBG: 157 minIOBPredBG: 157 avgPredBG: 162 COB: 0 carbs: 22
Jul 19 10:36:04 edisonhost pump-loop.log: enact/smb-suggested.json: {"insulinReq":0.34,"bg":133,"reservoir":"88.65","temp":"absolute","snoozeBG":162,"rate":0.875,"predBGs":{"IOB":[133,134,135,137,138,139,141,142,144,145,147,148,150,151,153,154,155,156,157,158,159,159,160,160,161,161,162]},"minPredBG":157,"IOB":-0.167,"reason":"COB: 0, Dev: -1, BGI: 1.62, ISF: 180, Target: 96, minPredBG 157, IOBpredBG 162; Eventual BG 162 >= 102, temp 0<0.875U/hr. ","COB":0,"eventualBG":162,"duration":30,"tick":"+1","deliverAt":"2017-07-19T08:36:01.003Z"} Jul 19 10:36:14 edisonhost pump-loop.log: enact/smb-enacted.json: {"insulinReq":0.34,"bg":133,"reservoir":"88.65","temp":"absolute","snoozeBG":162,"recieved":true,"predBGs":{"IOB":[133,134,135,137,138,139,141,142,144,145,147,148,150,151,153,154,155,156,157,158,159,159,160,160,161,161,162]},"minPredBG":157,"deliverAt":"2017-07-19T08:36:01.003Z","duration":30,"rate":0.875,"COB":0,"eventualBG":162,"timestamp":"2017-07-19T10:36:13.708734","reason":"COB: 0, Dev: -1, BGI: 1.62, ISF: 180, Target: 96, minPredBG 157, IOBpredBG 162; Eventual BG 162 >= 102, temp 0<0.875U/hr. ","tick":"+1","IOB":-0.167}
Jul 19 10:39:53 edisonhost pump-loop.log: {"iob":-0.159,"activity":-0.0019,"bolussnooze":0,"basaliob":-0.159,"netbasalinsulin":-0.25,"hightempinsulin":0.05,"microBolusInsulin":0,"microBolusIOB":0,"time":"2017-07-19T08:39:22.000Z","lastBolusTime":0}
'''
francesc0-cgm
@francesc0-cgm
Jul 19 2017 09:40
i made the bolus from the bolus wizard of the pump and i have loop in open loop mode in background
Michael Spradling
@M1Sports20
Jul 19 2017 11:47
@PieterGit I tried the nightscout careportal before asking, but noticed openaps wasn't using it. Thanks for the patch. I may just pull that one in rather than the dev branch. I am new to the project and don't know much about it, but dev branch makes me unconfortable at the moment.
PieterGit
@PieterGit
Jul 19 2017 11:59
@M1Sports20 : it's good to use stable / master versions if your new to the project. In this case it doesn't really matter, because the patch is the first and only since 0.5.1, see https://github.com/openaps/oref0/commits/dev
Michael Spradling
@M1Sports20
Jul 19 2017 12:26
Thanks
cameronrenwick
@cameronrenwick
Jul 19 2017 14:03
has anyone dug into the mLab upgrade email that we all likely got? I haven't but am just wondering...
@DriverNightscout pump wizard is totally fine for carbs and bolus data. You can also enter carbs via NS/ifttt.
Scott Leibrand
@scottleibrand
Jul 19 2017 15:12
@M1Sports20 no, oref0 will only use boluses entered via the pump. As a workaround you can set a high temp target, or disconnect the tubing from the pump site and do an equivalent bolus and just let it drip out.
Dana Lewis
@danamlewis
Jul 19 2017 15:12
@M1Sports20 the only way to make it see a bolus is for the bolus to happen on the pump
So if you switch pump, do an air bolus before attaching the new one
Michael Spradling
@M1Sports20
Jul 19 2017 15:12
Thanks, so the patch pieter showed me will not do what I expect
Dana Lewis
@danamlewis
Jul 19 2017 15:13
Otherwise, the next pump history pull is going to write over any manual attempt to log insulin
Scott Leibrand
@scottleibrand
Jul 19 2017 15:15
@M1Sports20 @PieterGit that patch shouldn't change oref0's behavior for looping. It is only for autotune use, which pulls from NS.
@francesc0-cgm it sounds like you might be seeing similar behavior to what @jmcrawford and @JELCRAWFORD reported. Their boluses get lost after 2h, when they should be just transitioning from pumphistory.json to pumphistory-24h.json and should still end up in pumphistory-merge.json. We need someone to open an issue and do the drill down troubleshooting to figure out why that is occurring.
Stephen Chandler
@stephenc95
Jul 19 2017 15:42
Does anyone have any new info or a fix for the openaps and pump pills not showing anything on NS?
Dana Lewis
@danamlewis
Jul 19 2017 15:45
@stephenc95 almost everyone's has been mlab related. Can you remind me what your size before after compacting has been?
According to @Kdisimone, compacting can be finicky, so checking that size went down is the key to making sure it completed.
A successful run always says it was successful and the size on disk should decrease, vs just ending back up at the prompt
Stephen Chandler
@stephenc95
Jul 19 2017 15:49
@danamlewis I don't recall, but both numbers were at least 300MB under the limit. I also reflashed my edison with jubilinux and reinstalled openaps, and I made a completely new nightscout website and still have the same results with nothing showing up in the openaps and pump pills.
Dana Lewis
@danamlewis
Jul 19 2017 15:50
Ok. I would try compacting anyway and see if that changes anything?
@audiefile did yours ever get going again?
katie disimone
@Kdisimone
Jul 19 2017 15:51
@stephenc95 have you ever had it working previously? Is this a new problem?
jmcrawford
@jmcrawford
Jul 19 2017 15:58
@francesc0-cgm We see IOB drop off at the 2 hour mark. What's your DIA set to?
Stephen Chandler
@stephenc95
Jul 19 2017 15:59
@Kdisimone It was working until I updated to the latest version of oref0
katie disimone
@Kdisimone
Jul 19 2017 16:00
Have you tried to deploy worth a different branch of cgm-remote-monitor?
Stephen Chandler
@stephenc95
Jul 19 2017 16:01
@Kdisimone no, not yet
Andy Sharrow
@dramageek
Jul 19 2017 16:08
@danamlewis @audiefile Mine's still not back up either. I know Dana mentioned opening an issue yesterday for it, but I don't see one so I just opened one: here:openaps/oref0#553
francesc0-cgm
@francesc0-cgm
Jul 19 2017 16:18
@jmcrawford 4 hours. It is not a drop. It lost bolus time...
Christian Driver
@DriverNightscout
Jul 19 2017 16:20
@danamlewis Thanks
Another question: I'd like to use XDripAPS. I know this uses a local SQLlite instance. Does XDripAPS clean itself up, or is preventative maintenance needed to keep the database size within bounds of what the Edison can cope with?
francesc0-cgm
@francesc0-cgm
Jul 19 2017 16:30
It never happened...because till today i never used bolus wizard on the pump. @jmcrawford are you using it when it happens? I use loop to bolus normally
Stephen Chandler
@stephenc95
Jul 19 2017 16:32
@Kdisimone Right now I am using the master branch, should I redeploy with dev branch?
jmcrawford
@jmcrawford
Jul 19 2017 16:34
@francesc0-cgm We use bolus wizard on pump. What we've seen is that IOB decays normally up to the two-hour mark, then the next openaps iteration the iob is reported as 0 (or negative, if it's been low-temping). Wondered if it was related to 1/2 DIA, or as Scott suggested something to do with pumphistory.
We also have 4 hour DIA, we see the IOB disappear 2hours from bolus. You see your iob disappear at 2.5hours from bolus, with the same DIA, correct? That would seem to rule out the 1/2DIA idea.
francesc0-cgm
@francesc0-cgm
Jul 19 2017 16:42
Yes but i had this problem only using bolus wizard from the pump. When bolusing from loop i never met this issue
Rachel Sandlain
@audiefile
Jul 19 2017 16:45
Not reliably @danamlewis. I'm now having issues with my site loading at all. I even created a brand new site with a brand new monogo. That loaded ok before the openaps stuff was added. Now it loaded only sometimes. I'll get a white screen with just the nightscout title or just dashes more often than I get actual info. I do know that there is data there to load
I still get that segmentation fault if I the Edison checks the battery kevel
Tim Street
@tim2000s
Jul 19 2017 17:23
@audiefile have you flashed back to 0.1.1?
If you have you may need to return to Yocto then reflash to jubilinux to get around that.
Rachel Sandlain
@audiefile
Jul 19 2017 17:25
Not yet. Right now I'm more worried about not having a reliable nights out site
Would I need to go back to goto or can I just flash 0.1.1?
Dana Lewis
@danamlewis
Jul 19 2017 17:47
https://github.com/openaps/oref0/issues/553#issuecomment-316463448 <— @audiefile @stephenc95 @dramageek. Also, @dramageek you started noticing it on dev, what point in time (near the end right before release, or farther back)?
Andy Sharrow
@dramageek
Jul 19 2017 17:49
@danamlewis It was after I had upgraded to dev-5.0 to give it the OK for final release. Didn't break immediately, it was a couple of days later. I was on dev before that, but IDK what version of dev.
Tim Street
@tim2000s
Jul 19 2017 17:50
You should just be able to flash to 0.1.1. The 0.2.0 build is missing the files needed to get the Edison battery data, which is why you get the segmentation fault. OpenAPS will run on it, but you just have to know how long a fully charged battery lasts.
Dana Lewis
@danamlewis
Jul 19 2017 17:51
@dramageek what version of jubilinux are you running? wondering if audiefile’s is coincidental/not related
Scott Leibrand
@scottleibrand
Jul 19 2017 17:57
@francesc0-cgm @jmcrawford can one of you open an issue please? https://github.com/openaps/oref0/issues/new
Andy Sharrow
@dramageek
Jul 19 2017 17:57
I believe I'm on the latest. I last re-flashed back in March. Let me connect in and I'll post the uname results
Rachel Sandlain
@audiefile
Jul 19 2017 18:29
@danamlewis I started having issues when I went to do a new, updated rig. This was a brand new Edison. After I put it in production, I started having site issues. It wouldn't update the openaps pill. I tried a bunch if things in the site and database. I even created a new one. Then I eventually figured out the segmentation fault thing was preventing the rig from updating but I still couldn't get things reliable. I had a ton of errors on the site. I tried compacting the db, I even created a new one but still flaky. I eventually created a new site with an auto db. I tried
That site worked at first but once I added openaps and point the rig to it, it became flaky and throwing errors
Dana Lewis
@danamlewis
Jul 19 2017 18:30
hm. can you check and see if like @dramageek , your mlab is getting entries etc. but see if device status is what’s blanking out?
Rachel Sandlain
@audiefile
Jul 19 2017 18:31
@tim2000s Thank you! I wondered what was causing that.
Andy Sharrow
@dramageek
Jul 19 2017 18:32
uname -a: Linux openaps2 3.10.17-poky-edison+ #6 SMP PREEMPT Wed Mar 23 21:47:59 EDT 2016 i686 GNU/Linux
Rachel Sandlain
@audiefile
Jul 19 2017 18:35
It does update to devicestatus because I stopped it from checking the Edison battery
Stephen Chandler
@stephenc95
Jul 19 2017 18:55
@danamlewis I booted up an older edison that I haven't updated yet still running jubilinux v0.1.1 and oref0 v0.4.2, and using the same NS instance v0.9.2 that I tried with my newer edison and the openaps and pump pills were working
jmcrawford
@jmcrawford
Jul 19 2017 19:01
@scottleibrand @francesc0-cgm Issue created: openaps/oref0#554
Tim Street
@tim2000s
Jul 19 2017 19:03
If people are using 0.2.0, that may be an issue. It's not a stable release.
(Or has there been an update to it and it's now being pushed as stable?)
I know it breaks the rig battery detection, and I wouldn't be at all surprised if it breaks other things!
Michael Spradling
@M1Sports20
Jul 19 2017 19:11
Ahh, just shot myself in the foot. I renamed my edison user to a more common user I use on all my unix systems. I just noticed oref-setup script parses /etc/passwd to determine if it should install edison features such as battery.
Really, I don't think it should look at the username. Maybe it would be better to parse /proc/cpuinfo or something else displayed by the kernel.
I would be willing to create a git issue and fix it myself. It would be a good way to introduce my self to the code side of the project with you guys. Minor change.
Before I do it though, I am just wondering if you like the idea or not?
I guess it would really be nice to ask the edision if the explorer board is attached. I have a few ideas. Let me know
RedCyclist1
@RedCyclist1
Jul 19 2017 19:17
@tim2000s I have 0.2.0 and my NS is working fine. I am on 5.1 master with edison/explorer rig
Andy Sharrow
@dramageek
Jul 19 2017 19:25
0.2.0 of what?
Jubilinux?
Eric
@ecc1
Jul 19 2017 19:27
@M1Sports20 For a while I was using rigs with different kinds of radios, so my code does a sanity check by reading the hardware version id over SPI
Michael Spradling
@M1Sports20
Jul 19 2017 19:29
@ecc1: I was actually thinking about that after I typed it out that. THis feature is actually tied to the explorer board and not the edison. I can create a pull request
I guess I was more curious if anyone else would see it useful or wanted. More targeted at @anamlewis and scottleibrand
Scott Leibrand
@scottleibrand
Jul 19 2017 19:44
@M1Sports20 that was just a quick and relatively reliable method of detecting if we were on an Edison. If you can replace that with a more reliable method, please do PR it.
Michael Spradling
@M1Sports20
Jul 19 2017 19:49
scottlibrand: Will do. Thanks
Tim Street
@tim2000s
Jul 19 2017 20:04
@RedCyclist1 I run a rig with the 0.2.0 release on it too (running 0.5.0-dev) with no issues, except the lack of battery check.
Scott Leibrand
@scottleibrand
Jul 19 2017 20:27
@tim2000s @RedCyclist1 please reference which thing you're talking about when mentioning 0.2.0. there are 0.2.0 versions of both the openaps toolkit and of jubilinux. I assume you're both talking about jubilinux 0.2.0, but we all know what they say about assumptions...
And of course: https://xkcd.com/1339/
scottleibrand @scottleibrand wonders how meta this joke can get
skubesch
@skubesch
Jul 19 2017 21:57
@tim2000s The latest state release of jubilinux is actually 0.2.0 now (as of a few days ago I believe)
Tim Street
@tim2000s
Jul 19 2017 21:59
@scottleibrand 😂
Yes. Jubilinux
Scott Leibrand
@scottleibrand
Jul 19 2017 22:08
if anyone running jubilinux 0.2.0 is having problems with edisonvoltage, we should probably raise that with @esialb or in https://gitter.im/jubilinux/jubilinux
Rachel Sandlain
@audiefile
Jul 19 2017 22:24
I can confirm edisonvoltage as run in oref0 results in a segmentation fault
On jub
On jubilinuc 0.2.0
tepidjuice
@tepidjuice
Jul 19 2017 22:40
I can also confirm a problem with Edison voltage on Jubilinux 0.2.0