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

19th
Nov 2018
Martin Haeberli
@mhaeberli
Nov 19 2018 01:27
how do i do a standalone mmtune on Edison / dev ?
Eric
@ecc1
Nov 19 2018 01:29
make sure you've set MEDTRONIC_PUMP_ID in your environment, then run mmtune from the command line
Martin Haeberli
@mhaeberli
Nov 19 2018 01:29
  • found this note : OREF0_DEBUG=1 oref0-mmtune
which seems to be working
@ecc1 thanks!
@ecc1 mmtune failed. is it possible I should re-flash the radio?
Eric
@ecc1
Nov 19 2018 01:32
unlikely. what's the failure?
cduarte
@cduarte
Nov 19 2018 01:32
is secutiry to use enableSMB_always with logger ?
Martin Haeberli
@mhaeberli
Nov 19 2018 01:35
pump 1 foot away. all other rigs see pump. mmtune finds no signal on this rig
btw, tried to re-flash, but got this error:
./ccprog -p 19,7,36 erase
./ccprog: error while loading shared libraries: libmraa.so.0: cannot open shared object file: No such file or directory
Eric
@ecc1
Nov 19 2018 01:36
please paste the actual log output from mmtune
Martin Haeberli
@mhaeberli
Nov 19 2018 01:38

head of log:

2018/11/18 17:37:46 setting frequency to 916.550
2018/11/18 17:37:48 waking pump
2018/11/18 17:38:03 no response to wakeup
2018/11/18 17:38:03 frequency set to 916.300
2018/11/18 17:38:04 frequency set to 916.350
2018/11/18 17:38:05 frequency set to 916.400
2018/11/18 17:38:07 frequency set to 916.450
2018/11/18 17:38:09 frequency set to 916.500
2018/11/18 17:38:10 frequency set to 916.550
2018/11/18 17:38:12 frequency set to 916.600
2018/11/18 17:38:13 frequency set to 916.650
2018/11/18 17:38:14 frequency set to 916.700
2018/11/18 17:38:16 frequency set to 916.750
2018/11/18 17:38:18 frequency set to 916.800
2018/11/18 17:38:19 frequency set to 916.850

tail of it:

    [
      "916.800",
      0,
      -128
    ],
    [
      "916.850",
      0,
      -128
    ],
    [
      "916.900",
      0,
      -128
    ]
  ],
  "setFreq": 916.6,
  "usedDefault": true
}
so i guess re- flashing won’t help
Eric
@ecc1
Nov 19 2018 01:43
does this rig have an external antenna? if so, check that it's connected securely. has it communicated well in the past (with master branch for example)?
Martin Haeberli
@mhaeberli
Nov 19 2018 01:43
yes, yes external antenna, will try to reconnect thx
Eric
@ecc1
Nov 19 2018 01:44
and if you've got an SDR or wideband receiver, you can doublecheck that there's a signal on 916 MHz
Martin Haeberli
@mhaeberli
Nov 19 2018 01:47
sad - looks like antenna connector on explorer has a micro-flaw
ArvoNiilo
@ArvoNiilo
Nov 19 2018 07:12
Monday withH48 and this morning my Veo stoped and emptied its I memory after 52.I hope they have nothing to with my OpenAps.
ArvoNiilo
@ArvoNiilo
Nov 19 2018 07:29
Sorry.my message began: does anybody know what error codes H52 and H52 mean? My paradig stopped last Monday withH48 and Veo today withH52.
gjarreau
@gjarreau
Nov 19 2018 15:13
using openaps now for about a month and I would like to enable SMB. How would I do that? Do I have to have oref1 instead of oref0 to begin?
if I just have to change the preferences file, does anyone have the command lines to insert?
wfeddern
@wfeddern
Nov 19 2018 16:00
Looking like my screen died on my piHAT again, this time getting errors though:

Updating HAT Display...
fs.js:735
return binding.writeBuffer(fd, buffer, offset, length, position);
^

Error: EREMOTEIO: remote I/O error, write
at Object.fs.writeSync (fs.js:735:20)
at Bus.i2cWriteSync (/root/src/openaps-menu/node_modules/i2c-bus/i2c-bus.js:348:13)
at Oled._transfer (/root/src/openaps-menu/node_modules/oled-i2c-bus/oled.js:136:25)
at Oled._initialise (/root/src/openaps-menu/node_modules/oled-i2c-bus/oled.js:110:10)
at new Oled (/root/src/openaps-menu/node_modules/oled-i2c-bus/oled.js:81:8)
at Object.init (/root/src/openaps-menu/lib/display/ssd1306.js:36:24)
at module.exports (/root/src/openaps-menu/lib/display/ssd1306.js:68:13)
at Object.<anonymous> (/root/src/openaps-menu/scripts/status.js:41:68)
at Module._compile (module.js:652:30)
at Object.Module._extensions..js (module.js:663:10)

