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

9th
Mar 2019
Ebgineer
@Ebgineer
Mar 09 00:16
@111mastermind That can happen if the microusb cables are wired for data only. The cables need to include the power wires too.
straykatz
@straykatz
Mar 09 00:18
Oh that would also explain why the battery is not charging ...
Ebgineer
@Ebgineer
Mar 09 00:19
@111mastermind Also, to be sure it is getting power, plug the other end of the microusb cable into a wall charger and not the computer. Some computer usb ports don't put out enough power.
katrina1232
@katrina1232
Mar 09 01:21
i'm slowly progressing with my pi0 build. after rerunning the install ~6 more times (failed at a slightly different point each time) I've finally got one that completed (got to the enter/ctrl-c stage) It did however give these errors right at the end
alt
i suspect they are significant as when running the global install this happened
alt
then a bunch more kernel messages then
alt
alt
How do I progress?
Jon Cluck
@cluckj
Mar 09 01:22
that looks like your hardware is bad
if you have another pi, try it with that?
@Stargazer32584 do you know how to switch to another repository/branch?
boc-the-git
@boc-the-git
Mar 09 01:25
I'd also consider attempting to start from the beginning (i.e. flash your microSD again) @katrina1232
katrina1232
@katrina1232
Mar 09 01:26
rip okay thanks, no don't have another pi
@boc-the-git i'll give it a go
Mags
@111mastermind
Mar 09 01:41
@Ebgineer
Thank you I will buy a new cable @Ebgineer
The rig even when plugged in to power not computer always had ‘low battery’ orange light ignited. Explains it is the wrong cables now.
TranceCake
@TranceCake
Mar 09 07:07
Possibly weird behavior.png
So I have a question about what happened here. You can see that I was low for quite some time, but that the rig decided to give a basal. anyway for a short duration. Just wanted to share this here in case it is unwanted behavior! I am going to speak to my endo because I think I am hypo unaware during the night.
Scott Leibrand
@scottleibrand
Mar 09 07:30
It thought you had enough negative IOB to bring you up, and BG was no longer falling, nor below the safety threshold, so it stopped zero temping briefly. That’s expected behavior given the inputs.
I would instead focus on why you went low and didn’t rise even with -1U IOB. Check autotune and see if it recommends lowering basals or raising CR/ISF. And if those are all correct, maybe don’t bolus 100% up front on that kind of meal?
TranceCake
@TranceCake
Mar 09 07:33
yeah was a one off situation anyway
went swimming and had a table tennis cup at work where I had fries for which I didn't have to bolus at all so kinda surprised it didn't go worse than this. so +1 for openAPS!
Scott Leibrand
@scottleibrand
Mar 09 07:41
If you aren’t sure if you need a bolus for some meal, you can just enter the carbs into NS and let SMB figure it out. It generally won’t bolus any more than is safe.
TranceCake
@TranceCake
Mar 09 08:00
yeah that's exactly what I did :)
although I learned on the discord that it is unwise to enable smb always with a libre, which I have
so think I'm going to turn enable_after_carbs off since 6 hours after carbs sometimes is true during my sleep when I ate a little snack in the evening
Stargazer32584
@Stargazer32584
Mar 09 09:46
@cluckj Last week, i tested the same with the HAT on a Raspberry Pi 2 . Same problems with this hardware. Switching is like : "cd ~/src/oref0 && git checkout dev" or "cd ~/src/oref0 && git checkout master". Is it right ?
viq
@viq
Mar 09 09:47
@Stargazer32584 yes, that's how you change branches
and git pull to update that branch to what's on github for that branch
Stargazer32584
@Stargazer32584
Mar 09 09:52
@viq Thank you. So i switched to the master. But "dev" is the right for the HAT. But i will try in master's branch. The branch is already up to date. I reboot the system but there was the same errors...
JohnDoeAkira
@JohnDoeAkira
Mar 09 12:51
Quick question : I am running oref1. I know that an smb when doing a wizard bolus can trigger an a52 error. How bad is this ? Does is brick the pump forever or can a reset cure it ? Shall I completely avoid wizard bolus at all cost or can I do it carefully ?
Jon Cluck
@cluckj
Mar 09 12:52
@Stargazer32584 you'll have to redo the git clone, then do a branch change to x12-fix but try this one? https://github.com/cluckj/oref0/tree/x12-fix
Jon Cluck
@cluckj
Mar 09 12:58
basically cd ~/src rm -rf oref0/ git clone https://github.com/cluckj/oref0/ cd oref0 git checkout x12-fix and npm run global-install
then re-run the interactive setup; it shouldn't ask you anything about the x12 and should "just work" after the reboot at the end
PieterGit
@PieterGit
Mar 09 13:41
@scottleibrand are the problems on the dev branch fixed again? I think openaps/oref0#1176 is ready. The failing unit test now works like a charm. Can you please merge this to dev? I'm now working on a proper shutdown with pushover_message to warn the user. If you charge it within 15 minutes the shutdown will be cancelled
Jon Cluck
@cluckj
Mar 09 14:45
@PieterGit should line 287 in oref0-setup.sh be "doesn't exist"?
Stargazer32584
@Stargazer32584
Mar 09 14:48

