-
Notifications
You must be signed in to change notification settings - Fork 26
Release Notes
Barış Kurtlutepe edited this page May 5, 2019
·
22 revisions
May 5th, 2019
New features & improvements:
- Improvement of handling communication failures due to reception problems
- French translation! Courtesy of Yann
- A new raspberry pi service which ensures wireless connections are kept alive
- Wireless hot-spot feature for the raspberry pi! Courtesy of Jeff, that activates and deactivates automatically
- Raspberry pi battery rig monitoring! Courtesy of Dan
Fixes:
- A workaround which wasn't working in case of communication failures
- Fixed message "pod with lot 0 and serial 0 removed" while activating a new pod.
Known Issues
- Activated pods will not have reservoir based alerts and pod expiry nearing alerts.
- Depending on the pod version (yet unknown) you may receive hourly "pod expired" alerts after 72h, until the 80th hour.
- Pods are silent during all operations.
April 29th, 2019
New features & improvements:
- Pod activation
- Basal rate setting (as per Profile function in AAPS)
- Headless setup for raspberry pi
- Performance improvements in AndroidAPS application
- Significant stability improvements in BLE connections and in pod communication
Fixes:
- Bluetooth tethering now works on newer android phones
- Auto detection of omnipy network address in AndroidAPS is now working
Known Issues
- Activated pods will not have reservoir based alerts and pod expiry nearing alerts.
- Depending on the pod version (yet unknown) you may receive hourly "pod expired" alerts after 72h, until the 80th hour.
March 17th, 2019
Fixes:
- Fixed an issue where failed pod commands were interpreted as successful by AAPS
- Fixed issue with temp directory creation which would lead to rileylink bt address not being saved
- Service now exits with error if it cannot read the password key during start-up
- Set password script is now restarting the service for changes to take effect
New features & improvements:
- Pump status is now uploaded to nightscout
- Version number embedded in AAPS About dialog
Known issues:
- SetBasalProfile is faking the action as before in v1.0 & v1.1, no actual basal profile changes are sent to the pod.
- FileNotFoundError during setup or operation with a message similar to: "No such file or directory: /run/user/1000/omnipy/". As a workaround, run this command after each restart of the raspberry pi:
mkdir -p /run/user/1000/omnipy
Links
March 16th, 2019
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.
- Fixed bug in UDP beacon service, now AAPS will detect the ip address of omnipy automatically if configured to do so.
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.
- 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.
- Added an update script for future versions
- omnipy service will now perform a graceful shutdown and wait for the currently running comand to finish.
- Reduced file i/o on the SD card to improve stability
Known issues
- SetBasalProfile is faking the action as before in v1.0, no actual basal profile changes are sent to the pod.
Links
March 3rd, 2019
First release
Known issues
- Detect IP address automatically in AAPS is not working
- Setting a basal profile from AAPS doesn't work
- The user interface on "PDM/Omnipod" tab in AAPS is a mock-up only and not functional.
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