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

6th
Aug 2018
Rob Neu
@robpneu
Aug 06 2018 03:47 UTC

I've built 2 edison rigs, one for my wife and one for her sister. They both have this issue and it's quite frustrating for us. Can someone explain to me why when BG is reading very high (200+ is very high for us) that oref0 thinks that BG is going to drop dramatically, from what can tell entirely based on a single very low delta (like -2 or -3)?

The main reason I ask is that it then decides to set a zero temp basal, which doesn't actually help them come down, and it doesn't seem to kill it until they start rising again. What setting I would change so it doesn't do this anymore (set a zero temp with such a small negative delta)? We've taken to just watching when they're high and manually cancelling any zero temps on the pump. 3 example NS screenshots from a few minutes ago and a half hour before are below.

1 - we'd just cancelled a zero temp (see the short 0 blip)
2 - It decided to set a temp of 0.9 (which is a much more reasonable response to a small negative delta), but which we also cancelled because she hadn't actually dropped much
3 - (30 minutes later) It finally realizes that zero temps aren't helping (probably because of the low positive delta) and sets a high temp to actually help.

Screen Shot 2018-08-05 at 9.05.26 PM.png
Screen Shot 2018-08-05 at 9.09.14 PM.png
Screen Shot 2018-08-05 at 9.39.01 PM.png
Scott Leibrand
@scottleibrand
Aug 06 2018 05:50 UTC
Don’t guess as to its reasoning: check the OpenAPS pill and the pump-loop.log on the rig. Also, run/check autotune and see if any of your settings seem to be off.
woodtrevor
@woodtrevor
Aug 06 2018 06:00 UTC
@wfeddern The builtin tether was never an option for me. And at the time no one else seemed to have a similar issue. So I used oref0-online as a skeleton, stripped out all of the normal bluetooth stuff, and then added what I needed to get easytether to work. I agree, for general use, the original tether code would need to remain in place since that is the route most people will take. Not sure how best to make them live side by side since I haven't looked at the stock oref0-online in some time. Does it seem reasonable to add an argument that would have it do easytether stuff instead, or would it make more since to have a separate script that could be substituted for those few of us who need a non-standard tethering solution?
iValkou
@iValkou
Aug 06 2018 09:09 UTC
How can I disable Explorer Hat screen?
Jens Heuschkel
@juehv
Aug 06 2018 10:41 UTC
@woodtrevor is your code available somewhere?
Jon Cluck
@cluckj
Aug 06 2018 12:11 UTC
@iValkou how disabled do you want it?
iValkou
@iValkou
Aug 06 2018 12:14 UTC
@cluckj The screen is on all the time. I want to turn it off to conserve battery power.
Jon Cluck
@cluckj
Aug 06 2018 12:22 UTC
It uses about 15mA
There's no toggle for it right now, so you'd have to go into the openaps-menu code and comment out everything but the voltage monitor and socket server in index.js, then remove updatedisplay from oref0-pump-loop.sh
Jon Cluck
@cluckj
Aug 06 2018 12:35 UTC
Next release will probably have a toggle 😉
Diabetic_Dude
@diabetic_dude_twitter
Aug 06 2018 13:19 UTC
is there an easy way to confirm a TI stick is working without a debugger? Someone sent me a stick and said it was pre configured. I have been testing with it for a few months, but can not seem to get it set up. When I run "ls -al /dev/tty*" with it plugged in and then unplugged, I get the same outputs. also when I run lsusb, I do not see it
Also when I plug it into my windows box, it is not seen in device manager
@diabetic_dude_twitter it will only show up under lsusb / ttyACM? if it was flashed with the USB version of the subg_rfspy firmware. If it was flashed with either the SPI or UART versions, you'll have to either re-flash it, or connect it using one of those methods instead. (I recommend connecting TI Sticks via SPI, because then your rig "looks like" an Explorer board setup to the rest of the software)
I'd say your checking on both Linux and Windows is a strong indicator that it has a different FW version, if any
Diabetic_Dude
@diabetic_dude_twitter
Aug 06 2018 13:58 UTC
thanks (it should have been flashed for the USB version )
Tom Boudreau
@tomasboudr
Aug 06 2018 13:58 UTC
@wfeddern I changed my NS pump battery low alert to 1.20 volts - I use amazon basics alkalines and they last for about a week (2 sometimes 3 set changes)
Diabetic_Dude
@diabetic_dude_twitter
Aug 06 2018 13:59 UTC
root
oops
Tore Bjørndalen
@BjoTore_twitter
Aug 06 2018 14:00 UTC
@ecc1 I enabled the the bolus wizard on my pump to test it for offline use. When I had to enterthe BG value it struck me that you did some work to send the BG value to the pump? Or am I totally mistaken?
Diabetic_Dude
@diabetic_dude_twitter
Aug 06 2018 14:06 UTC
@ecc1 Thank you again, I would be willing to bet this was flashed for UART since I got this when the edison boards were the standard things to have.
Diabetic_Dude
@diabetic_dude_twitter
Aug 06 2018 14:14 UTC
If anyone would be willing to re-flash this TI stick for me, I would be very grateful. The device I am building now is nothing more than a toy of sorts. I want to use a PI3B+ and a TI stick along with an Adafruit PiTFT Plus 320x240 2.8-inch TFT resistive touchscreen. This device will only be used at home and plugged in because of the power drain the PI3 and screen will cause.
I will also pay for shipping and time of course.
@BjoTore_twitter yes I wrote a stupid little program called "fakemeter" that sends a single BG value to the pump as if it were from a linked meter, so it shows up on the screen. Some folks have plumbed it into their loops "by hand", not sure if it's an option in the official install script. It's in the medtronic tarball that gets downloaded or compiled in the dev branch
(you have to register a meter ID of 0000000 on your pump to receive the BG values)
Ryan Dalisky
@rdalisky
Aug 06 2018 15:02 UTC
Anybody getting consistent preflight fails using mdt sensors on ‘Dev’?
jdunn42
@jdunn42
Aug 06 2018 15:13 UTC
Anyone else ever seen a pump battery reported as 3v? Switched pumps (to a 722) and the battery has reported as 3v ever sinse.
wfeddern
@wfeddern
Aug 06 2018 15:14 UTC
@woodtrevor after you run easytether, are you getting an IP assigned to the device? I am just seeing :
3: tun-easytether: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN group default qlen 500
link/none
inet 192.168.117.0 peer 192.168.117.1/31 scope global tun-easytether
valid_lft forever preferred_lft forever
I can ping the 192.168.117.1 address, but not sure how/if I can ssh back into my rig from phone once wifi is off to verify things are working.
Jon Cluck
@cluckj
Aug 06 2018 15:22 UTC
@diabetic_dude_twitter if it's flashed for UART, you can still wire it up
@diabetic_dude_twitter https://github.com/oskarpearson/mmeowlink/wiki/TI-USB-Stick-over-Serial#raspberry-pi-with-full-40-pin-gpio-header <-- wiring instructions, then you can compile mdt for UART :)
Diabetic_Dude
@diabetic_dude_twitter
Aug 06 2018 16:29 UTC
@cluckj but if I do that, I was under the impression that I would not be able to use the Adafruit PiTFT Plus 320x240 2.8-inch TFT resistive touchscreen because they both use the same pens. (I hope I am wrong)
Dana Lewis
@danamlewis
Aug 06 2018 16:47 UTC
@BjoTore_twitter be careful about sending BGs: you don't want bolus wizard to correct for BGs because OpenAPS is already doing so
I think @alimhassam added something to filter out the ones from that special meter ID 000000, iirc
Dana Lewis
@danamlewis
Aug 06 2018 16:56 UTC
So it's not going into bolus wizard?
If you use bolus wizard on the pump, it probably presets the BG value to what it most recently received, so you have to remember to change that if needed. But the openaps code doesn't use the BGReceived records from the pump history anywhere as far as I can see in the dev branch. So now I've confused myself; not sure whether filtering was ever necessary?
Jon Cluck
@cluckj
Aug 06 2018 17:18 UTC
@diabetic_dude_twitter it looks like you can share the pins?
yes, it looks like that TFT uses SPI and I2C plus 2 other GPIOs, none of which conflict with UART connection
Dana Lewis
@danamlewis
Aug 06 2018 17:48 UTC
Right - OpenAPS won't use it, but most people forget if they enter or receiver a BG and cause a double correction via the BW then get confused when OpenAPS is low temping or doing something else
So generally I tell people not to do that if they are not willing to be diligent about clearing that out in BW every time
Scott Leibrand
@scottleibrand
Aug 06 2018 18:03 UTC
Another workaround would be a high max_bg target on the pump bolus wizard settings.
@ecc1 perhaps the filtering was so that OpenAPS wouldn’t re-upload the MBG to NS?
alimhassam
@alimhassam
Aug 06 2018 18:18 UTC
That's right. On the filtering, but its not needed right now because openAps.jq hides BGCapture records now. For bolus wizard isdue what I do is I use a high upper value since openaps only uses the low value as target.
Diabetic_Dude
@diabetic_dude_twitter
Aug 06 2018 18:34 UTC
thank you @cluckj and @ecc1
Car
@cyborgpancreas_twitter
Aug 06 2018 19:28 UTC
Hi guys-having issues with the log after installing the program-I actually had a heck of a time even being able to log back into th rig at first. When I put l into the terminal it says there is no file or directory. I thought at first it was because I hadn’t been actually using the pump—but still getting nothing. I’m actuallt not at my setup now—but any help is appreciated for me to go back and do late! TIA!
Dana Lewis
@danamlewis
Aug 06 2018 19:36 UTC
@cyborgpancreas_twitter thanks for hopping over here! usually if you get no file or directory, it means you are not inside myopenaps - next time you're at the rig, try cd myopenaps first. but l for logs should work when you first log in, without having to be inside of myopenaps. so if that persists - yes, I'd try re-running the setup script (http://openaps.readthedocs.io/en/latest/docs/Build%20Your%20Rig/OpenAPS-install.html#step-4-setup-script shows you how to run just the setup script part),
woodtrevor
@woodtrevor
Aug 06 2018 19:37 UTC
@juehv No, not at the moment. I'd be happy to share later when I can properly access my rig from a computer. Do you have specific questions about setting up the tether or are you more interested in how I automated the switching back and forth between it and wifi?
Car
@cyborgpancreas_twitter
Aug 06 2018 19:38 UTC
@danamlewis
Thank you! I will definitely give that a shot and if it doesn’t work I’ll hop back on here! Thank you so much!
Dana Lewis
@danamlewis
Aug 06 2018 19:41 UTC
:+1:
woodtrevor
@woodtrevor
Aug 06 2018 19:50 UTC
@wfeddern Sorry, I wasn't thinking and should have mentioned that. The pair will always get the .0 and .1 addresses. Easytether acts as a bridge between the rig and the net but doesn't appear to make android aware of the tethered interface. This means you can get out to the net from the rig but can't directly access the rig from the phone. It might be worth approaching the dev to see if they can/are willing to make the tethered device accessible from the phone... I've made it work by monitoring externally from NS/papertrail. For the rare cases when I need to access the rig when I'm not on home wifi I carry an otg cable and can get in from my phone using a serial console app.
@juehv Also see the note above. ^
Tim Street
@tim2000s
Aug 06 2018 21:07 UTC
@danamlewis - on yesterday’s issue, doesn’t the script for Pi pull dev anyway?
@woodtrevor - not having rig access on the go from the phone may well be a dealbreaker for quite a few of us. For me (don’t know about others) I generally ssh into my rig from the tethered phone more than anywhere else, because it’s convenient and because I can do it on the commute/ when away from the desk at work.
marafie
@marafie
Aug 06 2018 21:22 UTC
hello

`Starting oref0-pump-loop at Tue 7 Aug 00:13:05 +03 2018 with 4 second wait_for_silence:
Waiting up to 4 minutes for new BG: First loop: not waiting

Listening: .No interfering pump comms detected from other rigs (this is a good thing!)
Continuing oref0-pump-loop at Tue 7 Aug 00:13:08 +03 2018

Preflight fail. Retry 1 of preflight
Preflight fail. Listening: .No interfering pump comms detected from other rigs (this is a good thing!)
Continuing oref0-pump-loop at Tue 7 Aug 00:13:14 +03 2018

Retry 2 of preflight
Preflight fail. Listening: .No interfering pump comms detected from other rigs (this is a good thing!)
Continuing oref0-pump-loop at Tue 7 Aug 00:13:17 +03 2018

Retry 3 of preflight
Preflight fail. Couldn't preflight
oref0-pump-loop failed. pump_loop_completed more than 15m old; waiting for 12 s silence before mmtuning
Listening: .No interfering pump comms detected from other rigs (this is a good thing!)
Continuing oref0-pump-loop at Tue 7 Aug 00:13:30 +03 2018

Listening for 12 s silence before mmtuning: Listening: .No interfering pump comms detected from other rigs (this is a good thing!)
Continuing oref0-pump-loop at Tue 7 Aug 00:13:31 +03 2018`

i am getting this error after running runagain
marafie
@marafie
Aug 06 2018 21:29 UTC
any idea how can i solve it
i am using the new hat
Tim Street
@tim2000s
Aug 06 2018 22:38 UTC
When I installed the pi+hat it took a little longer to get going than the Edison did.
Martin Haeberli
@mhaeberli
Aug 06 2018 23:04 UTC
ok - beginning to think about offline G5 use, but it looks so complicated - because - ideally, I’d like to keep on using the Dexcom iOS app, but just feed data offline if no internet connectivity. looks like that won’t fly. (raises the question - WHY won’t it fly?) I gather with Loop / RileyLink we can keep using the Dexcom iOS app. Is there a real or theoretical possibility of building a really small application for iOS that spys on G5 CGM data and relays it via Bluetooth / IP back to the rig? Has anyone done this? Can we offline loop with Spike? Yes, we COULD use a receiver, but also complicated. Ideally would like something easy to do with minimum user burden… (Which sadly had me thinking switch over to Loop.) thoughts welcome
alimhassam
@alimhassam
Aug 06 2018 23:27 UTC
@mhaeberli have you tried xdrip-js ?
Martin Haeberli
@mhaeberli
Aug 06 2018 23:28 UTC
not yet - but docs say I can’t use it in conjunction with Dexcom app … :-(
alimhassam
@alimhassam
Aug 06 2018 23:45 UTC
I think it works for some people. Its able to use Dexcom internal calibration if that's why you want Dexcom app.
Otherwise If its because you prefer Dexcom app for other reasons then you could use it just when it's time to calibrate for example. Or you might be lucky and may be able to make it work side by side.
Martin Haeberli
@mhaeberli
Aug 06 2018 23:51 UTC
@alimhassam thx - actually wanted both initially for minimum hassle so data can still flow through Share when internet is available, minimum user interface changes - ideally, we would just have opportunistic changeover to offline looping when internet goes away.