@cluckj So...i made it like you described it in your post. Here is the result. In the oref0 - setup is no question about the x12 - pump. Laike you said it before. Here is the screenshot.

https://drive.google.com/open?id=1mpuWiR6XqlEKyhakZGS6oTjBxYC2tEXY

Jon Cluck
@cluckj
Mar 09 14:49
how many loops has it gone through like that?
when I tested it this morning, it took about 15 minutes (4-5 loops) for it to successfully complete a loop
you may need to setup the bolus wizard on the pump too, if you haven't already done so :)
Stargazer32584
@Stargazer32584
Mar 09 15:16
@cluckj So..i do the bolus on the pump on 0,5. In the moment, the loop runs for 30 min. But the errors are the same. But why doesn't run on my rig ?
Jon Cluck
@cluckj
Mar 09 15:28
I think there's an alias left over from the old setup that we'll have to remove, let me check on how to get rid of that
Jon Cluck
@cluckj
Mar 09 15:33
can you paste the contents of ~/myopenaps/settings/insulin_sensitivities.json, ~/myopenaps/settings/bg_targets.json and ~/myopenaps/settings/settings.json?
Stargazer32584
@Stargazer32584
Mar 09 17:10

@cluckj so..there is my problem. There are only the following files: insulin_sensitivities_raw.json, bg_targets_raw.json. The settings.json have the following :

https://drive.google.com/open?id=1PdI4jyKAsNGKUcsTUlJcYuILkRiDVN5p

viq
@viq
Mar 09 17:12
@Stargazer32584 I don't believe JSON supports comments
@Stargazer32584 have those lines contain just the number, without even a space after
Jon Cluck
@cluckj
Mar 09 17:15
it looks like something went wrong with switching branches
Stargazer32584
@Stargazer32584
Mar 09 17:16
Ah..okay...but he tells me the right one, if i switching the branch.
Jon Cluck
@cluckj
Mar 09 17:23
were you on dev before?
Stargazer32584
@Stargazer32584
Mar 09 17:23
Jepp...i was on dev - branch.
Jon Cluck
@cluckj
Mar 09 17:25
can you run export MEDTRONIC_PUMP_ID=`grep serial ~/myopenaps/pump.ini | tr -cd 0-9`
then mdt settings?
Jon Cluck
@cluckj
Mar 09 17:30
retry the mdt settings, that message just means you're bumping into the loop
(and keep retrying until it returns a bunch of data)
you can copy/paste blocks of text into gitter if you surround them with three backticks: ```
like:
```
bunch of text here
```
viq
@viq
Mar 09 17:44
Or use services like https://pbot.rmdir.de
amspoke
@amspoke
Mar 09 17:56
Hi! I have a (probably stupid) question. I have been looping for two weeks now. And i would like to fine tune the battery consumption. I see that the oref0 script executes every minute. So i have two questions. The firstone is that some times this script takes longer to execute than 1 minute so it overlaps with the next execution, is this normal? Second one, is about network connectivity, everyminute the system tries to refresh the network connection (or it looks like this on the log) is this normal?
Stargazer32584
@Stargazer32584
Mar 09 18:19

@cluckj I do the "mdt settings" again, and there are four lines of output:

'''
connected to CC111X radio on /dev/spidev0.0
setting frequency to 916.600
waking pump
no response to wakeup
'''

The frequency is not right. It's the EU model of the 712, so we need 868 Mhz.

Jon Cluck
@cluckj
Mar 09 18:21
ah okay :)
export MEDTRONIC_FREQUENCY=`cat ~/myopenaps/monitor/medtronic_frequency.ini`
run that, and try the settings thing again
@amspoke are you on the edison or raspberry pi?
Stargazer32584
@Stargazer32584
Mar 09 18:39
Alright. I do "export 868.450=cat...etc.´ So..he gave me some hint: ```bash: export:868.450=201849': not a valid identifier´´´
Scott Leibrand
@scottleibrand
Mar 09 18:42
@JohnDoeAkira if you get an A52, it won’t brick your pump, but it may make it unsafe to continue looping for a few hours until the corrupted pumphistory is no longer relevant for calculating IOB.
Jon Cluck
@cluckj
Mar 09 18:44
@Stargazer32584 ? try just export MEDTRONIC_FREQUENCY=868.450
Scott Leibrand
@scottleibrand
Mar 09 18:44
@amspoke the script doesn’t do much except on the 5m interval at which new CGM readings arrive. It starts within a minute of finishing the last loop, and then waits for up to 4 minutes for a new reading to arrive.
And if the script is already running it won’t start a second instance.
What do you mean by trying to refresh the network connection? What are the repeated log lines?
Stargazer32584
@Stargazer32584
Mar 09 19:09

