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

4th
Feb 2018
Scott Leibrand
@scottleibrand
Feb 04 2018 00:00
It’s Termius. ;-) You can use it to ssh to the rig just like you would from your computer.
Bob Duerr
@Duer0049
Feb 04 2018 00:10
I don't know the ip address of the rig to be able to use ssh.
Scott Leibrand
@scottleibrand
Feb 04 2018 00:23
There is a page in the docs about how to find that out.
phoenixflame611
@phoenixflame611
Feb 04 2018 01:34
So heres a question now: loop is running, but i do not have a "myopenaps" folder. this is all i can see really
image.png
katie disimone
@Kdisimone
Feb 04 2018 04:33
@phoenixflame611 try cd && ls. You aren’t in your root directory currently, so you need to get there first
phoenixflame611
@phoenixflame611
Feb 04 2018 05:10
i was in root on the first line before
image.png
phoenixflame611
@phoenixflame611
Feb 04 2018 05:17
found it....the folder is in "~/src/oref0/bin" is there an easy way of moving things out of there or do i have to start all over again?
Scott Leibrand
@scottleibrand
Feb 04 2018 07:09
Probably easier to re-run oref0-runagain and then delete the one in src/oref0/bin once you confirm the new one is in the right place. Check the contents of the oref0-runagain before you run it.
jquitos
@jquitos
Feb 04 2018 15:23

So... I had this issue previously on both rigs.. and it's happened again and I've had to reflash both to be able to get it again. The BT is able to connect and I am able to connect via BT PAN however the rigs never have an IP address... this is what I always end of getting :

root@Baymax:~# ifconfig bnep0
bnep0 Link encap:Ethernet HWaddr 58:a8:39:01:0e:cf
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:3 errors:0 dropped:0 overruns:0 frame:0
TX packets:3 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:283 (283.0 B) TX bytes:96 (96.0 B)

I restarted BT, un-paired, re-paired and all that jazz... but it never comes back. So he is only able to loop at home... any help for this other than reflash again?

Lorenzo Sandini
@lsandini
Feb 04 2018 16:35
@Duer0049 you need to find out what is the IP address of your rig, using a port scanner. Then connect to your rig using your phone. Everything is in the docs... https://openaps.readthedocs.io/en/latest/docs/Customize-Iterate/useful-mobile-apps.html#
Samuchco
@Samuchco
Feb 04 2018 17:28

