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

8th
Feb 2019
Scott Leibrand
@scottleibrand
Feb 08 00:46
David Klapan: Have you confirmed the pump serial number? Do you have another pump or rig to help narrow down where the problem is?
renegadeandy
@renegadeandy
Feb 08 01:22
@scottleibrand I can't get anyone to bite in terms of testing my version apart from me, who has tested it extensively.
It was validated by another member of the community, who is not an openaps user but does use xDripAPS
Scott Leibrand
@scottleibrand
Feb 08 01:26
It’d probably be worthwhile opening the oref0 PR and getting that person to comment on it.
If there aren’t any other xdripAPS users who want to test it, we’ll just need someone to validate that it doesn’t change anything for folks using other methods.
It might also be worthwhile considering whether to put the community xdripAPS fork under the openaps org in github.
renegadeandy
@renegadeandy
Feb 08 01:28
Definitely worth considering
ill locate the guy, he was posting in here when i made it
no doubt i can scroll back a couple weeks and find him
I wonder, is there an advantage to rebasing under my ID
i.e create a brand new repo
instead of it being a fixed fork?
Matthew Yeager
@AmazingThew
Feb 08 01:49

Hi all! I built my first rig and have been running it for about 30 hours. I'm getting a ton of loop failures; only succeeding around once an hour or so. Seeing mostly pump clock refresh error / mismatch and pumphistory too old:

Starting oref0-pump-loop at Thu  7 Feb 19:03:05 CST 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. Refreshed pumphistory and meal.json
Checking pump clock: "2019-02-07T18:46:56-06:00" is within 90s of current time: Thu  7 Feb 19:08:06 CST 2019
Pump clock is more than 55s off: attempting to reset it
Waiting for ntpd to synchronize... OK!
Setting pump time to Thu 7 Feb 19:08:09 CST 2019
mmeowlink.exceptions.CommsException: No acknowledgement from pump on wakeup. Is it out of range or is the battery too low?
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!)
Listening for 40s silence before mmtuning: .No interfering pump comms detected from other rigs (this is a good thing!)
mmtune: "916.516", 5, -75 waiting for 30 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.
If pump and rig are close enough, this error usually self-resolves. Stand by for the next loop.
Unsuccessful oref0-pump-loop at Thu 7 Feb 19:12:39 CST 2019


Starting oref0-pump-loop at Thu  7 Feb 19:13:04 CST 2019 with 25 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. Refreshed pumphistory and meal.json
Checking pump clock: "2019-02-07T19:16:38-06:00" is within 90s of current time: Thu  7 Feb 19:16:40 CST 2019
Error: pumphistory too old
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!)
Listening for 40s silence before mmtuning: .No interfering pump comms detected from other rigs (this is a good thing!)
mmtune: "916.540", 5, -70 waiting for 20 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.
If pump and rig are close enough, this error usually self-resolves. Stand by for the next loop.
Unsuccessful oref0-pump-loop at Thu 7 Feb 19:20:33 CST 2019

Notably, the "pump clock" time in the logs doesn't seem to line up with the actual clock display on the pump, which is closely synced the system time on my computer. Additionally, it's correctly reading bolus/carb entries from the pump and (eventually) uploading them to nightscout despite loop failures, which would suggest it isn't a radio problem.
Any suggestions for how to troubleshoot this?

