Test instructions Medtronic

Info about project

Since I started getting mails and I don't like to repeat myself, I decided to post some QAs here.

Where are the binaries?

AAPS (Android APS) is Do-It-Yourself project, which means you have to build binaries yourself.

Can I use AAPS Medtronic plugin on live person?

NO. We are still in development, and while we are almost finished, we still have some hickups, that make plugin unreliable.

When will be Medtronic plugin released?

There is no definite date yet, but my hopes are that I will be able to merge this repository, to main repository and it will be released with next release sometime after May 2019. If you want more detailed info, please follow us in gitter room or you can see what we still have left over in Project overview (https://github.com/andyrozman/RileyLinkAAPS/projects/1) and some of info is also here in section "What still needs to be done"

Where is "our" gitter room

Like I said most of communication happens in our gitter room which can be reached on following link: https://gitter.im/RileyLinkAAPS/Lobby

How to configure Pump and RileyLink to start

If you continue on this page, there should be all instructions needed. I will create separate instructions page soon, because we will need it for when the plugin is released.

More QA

If you think I forgot any of QA, please send me the mail and I will update it.

Requirement for testing

• RileyLink device with correct firmware (for 900 Mhz) - This is default shipped firmware, so it should work Out-Of-The-Box
• Compatible pump:
  • 512/712
  • 515/715
  • 522/722
  • 523/723 (firmware 2.4A or lower)
  • 554/754 EU (firmware 2.6A or lower)
  • 554/754 CA (firmware 2.7A or lower)

How to prepare your pump and software

• Set Max Basal on your Pump to your "max basal entry in your STD profile" * 4 (if you want to have 400% TBR as max). This number must be under 35 (as you can see in pump). Set the same number in Medtronic configuration.
• Set Max Bolus from your Pump to Medtronic configuration (max is 25).
• Set profile to STD. This will be the only profile we will use.
• Set TBR type to Absolute (not Percent)
• Disable Auto-rotate on your phone
• In AAPS go to Maintenance and select Log settings, disable option "Autosens" (this options produces a lot of entries, which creates big log files, and data there is not important for MDT testing)
• Enable engineering mode on AAPS (This will make Medtronic option visible in Pumps) Here are instructions.
• If you are new tester with medtronic, please download latest "release". After you have tested for a while, you can upgrade to my development branch, but be prepared that not everything will work.
• Do not pair RileyLink with your Phone. If you paired your RL, then AAPS won't be able to find it in configuration.
• It might happen that Wizard won't work for you. If this is the case select Virtual Pump and finish the wizard, and when you are out of wizard, go to Config Builder, select Medtronic and configure
• Enable remote mode on Pump (Utilities -> Remote Options, Select Yes, and on next screen do Add ID and add dummy id (111111 or something). You need to at least one ID on that Remote IDs list.
• Serial number is located on back side of your pump (SN). You need to add only numbers from that SN (6 digits).
• When pump shows Low Battery, all the communication will stop.

Important note

• You must not use CGMS with pump you use for AAPS

History of Test releases (and main branch)

I regularly release new tags, so that people can start testing, last release was 0.4 and it contained support for most of functionalties, except reading of History data (which in turn returns status of the pump)

0.1 - Initial integration What is working:

• Bolus,
• TBR
• Getting statuses: Remaining Insulin, Remaining power, Pump Time
• Checking settings on pump and compare with AAPS configuration

0.2 - Support for RileyLink v2

0.3

• fixing a lot of problems from Fabric server (I can sort-of see what exception happen if you don't change app/build.gradle SO PLEASE DONT CHANGE IT).
• connection checking and try to make plugin more robust to sudden connection changes
• Tunning changes
• fixed configuration...
• Now most what was done was in stability area. I expected we will still getting few exception and I will try to fix them ASAP. I will create "releases" more often now (I hope to do it every 1-2 weeks), so that you guys can test with newest options. We still don't get status from pump (no reading of history yet, but I am almost done with that so I hope to get it done in time for next "release", also we are missing setting of basal profile, which is also being worked on.

0.4

• about 10 fixes, I noticed on Fabric server (its server that logs all exceptions and problems) for problems you seem to be having
• added additional logging for 2 problems that seem to happen and are really unexplainable
• upgraded to RC14
• added command SetBasalProfile
• I discovered two weird problems and I would ask any tester, just to make sure that they don't happen on his phone... After testing, please look for "=============" in your log files, which mark both this problems.

0.5 What changes are here:

• downloading of pump history (every 5 minutes)
• changes in handling of errors during communication (if any commands fail, it is retried (2 retries, 3 tries all together)
• switching frequency from US to WW for first connection
• refactoring on encoding
• refactoring pump handling (no more empty warnings when action was in error, logging refactored, working with refreshes (so that we don't do too many calls))
• improvement in stability

0.6

• bolus finalized: added delay before bolus is delivered (configurable 5, 10, 15s) and if cancel is issued, after delay, and bolus was already sent to pump, message is displayed saying that you need to manually stop the pump to cancel bolus
• BLE Scanner refactored and finished (removed un-needed code)
• fixed 5 most common Crashalytics errors found (errors happened while you were testing), should improve stability
• fixed Basal Profile problem (I hope)
• started on decoding DailyTotals History entries (one of few not yet decoded and needed)

0.7

• merge of /dev branch (13.2.2019)
• finished decoding dailyTotals
• fixed some Crashalytics errors
• fixed problem with settings on 554 (reporting problem with max bolus)
• Pump History page (from Medtronic tab) - Showing history for last 36 hours
• fixed set/get of BasalProfiles

0.8

• process Treatments/Boluses and store them in Db
• determining status from history
• prevent multiple refreshes in queue
• set driver to busy when wake up/tuning is made
• when bolus is delivering pump can't be used (we set driver to busy when bolus is delivering, so that no new commands are processed)
• fixed over 30 crashalytic problems
• merge to latest 2.2.3-dev (7.4.2019)

0.9

• fixes with process of Treatment (Bolus) records from Pump
• processing of TDD entries
• processing TBR history records
• lot of Crashalytic error fixed
• merged to latest 2.3-dev (3.5.2019)

0.10

• Clean up code
• Prepare documentation
• Basal Profile comparison by correct rounding
• Implementation of Superbolus
• Implementation of Disconnect Pump
• Prevent RileyLink Stats implementation to crash if initalization is not finished
• Reset RL Configuration
• Pump Config Tweaks
• FIx calibration of RL
• Calculate battery status (by selecting correct Battery type)
• USe RileyLink internal encoding (4b6b Hardware encoiding)
• Bolus Wizard entry is considered
• and many other changes

0.11

• Determine "Stop delivery" from history (#109)
• Track TZ and Time changes in pump driver (#140)
• Calculate Battery status - reopened (#126)
• Set/Check pump time (#139)
• When TBRs are processed is done in wrong order (#122)
• Change Bolus synchronization to work with SetTime functionality (#141)
• Change TBR synchronization to work with SetTime functionality (#142)
• Change "Suspend delivery" synchronization to work with SetTime functionality (#143)
• If Basal profile reading fails first time its never retries (#149)
• Battery not updated every hours (#146)
• Pump history should have working filter (#148)
• Prevent time updates if difference is more than 24 hours (#147)
• BolusWizard 512 problems (#150)
• Bolus records are changes if next Bolus is too soon (#151)
• Bolus Records are sometimes duplicated (#154)
• Cleanup code

What still needs to be done: (Detailed list can be found here)

• (1.1) Medtronic tab, for executing commands with response (similar to Loop) (0% DONE)

Most of big stuff is done, what is left are just small things... so please start testing and if you find a problem, please open ticket on RileyLinkAAPS (please check if someone has opened the same bug)... If you notice that AAPS is taking longer to respond (when communicating with pump), please let me know (I might need to change communication again, if pump communication is stoping normal functioning of AAPS).

On medtronic_andy work is continuing... While parsing should work correctly, there might be sometimes problems with 512 and 515, if you notice something going wrong, please let me know.