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

6th
Jan 2018
Scott Leibrand
@scottleibrand
Jan 06 2018 00:00
真奇怪 如果工作正常,你可以在“收音机没问题”,“收听收听”和“在收听之前收听40秒的沉默”之间看到其他内容,以表明错误是什么。 你正在使用浏览器板,还是其他类型的收音机?
jzycom123
@jzycom123
Jan 06 2018 00:00
图片不好弄
我用ssh连接的edison
Scott Leibrand
@scottleibrand
Jan 06 2018 00:01
你使用Explorer Board还是其他类型的收音机?
jzycom123
@jzycom123
Jan 06 2018 00:02
Explorer Board
Scott Leibrand
@scottleibrand
Jan 06 2018 00:02
ok
In that case I would first try running oref0-setup again to see if that helps. 在这种情况下,我会首先尝试再次运行oref0-setup,看看是否有帮助。
jzycom123
@jzycom123
Jan 06 2018 00:04
也就是重新安装oref0?
jzycom123
@jzycom123
Jan 06 2018 00:12
谢谢您!有没有快捷一点的方式,好多内容看不懂
jzycom123
@jzycom123
Jan 06 2018 00:17
谢谢!我去尝试一下
Scott Leibrand
@scottleibrand
Jan 06 2018 00:18
:+1:
jzycom123
@jzycom123
Jan 06 2018 00:27
正在安装中,请稍等!
jzycom123
@jzycom123
Jan 06 2018 00:34

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: No wait required.
Unsuccessful oref0-pump-loop at Sat Jan 6 08:27:12 HKT 2018
grep: monitor/temp_basal.json: No such file or directory

/bin/sh: 1: oref0-pump-loop: not found
/bin/sh: 1: oref0-pump-loop: not found

Starting oref0-pump-loop at Sat Jan 6 08:28:32 HKT 2018 with 17 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: .
Starting oref0-pump-loop at Sat Jan 6 08:29:02 HKT 2018 with 30 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 mmeowlink.exceptions.CommsException: No acknowledgement from pump on wakeup. Is it out of range or is the battery too low?
fail. Retrying preflight
Preflight mmeowlink.exceptions.CommsException: No acknowledgement from pump on wakeup. Is it out of range or is the battery too low?
fail. Couldn't preflight
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

jzycom123
@jzycom123
Jan 06 2018 00:47
求助!!
jzycom123
@jzycom123
Jan 06 2018 00:54

Listening for 40s silence before mmtuning: .Listening for 40s silence before mmtuning: .No interfering pump comms detected from other rigs (this is a good thing!)
mmtune: "868.438", 5, -46 No wait required.
Unsuccessful oref0-pump-loop at Sat Jan 6 08:50:06 HKT 2018
grep: monitor/temp_basal.json: No such file or directory

Starting oref0-pump-loop at Sat Jan 6 08:50:31 HKT 2018 with 25 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 25 seconds of silence: Radio ok. Listening: .No interfering pump comms detected from other rigs (this is a good thing!)
Old pumphistory-24h refreshValueError: need more than 0 values to unpack
Couldn't refresh_old_pumphistory_24h
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!)