(Rig is a Pi Zero/Explorer Hat, pump is a 722)
Jon Cluck
@cluckj
Feb 08 01:52
@AmazingThew are you using a HAT on the pi 0?
Matthew Yeager
@AmazingThew
Feb 08 01:52
@cluckj Yes
Jon Cluck
@cluckj
Feb 08 01:53
do you mind switching to dev? the issue is that sometimes the commands don't run fast enough and pass the "too old" threshold
Matthew Yeager
@AmazingThew
Feb 08 01:55
ah cool; will give that a shot. Thanks!
Matthew Yeager
@AmazingThew
Feb 08 02:59
So I switched to dev branch and ran through oref0-setup again. After reboots, nothing seems to be running? pump-loop.log hasn't updated since before switching branches. Am I missing a step?
Jon Cluck
@cluckj
Feb 08 03:08
@AmazingThew did you get any errors during the npm run global-install part?
or cron may be turned off: systemctl status cron?
Matthew Yeager
@AmazingThew
Feb 08 03:17
oh wait I am a fool and missed the npm step altogether :/ nevermind lol
Jon Cluck
@cluckj
Feb 08 03:17
oh lol
Matthew Yeager
@AmazingThew
Feb 08 04:47
Looks like switching to dev worked; loop's been running great so far. Thanks a lot @cluckj !
Dana Lewis
@danamlewis
Feb 08 04:53
:+1:
Jon Cluck
@cluckj
Feb 08 04:58
:thumbsup: no problem
David Klapan
@dklapan_twitter
Feb 08 05:38
I've had problem with overheating and Preflight fali. Now I've changed Pi board and have still Preflight problem, can someone advise me what to do?
https://prnt.sc/mi2m8i
Stargazer32584
@Stargazer32584
Feb 08 06:39
Hi, so i updated my npm and node on the Raspberry Pi Zero manually. But when i do oref0 - Setup and continue, the Pi give
me two errors after compilation. I loeded these two screenshots in Google Drive. Here is the Link: https://drive.google.com/drive/mobile/folders/1c4BzGuHmnqb1Z6GDIrmJHKJW-PBXZpXa?usp=drive_open
Can anyone help me in this case ? Thanks a lot...
renegadeandy
@renegadeandy
Feb 08 07:51
Can somebody please explain why my loop just upped my basal from 0.75 to 1.30, u/h when my bloods were pretty much static :
Starting oref0-pump-loop at Fri Feb 8 07:39:03 GMT 2019 with 22 second wait_for_silence: Waiting up to 4 minutes for new BG: ........................ Listening for 22s: .No interfering pump comms detected from other rigs (this is a good thing!) Continuing oref0-pump-loop at Fri Feb 8 07:44:23 GMT 2019 Preflight OK. Profile less than 60m old; Profile valid. Pump history updated through 2019-02-08T07:23:37Z with 0 new records; meal.json refreshed: {"carbs":0,"nsCarbs":0,"bwCarbs":0,"journalCarbs":0,"mealCOB":0,"currentDeviation":-0.88,"maxDeviation":0,"minDeviation":-1.18,"slopeFromMaxDeviation":0,"slopeFromMinDeviation":0.053,"allDeviations":[-1,0,-1,-1,-1],"lastCarbTime":0,"bwFound":false} Listening for 4s: .No interfering pump comms detected from other rigs (this is a good thing!) Continuing oref0-pump-loop at Fri Feb 8 07:44:52 GMT 2019 Checking that pump clock: "2019-02-08T07:44:37Z" is within 90s of current time: 2019-02-08T07:44:54+0000 Temp refreshed: monitor/temp_basal.json: {"duration":10,"temp":"absolute","rate":0.75} {"carbs":0,"nsCarbs":0,"bwCarbs":0,"journalCarbs":0,"mealCOB":0,"currentDeviation":-0.88,"maxDeviation":0,"minDeviation":-1.18,"slopeFromMaxDeviation":0,"slopeFromMinDeviation":0.053,"allDeviations":[-1,0,-1,-1,-1],"lastCarbTime":0,"bwFound":false} Autotune exists! Hoorah! You can use microbolus-related features. {"iob":-0.491,"activity":-0.0034,"basaliob":-0.491,"bolusiob":0,"netbasalinsulin":-0.25,"bolusinsulin":0,"time":"2019-02-08T07:44:39.000Z","iobWithZeroTemp":{"iob":-0.491,"activity":-0.0034,"basaliob":-0.491,"bolusiob":0,"netbasalinsulin":-0.25,"bolusinsulin":0,"time":"2019-02-08T07:44:39.000Z"},"lastBolusTime":1549571589000,"lastTemp":{"rate":0.75,"timestamp":"2019-02-08T07:23:37Z","started_at":"2019-02-08T07:23:37.000Z","date":1549610617000,"duration":22.03}} {"delta":-1.67,"glucose":79,"noise":1,"short_avgdelta":-0.96,"long_avgdelta":-0.59,"date":1549611425201,"last_cal":30} Autosens ratio: 1.05; Adjusting basal from 1.25 to 1.3; ISF from 45.6 to 43.4; CR: 8.566 currenttemp: { duration: 10, temp: 'absolute', rate: 0.75 } lastTempAge: 21 m tempModulus: 1 m SMB disabled (no enableSMB preferences active) Carb Impact: -2.4 mg/dL per 5m; CI Duration: 0 hours; remaining CI (~2h peak): 0 mg/dL per 5m UAM Impact: -2.4 mg/dL per 5m; UAM Duration: 0 hours minPredBG: 80 minIOBPredBG: 80 minZTGuardBG: 80 minUAMPredBG: 76 avgPredBG: 87 COB: 0 / 0 BG projected to remain above 5.1 for 0 minutes BG projected to remain above 3.7 for 240 minutes naive_eventualBG: 100 bgUndershoot: -34 zeroTempDuration: 240 zeroTempEffect: 214 carbsReq: -49 2019-02-08T07:45:04.815Z Checking deliverAt: 2019-02-08T07:45:04.815Z is within 1m of current time: Fri Feb 8 07:45:05 GMT 2019 and that smb-suggested.json is less than 1m old enact/smb-suggested.json: {"temp":"absolute","bg":79,"tick":-2,"eventualBG":92,"insulinReq":0,"reservoir":"78.2\n","deliverAt":"2019-02-08T07:45:04.815Z","sensitivityRatio":1.05,"COB":0,"IOB":-0.491,"duration":30,"rate":1.3} "COB: 0, Dev: -0.4, BGI: 0.0, ISF: 2.4, CR: 8.57, Target: 5.1, minPredBG 4.4, minGuardBG 4.1, IOBpredBG 4.8; Eventual BG 5.1 > 5.1 but Min. Delta -1.67 < Exp. Delta 0.0; setting current basal of 1.3 as temp. " IOB: [79,78,76,75,75,74,74,74,74,74,75,75,76,77,78,78,79,80,80,81,81,82,82,83,83,84,84,84,85,85,85,85,86,86,86,86,86,87] ZT: [79,80,81,81,83,84,85,86,88,90,91] Temp refreshed: monitor/temp_basal.json: {"duration":10,"temp":"absolute","rate":0.75} enact/smb-enacted.json: "Rate: 1.3 Duration: 30" Checking pump status (suspended/bolusing): {"status":"normal","bolusing":false,"suspended":false} Temp refreshed: monitor/temp_basal.json: {"duration":30,"temp":"absolute","rate":1.3} No bolus needed. Pump profile refreshed; Could not parse temptargets_data.No temptargets found. Settings refreshed; grep: enact/bolused.json: No such file or directory Refreshing pumphistory because: enacted, Settings less than 3 minutes old. Pump history update failed. Last record 2019-02-08T07:23:37Z Couldn't invoke_pumphistory_etc - continuing Your instance of oref0 [0.7.0-dev, dev] is
EmericSch
@EmericSch
Feb 08 08:30
Hi, I'm about to buy an explorer hat. I have a European pump, so I have to choose a frequency at 868 mHz. There is no subtlety? Thank you
PieterGit
@PieterGit
Feb 08 11:58
@EmericSch I don't no what you mean with"There is no subtlety? ". You need an openaps compatible pump, see https://openaps.readthedocs.io/en/latest/docs/Gear%20Up/pump.html
newer European pumps will not work
EmericSch
@EmericSch
Feb 08 14:56
I mean for frequency Europe =868 mhz. There is no exception. I have a medtronic 722.
Scott Leibrand
@scottleibrand
Feb 08 16:42
If the model number says WW, you need 868. For NA you need 916.
The only hardware difference is the antenna length, so if you get it wrong you can replace that for $5
And even with the wrong antenna it will still work with slightly reduced range.
@renegadeandy Eventual BG 5.1 > 5.1 but Min. Delta -1.67 < Exp. Delta 0.0; setting current basal of 1.3 as temp. "
Scott Leibrand
@scottleibrand
Feb 08 16:51
Obviously that > should be >=
renegadeandy
@renegadeandy
Feb 08 18:52
@scottleibrand is that a bug in dev in that case?
Doug
@dougboss
Feb 08 23:26
just updated to most recent DEV version and seeing this in the logs
Feb 08 17:26:04 smartpump3 network.log: edison:x:1002:100::/home/edison:/bin/bash
Feb 08 17:26:05 smartpump3 pump-loop.log: Profile less than 60m old; Profile valid. Refreshed pumphistory and meal.json
Feb 08 17:26:08 smartpump3 pump-loop.log: Checking pump clock: "2019-02-08T08:28:27-06:00" is within 90s of current time: Fri Feb 8 17:26:08 CST 2019
Feb 08 17:26:08 smartpump3 pump-loop.log: Pump clock is more than 55s off: attempting to reset it
Feb 08 17:26:08 smartpump3 pump-loop.log: Waiting for ntpd to synchronize... OK!
Feb 08 17:26:08 smartpump3 pump-loop.log: Setting pump time to Fri Feb 8 17:26:08 CST 2019
Feb 08 17:26:11 smartpump3 pump-loop.log: serial.serialutil.SerialException: Attempting to use a port that is not open
Feb 08 17:26:11 smartpump3 pump-loop.log: Error: pump clock refresh error / mismatch
What is the serial port ?
Wont loop