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

24th
Jun 2018
loztblaz
@loztblaz
Jun 24 2018 00:17
I'm attempting to run through the install steps outlined here, and encountering a couple issues. http://openaps.readthedocs.io/en/latest/docs/Build%20Your%20Rig/pi-install.html I'm a Pi zero with an explorer hat.
First issue is that at the end of the oref0 setup script, i get
Checking oref0 installation
npm ERR! not ok code 1
Installing latest oref0 from /root/src/oref0/
which sends it back into a reinstall, and then errors out at

Checking mmeowlink installation
Version: 0.11.1
module.js:327
throw err;
^

Error: Cannot find module 'lodash'
at Function.Module._resolveFilename (module.js:325:15)
at Function.Module._load (module.js:276:25)
at Module.require (module.js:353:17)
at require (internal/module.js:12:17)
at Object.<anonymous> (/root/src/oref0/lib/profile/basal.js:2:9)
at Module._compile (module.js:409:26)
at Object.Module._extensions..js (module.js:416:10)
at Module.load (module.js:343:32)
at Function.Module._load (module.js:300:12)
at Module.require (module.js:353:17)
Could not run oref0-get-profile

I understand my hardware setup is a bit new, so the docs may not be totally updated. Should I be ignoring the part where I ctrl-c out of the initial setup script and move to a raspian compatible dev branch? This also isn't a critical thing for me, as I'm currently working through other treatment changes on my non-loop pump, so I'm not in need of immediate help or anything.
loztblaz
@loztblaz
Jun 24 2018 00:50
alright, figured out that the npm err was likely due to an old npm version from the raspbian package manager, updated and it's not giving that error anymore. 1.4.21 -> 5.6.0
still hitting that error when checking mmeowlink installation though. will keep poking at it.
loztblaz
@loztblaz
Jun 24 2018 00:56
also with updated npm i got a debug log for the error, which i can share if desired but won't right now since i've already dumped enough into this chat for now
loztblaz
@loztblaz
Jun 24 2018 03:59
... nevermind, i tried the old faithful "flatten and reinstall" following the exact same steps and it all worked perfectly. weird, but happy.
JohnDoeAkira
@JohnDoeAkira
Jun 24 2018 18:13
First problem. I got an error in the edison openaps logs :
mmeowlink.exceptions.CommsException: Could not get subg_rfspy state or version. Have you got the right port/device and radio_type?
N3FM
@N3FM
Jun 24 2018 18:13
@ecc1 @scottleibrand Really looking forward to Go-based CGM monitor/history code in 0.7.0... I can't run 0.7.0 till then, as Enlite cgm immediately blows up.
JohnDoeAkira
@JohnDoeAkira
Jun 24 2018 18:14
I have an edison+explorer with enlite sensors. It was looping fine until this afternoon. The edison rebooted to clear the problem but it did not change.
I get a list of tens of : retry 0 (Do you need to run 'export RFSPY_RTSCTS=0' first?)
Scott Leibrand
@scottleibrand
Jun 24 2018 18:53
@N3FM there is some work ongoing to get MDT CGM working before that. See @juehv’s recent comments in https://gitter.im/openaps/oref0
JohnDoeAkira
@JohnDoeAkira
Jun 24 2018 20:26
OK, it might have been a low level of battery. BTW, I changed to a 18650 (LG-HE4) instead of a lipo to power my edison rig. I printed this enclosure : https://www.thingiverse.com/thing:2798858
The closing could probably be improved but it'a a nice enclosure !!
Jens Heuschkel
@juehv
Jun 24 2018 20:54
@JohnDoeAkira just a minor comment on using li-ion instead of lipo: the li-ion batteries go way lower in voltage (around 2.8 depending on the exact model). Hence, if you want to use the whole capacity you may have to modify the rig.
JohnDoeAkira
@JohnDoeAkira
Jun 24 2018 21:04
Ah good to know. And the rig is meant to be used with Lipo ? Is there a min voltage under which the explorer board stops working to protect the Lipo ? Is that what you mean ?
Jens Heuschkel
@juehv
Jun 24 2018 21:21
that's exactly what I mean ;)
N3FM
@N3FM
Jun 24 2018 21:32
@scottleibrand @juehv Thanks to you both! Yes, Jens is going exactly down the solution path for me! I expect this work will also fix the software issues being experienced by @JohnDoeAkira, as he has an identical front end to my rig (Edison/Explorer/722/Enlite) However, without a second rig, it's a bit of an ordeal to try 0.7.0 and then switch back to 0.6.2 for 'live' control.
garykidd
@garykidd
Jun 24 2018 23:00
anyone having issues with display on pihat...mine started to show what looks to be every other horizontal line....then no lines.....?
Martin Haeberli
@mhaeberli
Jun 24 2018 23:15
@garykidd alas, in my experience, the ‘every other line’ failure mode is so common that: 2 of my 5 initial Pi Hats arrived that way; and at least one other failed that way after a while… :-(
garykidd
@garykidd
Jun 24 2018 23:19
@mhaeberli were you able to repair any of them?
Martin Haeberli
@mhaeberli
Jun 24 2018 23:20
no - i DID acquire what were likely good spares, pretty cheap, maybe $6 each at Amazon. BUT I trashed one of the Hat boards taking the broken display out
at which point I decided, not worth breaking another one...