Feb 04 12:23:03 loop2 pump-loop.log: Listening for 40s silence before mmtuning: .......................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................
``` 04 12:23:03 loop2 pump-loop.log: Starting oref0-pump-loop at Sun Feb 4 12:23:03 EST 2018 with 14 second wait_for_silence:
Feb 04 12:23:03 loop2 pump-loop.log: Waiting up to 4 minutes for new BG: ls: cannot access /tmp/pump_loop_completed: No such file or directory
Feb 04 12:23:39 loop2 pump-loop.log: mmeowlink.exceptions.CommsException: Could not get subg_rfspy state or version. Have you got the right port/device and radio_type?
Feb 04 12:23:39 loop2 pump-loop.log: Radio check failed. mmeowlink.exceptions.CommsException: Could not get subg_rfspy state or version. Have you got the right port/device and radio_type?

pump-loop.log
Search
All Systems

Rig stopped connecting with pump. Any idea how to fix the exception?
Eric
@ecc1
Feb 04 2018 18:09

@jquitos what does you system log (/var/log/syslog) show after the connection via BT PAN? It looks like the rig is not making a DHCP request for an IP address. The oref0-online.sh script does this:

sudo bt-pan client $MAC && sudo dhclient bnep0

but in my experience that might be too short of an interval. You could try putting a small "sleep" in between, or add the lines

allow-hotplug bnep0
iface bnep0 inet dhcp

to your /etc/network/interfaces file

peterfulvi
@peterfulvi
Feb 04 2018 19:12
This keeps showing up in my loop 'SMB disabled (no enableSMB preferences active)'. I have to my knowledge all the SMB features enabled. ''' "max_iob": 12, "max_daily_safety_multiplier": 3,
"current_basal_safety_multiplier": 4,
"autosens_max": 1.2, "autosens_min": 0.7, "rewind_resets_autosens": true, "adv_target_adjustments": false, "exercise_mode": false, "wide_bg_target_range": false, "sensitivity_raises_target": true,
"unsuspend_if_no_temp": false,
"enableSMB_with_COB": true,
"enableSMB_with_temptarget": true, "enableUAM": true,
"curve": "rapid-acting",
"offline_hotspot": false
}'''
Sławomir Malinowski
@sarunia
Feb 04 2018 19:17
Hello everyone, we are creating a new pilot project with a display for Medtronic Paradigm pumps based on the original MMT-503EU remote control. We managed to decode the method of sending the pilot's serial number in a single data packet. Unfortunately, the pilot transmits with a variable code and we do not know how 3 bytes of data are changed in each packet - marked in red. Does anyone have knowledge about this? Please see photos. We also managed to separate the serial number of the remote control from the code. The data is encoded using an encoding called 4b6b.
Dana Lewis
@danamlewis
Feb 04 2018 19:19
@peterfulvi there's more SMB preferences if you want to add them - right now SMB will only be triggered for you with a temp target or carbs
Check the preferences page for the list of all available preferences
Eric
@ecc1
Feb 04 2018 19:24

@sarunia Here's the format of the packets that the RF remote sends:

//   device type (0xA6)
//   3 bytes of RF remote ID
//   command code
//   sequence number
//   CRC-8

Then the packets are 4B/6B encoded like the CareLink comms. I had code in github.com/ecc1/medtronic to simulate a remote until recently; if you go back a few commits you can still find it.

Sławomir Malinowski
@sarunia
Feb 04 2018 19:27
Eric@ecc1 please look:
Eric
@ecc1
Feb 04 2018 19:29
what didn't you understand about the code I pointed you to?
In your picture, 81 = command ("S" button"), A6 = sequence #, D8 = CRC-8 of the packet
Sławomir Malinowski
@sarunia
Feb 04 2018 19:45
@ecc1 We made the LUT tables based on oscillograms at the transmitter input, only now I found your repository and try to use it. We use the STM8 microcontroller in our project. https://www.imageupload.co.uk/image/Ekij
Sorry for polish comments in C
Eric
@ecc1
Feb 04 2018 19:47
well, it's in Go, which won't work directly on most MCUs. but it should be easy to translate to C. If you prefer Python, my code was based by @bewest 's original decocare project, now at https://github.com/openaps/decocare
nie ma problemu :-)
Wow, that's impressive reverse-engineering. There are some other pump comms that still need to be decoded, where your skills would probably help!
Sławomir Malinowski
@sarunia
Feb 04 2018 19:49
Thank You Eric, we will try in the next days.
peterfulvi
@peterfulvi
Feb 04 2018 20:15
enableSMB_always,enableSMB_after_carbs,allowSMB_with_high_temptarget,maxSMBBasalMinutes
Are those the preferences. I didn't see them in mine as you see above. Do I just add them with the default values? I heard that I can just do the math in bolus wizard and just do a portion of the bolus with the easy Bolus and the SMB would do the rest. That is my approach once I iron this issue out. @danamlewis
Samuchco
@Samuchco
Feb 04 2018 20:29
anybody has any idea what this is and how to solve this problem
Feb 04 14:11:03 loop2 pump-loop.log:  Starting oref0-pump-loop at Sun Feb  4 14:11:03 EST 2018 with 28 second wait_for_silence:
Feb 04 14:11:03 loop2 pump-loop.log:  Waiting up to 4 minutes for new BG: ls: cannot access /tmp/pump_loop_completed: No such file or directory
Feb 04 14:11:32 loop2 pump-loop.log:  mmeowlink.exceptions.CommsException: Could not get subg_rfspy state or version. Have you got the right port/device and radio_type?
Feb 04 14:11:35 loop2 pump-loop.log:  Radio check failed. mmeowlink.exceptions.CommsException: Could not get subg_rfspy state or version. Have you got the right port/device and radio_type?
Feb 04 14:35:56 localhost remote_syslog:  2018-02-04 19:35:55 INFO  remote_syslog.go:202 Forwarding file: /var/log/openaps/pump-loop.log
Feb 04 14:36:03 loop2 pump-loop.log:  Starting oref0-pump-loop at Sun Feb  4 14:36:02 EST 2018 with 6 second wait_for_silence:
Feb 04 14:36:03 loop2 pump-loop.log:  Waiting up to 4 minutes for new BG: ls: cannot access /tmp/pump_loop_completed: No such file or directory
Feb 04 14:36:34 loop2 pump-loop.log:  mmeowlink.exceptions.CommsException: Could not get subg_rfspy state or version. Have you got the right port/device and radio_type?
Feb 04 14:36:37 loop2 pump-loop.log:  Radio check failed. mmeowlink.exceptions.CommsException: Could not get subg_rfspy state or version. Have you got the right port/device and radio_type?
Feb 04 15:07:08 loop2 pump-loop.log:  Listening for 40s silence before mmtuning:
Samuchco
@Samuchco
Feb 04 2018 20:43
@Kdisimone thanks Katie, was reading this.