Roadmap for Omnipod development

There is currently no roadmap for Omnipod. Start of development hangs on prerequisites. I imagine we will be able to start at end of 2018 (or maybe before).

Prerequisites:

• A working Rileylink device driver. 80% of the protocol is now decoded, which is documented on openaps/Openomni. Pete Schwamb has got the first commands are working: Pairing, Temp Basal and Bolus and basic Status. It can be tested by flashing the rileylink with dev branch of subg_rfspy and ble113_rfspy (there are two chips). And then run the omnikit branch of rileylink_ios.
• development of Medtronic needs to be in phase where it can be integrated into AAPS (at least base framework needs to be split and prepared for use for two different target pumps and some of commands needs to be working). After this is done we will create new branch dev_omnipod and work can begin.

This are just approximate milestones here. Development might be done by me (Andy) or not. I will prepare base stuff (M1) so that somebody else can start, since I am currently working on Medtronic implementation.

Milestones: Milestone 1: Create branch (from Medtronic one) and prepare base files for Omnipod implementation (barebones so that someone can start implementation). (1.8.2018)

Milestone 2: Basic Omnipod framework, Init Pod and Bolus Command (unknown time)

Milestone 3: TBR command, TBR cancel, ?? Status Commands (unknown time)

Milestone 4: Set Profile, Get Profile, ?? History (unknown time)

Milestone 5: Start integration into AAPS, with Status and InitPod commands (look at MDT integration code) (unknown time)

Milestone 6: Integration AAPS: Profiles, Bolus, TBR (unknown time)

Milestone 7: ??? Finalize integration