@cluckj Now, i have the following message:

``connected to CC111X radio on /spidev0.0
MEDTRONIC_FREQUENCY: strconv.ParseFloat: parsing "\n86845000 ´´

Jon Cluck
@cluckj
Mar 09 19:12
that's extremely strange, can you run echo $MEDTRONIC_FREQUENCY
Stargazer32584
@Stargazer32584
Mar 09 19:14
If i run these command, he take a blank line and then, there is the simple prompt.
Jon Cluck
@cluckj
Mar 09 19:16
run export MEDTRONIC_FREQUENCY=868.450
then echo $MEDTRONIC_FREQUENCY
Stargazer32584
@Stargazer32584
Mar 09 19:18
Jepp...the echo is good. It is "868.450"
Jon Cluck
@cluckj
Mar 09 19:19
okay cool, now run mdt settings
Stargazer32584
@Stargazer32584
Mar 09 19:20

Return from rig:

"connected to CC111x radio on /dev/spidev0.0"
"MEDTRONIC_PUMP_ID enviroment variable is not set"

Jon Cluck
@cluckj
Mar 09 19:22
export MEDTRONIC_PUMP_ID=`grep serial ~/myopenaps/pump.ini | tr -cd 0-9`
try that one again
Stargazer32584
@Stargazer32584
Mar 09 19:24
Okay....i've done it. But i don't need any number for the placeholder MEDTRONIC_PUMP_ID ?
Jon Cluck
@cluckj
Mar 09 19:25
that's not a placeholder
it's setting that variable to the contents of a file
Stargazer32584
@Stargazer32584
Mar 09 19:26
Oh..okay. Then, it must be right...
Jon Cluck
@cluckj
Mar 09 19:27
you should be copying and pasting these commands :)
they're made to use the files that you've already configured with this info
Stargazer32584
@Stargazer32584
Mar 09 19:28
Okay...so you are my mentor ;-))
Jon Cluck
@cluckj
Mar 09 19:31
what did mdt settings return?
Stargazer32584
@Stargazer32584
Mar 09 19:36

Au....very nice..here are the results:

"connected to CC111x radion on /dev/spidev0.0"
"setting frequency to 868.450"
"model 712 pump"
{
"auto_off_duration_hrs": 0,
"insulin_action_curve": 6,
"insulinConcentration": 100,
"maxBolus": 10,
"maxBasal": 2,
"rf_enable": true,
"selected_pattern": 0
}
2019/03/09 20:31:37 disconnecting CC111x radio on /dev/spidev0.0

Jon Cluck
@cluckj
Mar 09 19:37
now run mdt sensitivities
Dana Lewis
@danamlewis
Mar 09 19:37
:clap:
Stargazer32584
@Stargazer32584
Mar 09 19:41

Here are the results:

"connecting to CC111x radio on /dev/spidev0.0"
"setting frequency to 868.450"
"waking pump"
"no response to wakeup"

Jon Cluck
@cluckj
Mar 09 19:42
keep running that until it returns some data that looks like the format of mdt settings
Stargazer32584
@Stargazer32584
Mar 09 19:43
Okay...i try it..
Jon Cluck
@cluckj
Mar 09 19:43
after you get a good result from that, run mdt targets until you get the same :)
Stargazer32584
@Stargazer32584
Mar 09 19:46
Few seconds ago, he made a reboot. To fix some radio problems. After the reboot, i must start again at "export MEDTRONIC_FREQUENCY=868.450
Jon Cluck
@cluckj
Mar 09 19:49
yes
Stargazer32584
@Stargazer32584
Mar 09 19:50

