I've noticed it every once and a while, it clears itself after it polls the pump history again.
Looks like what happens is that it thinks that the bolus attempt is not delivered to the pump (it gives a not delivered alarm) but in fact it actually was delivered.
I noticed it in RC6 and 5 but was going to see if fixed in 7 and haven't encountered it again yet.
Yeah, it should clear itself out when history is read again (every 5 minutes).
The first issue is a bit surprising as it is a new behavior I hadn't seen since the 2.6 RCs feels like a timing or loss of an ACK somewhere.
@andyrozman After testing Omnipod with AAPS I saw that it had a bolus progress bar. Is it possible to get the same for Medtronic( it just disappears when the bolus starts)? Or is it a reason why this is not implemented for Medtronic?
No, we can't. In MDT this is fire-and-forget action. You can place the bolus, but you can't stop it, so having progress bar there is useless. And bolus with MDT is veeeeery slow, so you could have blocking message there for few minutes. Only way to cancel running bolus with MDT is to stop the pump and then restart it.
@andyrozman but you do have a pump status of "bolusing" while it's going on, so you could poll that if desired
Only thing we do is set driver to busy for calculated amount of time, so that no other command is triggered during the bolus
Could a banner be displayed during this timer like "Bolus delivery timer XX:XX"? Not often that it is in question but could help with the odd troubleshooting moment.
To get omnipod to show up as a pump, I need to build the omnipod_eros branch (is there a better branch to use?), create a file called engineering_mode in logs (how can I verify that this worked?), Is there anything else?
@seattlebrighton Join the discord please. And yes you will need to build the correct branch, but which one is correct you will find out on discord... They can help you further...
Hi everyone, I'm just setting up my pump with APS and rileylink, but APS is saying my Rileylink has a bluetooth error....any ideas how to fix this?
@BrittanyEdel_twitter Hi! I usually do a pump battery replacement, then restart my phone, then restart the RL. You will have to wait about 5 min and go to the Medtronic tab and wait to see if the RL status is "spinning" and the pump status should begin to count down. If it does that then you're on your way. If that doesn't work, try going to the actions tab and "wake and tune up pump and RL" , if that doesn't work, try "resetting RL config". Make sure everything is close, I know my phone has issues when the phone is on one side, and pump and RL are on the other side of my body.
@BrittanyEdel_twitter I use RL, AAPS, Samsung Galaxy S9 and a Medtronic pump. Hopefully this helps!
There is one bug reported, that TBR that comes from History is not correct... Did anybody else see this?
Can somebody send an invitation to join the Discord server? The link above is expired. Thanks!
Only a question, is there a chance for an option, to see the battery life for OrangeLink into the Medtronic driver ?
Not at the moment, but we could add it... Please open feature request, and I will see what I can do... Shouldn't be that much work to add this...
For now, I have to delete the orangelink in AAPS and open nRF Connect, to see the stats for the orangelink. I hear that Omnipod Users can see, how empty the battery in the orange was.
Thanks, happy to have you. 😉
Feature Request done. 🙂
Just updated to new AAPS, and with intermittent connection w RL, I get a number of alarms a day. I've turned off volume, as its annoying and takes a full 15 seconds to unlock, get to app, ans ear alarm. Upon new update I get the alarm jingle, w no alert in AAPS so I can't clear. Suggestions other than a full phone restart?
This "forum" is closed... Please join the discord and ask question there.
Hello, I just received my Orange Link and I don't know how to connect it with my Android Apps. Im using Dexcom G5, Android apps and Medtronic 523. What should I do? thanks!
So I know this "forum" is closed, but I need little help with testing. We are adding new database and Nightscout functionality (in dev2 branch) and I changed whole driver from java to kotlin, so I would need some people willing to test everything with test setups... Can you please join discord, and come into #medtronic-testing group. This invite code should work: https://discord.gg/C9Ma7AcCcn