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

4th
Sep 2017
Deweyoxberg
@Deweyoxberg
Sep 04 2017 01:26
@cameronrenwick : Have a link to the doc? Couldn't find the references to pump_fields.
Miiko
@tw_miiko_twitter
Sep 04 2017 04:49
@scottleibrand Checking pump clock: "2017-09-04T06:47:24+02:00" is within 1m of current time: Mon Sep 4 06:47:51 CEST 2017
It looks no problem, or?
Scott Leibrand
@scottleibrand
Sep 04 2017 04:51
at the moment they look correct. is the problem still ongoing? if so, you may have a bolus from the future (from when the clock was set incorrectly, or from a decoding error) in your pumphistory.
Miiko
@tw_miiko_twitter
Sep 04 2017 04:59
yes, it has still the same problem, waiting for 1901011 Min
a bolus in future it not found, but it looks like so
Luis Betancourt
@betluis
Sep 04 2017 05:04
@scottleibrand hello... I have been trying to get one of the two failed rigs to connect but no success so far. I reloaded oref0 (this time de 5.3 dev) from scratch and no luck.. I went through the ccprog troubleshooting instructions and tried to ref lash the radio chip but no success either. It says this: root@edison2:~/src/ccprog# ./ccprog -p 19,7,36 erase
Using pins: DC=19, DD=7, RESET=36
Erasing chip.
NOP failed!
Could not put device into debug mode.
Chip erase failed.
root@edison2:~/src/ccprog# ./ccprog -p 19,7,36 write spi1_alt2_EDISON_EXPLORER_US_STDLOC.hex
Using pins: DC=19, DD=7, RESET=36
NOP failed!
Could not put device into debug mode.
please if you have any other advice let me know... I just can't figure out why two rigs that have worked for months suddenly decide not to connect with the pump at all. but other two rigs do...
Miiko
@tw_miiko_twitter
Sep 04 2017 05:06
@scottleibrand thanks, pls more Idea
Luis Betancourt
@betluis
Sep 04 2017 05:10
ref lashing the edison could help in anyway? should I scrap the explorer board and acquire new ones perhaps?
the error is: mmeowlink.exceptions.CommsException: Could not get subg_rfspy state or version. Have you got the right port/device and radio_type?
Scott Leibrand
@scottleibrand
Sep 04 2017 05:13
@betluis I would try reseating your Edisons on your EBs, and if that doesn't help, try swapping a working EB with a failing one, and make sure the problem follows the EB and not the Edison.
@tw_miiko_twitter you'll probably need to look at your pumphistory.json and see if you can find the offending bolus. the full pump-loop.log might have a clue.
Luis Betancourt
@betluis
Sep 04 2017 05:15
@scottleibrand yes.. I was just thinking about that, maybe a physical connection indeed... have to try this
Luis Betancourt
@betluis
Sep 04 2017 05:20
@scottleibrand yes... that's what it was. after some months with a bit of heat I think the connection got a bit loose and got disconnected. this is probably a good addition to the documentation?
it would have definitely saved me a few hours looking for an issue
Miiko
@tw_miiko_twitter
Sep 04 2017 05:22
@scottleibrand [
{
"_type": "TempBasalDuration",
"duration (min)": 30,
"_description": "TempBasalDuration 2017-09-04T07:12:19 head[2], body[0] op[0 x16]",
"timestamp": "2017-09-04T07:12:19",
"_body": "",
"_head": "1601",
"_date": "934c074411"
},
{
"_type": "TempBasal",
"temp": "absolute",
"_description": "TempBasal 2017-09-04T07:12:19 head[2], body[1] op[0x33]",
"timestamp": "2017-09-04T07:12:19",
"_body": "00",
"_head": "335c",
"rate": 2.3,
"_date": "934c074411"
},
{
"_type": "TempBasalDuration",
"duration (min)": 30,
"_description": "TempBasalDuration 2017-09-04T07:03:45 head[2], body[0] op[0 x16]",
"timestamp": "2017-09-04T07:03:45",
"_body": "",
"_head": "1601",
"_date": "ad43074411"
},
{
"_type": "TempBasal",
"temp": "absolute",
"_description": "TempBasal 2017-09-04T07:03:45 head[2], body[1] op[0x33]",
"timestamp": "2017-09-04T07:03:45",
"_body": "00",
"_head": "3336",
"rate": 1.35,
"_date": "ad43074411"
},
{
"_type": "NewTimeSet",
"_description": "NewTimeSet 2017-09-04T06:54:00 head[2], body[0] op[0x18]",
"timestamp": "2017-09-04T06:54:00",
"_body": "",
"_head": "1800",
"_date": "8076060411"
},
{
"_type": "ChangeTime",
"_description": "ChangeTime 2017-09-04T06:54:24 head[2], body[0] op[0x17]",
"timestamp": "2017-09-04T06:54:24",
"_body": "",
"_head": "1700",
"_date": "9876060411"
},
{
"_type": "ChangeTimeDisplay",
"_description": "ChangeTimeDisplay 2017-09-04T06:54:11 head[2], body[0] op[0 x64]",
"timeFormat": "d24",
"timestamp": "2017-09-04T06:54:11",
"_body": "",
"_head": "6401",
"_date": "8b76060411"
},
{
"_type": "TempBasalDuration",
"duration (min)": 30,
"_description": "TempBasalDuration 2017-09-04T06:46:45 head[2], body[0] op[0 x16]",
"timestamp": "2017-09-04T06:46:45",
"_body": "",
"_head": "1601",
"_date": "ad6e064411"
},
{
"_type": "TempBasal",
"temp": "absolute",
"_description": "TempBasal 2017-09-04T06:46:45 head[2], body[1] op[0x33]",
"timestamp": "2017-09-04T06:46:45",
"_body": "00",
"_head": "3360",
"rate": 2.4,
"_date": "ad6e064411"
},
{
"_type": "TempBasalDuration",
"duration (min)": 30,
"_description": "TempBasalDuration 2017-09-04T06:05:54 head[2], body[0] op[0 x16]",
"timestamp": "2017-09-04T06:05:54",
"_body": "",
"_head": "1601",
"_date": "b645064411"
},
{
"_type": "TempBasal",
"temp": "absolute",
"_description": "TempBasal 2017-09-04T06:05:54 head[2], body[1] op[0x33]",
"timestamp": "2017-09-04T06:05:54",
"_body": "00",
"_head": "3338",
"rate": 1.4,
"_date": "b645064411"
},
{
"_type": "TempBasalDuration",
"duration (min)": 30,
"_description": "TempBasalDuration 2017-09-04T06:04:52 head[2], body[0] op[0 x16]",
"timestamp": "2017-09-04T06:04:52",
"_body": "",
"_head": "1601",
"_date": "b444064411"
},
{
"_type": "TempBasal",
"temp": "absolute",
"_description": "TempBasal 2017-09-04T06:04:52 head[2], body[1] op[0x33]",
"timestamp": "2017-09-04T06:04:52",
"_body": "00",
"_head": "336a",
"rate": 2.65,
"_date": "b444064411"
},
{
"_type": "TempBasalDuration",
"duration (min)": 30,
"_description": "TempBasalDuration 2017-09-04T06:03
@scottleibrand I do not complet uderstand the Loop-log :worried:
Luis Betancourt
@betluis
Sep 04 2017 05:25
@scottleibrand or I could have mishandled the rig as well...
jcwarrior
@jcwarrior
Sep 04 2017 10:18
Hi! I'm checking openaps configuration before connect my son. While I was reviewing settings/settings.json downloaded from pump, I've seen insulinConcentration:50. On pump display it says U100. Is insulinConcentration used on any computation of OpenAPS? I've searched for similar questions on gitter but found nothing
Miiko
@tw_miiko_twitter
Sep 04 2017 10:54

peterfulvi
@peterfulvi
Sep 04 2017 12:37
Same as before, xdrip is not talking to rig. Should i reinstall xdrip? Anyone had this problem before. It happened when I switched back to My dexcom transmitter and started running the offline setup again. I checked the /Monitor/Glucose.json and it was empty. Thats when i concluded xdrip was not uploadin BG values to my rig. Ayways here is my output still:
Starting pump-loop at Sun Sep 3 16:58:34 EDT 2017:
Waiting up to 4 minutes for new BG: date: invalid date ‘@’
.date: invalid date ‘@’
.date: invalid date ‘@’
.date: invalid date ‘@’
.date: invalid date ‘@’
.date: invalid date ‘@’
.date: invalid date ‘@’
.date: invalid date ‘@’
.date: invalid date ‘@’
.date: invalid date ‘@’
.date: invalid date ‘@’
.date: invalid date ‘@’
.date: invalid date ‘@’
.date: invalid date ‘@’
.date: invalid date ‘@’
.date: invalid date ‘@’
.date: invalid date ‘@’
.date: invalid date ‘@’
.date: invalid date ‘@’
.date: invalid date ‘@’
.date: invalid date ‘@’
.date: invalid date ‘@’
.date: invalid date ‘@’
.date: invalid date ‘@’
.Radio ok. Listening: .No pump comms detected from other rigs
Profile less than 60m old. date: invalid date ‘@’
temp_basal.json more than 5m old.
Temp refreshed
Could not parse input data:  [SyntaxError: /root/myopenaps/monitor/glucose.json:                                                                                                                                                              Unexpected end of input]
determine-basal://text/shell/enact/suggested.json
reporting enact/suggested.json
enact/enacted.json: cat: enact/enacted.json: No such file or directory
Error, retrying

Starting pump-loop at Sun Sep 3 17:03:42 EDT 2017:
Waiting up to 4 minutes for new BG: date: invalid date ‘@’
.date: invalid date ‘@’
.date: invalid date ‘@’
.date: invalid date ‘@’
.date: invalid date ‘@’
.date: invalid date ‘@’
.date: invalid date ‘@’
.date: invalid date ‘@’
.date: invalid date ‘@’
.date: invalid date ‘@’
.date: invalid date ‘@’
.date: invalid date ‘@’
.date: invalid date ‘@’
.date: invalid date ‘@’
.date: invalid date ‘@’
.date: invalid date ‘@’
.date: invalid date ‘@’
.date: invalid date ‘@’
.date: invalid date ‘@’
.date: invalid date ‘@’
.date: invalid date ‘@’
.date: invalid date ‘@’
.date: invalid date ‘@’
.date: invalid date ‘@’
.Radio ok. Listening: .No pump comms detected from other rigs
Profile less than 60m old. date: invalid date ‘@’
temp_basal.json less than 5m old. date: invalid date ‘@’
pumphistory more than 5m old. : Refreshed pumphistory    at node.js:906:3
 and meal.json
Could not parse input data:  [SyntaxError: /root/myopenaps/monitor/glucose.json:                                                                                                                                                              Unexpected end of input]
determine-basal://text/shell/enact/suggested.json
reporting enact/suggested.json
enact/enacted.json: cat: enact/enacted.json: No such file or directory
Error, retrying
Waiting for 30s silence before mmtuning
Radio ok. Listening: .No pump comms detected from other rigs
Listening for 30s silence before mmtuning: .No pump comms detected from other ri                                                                                                                                                             gs
mmtune: "916.564", 5, -57
cameronrenwick
@cameronrenwick
Sep 04 2017 12:49
@YYCMichael got to this page --> http://openaps.readthedocs.io/en/latest/docs/While%20You%20Wait%20For%20Gear/nightscout-setup.html?highlight=heroku and read the 2 key/value charts. Make sure you have yours set correctly in heroku
Scott Leibrand
@scottleibrand
Sep 04 2017 13:07
@jcwarrior afaik that value is never used anywhere.
jcwarrior
@jcwarrior
Sep 04 2017 13:08
thank you @scottleibrand
Deweyoxberg
@Deweyoxberg
Sep 04 2017 14:41
Thanks @cameronrenwick , got it working and added the voltage alarm.
Luis Betancourt
@betluis
Sep 04 2017 16:45
Hello.. quick question about SMB... does it makes sense to have zero temp when BG is in the order of 300+?
Scott Leibrand
@scottleibrand
Sep 04 2017 16:47
if you have enough IOB to get you below 80, then yes.
it will keep delivering SMBs as needed (delivering a lot more insulin than the basal would, most likely), and keep the zero temps in place in case BG starts falling rapidly
fjungman
@fjungman
Sep 04 2017 16:56
A question on NS pills. Maybe this is the wrong forum. My "Pump" and "OpenAPS" pills stopped functioning a couple weeks ago. I had made no changes, so I assumed that the Edison code got corrupted and I needed to reflash. I checked my NS install on Azure and it is current as of yesterday, and I have not touched that in a couple of months. So, I switched to the backup rig last night (I created the two rigs on the same day in July, and this one has not been used). Rig works fine, but the pills are still missing. I see in Papertrail that the values are all being uploaded, so it isn't a JSON problem. Really out of ideas here. I'm using the BT PAN method of connecting the rig to the phone/internet.
Scott Leibrand
@scottleibrand
Sep 04 2017 16:57
(sigh)... please check the docs troubleshooting page. (this comes up about once a day, and always requires the same troubleshooting steps. not sure what we can do to make that more clear, but if you have any ideas, PRs welcome.)
Scott Leibrand
@scottleibrand
Sep 04 2017 17:12
Luis Betancourt
@betluis
Sep 04 2017 17:59
@scottleibrand I think people will encounter this problem as many of us approach a full mlab database... when setting up the first time this was not quite apparent and most people I assume didn't knot know very well how the whole database process and mlab account really work. An idea would be to be more emphatic on the mlab account limit at the setup instructions rather than on the troubleshooting... by the other hand, what could be considered as the "official openaps updates/news channel" that users could refer to or suscribe to? I am not sure the intend-to-bolus or google group serve this purpose well, perhaps something like this could be useful?... just throwing ideas on the table...
Scott Leibrand
@scottleibrand
Sep 04 2017 18:01
yeah, I was looking for where else in the setup docs we could put a note about it. I'm not sure where the actual mLab setup is, though...
Google group + @OpenAPS on Twitter are the main announcement channels
Luis Betancourt
@betluis
Sep 04 2017 18:06
Dana, I agree. my concern is that as Openas have become a rather stable part of our lives we naturally become a bit less information hungry and perhaps require one "most read" channel that we all know is key (thinking on the user base). Again, it's just ideas to bounce around...
peterfulvi
@peterfulvi
Sep 04 2017 18:10
I'm still getting the same error as before. I tried even running xdrip on another phone and still get the same result as you see above-mentioned. I'm using the Dev branch by the way. That's one similarity between both rigs. I could try reinstalling xdrip and doing it all from scratch again. I hate to lose all my records though.
Miiko
@tw_miiko_twitter
Sep 04 2017 18:34
All microboluses was disabled:-(
Phil
@drnoname82_twitter
Sep 04 2017 19:03
I hardly dare to ask a Nightscout question, but yes, I have gone through the usual troubleshooting steps :smile: I just installed the cob-aware-autosens branch on our backup rig for daytime testing because we had problems with the current autosens algorithm. The rig works perfectly fine and also uploads everything to Nightscout but the OpenAPS pill keeps displaying "Not enacted" although basal rates are set on the pump and there are no error messages in the logs. Any ideas?
Dana Lewis
@danamlewis
Sep 04 2017 19:53
We broke something on that branch before we walked out the door an hour ago, so not sure. (That's a super live active dev branch that's many steps away from dev, so...I'd advise a huge amount of caution)
Martin Haeberli
@mhaeberli
Sep 04 2017 19:58
what is the expected timing on 0.5.3?
Dana Lewis
@danamlewis
Sep 04 2017 20:02
Soon. Maybe this week?
Martin Haeberli
@mhaeberli
Sep 04 2017 20:10
k thx
Scott Leibrand
@scottleibrand
Sep 04 2017 20:25
The branch I broke was fix-autotune. The cob-aware-autosens one has been working for us, but hasn't been tested more widely yet. Have you checked your mLab collection size etc.?
Dana Lewis
@danamlewis
Sep 04 2017 20:26
Phil - Kate just reported the same thing in 0.6.0-dev
So probably same issue
Not sure where it is yet though
Scott Leibrand
@scottleibrand
Sep 04 2017 20:27
openaps/oref0#637
Phil
@drnoname82_twitter
Sep 04 2017 20:28
Yes I performed all the usual checks. Nightscout works fine with the other rig on 0.5.3, installing 0.6.0-dev yielded the same Nightscout error
Dana Lewis
@danamlewis
Sep 04 2017 20:28
K I would switch back to 0.5.3 if you want the pill to work; may take us a while to resolve since we are out and about right now.
Scott Leibrand
@scottleibrand
Sep 04 2017 20:29
Ok, can you paste your pump-loop.log output into openaps/oref0#637 too?
Phil
@drnoname82_twitter
Sep 04 2017 20:36
Sure! I also looked at the mlab entries and could not spot any significant difference between the entries made by 0.5.3 and 0.6.0. (Don't worry, we don't rely on an untested branch and only use it while someone is watching the logs continuously...)
Dana Lewis
@danamlewis
Sep 04 2017 20:38
:+1:
Craig Brenner
@cbrenner
Sep 04 2017 20:44
As I was looking at NS, I noticed the forecasts line for my son's BG suddenly swung from a dropping BG to a very high BG prediction. When I investigated further, I saw that the IOB amount went from 3.53u to -0.78 in a few minutes. The IOB was from an earlier food bolus of 117g / 9.7u. (See pictures). Can someone please shed some light on what may have happened here. This is very concerning as the OpenAPS system is still showing 40gs for COB but the matching IOB is gone and the system is now predicting a COBpredBG of 300.
IOB Question.jpg
Scott Leibrand
@scottleibrand
Sep 04 2017 20:55
pump-loop.log as well please?
Craig Brenner
@cbrenner
Sep 04 2017 20:58
ok, I will grab it from that 10 min time period.
Scott Leibrand
@scottleibrand
Sep 04 2017 21:00
Also, what oref0 version are you running? And did it recover and correct IOB on its own?
Craig Brenner
@cbrenner
Sep 04 2017 21:06
running the current master of oref0 and no it did not ever correct the IOB on its own. Still showing incorrect iOB now. Attached log as PDF
Sep 04 Pump Log.pdf
Scott Leibrand
@scottleibrand
Sep 04 2017 21:21
Ok. Looks like it sees all the boluses, but isn't using them to calculate IOB. We could either run reports manually to narrow it down, or just check if 0.5.3 fixes it...
Craig Brenner
@cbrenner
Sep 04 2017 21:24
@scottleibrand With my son going back to school tomorrow, I would like to take the most conservative approach in the short-term to resolve. Wondering if the git repository issue at 12:45p may have caused any issues and if it would be worth it to try to run a fix for a corrupted git repository?
Scott Leibrand
@scottleibrand
Sep 04 2017 22:13
You could try just renaming/moving your myopenaps directory to a backup directory name and rerunning oref0-setup using your oref0-runagain
peterfulvi
@peterfulvi
Sep 04 2017 22:35
Ok I seemed to have fixed it. I went back to the master branch. My loop started our 3 hrs behind i ran oref0 set-system-time and that brought it up to the right time. The only thing now is every other loop it tries to run the ntp service and always fails, the it say unsuccessful microbolus, then it does it again sucessfully. is there a way to iron out this issue? Here is my output

Starting supermicrobolus pump-loop at Mon Sep 4 18:25:02 EDT 2017 with 15 second wait_for_silence:
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
Preflight OK. Profile less than 60m old. glucose.json newer than pump_loop_completed.
Temp refreshed
Warning: Autotune has not been run. All microboluses will be disabled until you manually run autotune or add it to run nightly in your loop.
{"carbs":38,"boluses":11.2,"mealCOB":0,"currentDeviation":1.51,"maxDeviation":7.21,"minDeviationSlope":-1.493}
{"iob":4.587,"activity":0.0496,"bolussnooze":0.163,"basaliob":3.141,"netbasalinsulin":5.3,"hightempinsulin":5.3,"microBolusInsulin":0,"microBolusIOB":0,"time":"2017-09-04T22:27:34.000Z","lastBolusTime":1504558391000}
{"delta":-5,"glucose":210,"short_avgdelta":-4,"long_avgdelta":-4.09}
{"duration":29,"rate":1.75,"temp":"absolute"}
Autosens adjusting basal from 1.25 to 1.45; target_bg from 90 to 86; sens from 30 to 25.9 (autosens ratio 1.16)
min_bg unchanged: 77; target_bg from 86 to 80; max_bg from 94 to 80
Carb Impact: 1.4 mg/dL per 5m; CI Duration: 0 hours; remaining 4h+ CI: 0 mg/dL per 5m
Accel. Carb Impact: 10 mg/dL per 5m; ACI Duration: 0 hours
UAM Impact: 2.3 mg/dL per 5m; UAM Duration: 0.2 hours
minPredBG: 84 minIOBPredBG: 87 minUAMPredBG: 80 avgPredBG: 84 COB: 0 carbs: 38
BG projected to remain above 77 for 240 minutes
bgUndershoot: -20 zeroTempDuration: 240 zeroTempEffect: 130 carbsReq: -40
Checking deliverAt: 2017-09-04T22:25:38.034Z is within 1m of current time: Mon Sep  4 18:25:39 EDT 2017
and that smb-suggested.json is less than 1m old
enact/smb-suggested.json: {"insulinReq":0.05,"bg":210,"reservoir":"84.6","temp":"absolute","snoozeBG":106,"predBGs":{"UAM":[210,204,198,191,185,178,172,166,160,154,148,143,138,133,128,123,119,115,111,107,104,101,98,96,94,91,90,88,87,86,85,84,83,83,82,82,81,81,80],"IOB":[210,205,199,194,188,183,177,172,166,161,155,150,145,139,135,130,126,122,118,114,111,108,105,103,100,98,97,95,94,93,92,91,90,89,89,88,88,88,87]},"minPredBG":84,"IOB":4.587,"reason":"COB: 0, Dev: 9, BGI: -6.42, ISF: 26, Target: 80, minPredBG 84, IOBpredBG 87, UAMpredBG 80; Eventual BG 100 >= 80, 29m@1.75 > 2 * insulinReq. Setting temp basal of 1.55U/hr.  29m left and 1.75 ~ req 1.55U/hr: no temp required","COB":0,"eventualBG":100,"tick":-5,"deliverAt":"2017-09-04T22:25:38.034Z"}
No smb_enact needed. Temp refreshed: monitor/temp_basal.json: {"duration":29,"rate":1.75,"temp":"absolute"}
RefreshInterpolated [ date: 1504562228748, glucose: 249 ]
ed pumphistory
Checking pump clock: "2017-09-04T18:28:23-04:00" is within 1m of current time: Mon Sep  4 18:26:20 EDT 2017
Pump clock is more than 1m off: attempting to reset it
Waiting for ntpd to synchronize... No!
ntpd did not synchronize.
Restarting ntp (via systemctl): ntp.service.
Waiting for ntpd to synchronize... Unexpected first line <localhost: timed out, nothing received>
Unsuccessful supermicrobolus pump-loop at Mon Sep 4 18:26:37 EDT 2017
Craig Brenner
@cbrenner
Sep 04 2017 23:01
@scottleibrand Ok, I can try that but you don't think there is a corrupted git repository per the 12:45p error? And, would that even have an impact on the IOB problem?