jzycom123
@jzycom123
Jan 06 2018 01:17
大家好
我刚刚开始试用openaps
G4 +爱迪生+ 722,发现我的爱迪生不能和泵连接,怎么办?
Scott Leibrand
@scottleibrand
Jan 06 2018 01:53
oref0-pump-loop: not found is a good clue; it means that oref0 didn’t get completely installed correctly.
jzycom123
@jzycom123
Jan 06 2018 01:57
好希望有人能帮我连接一下
到底哪里出错了,需要重新安装吗
jzycom123
@jzycom123
Jan 06 2018 02:03
scott leibrand,,你是一个好人!!!😊😊😊😊
jzycom123
@jzycom123
Jan 06 2018 02:10
Pi3价格多少钱
Deweyoxberg
@Deweyoxberg
Jan 06 2018 03:43
Hi all, looking for a bit of help troubleshooting lop. Keep seeing Timed: out or other comms error - Received an error response Timeout - retrying: 3 of 3 and Old pumphistory: RefreshIndexError: bytearray index out of range . Have done several reboots and confirmed signal looks good (mmtune shows "868.342", 5, -34 relatively consistently). Any ideas why these errors keep popping up? Edison and pump are pretty much next to each other with a gap of about an inch.
Dana Lewis
@danamlewis
Jan 06 2018 03:53
That's a bad pump read for whatever reason - so if mmtune looks good, no other ideas other than it usually self resolves with the next good read.
Deweyoxberg
@Deweyoxberg
Jan 06 2018 03:55
That's what we've been relying on, but it's with increasing frequency and really driving my tech brain crazy.
Is it possible we're looking at bad hardware?
Because the last good read was almost 45 minutes ago and it's not resolving itself this time around.
Deweyoxberg
@Deweyoxberg
Jan 06 2018 04:03
This message was deleted
Dana Lewis
@danamlewis
Jan 06 2018 04:17
Wouldn't be able to say from that. Usually bad hardware is other errors like -99 permanently or other stuff
Do you have another rig?
Deweyoxberg
@Deweyoxberg
Jan 06 2018 04:18
nope, no other rig.
Dana Lewis
@danamlewis
Jan 06 2018 04:18
If so you could try swapping Edison's and see if a different board and same edison gets you different results
K
Deweyoxberg
@Deweyoxberg
Jan 06 2018 04:28
Looking at mmtune results from the 28th of December, there's a lot of blank results. That's not good.
Would cutting the trace be advisable for this?
Guessing no, given it's not an NA pump.
Deweyoxberg
@Deweyoxberg
Jan 06 2018 04:56
oh, other error is this: pump-loop.log: Old pumphistory: mmeowlink.exceptions.InvalidPacketReceived: Error decoding FourBySix packet Guessing that's also communications related yes?
Dana Lewis
@danamlewis
Jan 06 2018 05:32
Hm, interesting. Yes
Marco
@CaptainBalou
Jan 06 2018 14:20
I just got my Dexcom G5. So I want to deactivate my MDT Enlite setup and switch to G5. I thought that this would be easy but to be honest it isn’t. I just deactivated my Sensor in the pump and reran setup with CGM=xdrip. Since this I cannot loop anymore but I don’t see why. For example it looks like my profile doesn’t get read well. The file is getting created but with size zero. Can anyone instruct me what to look for to fix that? Being without loop is quite annoying. ;-)
Starting oref0-pump-loop at Sat Jan  6 14:52:03 CET 2018 with 24 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: Profile valid. Refreshed
module.js:485
    throw err;
          ^
SyntaxError: /root/myopenaps/settings/profile.json: Unexpected end of input
    at Object.parse (native)
    at Object.Module._extensions..json (module.js:482:27)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:312:12)
    at Module.require (module.js:364:17)
    at require (module.js:380:17)
    at Object.<anonymous> (/root/src/oref0/bin/oref0-calculate-iob.js:44:22)
    at Module._compile (module.js:456:26)
    at Object.Module._extensions..js (module.js:474:10)
    at Module.load (module.js:356:32)

Couldn't calculate IOB
oref0-pump-loop failed. If pump and rig are close enough, this error usually self-resolves. Stand by for the next loop.
Unsuccessful oref0-pump-loop at Sat Jan 6 14:52:55 CET 2018

Retrying merge_pumphistory

module.js:485
    throw err;
          ^
SyntaxError: /root/myopenaps/settings/profile.json: Unexpected end of input
    at Object.parse (native)
    at Object.Module._extensions..json (module.js:482:27)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:312:12)
    at Module.require (module.js:364:17)
    at require (module.js:380:17)
    at Object.<anonymous> (/root/src/oref0/bin/oref0-calculate-iob.js:44:22)
    at Module._compile (module.js:456:26)
    at Object.Module._extensions..js (module.js:474:10)
    at Module.load (module.js:356:32)