The results for mdt sensitivities are:

"connected to CC111x..."
"setting frequency to 868.450"
"model 712 pump"
null
"disconnecting CC111x..."

Then...he will start the reboot..
Jon Cluck
@cluckj
Mar 09 19:51
what is the reboot for?
Stargazer32584
@Stargazer32584
Mar 09 19:51
"Rebooting to fix radio errors!"
Jon Cluck
@cluckj
Mar 09 19:52
oh boy
systemctl stop cron && shutdown -c
that'll stop it from rebooting
Stargazer32584
@Stargazer32584
Mar 09 19:58
Okay...
so i tried the "mdt sensitivities" and the "mdt targets" over and over again. Both have the same results like 20:50 o'clock post
Jon Cluck
@cluckj
Mar 09 19:59
did you do the bolus wizard setup?
Stargazer32584
@Stargazer32584
Mar 09 20:00
On the pump ? The bolus on the pump is on 0.5.
Jon Cluck
@cluckj
Mar 09 20:01
it's a menu on the pump: press ACT --> Bolus --> Bolus Wizard Setup --> Edit Settings
set Wizard "On" and input all the info it's asking for
Stargazer32584
@Stargazer32584
Mar 09 20:09
Okay...that was it !! The Wizard on the pump. Now, i have some data. What should i do next ?
Can i save the data for next reboot ?
Jon Cluck
@cluckj
Mar 09 20:12
nope! it should be able to pull that data directly off the pump whenever it loops (just like all the other pump models)
give it a reboot and see what happens
Stargazer32584
@Stargazer32584
Mar 09 20:19

The reboot is complete. Always with "reboot -f". Thank you for the hint.

The loop have one problem with the frequency. It was to many...:

https://drive.google.com/open?id=1xvgCS2yvXukHKyB8ifvGHiT14LQrZa2A

Jon Cluck
@cluckj
Mar 09 20:23
try cd ~/myopenaps && oref0-mmtune
Stargazer32584
@Stargazer32584
Mar 09 20:26

Okay...return is :

"mmtune: radio_locale = WW
2019/03/09 21:23:31 connected to CC111x radio on /dev/spidev0.0
2019/03/09 21:23:31 MEDTRONIC_FREQUENCY: strconv.ParseFloat: parsing "\n86845000000": invalid syntax
Usage: grep [OPTION]... PATTERN [FILE]...
Try 'grep --help' for more information."

Jon Cluck
@cluckj
Mar 09 20:27
hmm
@ecc1 ^
@Stargazer32584 can you cat ~/myopenaps/monitor/medtronic_frequency.ini
Stargazer32584
@Stargazer32584
Mar 09 20:31
Return from rig: 868450
Jon Cluck
@cluckj
Mar 09 20:32
is there a new line in there? does it look like:
#> cat ~/myopenaps/monitor/medtronic_frequency.ini

868450
Stargazer32584
@Stargazer32584
Mar 09 20:33

Yes...it is...:

root@APS:~# cat ~/myopenaps/monitor/medtronic_frequency.ini

868450
root@APS:~#

Jon Cluck
@cluckj
Mar 09 20:34
can you edit that file, and delete the empty space above the number? (while I figure out what's causing that)
Stargazer32584
@Stargazer32584
Mar 09 20:34
Yes...i will do with nano.
Jon Cluck
@cluckj
Mar 09 20:34
yep :thumbsup:
Stargazer32584
@Stargazer32584
Mar 09 20:39

Okay...I've done it with nano and reboot the system. Now, he shows a message with invalid frequency:

``mmtune: radio_locale = WW
2019/03/09 21:38:26 connected to CC111x radio on /dev/spidev0.0
2019/03/09 21:38:26 MEDTRONIC_FREQUENCY: invalid frequency 868450
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.
If pump and rig are close enough, this error usually self-resolves. Stand by for the next loop.
Unsuccessful oref0-pump-loop at Sat 9 Mar 21:38:39 CET 2019
´´

Jon Cluck
@cluckj
Mar 09 20:41
put a . in there so it reads 868.450
you don't need to reboot after every change :)
Stargazer32584
@Stargazer32584
Mar 09 20:41
Oh...little mistake...:-/
Stargazer32584
@Stargazer32584
Mar 09 20:49

Now...we have some other things. Things like that..;-):

