These are chat archives for nightscout/intend-to-bolus
# src/oref0/bin/oref0-setup.sh --dir=/home/edison/xxx --serial=xxx --cgm=G4 --ns-host=http://xxx.herokuapp.com --api-secret=xxx --tty=/dev/spidev5.1 --enable=' autosens meal ' --radio_locale='US' --max_iob=4 --btmac="xx:xx:xx:xx:xx:xx"
@/all Explorer Board Users - Q, this here again with
rootcredentials :question: or login with
.....and does this hex file match to WW?
WWparameter and see what's the result...
nightscout ns $NIGHTSCOUT_HOST $API_SECRET latest-treatment-timeand tell me what it returns? Does it return json, or
I have the opposite feeling after making a few changes. But I need to wait a few days before I could say for sure. I am running oref0, however (as of a couple of weeks ago, but with some mods). It seems that my instabilities came from two sides - the RF hang-ups and the network switching.
serial_rf_spy.py mod I told you about there has not been a single hang-up of the RF yet. Of course, it's been only 40 hours or so. I also modded the oref0-online.sh script to make it not to attempt the network switching every single time it fails to obtain the IP address from the icanhazip.com, and also to not restart the bluetoothd unless it is not running.
rm -f git*. I've also had a few times where I've been away from a computer and my rig has stopped responding. I couldn't SSH onto it from my phone, so I rebooted it and that got it back up and running. I suspect it might've been the same git propagation issue at those times too.
Guess I'll have to use my cc-debugger when I get home
edison@ediscout2:~/src/ccprog$ sudo ./ccprog -p 19,7,36 erase [sudo] password for edison: Using pins: DC=19, DD=7, RESET=36 Erasing chip. could not update FWT! Chip erase failed.
ifconfig wlan0and if it's on the network it'll give you the IP address. You can use that address from putty instead of the
ifconfig wlan0into the Pi, not into putty
It'll return something like:
root@openaps2:~# ifconfig wlan0 wlan0 Link encap:Ethernet HWaddr 90:b6:86:11:ad:96 inet addr:192.168.1.191 Bcast:192.168.1.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:405023 errors:0 dropped:0 overruns:0 frame:0 TX packets:199562 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:293299755 (279.7 MiB) TX bytes:20692030 (19.7 MiB)
The address you need is whatever is in the spot of "192.168.1.191" on mine.
ifconfig wlan0output should looks something like:
edison@edison-rl ~ $ ifconfig wlan0 wlan0 Link encap:Ethernet HWaddr 78:4b:87:ab:23:54 inet addr:192.168.29.29 Bcast:192.168.29.255 Mask:255.255.255.0 inet6 addr: 2601:602:9801:31f9:7a4b:dead:beef:cafe/64 Scope:Global inet6 addr: fe80::7a4b:dead:beef:cafe/64 Scope:Link
inet6 addr: fe80::line?
cp settings/profile.json settings/pumpprofile.jsonto start with. What fields of the profile.json are mandatory for the (manual) autotune process?
edison@miniaps:~/APS$ openaps report invoke settings/profile.json get-profile://text/shell/settings/profile.json /usr/local/bin/oref0-get-profile pump_settings.json bg_targets.json insulin_sensitivities.json basal_profile.json [preferences.json] [<carb_ratios.json>] [<temptargets.json>] [--model model.json] Options: --model, -m Pump model response [default: false] --help Show help [boolean] --exportDefaults Show default preference values [default: false] --updatePreferences Check for any keys missing from current prefs and add from defaults [default: false] Unknown argument: autotune reporting settings/profile.json edison@miniaps:~/APS$
npm run global-installfrom ~/src/oref0 to fully install the version of oref0 that supports autotune