Couldn't calculate IOB
oref0-pump-loop failed. If pump and rig are close enough, this error usually self-resolves. Stand by for the next loop.
Unsuccessful oref0-pump-loop at Sat Jan 6 14:52:56 CET 2018
Pump communication is working fine. For example:
root@captainsloop1:~/myopenaps# openaps use pump read_settings
{
  "low_reservoir_warn_point": 20, 
  "keypad_lock_status": 0, 
  "maxBasal": 9.0, 
  "temp_basal": {
    "percent": 100, 
    "type": "Units/hour"
  }, 
  "low_reservoir_warn_type": 0, 
  "insulinConcentration": 50, 
  "audio_bolus_enable": false, 
  "variable_bolus_enable": true, 
  "alarm": {
    "volume": 1, 
    "mode": 2
  }, 
  "rf_enable": false, 
  "auto_off_duration_hrs": 0, 
  "block_enable": false, 
  "timeformat": 104, 
  "insulin_action_curve": 5, 
  "audio_bolus_size": 0, 
  "selected_pattern": 0, 
  "patterns_enabled": true, 
  "maxBolus": 25.0, 
  "paradigm_enabled": 1
}root@captainsloop1:~/myopenaps#
jzycom123
@jzycom123
Jan 06 2018 15:30
Starting oref0-pump-loop at Sat Jan 6 23:13:02 HKT 2018 with 4 second wait_for_silence:
Waiting up to 4 minutes for new BG: ........................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. RefreshValueError: need more than 0 values to unpack
Retrying invoke_pumphistory_etc
ValueError: need more than 0 values to unpack
Couldn't invoke_pumphistory_etc - continuing
Retrying monitor_pump
ValueError: need more than 0 values to unpack
Retrying invoke_pumphistory_etc
ValueError: need more than 0 values to unpack
Couldn't invoke_pumphistory_etc - continuing
Couldn't monitor_pump - continuing
Couldn't refresh_pumphistory_and_meal
oref0-pump-loop failed. Unsuccessful oref0-pump-loop at Sat Jan 6 23:18:13 HKT 2018
philipgo
@philipgo
Jan 06 2018 15:31
@CaptainBalou Seems to be something with dev. I had the same problem twice in the past few days. I had to drill down and run all commands separately, afterwards it worked. I did not understand why, but at least it worked...
Jon Cluck
@cluckj
Jan 06 2018 15:36
@CaptainBalou please see openaps/oref0#889
Marco
@CaptainBalou
Jan 06 2018 15:49
@drnoname82 @cluckj Thanks for answering. So it looks like I didn’t made a fatal configuration error. ;-) Does anyone of you know if I can ‚pull dev branch from one week ago‘ or so?
Jon Cluck
@cluckj
Jan 06 2018 15:51
it might be easier to run the reports manually ;)
Marco
@CaptainBalou
Jan 06 2018 15:52
Oh lord. :-) I had some debug sessions in the past and this „running reports manually“ freaked me out each time. ;-)
Even finding the right ones is horrible.
Jon Cluck
@cluckj
Jan 06 2018 15:53
haha
Marco
@CaptainBalou
Jan 06 2018 15:53
But I start with those in the ticket and try them...
Jon Cluck
@cluckj
Jan 06 2018 15:54
I know the feeling :)
settings/profile.json is a compilation of a bunch of different files
so all you're doing is making sure that each of the files that needs to go into it is generated
each of those reports just pulls data from the pump and passes it on to the next
the error messages will tell you which one isn't working, and you can invoke them down the "chain" until you get to the broken one
Marco
@CaptainBalou
Jan 06 2018 16:01
Ah ok. I understand. Those commands in the ticket worked fine. How do I see which others I have to try? Is there a script were I should look in?
oref0-pump-loop?
Jon Cluck
@cluckj
Jan 06 2018 16:02
if you do openaps report invoke settings/profile.json it should tell you which of the required reports is broken
(I imagine it's openaps report invoke settings/basal_profile.json just based on what I remember from how it works)
Marco
@CaptainBalou
Jan 06 2018 16:05
To be honest I really would need something like a „debug bash script to remember that the next time“. ;-)
Marco
@CaptainBalou
Jan 06 2018 16:11
The basal_profile report seems to work without error. The file contains alls the basal hours. But what I see in there are some strange long rates like 0.8250000000000001. I don’t know if this could possibly produce some problems.
Jon Cluck
@cluckj
Jan 06 2018 16:12
does openaps report invoke settings/basal_profile.json work now?
Marco
@CaptainBalou
Jan 06 2018 16:13
Yes this works but I get an error while generating profile.json:
root@captainsloop1:~/myopenaps# openaps report invoke settings/profile.json
get-profile://text/shell/settings/profile.json
Could not parse carbratio_data. Feature Meal Assist enabled but cannot find required carb_ratios.
reporting settings/profile.json
root@captainsloop1:~/myopenaps#
Jon Cluck
@cluckj
Jan 06 2018 16:16
getting closer ;) try openaps report invoke settings/carb_ratios.json?
Marco
@CaptainBalou
Jan 06 2018 16:16
Ah settings/carb_ratios.json does not exist. Report issued…waiting.
Created with proper content. Rerun profile.json report again...
OH MY GOD! The report works!
Jon Cluck
@cluckj
Jan 06 2018 16:18
:clap:
Marco
@CaptainBalou
Jan 06 2018 16:20
I try a loop now.
Jon Cluck
@cluckj
Jan 06 2018 16:25
hmm
Marco
@CaptainBalou
Jan 06 2018 16:28
I got far further. I am stuck at „waiting for BG“ but this is because I changed from MDT CGM to DEXCOM and have changed the setup...
But I have to go to dinner now. Thanks for your awesome help! Unfortunately we eat spaghetti and I am not looping. :-D
Jon Cluck
@cluckj
Jan 06 2018 16:52
you're welcome :)
Carl
@c-robertson
Jan 06 2018 16:59
For BT tethering, I did the rig setup and have BTAutoTether app on my phone (Galaxy S7, Android 7.0). The rig does the right thing, initiating a tether request when WIFI goes out of range. However, the phone experience is not as automatic as I expected, it pops up a dialog to the effect 'rig is trying to tether' with OK and Cancel. Half the time, the OK button is grayed out, restarting the phone fixes this temporarily. So, is the dialog expected behavior?
Dave Acklam
@dcacklam
Jan 06 2018 17:22
@c-robertson must be a Samsung thing. I'm on a Nexus 6P and I don't get that prompt.
ZandMarc
@ZandMarc
Jan 06 2018 17:37
My OpenAPS rig has stopped working. In the log there's this error: Waiting up to 4 minutes for new BG: date: invalid date ‘@’
.date: invalid date ‘@’
Than the invalid date message is repeated a couple of times and than there's this: ".Radio ok. Listening: .No interfering pump comms detected from other rigs (this is" After that it has done nothing.
I have rebooted the rig and stopped and restarted the cron. That didn't solve it. Now I thougt to update my dev and hopefully overwrite what is going wrong, but after the "... && git pull" command, I get the message "unable to write new index file".
Does somebody know what can be going on and/or how to fix it?
ZandMarc
@ZandMarc
Jan 06 2018 17:50