Starting oref0-pump-loop at Sat 9 Mar 21:44:06 CET 2019 with 4 second wait_for_silence:
Waiting up to 4 minutes for new BG: First loop: not waiting

Listening for 4s: .No interfering pump comms detected from other rigs (this is a good thing!)
Continuing oref0-pump-loop at Sat 9 Mar 21:44:13 CET 2019
Preflight (x12 models do not support SMB safety checks, SMB will not be available.) OK. Old settings: jq: error (at settings/pumpprofile.json.new:1): Cannot index number with string "current_basal"
Invalid pumpprofile.json.new after refresh
-rw-r--r-- 1 root root 3 Mar 9 21:45 settings/pumpprofile.json.new
Could not parse autotune_data
Could not parse temptargets_data.
current_basal of 0 is not supported
jq: error (at settings/profile.json.new:1): Cannot index number with string "current_basal"
Invalid profile.json.new after refresh
-rw-r--r-- 1 root root 3 Mar 9 21:45 settings/profile.json.new
Profile valid. Full history refreshed through 2019-03-09T21:05:25+01:00
meal.json Could not parse profile data: SyntaxError: Unexpected end of JSON input
at JSON.parse (<anonymous>)
at Object.<anonymous> (/usr/local/lib/node_modules/oref0/bin/oref0-meal.js:61:29)
at Module._compile (module.js:652:30)
at Object.Module._extensions..js (module.js:663:10)
at Module.load (module.js:565:32)
at tryModuleLoad (module.js:505:12)
at Function.Module._load (module.js:497:3)
at Function.Module.runMain (module.js:693:10)
at startup (bootstrap_node.js:188:16)
at bootstrap_node.js:609:3
refreshed: { "carbs": 0, "mealCOB": 0, "reason": "Could not parse profile data" }
Listening for 10s: .No interfering pump comms detected from other rigs (this is a good thing!)
Continuing oref0-pump-loop at Sat 9 Mar 21:46:07 CET 2019
Checking that pump clock: "2019-03-09T21:46:56+01:00" is within 90s of current time: 2019-03-09T21:46:09+0100
Temp refreshmodule.js:674
throw err;
^

