RileyLinkKit: High-level device interface#71
Conversation
|
Is this something that should eventually just be part of the RLBLE classes, or do you see it staying as a separate layer? |
|
Ah, guessing keep it separate as it depends on MinimedKit. I can see the utility it provides. LGTM |
|
Yeah. I think we instruct folks to use the I also plan to normalize both of our device utility interfaces into a single root view controller, and include them in
|
* Updates for improved commonality and to better match Loop + Message updates for Omnipod commonality and to match Loop + Improved BolusExtraCommand CustomDebugStringConvertible to match Loop + Rename StatusResponse insulin to insulinDelivered to match Loop + Make StatusResponse reservoirLevel non-optional to match Loop + Add additional StatusResponse initializers to match Loop + Rename DetailedStatus insulin to insulinDelivered to match Loop + Make DetailedStatus reservoirLevel non-optional to match Loop + Various UnfinalizedDose updates to better match Loop + Update updateFromStatusResponse() so insulin delivered never decreases + Derive StatusResponse from DetailedStatus when needed + Remove now uneeded updateFromDetailedStatusResponse() + Remove inconsistent termination of PodCommsError recovery strings + Rename VersionResponse pmVersion to firmwareVersion to match OmniBLE + Rename VersionResponse prVersion to iFirmwareVersion to match OmniBLE + Update PodState firmware ordering to match VersionResponse layout + Improved and cleaned up PodStateTests using more VersionResponse fields * Various backports and additional updates + Fix calls to store() when comms were unsuccessful + Account for non-zero cannulaInsertionUnitsExtra in initial updates + Updated StatusResponse CustomDebugStringConvertible extension + Remove useless completionBeep options for basal enabling session funcs + Updated bolus timing + deactivatePod() cleanup + Add additional delivery state checking for failed setBasalSchedule + Updates to handle possible basal state mismatches + Improvements for uncertainly resolution in updateDeliveryStatus() + Only display DetailedStatus faultEventCode for actual pod faults + New convenience utility funcs for reservoirLevel checking & display + Rename pumpManager readPodStatus() to getDetailedStatus() + Improved and more consistent commenting * Add back missing commands to end of MDT Pump Settings menu Delete unreferenced RileyLinkMinimedDeviceTableViewController.swift * Don't display a MySentry Pair command for non-MySentry pumps Co-authored-by: Joe Moran <mojo@moranfoundation.org> Co-authored-by: Marion Barker <marionbarker@earthlink.net>
…tore LOOP-4735 CGM Event Store
…tore LOOP-4735 CGM Event Store
This is an nearly-exact port of the interfaces I've been using in Naterade since August of last year. It provides a high-level interface for working with RileyLink devices and running pump commands.
Here's an example of where my
LoopDataManagerenacts its recommended temp basal