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

7th
Jan 2019
Martin Haeberli
@mhaeberli
Jan 07 01:54
Temp refreshed: monitor/temp_basal.json: {"duration":0,"temp":"absolute","rate":0}
rm: cannot remove ‘enact/smb-enacted.json’: No such file or directory
grep: enact/smb-enacted.json: No such file or directory
cp: cannot stat ‘enact/smb-enacted.json’: No such file or directory
enact/smb-enacted.json: cat: enact/smb-enacted.json: No such file or directory
(NOT VALID JSON: empty)
Checking pump status (suspended/bolusing): {"status":"normal","bolusing":false,"suspended":false}
Temp refreshed: monitor/temp_basal.json: {"duration":0,"temp":"absolute","rate":0}
Couldn't smb_enact_temp
oref0-pump-loop failed. pump_loop_completed more than 15m old; waiting for 6 s silence before mmtuning
Listening for 6s: .No interfering pump comms detected from other rigs (this is a good thing!)
(this is on a new Edison rig running dev against a test pump)
Martin Haeberli
@mhaeberli
Jan 07 02:09

to be clear, I’m stuck on:

rm: cannot remove ‘enact/smb-enacted.json’: No such file or directory
grep: enact/smb-enacted.json: No such file or directory
cp: cannot stat ‘enact/smb-enacted.json’: No such file or directory
enact/smb-enacted.json: cat: enact/smb-enacted.json: No such file or directory
(NOT VALID JSON: empty)

so it acts like it’s looping, but it doesn’t actually set any temp basal...