SyntaxError: /root/myopenaps/settings/profile.json: Unexpected end of JSON input
at JSON.parse (<anonymous>)
at Object.Module._extensions..json (module.js:671:27)
at Module.load (module.js:565:32)
at tryModuleLoad (module.js:505:12)
at Function.Module._load (module.js:497:3)
at Module.require (module.js:596:
at require (internal/module.js:11:18)
at Object.<anonymous> (/usr/local/lib/node_modules/oref0/bin/oref0-calculate-iob.js:50:22)
at Module._compile (module.js:652:30)
at Object.Module._extensions..js (module.js:663:10)

Couldn't calculate IOB
oref0-pump-loop failed. pump_loop_completed more than 15m old; waiting for 3 s silence before mmtuning

Listening for 3s: .No interfering pump comms detected from other rigs (this is a good thing!)
Continuing oref0-pump-loop at Sat 9 Mar 21:46:39 CET 2019
Listening for 3 s silence before mmtuning: Listening for 3s: .No interfering pump comms detected from other rigs (this is a good thing!)
Continuing oref0-pump-loop at Sat 9 Mar 21:46:43 CET 2019
mmtune: "868.500", 3, -44 -- "868.550", 3, -53
No wait required.
If pump and rig are close enough, this error usually self-resolves. Stand by for the next loop.
Unsuccessful oref0-pump-loop at Sat 9 Mar 21:47:18 CET 2019

Jon Cluck
@cluckj
Mar 09 20:50
let it run a couple more loops
it hasn't gotten all the data it needs yet
but these are good error messages, it means it's working
Stargazer32584
@Stargazer32584
Mar 09 20:51
Okay....one is for sure. YOU made my day....!!!!
Jon Cluck
@cluckj
Mar 09 21:00
anything new happening?
Stargazer32584
@Stargazer32584
Mar 09 21:09

Now, we have that:

Starting oref0-pump-loop at Sat 9 Mar 22:06:06 CET 2019 with 9 second wait_for_silence:
Waiting up to 4 minutes for new BG: First loop: not waiting

Listening for 9s: .No interfering pump comms detected from other rigs (this is a good thing!)
Continuing oref0-pump-loop at Sat 9 Mar 22:06:17 CET 2019
Preflight (x12 models do not support SMB safety checks, SMB will not be available.) OK. Old settings: jq: error (at settings/pumpprofile.json.new:1): Cannot index number with string "current_basal"
Invalid pumpprofile.json.new after refresh
-rw-r--r-- 1 root root 3 Mar 9 22:06 settings/pumpprofile.json.new
Could not parse autotune_data
Could not parse temptargets_data.
current_basal of 0 is not supported
jq: error (at settings/profile.json.new:1): Cannot index number with string "current_basal"
Invalid profile.json.new after refresh
-rw-r--r-- 1 root root 3 Mar 9 22:06 settings/profile.json.new
Profile valid. Pump history updated through 2019-03-09T21:05:25+01:00 with 0 new records; meal.json Could not parse profile data: SyntaxError: Unexpected end of JSON input
at JSON.parse (<anonymous>)
at Object.<anonymous> (/usr/local/lib/node_modules/oref0/bin/oref0-meal.js:61:29)
at Module._compile (module.js:652:30)
at Object.Module._extensions..js (module.js:663:10)
at Module.load (module.js:565:32)
at tryModuleLoad (module.js:505:12)
at Function.Module._load (module.js:497:3)
at Function.Module.runMain (module.js:693:10)
at startup (bootstrap_node.js:188:16)
at bootstrap_node.js:609:3
refreshed: { "carbs": 0, "mealCOB": 0, "reason": "Could not parse profile data" }
Listening for 8s: .No interfering pump comms detected from other rigs (this is a good thing!)
Continuing oref0-pump-loop at Sat 9 Mar 22:07:43 CET 2019
Checking that pump clock: "2019-03-09T22:08:32+01:00" is within 90s of current time: 2019-03-09T22:07:45+0100
Temp refreshmodule.js:674
throw err;
^

SyntaxError: /root/myopenaps/settings/profile.json: Unexpected end of JSON input
at JSON.parse (<anonymous>)
at Object.Module._extensions..json (module.js:671:27)
at Module.load (module.js:565:32)
at tryModuleLoad (module.js:505:12)
at Function.Module._load (module.js:497:3)
at Module.require (module.js:596:17)
at require (internal/module.js:11:18)
at Object.<anonymous> (/usr/local/lib/node_modules/oref0/bin/oref0-calculate-iob.js:50:22)
at Module._compile (module.js:652:30)
at Object.Module._extensions..js (module.js:663:10)

Couldn't calculate IOB
oref0-pump-loop failed. pump_loop_completed more than 15m old; waiting for 29 s silence before mmtuning

Jon Cluck
@cluckj
Mar 09 21:10
do you have basals set up?
(on the pump)
ACT --> Basal --> Basal Review (to check)
you shouldn't be using "Patterns", as those aren't supported
Stargazer32584
@Stargazer32584
Mar 09 21:14

Okay..Patterns are off. I have two points in Basal:
Standard 0.00U
1)00:00 0.00U/H
2)23:30 0.05U/H

That's for a test.

Jon Cluck
@cluckj
Mar 09 21:15
ah okay, so it's actually zero :laughing:
Stargazer32584
@Stargazer32584
Mar 09 21:15
That's my little handicap. I make the system for my sister and i haven't enough experince..
Jon Cluck
@cluckj
Mar 09 21:16
you'll need to change the zero basal to .05 or something
Stargazer32584
@Stargazer32584
Mar 09 21:18

Okay...Now it is:

Standard 1.20U
1)00:00 0.05
2)23:30 0.05

Jon Cluck
@cluckj
Mar 09 21:18
that should do it, keep an eye on the loop log!
Stargazer32584
@Stargazer32584
Mar 09 21:23

Wow !!!

Starting oref0-pump-loop at Sat 9 Mar 22:18:05 CET 2019 with 21 second wait_for_silence:
Waiting up to 4 minutes for new BG: First loop: not waiting

