I’ve just checked the OmniAPS slack channel - the key comm protocol steps have been verified by multiple people, and there are already discussions about writing drivers - so, indeed excellent and exciting news! If you do not mind techie language and if you wish to monitor the progress, looks like the easiest way to sign up for this slack channel is to go to: https://omniapsslack.azurewebsites.net/ (but please resist the urge to ask “when” is this or that going to be done, or to make random suggestions - they know what they are doing). Later on, there will be many opportunities for everyone interested to contribute to testing, feedback, documentation, etc.
Edit: another good news: looks like existing RileyLink hardware (used with Loop) will work with the new drivers!
Thanks @Bradford! And @Michel for expanding on that. I’m so glad because I just spent some time Monday arguing that it would soon be possible with the OmniPod with @EricH’s idiot endo (maternity coverage guy sucks, and is fired from being our endo). So yay for it being true!!!
There has been significant progress on the Omnipod closed loop project but it is a big project.
The communications encryption is now understood and the group has been working on “sniffing” the messages between the POD and PDM and developing a command list based on these messages.
A big challenge is that the POD cannot talk to the PDM and another device. The original idea was that you could operate in parallel with a PDM and send a temp basal to the POD (like the Medtronic Pumps). They quickly discovered that if two devices send messages to the same pod, the pod will fault (go into scream mode). From a device security perspective, this is a good feature for the POD becasue it means someone else can’t take control of your POD without your PDM, but from a hacking perspective it means more work.
They have to basically recreate all the PDM functions in the device that hosts the APS software and that device will become the PDM. This is what is taking so long - to figure out all the commands and alarms etc.
Yesterday someone on the development group got a raspberry pi to bolus so there is some functionality there, but there is a lot more to go.
I would say there is definitely momentum on the project and lots of people are contributing. I would say at this point it is a matter of when and not if, but you never know.
There is a github site set-up for this work and the current status is on the github page.
It is so encouraging to think that we may be able to loop on a current pump, rather than having to rely on old fossilized Medtronic pumps that are years past their expiration date.
But I am also looking eagerly forward to the Dana pump Two options are better than one, either is better than older pumps, and older pumps are MUCH better than none!
Incremental progress with Omnipod. Looks like the OmniAPS team is slowly being able to integrate the comms into the RileyLink controller. Slow and steady. But steady indeed. Here is a snapshot of some POD info populated into RL. BTW if anyone has any expired PODs they no longer need, please head over to the the SLACK channel to donate if you are able. https://omniaps.slack.com/
Does anyone know if the existing Rileylink will still work as designed with Omnipod? @dm61 was mentioning that it may need a redesign to be as effective as possible with Omnipod.
- I’m not the on,y one that’s clueless about this!
Two options are better than one, either is better than older pumps, and older pumps are MUCH better than none!