Will this prevent the rest of the loop from running? I can live with no screen.
Actually, looks like after last restart it is working again, just with no screen.
Scott Leibrand
@scottleibrand
Nov 19 2018 17:18
@cduarte you're using Dexcom G5 with Logger, and asking whether it's safe to use enableSMB_always with that? If you're calibrating the G5 normally through the Dexcom G5 app, and Logger is just reporting the glucose values directly from the G5 (not applying any local calibration), then it should be fine. If you're doing things differently than that, please specify.
ArvoNiilo
@ArvoNiilo
Nov 19 2018 18:22
Hi . I'd like to return to my messages from thus morning from a better device. So, last Monday my Paradigm 722 displayed message H48 and crached completely. Today morning my Veo showed H52, stopped working, emptied its memory but recovered. Thus I have teo questions:
Does anybidy know
Does anybody know wgat these codes mean? Is it possible that they would stem from some ussue from mt OpenAps rig?
Dana Lewis
@danamlewis
Nov 19 2018 18:24
H48? i've not heard of that error message before. Are you sure it was H?
A52 is possible if there is a bolus ongoing while an smb is delivered, and will cause the pump to crash and reboot.
JovanyR
@JovanyR
Nov 19 2018 18:36
Hello everyone, I'm very happy to see such an active community here. I see you all are getting into the details and I was hoping you all could point me in the right direction to help me get started. I have been reading through the OpenAPS docs but I don't even use a pump or CGM currently/ever so I don't understand what 90% of it even means. It is very overwhelming. I would hate to jump on here and start asking a million basic questions. If anyone is willing to spare some time to help me out, I would greatly appreciate it.
Dana Lewis
@danamlewis
Nov 19 2018 18:46
@JovanyR (welcome!) I think the first steps would be to get a CGM and get a pump, and get familiar with those first. That itself is it's own learning curve; then there's an additional learning curve for using OpenAPS
Dana Lewis
@danamlewis
Nov 19 2018 18:53
I would also join the "Looped" group on Facebook - there's a lot of great history in there, with questions about much of the basics, which are also good to read/start soaking up as you get started
JovanyR
@JovanyR
Nov 19 2018 18:53
@danamlewis Thank you for your response. I noticed most of the gear must be older. Does anyone know if it is possible to get any of it with insurance? Also, I always have trouble making a decision with so many options. I'm not sure what I should be looking for when choosing the right one (this is in reference to the CGM primarily). Is this something my doctor can help me with or is there a high chance he will be bias?
Scott Leibrand
@scottleibrand
Nov 19 2018 18:54
what country are you in?
Dana Lewis
@danamlewis
Nov 19 2018 18:54
CGM = yes to insurance. Any CGM works.
JovanyR
@JovanyR
Nov 19 2018 18:54
Unfortunately, I do not have Facebook.
US
Dana Lewis
@danamlewis
Nov 19 2018 18:55
some physicians don't encourage DIY, others are more helpful - so it really varies doctor to doctor, and depends a lot on your relationship with them. chances are though you'll get more help from the community
and in the case of being US based, yes, you need the older pump which you can't get on insurance -b ut the supplies can be recevied through insurance (because they match the current pumps)
ArvoNiilo
@ArvoNiilo
Nov 19 2018 18:56
I tried to restart my Paradigm and the error code is indeed H48.
Dana Lewis
@danamlewis
Nov 19 2018 18:57
@ArvoNiilo what country are you in? i would google and see if you can find anything about that error message
JovanyR
@JovanyR
Nov 19 2018 18:57
Unfortunately, that will actually put a hold on this for a little while. Thank you all so much for the help!
Dana Lewis
@danamlewis
Nov 19 2018 18:57
(pumps can be found for free, though, so if you're interested I would look anyway) @JovanyR
JovanyR
@JovanyR
Nov 19 2018 18:58
I will do that. Thank you!
Dana Lewis
@danamlewis
Nov 19 2018 18:58
:+1:
ArvoNiilo
@ArvoNiilo
Nov 19 2018 19:21
Finland.
Dana Lewis
@danamlewis
Nov 19 2018 19:21
@sulkaharo have you ever seen H48? ^
ArvoNiilo
@ArvoNiilo
Nov 19 2018 20:00
As to Veo, alert history gives H52 at 08:47 (Finnish time)
Garrett Webb
@garetis
Nov 19 2018 23:53
I reinstalled the bootstrap script on my Edison/Explorer board, and ended up with this message. Is this a problem or is it because I reinstalled with a version that already existed?
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 npm : Depends: nodejs but it is not going to be installed
       Depends: node-abbrev (>= 1.0.4) but it is not going to be installed
       Depends: node-ansi (>= 0.3.0-2) but it is not going to be installed
       Depends: node-ansi-color-table but it is not going to be installed
       Depends: node-archy but it is not going to be installed
       Depends: node-block-stream but it is not going to be installed
       Depends: node-fstream (>= 0.1.22) but it is not going to be installed
       Depends: node-fstream-ignore but it is not going to be installed
       Depends: node-github-url-from-git but it is not going to be installed
       Depends: node-glob (>= 3.1.21) but it is not going to be installed
       Depends: node-graceful-fs (>= 2.0.0) but it is not going to be installed
       Depends: node-inherits but it is not going to be installed
       Depends: node-ini (>= 1.1.0) but it is not going to be installed
       Depends: node-lockfile but it is not going to be installed
       Depends: node-lru-cache (>= 2.3.0) but it is not going to be installed
       Depends: node-minimatch (>= 0.2.11) but it is not going to be installed
       Depends: node-mkdirp (>= 0.3.3) but it is not going to be installed
       Depends: node-gyp (>= 0.10.9) but it is not going to be installed
       Depends: node-nopt (>= 3.0.1) but it is not going to be installed
       Depends: node-npmlog but it is not going to be installed
       Depends: node-once but it is not going to be installed
       Depends: node-osenv but it is not going to be installed
       Depends: node-read but it is not going to be installed
       Depends: node-read-package-json (>= 1.1.0) but it is not going to be installed
       Depends: node-request (>= 2.25.0) but it is not going to be installed
       Depends: node-retry but it is not going to be installed
       Depends: node-rimraf (>= 2.2.2) but it is not going to be installed
       Depends: node-semver (>= 2.1.0) but it is not going to be installed
       Depends: node-sha but it is not going to be installed
       Depends: node-slide but it is not going to be installed
       Depends: node-tar (>= 0.1.18) but it is not going to be installed
       Depends: node-underscore but it is not going to be installed
       Depends: node-which but it is not going to be installed
E: Unable to correct problems, you have held broken packages.