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

6th
Jan 2019
straykatz
@straykatz
Jan 06 00:16
thank you, Eric. I think so, but I should re-do it. Where is the correct CC1110 firmware?
hmm... I think I flashed the chip sitting on an Arduino board ... could that play a role?
the chip sitting, not me :)
Eric
@ecc1
Jan 06 00:21
Has it ever worked (i.e. with an earlier version of openaps)? What kind of rig is this?
straykatz
@straykatz
Jan 06 00:31
I'll reflash and see what happens.
renegadeandy
@renegadeandy
Jan 06 00:31
Sometimes my xdrip reports say 5.9, but my nightscout reports 6.1, for the same time period. Why might that be? xDrip calibrates, but I assume that xdrip sends to the nightscout the calibrated figures....?
straykatz
@straykatz
Jan 06 00:32
Edison/explorer rig. The board's previous owner had concerns about the board being OK. I'll re-do it and see what happens
renegadeandy
@renegadeandy
Jan 06 14:44

Hi all. Loop has been working well, and I setup the bluetooth link so it can access the network through my fone when I amout the house.

I left the house for maybe 3 hours, everything was fine, then I went to a coffee shop. The loop stopped, not sure why, the device was powered up, the phone was hooked up to the loop, but openaps seemed to stop

how can I figure out what happened?\
It could have potentially been the battery dieing, but I am sure it had > 40% left when I checked an hour or two before this happened
again, any tips on how to debug would be ace
Ebgineer
@Ebgineer
Jan 06 15:02
One possibility is if your phone switched from cell to wifi at the coffee shop and dropped the bluetooth connection. Battery is pretty likely too. For example, the pump can turn off radio communication but work otherwise to save power when the battery is low. When you connect to the rig, check the log to see what error messages you received at the time it stopped. What was your first indication that it stopped?
renegadeandy
@renegadeandy
Jan 06 15:14
i bolused and didn't see the marker on xdrip
where would i find the logs?
found em

I see this around the time:

Starting oref0-pump-loop at Sun Jan 6 13:03:02 GMT 2019 with 7 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. 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

There are lots of those

around that time, and the occasional message set which looks like this:

```Starting oref0-pump-loop at Sun Jan 6 13:13:02 GMT 2019 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 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. 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!)

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.414", 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 Jan 6 13:15:40 GMT 2019```

Ebgineer
@Ebgineer
Jan 06 15:17
and they started right at the time you noticed a problem
renegadeandy
@renegadeandy
Jan 06 15:18
so pulling from that, Couldn't refresh_pumphistory_and_meal this seems key
yeah
pretty certain its that time
Ebgineer
@Ebgineer
Jan 06 15:19
interesting the mmtune says the rig was able to communicate with the pump, just not pull the history
renegadeandy
@renegadeandy
Jan 06 15:20
then got a bunch of these :Listening for 40s silence before mmtuning: .No interfering pump comms detected from other rigs (this is a good thing!) mmtune: "868.438", 5, -71 waiting for 22 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. 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-06T13:39:55+00:00" is within 90s of current time: Sat Jan 1 00:04:25 GMT 2000 Pump clock is more than 55s 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... No! ntpd did not synchronize. 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!) Which may be because I rebooted the edison, and perhaps it couldn't set the time and therefore got a pump time mismatch
which is also odd, not sure why it wouldn't revert to the last timezone it booted with a connection
Ebgineer
@Ebgineer
Jan 06 15:20
It looks like you had a bolus running at the time
renegadeandy
@renegadeandy
Jan 06 15:21
yes i did
Ebgineer
@Ebgineer
Jan 06 15:23
likely a coincidence, the loop should continue after the bolus finishes. As you said, perhaps the edison lost its time on reboot then was unable to reach the time server to reset it.
Scott Leibrand
@scottleibrand
Jan 06 17:21
How did you reboot?
If you completely cut power to the rig, it loses track of time until it gets Internet again. If you use the black button, the clock is unaffected.
renegadeandy
@renegadeandy
Jan 06 17:22
I tried both
button
then it still didn;'t work
then i pulled the plug
viq
@viq
Jan 06 18:15
I'm looking to make it easier and less intrusive to be able to run openaps (mainly for autotune and such) on non-dedicated computer. As part of that I have a script that generates symlinks by the names that normal execution expects (for example ns-get.sh gets symlinked to ns-get). The question now is - should the merge request be for just the script, or also the created symlinks?
Scott Leibrand
@scottleibrand
Jan 06 18:18
symlinks are normally created by npm. have you tried adding them in package.json?
viq
@viq
Jan 06 18:19
They are added if you do global install, which I'm trying to avoid
With them created locally you're perfectly able to run autotune without ever touching anything as root (except of course system package installs)
Scott Leibrand
@scottleibrand
Jan 06 18:21
then I would not commit the symlinks, just the script that you can optionally run as an alternative to global-install
viq
@viq
Jan 06 18:21
ook
Thanks
viq
@viq
Jan 06 19:09
There, #1181
uh, no
renegadeandy
@renegadeandy
Jan 06 20:04
On NS on the OpenAPS pill, is there a description which explains '1 m ago:enacted' etc?
viq
@viq
Jan 06 21:31
What am I doing wrong?
$ oref0-upload-profile myopenaps/autotune/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)
renegadeandy
@renegadeandy
Jan 06 21:36
maybe something wrong in your profile json file
can you include that
viq
@viq
Jan 06 21:39
This is what autotune gave me
profile.json
Or should I be trying profile.pump.json ?
renegadeandy
@renegadeandy
Jan 06 21:41
i dont actually know what you are trying to do
i haven't ever called that file manually before
viq
@viq
Jan 06 21:43
I'm on AndroidAPS, so I don't have autotune, and I have to run it "out of band" so to say, on a computer. So I downloaded (and converted) the profile I'm using from nightscout, ran autotune on it and the data, and now I'm looking to upload it to nightscout so I can use it in AndroidAPS
As in the profile that autotune generated
renegadeandy
@renegadeandy
Jan 06 21:43
I am not sure, apologies I can't help here
renegadeandy
@renegadeandy
Jan 06 21:44
The problemis
either

profiledata.basalprofile.length < 1
profiledata.bg_targets.length < 1
profiledata.isfProfile.length

One of those 3 is null

which is throwing that error
im not sure which
maybe try to cross corelate the data in the profile to see if there is data missing
:)
good luck
viq
@viq
Jan 06 21:46
But is this about the profile in nightscout, or the profile I'm trying to upload?
renegadeandy
@renegadeandy
Jan 06 21:47
upload i believe
viq
@viq
Jan 06 21:49
Then indeed there are no bg_targets in there
renegadeandy
@renegadeandy
Jan 06 21:50
bingo
that's whats causing this error
not sure how you fix that though :)
i think
im off, gl
viq
@viq
Jan 06 21:51
Thanks!
renegadeandy
@renegadeandy
Jan 06 21:51
np ":)
viq
@viq
Jan 06 22:05
apparently not. Well, enough for tonight