Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • Jan 31 2019 15:51
    xen0n starred openaps/oref0
  • Jan 31 2019 15:12
    cclauss opened #1191
  • Jan 31 2019 15:09
    cclauss edited #1190
  • Jan 31 2019 15:08
    cclauss edited #1189
  • Jan 31 2019 15:07
    cclauss edited #1190
  • Jan 31 2019 15:07
    cclauss opened #1190
  • Jan 31 2019 15:00
    cclauss synchronize #1189
  • Jan 31 2019 14:52
    cclauss opened #1189
  • Jan 31 2019 14:10
  • Jan 31 2019 14:06
    Owaisaaa starred openaps/docs
  • Jan 31 2019 12:20
    cclauss synchronize #22
  • Jan 31 2019 12:16
    cclauss opened #22
  • Jan 31 2019 12:11
    cclauss edited #21
  • Jan 31 2019 12:09
    cclauss opened #21
  • Jan 31 2019 11:31
    tuzoenduro commented #1406
  • Jan 31 2019 11:25
    cclauss opened #140
  • Jan 30 2019 05:53
  • Jan 29 2019 16:03
    tzachi-dar commented #1406
  • Jan 29 2019 14:46
    rostag starred openaps/oref0
  • Jan 27 2019 22:06
    PieterGit synchronize #1176
garetis
@garetis
I'm trying to get my rig set up for offline looping. I'm using RPi3+G6+Medtronic for now. I assumed the easiest option would be to plug a G6 receiver into the RPi via USB micro-to-A. I used the G6 command when configuring the setup for offline. Could someone point me to some of the old bash commands for pulling the data manually, or troubleshooting guides that I could use to try to get it sorted out? Or is this not recommended and I should be looking to Logger/Lookout instead?
jaybaron1
@jaybaron1
If you use lookout/logger I would run cgm-start -t 8M2NHT -c 9211. When youre ready to stop -- cgm-stop
Replace codes as needed
Why plug in a receiver?
I used RPi0
Not sure how different they are
Foxy7
@Foxy7
@danamlewis yes I'm using the automated tool.
Step
2b
2b. REPEAT USERS: Go here: https://dataxfer-ns-oh.herokuapp.com
It's worked fine in the past. Is there another way to transfer the data?
Is there a link to the code behind the transfer tool?
garetis
@garetis
@jaybaron1 I was using the RP0 but it was having issues. I think it would stop working randomly? I don't recall but it was frustrating. The RP3 seems much more stable. I figure plugging in the receiver is quick and easy without having to login, and if I'm carrying around the RPi3 and usually a big battery to keep it charged there's plenty of room to add on the receiver. When you say replace codes, the "8M2NHT" is the transmitter code for the dexcom?
Dave Acklam
@dcacklam

@garetis The Pi0 does not have the processing power to work with the HAT reliably. It tends to have issues with timeouts.
I had one working well enough with a plain radio board ('Slice of Radio' device), but trying to make it work with the hat resulted in something rather unstable...

IMHO the best Pi for a rig - if we had a radio/LCD-board designed for it - would be the CM4 or CM3

@garetis
Also, the easiest way to do offline looping with the G6, is to use xdrip-js & connect directly from your rig to the transmitter via bluetooth.
@chrisdex Contact ebay-seller 'all-of-cpu'.
He had a bunch of Medtronic 722s for sale at one time, and when I bought 2 (one as a backup) he offered to sell me the entire stock...
I didn't have the money for that, so I declined...
jaybaron1
@jaybaron1
@garetis yes that's the code
Dave Acklam
@dcacklam
@jaybaron1
The Pi 0 has 1/4 the CPU cores of the Pi3 and they are less-capable cores as well.
Eric
@ecc1
@dcacklam there are some small carrier boards for CM4 with HAT-compatible headers, so one could use the Adafruit radio hat with it
Dana Lewis
@danamlewis

@Foxy7 you could manually download your files from Ns command line and then upload to OH, but that’s a bit of work if you’ve not done it before. There’s a NS repo for the code behind the uploader tool if you want to check it out.

Can you file an issue in that repo and I can get someone to help take a look? Might be the heroku side of it (which I can’t remember if I have access to but won’t be able to check until I’m back on decent Wi-Fi mid week)

