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

22nd
Apr 2019
Dana Lewis
@danamlewis
Apr 22 01:18
Just released 0.6.3 - this should resolve the issues people were having installing master. Nothing special needed, just follow the docs and it should work for re-installing or new master installs. Full release notes at https://github.com/openaps/oref0/releases
kudos and :clap: to @cluckj for ID'ing and troubleshooting and resolving the issues on this one :confetti_ball:
(Even if your rig says you're 12 commits out of date on master - no need to re-install, these changes just impact the setup process - no algorithm changes are involved)
Jonathan Arms
@phinious_arms_twitter
Apr 22 01:48
I'm hoping someone can help me get my rig set up. I'm not a programmer. I have a Medtronic 723 pump, Dexcom G6, and Edison w/ Explorer. Heroku, xDrip and Nightscout are set up. My pump is connected to WiFi and it is also communicating with my pump. However, the time zone is showing EDT when it should be PDT. I don't know how to change this. More significantly, I don't think the Edison is picking up my blood sugar reading which are displayed in xDrip and Nightscout.

This is a cut and paste of my log....Listening for 24s: .No interfering pump comms detected from other rigs (this is a good thing!)
Continuing oref0-pump-loop at Sun Apr 21 11:55:34 EDT 2019
Preflight fail. Retry 1 of preflight
Preflight fail. Listening for 9s: .No interfering pump comms detected from other rigs (this is a good thing!)
Continuing oref0-pump-loop at Sun Apr 21 11:56:55 EDT 2019
Retry 2 of preflight
Preflight fail. Listening for 24s: .No interfering pump comms detected from other rigs (this is a good thing!)
Continuing oref0-pump-loop at Sun Apr 21 11:57:55 EDT 2019
Retry 3 of preflight
Preflight fail. Couldn't preflight
oref0-pump-loop failed. pump_loop_completed more than 15m old; waiting for 43 s silence before mmtuning
Listening for 43s: .
Starting oref0-pump-loop at Sun Apr 21 12:00:06 EDT 2019 with 17 second wait_for_silence:
Waiting up to 4 minutes for new BG: First loop: not waiting

Listening for 17s: .No interfering pump comms detected from other rigs (this is a good thing!)
Continuing oref0-pump-loop at Sun Apr 21 12:00:28 EDT 2019
Preflight fail. Retry 1 of preflight
Preflight fail. Listening for 10s: .No interfering pump comms detected from other rigs (this is a good thing!)
Continuing oref0-pump-loop at Sun Apr 21 12:01:50 EDT 2019
Retry 2 of preflight
Preflight fail. Listening for 17s: .No interfering pump comms detected from other rigs (this is a good thing!)
Continuing oref0-pump-loop at Sun Apr 21 12:02:43 EDT 2019
Retry 3 of preflight
Preflight No updates to pump-loop.log in 5m - killing processes

Starting oref0-pump-loop at Sun Apr 21 21:38:07 EDT 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 Sun Apr 21 21:38:20 EDT 2019
Preflight fail. Retry 1 of preflight
Preflight fail. Listening for 4s: .No interfering pump comms detected from other rigs (this is a good thing!)
Continuing oref0-pump-loop at Sun Apr 21 21:39:36 EDT 2019
Retry 2 of preflight
Preflight fail. Listening for 9s: .No interfering pump comms detected from other rigs (this is a good thing!)
Continuing oref0-pump-loop at Sun Apr 21 21:40:22 EDT 2019
Retry 3 of preflight
Preflight fail. Couldn't preflight
oref0-pump-loop failed. pump_loop_completed more than 15m old; waiting for 20 s silence before mmtuning
Listening for 20s: .No interfering pump comms detected from other rigs (this is a good thing!)
Continuing oref0-pump-loop at Sun Apr 21 21:41:18 EDT 2019
Listening for 20 s silence before mmtuning: Listening for 20s: .No interfering pump comms detected from other rigs (this is a good thing!)
Continuing oref0-pump-loop at Sun Apr 21 21:41:39 EDT 2019
mmtune:
waiting for 90 second si

Jonathan Arms
@phinious_arms_twitter
Apr 22 02:05
@danamlewis Thanks! Time zone is now set. Any suggestions on ho I can get my Edison to pick up my BG readings?
Dana Lewis
@danamlewis
Apr 22 02:06
let's start with troubleshooting pump communications first, as it doesn't appear to be connecting to the pump. can you cat your runagain file and doublecheck that your pump SN is correct? cd ~/myopenaps && cat oref0-runagain.sh
(don't paste it here, though - just check it yourself)
Jonathan Arms
@phinious_arms_twitter
Apr 22 02:13
Silly mistake. I took the battery out of my pump last night because the alarm was going off. (I using Omnipods until I get my loop openAPS set up.)

This is the message I'm getting. Starting oref0-pump-loop at Sun Apr 21 19:09:06 PDT 2019 with 11 second wait_for_silence:
Waiting up to 4 minutes for new BG: First loop: not waiting

Listening for 11s: .No interfering pump comms detected from other rigs (this is a good thing!)
Continuing oref0-pump-loop at Sun Apr 21 19:09:18 PDT 2019
Preflight OK. Profile less than 60m old; Profile valid. Full history refreshed through null
meal.json
Warning: setting mealCOB to 0 because currentDeviation is null/undefined
refreshed: {"carbs":0,"nsCarbs":0,"bwCarbs":0,"journalCarbs":0,"mealCOB":0,"currentDeviation":null,"maxDeviation":0,"minDeviation":999,"slopeFromMaxDeviation":0,"slopeFromMinDeviation":999,"allDeviations":[],"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 Sun Apr 21 19:09:43 PDT 2019
Checking that pump clock: "2007-01-01T00:02:01-08:00" is within 90s of current time: 2019-04-21T19:09:45-0700
Pump clock is more than 55s off: attempting to reset it and reload pumphistory
Checking pump status (suspended/bolusing): {"status":"error","bolusing":false,"suspended":false}
Error: pump clock refresh error / mismatch
oref0-pump-loop failed. pump_loop_completed more than 15m old; waiting for 21 s silence before mmtuning
Listening for 21s: .No interfering pump comms detected from other rigs (this is a good thing!)
Continuing oref0-pump-loop at Sun Apr 21 19:10:09 PDT 2019
Listening for 21 s silence before mmtuning: Listening for 21s: .No interfering pump comms detected from other rigs (this is a good thing!)
Continuing oref0-pump-loop at Sun Apr 21 19:10:31 PDT 2019
mmtune: "916.650", 3, -75
waiting for 30 second silence before continuing
Listening for 30s: .No interfering pump comms detected from other rigs (this is a good thing!)
Continuing oref0-pump-loop at Sun Apr 21 19:11:21 PDT 2019
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 Sun Apr 21 19:11:21 PDT 2019

Dana Lewis
@danamlewis
Apr 22 02:13
:D that was going to be my guess (pump not fully in use)
so that's good - time zone is good, it's reading from the pump
give it a few minutes and it should be on it's way
Jonathan Arms
@phinious_arms_twitter
Apr 22 02:22

It's still not picking up my BG readings. I'll give it more time. This is the latest...Continuing oref0-pump-loop at Sun Apr 21 19:16:21 PDT 2019
Preflight OK. Profile less than 60m old; Profile valid. Full history refreshed through null
meal.json refreshed: {"carbs":0,"nsCarbs":0,"bwCarbs":0,"journalCarbs":0,"mealCOB":0,"currentDeviation":0.33,"maxDeviation":3,"minDeviation":0.67,"slopeFromMaxDeviation":-1.846,"slopeFromMinDeviation":0,"allDeviations":[0,3,1,3,1,1],"lastCarbTime":0,"bwFound":false}
Listening for 1s: .No interfering pump comms detected from other rigs (this is a good thing!)
Continuing oref0-pump-loop at Sun Apr 21 19:16:43 PDT 2019
Checking that pump clock: "2019-04-21T19:16:06-07:00" is within 90s of current time: 2019-04-21T19:16:44-0700
Error: pumphistory-24h >5m old (or empty)
oref0-pump-loop failed. pump_loop_completed more than 15m old; waiting for 2 s silence before mmtuning
Listening for 2s: .No interfering pump comms detected from other rigs (this is a good thing!)
Continuing oref0-pump-loop at Sun Apr 21 19:16:48 PDT 2019
Listening for 2 s silence before mmtuning: Listening for 2s: .No interfering pump comms detected from other rigs (this is a good thing!)
Continuing oref0-pump-loop at Sun Apr 21 19:16:51 PDT 2019
mmtune: "916.600", 3, -69 -- "916.650", 3, -75
waiting for 30 second silence before continuing
Listening for 30s: .No interfering pump comms detected from other rigs (this is a good thing!)
Continuing oref0-pump-loop at Sun Apr 21 19:17:42 PDT 2019
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 Sun Apr 21 19:17:42 PDT 2019

Starting oref0-pump-loop at Sun Apr 21 19:18:06 PDT 2019 with 19 second wait_for_silence:
Waiting up to 4 minutes for new BG: First loop: not waiting

Listening for 19s: .No interfering pump comms detected from other rigs (this is a good thing!)
Continuing oref0-pump-loop at Sun Apr 21 19:18:26 PDT 2019
Preflight OK. Profile less than 60m old; Profile valid. Full history refreshed through null
meal.json refreshed: {"carbs":0,"nsCarbs":0,"bwCarbs":0,"journalCarbs":0,"mealCOB":0,"currentDeviation":0.33,"maxDeviation":3,"minDeviation":0.67,"slopeFromMaxDeviation":-1.433,"slopeFromMinDeviation":0,"allDeviations":[0,3,1,3,1,1],"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 Sun Apr 21 19:18:57 PDT 2019
Checking that pump clock: "2019-04-21T19:18:20-07:00" is within 90s of current time: 2019-04-21T19:18:58-0700
Error: pumphistory-24h >5m old (or empty)
oref0-pump-loop failed. pump_loop_completed more than 15m old; waiting for 35 s silence before mmtuning
Listening for 35s: .No interfering pump comms detected from other rigs (this is a good thing!)
Continuing oref0-pump-loop at Sun Apr 21 19:19:35 PDT 2019
Listening for 35 s silence before mmtuning: Listening for 35s: .No interfering pump comms detected from other rigs (this is a good thing!)
Continuing oref0-pump-loop at Sun Apr 21 19:20:11 PDT 2019
mmtune: "916.550", 3, -70
waiting for 20 second silence before continuing
Listening for 20s: .No interfering pump comms detected from other rigs (this is a good thing!)
Continuing oref0-pump-loop at Sun Apr 21 19:20:52 PDT 2019
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 Sun Apr 21 19:20:52 PDT 2019

Dana Lewis
@danamlewis
Apr 22 02:22
give it the >20 minutes to do a full pump history read before it'll do anything else
Jonathan Arms
@phinious_arms_twitter
Apr 22 02:24
Sounds good. I'll let you know if it starts working shortly.
Jon Cluck
@cluckj
Apr 22 02:24
@LuminaryXion is that on a fresh install?
Jonathan Arms
@phinious_arms_twitter
Apr 22 02:43
@danamlewis Still not working. One thing I should have mentioned is that I'm still waiting for my reservoir. I didn't think the reservoir would be needed in order to pick up reading and get the loop to work, but maybe it does. Here's the message I'm seeing...Listening for 23s: .No interfering pump comms detected from other rigs (this is a good thing!)
Continuing oref0-pump-loop at Sun Apr 21 19:38:30 PDT 2019
Preflight OK. Profile less than 60m old; Profile valid. Full history refreshed through null
meal.json refreshed: {"carbs":0,"nsCarbs":0,"bwCarbs":0,"journalCarbs":0,"mealCOB":0,"currentDeviation":1.67,"maxDeviation":4.67,"minDeviation":0.33,"slopeFromMaxDeviation":-1.599,"slopeFromMinDeviation":0.275,"allDeviations":[2,5,2,3,0,3],"lastCarbTime":0,"bwFound":false}
Listening for 2s: .No interfering pump comms detected from other rigs (this is a good thing!)
Continuing oref0-pump-loop at Sun Apr 21 19:38:52 PDT 2019
Checking that pump clock: "2019-04-21T19:38:16-07:00" is within 90s of current time: 2019-04-21T19:38:54-0700
Error: pumphistory-24h >5m old (or empty)
oref0-pump-loop failed. pump_loop_completed more than 15m old; waiting for 39 s silence before mmtuning
Listening for 39s: .No interfering pump comms detected from other rigs (this is a good thing!)
Continuing oref0-pump-loop at Sun Apr 21 19:39:34 PDT 2019
Listening for 39 s silence before mmtuning: Listening for 39s: .No interfering pump comms detected from other rigs (this is a good thing!)
Continuing oref0-pump-loop at Sun Apr 21 19:40:15 PDT 2019
mmtune: "916.600", 3, -50 -- "916.650", 3, -51
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 Sun Apr 21 19:40:35 PDT 2019
Dana Lewis
@danamlewis
Apr 22 02:44
is your pump "working" without the reservoir? it may need you to do a few boluses and temp basals into the air to get some history records for it to read
Jonathan Arms
@phinious_arms_twitter
Apr 22 02:47
@danamlewis Unfortunately my doctor and Medtronic have been like the keystone cops so I'm still waiting on my supplies. They should arrive later this week. I'll try again once my supplies arrive. Thanks for your help.
Dana Lewis
@danamlewis
Apr 22 03:09
No, you don’t need a reservoir or any supplies to get started
Put your finger in and apply a little pressure when priming
Then set up your pump with basals etc and do a few manual things to get history
If you want to wait, that’s fine too, but if you’re still curious you should be able to get it looping
Jonathan Arms
@phinious_arms_twitter
Apr 22 05:07
@danamlewis I should get the supplies in the next couple of days. I'll probably just wait until they arrive. I'll let you if I'm successful.
Dana Lewis
@danamlewis
Apr 22 05:17
:+1:
marafie
@marafie
Apr 22 09:17
Your configuration specifies to merge with the ref 'refs/heads/setup-improvements'
from the remote, but no such ref was fetched.
Couldn't pull latest oref0
root@raspberrypi:~#
any help on this ?
tzachi-dar
@tzachi-dar
Apr 22 09:23
@marafie what git did you run?
marafie
@marafie
Apr 22 09:42
@tzachi-dar $ cd ~/src/oref0 && git fetch && git checkout setup-improvements && git pull && npm run global-install
i had this error
mmtune: 2019/04/21 15:18:42 cannot connect to CC111x radio on /dev/spidev0.0
2019/04/21 15:18:42 cc111x: no response
2019/04/21 15:18:44 cannot connect to CC111x radio on /dev/spidev0.0
2019/04/21 15:18:44 cc111x: no response
so riko suggested to run the setup improvements
LuminaryXion
@LuminaryXion
Apr 22 10:34
@cluckj Hi Jon, yeah reflashed and fresh installed. Tried the apt-get clean/update/install, but same error
tzachi-dar
@tzachi-dar
Apr 22 10:51
@marafie I'm not sure if this are hw problems or sw problems. What device are you using?
tzachi-dar
@tzachi-dar
Apr 22 11:55
Just did another install on a pi. Seems like a new problem :-(
After the first step: curl -s https://raw.githubusercontent.com/openaps/oref0/dev/bin/openaps-install.sh > /tmp/openaps-install.sh && bash /tmp/openaps-install.sh
I got:
sudo: npm: command not found
It can easily be fixed by: sudo apt-get install npm and running the command again.
marafie
@marafie
Apr 22 12:15
raspberry pi
@tzachi-dar raspberry pi zero
jvemme
@jvemme
Apr 22 12:23
Hi. I think i mentioned this before. But if anyone is interested, im looking to start a windows setup/installation utillity where it should be easy to chose and checkout different branches. Maybe as a log gathering tool, and other features.
marafie
@marafie
Apr 22 12:30
@jvemme it would be nice and if you can do the same think like pibakery does
jvemme
@jvemme
Apr 22 13:18
Im not thinking just as Pibakery, I would like to do a tool only ment for Openaps, and thus with tools and features for this only. pibakery would still be needed for intial start, if it aint broke...
NSewar
@nsewar01
Apr 22 13:30
basic question - can my edison connect to home wifi if it is serial connected to putty?
tzachi-dar
@tzachi-dar
Apr 22 13:54
@marafie I meant what hw do you use to connect to the pump (for example: RFM69)
@jvemme I think that projects like androidaps, should be easier to operate than doing an installer for rpii. That said, I once had a project that asked people to only do the following:
``` git clone xxx
cd xxx
run_script.bat```
95% or even more could not do it. So I guess your task will be close to impossible. And remember that installing is only the first step. What will happen when will want to allow BT tethering?
Jon Cluck
@cluckj
Apr 22 14:09
@tzachi-dar gotta add dev at the end of that command so it's: curl -s https://raw.githubusercontent.com/openaps/oref0/dev/bin/openaps-install.sh > /tmp/openaps-install.sh && bash /tmp/openaps-install.sh dev
Jon Cluck
@cluckj
Apr 22 14:17
(I'm going to double-check that though :))
NSewar
@nsewar01
Apr 22 14:40
going backwards here......Edison was looping fine both on home wifi and BT tether. Now it willl not conect to wifi at all so I cant SSH via putty. However I can connect via serial. When I log in and type L to see the loop run, I get -bash: l: command not found and similarly when I enter wifi i get "-bash: wifi: command not found" . Any help would be appreciated.
Jon Cluck
@cluckj
Apr 22 14:46
@nsewar01 your install may be messed up, did you re-run oref0-setup to install the bluetooth stuff?
NSewar
@nsewar01
Apr 22 14:48
cd ~/src/oref0 && git checkout master && git pull && sudo npm install -g oref0
Already on 'master'
Your branch is up-to-date with 'origin/master'.
fatal: unable to connect to github.com:
github.com: Name or service not known
I tried to run install the new version using above command. But I keep getting the fatal: unable to connect to github message. I presume that this is because I am not connected via wifi?
Jon Cluck
@cluckj
Apr 22 14:50
yep
does rebooting get you reconnected to wifi?
Scott Leibrand
@scottleibrand
Apr 22 14:50
@marafie the setup-improvements branch was merged to dev and deleted. Checkout dev instead.
NSewar
@nsewar01
Apr 22 14:51
@cluckj .....No it doesnt....My home router does not show any connected device.
Scott Leibrand
@scottleibrand
Apr 22 14:52
Re-run bootstrap?
NSewar
@nsewar01
Apr 22 14:54
@scottleibrand Can I do this from my rig's root prompt?
Scott Leibrand
@scottleibrand
Apr 22 14:55
Yes, see the docs: it’s the block of code you paste in to get wifi set up initially.
Very first step after flashing.
And if that doesn’t work on your home wifi, try it on your phone hotspot.
NSewar
@nsewar01
Apr 22 15:01
@scottleibrand its running now....thanks!
NSewar
@nsewar01
Apr 22 15:13

W: Failed to fetch https://deb.nodesource.com/node_8.x/dists/jessie/main/source/Sources Could not resolve host: deb.nodesource.com

W: Failed to fetch https://deb.nodesource.com/node_8.x/dists/jessie/main/binary-i386/Packages Could not resolve host: deb.nodesource.com

E: Some index files failed to download. They have been ignored, or old ones used instead.
Adding edison to sudo users
The user edison' is already a member ofsudo'.
Adding edison to dialout users
The user edison' is already a member ofdialout'.
fatal: destination path 'oref0' already exists and is not an empty directory.
Already on 'master'
Your branch is up-to-date with 'origin/master'.
fatal: unable to connect to github.com:
github.com: Name or service not known

it looked promising to start with but ended badly!
tzachi-dar
@tzachi-dar
Apr 22 15:40
Xx as x
Scott Leibrand
@scottleibrand
Apr 22 17:12
@nsewar01 your wifi still isn't working. try another SSID?
fidoman
@efidoman
Apr 22 17:27
Getting this error in my oref0-online (network.log) file. ERROR: Failed to run oref0-bash-common-functions.sh. Is oref0 correctly installed? Is there something I can check?
Scott Leibrand
@scottleibrand
Apr 22 17:35
did you upgrade without re-running oref0-setup?
fidoman
@efidoman
Apr 22 17:37
I found the error. Somehow the first line and first character of the third line in the shell script was missing. I don't recall, but it is possible that I could have been looking in that shell script and accidentally made that edit. So, this one is solved and was easy and root cause was likely user error.
Martin Haeberli
@mhaeberli
Apr 22 17:54
can someone please send me a link to the external antenna for use with the edison / explorer board? I just got a new batch of explorers, but the antennas were missing. I tried google but no joy so far.
Dana Lewis
@danamlewis
Apr 22 17:57
@mhaeberli the search feature within the docs usually works better than googling, so always worth a try there. here's how: https://openaps.readthedocs.io/en/latest/docs/Understanding%20OpenAPS-Overview/communication-support-channels.html#the-docs-also-have-their-own-search-function
Martin Haeberli
@mhaeberli
Apr 22 18:15
thx @nsewar01 @danamlewis
NSewar
@nsewar01
Apr 22 18:16
when I reboot Edison rig I get the following "Failed to start remote_syslog.sevice"not sure what this means , is it the reason my wifi won't connect? If I want to start again from scratch, with a fresh jubilinux install on the Edison how do I wipe the existing operating system off ? or do I just overwrite? Help would be appreciated
Martin Haeberli
@mhaeberli
Apr 22 18:27
@nsewar01 if you can, the best way may be just to re-flash jubilinux
which erases everything
NSewar
@nsewar01
Apr 22 18:44
@mhaeberli thanks for your help
Martin Haeberli
@mhaeberli
Apr 22 18:47
:+1:
btw remote_syslog is also involved if/when you have set up papertrail; I don’t know whether you did that or not.
NSewar
@nsewar01
Apr 22 18:51
yes I had it working once!
marafie
@marafie
Apr 22 19:12
@tzachi-dar I am using explorer hat
marafie
@marafie
Apr 22 19:42
Starting oref0-pump-loop at Mon 22 Apr 22:28:05 +03 2019 with 26 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 grep: settings/model.json: No such file or directory
grep: settings/model.json: No such file or directory
fail. Retrying preflight
Preflight grep: settings/model.json: No such file or directory
grep: settings/model.json: No such file or directory
fail. Couldn't preflight
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!)
2019-04-22 22:30:30,342 ERROR port is not set in pump.ini. Please set port to your serial device, e.g. /dev/mmeowlink
Listening for 40s silence before mmtuning: .
i reinstalled Dev on rasp pi
and got this error which i got few days ago
Jon Cluck
@cluckj
Apr 22 19:53
@marafie can you run npm remove oref0 -g please? it looks like that's a master branch loop
or a really old version of dev
marafie
@marafie
Apr 22 19:54
@cluckj i use the dev, pulled it today
Jon Cluck
@cluckj
Apr 22 19:55
it's probably a leftover master branch loop then
marafie
@marafie
Apr 22 19:56
what should i do now ?
npm remove oref0 -g<===??
Jon Cluck
@cluckj
Apr 22 19:56
yes
straykatz
@straykatz
Apr 22 20:15
Martin - you will need WiFi antennas for those boards. They are 2.4 GHz, as opposed to the 915 MHz for pump communication. https://www.mouser.com/ProductDetail/molex/204281-0100/?qs=HXFqYaX1Q2zxrb0YqrfD%252bQ%3D%3D&countrycode=US&currencycode=USD these work for my Edisons without onboard antenna
Jason G
@jguyea
Apr 22 20:18
Should it be ok to run two rigs, one from master, one from dev and interface them to the same instance of nightscout(Heroku)? It seems my dev rig (built today) is causing the nightscout app to get into a bad state. (heroku/web.1: State changed from up to crashed)
Jon Cluck
@cluckj
Apr 22 20:21
@jguyea which hardware are you using?
Jason G
@jguyea
Apr 22 20:21
Using Pi0 + RFM69HCW radio for dev rig and P3b+ w/carelink usb for my master rig
my dev rig is probably in need of a fresh start as I've been bashing at it for a while now trying to get the radio working. I'll re-image it and see that helps... Jason
Jon Cluck
@cluckj
Apr 22 20:24
yes, if you use the latest dev, installation will be much easier
we just added a new installer that includes a better hardware setup picker
Jason G
@jguyea
Apr 22 20:26
The final fix was rearranging the pin connections to follow 'new' configuration. DIO0 => pi15 RESET=>pi22
I'll let ya know if a new install fixes things. Thanks Jon.
Jon Cluck
@cluckj
Apr 22 20:28
there's another pin that needs changing: https://github.com/openaps/docs/pull/1455/files
but if you've wired it up according to that diagram, option 3 (RFM69HCW) in the installer will work ez
Jason G
@jguyea
Apr 22 20:28
oh yes, I figured that one out previously from 0.0 to 0.1
Jon Cluck
@cluckj
Apr 22 20:29
:thumbsup:
Jon Cluck
@cluckj
Apr 22 20:37
@jguyea after you reinstall, make sure that ~/src/openaps-menu isn't there, and you'll have to clear out your devicestatus collection in your mlab database
Jason G
@jguyea
Apr 22 20:39
will do
LuminaryXion
@LuminaryXion
Apr 22 21:04

@cluckj Hi Jon, yeah reflashed and fresh installed. Tried the apt-get clean/update/install, but same error

Any ideas?

Jon Cluck
@cluckj
Apr 22 21:13
@LuminaryXion is this the error in python3.5 again?
LuminaryXion
@LuminaryXion
Apr 22 21:14

Hiii, more errors. :(

dpkg: error processing package python-all-dev (--configure):
dependency problems - leaving unconfigured
Processing triggers for libc-bin (2.24-11+deb9u4) ...
Errors were encountered while processing:
libssl1.1:armhf
python-cryptography
openssl
ca-certificates
python-pip
libpython2.7-stdlib:armhf
python2.7-minimal
libpython3.5-minimal:armhf
python-secretstorage
python-pip-whl
python-keyring
libpython3.5-stdlib:armhf
ntp
wpasupplicant
python2.7
python3.5-minimal
ntpdate
libpython2.7:armhf
libpython2.7-dev:armhf
python2.7-dev
python-all
python3.5
libpython-dev:armhf
libpython3.5:armhf
python-dev
libpython-all-dev:armhf
python-all-dev
E: Sub-process /usr/bin/dpkg returned an error code (1)

maybe?
Jon Cluck
@cluckj
Apr 22 21:15
yep, looks like the same one
Jon Cluck
@cluckj
Apr 22 21:25
I have no idea what could be wrong off the top of my head, but let's do some troubleshooting?
LuminaryXion
@LuminaryXion
Apr 22 21:46
OK! I'm on my way to work now, but if you send some ideas to try, I'll do it when I get home tonight. ^^
Jon Cluck
@cluckj
Apr 22 21:48
okay, I'll send you a list :)
LuminaryXion
@LuminaryXion
Apr 22 21:54
You're so awesome. Thank you for your help. :)
Jonathan Arms
@phinious_arms_twitter
Apr 22 23:57
@danamlewis I got my rig set-up. The only remaining item before I start looping is I need to get my infusion sets and reservoirs from Medtronic. Should arrive in 3 days. Thanks again for your help.