or SMBs, etc
running dev; most recent commit
commit 53e49fa4f70c3853d22f6156cbadc504f9f92330
Author: viq <vicviq@gmail.com>
Date:   Sun Jan 6 21:46:30 2019 +0100

    Script to create local symlinks (#1181)

    * Consistent script naming

    * Script to create local symlinks.
Martin Haeberli
@mhaeberli
Jan 07 02:15
is there a way (when running setup) to have the script be happy with the current checked out commit instead of pulling head?
Martin Haeberli
@mhaeberli
Jan 07 03:07
ok - the hard way - forked oref0 into my own github, created a new branch that is current only to 7f3526e190c9455016c71f664de6e6bd1dce934a , which I had last had success with; trying again
Martin Haeberli
@mhaeberli
Jan 07 03:22
which still didn’t fix this...
still get:
rm: cannot remove ‘enact/smb-enacted.json’: No such file or directory
grep: enact/smb-enacted.json: No such file or directory
cp: cannot stat ‘enact/smb-enacted.json’: No such file or directory
enact/smb-enacted.json: cat: enact/smb-enacted.json: No such file or directory
(NOT VALID JSON: empty)
so maybe this error is ‘normal’ in normal operation?
Martin Haeberli
@mhaeberli
Jan 07 03:27
getting this error against test pump:
Continuing oref0-pump-loop at Sun Jan  6 19:25:24 PST 2019
mmtune: "916.550", 2, -46 
No wait required.
If pump and rig are close enough, this error usually self-resolves. Stand by for the next loop.
Unsuccessful oref0-pump-loop at Sun Jan 6 19:25:45 PST 2019
(separated by a few inches; signal looks good, trying to understand why temp basals and SMBs shown in the pump log aren’t happening on the pump, which is a 2.4A 722)
Martin Haeberli
@mhaeberli
Jan 07 03:54
somehow resolved; not clear how
renegadeandy
@renegadeandy
Jan 07 16:03
I am getting another issue - similar to my last. aps just stops when out and about

log from the last period where it wasn't working : ```Starting oref0-pump-loop at Mon Jan 7 14:19:02 GMT 2019 with 2 second wait_for_silence:
Waiting up to 4 minutes for new BG: ................
Starting oref0-pump-loop at Mon Jan 7 16:01:24 GMT 2019 with 30 second wait_for_silence:
Waiting up to 4 minutes for new BG: ls: cannot access /tmp/pump_loop_completed: No such file or directory
mmeowlink.exceptions.CommsException: Could not get subg_rfspy state or version. Have you got the right port/device and radio_type?

Radio check failed. mmeowlink.exceptions.CommsException: Could not get subg_rfspy state or version. Have you got the right port/device and radio_type?

The CC111x is located at /dev/spidev5.1
RileyLink OK
Version: subg_rfspy 0.8
OK


Log from period where it wasnt working shows the same issue as yesterday:

```Starting oref0-pump-loop at Mon Jan  7 13:50:02 GMT 2019 with 8 second wait_for_silence:
Retrying without waiting for new BG
Radio ok. Listening: .No interfering pump comms detected from other rigs (this is a good thing!)
Preflight OK. Profile less than 60m old; Profile valid. Ref
{"status":"normal","bolusing":true,"suspended":false}
Couldn't refresh_pumphistory_and_meal
oref0-pump-loop failed. 
The CC111x is located at /dev/spidev5.1
RileyLink OK
Version: subg_rfspy 0.8
OK

The CC111x is located at /dev/spidev5.1
RileyLink OK
Version: subg_rfspy 0.8
SUCCESS
RileyLink OK
Version: subg_rfspy 0.8
SUCCESS
RileyLink OK
Version: subg_rfspy 0.8
SUCCESS
RileyLink OK
Version: subg_rfspy 0.8
SUCCESS
RileyLink OK
Version: subg_rfspy 0.8
SUCCESS
RileyLink OK
Version: subg_rfspy 0.8
SUCCESS
RileyLink OK
Version: subg_rfspy 0.8
SUCCESS
RileyLink OK
Version: subg_rfspy 0.8
SUCCESS
RileyLink OK
Version: subg_rfspy 0.8
SUCCESS
RileyLink OK
Version: subg_rfspy 0.8
SUCCESS
Listening for 40s silence before mmtuning: .No interfering pump comms detected from other rigs (this is a good thing!)
mmtune: "868.366", 5, -70 waiting for 20 second silence before continuing
Radio ok. Listening: .No interfering pump comms detected from other rigs (this is a good thing!)
Preflight OK. Done waiting for rigs with better signal.
If pump and rig are close enough, this error usually self-resolves. Stand by for the next loop.
Unsuccessful oref0-pump-loop at Mon Jan 7 13:52:06 GMT 2019

Error identified is : Couldn't refresh_pumphistory_and_meal

Last pump loop which worked was at 13:39:02

```Starting oref0-pump-loop at Mon Jan 7 13:39:02 GMT 2019 with 18 second wait_for_silence:
Waiting up to 4 minutes for new BG: glucose.json newer than pump_loop_completed
Radio ok. Listening: .No interfering pump comms detected from other rigs (this is a good thing!)
Preflight OK. Profile less than 60m old; Profile valid. Refreshed pumphistory and meal.json
Checking pump clock: "2019-01-07T13:40:02+00:00" is within 90s of current time: Mon Jan 7 13:40:03 GMT 2019
Temp refreshed
Autotune exists! Hoorah! You can use microbolus-related features.
{"carbs":15,"nsCarbs":15,"bwCarbs":0,"journalCarbs":0,"mealCOB":0,"currentDeviation":3.33,"maxDeviation":9.7,"minDeviation":-2.72,"slopeFromMaxDeviation":-3.753,"slopeFromMinDeviation":1.061,"allDeviations":[8,10,8,5,1,-3],"lastCarbTime":1546857553000,"bwFound":false}
{"iob":0.509,"activity":0.0028,"basaliob":0.398,"bolusiob":0.111,"netbasalinsulin":0.65,"bolusinsulin":1.5,"time":"2019-01-07T13:40:06.000Z","iobWithZeroTemp":{"iob":0.509,"activity":0.0028,"basaliob":0.398,"bolusiob":0.111,"netbasalinsulin":0.65,"bolusinsulin":1.5,"time":"2019-01-07T13:40:06.000Z"},"lastBolusTime":1546857553000,"lastTemp":{"rate":3.75,"timestamp":"2019-01-07T13:23:16+00:00","started_at":"2019-01-07T13:23:16.000Z","date":1546867396000,"duration":17.87}}
{"delta":-2,"glucose":115,"noise":1,"short_avgdelta":0.56,"long_avgdelta":5.35,"date":1546868158725}
Autosens ratio: 0.86; Adjusting basal from 1.65 to 1.4; target_bg from 86 to 90; ISF from 45.5 to 52.9; CR: 9
currenttemp: { duration: 25, rate: 4, temp: 'absolute' } lastTempAge: 17 m tempModulus: 12 m
2019-01-07T13:40:12.857Z
Checking deliverAt: 2019-01-07T13:40:12.857

Then next period it fails at 13:41:03 with :

```Starting oref0-pump-loop at Mon Jan 7 13:41:03 GMT 2019 with 14 second wait_for_silence:
Retrying without waiting for new BG
Radio ok. Listening: .No interfering pump comms detected from other rigs (this is a good thing!)
Preflight OK. Profile less than 60m old; Profile valid. Ref
{"status":"normal","bolusing":true,"suspended":false}
Couldn't refresh_pumphistory_and_meal
oref0-pump-loop failed. If pump and rig are close enough, this error usually self-resolves. Stand by for the next loop.
Unsuccessful oref0-pump-loop at Mon Jan 7 13:41:27 GMT 2019

Starting oref0-pump-loop at Mon Jan 7 13:42:02 GMT 2019 with 14 second wait_for_silence:
Retrying without waiting for new BG
Radio ok. Listening: .No interfering pump comms detected from other rigs (this is a good thing!)
Preflight OK. Profile less than 60m old; Profile valid. Ref
{"status":"normal","bolusing":true,"suspended":false}
Couldn't refresh_pumphistory_and_meal
oref0-pump-loop failed. If pump and rig are close enough, this error usually self-resolves. Stand by for the next loop.
Unsuccessful oref0-pump-loop at Mon Jan 7 13:42:27 GMT 2019```

Help help help!
Why does this happen?
straykatz
@straykatz
Jan 07 16:29
Good morning. Since running 0.7.0 I have been getting repeatedly this issue where the BGs are not read, however, boluses, and other pump activities (rewinds...) are read. I have two rigs running. Right now they are both doing this. In the past it's resolved itself with some rebooting (not the first).
Starting oref0-pump-loop at Mon Jan 7 08:28:03 PST 2019 with 20 second wait_for_silence:
MDT CGM configured; not waiting
Listening for 20s: .......No interfering pump comms detected from other rigs (this is a good thing!)
Continuing oref0-pump-loop at Mon Jan 7 08:28:52 PST 2019
Preflight OK.
Attempting to retrieve MDT CGM data from pump
MDT CGM data retrieved
Profile less than 60m old; Profile valid. Pump history updated through 2019-01-07T07:57:38-08:00 with 0 new records; meal.json
Warning: setting mealCOB to 0 because currentDeviation is null/undefined
refreshed: {"carbs":30,"nsCarbs":30,"bwCarbs":0,"journalCarbs":0,"mealCOB":0,"currentDeviation":null,"maxDeviation":0,"minDeviation":999,"slopeFromMaxDeviation":0,"slopeFromMinDeviation":999,"allDeviations":[],"lastCarbTime":1546878013748,"bwFound":false}
Listening for 8s: .......No interfering pump comms detected from other rigs (this is a good thing!)
Continuing oref0-pump-loop at Mon Jan 7 08:29:45 PST 2019
Checking that pump clock: "2019-01-07T08:29:47-08:00" is within 90s of current time: 2019-01-07T08:29:46-0800
Temp refreshed: monitor/temp_basal.json: {"duration":0,"temp":"absolute","rate":0}
{"carbs":30,"nsCarbs":30,"bwCarbs":0,"journalCarbs":0,"mealCOB":0,"currentDeviation":null,"maxDeviation":0,"minDeviation":999,"slopeFromMaxDeviation":0,"slopeFromMinDeviation":999,"allDeviations":[],"lastCarbTime":1546878013748,"bwFound":false}
Autotune exists! Hoorah! You can use microbolus-related features.
{"iob":1.346,"activity":0.0174,"basaliob":-0.29,"bolusiob":1.636,"netbasalinsulin":-0.7,"bolusinsulin":3.9,"time":"2019-01-07T16:29:49.000Z","iobWithZeroTemp":{"iob":1.346,"activity":0.0174,"basaliob":-0.29,"bolusiob":1.636,"netbasalinsulin":-0.7,"bolusinsulin":3.9,"time":"2019-01-07T16:29:49.000Z"},"lastBolusTime":1546875208000,"lastTemp":{"rate":0,"timestamp":"2019-01-07T07:52:11-08:00","started_at":"2019-01-07T15:52:11.000Z","date":1546876331000,"duration":30}}
{"delta":0,"glucose":116,"noise":null,"short_avgdelta":0.56,"long_avgdelta":-0.07,"date":1546875540000,"last_cal":0}
null
No deliverAt found.
{"reason":"If current system time Mon Jan 07 2019 08:29:58 GMT-0800 (PST) is correct, then BG data is too old. The last BG data was read 51m ago at Mon Jan 07 2019 07:39:00 GMT-0800 (PST). Temp 0 <= current basal 0.55U/hr; doing nothing. "}
Couldn't smb_verify_suggested
oref0-pump-loop failed. MDT CGM configured; not waiting
Unsuccessful oref0-pump-loop (BG too old) at Mon Jan 7 08:29:58 PST 2019
that's one typical loop.
Any thoughts? Thank you!
straykatz
@straykatz
Jan 07 19:08
Oh, and this is ExplorerBoard/Edison and Enlite setup with a 522. Offline looping is also not working.
Dana Lewis
@danamlewis
Jan 07 19:15
@ecc1 see ^ for 0.7.0-dev - wondering if there's something that needs to be done to pull enlite data more regularly? or other ideas?
renegadeandy
@renegadeandy
Jan 07 19:36
@danamlewis can you take a look at my post from 16:03 this afternoon (or 4 hours ago?)
Eric
@ecc1
Jan 07 19:37
@straykatz what output do you get if you just run "cgmupdate -b 1h" ?
Dana Lewis
@danamlewis
Jan 07 19:37
@renegadeandy do the errors still occur if you reboot?
straykatz
@straykatz
Jan 07 19:38
Let me check
Eric
@ecc1
Jan 07 19:40
also check /var/log/openaps/cgm-loop.log for errors
renegadeandy
@renegadeandy
Jan 07 19:58
@danamlewis Yea, I pressed the black reset button, and it didnt fix anything
Dana Lewis
@danamlewis
Jan 07 19:59
did you press and hold down for 10 seconds until it powered off; then power it back on fully?
renegadeandy
@renegadeandy
Jan 07 19:59
@ecc1 cgm-loop only has very old errors
@danamlewis i don't think so......how would I know? Would the red LED flash>?
Dana Lewis
@danamlewis
Jan 07 20:01
https://openaps.readthedocs.io/en/latest/docs/While%20You%20Wait%20For%20Gear/understanding-your-Explorer-Board-rig.html#where-is-the-power-button yes, lights will power down completely when the rig is fully turned off; wait a second, then press and hold for several seconds til the light comes back on
straykatz
@straykatz
Jan 07 20:03
@straykatz what output do you get if you just run "cgmupdate -b 1h" ?
root@DiaBrain:~# cgmupdate -b 1h
2019/01/07 12:02:21 PAPERTRAIL environment variable is not set
2019/01/07 12:02:22 connected to CC111x radio on /dev/spidev5.1
2019/01/07 12:02:22 MEDTRONIC_PUMP_ID environment variable is not set
Eric
@ecc1
Jan 07 20:07
set the MEDTRONIC_PUMP_ID variable first
the suggestion about checking cgm-loop.log was for @straykatz too
viq
@viq
Jan 07 20:08

I'm running AndroidAPS, and I'm trying to set up OpenAPS to use autotune and upload the updated profile to nightscout. I kinda found a way to grab a profile from nightscout, and autotune ran fine, but I'm having issues with uploading.

For now I even copied the sample profile from https://openaps.readthedocs.io/en/latest/docs/Customize-Iterate/autotune.html#phase-c-running-autotune-for-suggested-adjustments-without-an-openaps-rig and filled the things it was missing with numbers, but even now uploading the profile doesn't work:

$ oref0-upload-profile test-profile.json $NS_SITE $API_SECRET -p
Could not parse input data:  TypeError: Cannot read property 'length' of undefined
    at Object.<anonymous> (/home/diabox/src/oref0/bin/oref0-upload-profile.js:82:37)
    at Module._compile (internal/modules/cjs/loader.js:689:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:700:10)
    at Module.load (internal/modules/cjs/loader.js:599:32)
    at tryModuleLoad (internal/modules/cjs/loader.js:538:12)
    at Function.Module._load (internal/modules/cjs/loader.js:530:3)
    at Function.Module.runMain (internal/modules/cjs/loader.js:742:12)
    at startup (internal/bootstrap/node.js:283:19)
    at bootstrapNodeJSCore (internal/bootstrap/node.js:743:3)

What's missing there?

Or should I be asking in https://gitter.im/openaps/autotune ?
straykatz
@straykatz
Jan 07 20:13
is that the pump number? because I have set that during setup ... I just checked the "run again"
@ecc1: here's the cleaned version: /root/src/oref0/bin/oref0-setup.sh --dir=/root/myopenaps --serial=XXPump SerialXX --cgm=MDT --ns-host=https://xxx.herokuapp.com --api-secret=token=API token for this rig XX --tty=/dev/spidev5.1 --max_iob=11 --enable=' autotune ' --radio_locale='US' --btmac='btmac=‘xxx9' --pushover_token=‘tokenxx’ --pushover_user=‘userXX’
Eric
@ecc1
Jan 07 20:16
the environment variable needs to be set in the shell in which you run cgmupdate
straykatz
@straykatz
Jan 07 20:16
if not, uh. how do I do that?
Eric
@ecc1
Jan 07 20:16
setup has (almost) nothing to do with running commands from the command line, except for downloading/building them in the first place
$ export MEDTRONIC_PUMP_ID=123456
$ cgmupdate -b 1h
`
straykatz
@straykatz
Jan 07 20:17
ah. thx
root@DiaBrain:~# cgmupdate -b 1h
2019/01/07 12:19:14 PAPERTRAIL environment variable is not set
2019/01/07 12:19:14 cannot connect to CC111x radio on /dev/spidev5.1
2019/01/07 12:19:14 /dev/spidev5.1: device is in use
renegadeandy
@renegadeandy
Jan 07 20:20
@danamlewis Ok - will try that, but its still a work around, i want to identify the root cause to fix it
Dana Lewis
@danamlewis
Jan 07 20:21
@renegadeandy you may end up needing to re-flash cprog; but rebooting is a simple and easy fix for most temporary and transient issues.
straykatz
@straykatz
Jan 07 20:23
also, @ecc1: root@DiaBrain:~# /var/log/openaps/cgm-loop.log
-bash: /var/log/openaps/cgm-loop.log: Permission denied
root@DiaBrain:~# cd myopenaps
root@DiaBrain:~/myopenaps# /var/log/openaps/cgm-loop.log
-bash: /var/log/openaps/cgm-loop.log: Permission denied
Eric
@ecc1
Jan 07 20:23
@straykatz wait until your loop isn't running, since cgmupdate needs the radio. or temporarily disable your loop
straykatz
@straykatz
Jan 07 20:23
ok.
Eric
@ecc1
Jan 07 20:23
it's a file: use "less" or "cat" to view it
renegadeandy
@renegadeandy
Jan 07 20:24
how do you mean reflash cprog?
Scott Leibrand
@scottleibrand
Jan 07 20:24
@renegadeandy {"status":"normal","bolusing":true,"suspended":false}
are you using extended / dual-wave boluses?
renegadeandy
@renegadeandy
Jan 07 20:25
yes, sometimes, and at that point when it all went wrong, i was using dual wave
renegadeandy
@renegadeandy
Jan 07 20:27
Oh no way! That makes sense, this happens in a coffee shop, where i always use a dual wave!
Dana Lewis
@danamlewis
Jan 07 20:27
(so, disable/stop doing dual waves, and if errors still appear, we can troubleshoot those, but stopping those wave boluses should resolve everything else)
renegadeandy
@renegadeandy
Jan 07 20:30
Okay, will try that
however
after my dual wave stoped, it didn't return to operation...
so it was perhaps associated with a more crippling issue
straykatz
@straykatz
Jan 07 20:30

@ecc1: cat /var/log/openaps/cgm-loop.log
Here I get a whole lot of this:

Starting oref0-mdt-update at Mon Jan 7 12:18:32 PST 2019:
Most recent cgm record: cgm data < 2.5m old
Completed oref0-mdt-update at Mon Jan 7 12:18:32 PST 2019

Starting oref0-mdt-update at Mon Jan 7 12:20:49 PST 2019:
Most recent cgm record: cgm data < 2.5m old
Completed oref0-mdt-update at Mon Jan 7 12:20:49 PST 2019
etc.

Dana Lewis
@danamlewis
Jan 07 20:30
I would fully turn off your rig, turn it back on, then wait a few (up to 20) minutes until after it does it's next pump history read
if it's still erroring, then paste those error messages, but wait up until it's successfully read pump history
straykatz
@straykatz
Jan 07 20:31
@dana - who?
Dana Lewis
@danamlewis
Jan 07 20:31
@straykatz sorry, that was for @renegadeandy ^
straykatz
@straykatz
Jan 07 20:31
and here's what the pump is saying :): {"reason":"If current system time Mon Jan 07 2019 12:30:06 GMT-0800 (PST) is correct, then BG data is too old. The last BG data was read 291.1m ago at Mon Jan 07 2019 07:39:00 GMT-0800 (PST). Temp 0 <= current basal 0.6U/hr; doing nothing. "}
Couldn't smb_verify_suggested
oref0-pump-loop failed. MDT CGM configured; not waiting
Unsuccessful oref0-pump-loop (BG too old) at Mon Jan 7 12:30:06 PST 2019
* (well, really, the rig saying about the loop)
I have the other rig back on 0.6.2, but off right now, as it has been the case since this started yesterday, that when one rig eventually starts reading BGs, the other one is happy and plays along. Until I turn one off, or leave the house.
Eric
@ecc1
Jan 07 20:36
I still haven't seen the output of that cgmupdate command though
(and obvious question, there is recent Enlite CGM data, right? shown on the pump?)
straykatz
@straykatz
Jan 07 20:38
oh, right. Here you go:
root@DiaBrain:~# cgmupdate -b 1h
2019/01/07 12:38:00 PAPERTRAIL environment variable is not set
2019/01/07 12:38:01 connected to CC111x radio on /dev/spidev5.1
2019/01/07 12:38:01 setting frequency to 916.600
2019/01/07 12:38:03 waking pump
2019/01/07 12:38:12 CGM clock difference = 217.477794ms
2019/01/07 12:38:12 retrieving records since 2019-01-07 11:38:12
2019/01/07 12:38:13 writing CGM timestamp for page 23 and rescanning
2019/01/07 12:38:13 no response to glucosePage
Affirmative. (and obvious question, there is recent Enlite CGM data, right? shown on the pump?)
Eric
@ecc1
Jan 07 20:41
so that didn't read anything, because it didn't get a response to that glucosePage command. Can you try it a few more times to see if it eventually works? could be a timing problem with this code on the Edison; I think most users of it have been on RPis
straykatz
@straykatz
Jan 07 20:44
there's some life after all :)
root@DiaBrain:~# cgmupdate -b 1h
2019/01/07 12:43:30 PAPERTRAIL environment variable is not set
2019/01/07 12:43:31 connected to CC111x radio on /dev/spidev5.1
2019/01/07 12:43:31 setting frequency to 916.600
2019/01/07 12:43:32 model 522 pump
2019/01/07 12:43:32 CGM clock difference = 341.880423ms
2019/01/07 12:43:32 retrieving records since 2019-01-07 11:43:32
2019/01/07 12:43:36 writing CGM timestamp for page 23 and rescanning
2019/01/07 12:43:41 stopping CGM history scan at 2019-01-07 11:39:00
2019/01/07 12:43:41 15 CGM records
2019/01/07 12:43:41 12 Nightscout entries from 2019-01-07 12:39:00 to 2019-01-07 11:44:00
Eric
@ecc1
Jan 07 20:45
OK, that's promising. Can you run it again with the "-v" flag so it prints the records?
straykatz
@straykatz
Jan 07 20:46
yes, it is reading BGs
first loop after ... still BG too old. let's give it a while.
Observation, even when the BGs here updating, they were updating with a lot of gaps - 10, 12 minutes and more.
straykatz
@straykatz
Jan 07 20:52
same thing in the loop - "The last BG data was read 313m ago at Mon Jan 07 2019 07:39:00 GMT-0800 (PST). Temp 0 <= current basal 0.6U/hr; doing nothing. "}
Couldn't smb_verify_suggested
oref0-pump-loop failed. MDT CGM configured; not waiting
Unsuccessful oref0-pump-loop (BG too old) at Mon Jan 7 12:52:01 PST 2019"
straykatz
@straykatz
Jan 07 20:59
@ecc1 sorry, that was not clear - so the result of root@DiaBrain:~# cgmupdate -b 1h -v
2019/01/07 12:58:43 PAPERTRAIL environment variable is not set
2019/01/07 12:58:44 connected to CC111x radio on /dev/spidev5.1
2019/01/07 12:58:44 setting frequency to 916.600
2019/01/07 12:58:45 model 522 pump
2019/01/07 12:58:45 CGM clock difference = 306.613946ms
2019/01/07 12:58:45 retrieving records since 2019-01-07 11:58:45
2019/01/07 12:58:49 stopping CGM history scan at 2019-01-07 11:54:00
2019/01/07 12:58:49 15 CGM records
2019/01/07 12:58:49 12 Nightscout entries from 2019-01-07 12:54:00 to 2019-01-07 11:59:00
[
{
"type": "sgv",
"date": 1546894440000,
"dateString": "2019-01-07T12:54:00-08:00",
"device": "openaps://DiaBrain",
"sgv": 226,
"direction": "Flat"
},
{
"type": "sgv",
"date": 1546894140000,
"dateString": "2019-01-07T12:49:00-08:00",
"device": "openaps://DiaBrain",
"sgv": 226,
"direction": "Flat"
},
{
however, no change on the loop:
Starting oref0-pump-loop at Mon Jan 7 12:57:03 PST 2019 with 30 second wait_for_silence:
MDT CGM configured; not waiting
Listening for 30s: .No interfering pump comms detected from other rigs (this is a good thing!)
Continuing oref0-pump-loop at Mon Jan 7 12:57:34 PST 2019
Preflight OK.
Attempting to retrieve MDT CGM data from pump
MDT CGM data retrieved
Profile less than 60m old; Profile valid. Pump history updated through 2019-01-07T12:39:42-08:00 with 0 new records; meal.json
Warning: setting mealCOB to 0 because currentDeviation is null/undefined
refreshed: {"carbs":30,"nsCarbs":30,"bwCarbs":0,"journalCarbs":0,"mealCOB":0,"currentDeviation":null,"maxDeviation":0,"minDeviation":999,"slopeFromMaxDeviation":0,"slopeFromMinDeviation":999,"allDeviations":[],"lastCarbTime":1546878013748,"bwFound":false}
Listening for 10s: .No interfering pump comms detected from other rigs (this is a good thing!)
Continuing oref0-pump-loop at Mon Jan 7 12:58:14 PST 2019
Checking that pump clock: "2019-01-07T12:58:16-08:00" is within 90s of current time: 2019-01-07T12:58:16-0800
Temp refreshed: monitor/temp_basal.json: {"duration":0,"temp":"absolute","rate":0}
{"carbs":30,"nsCarbs":30,"bwCarbs":0,"journalCarbs":0,"mealCOB":0,"currentDeviation":null,"maxDeviation":0,"minDeviation":999,"slopeFromMaxDeviation":0,"slopeFromMinDeviation":999,"allDeviations":[],"lastCarbTime":1546878013748,"bwFound":false}
Autotune exists! Hoorah! You can use microbolus-related features.
{"iob":1.238,"activity":0.0076,"basaliob":-0.003,"bolusiob":1.241,"netbasalinsulin":-0.55,"bolusinsulin":1.6,"time":"2019-01-07T20:58:18.000Z","iobWithZeroTemp":{"iob":1.238,"activity":0.0076,"basaliob":-0.003,"bolusiob":1.241,"netbasalinsulin":-0.55,"bolusinsulin":1.6,"time":"2019-01-07T20:58:18.000Z"},"lastBolusTime":1546893582000,"lastTemp":{"rate":0,"timestamp":"2019-01-07T08:36:29-08:00","started_at":"2019-01-07T16:36:29.000Z","date":1546878989000,"duration":30}}
{"delta":0,"glucose":116,"noise":null,"short_avgdelta":0.56,"long_avgdelta":-0.07,"date":1546875540000,"last_cal":0}
null
No deliverAt found.
{"reason":"If current system time Mon Jan 07 2019 12:58:29 GMT-0800 (PST) is correct, then BG data is too old. The last BG data was read 319.5m ago at Mon Jan 07 2019 07:39:00 GMT-0800 (PST). Temp 0 <= current basal 0.6U/hr; doing nothing. "}
Couldn't smb_verify_suggested
oref0-pump-loop failed. MDT CGM configured; not waiting
Unsuccessful oref0-pump-loop (BG too old) at Mon Jan 7 12:58:29 PST 2019
Eric
@ecc1
Jan 07 21:23
That command looked back 1 hour in pump history but only found 2 BG readings on that pump. Are there more, or are you having marginal comms with your Enlite sensor?
straykatz
@straykatz
Jan 07 21:24
is that what 1h means?
Eric
@ecc1
Jan 07 21:24
Oh, never mind, you didn't paste it all -- I see it says 15 records. Afraid I don't know what else to suggest (the oref loop is outside my expertise)
straykatz
@straykatz
Jan 07 21:25
OK, thank you for trying to help. I am trying to get the 0.6.2. loop back to work. :-)
I'll also try a different transmitter. that's another thing that might have changed. (not totally sure about that)
Evgeny Pakhomov
@eupakhomov
Jan 07 21:48
@renegadeandy Which error you have in logs now?
renegadeandy
@renegadeandy
Jan 07 22:25
@eupakhomov It was the same as yesterday , a pump history retrival error, Couldn't refresh_pumphistory_and_meal which we believe is linked to me at the time using a dual wave
Scott Leibrand
@scottleibrand
Jan 07 23:58
@renegadeandy that Couldn't refresh_pumphistory_and_meal is fairly generic: are there any other errors or warnings in the log along with that (when you don't have an extended bolus running)?