Dave Acklam
@dcacklam
@ecc1
The hard part with the premade Pi4 boards is finding one with LiPo charge/power support.
I am becoming a bit convinced that - absent a new 4CM or 3CM based Explorer Hat - the best pi is the Pi3A (which is the same width as a Zero, the same CPU as the 'full size' Pi3, but has a greater height because it has the camera headers, HDMI and USB-A)
Dave Acklam
@dcacklam
Issue with oref0-setup:
Trying to build the go binaries is failing:
/root/go/src/github.com/ecc1/medtronic/cmd/cgmupdate/main.go:55:2: undefined: nightscout.SetNoUpload
/root/go/src/github.com/ecc1/medtronic/cmd/cgmupdate/main.go:56:2: undefined: nightscout.SetVerbose
/root/go/src/github.com/ecc1/medtronic/cmd/cgmupdate/main.go:136:15: undefined: nightscout.Gaps
/root/go/src/github.com/ecc1/medtronic/cmd/cgmupdate/main.go:152:10: undefined: nightscout.Upload
/root/go/src/github.com/ecc1/medtronic/cmd/cgmupdate/main.go:189:41: cannot use *jsonFile (type string) as type io.Reader in argument to nightscout.ReadEntries:
string does not implement io.Reader (missing Read method)
# github.com/ecc1/medtronic/cmd/bgproxy
/root/go/src/github.com/ecc1/medtronic/cmd/bgproxy/main.go:40:41: cannot use *jsonFile (type string) as type io.Reader in argument to nightscout.ReadEntries:
string does not implement io.Reader (missing Read method)
Couldn't go get medtronic
root@piaps:~/myopenaps# go version
go version go1.12.5 linux/arm

