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

30th
Jun 2018
tepidjuice
@tepidjuice
Jun 30 2018 11:22
ns-loop does not appear to be getting the bg data from nightscout loop is uploading the pump data but not getting any bg information.
running dev branch
tepidjuice
@tepidjuice
Jun 30 2018 11:51
Getting 'cgm data unchanged for the past 45 mins' but last-glucose.json and ns-glucose.json has all the recent data.
garykidd
@garykidd
Jun 30 2018 12:14
next step oref1....
@tepidjuice mlab size stats under limits?
tepidjuice
@tepidjuice
Jun 30 2018 12:17
it should be getting the data from xdrip aps anyway
which it is.
@garykidd Also is there a way to clear mlab database without going to mlab?
tepidjuice
@tepidjuice
Jun 30 2018 14:10
I'm very confused now. Pump and rig are talking as boluses are appearing in NS and cgm data is up to date in xdrip/glucose.json and cgm/glucose.json
Jon Cluck
@cluckj
Jun 30 2018 14:18
@tepidjuice are they in the right order?
(newest BG record should be at the top of glucose.json)
tepidjuice
@tepidjuice
Jun 30 2018 14:23
@cluckj yes.
In the cgm folder they are the wrong way round but in the xdrip folder they are in the correct order...
So no I guess.
Jon Cluck
@cluckj
Jun 30 2018 14:25
iirc @cascer1 had this issue around 5/22
tepidjuice
@tepidjuice
Jun 30 2018 14:25
Is there a solution?
Jon Cluck
@cluckj
Jun 30 2018 14:26
yes :) I can't do a log search right now
tepidjuice
@tepidjuice
Jun 30 2018 14:26
How do I do a log search>
?
Jon Cluck
@cluckj
Jun 30 2018 14:35
lol, the solution was to not use xdripaps?
tepidjuice
@tepidjuice
Jun 30 2018 14:37
Yes seems like it but I need to be offline!
I've tried deleting ns-get-bg from ns-loop
and I've cleaned all glucose.json files except for the xdrip one
tepidjuice
@tepidjuice
Jun 30 2018 14:44
ok monitor/glucose.json seems to be in the correct order now.
Jon Cluck
@cluckj
Jun 30 2018 14:44
hmm, which branch are you using?
tepidjuice
@tepidjuice
Jun 30 2018 14:44
dev-0.6.
2
Jon Cluck
@cluckj
Jun 30 2018 14:44
ah okay
tepidjuice
@tepidjuice
Jun 30 2018 14:45
seems like I'm getting radio errors as well :/
Jon Cluck
@cluckj
Jun 30 2018 14:46
what kinds?
tepidjuice
@tepidjuice
Jun 30 2018 14:47
'Setting pump time to Sun Jul 1 00:41:35 AEST 2018
IndexError: bytearray index out of range
Error: pump clock refresh error / mismatch
oref0-pump-loop failed. pump_loop_completed more than 15m old; waiting for 40s silence before mmtuning
Radio ok. Listening: .No interfering pump comms detected from other rigs (this is a good thing!)
Listening for 40s silence before mmtuning: .No interfering pump comms detected from other rigs (this is a good thing!)
mmtune: "916.660", 5, -58 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 Jul 1 00:43:23 AEST 2018
'
Jon Cluck
@cluckj
Jun 30 2018 14:52
is that repeating over and over again?
tepidjuice
@tepidjuice
Jun 30 2018 14:53
yes
Jon Cluck
@cluckj
Jun 30 2018 14:55
is the battery in your pump okay? not being able to set the pump clock is usually indicative of bad comms
tepidjuice
@tepidjuice
Jun 30 2018 14:56
Has three bars. So yes...
I can change the battery and see.
Jon Cluck
@cluckj
Jun 30 2018 15:00
:thumbsup:
tepidjuice
@tepidjuice
Jun 30 2018 15:02
Hasn't solved it :(
Still has the same issure
tepidjuice
@tepidjuice
Jun 30 2018 15:09
I ran oref0-radio-reboot manually and the radio errors have stopped.
Jon Cluck
@cluckj
Jun 30 2018 15:09
(whew, I was at a bit of a loss)
tepidjuice
@tepidjuice
Jun 30 2018 15:10
Actually... maybe not.
Sorry
Jon Cluck
@cluckj
Jun 30 2018 15:10
haha
same error, or different error?
tepidjuice
@tepidjuice
Jun 30 2018 15:10
I think running it manually just reset a config file somewhere
Same error,
Should I try a different branch
tepidjuice
@tepidjuice
Jun 30 2018 15:16
'''Starting oref0-pump-loop at Sun Jul 1 01:11:02 AEST 2018 with 18 second wait_for_silence:
Waiting up to 4 minutes for new BG: ls: cannot access /tmp/pump_loop_completed: No such file or directory
Radio ok. Listening: .No interfering pump comms detected from other rigs (this is a good thing!)
Preflight OK. Old pumphistory-24h, waiting for 18 seconds of silence: Radio ok. Listening: .No interfering pump comms detected from other rigs (this is a good thing!)
Old pumphistory-24h refreshed
Profile less than 60m old; Profile valid. Refreshed pumphistory and meal.json
Checking pump clock: "2018-07-01T01:13:43+10:00" is within 90s of current time: Sun Jul 1 01:13:46 AEST 2018
Error: pumphistory too old
oref0-pump-loop failed. pump_loop_completed more than 15m old; waiting for 40s silence before mmtuning
Radio ok. Listening: .No interfering pump comms detected from other rigs (this is a good thing!)
Listening for 40s silence before mmtuning: .No interfering pump comms detected from other rigs (this is a good thing!)
mmtune: "916.660", 5, -53 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 Jul 1 01:15:27 AEST 2018
''''
It's weird it's still uploading pump data to NS.
but not reliably I think.
Anyway I need to sleep.
Jon Cluck
@cluckj
Jun 30 2018 15:18
that's a different error
it looks like it was finally able to set the clock
tepidjuice
@tepidjuice
Jun 30 2018 15:19
It looks like radio comms are happening but unreliably. So either a hardware problem which I don't know how to check for/fix. Or some software bug.
Jon Cluck
@cluckj
Jun 30 2018 15:20
how long were you not looping?
tepidjuice
@tepidjuice
Jun 30 2018 15:21
A while... Probably about 3 weeks.
Jon Cluck
@cluckj
Jun 30 2018 15:21
oh
you might not have any pump history for the last 24 hours :)
tepidjuice
@tepidjuice
Jun 30 2018 15:22
Is there a fix?
Jon Cluck
@cluckj
Jun 30 2018 15:22
set a temp basal, add a small bolus or something
the pumphistory too old thing is because the last record it's pulling from your pump is probably very very old
tepidjuice
@tepidjuice
Jun 30 2018 15:24
It's uploaded some temp-basals and boluses to NS within the last 24 -hrs
Jon Cluck
@cluckj
Jun 30 2018 15:29
were they ones that you set?
the issue may self-resolve once your pumphistory is new enough
tepidjuice
@tepidjuice
Jun 30 2018 15:31
Yes they were
tepidjuice
@tepidjuice
Jun 30 2018 15:37
definitely looks like unreliable radio comms.
I have to get some sleep. Might try trouble shooting again tomorrow.
Jon Cluck
@cluckj
Jun 30 2018 15:38
:thumbsup:
it may self resolve overnight
tepidjuice
@tepidjuice
Jun 30 2018 15:38
'Starting oref0-pump-loop at Sun Jul 1 01:35:02 AEST 2018 with 20 second wait_for_silence:
Waiting up to 4 minutes for new BG: ls: cannot access /tmp/pump_loop_completed: No such file or directory
Radio ok. Listening: .No interfering pump comms detected from other rigs (this is a good thing!)
Preflight OK. Old settings: Pump profile refreshed; Could not parse autotune_data
Settings refreshed; Profile valid. Refreshed pumphistory and meal.json
Checking pump clock: "2018-07-01T01:35:42+10:00" is within 90s of current time: Sun Jul 1 01:37:30 AEST 2018
Pump clock is more than 55s off: attempting to reset it
Waiting for ntpd to synchronize... OK!
Setting pump time to Sun Jul 1 01:37:32 AEST 2018
Error: pump clock refresh error / mismatch
oref0-pump-loop failed. pump_loop_completed more than 15m old; waiting for 40s silence before mmtuning
Radio ok. Listening: .No interfering pump comms detected from other rigs (this is a good thing!)
Listening for 40s silence before mmtuning: .
'
and a 0.1u bolus from the pump which I delivered 5 mins ago appeared on NS
Jon Cluck
@cluckj
Jun 30 2018 15:39
wow, that's a lot of clock drift
tepidjuice
@tepidjuice
Jun 30 2018 15:40
Also I'll turn the rig off overnight I don't want it to start/stop working while I'm asleep.
Thanks.
PCTamer
@PCTamer
Jun 30 2018 20:00
is there a way i can remove openaps and start over? no install info in troubleshooting
Zakm0n
@Zakm0n
Jun 30 2018 20:22
Anyone else get the mlab maintenance email?
PCTamer
@PCTamer
Jun 30 2018 20:46
nope i didn't
are they shutting down for maintainence?
JohnDoeAkira
@JohnDoeAkira
Jun 30 2018 20:57
And they are switching to another version of mongo ... no idea wether this is a problem.
Caleb Seekell
@musicman0329
Jun 30 2018 21:10
Using a hat/pi rig. On the oref0 interactive setup (0.7.0 dev), which one do I pick?
Would you like to [D]ownload precompiled Go pump communication library or build them from [S]ource? [D]/S
PCTamer
@PCTamer
Jun 30 2018 21:30
not looking forward to changing / updating that if i have to. i'm still installing openaps for the 100th time i think.
but i have NS up etc.. just not edison yet
marafie
@marafie
Jun 30 2018 21:36
Hi
How is that the insulin duration calculated in the open aps? My kid toke 2 units of insulin and after 2.5 hours it mentions that the iob is 0.01u
Jon Cluck
@cluckj
Jun 30 2018 21:36
@musicman0329 download
Caleb Seekell
@musicman0329
Jun 30 2018 21:38
@cluckj thanks
N3FM
@N3FM
Jun 30 2018 22:06
@tepidjuice @cluckj Tepidjuice's clock drift is (I think) just a 'missed clock update'... and it's re-reading the old clock entry. It happens for me from time to time... (and triggers the 'failing' clock update in set-device-clocks.sh for me!) My pump clock will agree within 2 seconds for an hour, and then boom! it's off and being reset... (722/Enlite/Edison/Explorer/0.6.2 master) One more reason I'm excited about 0.7.0!
Ebgineer
@Ebgineer
Jun 30 2018 22:15
@marafie this docs page might help explain DIA (duration of insulin activity).