-
Notifications
You must be signed in to change notification settings - Fork 26
Release Notes
Barış Kurtlutepe edited this page Mar 16, 2019
·
22 revisions
March 16th, 2019
--incomplete list--
Fixes:
- An edge case where a bolus under 0.50U could be transmitted twice, if radio reception follows a pattern of: Barely possible for 30 seconds - complete breakdown for 60 seconds at the right moment of the message sequence, and barely working again for the next 30 seconds. Omnipy will now recognize the failed attempt and recover the pod from crashing if it becomes reachable within 4 minutes.
New features & improvements
- Intermittent BLE disconnections (due to reception or RL battery issues) now will be recovered automatically during message transmission to prevent total communication failures.
- Adaptive power amplification during message transmission for faster and more reliable operation when the RL and pod are too close, or are too far.
- Better Android APS stability and performance via complete rework of how AAPS communicates with the omnipy API.
- Automatic IP detection now working and AAPS will detect disconnections automatically.
- Connection and disconnection from omnipy now indicated in the UI via standard AAPS interface style.
- "Omnipod/PDM" tab now shows a brief status of connection to omnipy and some information on the active pod.
Known issues
Links
March 3rd, 2019
Links:
omnipy v0.1 (incorrectly named v0.1)
AAPS v2.1.1 for omnipy v1.0
-
Hardware setup:
3.2. (optional) DIY rig setup
3.3. (optional) Increase RF range of RileyLink
-
4.1.AAPS setup
4.3 Upgrading
4.4 (optional) Wifi tethering on android
4.5 (optional) Wifi tethering on raspberry pi
-
User Intefaces
5.1 Pod activation and deactivation
5.2 SSH Console