trying to do setup again, gives me the messages: "fatal: unable to connect to github.com:
github.com: Name or service not known

Couldn't pull latest decocare 0.1.0-dev"

so that doesn't solve it...
Carl
@c-robertson
Jan 06 2018 18:00
Thx @dcacklam. Some googling seems to support that it is a Samsung thing, but hard to find definitive info. Anyone have an S7 with similar experience?
mkericson
@mkericson
Jan 06 2018 18:11
I have a new phone and update my MAC address. Since I have oref0 already running what should I select for the cron questions.
Dana Lewis
@danamlewis
Jan 06 2018 18:19
@ZandMarc means your rig isn't online.
@mkericson yes for replacing cron; you want it to use the new info you're putting in
@CaptainBalou are you using xdrip, or Just G5? How are your BGs getting to NS?
Marco
@CaptainBalou
Jan 06 2018 18:34
@c-robertson @dcacklam I see the same promt ‚sometimes‘ on the same phone. Samsung Galaxy S7. I would say it comes every 20th try.
@cluckj I am looping again. BG was not there because I stopped cron to debug the loop issue. After re-enabling I am back in the loop. @danamlewis Currently I am using xdrip to receive values from G5 and this is uploading to NS (heroku). I think at this point of time OpenAPS is getting the values from NS because I didn’t set up any direct xdrip readings. So if I am offline with this setup I think the loop will stop working.
Deweyoxberg
@Deweyoxberg
Jan 06 2018 18:39
@danamlewis : For the communication issues I mentioned yesterday, is a trace cut a fix? Or something else?
Marco
@CaptainBalou
Jan 06 2018 18:41
@cluckj @drnoname82 @danamlewis To see what went wrong after setting up dev branch from scratch I could erase all content of directory ‚settings‘ and start over again, isn’t it? The content of this directory is getting recreated ever or nearly every loop interval?!
Dana Lewis
@danamlewis
Jan 06 2018 18:44
@YYCMichael no, trade cut not related
@CaptainBalou if this is your only rig, I would just install master for now if you're stressed about it. There's not that much changed in dev.
Jon Cluck
@cluckj
Jan 06 2018 18:46
@CaptainBalou once the files are generated, it should work fine
mkericson
@mkericson
Jan 06 2018 18:55
@danamlewis Thanks. I reran with Y, Y for cron. Preflight was failing now its good to go. Now to tether the bluetooth. :smile:
Marco
@CaptainBalou
Jan 06 2018 19:01
@danamlewis Installing master sounds like ‚sorry, you’ve lost the game‘. ;-)
@cluckj Yes it does. But if it has problems generating the first version it could be possible that if I change the values it gets not reflected in the rig because a regeneration fails as well.
mkericson
@mkericson
Jan 06 2018 19:19
what is this failure: [DEPEND] Dependency failed for Host and Network Name Lookups.
Dana Lewis
@danamlewis
Jan 06 2018 19:35
@CaptainBalou no, it revokes your freakout privileges temporarily ;) is all.
mkericson
@mkericson
Jan 06 2018 19:38
cron was off. new instructions for bt tether have you turn cron off.
Dana Lewis
@danamlewis
Jan 06 2018 19:45
Can you PR to have folks turn it back on when done?
Carl
@c-robertson
Jan 06 2018 20:08
what steps are necessary to see the 'Zero Temp' line in Nightscout? Is it a particular NS version? I am on NS Habanero, but only see the 'middle' line with COB > 0 and the 'bottom' insulin-only line.
note I am running oref0 0.6.0
mkericson
@mkericson
Jan 06 2018 20:32
Its already in there. Old instructions allow you to test with a 120 sleep. I jump from the new to the old after turning cron off.
Diadon81
@Diadon81
Jan 06 2018 21:01
Dears, I am getting the following message from pump-looplog mmtune: No wait required.
My pump can’t pass through mmtune process
Diadon81
@Diadon81
Jan 06 2018 21:06
image.png
someone can explain me what means this message mmtune: No wait request.
philipgo
@philipgo
Jan 06 2018 21:18
@Diadon81 The important message is "No acknowledgement from pump...", a problem in the communication between rig and pump. Check that the pump battery is new, move them closer together and wait.
Diadon81
@Diadon81
Jan 06 2018 21:20
@drnoname82 clear, It's looks like something happen with my explorer board, during two days the range between rig and pump was reduced dramatically.
regdubbed
@regdubbed
Jan 06 2018 21:22
I tried oref0-runagain an it fails with: npm WARN engine boom@2.10.1: wanted: {"node":">=0.10.40"} (current: {"node":"0.10.29","npm":"1.4.21"})
npm ERR! TypeError: Cannot read property 'latest' of undefined
npm ERR! at next (/home/.rootfs/usr/share/npm/lib/cache/add-named.js:219:35)
npm ERR! at /home/.rootfs/usr/share/npm/lib/cache/add-named.js:207:5
npm ERR! at saved (/home/.rootfs/usr/share/npm/node_modules/npm-registry-client/lib/get.js:167:7)
npm ERR! at Object.oncomplete (fs.js:107:15)
regdubbed
@regdubbed
Jan 06 2018 21:44
and the whole installation is gone...
Ivica Suran
@isuran
Jan 06 2018 21:50
Does autotune works with 512? Should I manually enter settings that autotune.json suggest?
Dana Lewis
@danamlewis
Jan 06 2018 21:51
autotune does work; but like any other pump, you'll have to manually update your settings if you want to change the baseline settings. your call on whether you want to do that; if so, the next tune will tune off the new numbers. for the x12, that means updating the files you manually created or edited during setup, instead of editing that info on the pump.
ZandMarc
@ZandMarc
Jan 06 2018 21:59
I think my rig has stopped working because my root directory has no more space available. Probably caused by log: syslog and kern.log are over 180 MB. Looking into those, it turns out those files are filled up with the following message:
Jan 6 06:25:47 localhost kernel: [221606.419646] pci_pm_runtime_suspend(): serial_hsu_pci_runtime_suspend+0x0/0xf0 returns -16
Any suggestions what can be the cause of this?
Ebgineer
@Ebgineer
Jan 06 2018 22:09
@ZandMarc can't say what's causing it, but those files also filled up my disk
ZandMarc
@ZandMarc
Jan 06 2018 22:11
@Ebgineer I also have more of those files (e.g. syslog.1 and kern.log.1) that are almost the same size. What did you do?
Ebgineer
@Ebgineer
Jan 06 2018 22:12
well don't tell anyone but I just deleted them and hoped for the best
probably won't solve the underlying problem, why they are getting so many messages