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

27th
Jan 2018
Iain
@iainct
Jan 27 2018 00:01
the nightmare scenario has just eventuated, the buttons on my 722 pump have stopped responding, that is all buttons. Swapping the battery has not fixed the issue and for many months a battery change results in an A21 fault, that i cannot clear because the buttons are not working. Are there any known fixes within the community for this issue or reference i should look at?
davidwagaps
@davidwagaps
Jan 27 2018 00:07
@danamlewis thanks, thanks, thanks
Dana Lewis
@danamlewis
Jan 27 2018 00:07
:)
Iain
@iainct
Jan 27 2018 00:07
and now i cannot get any radio response from my backup pump, being MMT-722LCAS I understand I need to change the configuration to WW but I am not seeing any response, i am at a loss of what else to try...
Dana Lewis
@danamlewis
Jan 27 2018 00:07
@iainct have you seen some of the images of how to fix pump buttons?
Iain
@iainct
Jan 27 2018 00:08
I am aware of some videos etc, is it normal that all the buttons fail at once?
Dana Lewis
@danamlewis
Jan 27 2018 00:08
if you had a21 i wouldn't be surprised if they seem to not be working now. i'd definitely try the button clean and see if that resolves.
when you say radio response: how did you do it? did you change the SN in your run again, save it, and rerun oref0 setup?
Iain
@iainct
Jan 27 2018 00:09
change SN and pump region re ran set up
Dana Lewis
@danamlewis
Jan 27 2018 00:09
k. what are you getting in your logs, and how long has it been?
Iain
@iainct
Jan 27 2018 00:10
one moment
Starting oref0-pump-loop at Sat Jan 27 10:26:02 ACDT 2018 with 12 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
manually running mmtune i get
root@edi2:~/slicaps# cat monitor/mmtune.json
{
  "scanDetails": [
    [
      "868.150",
      0,
      -99
    ],
    [
      "868.174",
      0,
      -99
    ],
    [
      "868.198",
      0,
      -99
    ],
    [
      "868.222",
      0,
      -99
    ],
    [
      "868.246",
      0,
      -99
    ],
    [
      "868.270",
      0,
      -99
    ],
    [
      "868.294",
      0,
      -99
    ],
    [
      "868.318",
      0,
      -99
    ],
    [
      "868.342",
      0,
      -99
    ],
    [
      "868.366",
      0,
      -99
    ],
    [
      "868.390",
      0,
      -99
    ],
    [
      "868.414",
      0,
      -99
    ],
    [
      "868.438",
      0,
      -99
    ],
    [
      "868.462",
      0,
      -99
    ],
    [
      "868.486",
      0,
      -99
    ],
    [
      "868.510",
      0,
      -99
    ],
    [
      "868.534",
      0,
      -99
    ],
    [
      "868.558",
      0,
      -99
    ],
    [
      "868.582",
      0,
      -99
    ],
    [
      "868.606",
      0,
      -99
    ],
    [
      "868.630",
      0,
      -99
    ],
    [
      "868.654",
      0,
      -99
    ],
    [
      "868.678",
      0,
      -99
    ],
    [
      "868.702",
      0,
      -99
    ],
    [
      "868.726",
      0,
      -99
    ]
  ],
  "setFreq": 868.328,
  "usedDefault": true
}
at first i did not account for the region change and got the same lack of response
thisistw
@thisistw
Jan 27 2018 00:14
Hi everyone, I have just updated to the latest Dev version and since doing so have lost all coms between rig and pump. Even though the setup script is set to WW the pump is mmtune at 916.636 (not sure is this is the same issue as @iainct )
Iain
@iainct
Jan 27 2018 00:14
@thisistw I am on master
Looks like my frequency has been correctly set
e.g. WW and searching in the 868MHz range
thisistw
@thisistw
Jan 27 2018 00:15
just wondering why on my rig even though setup is set to WW why the mmtune is happening at 916
I have reflashed radio chip and re-run setup...???
Iain
@iainct
Jan 27 2018 00:22
@thisistw try reverting to master
thisistw
@thisistw
Jan 27 2018 00:22
yeah - might try that in a second
Iain
@iainct
Jan 27 2018 00:23
looking for any advice on testing comms to my WW pump.....
?
thisistw
@thisistw
Jan 27 2018 00:23
can anyone tell me what the normal contents of pump.ini looks like?
@iainct have you tried flashing the radio chip?
Iain
@iainct
Jan 27 2018 00:24
flash the radio chip? on an explorer board?
that is something i did with the Ti debugger but not the edison
thisistw
@thisistw
Jan 27 2018 00:26
In the past I had to do that (suspect it had overheated) - relatively simple just finding the link for you
Iain
@iainct
Jan 27 2018 00:36
@thisistw does spi1_alt2_EDISON_EXPLORER_US_STDLOC.hex work with a WW pump?
thisistw
@thisistw
Jan 27 2018 00:40
that is the script that I have used in the past for my WW pump
Iain
@iainct
Jan 27 2018 00:41
no improvement or change in the output
:-(
Dana Lewis
@danamlewis
Jan 27 2018 00:41
are you sure it's a WW pump, @iainct ?
Iain
@iainct
Jan 27 2018 00:41
'MMT-722LCAS' it came from Canada
and didn't get picked up on my US settings
Dana Lewis
@danamlewis
Jan 27 2018 00:42
CA is part of north america
switch back. you probably didn't give it enough time.
Iain
@iainct
Jan 27 2018 00:43
yep totally miss read that page
i'll swap back
Dana Lewis
@danamlewis
Jan 27 2018 00:43
:+1:
thisistw
@thisistw
Jan 27 2018 00:44
Any suggestions on why the latest Dev code and with setup script set to WW mmtune is using 916Mhz?
Iain
@iainct
Jan 27 2018 01:04
@danamlewis thank you, curse my inpatients had I have waited with just the SN change it would get got going doh!
:-D smiles all around here
Dana Lewis
@danamlewis
Jan 27 2018 01:04
:) 20 minute rule always. glad it's working!
thisistw
@thisistw
Jan 27 2018 01:13
I have my rig up an running again - after swapping the explorer board for a spare. If anyone has any suggestions why the explorer board was failing to tune at the correct frequency, please send me a message (time for sleep now as its 1:13am
Dana Lewis
@danamlewis
Jan 27 2018 01:14
did you check that the edison was firmly seated before on the perceived 'bad' board?
thisistw
@thisistw
Jan 27 2018 01:14
yes - all looked seated properly
Dana Lewis
@danamlewis
Jan 27 2018 01:15
looked? or unplugged and replugged to confirm?
thisistw
@thisistw
Jan 27 2018 01:15
just looked - by the time I had found tools to remove the mounting screws...
I will test the board again - probably tomorrow.
Dana Lewis
@danamlewis
Jan 27 2018 01:17
:+1: sounds like a good plan. have a good night!
thisistw
@thisistw
Jan 27 2018 01:17
thanks!
chriddetyp1
@chriddetyp1
Jan 27 2018 12:29
I just fully ramped up my Edison Rig (Oref0 0.6.0). I saw in the first days lots of interruptions (low temping) which causes lots of insulin gaps, which in return rewards me with raising BGs...Anyway I know from my previous therapy settings that BR are more accurate than ISF and carb ratios. I also kept an eye on steady TDD s and DIA is 6. I also run autotune and autosense. I considered it would be the best to raise slightly (+5%) first ISF on the pump (because of the interruptions) as I might be more sensitive. Anyway Oref0 seems to consider ISF from autosense (OpenAPS pill show different ISFs than in the pump), does autosense run against pumps settings if I´d raise there ISF? How do I see that this changes ISF in OpenAPS calculations? Does autosense care about this? I want to smooth insulin distribution...And also tend to have exploding BG after meals as I try to bolus in advance (1 IE / 1 hours prior eating) , but then during Oref0 low temps as it is forecasting lows...and it takes hours to get highs down...Is there something like a first weeks on Oref0 documentation? My previous therapy setting was more radical to avoid bg beyond 140 mg/dl...
Scott Leibrand
@scottleibrand
Jan 27 2018 16:34
Are you using eating soon mode (low temp targets) before and right after eating?
chriddetyp1
@chriddetyp1
Jan 27 2018 17:23
I administer a lower target in ns 1 hour in advance and for like 2 hours after meals. Meanwhile I switched off autosense and autotune and going to test (ISF, CR and BR) for the next weeks. I need to decrease volatility in all terms.
Scott Leibrand
@scottleibrand
Jan 27 2018 17:29
An objective to reduce the volatility / standard deviation in BG makes sense. I would not try to reduce the volatility / variation in insulin delivery: the entire point of a closed loop is to modulate insulin delivery (make it more variable) so as to make BG less variable / keep it inside a safe range.
What insulin are you using?
chriddetyp1
@chriddetyp1
Jan 27 2018 19:43
@scottleibrand I`m totally with you. I have well tested basal rate (or better profile if you consider up/down regulation) which keeps me steady around 110 mg/dl (prior looping). Initially I started with autotune and autosense. So autotune would assume lower basal rates and strong ISFs (low ISF number) which resulted in very bumpy stop and go insulin delivery ranging from high temping 4,30 IE for 5 minutes, then lowering and then low temping with zero IE. I´m using Apidra and sometimes Humalog. As I switched off today autotune and autosense I have wait for outcomes the next days. In the first 4 hours it seems to increase predictabilty and trend BGs seem to be less bumpy as strong stop and go faded away which is consistent with my observation above. Let´s see what´s happening the next days...