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

20th
Feb 2018
fidoman
@efidoman
Feb 20 2018 00:06
@tim2000s - sometimes I have to remove /root/src/oref0, reclone it, and then global-install again. I had a similar error with dpkg and I ended up resolving it by purging the package it was complaining about and then re-running global-install and oref0 install. Not sure either of these methods will fix your issue though.
mariano42
@mariano42
Feb 20 2018 01:28
@tazitoo thanks for the suggestion, unfortunately it didn't work.
its been awhile since I setup my Edison, need to reflash it and running into something I haven't been able to find an answer for in the docs. I can putty into it using a serial connection, but it never "wakes"up.. I never get the edison command line. I am not sure if that is because it already is flashed (just a corrupt filesystem right now), or if this means my connection is no good. I was going to try the flashall step and see if that tells me anything else about the connection but I was a little worried about going rogue from the documentation. anyone have any advice?
alimhassam
@alimhassam
Feb 20 2018 01:32
@mariano42 did you try pressing "enter" ?
mariano42
@mariano42
Feb 20 2018 01:34
yes, sorry I should have mentioned that. Multiple times, but nothing happens
Scott Leibrand
@scottleibrand
Feb 20 2018 01:36
try power-cycling it with the black button while connected over console
plug in console, and once you have the black screen, hold down the black button for 10s until the red LED between the microUSB ports goes off, then press it again for 2s or so until that comes back on
when the Edison starts booting, you should see the boot sequence. if you don't, it's a cable or other hardware issue.
mariano42
@mariano42
Feb 20 2018 01:39
@scottleibrand ok, i did that and restarted my putty session that went inactive when i power cycled (I assume thats required because putty didnt restore the session). Now it came back with only:
▒*B0100000063f694
Cfomodz
@Cfomodz
Feb 20 2018 01:45
Is there a straight forward way to transition into using the dev branch?
mariano42
@mariano42
Feb 20 2018 01:50
@scottleibrand here is one thing I noticed.. despite the fact I can connect to it and see it in my device manager, it doesn't show up as a drive in windows explorer. I figured my autoplay settings were just off so I didn't see the pop up, but that doesn't appear to be the case. Do you think that matters even though I see it as a device?
Scott Leibrand
@scottleibrand
Feb 20 2018 02:00
@Cfomodz there's a section in the docs on upgrading
@mariano42 there are two microUSB ports. the one labeled UART gives you serial console. the one labeled OTG creates the mountable drive on your computer. if you are only plugged into UART you shouldn't see a drive.
your putty session should not die when you power down the Edison if you're plugged into the UART port (the chip sending console data is powered by the console port itself, not by the Edison)
you might try unseating the Edison from the Explorer Board and reseating it, and re-plug / replace all the USB cables you're using
mariano42
@mariano42
Feb 20 2018 02:04
@scottleibrand ok, i have tried a handful of cables, but I will try re-seating. I assume since I can get in to the serial console at all that my UART connection is OK, but my OTG isn't and that's why I don't see the drive.
Scott Leibrand
@scottleibrand
Feb 20 2018 02:05
are you doing this with two cables connected, or just the UART one?
mariano42
@mariano42
Feb 20 2018 02:05
two cables
Scott Leibrand
@scottleibrand
Feb 20 2018 02:05
if the Edison software is borked and it needs reflashed, that can also account for the lack of a mountable drive
but that shouldn't affect your ability to console (including through an Edison reboot)
the console stuff is lower-level than the OS you flash onto the Edison
mariano42
@mariano42
Feb 20 2018 02:10
I am thinking my cables are ok. When I am plugging and unplugging either cable my laptop is certainly recognizing a change (that fun windows device .wav). I did not realize that about putty, I figured that losing power would make the session inactive and you would have to restart it.
jzycom123
@jzycom123
Feb 20 2018 02:31
11'
1
1
双色球开奖结果😊
Tim Street
@tim2000s
Feb 20 2018 06:35
Thanks @efidoman - one for later today.
Debby Muskar
@debbymuskar
Feb 20 2018 14:01
Hello all. I haven't been here in a while, but I need some help with my bluetooth setup. Is anyone free for a few minutes?
root@debbymuskar:~# sudo /usr/local/bin/bluetoothd --experimental & [1] 18531 root@debbymuskar:~# bluetoothctl [NEW] Controller 58:A8:39:01:13:20 BlueZ 5.47 [default] [NEW] Device 00:B3:62:8D:5F:FB DM Work iPhone Agent registered [bluetooth]# bluetoothctl Invalid command [bluetooth]# power off Changing power off succeeded [bluetooth]# power on [CHG] Controller 58:A8:39:01:13:20 Class: 0x00000110 Changing power on succeeded [CHG] Controller 58:A8:39:01:13:20 Powered: yes [bluetooth]# exit Agent unregistered [DEL] Controller 58:A8:39:01:13:20 BlueZ 5.47 [default] root@debbymuskar:~# sudo hciconfig hci0 name $HOSTNAME root@debbymuskar:~# bluetoothctl [NEW] Controller 58:A8:39:01:13:20 debbymuskar [default] [NEW] Device 00:B3:62:8D:5F:FB DM Work iPhone Agent registered [bluetooth]# pair 00:B3:62:8D:5F:FB Attempting to pair with 00:B3:62:8D:5F:FB Failed to pair: org.bluez.Error.AuthenticationCanceled [bluetooth]# remove 00:B3:62:8D:5F:FB [DEL] Device 00:B3:62:8D:5F:FB DM Work iPhone Device has been removed [bluetooth]# exit Agent unregistered [DEL] Controller 58:A8:39:01:13:20 debbymuskar [default] root@debbymuskar:~# bluetoothd --version 5.47 root@debbymuskar:~# sudo service cron stop root@debbymuskar:~# sudo killall bluetoothd root@debbymuskar:~# sudo killall bluetoothd bluetoothd: no process found [1]+ Done sudo /usr/local/bin/bluetoothd --experimental root@debbymuskar:~# sudo /usr/local/bin/bluetoothd --experimental & [1] 18564 root@debbymuskar:~# sudo hciconfig hci0 name $HOSTNAME Can't change local name on hci0: Network is down (100) root@debbymuskar:~# bluetoothctl [NEW] Controller 58:A8:39:01:13:20 BlueZ 5.47 [default] Agent registered [bluetooth]# power off Changing power off succeeded [bluetooth]# power on [CHG] Controller 58:A8:39:01:13:20 Class: 0x00000110 Changing power on succeeded [CHG] Controller 58:A8:39:01:13:20 Powered: yes [bluetooth]# exit Agent unregistered [DEL] Controller 58:A8:39:01:13:20 BlueZ 5.47 [default] root@debbymuskar:~# sudo hciconfig hci0 name $HOSTNAME root@debbymuskar:~# bluetoothctl [NEW] Controller 58:A8:39:01:13:20 debbymuskar [default] Agent registered [bluetooth]# power off Changing power off succeeded [CHG] Controller 58:A8:39:01:13:20 Powered: no [CHG] Controller 58:A8:39:01:13:20 Discovering: no [CHG] Controller 58:A8:39:01:13:20 Class: 0x00000000 [bluetooth]# power on [CHG] Controller 58:A8:39:01:13:20 Class: 0x00000110 Changing power on succeeded [CHG] Controller 58:A8:39:01:13:20 Powered: yes [bluetooth]# discoverable on Changing discoverable on succeeded [CHG] Controller 58:A8:39:01:13:20 Discoverable: yes [bluetooth]# scan on Discovery started [CHG] Controller 58:A8:39:01:13:20 Discovering: yes [NEW] Device 48:E0:3B:86:C8:50 48-E0-3B-86-C8-50 [NEW] Device 4B:AC:74:E3:C0:DF 4B-AC-74-E3-C0-DF [NEW] Device E4:24:61:BC:13:21 Charge 2 [NEW] Device C4:46:89:5E:1C:AC Charge 2 [NEW] Device 40:69:AB:D6:AC:7B 40-69-AB-D6-AC-7B [NEW] Device 00:B3:62:8D:5F:FB DM Work iPhone [NEW] Device 74:DF:BF:D4:89:0A CA0419W01324 [bluetooth]# agent on Agent is already registered [NEW] Device C4:23:A8:07:20:33 C4-23-A8-07-20-33 [CHG] Device 48:E0:3B:86:C8:50 AdvertisingFlags: 1a . [CHG] Device 48:E0:3B:86:C8:50 AdvertisingFlags: 00 . [CHG] Device 4B:AC:74:E3:C0:DF AdvertisingFlags: 00 . [CHG] Device C4:23:A8:07:20:33 Name: Forerunner 35 [CHG] Device C4:23:A8:07:20:33 Alias: Forerunner 35 [CHG] Device C4:23:A8:07:20:33 ServiceData Key: 00003e10-0000-1000-8000-00805f9b34fb [CHG] Device C4:23:A8:07:20:33 ServiceData Value: 00 12 00 ... [CHG] Device C4:23:A8:07:20:33 AdvertisingFlags: 00 . [CHG] Device E4:24:61:BC:13:21 RSSI: -90 [CHG] Device E4:24:61:BC:13:21 AdvertisingFlags: 06 . [CHG] Device E4:24:61:BC:13:21 AdvertisingFlags: 00 . [bluetooth]# default-agent
mariano42
@mariano42
Feb 20 2018 15:49
@scottleibrand I switched PC's that I was working on and I was able to get this thing flashed and run oref0-setup. I read somewhere that some anti-virus software can block the serial connection, never heard of that before, but it must have been something along those lines. Thanks again for your help. New issues now with my loop, but I am going to take a stab at them before posting questions.
Tim Street
@tim2000s
Feb 20 2018 18:47
Well @scottleibrand @efidoman that was a curious issue. Turns out the reason for the failure on bluez was an old version of bluez hanging around in the background. An “apt-get remove bluez” cleared it out and allowed a fresh install.
Scott Leibrand
@scottleibrand
Feb 20 2018 18:50
k. did that come from following directions, or from something you'd done manually earlier while developing?
Peter Kok
@kretep
Feb 20 2018 18:57
I'm trying to get openaps running on a rpi3 with the carelink stick, but I get the error below in the pump-loop log. I can successfully connect to the pump using the openaps use commands to get data or send commands. I followed the interactive installation procedure. Is there anything else I need to configure to get the loop to work?
...........................Couldn't wait_for_silence 14
oref0-pump-loop failed. pump_loop_completed more than 15m old; waiting for 40s silence before mmtuning
ImportError: No module named spi_serial

