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

26th
Jan 2018
garykidd
@garykidd
Jan 26 2018 00:08
 Dont think so. 
garykidd
@garykidd
Jan 26 2018 00:17
All I did was update to the latest 10th and run again
Heading home now to see if it will work on my home network or whether I can isolate the problem to my hotspot off my phone
Dirk Gastaldo
@dirkgastaldo
Jan 26 2018 00:27
Do you know why I my rig on master would have two IPs?
blob
garykidd
@garykidd
Jan 26 2018 01:09
so took awhile but clocks synchronized at home. wouldnt do it all day when connected thru BT phone hotspot...it did have internet access though. can only loop at home. any idea what I can troubleshoot?
or how I can troubleshoot?
rather
hmmm I take that back---looks like a different rig set my temp which confused me--it's rather far away.
```/
Starting oref0-pump-loop at Thu Jan 25 20:10:02 EST 2018 with 4 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 4 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 Warning: setting mealCOB to 0 because currentDeviation is null/undefined and meal.json Checking pump clock: "2018-01-23T21:01:33-05:00" is within 90s of current time: Thu Jan 25 20:10:39 EST 2018 Pump clock is more than 55s off: attempting to reset it Waiting for ntpd to synchronize... OK! Setting pump time to Thu Jan 25 20:10:39 EST 2018 serial.serialutil.SerialException: Attempting to use a port that is not open Setting CGM time to Thu Jan 25 20:10:41 EST 2018 AttributeError: 'NoneType' object has no attribute 'ReadSystemTime' 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: ........................../
mkericson
@mkericson
Jan 26 2018 14:22
I bought a Mouser 915MHZ antenna and tried it on my rig. when I rebooted I got a radio error when trying to mmtune to see how it changed. Couldn't get the mmtune to run. So I took it off and rebooted. But I still get this error:
mmtune: pump://JSON/mmtune/monitor/mmtune.json
monitor/mmtune.json raised /dev/spidev5.1 already in use
Traceback (most recent call last):
File "/usr/local/bin/openaps-report", line 82, in <module>
app( )
File "/usr/local/lib/python2.7/dist-packages/openaps/cli/init.py", line 51, in call
self.run(self.args)
File "/usr/local/bin/openaps-report", line 75, in run
output = app(args, self)
File "/usr/local/lib/python2.7/dist-packages/openaps/cli/subcommand.py", line 52, in call
return self.method.main(args, app)
File "/usr/local/lib/python2.7/dist-packages/openaps/reports/invoke.py", line 40, in main
output = task.method(args, app)
File "/usr/local/lib/python2.7/dist-packages/openaps/uses/use.py", line 44, in call
self.before_main(args, app)
File "/usr/local/lib/python2.7/dist-packages/openaps/vendors/medtronic.py", line 62, in before_main
self.setup_medtronic( )
File "/usr/local/lib/python2.7/dist-packages/mmeowlink/vendors/mmeowlink.py", line 92, in setup_medtronic
setup_medtronic_link(self)
File "/usr/local/lib/python2.7/dist-packages/mmeowlink/vendors/mmeowlink.py", line 75, in setup_medtronic_link
link = builder.build(radio_type, port)
File "/usr/local/lib/python2.7/dist-packages/mmeowlink/link_builder.py", line 16, in build
return SubgRfspyLink(port)
File "/usr/local/lib/python2.7/dist-packages/mmeowlink/vendors/subg_rfspy_link.py", line 55, in init
self.open()
File "/usr/local/lib/python2.7/dist-packages/mmeowlink/vendors/serial_interface.py", line 23, in open
raise AlreadyInUseException("%s already in use" % self.device)
mmeowlink.vendors.serial_interface.AlreadyInUseException: /dev/spidev5.1 already in use
Usage: grep [OPTION]... PATTERN [FILE]...
Try 'grep --help' for more information.
Any thoughts on what happened?
Jon Cluck
@cluckj
Jan 26 2018 14:28
do you have a loop currently running?
alimhassam
@alimhassam
Jan 26 2018 14:31
Did you stop your loop or make sure it wasn't communicating with the pump when you ran mmtune?
mkericson
@mkericson
Jan 26 2018 14:34
Yes the loop is running. No I didn't stop anything. Just ran mmtune
Jon Cluck
@cluckj
Jan 26 2018 14:41
your loop is already using the radio when you try to run mmtune; you can turn it off temporarily by typing systemctl stop cron (and waiting a few minutes for the next loop to complete) then back on when you're done with systemctl start cron
mkericson
@mkericson
Jan 26 2018 14:43
@cluckj Thanks. timing is everything. thought I broke something when connecting the antenna. ... I've run mmtune several time before but must have hit enter at the 'right' time.
Jon Cluck
@cluckj
Jan 26 2018 14:48
:) no problem
Dave Acklam
@dcacklam
Jan 26 2018 16:52
@Ebgineer enablesmb_allways does not seem to be working.
I have it on, but I still need a TT or COB to have SMB
Ebgineer
@Ebgineer
Jan 26 2018 17:01
I have some various SMB features turned on, and am getting microboluses consistently. If you want to link me your preferences.json I could tell you what I have set differently
image.png
Dave Acklam
@dcacklam
Jan 26 2018 17:07
@cluckj You need to do more than stop cron - you also need to do a killall -g -TERM oref0-pump-loop after you stop cron
Jon Cluck
@cluckj
Jan 26 2018 17:07
you can also wait for the loop to finish :P
Scott Leibrand
@scottleibrand
Jan 26 2018 17:58
I’ve never seen the need for -TERM - is there a situation you observed where killall -g doesn’t work without that?
@dcacklam check that you used uppercase where needed.
Dave Acklam
@dcacklam
Jan 26 2018 17:59
@scottleibrand
@scottleibrand Yes, I've seen it ignore plain kill
Eric
@ecc1
Jan 26 2018 19:33
-TERM is the default signal that kill uses, so no need to specify it. If a process ignores that, you can use 9 (-KILL) which is un-ignorable
davidwagaps
@davidwagaps
Jan 26 2018 20:48
From docs: "Using the pump bolus wizard to enter carbs will prevent SMBs from being enabled for COB as long as those carbs are active." Will using wizard for .1 units in order to record the carbs still disable SMBs for the entire COB entered? Is the only way to use this carb-entry method with SMB to set A52_risk_enable to True? And if so, is the "3-ESC" method still enabled if A52_risk_enable = true?
Dana Lewis
@danamlewis
Jan 26 2018 20:50
Yes, yes, yes