Listening for 21s: .No interfering pump comms detected from other rigs (this is a good thing!)
Continuing oref0-pump-loop at Sat 9 Mar 22:18:29 CET 2019
Preflight (x12 models do not support SMB safety checks, SMB will not be available.) OK. Old settings: Pump profile refreshed; Could not parse autotune_data
Could not parse temptargets_data.
No temptargets found.
Settings refreshed; Profile valid. Pump history updated through 2019-03-09T21:05:25+01:00 with 0 new records; meal.json Warning: could not parse monitor/carbhistory.json
refreshed: {"carbs":0,"nsCarbs":0,"bwCarbs":0,"journalCarbs":0,"mealCOB":0,"currentDeviation":0.68,"maxDeviation":5.96,"minDeviation":0.66,"slopeFromMaxDeviation":-0.989,"slopeFromMinDeviation":0.006,"allDeviations":[1,1,1,1,3,6],"lastCarbTime":0,"bwFound":false}
Listening for 10s: .No interfering pump comms detected from other rigs (this is a good thing!)
Continuing oref0-pump-loop at Sat 9 Mar 22:20:26 CET 2019
Checking that pump clock: "2019-03-09T22:21:15+01:00" is within 90s of current time: 2019-03-09T22:20:28+0100
Temp refreshed: monitor/temp_basal.json: {"duration":0,"temp":"absolute","rate":0}
{"carbs":0,"nsCarbs":0,"bwCarbs":0,"journalCarbs":0,"mealCOB":0,"currentDeviation":0.68,"maxDeviation":5.96,"minDeviation":0.66,"slopeFromMaxDeviation":-0.955,"slopeFromMinDeviation":0.006,"allDeviations":[1,1,1,1,3,6],"lastCarbTime":0,"bwFound":false}
{"iob":0.818,"activity":0.0069,"basaliob":0,"bolusiob":0.818,"netbasalinsulin":0,"bolusinsulin":1.2,"time":"2019-03-09T21:21:18.000Z","iobWithZeroTemp":{"iob":0.818,"activity":0.0069,"basaliob":0,"bolusiob":0.818,"netbasalinsulin":0,"bolusinsulin":1.2,"time":"2019-03-09T21:21:18.000Z"},"lastBolusTime":1552161925000,"lastTemp":{"date":0}}
{"delta":0,"glucose":400,"noise":1,"short_avgdelta":0,"long_avgdelta":0.63,"date":1552166324102,"last_cal":0}
Autosens ratio: 1; Basal unchanged: 0.05; ISF unchanged: 19.8; CR: 12
currenttemp: { duration: 0, temp: 'absolute', rate: 0 } lastTempAge: 25869441 m tempModulus: 21 m
SMB disabled (!microBolusAllowed)
profile.sens: 19.8 sens: 19.8 CSF: 1.6500000000000001
Carb Impact: 0.7 mg/dL per 5m; CI Duration: 0 hours; remaining CI (~2h peak): 0 mg/dL per 5m
UAM Impact: 0.7 mg/dL per 5m; UAM Duration: 0 hours
minPredBG: 386 minIOBPredBG: 387 minZTGuardBG: 384 minUAMPredBG: 384 avgPredBG: 386 COB: 0 / 0
BG projected to remain above 5.0 for 240 minutes
naive_eventualBG: 384 bgUndershoot: -319 zeroTempDuration: 240 zeroTempEffect: 4 carbsReq: -196
Setting neutral temp basal of 0.05U/hr
2019-03-09T21:21:00.099Z
Checking deliverAt: 2019-03-09T21:21:00.099Z is within 1m of current time: Sat 9 Mar 22:21:00 CET 2019
and that smb-suggested.json is less than 1m old
enact/smb-suggested.json: {"temp":"absolute","bg":400,"tick":"+0","eventualBG":388,"insulinReq":0,"reservoir":"93.8\n","deliverAt":"2019-03-09T21:21:00.099Z","sensitivityRatio":1,"COB":0,"IOB":0.818,"duration":30,"rate":0.05}
"COB: 0, Dev: 0.2, BGI: 0.0, ISF: 1.1, CR: 12, Target: 5.0, minPredBG 21.4, minGuardBG 21.3, IOBpredBG 21.6, UAMpredBG 21.3; Eventual BG 21.6 >= 5.0, IOB 0.82 > max_iob 0; setting current basal of 0.05 as temp. . Setting neutral temp basal of 0.05U/hr"
UAM: [400,399,399,398,397,397,396,395,395,394,394,393,393,392,392,391,391,390,390,389,389,388,388,388,387,387,387,387,386,386,386,386,385,385,385,385,385,385,384]
IOB: [400,400,400,400,400,399,399,399,398,398,397,397,396,396,395,395,394,394,394,393,393,392,392,392,391,391,391,390,390,390,390,389,389,389,389,389,389,388]
ZT: [400,399,399,398,397,397,396,395,395,394,394,393,393,392,392,391,391,390,390,389,389,388,388,388,387,387,387,387,386,386,386,386,385,385,385,385,385,385,384,384,384,384,384,384,384,384,384,384]
Temp refreshed: monitor/temp_basal.json: {"duration":0,"temp":"absolute","rate":0}
rm: cannot remove 'enact/smb-enacted.json': No such file or directory
enact/smb-enacted.json: "Rate: 0.05 Duration: 30"