Eric
@ecc1
@dcacklam I can't reproduce that with go 1.15 from bullseye:
/tmp $ git clone https://github.com/ecc1/medtronic
Cloning into 'medtronic'...
remote: Enumerating objects: 3007, done.
...
/tmp $ cd medtronic/cmd/cgmupdate/
/tmp/medtronic/cmd/cgmupdate $ go build -v
go: downloading github.com/ecc1/nightscout v0.0.0-20181103224750-3f979d458431
github.com/ecc1/medtronic/packet
github.com/ecc1/gpio
github.com/ecc1/nightscout
github.com/ecc1/spi
github.com/ecc1/cc111x
github.com/ecc1/radio
github.com/ecc1/medtronic
github.com/ecc1/medtronic/cmd/cgmupdate
/tmp/medtronic/cmd/cgmupdate $ go version
go version go1.15.9 linux/amd64
Looks like your build is using an older version of code from the nightscout repo. I'd try removing your local copy of the Go source and retrying
Dave Acklam
@dcacklam
@ecc1
I am using the 'go' source that is installed by the oref0-install script.
Dave Acklam
@dcacklam
@ecc1
From oref0-setup.sh
    golangversion=1.12.5
    if go version | grep go${golangversion}.; then
        echo Go already installed
    else
        echo "Removing possible old go install..."
        rm -rf /usr/local/go/*
        echo "Installing Golang..."
        if uname -m | grep armv; then
            cd /tmp && wget -c https://storage.googleapis.com/golang/go${golangversion}.linux-armv6l.tar.gz && tar -C /usr/local -xzvf /tmp/go${golangversion}.linux-armv6l.tar.gz
        elif uname -m | grep i686; then
            cd /tmp && wget -c https://dl.google.com/go/go${golangversion}.linux-386.tar.gz && tar -C /usr/local -xzvf /tmp/go${golangversion}.linux-386.tar.gz
        fi
    fi
If you try running the oref0-setup on a clean SD card (pi) or Edison flash, you will get the above crash
Dave Acklam
@dcacklam
I updated the 'golangversion' to 1.15.13, and ran oref0-setup again.

go version go1.15.13 linux/arm
Go already installed
GOROOT=/usr/local/go
export GOROOT
PATH=$PATH:/usr/local/go/bin:$GOROOT/bin:$GOPATH/bin
GOPATH=$HOME/go
export GOPATH
PATH=$PATH:/usr/local/go/bin:$GOROOT/bin:$GOPATH/bin
Making sure SPI is enabled...
github.com/ecc1/medtronic (download)
github.com/ecc1/cc111x (download)
github.com/ecc1/gpio (download)
get "golang.org/x/sys/unix": found meta tag get.metaImport{Prefix:"golang.org/x/sys", VCS:"git", RepoRoot:"https://go.googlesource.com/sys"} at //golang.org/x/sys/unix?go-get=1
get "golang.org/x/sys/unix": verifying non-authoritative meta tag
golang.org/x/sys (download)
get "golang.org/x/sys/internal/unsafeheader": found meta tag get.metaImport{Prefix:"golang.org/x/sys", VCS:"git", RepoRoot:"https://go.googlesource.com/sys"} at //golang.org/x/sys/internal/unsafeheader?go-get=1
get "golang.org/x/sys/internal/unsafeheader": verifying non-authoritative meta tag
github.com/ecc1/spi (download)
github.com/ecc1/nightscout (download)
github.com/ecc1/radio (download)
github.com/ecc1/papertrail (download)
github.com/ecc1/medtronic/cmd/bgproxy
github.com/ecc1/medtronic/cmd/cgmupdate
# github.com/ecc1/medtronic/cmd/cgmupdate
/root/go/src/github.com/ecc1/medtronic/cmd/cgmupdate/main.go:55:2: undefined: nightscout.SetNoUpload
/root/go/src/github.com/ecc1/medtronic/cmd/cgmupdate/main.go:56:2: undefined: nightscout.SetVerbose
/root/go/src/github.com/ecc1/medtronic/cmd/cgmupdate/main.go:136:15: undefined: nightscout.Gaps
/root/go/src/github.com/ecc1/medtronic/cmd/cgmupdate/main.go:152:10: undefined: nightscout.Upload
/root/go/src/github.com/ecc1/medtronic/cmd/cgmupdate/main.go:189:41: cannot use *jsonFile (type string) as type io.Reader in argument to nightscout.ReadEntries:
string does not implement io.Reader (missing Read method)
# github.com/ecc1/medtronic/cmd/bgproxy
/root/go/src/github.com/ecc1/medtronic/cmd/bgproxy/main.go:40:41: cannot use *jsonFile (type string) as type io.Reader in argument to nightscout.ReadEntries:
string does not implement io.Reader (missing Read method)
Couldn't go get medtronic
root@piaps:~/myopenaps# go version
go version go1.15.13 linux/arm
Is it possible that the setup script is pulling the wrong go source from github?
Dave Acklam
@dcacklam

When I do a 'git clone' and a 'go build -v' I get the same thing you do...

But when I run the setup script it crashes and burns

The setup script is doing a ' go get -u -v -tags "$radiotags" github.com/ecc1/medtronic/... '
wherein radiotags = cc111x in my case
Eric
@ecc1
not sure the setup script is doing the right thing. it should clone and then build, not do a "go get" if there's no local source yet
Eric
@ecc1
sorry, my mistake. setup is pulling the master branch of the medtronic repo, which had lagged behind dev. I've updated them both now
Dave Acklam
@dcacklam
@ecc1
That fixes it.
tzachi-dar
@tzachi-dar
Should rpi 4 works as a rig just like rpi 3?
tynbendad
@tynbendad
about the radio hack that attempts to guess your pump's serial number - has anyone tried to detect a hack in progress (e.g., from an explorer or explorer hat rig)?
is it feasible?
Eric
@ecc1
@tynbendad not sure what hack you mean, but it's trivial to snoop on pump comms in progress and extract the serial number, since it's not encrypted in any way. Impossible to detect, since it's receive-only
tynbendad
@tynbendad
Oh, ok that's worse than i thought. Thought they had to try every serial number, but maybe that's just for pumps that aren't using comms.
jaybaron1
@jaybaron1
Thanks for sharing.
Dave Acklam
@dcacklam
@tzachi-dar rpi4 works as a rig but the battery circuitry on the explorer hat is too weak to power it.
@tzachi-dar So only really good for a desktop rig.
Use a pi3A+ or pizero for portable
tzachi-dar
@tzachi-dar
Thanks @dcacklam is using pi3A+ with a battery a reasonable thing to do? Seems like it's power usage is relatively high.
Dave Acklam
@dcacklam
@tzachi-dar just use a 6000mah battery