Radio check failed. ImportError: No module named spi_serial
Listening for 40s silence before mmtuning: ................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................mmtune: KeyError: 'mmtune'
Usage: grep [OPTION]... PATTERN [FILE]...
Try 'grep --help' for more information.
Usage: grep [OPTION]... PATTERN [FILE]...
Try 'grep --help' for more information.
No wait required.
Listening: .......................................................................................
Dana Lewis
@danamlewis
Feb 20 2018 18:57
@kretep carelink is not currently supported right now - you'll need a TI stick or similar radio stick instead, or one of the upcoming Pi HATs that has built in radio
Peter Kok
@kretep
Feb 20 2018 19:00
@danamlewis Thanks for your reply. I ordered my parts, but I was just trying to set something up with the carelink stick while I wait for those. Is there any old version that can still be used with the carelink stick?
Scott Leibrand
@scottleibrand
Feb 20 2018 19:06
carelink can be used, but it's not supported by an of the automated setup scripts, so requires a lot of knowledge to get working right. if you'd like to dive into the old docs about how things used to be set up, you might be able to figure that out (and maybe even see where in the setup scripts things could be tweaked to work with Carelink), but it's not something that the rest of us have wanted to spend time on due to the really awful range of the Carelink sticks.
Peter Kok
@kretep
Feb 20 2018 19:26
Thanks, I'll give it a go. Any pointers on where to focus on in the configuration / code are welcome!
Scott Leibrand
@scottleibrand
Feb 20 2018 19:29
I'd compare the openaps aliases (which are still around but unused) to what oref0-pump-loop is doing. you might be able to get it working entirely using the alises, but it'd be better long-term if you could port over the old carelink logic (where oref0-setup used to set up the aliases differently for Carelink) into oref0-pump-loop.
Thacher
@thacherT1D
Feb 20 2018 19:45
I'm looping, but NS doesn't think I am... makes no sense because OpenAPS needs the BG #s (which are showing) from NS... any troubleshooting ideas? (I've already rebooted, I'm ssh-ed into my rig to confirm that it's looping locally)
Scott Leibrand
@scottleibrand
Feb 20 2018 19:49
there's a troubleshooting section in the docs for that. devicestatus (pill and purple line) uploads are completely separate from entries (CGM data) and treatments (boluses and temp basals).
Thacher
@thacherT1D
Feb 20 2018 20:04
thanks Scott -- I'll go back to the docs
Deweyoxberg
@Deweyoxberg
Feb 20 2018 20:23
Question please: would the safety setting of max IOB = 0 prevent OpenAPS from handling a high?
Currently at 300 flat and 0.65u IOB, aps seems to not add anymore units to combat the high.
Deweyoxberg
@Deweyoxberg
Feb 20 2018 20:29
Also if that's the case, can the rig be updated by editing a file or does the whole setup need to be run again?
no, just edit your preferences if you want to adjust it
Deweyoxberg
@Deweyoxberg
Feb 20 2018 20:30
Thanks Dana. Figured that was the case. :)