Checking pump status (suspended/bolusing): x12 model detected. Temp refreshed: monitor/temp_basal.json: {"duration":30,"temp":"absolute","rate":0.05}
No bolus needed. glucose.json newer than pump_loop_completed
Your instance of oref0 [0.7.0-dev, x12-fix] is up-to-date.
Completed oref0-pump-loop at Sat 9 Mar 22:21:09 CET 2019
Jon Cluck
@cluckj
Mar 09 21:27
:clap:
Stargazer32584
@Stargazer32584
Mar 09 21:27
Man.....you are the best !!!!!!!!
In the end...we could say...the main reason was the data in the pump. Now, i understand the whole system much better.
Dana Lewis
@danamlewis
Mar 09 21:30
Yea!!!!!
Jon Cluck
@cluckj
Mar 09 21:31
there was a weird frequency thing in there too :)
Stargazer32584
@Stargazer32584
Mar 09 21:36
Heieiei....my sister is full of pleasure....
Jon Cluck
@cluckj
Mar 09 21:36
yay!
Stargazer32584
@Stargazer32584
Mar 09 21:36
Also a great THANK YOU from her !!
Jon Cluck
@cluckj
Mar 09 21:38
you're very welcome!
thanks for testing this code, it'll help a bunch of other folks out :)
Dana Lewis
@danamlewis
Mar 09 21:39
^ that!
Stargazer32584
@Stargazer32584
Mar 09 21:40
That's it ! To help any other person out there. The openAPS is a great project !!
Jon Cluck
@cluckj
Mar 09 21:44
:thumbsup:
kempera
@kempera
Mar 09 21:47
Dear all, I'm trying to update Openaps, but I get a weird error message:
openaps installed
Traceback (most recent call last):
File "/usr/local/bin/openaps", line 11, in <module>
import openaps
ImportError: No module named openaps
Any ideas how I could fix it?
Thanks for any hints! ;)
Jon Cluck
@cluckj
Mar 09 21:52
does setup error out after that?
kempera
@kempera
Mar 09 21:54
Yes:
Jon Cluck
@cluckj
Mar 09 21:55
can you run the command (oref0-setup?) again?
kempera
@kempera
Mar 09 21:56
Yes trying it again now
Error :(

Removing any existing git in /root/myopenaps/.git
Removed any existing git
Checking openaps 0.2.1 installation with --nogit support
Installing latest openaps w/ nogit
Downloading/unpacking git+https://github.com/openaps/openaps.git@nogit
Cloning https://github.com/openaps/openaps.git (to nogit) to /tmp/pip-ZOAuYW-build
fatal: unable to access 'https://github.com/openaps/openaps.git/': Could not resolve host: github.com
Complete output from command /usr/bin/git clone -q https://github.com/openaps/openaps.git /tmp/pip-ZOAuYW-build:


Cleaning up...
Command /usr/bin/git clone -q https://github.com/openaps/openaps.git /tmp/pip-ZOAuYW-build failed with error code 128 in None
Storing debug log for failure in /root/.pip/pip.log
Couldn't install openaps w/ nogit

Jon Cluck
@cluckj
Mar 09 22:03
Could not resolve host: github.com <-- your internet connection may be wonky
kempera
@kempera
Mar 09 22:07
Ok checking
kempera
@kempera
Mar 09 22:51
Thanks... it works now. But what can I do if the docs "profile.json", "pumpprofile.json and autotune.json" are all empty in my myopeaps folder?
Jon Cluck
@cluckj
Mar 09 22:53
profile and pumpprofile will be filled with data from your pump during the first couple loops
autotune.json will get data in it after 4am (when autotune runs)
kempera
@kempera
Mar 09 22:55
ok thanks for clarification"
and for your support! Great project - highly appreciated by my family & me :)
Jon Cluck
@cluckj
Mar 09 23:04
:thumbsup:
Dana Lewis
@danamlewis
Mar 09 23:25
@kempera :clap: happy looping!