diff --git a/docs/CROWDIN/cs/CompatiblePumps/OmnipodDASH.md b/docs/CROWDIN/cs/CompatiblePumps/OmnipodDASH.md index acde7a8b3f17..0100221ca434 100644 --- a/docs/CROWDIN/cs/CompatiblePumps/OmnipodDASH.md +++ b/docs/CROWDIN/cs/CompatiblePumps/OmnipodDASH.md @@ -19,8 +19,8 @@ These are the specifications of the **Omnipod DASH** ('DASH') and what different ## Omnipod DASH known AAPS constraints/issues - Android 16 requires **AAPS** version 3.3.2.1 or later. - General advice is to run **AAPS** on Android 14 or 16. Android 15 has many reported [issues](https://github.com/nightscout/AndroidAPS/issues/3471) from the community. However, if you do run on Android 15 you will likely need to enable Bluetooth Bonding to successfully activate and use Pods, see [General Troubleshooting](../GettingHelp/GeneralTroubleshooting.md) for more info on the Bonding settings. -- Too frequent basal updates may cause basal insulin delivery [problems](https://github.com/nightscout/AndroidAPS/issues/4158) with Omnipod Dash. When using **SMB**, limit the interval to 5 minutes minimum to avoid this issue. -- Dash only supports basal rate in 0.05 U/h steps. If you try to set basal with 0.01 steps in your **AAPS profile**, AAPS will not give a warning even though the pod will round up the rate into 0.05 steps. If you view POD MGMT/Pod History it will display that 0.05 basal was set. This also means the lowest basal rate allowed by the DASH in **AAPS** is 0.05U/h. +- Temporary Basal rate changes (which occur frequently when the loop is active, especially overnight) result in under-delivery of insulin. This is effectively a hardware limitation of the Omnipod DASH. The issue has been addressed in AAPS 3.4.2.3, but the functionality is currently opt-in. Follow the [Basal Drift Fix Instructions ](#omnipod-dash-Basal-drift-fix) instructions to enable it. For more information regarding the fix see [Github Issue - 4783](https://github.com/nightscout/AndroidAPS/issues/4783) for more info. +- Dash only supports basal rate in 0.05 U/h steps. If you try to set Basal with 0.01 steps in your **AAPS profile**, AAPS will not give a warning even though the pod will round up the rate into 0.05 steps. If you view POD MGMT/Pod History it will display that 0.05 basal was set. This also means the lowest basal rate allowed by the DASH in **AAPS** is 0.05U/h. - The activation status of a Pod is stored in the settings file, if you export a settings file with an active pod. Then change to a new pod, then restore the settings from your previous export you will have now restored the old pod activation and removed the new pod activation. This is why we recommend to export settings after each pod activation to allow a restore of that pods activation state if something happens to your rig. - When setting a new basal profile, DASH will suspend delivery before setting the new basal **Profile**. If there is a communication interruption or error, the basal profile won't automatically re-start. See section [Resuming Insulin Delivery](#omnipod-dash-resuming-insulin-delivery) for details. - If alerts are configured, and the pod is about to expire, the pod will keep beeping until alerts are silenced, see [Silencing Pod Alerts](#omnipod-dash-silencing-pod-alerts) for details. @@ -70,7 +70,7 @@ As long as **AAPS** is operational it will send basal rate adjustment commands t When for some reason the pod does not receive any new commands (for instance because communication was lost due to Pod ➜ phone distance) the pod will automatically fall back to default basal rates as defined in your [**Profile**](../SettingUpAaps/YourAapsProfile.md). ### **AAPS Profile(s) do not support 30 minute basal rate time frames** -If you are new to **AAPS** and are setting up your basal rate [**Profile**](../SettingUpAaps/YourAapsProfile.md) for the first time, please be aware that basal rates starting on a half-hour basis are not supported. For example, on your Omnipod PDM, if you have a basal rate of 1.1 units which starts at 09:30 and has a duration of 2 hours ending at 11:30, it is not possible replicate this exact basil **Profile** in **AAPS**. +If you are new to **AAPS** and are setting up your basal rate [**Profile**](../SettingUpAaps/YourAapsProfile.md) for the first time, please be aware that basal rates starting on a half-hour basis are not supported. For example, on your Omnipod PDM, if you have a basal rate of 1.1 units which starts at 09:30 and has a duration of 2 hours ending at 11:30, it is not possible replicate this exact Basal **Profile** in **AAPS**. You will need to change this 1.1 unit basal rate to a time range of either 9:00-11:00 or 10:00-12:00. Even though the DASH hardware itself supports the 30 minute basal rate **Profile** increments, **AAPS** does NOT support this feature. ### **0U/h Profile basal rates are NOT supported in AAPS** @@ -480,11 +480,46 @@ Additional note: * **SMS** - Returns value or 50+U for SMS responses * **Nightscout** - Uploads value of 50 when over 50 units to Nightscout (version 14.07 and older). Newer versions will report a value of 50+ when over 50 units. -(omnipod-dash-troubleshooting)= +(omnipod-dash-known-issues-workarounds)= + +## Known Issues Workarounds + +This section covers common workarounds and settings that need to be changed to enable a feature to work around a community reported issue that has a fix. E.g. the Basal drift enable process is documented here. + +(#omnipod-dash-Basal-drift-fix)= + +### Basal Drift Fix Instructions + +The Omnipod Dash pump has a limitation that can cause it to deliver less basal insulin than **AAPS** expects, see [Issue #4783](https://github.com/nightscout/AndroidAPS/issues/4783) for more technical details. + +The Dash uses an internal timer to determine when a basal pulse of 0.05 U is delivered. Once the timer interval elapses, the pulse is delivered. However, this timer is restarted whenever a basal rate change occurs e.g when **AAPS** sends a new Basal rate. + +When used in combination with looping, this leads to under-delivery of basal insulin, as the algorithm updates the basal rate on the pump frequently. + +The issue is most apparent during the night. During daytime operation, SMBs often result in a basal rate of 0, which masks the effect. In observed usage, this results in approximately 10% of the expected Total Daily Dose (TDD) not being delivered over a 24-hour period. Additionally, glucose targets are often not reached overnight, particularly after meals with prolonged glucose impact (e.g. pasta). + +***NOTE:** This issue is especially important to understand for people on very small dosages of insulin, Children for example.* + +#### Enable Basal Drift Fix in AAPS + +You must be running AAPS Version 3.4.2.3 or later for this feature. + +The Basal Drift Fix is not enabled by default on AAPS. + +**To enable it:** + +1. Create an empty file named `omnipod_drift_compensation` (2) in the `extra` (1) subfolder of your phone [AAPS directory](#preferences-maintenance-settings). + + ![dash_drift_enable_file](../images/DASH_images/DASH_Drift/dash_drift_enable_file.png) + + ***NOTE:** Ensure you check in the AAPS settings where your AAPS Directory is, and that you placed the file in the correct one, a number of several have been caught out putting the file into the wrong folder.* + +2. Restart **AAPS**. This must be done for it to recognise the file is present and enable the drift compensation feature. +3. Please visit this [Github issue #4783](https://github.com/nightscout/AndroidAPS/issues/4783) and thumbs up the first post indicating you are using this feature, we need this data to help demonstrate the feature is widely used. Once there is significant community adoption the removal of the enable file will be possible, we appreciate your support here. ## Troubleshooting -(omnipod-dash-delivery-suspended)= +(omnipod-dash-troubleshooting)= This section covers common known issues and solutions for Omnipod DASH use with AAPS. There is also [General Troubleshooting](../GettingHelp/GeneralTroubleshooting.md) section in the documentation that should be reviewed as it covers relevant topics for some Pod issues too. @@ -497,6 +532,9 @@ This section covers common known issues and solutions for Omnipod DASH use with For known issues with Bluetooth connections, dropouts of pump/pods, or activation and connection issues [Bluetooth Troubleshooting](../GettingHelp/BluetoothTroubleshooting.md) --- + +(omnipod-dash-delivery-suspended)= + ### Delivery suspended - There is no suspend button anymore. If you want to "suspend" the pod, you can set a zero **TBR** for x minutes. diff --git a/docs/CROWDIN/cs/images/DASH_images/DASH_Drift/dash_drift_enable_file.png b/docs/CROWDIN/cs/images/DASH_images/DASH_Drift/dash_drift_enable_file.png new file mode 100644 index 000000000000..917f90c264b5 Binary files /dev/null and b/docs/CROWDIN/cs/images/DASH_images/DASH_Drift/dash_drift_enable_file.png differ diff --git a/docs/CROWDIN/cs/images/DASH_images/DASH_Drift/dash_drift_pod_mgmt.png b/docs/CROWDIN/cs/images/DASH_images/DASH_Drift/dash_drift_pod_mgmt.png new file mode 100644 index 000000000000..5b9a8485a40b Binary files /dev/null and b/docs/CROWDIN/cs/images/DASH_images/DASH_Drift/dash_drift_pod_mgmt.png differ diff --git a/docs/CROWDIN/cs/images/DASH_images/DASH_Drift/dash_drift_pod_stats_end.png b/docs/CROWDIN/cs/images/DASH_images/DASH_Drift/dash_drift_pod_stats_end.png new file mode 100644 index 000000000000..5b268b517df0 Binary files /dev/null and b/docs/CROWDIN/cs/images/DASH_images/DASH_Drift/dash_drift_pod_stats_end.png differ diff --git a/docs/CROWDIN/cs/images/DASH_images/DASH_Drift/dash_drift_pod_stats_start.png b/docs/CROWDIN/cs/images/DASH_images/DASH_Drift/dash_drift_pod_stats_start.png new file mode 100644 index 000000000000..2863168f7b19 Binary files /dev/null and b/docs/CROWDIN/cs/images/DASH_images/DASH_Drift/dash_drift_pod_stats_start.png differ diff --git a/docs/CROWDIN/cs/images/DASH_images/DASH_Drift/dash_drift_tab_pod_mgmt.png b/docs/CROWDIN/cs/images/DASH_images/DASH_Drift/dash_drift_tab_pod_mgmt.png new file mode 100644 index 000000000000..30a5edb90b1d Binary files /dev/null and b/docs/CROWDIN/cs/images/DASH_images/DASH_Drift/dash_drift_tab_pod_mgmt.png differ diff --git a/docs/CROWDIN/cs/images/DASH_images/DASH_Drift/dash_drift_tdd.png b/docs/CROWDIN/cs/images/DASH_images/DASH_Drift/dash_drift_tdd.png new file mode 100644 index 000000000000..28b7685fa5bd Binary files /dev/null and b/docs/CROWDIN/cs/images/DASH_images/DASH_Drift/dash_drift_tdd.png differ diff --git a/docs/CROWDIN/de/CompatiblePumps/OmnipodDASH.md b/docs/CROWDIN/de/CompatiblePumps/OmnipodDASH.md index 37550339057e..3acc202a73c8 100644 --- a/docs/CROWDIN/de/CompatiblePumps/OmnipodDASH.md +++ b/docs/CROWDIN/de/CompatiblePumps/OmnipodDASH.md @@ -19,8 +19,8 @@ Hier finden sich die besonderen Merkmale des **Omnipod DASH** („DASH“) und d ## Bekannte Omnipod DASH AAPS-Einschränkungen/Probleme - Android 16 benötigt eine **AAPS**-Version 3.3.2.1 oder höher. - Generell wird empfohlen, **AAPS** auf Android 14 oder 16 auszuführen. Die Community hat im Zusammenhang mit Android 15 viele [Probleme](https://github.com/nightscout/AndroidAPS/issues/3471) gemeldet. Wenn Du Android 15 nutzt, wirst Du sehr wahrscheinlich das „Bluetooth Bonding“ aktivieren müssen, um Pods erfolgreich aktivieren und nutzen zu können. Schaue im Abschnitt [Allgemeine Problembehandlung](../GettingHelp/GeneralTroubleshooting.md) nach, wenn Du mehr über die „Bonding Einstellungen“ erfahren möchtest. -- Beim Omnipod Dash können zu häufige Änderungen der Basalrate zu [Problemen](https://github.com/nightscout/AndroidAPS/issues/4158) bei der Basalabgabe führen. Um das Problem zu umgehen, wenn Du **SMB**s nutzt, setzte das Änderungsintervall auf 5 Minuten oder länger. -- Dash unterstützt nur Basalraten in 0,05 IE/h Schritten. Solltest Du versuchen in Deinem **AAPS-Profil** Basalraten mit 0,01 Schritten zu hinterlegen, wirst Du keine Warnmeldung von AAPS erhalten. Der Pod wird die Basalrate auf 0,05 Schritte aufrunden. Wenn Du Dir „POD MGMT/Pod History“ anschaust, wirst Du sehen, dass ein 0,05 Basal gesetzt wurde. Dies bedeutet auch, dass die kleinst mögliche Basalrate des DASH in **AAPS** 0,05 IE/h beträgt. +- Temporary Basal rate changes (which occur frequently when the loop is active, especially overnight) result in under-delivery of insulin. This is effectively a hardware limitation of the Omnipod DASH. The issue has been addressed in AAPS 3.4.2.3, but the functionality is currently opt-in. Follow the [Basal Drift Fix Instructions ](#omnipod-dash-Basal-drift-fix) instructions to enable it. For more information regarding the fix see [Github Issue - 4783](https://github.com/nightscout/AndroidAPS/issues/4783) for more info. +- Dash unterstützt nur Basalraten in 0,05 IE/h Schritten. If you try to set Basal with 0.01 steps in your **AAPS profile**, AAPS will not give a warning even though the pod will round up the rate into 0.05 steps. Wenn Du Dir „POD MGMT/Pod History“ anschaust, wirst Du sehen, dass ein 0,05 Basal gesetzt wurde. Dies bedeutet auch, dass die kleinst mögliche Basalrate des DASH in **AAPS** 0,05 IE/h beträgt. - Wenn Du die Einstellungen mit einem aktiven Pod exportierst, enthält die Datei den Pod-Aktivierungsstatus. Wechsel dann auf einen neuen Pod und stelle die Einstellungen mit der Exportdatei wieder her. Damit hast Du sowohl die alte Pod-Aktivierung wieder hergestellt, als auch die neue Aktivierung gelöscht. Aus diesem Grund empfehlen wir die Einstellungen nach jeder Pod-Aktivierung zu exportieren, um eine Wiederherstellung des Pod-Aktivierungsstatus zu ermöglichen, falls etwas mit Deinem Rigg passiert. - Beim Setzen eines neuen Basalprofils unterbricht der DASH die Insulinabgabe, bevor das neue Basalprofil **Profil** gesetzt wird. Wenn es eine Kommunikationsstörung oder einen Fehler gibt, wird das Basalprofil nicht automatisch neu gestartet. Mehr Details hierzu findest Du im Abschnitt [Insulinabgabe fortsetzen](#omnipod-dash-resuming-insulin-delivery). - Wenn Alarme konfiguriert sind und der Pod bald ablaufen wird, wird der Pod solange piepen, bis die Alarme stumm geschaltet werden. Der Abschnitt [Pod-Alarme stummschalten](#omnipod-dash-silencing-pod-alerts) enthält detailliertere Informationen. @@ -70,8 +70,8 @@ Solange **AAPS** funktioniert, wird es Basalraten-Anpassungen mit einer maxmalen Sollte der Pod aus irgendeinem Grund keine neuen Befehle erhalten (wenn z. B. die Verbindung aufgrund der Entfernung zum Smartphone abbricht), wird der Pod auf die in Deinem [**Profil**](../SettingUpAaps/YourAapsProfile.md) hinterlegte Standard-Basalrate zurückfallen. ### **AAPS Profil(e) unterstützen keine halbstündlichen Basalraten** -Wenn Du noch unerfahren mit **AAPS** sein solltest und erstmalig Deine Basalraten in Dein [**Profil**](../SettingUpAaps/YourAapsProfile.md) einpflegst, beachte, dass Basalraten nur zur vollen Stunde beginnen dürfen. Ein Start zur halben Stunde wird nicht unterstützt. Beispiel: Wenn Du auf Deinem Omnipod PDM einen basalrate von 1,1 IE, die um 09.30h für 2h startet und um 11:30h zu Ende ist, wird es nicht möglich sein, diese Basalrate exakt so im Basal-**Profil** für **AAPS** abzubilden. -Du wirst die Basalrate von 1,1 IE entweder auf das Zeitfenster von 9:00-11:00 oder 10:00-12:00 verschieben müssen. Auch wenn die DASH-Hardware 30-minütige-Segmente im Basalraten-**Profil** managen kann, unterstützt **AAPS** dieses Feature NICHT. +Wenn Du noch unerfahren mit **AAPS** sein solltest und erstmalig Deine Basalraten in Dein [**Profil**](../SettingUpAaps/YourAapsProfile.md) einpflegst, beachte, dass Basalraten nur zur vollen Stunde beginnen dürfen. Ein Start zur halben Stunde wird nicht unterstützt. For example, on your Omnipod PDM, if you have a basal rate of 1.1 units which starts at 09:30 and has a duration of 2 hours ending at 11:30, it is not possible replicate this exact Basal **Profile** in **AAPS**. +You will need to change this 1.1 unit basal rate to a time range of either 9:00-11:00 or 10:00-12:00. Auch wenn die DASH-Hardware 30-minütige-Segmente im Basalraten-**Profil** managen kann, unterstützt **AAPS** dieses Feature NICHT. ### **0 IE/h im Basalraten-Profil werden in AAPS NICHT unterstützt** Auch wenn der DASH „Null-Basalraten“ unterstützt, nutzt **AAPS** Vielfache Deiner im **Profile** hinterlegten Basalrate, um festzulegen mit wieviel Insulin automatisch behandelt werden soll. Das funktioniert mit einer „Nul-Basalrate“ jedoch nicht. @@ -477,11 +477,46 @@ Sonstiges * **SMS** - Aus dem Pod übernommener Wert oder 50+ IE für SMS-Antworten * **Nightscout** - Lädt den Wert 50 hoch, wenn mehr als 50 Einheiten angezeigt werden (Nightscout Version 14.07 und älter). Neuere Versionen melden einen Wert von 50+, wenn sich mehr als 50 Einheiten im Reservoir befinden. -(omnipod-dash-troubleshooting)= +(omnipod-dash-known-issues-workarounds)= + +## Known Issues Workarounds + +This section covers common workarounds and settings that need to be changed to enable a feature to work around a community reported issue that has a fix. z.B. the Basal drift enable process is documented here. + +(#omnipod-dash-Basal-drift-fix)= + +### Basal Drift Fix Instructions + +The Omnipod Dash pump has a limitation that can cause it to deliver less basal insulin than **AAPS** expects, see [Issue #4783](https://github.com/nightscout/AndroidAPS/issues/4783) for more technical details. + +The Dash uses an internal timer to determine when a basal pulse of 0.05 U is delivered. Once the timer interval elapses, the pulse is delivered. However, this timer is restarted whenever a basal rate change occurs e.g when **AAPS** sends a new Basal rate. + +When used in combination with looping, this leads to under-delivery of basal insulin, as the algorithm updates the basal rate on the pump frequently. + +The issue is most apparent during the night. During daytime operation, SMBs often result in a basal rate of 0, which masks the effect. In observed usage, this results in approximately 10% of the expected Total Daily Dose (TDD) not being delivered over a 24-hour period. Additionally, glucose targets are often not reached overnight, particularly after meals with prolonged glucose impact (e.g. pasta). + +***NOTE:** This issue is especially important to understand for people on very small dosages of insulin, Children for example.* + +#### Enable Basal Drift Fix in AAPS + +You must be running AAPS Version 3.4.2.3 or later for this feature. + +The Basal Drift Fix is not enabled by default on AAPS. + +**To enable it:** + +1. Create an empty file named `omnipod_drift_compensation` (2) in the `extra` (1) subfolder of your phone [AAPS directory](#preferences-maintenance-settings). + + ![dash_drift_enable_file](../images/DASH_images/DASH_Drift/dash_drift_enable_file.png) + + ***NOTE:** Ensure you check in the AAPS settings where your AAPS Directory is, and that you placed the file in the correct one, a number of several have been caught out putting the file into the wrong folder.* + +2. Restart **AAPS**. This must be done for it to recognise the file is present and enable the drift compensation feature. +3. Please visit this [Github issue #4783](https://github.com/nightscout/AndroidAPS/issues/4783) and thumbs up the first post indicating you are using this feature, we need this data to help demonstrate the feature is widely used. Once there is significant community adoption the removal of the enable file will be possible, we appreciate your support here. ## Problembehandlung -(omnipod-dash-delivery-suspended)= +(omnipod-dash-troubleshooting)= Dieser Abschnitt behandelt bekannte Probleme und Lösungen für den Einsatz des Omnipod DASH mit AAPS. Es gibt in der Dokumentation auch einen Abschnitt [Allgemeine Fehlerbehebung](../GettingHelp/GeneralTroubleshooting.md), den Du lesen solltest, da dort auch relevante Pod-Themen abgedeckt werden. @@ -494,6 +529,9 @@ Dieser Abschnitt behandelt bekannte Probleme und Lösungen für den Einsatz des Bei bekannten Problemen mit Bluetooth-Verbindungen, Pumpen/Pods oder Aktivierungs- und Verbindungsproblemen schau im Abschnitt [Bluetooth-Fehlerbehebung](../GettingHelp/BluetoothTroubleshooting.md) nach. --- + +(omnipod-dash-delivery-suspended)= + ### Insulinabgabe unterbrochen - Es gibt keine Unterbrechen-Taste mehr. Wenn Du die Insulinabgabe unterbrechen möchtest, kannst Du eine Null-**TBR** für x Minuten setzen. diff --git a/docs/CROWDIN/de/images/DASH_images/DASH_Drift/dash_drift_enable_file.png b/docs/CROWDIN/de/images/DASH_images/DASH_Drift/dash_drift_enable_file.png new file mode 100644 index 000000000000..917f90c264b5 Binary files /dev/null and b/docs/CROWDIN/de/images/DASH_images/DASH_Drift/dash_drift_enable_file.png differ diff --git a/docs/CROWDIN/de/images/DASH_images/DASH_Drift/dash_drift_pod_mgmt.png b/docs/CROWDIN/de/images/DASH_images/DASH_Drift/dash_drift_pod_mgmt.png new file mode 100644 index 000000000000..5b9a8485a40b Binary files /dev/null and b/docs/CROWDIN/de/images/DASH_images/DASH_Drift/dash_drift_pod_mgmt.png differ diff --git a/docs/CROWDIN/de/images/DASH_images/DASH_Drift/dash_drift_pod_stats_end.png b/docs/CROWDIN/de/images/DASH_images/DASH_Drift/dash_drift_pod_stats_end.png new file mode 100644 index 000000000000..5b268b517df0 Binary files /dev/null and b/docs/CROWDIN/de/images/DASH_images/DASH_Drift/dash_drift_pod_stats_end.png differ diff --git a/docs/CROWDIN/de/images/DASH_images/DASH_Drift/dash_drift_pod_stats_start.png b/docs/CROWDIN/de/images/DASH_images/DASH_Drift/dash_drift_pod_stats_start.png new file mode 100644 index 000000000000..2863168f7b19 Binary files /dev/null and b/docs/CROWDIN/de/images/DASH_images/DASH_Drift/dash_drift_pod_stats_start.png differ diff --git a/docs/CROWDIN/de/images/DASH_images/DASH_Drift/dash_drift_tab_pod_mgmt.png b/docs/CROWDIN/de/images/DASH_images/DASH_Drift/dash_drift_tab_pod_mgmt.png new file mode 100644 index 000000000000..30a5edb90b1d Binary files /dev/null and b/docs/CROWDIN/de/images/DASH_images/DASH_Drift/dash_drift_tab_pod_mgmt.png differ diff --git a/docs/CROWDIN/de/images/DASH_images/DASH_Drift/dash_drift_tdd.png b/docs/CROWDIN/de/images/DASH_images/DASH_Drift/dash_drift_tdd.png new file mode 100644 index 000000000000..28b7685fa5bd Binary files /dev/null and b/docs/CROWDIN/de/images/DASH_images/DASH_Drift/dash_drift_tdd.png differ diff --git a/docs/CROWDIN/el/CompatiblePumps/OmnipodDASH.md b/docs/CROWDIN/el/CompatiblePumps/OmnipodDASH.md index cbb861d809c9..3c255d534ffa 100644 --- a/docs/CROWDIN/el/CompatiblePumps/OmnipodDASH.md +++ b/docs/CROWDIN/el/CompatiblePumps/OmnipodDASH.md @@ -19,8 +19,8 @@ These are the specifications of the **Omnipod DASH** ('DASH') and what different ## Omnipod DASH known AAPS constraints/issues - Android 16 requires **AAPS** version 3.3.2.1 or later. - General advice is to run **AAPS** on Android 14 or 16. Android 15 has many reported [issues](https://github.com/nightscout/AndroidAPS/issues/3471) from the community. However, if you do run on Android 15 you will likely need to enable Bluetooth Bonding to successfully activate and use Pods, see [General Troubleshooting](../GettingHelp/GeneralTroubleshooting.md) for more info on the Bonding settings. -- Too frequent basal updates may cause basal insulin delivery [problems](https://github.com/nightscout/AndroidAPS/issues/4158) with Omnipod Dash. When using **SMB**, limit the interval to 5 minutes minimum to avoid this issue. -- Dash only supports basal rate in 0.05 U/h steps. If you try to set basal with 0.01 steps in your **AAPS profile**, AAPS will not give a warning even though the pod will round up the rate into 0.05 steps. If you view POD MGMT/Pod History it will display that 0.05 basal was set. This also means the lowest basal rate allowed by the DASH in **AAPS** is 0.05U/h. +- Temporary Basal rate changes (which occur frequently when the loop is active, especially overnight) result in under-delivery of insulin. This is effectively a hardware limitation of the Omnipod DASH. The issue has been addressed in AAPS 3.4.2.3, but the functionality is currently opt-in. Follow the [Basal Drift Fix Instructions ](#omnipod-dash-Basal-drift-fix) instructions to enable it. For more information regarding the fix see [Github Issue - 4783](https://github.com/nightscout/AndroidAPS/issues/4783) for more info. +- Dash only supports basal rate in 0.05 U/h steps. If you try to set Basal with 0.01 steps in your **AAPS profile**, AAPS will not give a warning even though the pod will round up the rate into 0.05 steps. If you view POD MGMT/Pod History it will display that 0.05 basal was set. This also means the lowest basal rate allowed by the DASH in **AAPS** is 0.05U/h. - The activation status of a Pod is stored in the settings file, if you export a settings file with an active pod. Then change to a new pod, then restore the settings from your previous export you will have now restored the old pod activation and removed the new pod activation. This is why we recommend to export settings after each pod activation to allow a restore of that pods activation state if something happens to your rig. - When setting a new basal profile, DASH will suspend delivery before setting the new basal **Profile**. If there is a communication interruption or error, the basal profile won't automatically re-start. See section [Resuming Insulin Delivery](#omnipod-dash-resuming-insulin-delivery) for details. - If alerts are configured, and the pod is about to expire, the pod will keep beeping until alerts are silenced, see [Silencing Pod Alerts](#omnipod-dash-silencing-pod-alerts) for details. @@ -70,7 +70,7 @@ As long as **AAPS** is operational it will send basal rate adjustment commands t When for some reason the pod does not receive any new commands (for instance because communication was lost due to Pod ➜ phone distance) the pod will automatically fall back to default basal rates as defined in your [**Profile**](../SettingUpAaps/YourAapsProfile.md). ### **AAPS Profile(s) do not support 30 minute basal rate time frames** -If you are new to **AAPS** and are setting up your basal rate [**Profile**](../SettingUpAaps/YourAapsProfile.md) for the first time, please be aware that basal rates starting on a half-hour basis are not supported. For example, on your Omnipod PDM, if you have a basal rate of 1.1 units which starts at 09:30 and has a duration of 2 hours ending at 11:30, it is not possible replicate this exact basil **Profile** in **AAPS**. +If you are new to **AAPS** and are setting up your basal rate [**Profile**](../SettingUpAaps/YourAapsProfile.md) for the first time, please be aware that basal rates starting on a half-hour basis are not supported. For example, on your Omnipod PDM, if you have a basal rate of 1.1 units which starts at 09:30 and has a duration of 2 hours ending at 11:30, it is not possible replicate this exact Basal **Profile** in **AAPS**. You will need to change this 1.1 unit basal rate to a time range of either 9:00-11:00 or 10:00-12:00. Even though the DASH hardware itself supports the 30 minute basal rate **Profile** increments, **AAPS** does NOT support this feature. ### **0U/h Profile basal rates are NOT supported in AAPS** @@ -480,11 +480,46 @@ Additional note: * **SMS** - Returns value or 50+U for SMS responses * **Nightscout** - Uploads value of 50 when over 50 units to Nightscout (version 14.07 and older). Newer versions will report a value of 50+ when over 50 units. -(omnipod-dash-troubleshooting)= +(omnipod-dash-known-issues-workarounds)= + +## Known Issues Workarounds + +This section covers common workarounds and settings that need to be changed to enable a feature to work around a community reported issue that has a fix. E.g. the Basal drift enable process is documented here. + +(#omnipod-dash-Basal-drift-fix)= + +### Basal Drift Fix Instructions + +The Omnipod Dash pump has a limitation that can cause it to deliver less basal insulin than **AAPS** expects, see [Issue #4783](https://github.com/nightscout/AndroidAPS/issues/4783) for more technical details. + +The Dash uses an internal timer to determine when a basal pulse of 0.05 U is delivered. Once the timer interval elapses, the pulse is delivered. However, this timer is restarted whenever a basal rate change occurs e.g when **AAPS** sends a new Basal rate. + +When used in combination with looping, this leads to under-delivery of basal insulin, as the algorithm updates the basal rate on the pump frequently. + +The issue is most apparent during the night. During daytime operation, SMBs often result in a basal rate of 0, which masks the effect. In observed usage, this results in approximately 10% of the expected Total Daily Dose (TDD) not being delivered over a 24-hour period. Additionally, glucose targets are often not reached overnight, particularly after meals with prolonged glucose impact (e.g. pasta). + +***NOTE:** This issue is especially important to understand for people on very small dosages of insulin, Children for example.* + +#### Enable Basal Drift Fix in AAPS + +You must be running AAPS Version 3.4.2.3 or later for this feature. + +The Basal Drift Fix is not enabled by default on AAPS. + +**To enable it:** + +1. Create an empty file named `omnipod_drift_compensation` (2) in the `extra` (1) subfolder of your phone [AAPS directory](#preferences-maintenance-settings). + + ![dash_drift_enable_file](../images/DASH_images/DASH_Drift/dash_drift_enable_file.png) + + ***NOTE:** Ensure you check in the AAPS settings where your AAPS Directory is, and that you placed the file in the correct one, a number of several have been caught out putting the file into the wrong folder.* + +2. Restart **AAPS**. This must be done for it to recognise the file is present and enable the drift compensation feature. +3. Please visit this [Github issue #4783](https://github.com/nightscout/AndroidAPS/issues/4783) and thumbs up the first post indicating you are using this feature, we need this data to help demonstrate the feature is widely used. Once there is significant community adoption the removal of the enable file will be possible, we appreciate your support here. ## Troubleshooting -(omnipod-dash-delivery-suspended)= +(omnipod-dash-troubleshooting)= This section covers common known issues and solutions for Omnipod DASH use with AAPS. There is also [General Troubleshooting](../GettingHelp/GeneralTroubleshooting.md) section in the documentation that should be reviewed as it covers relevant topics for some Pod issues too. @@ -497,6 +532,9 @@ This section covers common known issues and solutions for Omnipod DASH use with For known issues with Bluetooth connections, dropouts of pump/pods, or activation and connection issues [Bluetooth Troubleshooting](../GettingHelp/BluetoothTroubleshooting.md) --- + +(omnipod-dash-delivery-suspended)= + ### Delivery suspended - There is no suspend button anymore. If you want to "suspend" the pod, you can set a zero **TBR** for x minutes. diff --git a/docs/CROWDIN/el/images/DASH_images/DASH_Drift/dash_drift_enable_file.png b/docs/CROWDIN/el/images/DASH_images/DASH_Drift/dash_drift_enable_file.png new file mode 100644 index 000000000000..917f90c264b5 Binary files /dev/null and b/docs/CROWDIN/el/images/DASH_images/DASH_Drift/dash_drift_enable_file.png differ diff --git a/docs/CROWDIN/el/images/DASH_images/DASH_Drift/dash_drift_pod_mgmt.png b/docs/CROWDIN/el/images/DASH_images/DASH_Drift/dash_drift_pod_mgmt.png new file mode 100644 index 000000000000..5b9a8485a40b Binary files /dev/null and b/docs/CROWDIN/el/images/DASH_images/DASH_Drift/dash_drift_pod_mgmt.png differ diff --git a/docs/CROWDIN/el/images/DASH_images/DASH_Drift/dash_drift_pod_stats_end.png b/docs/CROWDIN/el/images/DASH_images/DASH_Drift/dash_drift_pod_stats_end.png new file mode 100644 index 000000000000..5b268b517df0 Binary files /dev/null and b/docs/CROWDIN/el/images/DASH_images/DASH_Drift/dash_drift_pod_stats_end.png differ diff --git a/docs/CROWDIN/el/images/DASH_images/DASH_Drift/dash_drift_pod_stats_start.png b/docs/CROWDIN/el/images/DASH_images/DASH_Drift/dash_drift_pod_stats_start.png new file mode 100644 index 000000000000..2863168f7b19 Binary files /dev/null and b/docs/CROWDIN/el/images/DASH_images/DASH_Drift/dash_drift_pod_stats_start.png differ diff --git a/docs/CROWDIN/el/images/DASH_images/DASH_Drift/dash_drift_tab_pod_mgmt.png b/docs/CROWDIN/el/images/DASH_images/DASH_Drift/dash_drift_tab_pod_mgmt.png new file mode 100644 index 000000000000..30a5edb90b1d Binary files /dev/null and b/docs/CROWDIN/el/images/DASH_images/DASH_Drift/dash_drift_tab_pod_mgmt.png differ diff --git a/docs/CROWDIN/el/images/DASH_images/DASH_Drift/dash_drift_tdd.png b/docs/CROWDIN/el/images/DASH_images/DASH_Drift/dash_drift_tdd.png new file mode 100644 index 000000000000..28b7685fa5bd Binary files /dev/null and b/docs/CROWDIN/el/images/DASH_images/DASH_Drift/dash_drift_tdd.png differ diff --git a/docs/CROWDIN/es/CompatiblePumps/OmnipodDASH.md b/docs/CROWDIN/es/CompatiblePumps/OmnipodDASH.md index 97460feac0b7..5e89ea63bdc1 100644 --- a/docs/CROWDIN/es/CompatiblePumps/OmnipodDASH.md +++ b/docs/CROWDIN/es/CompatiblePumps/OmnipodDASH.md @@ -19,8 +19,8 @@ These are the specifications of the **Omnipod DASH** ('DASH') and what different ## Omnipod DASH known AAPS constraints/issues - Android 16 requires **AAPS** version 3.3.2.1 or later. - General advice is to run **AAPS** on Android 14 or 16. Android 15 has many reported [issues](https://github.com/nightscout/AndroidAPS/issues/3471) from the community. However, if you do run on Android 15 you will likely need to enable Bluetooth Bonding to successfully activate and use Pods, see [General Troubleshooting](../GettingHelp/GeneralTroubleshooting.md) for more info on the Bonding settings. -- Too frequent basal updates may cause basal insulin delivery [problems](https://github.com/nightscout/AndroidAPS/issues/4158) with Omnipod Dash. When using **SMB**, limit the interval to 5 minutes minimum to avoid this issue. -- Dash only supports basal rate in 0.05 U/h steps. If you try to set basal with 0.01 steps in your **AAPS profile**, AAPS will not give a warning even though the pod will round up the rate into 0.05 steps. If you view POD MGMT/Pod History it will display that 0.05 basal was set. This also means the lowest basal rate allowed by the DASH in **AAPS** is 0.05U/h. +- Temporary Basal rate changes (which occur frequently when the loop is active, especially overnight) result in under-delivery of insulin. This is effectively a hardware limitation of the Omnipod DASH. The issue has been addressed in AAPS 3.4.2.3, but the functionality is currently opt-in. Follow the [Basal Drift Fix Instructions ](#omnipod-dash-Basal-drift-fix) instructions to enable it. For more information regarding the fix see [Github Issue - 4783](https://github.com/nightscout/AndroidAPS/issues/4783) for more info. +- Dash only supports basal rate in 0.05 U/h steps. If you try to set Basal with 0.01 steps in your **AAPS profile**, AAPS will not give a warning even though the pod will round up the rate into 0.05 steps. If you view POD MGMT/Pod History it will display that 0.05 basal was set. This also means the lowest basal rate allowed by the DASH in **AAPS** is 0.05U/h. - The activation status of a Pod is stored in the settings file, if you export a settings file with an active pod. Then change to a new pod, then restore the settings from your previous export you will have now restored the old pod activation and removed the new pod activation. This is why we recommend to export settings after each pod activation to allow a restore of that pods activation state if something happens to your rig. - When setting a new basal profile, DASH will suspend delivery before setting the new basal **Profile**. If there is a communication interruption or error, the basal profile won't automatically re-start. See section [Resuming Insulin Delivery](#omnipod-dash-resuming-insulin-delivery) for details. - If alerts are configured, and the pod is about to expire, the pod will keep beeping until alerts are silenced, see [Silencing Pod Alerts](#omnipod-dash-silencing-pod-alerts) for details. @@ -70,7 +70,7 @@ As long as **AAPS** is operational it will send basal rate adjustment commands t When for some reason the pod does not receive any new commands (for instance because communication was lost due to Pod ➜ phone distance) the pod will automatically fall back to default basal rates as defined in your [**Profile**](../SettingUpAaps/YourAapsProfile.md). ### **AAPS Profile(s) do not support 30 minute basal rate time frames** -If you are new to **AAPS** and are setting up your basal rate [**Profile**](../SettingUpAaps/YourAapsProfile.md) for the first time, please be aware that basal rates starting on a half-hour basis are not supported. For example, on your Omnipod PDM, if you have a basal rate of 1.1 units which starts at 09:30 and has a duration of 2 hours ending at 11:30, it is not possible replicate this exact basil **Profile** in **AAPS**. +If you are new to **AAPS** and are setting up your basal rate [**Profile**](../SettingUpAaps/YourAapsProfile.md) for the first time, please be aware that basal rates starting on a half-hour basis are not supported. For example, on your Omnipod PDM, if you have a basal rate of 1.1 units which starts at 09:30 and has a duration of 2 hours ending at 11:30, it is not possible replicate this exact Basal **Profile** in **AAPS**. You will need to change this 1.1 unit basal rate to a time range of either 9:00-11:00 or 10:00-12:00. Even though the DASH hardware itself supports the 30 minute basal rate **Profile** increments, **AAPS** does NOT support this feature. ### **0U/h Profile basal rates are NOT supported in AAPS** @@ -480,11 +480,46 @@ Additional note: * **SMS** - Returns value or 50+U for SMS responses * **Nightscout** - Uploads value of 50 when over 50 units to Nightscout (version 14.07 and older). Newer versions will report a value of 50+ when over 50 units. -(omnipod-dash-troubleshooting)= +(omnipod-dash-known-issues-workarounds)= + +## Known Issues Workarounds + +This section covers common workarounds and settings that need to be changed to enable a feature to work around a community reported issue that has a fix. E.g. the Basal drift enable process is documented here. + +(#omnipod-dash-Basal-drift-fix)= + +### Basal Drift Fix Instructions + +The Omnipod Dash pump has a limitation that can cause it to deliver less basal insulin than **AAPS** expects, see [Issue #4783](https://github.com/nightscout/AndroidAPS/issues/4783) for more technical details. + +The Dash uses an internal timer to determine when a basal pulse of 0.05 U is delivered. Once the timer interval elapses, the pulse is delivered. However, this timer is restarted whenever a basal rate change occurs e.g when **AAPS** sends a new Basal rate. + +When used in combination with looping, this leads to under-delivery of basal insulin, as the algorithm updates the basal rate on the pump frequently. + +The issue is most apparent during the night. During daytime operation, SMBs often result in a basal rate of 0, which masks the effect. In observed usage, this results in approximately 10% of the expected Total Daily Dose (TDD) not being delivered over a 24-hour period. Additionally, glucose targets are often not reached overnight, particularly after meals with prolonged glucose impact (e.g. pasta). + +***NOTE:** This issue is especially important to understand for people on very small dosages of insulin, Children for example.* + +#### Enable Basal Drift Fix in AAPS + +You must be running AAPS Version 3.4.2.3 or later for this feature. + +The Basal Drift Fix is not enabled by default on AAPS. + +**To enable it:** + +1. Create an empty file named `omnipod_drift_compensation` (2) in the `extra` (1) subfolder of your phone [AAPS directory](#preferences-maintenance-settings). + + ![dash_drift_enable_file](../images/DASH_images/DASH_Drift/dash_drift_enable_file.png) + + ***NOTE:** Ensure you check in the AAPS settings where your AAPS Directory is, and that you placed the file in the correct one, a number of several have been caught out putting the file into the wrong folder.* + +2. Restart **AAPS**. This must be done for it to recognise the file is present and enable the drift compensation feature. +3. Please visit this [Github issue #4783](https://github.com/nightscout/AndroidAPS/issues/4783) and thumbs up the first post indicating you are using this feature, we need this data to help demonstrate the feature is widely used. Once there is significant community adoption the removal of the enable file will be possible, we appreciate your support here. ## Troubleshooting -(omnipod-dash-delivery-suspended)= +(omnipod-dash-troubleshooting)= This section covers common known issues and solutions for Omnipod DASH use with AAPS. There is also [General Troubleshooting](../GettingHelp/GeneralTroubleshooting.md) section in the documentation that should be reviewed as it covers relevant topics for some Pod issues too. @@ -497,6 +532,9 @@ This section covers common known issues and solutions for Omnipod DASH use with For known issues with Bluetooth connections, dropouts of pump/pods, or activation and connection issues [Bluetooth Troubleshooting](../GettingHelp/BluetoothTroubleshooting.md) --- + +(omnipod-dash-delivery-suspended)= + ### Delivery suspended - There is no suspend button anymore. If you want to "suspend" the pod, you can set a zero **TBR** for x minutes. diff --git a/docs/CROWDIN/es/images/DASH_images/DASH_Drift/dash_drift_enable_file.png b/docs/CROWDIN/es/images/DASH_images/DASH_Drift/dash_drift_enable_file.png new file mode 100644 index 000000000000..917f90c264b5 Binary files /dev/null and b/docs/CROWDIN/es/images/DASH_images/DASH_Drift/dash_drift_enable_file.png differ diff --git a/docs/CROWDIN/es/images/DASH_images/DASH_Drift/dash_drift_pod_mgmt.png b/docs/CROWDIN/es/images/DASH_images/DASH_Drift/dash_drift_pod_mgmt.png new file mode 100644 index 000000000000..5b9a8485a40b Binary files /dev/null and b/docs/CROWDIN/es/images/DASH_images/DASH_Drift/dash_drift_pod_mgmt.png differ diff --git a/docs/CROWDIN/es/images/DASH_images/DASH_Drift/dash_drift_pod_stats_end.png b/docs/CROWDIN/es/images/DASH_images/DASH_Drift/dash_drift_pod_stats_end.png new file mode 100644 index 000000000000..5b268b517df0 Binary files /dev/null and b/docs/CROWDIN/es/images/DASH_images/DASH_Drift/dash_drift_pod_stats_end.png differ diff --git a/docs/CROWDIN/es/images/DASH_images/DASH_Drift/dash_drift_pod_stats_start.png b/docs/CROWDIN/es/images/DASH_images/DASH_Drift/dash_drift_pod_stats_start.png new file mode 100644 index 000000000000..2863168f7b19 Binary files /dev/null and b/docs/CROWDIN/es/images/DASH_images/DASH_Drift/dash_drift_pod_stats_start.png differ diff --git a/docs/CROWDIN/es/images/DASH_images/DASH_Drift/dash_drift_tab_pod_mgmt.png b/docs/CROWDIN/es/images/DASH_images/DASH_Drift/dash_drift_tab_pod_mgmt.png new file mode 100644 index 000000000000..30a5edb90b1d Binary files /dev/null and b/docs/CROWDIN/es/images/DASH_images/DASH_Drift/dash_drift_tab_pod_mgmt.png differ diff --git a/docs/CROWDIN/es/images/DASH_images/DASH_Drift/dash_drift_tdd.png b/docs/CROWDIN/es/images/DASH_images/DASH_Drift/dash_drift_tdd.png new file mode 100644 index 000000000000..28b7685fa5bd Binary files /dev/null and b/docs/CROWDIN/es/images/DASH_images/DASH_Drift/dash_drift_tdd.png differ diff --git a/docs/CROWDIN/fr/CompatiblePumps/OmnipodDASH.md b/docs/CROWDIN/fr/CompatiblePumps/OmnipodDASH.md index e95a3dc4e48a..94f04af5d1d9 100644 --- a/docs/CROWDIN/fr/CompatiblePumps/OmnipodDASH.md +++ b/docs/CROWDIN/fr/CompatiblePumps/OmnipodDASH.md @@ -19,8 +19,8 @@ These are the specifications of the **Omnipod DASH** ('DASH') and what different ## Omnipod DASH known AAPS constraints/issues - Android 16 requires **AAPS** version 3.3.2.1 or later. - General advice is to run **AAPS** on Android 14 or 16. Android 15 has many reported [issues](https://github.com/nightscout/AndroidAPS/issues/3471) from the community. However, if you do run on Android 15 you will likely need to enable Bluetooth Bonding to successfully activate and use Pods, see [General Troubleshooting](../GettingHelp/GeneralTroubleshooting.md) for more info on the Bonding settings. -- Too frequent basal updates may cause basal insulin delivery [problems](https://github.com/nightscout/AndroidAPS/issues/4158) with Omnipod Dash. When using **SMB**, limit the interval to 5 minutes minimum to avoid this issue. -- Dash only supports basal rate in 0.05 U/h steps. If you try to set basal with 0.01 steps in your **AAPS profile**, AAPS will not give a warning even though the pod will round up the rate into 0.05 steps. If you view POD MGMT/Pod History it will display that 0.05 basal was set. This also means the lowest basal rate allowed by the DASH in **AAPS** is 0.05U/h. +- Temporary Basal rate changes (which occur frequently when the loop is active, especially overnight) result in under-delivery of insulin. This is effectively a hardware limitation of the Omnipod DASH. The issue has been addressed in AAPS 3.4.2.3, but the functionality is currently opt-in. Follow the [Basal Drift Fix Instructions ](#omnipod-dash-Basal-drift-fix) instructions to enable it. For more information regarding the fix see [Github Issue - 4783](https://github.com/nightscout/AndroidAPS/issues/4783) for more info. +- Dash only supports basal rate in 0.05 U/h steps. If you try to set Basal with 0.01 steps in your **AAPS profile**, AAPS will not give a warning even though the pod will round up the rate into 0.05 steps. If you view POD MGMT/Pod History it will display that 0.05 basal was set. This also means the lowest basal rate allowed by the DASH in **AAPS** is 0.05U/h. - The activation status of a Pod is stored in the settings file, if you export a settings file with an active pod. Then change to a new pod, then restore the settings from your previous export you will have now restored the old pod activation and removed the new pod activation. This is why we recommend to export settings after each pod activation to allow a restore of that pods activation state if something happens to your rig. - When setting a new basal profile, DASH will suspend delivery before setting the new basal **Profile**. If there is a communication interruption or error, the basal profile won't automatically re-start. See section [Resuming Insulin Delivery](#omnipod-dash-resuming-insulin-delivery) for details. - If alerts are configured, and the pod is about to expire, the pod will keep beeping until alerts are silenced, see [Silencing Pod Alerts](#omnipod-dash-silencing-pod-alerts) for details. @@ -70,7 +70,7 @@ As long as **AAPS** is operational it will send basal rate adjustment commands t When for some reason the pod does not receive any new commands (for instance because communication was lost due to Pod ➜ phone distance) the pod will automatically fall back to default basal rates as defined in your [**Profile**](../SettingUpAaps/YourAapsProfile.md). ### **AAPS Profile(s) do not support 30 minute basal rate time frames** -If you are new to **AAPS** and are setting up your basal rate [**Profile**](../SettingUpAaps/YourAapsProfile.md) for the first time, please be aware that basal rates starting on a half-hour basis are not supported. For example, on your Omnipod PDM, if you have a basal rate of 1.1 units which starts at 09:30 and has a duration of 2 hours ending at 11:30, it is not possible replicate this exact basil **Profile** in **AAPS**. +If you are new to **AAPS** and are setting up your basal rate [**Profile**](../SettingUpAaps/YourAapsProfile.md) for the first time, please be aware that basal rates starting on a half-hour basis are not supported. For example, on your Omnipod PDM, if you have a basal rate of 1.1 units which starts at 09:30 and has a duration of 2 hours ending at 11:30, it is not possible replicate this exact Basal **Profile** in **AAPS**. You will need to change this 1.1 unit basal rate to a time range of either 9:00-11:00 or 10:00-12:00. Even though the DASH hardware itself supports the 30 minute basal rate **Profile** increments, **AAPS** does NOT support this feature. ### **0U/h Profile basal rates are NOT supported in AAPS** @@ -480,11 +480,46 @@ Additional note: * **SMS** - Renvoie la valeur ou 50+U pour les réponses SMS * **Nightscout** - Envoie la valeur 50 vers Nightscout s'il y a plus de 50 unités (version 14,07 et plus). Les nouvelles versions afficheront la valeur de plus de 50+ si au-dessus de 50 unités. -(omnipod-dash-troubleshooting)= +(omnipod-dash-known-issues-workarounds)= + +## Known Issues Workarounds + +This section covers common workarounds and settings that need to be changed to enable a feature to work around a community reported issue that has a fix. Par ex. the Basal drift enable process is documented here. + +(#omnipod-dash-Basal-drift-fix)= + +### Basal Drift Fix Instructions + +The Omnipod Dash pump has a limitation that can cause it to deliver less basal insulin than **AAPS** expects, see [Issue #4783](https://github.com/nightscout/AndroidAPS/issues/4783) for more technical details. + +The Dash uses an internal timer to determine when a basal pulse of 0.05 U is delivered. Once the timer interval elapses, the pulse is delivered. However, this timer is restarted whenever a basal rate change occurs e.g when **AAPS** sends a new Basal rate. + +When used in combination with looping, this leads to under-delivery of basal insulin, as the algorithm updates the basal rate on the pump frequently. + +The issue is most apparent during the night. During daytime operation, SMBs often result in a basal rate of 0, which masks the effect. In observed usage, this results in approximately 10% of the expected Total Daily Dose (TDD) not being delivered over a 24-hour period. Additionally, glucose targets are often not reached overnight, particularly after meals with prolonged glucose impact (e.g. pasta). + +***NOTE:** This issue is especially important to understand for people on very small dosages of insulin, Children for example.* + +#### Enable Basal Drift Fix in AAPS + +You must be running AAPS Version 3.4.2.3 or later for this feature. + +The Basal Drift Fix is not enabled by default on AAPS. + +**To enable it:** + +1. Create an empty file named `omnipod_drift_compensation` (2) in the `extra` (1) subfolder of your phone [AAPS directory](#preferences-maintenance-settings). + + ![dash_drift_enable_file](../images/DASH_images/DASH_Drift/dash_drift_enable_file.png) + + ***NOTE:** Ensure you check in the AAPS settings where your AAPS Directory is, and that you placed the file in the correct one, a number of several have been caught out putting the file into the wrong folder.* + +2. Restart **AAPS**. This must be done for it to recognise the file is present and enable the drift compensation feature. +3. Please visit this [Github issue #4783](https://github.com/nightscout/AndroidAPS/issues/4783) and thumbs up the first post indicating you are using this feature, we need this data to help demonstrate the feature is widely used. Once there is significant community adoption the removal of the enable file will be possible, we appreciate your support here. ## Troubleshooting -(omnipod-dash-delivery-suspended)= +(omnipod-dash-troubleshooting)= This section covers common known issues and solutions for Omnipod DASH use with AAPS. There is also [General Troubleshooting](../GettingHelp/GeneralTroubleshooting.md) section in the documentation that should be reviewed as it covers relevant topics for some Pod issues too. @@ -497,6 +532,9 @@ This section covers common known issues and solutions for Omnipod DASH use with For known issues with Bluetooth connections, dropouts of pump/pods, or activation and connection issues [Bluetooth Troubleshooting](../GettingHelp/BluetoothTroubleshooting.md) --- + +(omnipod-dash-delivery-suspended)= + ### Delivery suspended - There is no suspend button anymore. If you want to "suspend" the pod, you can set a zero **TBR** for x minutes. diff --git a/docs/CROWDIN/fr/images/DASH_images/DASH_Drift/dash_drift_enable_file.png b/docs/CROWDIN/fr/images/DASH_images/DASH_Drift/dash_drift_enable_file.png new file mode 100644 index 000000000000..917f90c264b5 Binary files /dev/null and b/docs/CROWDIN/fr/images/DASH_images/DASH_Drift/dash_drift_enable_file.png differ diff --git a/docs/CROWDIN/fr/images/DASH_images/DASH_Drift/dash_drift_pod_mgmt.png b/docs/CROWDIN/fr/images/DASH_images/DASH_Drift/dash_drift_pod_mgmt.png new file mode 100644 index 000000000000..5b9a8485a40b Binary files /dev/null and b/docs/CROWDIN/fr/images/DASH_images/DASH_Drift/dash_drift_pod_mgmt.png differ diff --git a/docs/CROWDIN/fr/images/DASH_images/DASH_Drift/dash_drift_pod_stats_end.png b/docs/CROWDIN/fr/images/DASH_images/DASH_Drift/dash_drift_pod_stats_end.png new file mode 100644 index 000000000000..5b268b517df0 Binary files /dev/null and b/docs/CROWDIN/fr/images/DASH_images/DASH_Drift/dash_drift_pod_stats_end.png differ diff --git a/docs/CROWDIN/fr/images/DASH_images/DASH_Drift/dash_drift_pod_stats_start.png b/docs/CROWDIN/fr/images/DASH_images/DASH_Drift/dash_drift_pod_stats_start.png new file mode 100644 index 000000000000..2863168f7b19 Binary files /dev/null and b/docs/CROWDIN/fr/images/DASH_images/DASH_Drift/dash_drift_pod_stats_start.png differ diff --git a/docs/CROWDIN/fr/images/DASH_images/DASH_Drift/dash_drift_tab_pod_mgmt.png b/docs/CROWDIN/fr/images/DASH_images/DASH_Drift/dash_drift_tab_pod_mgmt.png new file mode 100644 index 000000000000..30a5edb90b1d Binary files /dev/null and b/docs/CROWDIN/fr/images/DASH_images/DASH_Drift/dash_drift_tab_pod_mgmt.png differ diff --git a/docs/CROWDIN/fr/images/DASH_images/DASH_Drift/dash_drift_tdd.png b/docs/CROWDIN/fr/images/DASH_images/DASH_Drift/dash_drift_tdd.png new file mode 100644 index 000000000000..28b7685fa5bd Binary files /dev/null and b/docs/CROWDIN/fr/images/DASH_images/DASH_Drift/dash_drift_tdd.png differ diff --git a/docs/CROWDIN/he/CompatiblePumps/OmnipodDASH.md b/docs/CROWDIN/he/CompatiblePumps/OmnipodDASH.md index 7f51a891592d..a6599977d7f2 100644 --- a/docs/CROWDIN/he/CompatiblePumps/OmnipodDASH.md +++ b/docs/CROWDIN/he/CompatiblePumps/OmnipodDASH.md @@ -19,8 +19,8 @@ These are the specifications of the **Omnipod DASH** ('DASH') and what different ## Omnipod DASH known AAPS constraints/issues - Android 16 requires **AAPS** version 3.3.2.1 or later. - General advice is to run **AAPS** on Android 14 or 16. Android 15 has many reported [issues](https://github.com/nightscout/AndroidAPS/issues/3471) from the community. However, if you do run on Android 15 you will likely need to enable Bluetooth Bonding to successfully activate and use Pods, see [General Troubleshooting](../GettingHelp/GeneralTroubleshooting.md) for more info on the Bonding settings. -- Too frequent basal updates may cause basal insulin delivery [problems](https://github.com/nightscout/AndroidAPS/issues/4158) with Omnipod Dash. When using **SMB**, limit the interval to 5 minutes minimum to avoid this issue. -- Dash only supports basal rate in 0.05 U/h steps. If you try to set basal with 0.01 steps in your **AAPS profile**, AAPS will not give a warning even though the pod will round up the rate into 0.05 steps. If you view POD MGMT/Pod History it will display that 0.05 basal was set. This also means the lowest basal rate allowed by the DASH in **AAPS** is 0.05U/h. +- Temporary Basal rate changes (which occur frequently when the loop is active, especially overnight) result in under-delivery of insulin. This is effectively a hardware limitation of the Omnipod DASH. The issue has been addressed in AAPS 3.4.2.3, but the functionality is currently opt-in. Follow the [Basal Drift Fix Instructions ](#omnipod-dash-Basal-drift-fix) instructions to enable it. For more information regarding the fix see [Github Issue - 4783](https://github.com/nightscout/AndroidAPS/issues/4783) for more info. +- Dash only supports basal rate in 0.05 U/h steps. If you try to set Basal with 0.01 steps in your **AAPS profile**, AAPS will not give a warning even though the pod will round up the rate into 0.05 steps. If you view POD MGMT/Pod History it will display that 0.05 basal was set. This also means the lowest basal rate allowed by the DASH in **AAPS** is 0.05U/h. - The activation status of a Pod is stored in the settings file, if you export a settings file with an active pod. Then change to a new pod, then restore the settings from your previous export you will have now restored the old pod activation and removed the new pod activation. This is why we recommend to export settings after each pod activation to allow a restore of that pods activation state if something happens to your rig. - When setting a new basal profile, DASH will suspend delivery before setting the new basal **Profile**. If there is a communication interruption or error, the basal profile won't automatically re-start. See section [Resuming Insulin Delivery](#omnipod-dash-resuming-insulin-delivery) for details. - If alerts are configured, and the pod is about to expire, the pod will keep beeping until alerts are silenced, see [Silencing Pod Alerts](#omnipod-dash-silencing-pod-alerts) for details. @@ -70,7 +70,7 @@ As long as **AAPS** is operational it will send basal rate adjustment commands t When for some reason the pod does not receive any new commands (for instance because communication was lost due to Pod ➜ phone distance) the pod will automatically fall back to default basal rates as defined in your [**Profile**](../SettingUpAaps/YourAapsProfile.md). ### **AAPS Profile(s) do not support 30 minute basal rate time frames** -If you are new to **AAPS** and are setting up your basal rate [**Profile**](../SettingUpAaps/YourAapsProfile.md) for the first time, please be aware that basal rates starting on a half-hour basis are not supported. For example, on your Omnipod PDM, if you have a basal rate of 1.1 units which starts at 09:30 and has a duration of 2 hours ending at 11:30, it is not possible replicate this exact basil **Profile** in **AAPS**. +If you are new to **AAPS** and are setting up your basal rate [**Profile**](../SettingUpAaps/YourAapsProfile.md) for the first time, please be aware that basal rates starting on a half-hour basis are not supported. For example, on your Omnipod PDM, if you have a basal rate of 1.1 units which starts at 09:30 and has a duration of 2 hours ending at 11:30, it is not possible replicate this exact Basal **Profile** in **AAPS**. You will need to change this 1.1 unit basal rate to a time range of either 9:00-11:00 or 10:00-12:00. Even though the DASH hardware itself supports the 30 minute basal rate **Profile** increments, **AAPS** does NOT support this feature. ### **0U/h Profile basal rates are NOT supported in AAPS** @@ -480,11 +480,46 @@ Additional note: * **SMS** - מחזירה ערך או 50+U בתגובות של SMS * **נייטסקאוט** - העלאת ערך של 50 כאשר מעל 50 יחידות לנייטסקאוט (גרסה 14.07 ומעלה). גרסאות חדשות יותר ידווחו על ערך של 50+ כאשר מעל 50 יחידות. -(omnipod-dash-troubleshooting)= +(omnipod-dash-known-issues-workarounds)= + +## Known Issues Workarounds + +This section covers common workarounds and settings that need to be changed to enable a feature to work around a community reported issue that has a fix. E.g. the Basal drift enable process is documented here. + +(#omnipod-dash-Basal-drift-fix)= + +### Basal Drift Fix Instructions + +The Omnipod Dash pump has a limitation that can cause it to deliver less basal insulin than **AAPS** expects, see [Issue #4783](https://github.com/nightscout/AndroidAPS/issues/4783) for more technical details. + +The Dash uses an internal timer to determine when a basal pulse of 0.05 U is delivered. Once the timer interval elapses, the pulse is delivered. However, this timer is restarted whenever a basal rate change occurs e.g when **AAPS** sends a new Basal rate. + +When used in combination with looping, this leads to under-delivery of basal insulin, as the algorithm updates the basal rate on the pump frequently. + +The issue is most apparent during the night. During daytime operation, SMBs often result in a basal rate of 0, which masks the effect. In observed usage, this results in approximately 10% of the expected Total Daily Dose (TDD) not being delivered over a 24-hour period. Additionally, glucose targets are often not reached overnight, particularly after meals with prolonged glucose impact (e.g. pasta). + +***NOTE:** This issue is especially important to understand for people on very small dosages of insulin, Children for example.* + +#### Enable Basal Drift Fix in AAPS + +You must be running AAPS Version 3.4.2.3 or later for this feature. + +The Basal Drift Fix is not enabled by default on AAPS. + +**To enable it:** + +1. Create an empty file named `omnipod_drift_compensation` (2) in the `extra` (1) subfolder of your phone [AAPS directory](#preferences-maintenance-settings). + + ![dash_drift_enable_file](../images/DASH_images/DASH_Drift/dash_drift_enable_file.png) + + ***NOTE:** Ensure you check in the AAPS settings where your AAPS Directory is, and that you placed the file in the correct one, a number of several have been caught out putting the file into the wrong folder.* + +2. Restart **AAPS**. This must be done for it to recognise the file is present and enable the drift compensation feature. +3. Please visit this [Github issue #4783](https://github.com/nightscout/AndroidAPS/issues/4783) and thumbs up the first post indicating you are using this feature, we need this data to help demonstrate the feature is widely used. Once there is significant community adoption the removal of the enable file will be possible, we appreciate your support here. ## Troubleshooting -(omnipod-dash-delivery-suspended)= +(omnipod-dash-troubleshooting)= This section covers common known issues and solutions for Omnipod DASH use with AAPS. There is also [General Troubleshooting](../GettingHelp/GeneralTroubleshooting.md) section in the documentation that should be reviewed as it covers relevant topics for some Pod issues too. @@ -497,6 +532,9 @@ This section covers common known issues and solutions for Omnipod DASH use with For known issues with Bluetooth connections, dropouts of pump/pods, or activation and connection issues [Bluetooth Troubleshooting](../GettingHelp/BluetoothTroubleshooting.md) --- + +(omnipod-dash-delivery-suspended)= + ### Delivery suspended - אין יותר כפתור של הפסקת הזרקה. If you want to "suspend" the pod, you can set a zero **TBR** for x minutes. diff --git a/docs/CROWDIN/he/images/DASH_images/DASH_Drift/dash_drift_enable_file.png b/docs/CROWDIN/he/images/DASH_images/DASH_Drift/dash_drift_enable_file.png new file mode 100644 index 000000000000..917f90c264b5 Binary files /dev/null and b/docs/CROWDIN/he/images/DASH_images/DASH_Drift/dash_drift_enable_file.png differ diff --git a/docs/CROWDIN/he/images/DASH_images/DASH_Drift/dash_drift_pod_mgmt.png b/docs/CROWDIN/he/images/DASH_images/DASH_Drift/dash_drift_pod_mgmt.png new file mode 100644 index 000000000000..5b9a8485a40b Binary files /dev/null and b/docs/CROWDIN/he/images/DASH_images/DASH_Drift/dash_drift_pod_mgmt.png differ diff --git a/docs/CROWDIN/he/images/DASH_images/DASH_Drift/dash_drift_pod_stats_end.png b/docs/CROWDIN/he/images/DASH_images/DASH_Drift/dash_drift_pod_stats_end.png new file mode 100644 index 000000000000..5b268b517df0 Binary files /dev/null and b/docs/CROWDIN/he/images/DASH_images/DASH_Drift/dash_drift_pod_stats_end.png differ diff --git a/docs/CROWDIN/he/images/DASH_images/DASH_Drift/dash_drift_pod_stats_start.png b/docs/CROWDIN/he/images/DASH_images/DASH_Drift/dash_drift_pod_stats_start.png new file mode 100644 index 000000000000..2863168f7b19 Binary files /dev/null and b/docs/CROWDIN/he/images/DASH_images/DASH_Drift/dash_drift_pod_stats_start.png differ diff --git a/docs/CROWDIN/he/images/DASH_images/DASH_Drift/dash_drift_tab_pod_mgmt.png b/docs/CROWDIN/he/images/DASH_images/DASH_Drift/dash_drift_tab_pod_mgmt.png new file mode 100644 index 000000000000..30a5edb90b1d Binary files /dev/null and b/docs/CROWDIN/he/images/DASH_images/DASH_Drift/dash_drift_tab_pod_mgmt.png differ diff --git a/docs/CROWDIN/he/images/DASH_images/DASH_Drift/dash_drift_tdd.png b/docs/CROWDIN/he/images/DASH_images/DASH_Drift/dash_drift_tdd.png new file mode 100644 index 000000000000..28b7685fa5bd Binary files /dev/null and b/docs/CROWDIN/he/images/DASH_images/DASH_Drift/dash_drift_tdd.png differ diff --git a/docs/CROWDIN/ko/CompatiblePumps/OmnipodDASH.md b/docs/CROWDIN/ko/CompatiblePumps/OmnipodDASH.md index 5e2eb6663bff..55bb1bc03602 100644 --- a/docs/CROWDIN/ko/CompatiblePumps/OmnipodDASH.md +++ b/docs/CROWDIN/ko/CompatiblePumps/OmnipodDASH.md @@ -19,8 +19,8 @@ These are the specifications of the **Omnipod DASH** ('DASH') and what different ## Omnipod DASH known AAPS constraints/issues - Android 16 requires **AAPS** version 3.3.2.1 or later. - General advice is to run **AAPS** on Android 14 or 16. Android 15 has many reported [issues](https://github.com/nightscout/AndroidAPS/issues/3471) from the community. However, if you do run on Android 15 you will likely need to enable Bluetooth Bonding to successfully activate and use Pods, see [General Troubleshooting](../GettingHelp/GeneralTroubleshooting.md) for more info on the Bonding settings. -- Too frequent basal updates may cause basal insulin delivery [problems](https://github.com/nightscout/AndroidAPS/issues/4158) with Omnipod Dash. When using **SMB**, limit the interval to 5 minutes minimum to avoid this issue. -- Dash only supports basal rate in 0.05 U/h steps. If you try to set basal with 0.01 steps in your **AAPS profile**, AAPS will not give a warning even though the pod will round up the rate into 0.05 steps. If you view POD MGMT/Pod History it will display that 0.05 basal was set. This also means the lowest basal rate allowed by the DASH in **AAPS** is 0.05U/h. +- Temporary Basal rate changes (which occur frequently when the loop is active, especially overnight) result in under-delivery of insulin. This is effectively a hardware limitation of the Omnipod DASH. The issue has been addressed in AAPS 3.4.2.3, but the functionality is currently opt-in. Follow the [Basal Drift Fix Instructions ](#omnipod-dash-Basal-drift-fix) instructions to enable it. For more information regarding the fix see [Github Issue - 4783](https://github.com/nightscout/AndroidAPS/issues/4783) for more info. +- Dash only supports basal rate in 0.05 U/h steps. If you try to set Basal with 0.01 steps in your **AAPS profile**, AAPS will not give a warning even though the pod will round up the rate into 0.05 steps. If you view POD MGMT/Pod History it will display that 0.05 basal was set. This also means the lowest basal rate allowed by the DASH in **AAPS** is 0.05U/h. - The activation status of a Pod is stored in the settings file, if you export a settings file with an active pod. Then change to a new pod, then restore the settings from your previous export you will have now restored the old pod activation and removed the new pod activation. This is why we recommend to export settings after each pod activation to allow a restore of that pods activation state if something happens to your rig. - When setting a new basal profile, DASH will suspend delivery before setting the new basal **Profile**. If there is a communication interruption or error, the basal profile won't automatically re-start. See section [Resuming Insulin Delivery](#omnipod-dash-resuming-insulin-delivery) for details. - If alerts are configured, and the pod is about to expire, the pod will keep beeping until alerts are silenced, see [Silencing Pod Alerts](#omnipod-dash-silencing-pod-alerts) for details. @@ -70,7 +70,7 @@ As long as **AAPS** is operational it will send basal rate adjustment commands t When for some reason the pod does not receive any new commands (for instance because communication was lost due to Pod ➜ phone distance) the pod will automatically fall back to default basal rates as defined in your [**Profile**](../SettingUpAaps/YourAapsProfile.md). ### **AAPS Profile(s) do not support 30 minute basal rate time frames** -If you are new to **AAPS** and are setting up your basal rate [**Profile**](../SettingUpAaps/YourAapsProfile.md) for the first time, please be aware that basal rates starting on a half-hour basis are not supported. For example, on your Omnipod PDM, if you have a basal rate of 1.1 units which starts at 09:30 and has a duration of 2 hours ending at 11:30, it is not possible replicate this exact basil **Profile** in **AAPS**. +If you are new to **AAPS** and are setting up your basal rate [**Profile**](../SettingUpAaps/YourAapsProfile.md) for the first time, please be aware that basal rates starting on a half-hour basis are not supported. For example, on your Omnipod PDM, if you have a basal rate of 1.1 units which starts at 09:30 and has a duration of 2 hours ending at 11:30, it is not possible replicate this exact Basal **Profile** in **AAPS**. You will need to change this 1.1 unit basal rate to a time range of either 9:00-11:00 or 10:00-12:00. Even though the DASH hardware itself supports the 30 minute basal rate **Profile** increments, **AAPS** does NOT support this feature. ### **0U/h Profile basal rates are NOT supported in AAPS** @@ -480,11 +480,46 @@ Additional note: * **SMS** - Returns value or 50+U for SMS responses * **Nightscout** - Uploads value of 50 when over 50 units to Nightscout (version 14.07 and older). Newer versions will report a value of 50+ when over 50 units. -(omnipod-dash-troubleshooting)= +(omnipod-dash-known-issues-workarounds)= + +## Known Issues Workarounds + +This section covers common workarounds and settings that need to be changed to enable a feature to work around a community reported issue that has a fix. E.g. the Basal drift enable process is documented here. + +(#omnipod-dash-Basal-drift-fix)= + +### Basal Drift Fix Instructions + +The Omnipod Dash pump has a limitation that can cause it to deliver less basal insulin than **AAPS** expects, see [Issue #4783](https://github.com/nightscout/AndroidAPS/issues/4783) for more technical details. + +The Dash uses an internal timer to determine when a basal pulse of 0.05 U is delivered. Once the timer interval elapses, the pulse is delivered. However, this timer is restarted whenever a basal rate change occurs e.g when **AAPS** sends a new Basal rate. + +When used in combination with looping, this leads to under-delivery of basal insulin, as the algorithm updates the basal rate on the pump frequently. + +The issue is most apparent during the night. During daytime operation, SMBs often result in a basal rate of 0, which masks the effect. In observed usage, this results in approximately 10% of the expected Total Daily Dose (TDD) not being delivered over a 24-hour period. Additionally, glucose targets are often not reached overnight, particularly after meals with prolonged glucose impact (e.g. pasta). + +***NOTE:** This issue is especially important to understand for people on very small dosages of insulin, Children for example.* + +#### Enable Basal Drift Fix in AAPS + +You must be running AAPS Version 3.4.2.3 or later for this feature. + +The Basal Drift Fix is not enabled by default on AAPS. + +**To enable it:** + +1. Create an empty file named `omnipod_drift_compensation` (2) in the `extra` (1) subfolder of your phone [AAPS directory](#preferences-maintenance-settings). + + ![dash_drift_enable_file](../images/DASH_images/DASH_Drift/dash_drift_enable_file.png) + + ***NOTE:** Ensure you check in the AAPS settings where your AAPS Directory is, and that you placed the file in the correct one, a number of several have been caught out putting the file into the wrong folder.* + +2. Restart **AAPS**. This must be done for it to recognise the file is present and enable the drift compensation feature. +3. Please visit this [Github issue #4783](https://github.com/nightscout/AndroidAPS/issues/4783) and thumbs up the first post indicating you are using this feature, we need this data to help demonstrate the feature is widely used. Once there is significant community adoption the removal of the enable file will be possible, we appreciate your support here. ## Troubleshooting -(omnipod-dash-delivery-suspended)= +(omnipod-dash-troubleshooting)= This section covers common known issues and solutions for Omnipod DASH use with AAPS. There is also [General Troubleshooting](../GettingHelp/GeneralTroubleshooting.md) section in the documentation that should be reviewed as it covers relevant topics for some Pod issues too. @@ -497,6 +532,9 @@ This section covers common known issues and solutions for Omnipod DASH use with For known issues with Bluetooth connections, dropouts of pump/pods, or activation and connection issues [Bluetooth Troubleshooting](../GettingHelp/BluetoothTroubleshooting.md) --- + +(omnipod-dash-delivery-suspended)= + ### Delivery suspended - There is no suspend button anymore. If you want to "suspend" the pod, you can set a zero **TBR** for x minutes. diff --git a/docs/CROWDIN/ko/images/DASH_images/DASH_Drift/dash_drift_enable_file.png b/docs/CROWDIN/ko/images/DASH_images/DASH_Drift/dash_drift_enable_file.png new file mode 100644 index 000000000000..917f90c264b5 Binary files /dev/null and b/docs/CROWDIN/ko/images/DASH_images/DASH_Drift/dash_drift_enable_file.png differ diff --git a/docs/CROWDIN/ko/images/DASH_images/DASH_Drift/dash_drift_pod_mgmt.png b/docs/CROWDIN/ko/images/DASH_images/DASH_Drift/dash_drift_pod_mgmt.png new file mode 100644 index 000000000000..5b9a8485a40b Binary files /dev/null and b/docs/CROWDIN/ko/images/DASH_images/DASH_Drift/dash_drift_pod_mgmt.png differ diff --git a/docs/CROWDIN/ko/images/DASH_images/DASH_Drift/dash_drift_pod_stats_end.png b/docs/CROWDIN/ko/images/DASH_images/DASH_Drift/dash_drift_pod_stats_end.png new file mode 100644 index 000000000000..5b268b517df0 Binary files /dev/null and b/docs/CROWDIN/ko/images/DASH_images/DASH_Drift/dash_drift_pod_stats_end.png differ diff --git a/docs/CROWDIN/ko/images/DASH_images/DASH_Drift/dash_drift_pod_stats_start.png b/docs/CROWDIN/ko/images/DASH_images/DASH_Drift/dash_drift_pod_stats_start.png new file mode 100644 index 000000000000..2863168f7b19 Binary files /dev/null and b/docs/CROWDIN/ko/images/DASH_images/DASH_Drift/dash_drift_pod_stats_start.png differ diff --git a/docs/CROWDIN/ko/images/DASH_images/DASH_Drift/dash_drift_tab_pod_mgmt.png b/docs/CROWDIN/ko/images/DASH_images/DASH_Drift/dash_drift_tab_pod_mgmt.png new file mode 100644 index 000000000000..30a5edb90b1d Binary files /dev/null and b/docs/CROWDIN/ko/images/DASH_images/DASH_Drift/dash_drift_tab_pod_mgmt.png differ diff --git a/docs/CROWDIN/ko/images/DASH_images/DASH_Drift/dash_drift_tdd.png b/docs/CROWDIN/ko/images/DASH_images/DASH_Drift/dash_drift_tdd.png new file mode 100644 index 000000000000..28b7685fa5bd Binary files /dev/null and b/docs/CROWDIN/ko/images/DASH_images/DASH_Drift/dash_drift_tdd.png differ diff --git a/docs/CROWDIN/lt/CompatiblePumps/OmnipodDASH.md b/docs/CROWDIN/lt/CompatiblePumps/OmnipodDASH.md index b39adeddf16a..c9f92a24f182 100644 --- a/docs/CROWDIN/lt/CompatiblePumps/OmnipodDASH.md +++ b/docs/CROWDIN/lt/CompatiblePumps/OmnipodDASH.md @@ -19,8 +19,8 @@ These are the specifications of the **Omnipod DASH** ('DASH') and what different ## Omnipod DASH known AAPS constraints/issues - Android 16 requires **AAPS** version 3.3.2.1 or later. - General advice is to run **AAPS** on Android 14 or 16. Android 15 has many reported [issues](https://github.com/nightscout/AndroidAPS/issues/3471) from the community. However, if you do run on Android 15 you will likely need to enable Bluetooth Bonding to successfully activate and use Pods, see [General Troubleshooting](../GettingHelp/GeneralTroubleshooting.md) for more info on the Bonding settings. -- Too frequent basal updates may cause basal insulin delivery [problems](https://github.com/nightscout/AndroidAPS/issues/4158) with Omnipod Dash. When using **SMB**, limit the interval to 5 minutes minimum to avoid this issue. -- Dash only supports basal rate in 0.05 U/h steps. If you try to set basal with 0.01 steps in your **AAPS profile**, AAPS will not give a warning even though the pod will round up the rate into 0.05 steps. If you view POD MGMT/Pod History it will display that 0.05 basal was set. This also means the lowest basal rate allowed by the DASH in **AAPS** is 0.05U/h. +- Temporary Basal rate changes (which occur frequently when the loop is active, especially overnight) result in under-delivery of insulin. This is effectively a hardware limitation of the Omnipod DASH. The issue has been addressed in AAPS 3.4.2.3, but the functionality is currently opt-in. Follow the [Basal Drift Fix Instructions ](#omnipod-dash-Basal-drift-fix) instructions to enable it. For more information regarding the fix see [Github Issue - 4783](https://github.com/nightscout/AndroidAPS/issues/4783) for more info. +- Dash only supports basal rate in 0.05 U/h steps. If you try to set Basal with 0.01 steps in your **AAPS profile**, AAPS will not give a warning even though the pod will round up the rate into 0.05 steps. If you view POD MGMT/Pod History it will display that 0.05 basal was set. This also means the lowest basal rate allowed by the DASH in **AAPS** is 0.05U/h. - The activation status of a Pod is stored in the settings file, if you export a settings file with an active pod. Then change to a new pod, then restore the settings from your previous export you will have now restored the old pod activation and removed the new pod activation. This is why we recommend to export settings after each pod activation to allow a restore of that pods activation state if something happens to your rig. - When setting a new basal profile, DASH will suspend delivery before setting the new basal **Profile**. If there is a communication interruption or error, the basal profile won't automatically re-start. See section [Resuming Insulin Delivery](#omnipod-dash-resuming-insulin-delivery) for details. - If alerts are configured, and the pod is about to expire, the pod will keep beeping until alerts are silenced, see [Silencing Pod Alerts](#omnipod-dash-silencing-pod-alerts) for details. @@ -70,7 +70,7 @@ As long as **AAPS** is operational it will send basal rate adjustment commands t When for some reason the pod does not receive any new commands (for instance because communication was lost due to Pod ➜ phone distance) the pod will automatically fall back to default basal rates as defined in your [**Profile**](../SettingUpAaps/YourAapsProfile.md). ### **AAPS Profile(s) do not support 30 minute basal rate time frames** -If you are new to **AAPS** and are setting up your basal rate [**Profile**](../SettingUpAaps/YourAapsProfile.md) for the first time, please be aware that basal rates starting on a half-hour basis are not supported. For example, on your Omnipod PDM, if you have a basal rate of 1.1 units which starts at 09:30 and has a duration of 2 hours ending at 11:30, it is not possible replicate this exact basil **Profile** in **AAPS**. +If you are new to **AAPS** and are setting up your basal rate [**Profile**](../SettingUpAaps/YourAapsProfile.md) for the first time, please be aware that basal rates starting on a half-hour basis are not supported. For example, on your Omnipod PDM, if you have a basal rate of 1.1 units which starts at 09:30 and has a duration of 2 hours ending at 11:30, it is not possible replicate this exact Basal **Profile** in **AAPS**. You will need to change this 1.1 unit basal rate to a time range of either 9:00-11:00 or 10:00-12:00. Even though the DASH hardware itself supports the 30 minute basal rate **Profile** increments, **AAPS** does NOT support this feature. ### **0U/h Profile basal rates are NOT supported in AAPS** @@ -480,11 +480,46 @@ Additional note: * **SMS** - Returns value or 50+U for SMS responses * **Nightscout** - Uploads value of 50 when over 50 units to Nightscout (version 14.07 and older). Newer versions will report a value of 50+ when over 50 units. -(omnipod-dash-troubleshooting)= +(omnipod-dash-known-issues-workarounds)= + +## Known Issues Workarounds + +This section covers common workarounds and settings that need to be changed to enable a feature to work around a community reported issue that has a fix. E.g. the Basal drift enable process is documented here. + +(#omnipod-dash-Basal-drift-fix)= + +### Basal Drift Fix Instructions + +The Omnipod Dash pump has a limitation that can cause it to deliver less basal insulin than **AAPS** expects, see [Issue #4783](https://github.com/nightscout/AndroidAPS/issues/4783) for more technical details. + +The Dash uses an internal timer to determine when a basal pulse of 0.05 U is delivered. Once the timer interval elapses, the pulse is delivered. However, this timer is restarted whenever a basal rate change occurs e.g when **AAPS** sends a new Basal rate. + +When used in combination with looping, this leads to under-delivery of basal insulin, as the algorithm updates the basal rate on the pump frequently. + +The issue is most apparent during the night. During daytime operation, SMBs often result in a basal rate of 0, which masks the effect. In observed usage, this results in approximately 10% of the expected Total Daily Dose (TDD) not being delivered over a 24-hour period. Additionally, glucose targets are often not reached overnight, particularly after meals with prolonged glucose impact (e.g. pasta). + +***NOTE:** This issue is especially important to understand for people on very small dosages of insulin, Children for example.* + +#### Enable Basal Drift Fix in AAPS + +You must be running AAPS Version 3.4.2.3 or later for this feature. + +The Basal Drift Fix is not enabled by default on AAPS. + +**To enable it:** + +1. Create an empty file named `omnipod_drift_compensation` (2) in the `extra` (1) subfolder of your phone [AAPS directory](#preferences-maintenance-settings). + + ![dash_drift_enable_file](../images/DASH_images/DASH_Drift/dash_drift_enable_file.png) + + ***NOTE:** Ensure you check in the AAPS settings where your AAPS Directory is, and that you placed the file in the correct one, a number of several have been caught out putting the file into the wrong folder.* + +2. Restart **AAPS**. This must be done for it to recognise the file is present and enable the drift compensation feature. +3. Please visit this [Github issue #4783](https://github.com/nightscout/AndroidAPS/issues/4783) and thumbs up the first post indicating you are using this feature, we need this data to help demonstrate the feature is widely used. Once there is significant community adoption the removal of the enable file will be possible, we appreciate your support here. ## Troubleshooting -(omnipod-dash-delivery-suspended)= +(omnipod-dash-troubleshooting)= This section covers common known issues and solutions for Omnipod DASH use with AAPS. There is also [General Troubleshooting](../GettingHelp/GeneralTroubleshooting.md) section in the documentation that should be reviewed as it covers relevant topics for some Pod issues too. @@ -497,6 +532,9 @@ This section covers common known issues and solutions for Omnipod DASH use with For known issues with Bluetooth connections, dropouts of pump/pods, or activation and connection issues [Bluetooth Troubleshooting](../GettingHelp/BluetoothTroubleshooting.md) --- + +(omnipod-dash-delivery-suspended)= + ### Delivery suspended - There is no suspend button anymore. If you want to "suspend" the pod, you can set a zero **TBR** for x minutes. diff --git a/docs/CROWDIN/lt/images/DASH_images/DASH_Drift/dash_drift_enable_file.png b/docs/CROWDIN/lt/images/DASH_images/DASH_Drift/dash_drift_enable_file.png new file mode 100644 index 000000000000..917f90c264b5 Binary files /dev/null and b/docs/CROWDIN/lt/images/DASH_images/DASH_Drift/dash_drift_enable_file.png differ diff --git a/docs/CROWDIN/lt/images/DASH_images/DASH_Drift/dash_drift_pod_mgmt.png b/docs/CROWDIN/lt/images/DASH_images/DASH_Drift/dash_drift_pod_mgmt.png new file mode 100644 index 000000000000..5b9a8485a40b Binary files /dev/null and b/docs/CROWDIN/lt/images/DASH_images/DASH_Drift/dash_drift_pod_mgmt.png differ diff --git a/docs/CROWDIN/lt/images/DASH_images/DASH_Drift/dash_drift_pod_stats_end.png b/docs/CROWDIN/lt/images/DASH_images/DASH_Drift/dash_drift_pod_stats_end.png new file mode 100644 index 000000000000..5b268b517df0 Binary files /dev/null and b/docs/CROWDIN/lt/images/DASH_images/DASH_Drift/dash_drift_pod_stats_end.png differ diff --git a/docs/CROWDIN/lt/images/DASH_images/DASH_Drift/dash_drift_pod_stats_start.png b/docs/CROWDIN/lt/images/DASH_images/DASH_Drift/dash_drift_pod_stats_start.png new file mode 100644 index 000000000000..2863168f7b19 Binary files /dev/null and b/docs/CROWDIN/lt/images/DASH_images/DASH_Drift/dash_drift_pod_stats_start.png differ diff --git a/docs/CROWDIN/lt/images/DASH_images/DASH_Drift/dash_drift_tab_pod_mgmt.png b/docs/CROWDIN/lt/images/DASH_images/DASH_Drift/dash_drift_tab_pod_mgmt.png new file mode 100644 index 000000000000..30a5edb90b1d Binary files /dev/null and b/docs/CROWDIN/lt/images/DASH_images/DASH_Drift/dash_drift_tab_pod_mgmt.png differ diff --git a/docs/CROWDIN/lt/images/DASH_images/DASH_Drift/dash_drift_tdd.png b/docs/CROWDIN/lt/images/DASH_images/DASH_Drift/dash_drift_tdd.png new file mode 100644 index 000000000000..28b7685fa5bd Binary files /dev/null and b/docs/CROWDIN/lt/images/DASH_images/DASH_Drift/dash_drift_tdd.png differ diff --git a/docs/CROWDIN/nl/CompatiblePumps/OmnipodDASH.md b/docs/CROWDIN/nl/CompatiblePumps/OmnipodDASH.md index bb44a438bac6..421cca63fdb9 100644 --- a/docs/CROWDIN/nl/CompatiblePumps/OmnipodDASH.md +++ b/docs/CROWDIN/nl/CompatiblePumps/OmnipodDASH.md @@ -19,8 +19,8 @@ These are the specifications of the **Omnipod DASH** ('DASH') and what different ## Omnipod DASH known AAPS constraints/issues - Android 16 requires **AAPS** version 3.3.2.1 or later. - General advice is to run **AAPS** on Android 14 or 16. Android 15 has many reported [issues](https://github.com/nightscout/AndroidAPS/issues/3471) from the community. However, if you do run on Android 15 you will likely need to enable Bluetooth Bonding to successfully activate and use Pods, see [General Troubleshooting](../GettingHelp/GeneralTroubleshooting.md) for more info on the Bonding settings. -- Too frequent basal updates may cause basal insulin delivery [problems](https://github.com/nightscout/AndroidAPS/issues/4158) with Omnipod Dash. When using **SMB**, limit the interval to 5 minutes minimum to avoid this issue. -- Dash only supports basal rate in 0.05 U/h steps. If you try to set basal with 0.01 steps in your **AAPS profile**, AAPS will not give a warning even though the pod will round up the rate into 0.05 steps. If you view POD MGMT/Pod History it will display that 0.05 basal was set. This also means the lowest basal rate allowed by the DASH in **AAPS** is 0.05U/h. +- Temporary Basal rate changes (which occur frequently when the loop is active, especially overnight) result in under-delivery of insulin. This is effectively a hardware limitation of the Omnipod DASH. The issue has been addressed in AAPS 3.4.2.3, but the functionality is currently opt-in. Follow the [Basal Drift Fix Instructions ](#omnipod-dash-Basal-drift-fix) instructions to enable it. For more information regarding the fix see [Github Issue - 4783](https://github.com/nightscout/AndroidAPS/issues/4783) for more info. +- Dash only supports basal rate in 0.05 U/h steps. If you try to set Basal with 0.01 steps in your **AAPS profile**, AAPS will not give a warning even though the pod will round up the rate into 0.05 steps. If you view POD MGMT/Pod History it will display that 0.05 basal was set. This also means the lowest basal rate allowed by the DASH in **AAPS** is 0.05U/h. - The activation status of a Pod is stored in the settings file, if you export a settings file with an active pod. Then change to a new pod, then restore the settings from your previous export you will have now restored the old pod activation and removed the new pod activation. This is why we recommend to export settings after each pod activation to allow a restore of that pods activation state if something happens to your rig. - When setting a new basal profile, DASH will suspend delivery before setting the new basal **Profile**. If there is a communication interruption or error, the basal profile won't automatically re-start. See section [Resuming Insulin Delivery](#omnipod-dash-resuming-insulin-delivery) for details. - If alerts are configured, and the pod is about to expire, the pod will keep beeping until alerts are silenced, see [Silencing Pod Alerts](#omnipod-dash-silencing-pod-alerts) for details. @@ -70,7 +70,7 @@ As long as **AAPS** is operational it will send basal rate adjustment commands t When for some reason the pod does not receive any new commands (for instance because communication was lost due to Pod ➜ phone distance) the pod will automatically fall back to default basal rates as defined in your [**Profile**](../SettingUpAaps/YourAapsProfile.md). ### **AAPS Profile(s) do not support 30 minute basal rate time frames** -If you are new to **AAPS** and are setting up your basal rate [**Profile**](../SettingUpAaps/YourAapsProfile.md) for the first time, please be aware that basal rates starting on a half-hour basis are not supported. For example, on your Omnipod PDM, if you have a basal rate of 1.1 units which starts at 09:30 and has a duration of 2 hours ending at 11:30, it is not possible replicate this exact basil **Profile** in **AAPS**. +If you are new to **AAPS** and are setting up your basal rate [**Profile**](../SettingUpAaps/YourAapsProfile.md) for the first time, please be aware that basal rates starting on a half-hour basis are not supported. For example, on your Omnipod PDM, if you have a basal rate of 1.1 units which starts at 09:30 and has a duration of 2 hours ending at 11:30, it is not possible replicate this exact Basal **Profile** in **AAPS**. You will need to change this 1.1 unit basal rate to a time range of either 9:00-11:00 or 10:00-12:00. Even though the DASH hardware itself supports the 30 minute basal rate **Profile** increments, **AAPS** does NOT support this feature. ### **0U/h Profile basal rates are NOT supported in AAPS** @@ -480,11 +480,46 @@ Additional note: * **SMS** - Returns value or 50+U for SMS responses * **Nightscout** - Uploads value of 50 when over 50 units to Nightscout (version 14.07 and older). Newer versions will report a value of 50+ when over 50 units. -(omnipod-dash-troubleshooting)= +(omnipod-dash-known-issues-workarounds)= + +## Known Issues Workarounds + +This section covers common workarounds and settings that need to be changed to enable a feature to work around a community reported issue that has a fix. E.g. the Basal drift enable process is documented here. + +(#omnipod-dash-Basal-drift-fix)= + +### Basal Drift Fix Instructions + +The Omnipod Dash pump has a limitation that can cause it to deliver less basal insulin than **AAPS** expects, see [Issue #4783](https://github.com/nightscout/AndroidAPS/issues/4783) for more technical details. + +The Dash uses an internal timer to determine when a basal pulse of 0.05 U is delivered. Once the timer interval elapses, the pulse is delivered. However, this timer is restarted whenever a basal rate change occurs e.g when **AAPS** sends a new Basal rate. + +When used in combination with looping, this leads to under-delivery of basal insulin, as the algorithm updates the basal rate on the pump frequently. + +The issue is most apparent during the night. During daytime operation, SMBs often result in a basal rate of 0, which masks the effect. In observed usage, this results in approximately 10% of the expected Total Daily Dose (TDD) not being delivered over a 24-hour period. Additionally, glucose targets are often not reached overnight, particularly after meals with prolonged glucose impact (e.g. pasta). + +***NOTE:** This issue is especially important to understand for people on very small dosages of insulin, Children for example.* + +#### Enable Basal Drift Fix in AAPS + +You must be running AAPS Version 3.4.2.3 or later for this feature. + +The Basal Drift Fix is not enabled by default on AAPS. + +**To enable it:** + +1. Create an empty file named `omnipod_drift_compensation` (2) in the `extra` (1) subfolder of your phone [AAPS directory](#preferences-maintenance-settings). + + ![dash_drift_enable_file](../images/DASH_images/DASH_Drift/dash_drift_enable_file.png) + + ***NOTE:** Ensure you check in the AAPS settings where your AAPS Directory is, and that you placed the file in the correct one, a number of several have been caught out putting the file into the wrong folder.* + +2. Restart **AAPS**. This must be done for it to recognise the file is present and enable the drift compensation feature. +3. Please visit this [Github issue #4783](https://github.com/nightscout/AndroidAPS/issues/4783) and thumbs up the first post indicating you are using this feature, we need this data to help demonstrate the feature is widely used. Once there is significant community adoption the removal of the enable file will be possible, we appreciate your support here. ## Troubleshooting -(omnipod-dash-delivery-suspended)= +(omnipod-dash-troubleshooting)= This section covers common known issues and solutions for Omnipod DASH use with AAPS. There is also [General Troubleshooting](../GettingHelp/GeneralTroubleshooting.md) section in the documentation that should be reviewed as it covers relevant topics for some Pod issues too. @@ -497,6 +532,9 @@ This section covers common known issues and solutions for Omnipod DASH use with For known issues with Bluetooth connections, dropouts of pump/pods, or activation and connection issues [Bluetooth Troubleshooting](../GettingHelp/BluetoothTroubleshooting.md) --- + +(omnipod-dash-delivery-suspended)= + ### Delivery suspended - There is no suspend button anymore. If you want to "suspend" the pod, you can set a zero **TBR** for x minutes. diff --git a/docs/CROWDIN/nl/images/DASH_images/DASH_Drift/dash_drift_enable_file.png b/docs/CROWDIN/nl/images/DASH_images/DASH_Drift/dash_drift_enable_file.png new file mode 100644 index 000000000000..917f90c264b5 Binary files /dev/null and b/docs/CROWDIN/nl/images/DASH_images/DASH_Drift/dash_drift_enable_file.png differ diff --git a/docs/CROWDIN/nl/images/DASH_images/DASH_Drift/dash_drift_pod_mgmt.png b/docs/CROWDIN/nl/images/DASH_images/DASH_Drift/dash_drift_pod_mgmt.png new file mode 100644 index 000000000000..5b9a8485a40b Binary files /dev/null and b/docs/CROWDIN/nl/images/DASH_images/DASH_Drift/dash_drift_pod_mgmt.png differ diff --git a/docs/CROWDIN/nl/images/DASH_images/DASH_Drift/dash_drift_pod_stats_end.png b/docs/CROWDIN/nl/images/DASH_images/DASH_Drift/dash_drift_pod_stats_end.png new file mode 100644 index 000000000000..5b268b517df0 Binary files /dev/null and b/docs/CROWDIN/nl/images/DASH_images/DASH_Drift/dash_drift_pod_stats_end.png differ diff --git a/docs/CROWDIN/nl/images/DASH_images/DASH_Drift/dash_drift_pod_stats_start.png b/docs/CROWDIN/nl/images/DASH_images/DASH_Drift/dash_drift_pod_stats_start.png new file mode 100644 index 000000000000..2863168f7b19 Binary files /dev/null and b/docs/CROWDIN/nl/images/DASH_images/DASH_Drift/dash_drift_pod_stats_start.png differ diff --git a/docs/CROWDIN/nl/images/DASH_images/DASH_Drift/dash_drift_tab_pod_mgmt.png b/docs/CROWDIN/nl/images/DASH_images/DASH_Drift/dash_drift_tab_pod_mgmt.png new file mode 100644 index 000000000000..30a5edb90b1d Binary files /dev/null and b/docs/CROWDIN/nl/images/DASH_images/DASH_Drift/dash_drift_tab_pod_mgmt.png differ diff --git a/docs/CROWDIN/nl/images/DASH_images/DASH_Drift/dash_drift_tdd.png b/docs/CROWDIN/nl/images/DASH_images/DASH_Drift/dash_drift_tdd.png new file mode 100644 index 000000000000..28b7685fa5bd Binary files /dev/null and b/docs/CROWDIN/nl/images/DASH_images/DASH_Drift/dash_drift_tdd.png differ diff --git a/docs/CROWDIN/pb/CompatiblePumps/OmnipodDASH.md b/docs/CROWDIN/pb/CompatiblePumps/OmnipodDASH.md index 97460feac0b7..5e89ea63bdc1 100644 --- a/docs/CROWDIN/pb/CompatiblePumps/OmnipodDASH.md +++ b/docs/CROWDIN/pb/CompatiblePumps/OmnipodDASH.md @@ -19,8 +19,8 @@ These are the specifications of the **Omnipod DASH** ('DASH') and what different ## Omnipod DASH known AAPS constraints/issues - Android 16 requires **AAPS** version 3.3.2.1 or later. - General advice is to run **AAPS** on Android 14 or 16. Android 15 has many reported [issues](https://github.com/nightscout/AndroidAPS/issues/3471) from the community. However, if you do run on Android 15 you will likely need to enable Bluetooth Bonding to successfully activate and use Pods, see [General Troubleshooting](../GettingHelp/GeneralTroubleshooting.md) for more info on the Bonding settings. -- Too frequent basal updates may cause basal insulin delivery [problems](https://github.com/nightscout/AndroidAPS/issues/4158) with Omnipod Dash. When using **SMB**, limit the interval to 5 minutes minimum to avoid this issue. -- Dash only supports basal rate in 0.05 U/h steps. If you try to set basal with 0.01 steps in your **AAPS profile**, AAPS will not give a warning even though the pod will round up the rate into 0.05 steps. If you view POD MGMT/Pod History it will display that 0.05 basal was set. This also means the lowest basal rate allowed by the DASH in **AAPS** is 0.05U/h. +- Temporary Basal rate changes (which occur frequently when the loop is active, especially overnight) result in under-delivery of insulin. This is effectively a hardware limitation of the Omnipod DASH. The issue has been addressed in AAPS 3.4.2.3, but the functionality is currently opt-in. Follow the [Basal Drift Fix Instructions ](#omnipod-dash-Basal-drift-fix) instructions to enable it. For more information regarding the fix see [Github Issue - 4783](https://github.com/nightscout/AndroidAPS/issues/4783) for more info. +- Dash only supports basal rate in 0.05 U/h steps. If you try to set Basal with 0.01 steps in your **AAPS profile**, AAPS will not give a warning even though the pod will round up the rate into 0.05 steps. If you view POD MGMT/Pod History it will display that 0.05 basal was set. This also means the lowest basal rate allowed by the DASH in **AAPS** is 0.05U/h. - The activation status of a Pod is stored in the settings file, if you export a settings file with an active pod. Then change to a new pod, then restore the settings from your previous export you will have now restored the old pod activation and removed the new pod activation. This is why we recommend to export settings after each pod activation to allow a restore of that pods activation state if something happens to your rig. - When setting a new basal profile, DASH will suspend delivery before setting the new basal **Profile**. If there is a communication interruption or error, the basal profile won't automatically re-start. See section [Resuming Insulin Delivery](#omnipod-dash-resuming-insulin-delivery) for details. - If alerts are configured, and the pod is about to expire, the pod will keep beeping until alerts are silenced, see [Silencing Pod Alerts](#omnipod-dash-silencing-pod-alerts) for details. @@ -70,7 +70,7 @@ As long as **AAPS** is operational it will send basal rate adjustment commands t When for some reason the pod does not receive any new commands (for instance because communication was lost due to Pod ➜ phone distance) the pod will automatically fall back to default basal rates as defined in your [**Profile**](../SettingUpAaps/YourAapsProfile.md). ### **AAPS Profile(s) do not support 30 minute basal rate time frames** -If you are new to **AAPS** and are setting up your basal rate [**Profile**](../SettingUpAaps/YourAapsProfile.md) for the first time, please be aware that basal rates starting on a half-hour basis are not supported. For example, on your Omnipod PDM, if you have a basal rate of 1.1 units which starts at 09:30 and has a duration of 2 hours ending at 11:30, it is not possible replicate this exact basil **Profile** in **AAPS**. +If you are new to **AAPS** and are setting up your basal rate [**Profile**](../SettingUpAaps/YourAapsProfile.md) for the first time, please be aware that basal rates starting on a half-hour basis are not supported. For example, on your Omnipod PDM, if you have a basal rate of 1.1 units which starts at 09:30 and has a duration of 2 hours ending at 11:30, it is not possible replicate this exact Basal **Profile** in **AAPS**. You will need to change this 1.1 unit basal rate to a time range of either 9:00-11:00 or 10:00-12:00. Even though the DASH hardware itself supports the 30 minute basal rate **Profile** increments, **AAPS** does NOT support this feature. ### **0U/h Profile basal rates are NOT supported in AAPS** @@ -480,11 +480,46 @@ Additional note: * **SMS** - Returns value or 50+U for SMS responses * **Nightscout** - Uploads value of 50 when over 50 units to Nightscout (version 14.07 and older). Newer versions will report a value of 50+ when over 50 units. -(omnipod-dash-troubleshooting)= +(omnipod-dash-known-issues-workarounds)= + +## Known Issues Workarounds + +This section covers common workarounds and settings that need to be changed to enable a feature to work around a community reported issue that has a fix. E.g. the Basal drift enable process is documented here. + +(#omnipod-dash-Basal-drift-fix)= + +### Basal Drift Fix Instructions + +The Omnipod Dash pump has a limitation that can cause it to deliver less basal insulin than **AAPS** expects, see [Issue #4783](https://github.com/nightscout/AndroidAPS/issues/4783) for more technical details. + +The Dash uses an internal timer to determine when a basal pulse of 0.05 U is delivered. Once the timer interval elapses, the pulse is delivered. However, this timer is restarted whenever a basal rate change occurs e.g when **AAPS** sends a new Basal rate. + +When used in combination with looping, this leads to under-delivery of basal insulin, as the algorithm updates the basal rate on the pump frequently. + +The issue is most apparent during the night. During daytime operation, SMBs often result in a basal rate of 0, which masks the effect. In observed usage, this results in approximately 10% of the expected Total Daily Dose (TDD) not being delivered over a 24-hour period. Additionally, glucose targets are often not reached overnight, particularly after meals with prolonged glucose impact (e.g. pasta). + +***NOTE:** This issue is especially important to understand for people on very small dosages of insulin, Children for example.* + +#### Enable Basal Drift Fix in AAPS + +You must be running AAPS Version 3.4.2.3 or later for this feature. + +The Basal Drift Fix is not enabled by default on AAPS. + +**To enable it:** + +1. Create an empty file named `omnipod_drift_compensation` (2) in the `extra` (1) subfolder of your phone [AAPS directory](#preferences-maintenance-settings). + + ![dash_drift_enable_file](../images/DASH_images/DASH_Drift/dash_drift_enable_file.png) + + ***NOTE:** Ensure you check in the AAPS settings where your AAPS Directory is, and that you placed the file in the correct one, a number of several have been caught out putting the file into the wrong folder.* + +2. Restart **AAPS**. This must be done for it to recognise the file is present and enable the drift compensation feature. +3. Please visit this [Github issue #4783](https://github.com/nightscout/AndroidAPS/issues/4783) and thumbs up the first post indicating you are using this feature, we need this data to help demonstrate the feature is widely used. Once there is significant community adoption the removal of the enable file will be possible, we appreciate your support here. ## Troubleshooting -(omnipod-dash-delivery-suspended)= +(omnipod-dash-troubleshooting)= This section covers common known issues and solutions for Omnipod DASH use with AAPS. There is also [General Troubleshooting](../GettingHelp/GeneralTroubleshooting.md) section in the documentation that should be reviewed as it covers relevant topics for some Pod issues too. @@ -497,6 +532,9 @@ This section covers common known issues and solutions for Omnipod DASH use with For known issues with Bluetooth connections, dropouts of pump/pods, or activation and connection issues [Bluetooth Troubleshooting](../GettingHelp/BluetoothTroubleshooting.md) --- + +(omnipod-dash-delivery-suspended)= + ### Delivery suspended - There is no suspend button anymore. If you want to "suspend" the pod, you can set a zero **TBR** for x minutes. diff --git a/docs/CROWDIN/pb/images/DASH_images/DASH_Drift/dash_drift_enable_file.png b/docs/CROWDIN/pb/images/DASH_images/DASH_Drift/dash_drift_enable_file.png new file mode 100644 index 000000000000..917f90c264b5 Binary files /dev/null and b/docs/CROWDIN/pb/images/DASH_images/DASH_Drift/dash_drift_enable_file.png differ diff --git a/docs/CROWDIN/pb/images/DASH_images/DASH_Drift/dash_drift_pod_mgmt.png b/docs/CROWDIN/pb/images/DASH_images/DASH_Drift/dash_drift_pod_mgmt.png new file mode 100644 index 000000000000..5b9a8485a40b Binary files /dev/null and b/docs/CROWDIN/pb/images/DASH_images/DASH_Drift/dash_drift_pod_mgmt.png differ diff --git a/docs/CROWDIN/pb/images/DASH_images/DASH_Drift/dash_drift_pod_stats_end.png b/docs/CROWDIN/pb/images/DASH_images/DASH_Drift/dash_drift_pod_stats_end.png new file mode 100644 index 000000000000..5b268b517df0 Binary files /dev/null and b/docs/CROWDIN/pb/images/DASH_images/DASH_Drift/dash_drift_pod_stats_end.png differ diff --git a/docs/CROWDIN/pb/images/DASH_images/DASH_Drift/dash_drift_pod_stats_start.png b/docs/CROWDIN/pb/images/DASH_images/DASH_Drift/dash_drift_pod_stats_start.png new file mode 100644 index 000000000000..2863168f7b19 Binary files /dev/null and b/docs/CROWDIN/pb/images/DASH_images/DASH_Drift/dash_drift_pod_stats_start.png differ diff --git a/docs/CROWDIN/pb/images/DASH_images/DASH_Drift/dash_drift_tab_pod_mgmt.png b/docs/CROWDIN/pb/images/DASH_images/DASH_Drift/dash_drift_tab_pod_mgmt.png new file mode 100644 index 000000000000..30a5edb90b1d Binary files /dev/null and b/docs/CROWDIN/pb/images/DASH_images/DASH_Drift/dash_drift_tab_pod_mgmt.png differ diff --git a/docs/CROWDIN/pb/images/DASH_images/DASH_Drift/dash_drift_tdd.png b/docs/CROWDIN/pb/images/DASH_images/DASH_Drift/dash_drift_tdd.png new file mode 100644 index 000000000000..28b7685fa5bd Binary files /dev/null and b/docs/CROWDIN/pb/images/DASH_images/DASH_Drift/dash_drift_tdd.png differ diff --git a/docs/CROWDIN/pl/CompatiblePumps/OmnipodDASH.md b/docs/CROWDIN/pl/CompatiblePumps/OmnipodDASH.md index cbb861d809c9..3c255d534ffa 100644 --- a/docs/CROWDIN/pl/CompatiblePumps/OmnipodDASH.md +++ b/docs/CROWDIN/pl/CompatiblePumps/OmnipodDASH.md @@ -19,8 +19,8 @@ These are the specifications of the **Omnipod DASH** ('DASH') and what different ## Omnipod DASH known AAPS constraints/issues - Android 16 requires **AAPS** version 3.3.2.1 or later. - General advice is to run **AAPS** on Android 14 or 16. Android 15 has many reported [issues](https://github.com/nightscout/AndroidAPS/issues/3471) from the community. However, if you do run on Android 15 you will likely need to enable Bluetooth Bonding to successfully activate and use Pods, see [General Troubleshooting](../GettingHelp/GeneralTroubleshooting.md) for more info on the Bonding settings. -- Too frequent basal updates may cause basal insulin delivery [problems](https://github.com/nightscout/AndroidAPS/issues/4158) with Omnipod Dash. When using **SMB**, limit the interval to 5 minutes minimum to avoid this issue. -- Dash only supports basal rate in 0.05 U/h steps. If you try to set basal with 0.01 steps in your **AAPS profile**, AAPS will not give a warning even though the pod will round up the rate into 0.05 steps. If you view POD MGMT/Pod History it will display that 0.05 basal was set. This also means the lowest basal rate allowed by the DASH in **AAPS** is 0.05U/h. +- Temporary Basal rate changes (which occur frequently when the loop is active, especially overnight) result in under-delivery of insulin. This is effectively a hardware limitation of the Omnipod DASH. The issue has been addressed in AAPS 3.4.2.3, but the functionality is currently opt-in. Follow the [Basal Drift Fix Instructions ](#omnipod-dash-Basal-drift-fix) instructions to enable it. For more information regarding the fix see [Github Issue - 4783](https://github.com/nightscout/AndroidAPS/issues/4783) for more info. +- Dash only supports basal rate in 0.05 U/h steps. If you try to set Basal with 0.01 steps in your **AAPS profile**, AAPS will not give a warning even though the pod will round up the rate into 0.05 steps. If you view POD MGMT/Pod History it will display that 0.05 basal was set. This also means the lowest basal rate allowed by the DASH in **AAPS** is 0.05U/h. - The activation status of a Pod is stored in the settings file, if you export a settings file with an active pod. Then change to a new pod, then restore the settings from your previous export you will have now restored the old pod activation and removed the new pod activation. This is why we recommend to export settings after each pod activation to allow a restore of that pods activation state if something happens to your rig. - When setting a new basal profile, DASH will suspend delivery before setting the new basal **Profile**. If there is a communication interruption or error, the basal profile won't automatically re-start. See section [Resuming Insulin Delivery](#omnipod-dash-resuming-insulin-delivery) for details. - If alerts are configured, and the pod is about to expire, the pod will keep beeping until alerts are silenced, see [Silencing Pod Alerts](#omnipod-dash-silencing-pod-alerts) for details. @@ -70,7 +70,7 @@ As long as **AAPS** is operational it will send basal rate adjustment commands t When for some reason the pod does not receive any new commands (for instance because communication was lost due to Pod ➜ phone distance) the pod will automatically fall back to default basal rates as defined in your [**Profile**](../SettingUpAaps/YourAapsProfile.md). ### **AAPS Profile(s) do not support 30 minute basal rate time frames** -If you are new to **AAPS** and are setting up your basal rate [**Profile**](../SettingUpAaps/YourAapsProfile.md) for the first time, please be aware that basal rates starting on a half-hour basis are not supported. For example, on your Omnipod PDM, if you have a basal rate of 1.1 units which starts at 09:30 and has a duration of 2 hours ending at 11:30, it is not possible replicate this exact basil **Profile** in **AAPS**. +If you are new to **AAPS** and are setting up your basal rate [**Profile**](../SettingUpAaps/YourAapsProfile.md) for the first time, please be aware that basal rates starting on a half-hour basis are not supported. For example, on your Omnipod PDM, if you have a basal rate of 1.1 units which starts at 09:30 and has a duration of 2 hours ending at 11:30, it is not possible replicate this exact Basal **Profile** in **AAPS**. You will need to change this 1.1 unit basal rate to a time range of either 9:00-11:00 or 10:00-12:00. Even though the DASH hardware itself supports the 30 minute basal rate **Profile** increments, **AAPS** does NOT support this feature. ### **0U/h Profile basal rates are NOT supported in AAPS** @@ -480,11 +480,46 @@ Additional note: * **SMS** - Returns value or 50+U for SMS responses * **Nightscout** - Uploads value of 50 when over 50 units to Nightscout (version 14.07 and older). Newer versions will report a value of 50+ when over 50 units. -(omnipod-dash-troubleshooting)= +(omnipod-dash-known-issues-workarounds)= + +## Known Issues Workarounds + +This section covers common workarounds and settings that need to be changed to enable a feature to work around a community reported issue that has a fix. E.g. the Basal drift enable process is documented here. + +(#omnipod-dash-Basal-drift-fix)= + +### Basal Drift Fix Instructions + +The Omnipod Dash pump has a limitation that can cause it to deliver less basal insulin than **AAPS** expects, see [Issue #4783](https://github.com/nightscout/AndroidAPS/issues/4783) for more technical details. + +The Dash uses an internal timer to determine when a basal pulse of 0.05 U is delivered. Once the timer interval elapses, the pulse is delivered. However, this timer is restarted whenever a basal rate change occurs e.g when **AAPS** sends a new Basal rate. + +When used in combination with looping, this leads to under-delivery of basal insulin, as the algorithm updates the basal rate on the pump frequently. + +The issue is most apparent during the night. During daytime operation, SMBs often result in a basal rate of 0, which masks the effect. In observed usage, this results in approximately 10% of the expected Total Daily Dose (TDD) not being delivered over a 24-hour period. Additionally, glucose targets are often not reached overnight, particularly after meals with prolonged glucose impact (e.g. pasta). + +***NOTE:** This issue is especially important to understand for people on very small dosages of insulin, Children for example.* + +#### Enable Basal Drift Fix in AAPS + +You must be running AAPS Version 3.4.2.3 or later for this feature. + +The Basal Drift Fix is not enabled by default on AAPS. + +**To enable it:** + +1. Create an empty file named `omnipod_drift_compensation` (2) in the `extra` (1) subfolder of your phone [AAPS directory](#preferences-maintenance-settings). + + ![dash_drift_enable_file](../images/DASH_images/DASH_Drift/dash_drift_enable_file.png) + + ***NOTE:** Ensure you check in the AAPS settings where your AAPS Directory is, and that you placed the file in the correct one, a number of several have been caught out putting the file into the wrong folder.* + +2. Restart **AAPS**. This must be done for it to recognise the file is present and enable the drift compensation feature. +3. Please visit this [Github issue #4783](https://github.com/nightscout/AndroidAPS/issues/4783) and thumbs up the first post indicating you are using this feature, we need this data to help demonstrate the feature is widely used. Once there is significant community adoption the removal of the enable file will be possible, we appreciate your support here. ## Troubleshooting -(omnipod-dash-delivery-suspended)= +(omnipod-dash-troubleshooting)= This section covers common known issues and solutions for Omnipod DASH use with AAPS. There is also [General Troubleshooting](../GettingHelp/GeneralTroubleshooting.md) section in the documentation that should be reviewed as it covers relevant topics for some Pod issues too. @@ -497,6 +532,9 @@ This section covers common known issues and solutions for Omnipod DASH use with For known issues with Bluetooth connections, dropouts of pump/pods, or activation and connection issues [Bluetooth Troubleshooting](../GettingHelp/BluetoothTroubleshooting.md) --- + +(omnipod-dash-delivery-suspended)= + ### Delivery suspended - There is no suspend button anymore. If you want to "suspend" the pod, you can set a zero **TBR** for x minutes. diff --git a/docs/CROWDIN/pl/images/DASH_images/DASH_Drift/dash_drift_enable_file.png b/docs/CROWDIN/pl/images/DASH_images/DASH_Drift/dash_drift_enable_file.png new file mode 100644 index 000000000000..917f90c264b5 Binary files /dev/null and b/docs/CROWDIN/pl/images/DASH_images/DASH_Drift/dash_drift_enable_file.png differ diff --git a/docs/CROWDIN/pl/images/DASH_images/DASH_Drift/dash_drift_pod_mgmt.png b/docs/CROWDIN/pl/images/DASH_images/DASH_Drift/dash_drift_pod_mgmt.png new file mode 100644 index 000000000000..5b9a8485a40b Binary files /dev/null and b/docs/CROWDIN/pl/images/DASH_images/DASH_Drift/dash_drift_pod_mgmt.png differ diff --git a/docs/CROWDIN/pl/images/DASH_images/DASH_Drift/dash_drift_pod_stats_end.png b/docs/CROWDIN/pl/images/DASH_images/DASH_Drift/dash_drift_pod_stats_end.png new file mode 100644 index 000000000000..5b268b517df0 Binary files /dev/null and b/docs/CROWDIN/pl/images/DASH_images/DASH_Drift/dash_drift_pod_stats_end.png differ diff --git a/docs/CROWDIN/pl/images/DASH_images/DASH_Drift/dash_drift_pod_stats_start.png b/docs/CROWDIN/pl/images/DASH_images/DASH_Drift/dash_drift_pod_stats_start.png new file mode 100644 index 000000000000..2863168f7b19 Binary files /dev/null and b/docs/CROWDIN/pl/images/DASH_images/DASH_Drift/dash_drift_pod_stats_start.png differ diff --git a/docs/CROWDIN/pl/images/DASH_images/DASH_Drift/dash_drift_tab_pod_mgmt.png b/docs/CROWDIN/pl/images/DASH_images/DASH_Drift/dash_drift_tab_pod_mgmt.png new file mode 100644 index 000000000000..30a5edb90b1d Binary files /dev/null and b/docs/CROWDIN/pl/images/DASH_images/DASH_Drift/dash_drift_tab_pod_mgmt.png differ diff --git a/docs/CROWDIN/pl/images/DASH_images/DASH_Drift/dash_drift_tdd.png b/docs/CROWDIN/pl/images/DASH_images/DASH_Drift/dash_drift_tdd.png new file mode 100644 index 000000000000..28b7685fa5bd Binary files /dev/null and b/docs/CROWDIN/pl/images/DASH_images/DASH_Drift/dash_drift_tdd.png differ diff --git a/docs/CROWDIN/pt/CompatiblePumps/OmnipodDASH.md b/docs/CROWDIN/pt/CompatiblePumps/OmnipodDASH.md index cbb861d809c9..3c255d534ffa 100644 --- a/docs/CROWDIN/pt/CompatiblePumps/OmnipodDASH.md +++ b/docs/CROWDIN/pt/CompatiblePumps/OmnipodDASH.md @@ -19,8 +19,8 @@ These are the specifications of the **Omnipod DASH** ('DASH') and what different ## Omnipod DASH known AAPS constraints/issues - Android 16 requires **AAPS** version 3.3.2.1 or later. - General advice is to run **AAPS** on Android 14 or 16. Android 15 has many reported [issues](https://github.com/nightscout/AndroidAPS/issues/3471) from the community. However, if you do run on Android 15 you will likely need to enable Bluetooth Bonding to successfully activate and use Pods, see [General Troubleshooting](../GettingHelp/GeneralTroubleshooting.md) for more info on the Bonding settings. -- Too frequent basal updates may cause basal insulin delivery [problems](https://github.com/nightscout/AndroidAPS/issues/4158) with Omnipod Dash. When using **SMB**, limit the interval to 5 minutes minimum to avoid this issue. -- Dash only supports basal rate in 0.05 U/h steps. If you try to set basal with 0.01 steps in your **AAPS profile**, AAPS will not give a warning even though the pod will round up the rate into 0.05 steps. If you view POD MGMT/Pod History it will display that 0.05 basal was set. This also means the lowest basal rate allowed by the DASH in **AAPS** is 0.05U/h. +- Temporary Basal rate changes (which occur frequently when the loop is active, especially overnight) result in under-delivery of insulin. This is effectively a hardware limitation of the Omnipod DASH. The issue has been addressed in AAPS 3.4.2.3, but the functionality is currently opt-in. Follow the [Basal Drift Fix Instructions ](#omnipod-dash-Basal-drift-fix) instructions to enable it. For more information regarding the fix see [Github Issue - 4783](https://github.com/nightscout/AndroidAPS/issues/4783) for more info. +- Dash only supports basal rate in 0.05 U/h steps. If you try to set Basal with 0.01 steps in your **AAPS profile**, AAPS will not give a warning even though the pod will round up the rate into 0.05 steps. If you view POD MGMT/Pod History it will display that 0.05 basal was set. This also means the lowest basal rate allowed by the DASH in **AAPS** is 0.05U/h. - The activation status of a Pod is stored in the settings file, if you export a settings file with an active pod. Then change to a new pod, then restore the settings from your previous export you will have now restored the old pod activation and removed the new pod activation. This is why we recommend to export settings after each pod activation to allow a restore of that pods activation state if something happens to your rig. - When setting a new basal profile, DASH will suspend delivery before setting the new basal **Profile**. If there is a communication interruption or error, the basal profile won't automatically re-start. See section [Resuming Insulin Delivery](#omnipod-dash-resuming-insulin-delivery) for details. - If alerts are configured, and the pod is about to expire, the pod will keep beeping until alerts are silenced, see [Silencing Pod Alerts](#omnipod-dash-silencing-pod-alerts) for details. @@ -70,7 +70,7 @@ As long as **AAPS** is operational it will send basal rate adjustment commands t When for some reason the pod does not receive any new commands (for instance because communication was lost due to Pod ➜ phone distance) the pod will automatically fall back to default basal rates as defined in your [**Profile**](../SettingUpAaps/YourAapsProfile.md). ### **AAPS Profile(s) do not support 30 minute basal rate time frames** -If you are new to **AAPS** and are setting up your basal rate [**Profile**](../SettingUpAaps/YourAapsProfile.md) for the first time, please be aware that basal rates starting on a half-hour basis are not supported. For example, on your Omnipod PDM, if you have a basal rate of 1.1 units which starts at 09:30 and has a duration of 2 hours ending at 11:30, it is not possible replicate this exact basil **Profile** in **AAPS**. +If you are new to **AAPS** and are setting up your basal rate [**Profile**](../SettingUpAaps/YourAapsProfile.md) for the first time, please be aware that basal rates starting on a half-hour basis are not supported. For example, on your Omnipod PDM, if you have a basal rate of 1.1 units which starts at 09:30 and has a duration of 2 hours ending at 11:30, it is not possible replicate this exact Basal **Profile** in **AAPS**. You will need to change this 1.1 unit basal rate to a time range of either 9:00-11:00 or 10:00-12:00. Even though the DASH hardware itself supports the 30 minute basal rate **Profile** increments, **AAPS** does NOT support this feature. ### **0U/h Profile basal rates are NOT supported in AAPS** @@ -480,11 +480,46 @@ Additional note: * **SMS** - Returns value or 50+U for SMS responses * **Nightscout** - Uploads value of 50 when over 50 units to Nightscout (version 14.07 and older). Newer versions will report a value of 50+ when over 50 units. -(omnipod-dash-troubleshooting)= +(omnipod-dash-known-issues-workarounds)= + +## Known Issues Workarounds + +This section covers common workarounds and settings that need to be changed to enable a feature to work around a community reported issue that has a fix. E.g. the Basal drift enable process is documented here. + +(#omnipod-dash-Basal-drift-fix)= + +### Basal Drift Fix Instructions + +The Omnipod Dash pump has a limitation that can cause it to deliver less basal insulin than **AAPS** expects, see [Issue #4783](https://github.com/nightscout/AndroidAPS/issues/4783) for more technical details. + +The Dash uses an internal timer to determine when a basal pulse of 0.05 U is delivered. Once the timer interval elapses, the pulse is delivered. However, this timer is restarted whenever a basal rate change occurs e.g when **AAPS** sends a new Basal rate. + +When used in combination with looping, this leads to under-delivery of basal insulin, as the algorithm updates the basal rate on the pump frequently. + +The issue is most apparent during the night. During daytime operation, SMBs often result in a basal rate of 0, which masks the effect. In observed usage, this results in approximately 10% of the expected Total Daily Dose (TDD) not being delivered over a 24-hour period. Additionally, glucose targets are often not reached overnight, particularly after meals with prolonged glucose impact (e.g. pasta). + +***NOTE:** This issue is especially important to understand for people on very small dosages of insulin, Children for example.* + +#### Enable Basal Drift Fix in AAPS + +You must be running AAPS Version 3.4.2.3 or later for this feature. + +The Basal Drift Fix is not enabled by default on AAPS. + +**To enable it:** + +1. Create an empty file named `omnipod_drift_compensation` (2) in the `extra` (1) subfolder of your phone [AAPS directory](#preferences-maintenance-settings). + + ![dash_drift_enable_file](../images/DASH_images/DASH_Drift/dash_drift_enable_file.png) + + ***NOTE:** Ensure you check in the AAPS settings where your AAPS Directory is, and that you placed the file in the correct one, a number of several have been caught out putting the file into the wrong folder.* + +2. Restart **AAPS**. This must be done for it to recognise the file is present and enable the drift compensation feature. +3. Please visit this [Github issue #4783](https://github.com/nightscout/AndroidAPS/issues/4783) and thumbs up the first post indicating you are using this feature, we need this data to help demonstrate the feature is widely used. Once there is significant community adoption the removal of the enable file will be possible, we appreciate your support here. ## Troubleshooting -(omnipod-dash-delivery-suspended)= +(omnipod-dash-troubleshooting)= This section covers common known issues and solutions for Omnipod DASH use with AAPS. There is also [General Troubleshooting](../GettingHelp/GeneralTroubleshooting.md) section in the documentation that should be reviewed as it covers relevant topics for some Pod issues too. @@ -497,6 +532,9 @@ This section covers common known issues and solutions for Omnipod DASH use with For known issues with Bluetooth connections, dropouts of pump/pods, or activation and connection issues [Bluetooth Troubleshooting](../GettingHelp/BluetoothTroubleshooting.md) --- + +(omnipod-dash-delivery-suspended)= + ### Delivery suspended - There is no suspend button anymore. If you want to "suspend" the pod, you can set a zero **TBR** for x minutes. diff --git a/docs/CROWDIN/pt/images/DASH_images/DASH_Drift/dash_drift_enable_file.png b/docs/CROWDIN/pt/images/DASH_images/DASH_Drift/dash_drift_enable_file.png new file mode 100644 index 000000000000..917f90c264b5 Binary files /dev/null and b/docs/CROWDIN/pt/images/DASH_images/DASH_Drift/dash_drift_enable_file.png differ diff --git a/docs/CROWDIN/pt/images/DASH_images/DASH_Drift/dash_drift_pod_mgmt.png b/docs/CROWDIN/pt/images/DASH_images/DASH_Drift/dash_drift_pod_mgmt.png new file mode 100644 index 000000000000..5b9a8485a40b Binary files /dev/null and b/docs/CROWDIN/pt/images/DASH_images/DASH_Drift/dash_drift_pod_mgmt.png differ diff --git a/docs/CROWDIN/pt/images/DASH_images/DASH_Drift/dash_drift_pod_stats_end.png b/docs/CROWDIN/pt/images/DASH_images/DASH_Drift/dash_drift_pod_stats_end.png new file mode 100644 index 000000000000..5b268b517df0 Binary files /dev/null and b/docs/CROWDIN/pt/images/DASH_images/DASH_Drift/dash_drift_pod_stats_end.png differ diff --git a/docs/CROWDIN/pt/images/DASH_images/DASH_Drift/dash_drift_pod_stats_start.png b/docs/CROWDIN/pt/images/DASH_images/DASH_Drift/dash_drift_pod_stats_start.png new file mode 100644 index 000000000000..2863168f7b19 Binary files /dev/null and b/docs/CROWDIN/pt/images/DASH_images/DASH_Drift/dash_drift_pod_stats_start.png differ diff --git a/docs/CROWDIN/pt/images/DASH_images/DASH_Drift/dash_drift_tab_pod_mgmt.png b/docs/CROWDIN/pt/images/DASH_images/DASH_Drift/dash_drift_tab_pod_mgmt.png new file mode 100644 index 000000000000..30a5edb90b1d Binary files /dev/null and b/docs/CROWDIN/pt/images/DASH_images/DASH_Drift/dash_drift_tab_pod_mgmt.png differ diff --git a/docs/CROWDIN/pt/images/DASH_images/DASH_Drift/dash_drift_tdd.png b/docs/CROWDIN/pt/images/DASH_images/DASH_Drift/dash_drift_tdd.png new file mode 100644 index 000000000000..28b7685fa5bd Binary files /dev/null and b/docs/CROWDIN/pt/images/DASH_images/DASH_Drift/dash_drift_tdd.png differ diff --git a/docs/CROWDIN/ro/CompatiblePumps/OmnipodDASH.md b/docs/CROWDIN/ro/CompatiblePumps/OmnipodDASH.md index d2c5d3449d48..b978f6065966 100644 --- a/docs/CROWDIN/ro/CompatiblePumps/OmnipodDASH.md +++ b/docs/CROWDIN/ro/CompatiblePumps/OmnipodDASH.md @@ -19,8 +19,8 @@ Acestea sunt specificațiile modelului **Omnipod DASH** ("DASH") și ce îl dife ## Constrângeri/probleme AAPS cunoscute pentru Omnipod DASH - Android 16 necesită **AAPS** versiunea 3.3.2.1 sau mai târziu. - Recomandare generală este de a rula **AAPS** pe Android 14 sau 16. Android 15 are multe probleme [raportate ](https://github.com/nightscout/AndroidAPS/issues/3471) de către comunitate. Cu toate acestea, dacă rulați pe Android 15, este posibil să fie nevoie să activați și să utilizați Bluetooth Bonding cu succes pompele, vedeți [Depanare](../GettingHelp/GeneralTroubleshooting.md) pentru mai multe informații despre setările de asociere. -- Actualizările prea frecvente ale bazalelor pot cauza [probleme](https://github.com/nightscout/AndroidAPS/issues/4158) în administrarea insulinei bazale cu Omnipod Dash. Când se utilizează **SMB**, limitează intervalul la minim 5 minute pentru a evita această problemă. -- Dash acceptă doar rata bazale în pași de 0,05 U/h. Dacă încercați să setați bazala cu pași de 0,01 în profilul **AAPS**, AAPS nu vă va da un avertisment, chiar dacă pompa va rotunji rata bazală în pași de 0,05. Dacă afișați Gestionare Pompă/Istoric Pompă vă va arată că s-a setat o bazală de 0,05. Acest lucru înseamnă, de asemenea, cea mai mică rată bazală permisă de DASH din **AAPS** este de 0,05U/h. +- Temporary Basal rate changes (which occur frequently when the loop is active, especially overnight) result in under-delivery of insulin. This is effectively a hardware limitation of the Omnipod DASH. The issue has been addressed in AAPS 3.4.2.3, but the functionality is currently opt-in. Follow the [Basal Drift Fix Instructions ](#omnipod-dash-Basal-drift-fix) instructions to enable it. For more information regarding the fix see [Github Issue - 4783](https://github.com/nightscout/AndroidAPS/issues/4783) for more info. +- Dash acceptă doar rata bazale în pași de 0,05 U/h. If you try to set Basal with 0.01 steps in your **AAPS profile**, AAPS will not give a warning even though the pod will round up the rate into 0.05 steps. Dacă afișați Gestionare Pompă/Istoric Pompă vă va arată că s-a setat o bazală de 0,05. Acest lucru înseamnă, de asemenea, cea mai mică rată bazală permisă de DASH din **AAPS** este de 0,05U/h. - Starea de activare a unei pompe este stocată în fișierul de setări, dacă exportați un fișier de setări cu o pompă activă. Apoi schimbați la o nouă pompă, restabiliți setările din exportul anterior și veți fi restabilit activarea pompei vechi și veți fi eliminat activarea pompei noi. De aceea, vă recomandăm să exportați setările după fiecare activare de pompă pentru a permite o restaurare a stării de activare a pompei, dacă ceva se întâmplă cu dispozitivul dumneavoastră. - La setarea unui profil bazal nou, DASH va suspenda administrarea înainte de a seta noul **Profil** bazal. Dacă există o întrerupere sau o eroare de comunicare, profilul bazalei nu va reporni automat. Vedeți secțiunea [Reluarea Administrării de insulină](#omnipod-dash-resuming-insulin-delivery) pentru detalii. - În cazul în care alertele sunt configurate, iar pompa este pe cale să expire, pompa va continua să piuie până când alertele sunt reduse la tăcere, Vedeți [Suprimarea alertelor pompei](#omnipod-dash-silencing-pod-alerts) pentru detalii. @@ -70,8 +70,8 @@ Atâta timp cât **AAPS** este operațional va trimite comenzi de ajustare ale r Când pentru vreun motiv anume pompa nu primește comenzi noi (de exemplu pentru că comunicarea a fost pierdută din cauza distanței pompă ➜ telefon) pompa va reveni la rata bazală implicită așa cum a fost setată în [**profilul**](../SettingUpAaps/YourAapsProfile.md) dumneavoastră. ### **Profilul(urile) AAPS nu acceptă intervale de 30 minute pentru ratele bazale** -Dacă sunteți la început cu **AAPS** și configurați [**profilul**](../SettingUpAaps/YourAapsProfile.md) ratei bazale pentru prima dată, vă rugăm să rețineți că ratele bazale la intervale de o jumătate de oră nu sunt acceptate. De exemplu, pe telecomanda Omnipod, dacă aveți o rată bazală de 1,1 unitățile care începe la ora 09:30 și care au o durată de 2 ore care se termină la ora 11:30, în schimb nu este posibil să reproducem acest **profil** bazal în **AAPS**. -Va trebui să schimbați această rată bazală de 1,1 unități într-un interval de timp care să fie 9:00-11:00, fie 10:00-12:00. Chiar dacă hardware-ul DASH însuși suportă incrementele de 30 de minute ale **profilulului** ratei bazale, **AAPS** NU acceptă această caracteristică. +Dacă sunteți la început cu **AAPS** și configurați [**profilul**](../SettingUpAaps/YourAapsProfile.md) ratei bazale pentru prima dată, vă rugăm să rețineți că ratele bazale la intervale de o jumătate de oră nu sunt acceptate. For example, on your Omnipod PDM, if you have a basal rate of 1.1 units which starts at 09:30 and has a duration of 2 hours ending at 11:30, it is not possible replicate this exact Basal **Profile** in **AAPS**. +You will need to change this 1.1 unit basal rate to a time range of either 9:00-11:00 or 10:00-12:00. Chiar dacă hardware-ul DASH însuși suportă incrementele de 30 de minute ale **profilulului** ratei bazale, **AAPS** NU acceptă această caracteristică. ### **Valori bazale de 0U/h ale profilului NU sunt acceptate în AAPS** Deși DASH acceptă o rată bazală de zero, **AAPS** folosește multiplii ai ratelor bazale din **Profil** pentru a determina tratamentul automat; nu poate funcționa cu rată bazală de zero. @@ -480,11 +480,46 @@ Notă suplimentară: * **SMS** - Returnează valoarea sau 50+U pentru răspunsuri SMS * **Nightscout** - Încarcă în Nightscout valoarea de 50 atunci când sunt peste 50 de unități (versiunea 14.07 și mai vechi). Versiunile mai noi vor raporta o valoare de 50+ atunci când depășesc 50 de unități. -(omnipod-dash-troubleshooting)= +(omnipod-dash-known-issues-workarounds)= + +## Known Issues Workarounds + +This section covers common workarounds and settings that need to be changed to enable a feature to work around a community reported issue that has a fix. Spre exemplu the Basal drift enable process is documented here. + +(#omnipod-dash-Basal-drift-fix)= + +### Basal Drift Fix Instructions + +The Omnipod Dash pump has a limitation that can cause it to deliver less basal insulin than **AAPS** expects, see [Issue #4783](https://github.com/nightscout/AndroidAPS/issues/4783) for more technical details. + +The Dash uses an internal timer to determine when a basal pulse of 0.05 U is delivered. Once the timer interval elapses, the pulse is delivered. However, this timer is restarted whenever a basal rate change occurs e.g when **AAPS** sends a new Basal rate. + +When used in combination with looping, this leads to under-delivery of basal insulin, as the algorithm updates the basal rate on the pump frequently. + +The issue is most apparent during the night. During daytime operation, SMBs often result in a basal rate of 0, which masks the effect. In observed usage, this results in approximately 10% of the expected Total Daily Dose (TDD) not being delivered over a 24-hour period. Additionally, glucose targets are often not reached overnight, particularly after meals with prolonged glucose impact (e.g. pasta). + +***NOTE:** This issue is especially important to understand for people on very small dosages of insulin, Children for example.* + +#### Enable Basal Drift Fix in AAPS + +You must be running AAPS Version 3.4.2.3 or later for this feature. + +The Basal Drift Fix is not enabled by default on AAPS. + +**To enable it:** + +1. Create an empty file named `omnipod_drift_compensation` (2) in the `extra` (1) subfolder of your phone [AAPS directory](#preferences-maintenance-settings). + + ![dash_drift_enable_file](../images/DASH_images/DASH_Drift/dash_drift_enable_file.png) + + ***NOTE:** Ensure you check in the AAPS settings where your AAPS Directory is, and that you placed the file in the correct one, a number of several have been caught out putting the file into the wrong folder.* + +2. Restart **AAPS**. This must be done for it to recognise the file is present and enable the drift compensation feature. +3. Please visit this [Github issue #4783](https://github.com/nightscout/AndroidAPS/issues/4783) and thumbs up the first post indicating you are using this feature, we need this data to help demonstrate the feature is widely used. Once there is significant community adoption the removal of the enable file will be possible, we appreciate your support here. ## Depanare -(omnipod-dash-delivery-suspended)= +(omnipod-dash-troubleshooting)= Prezenta secțiune se referă la problemele comune cunoscute și la soluțiile pentru utilizarea Omnipod DASH împreună cu AAPS. Există, de asemenea, secțiunea [Depanare generală](../GettingHelp/GeneralTroubleshooting.md) în documentație care ar trebui să fie reluată deoarece acoperă subiecte relevante și pentru unele probleme specifice pompei Omnipod. @@ -497,6 +532,9 @@ Prezenta secțiune se referă la problemele comune cunoscute și la soluțiile p Pentru probleme cunoscute cu conexiunile Bluetooth, întreruperile pompei, activarea și problemele de conexiune [Depanarea Bluetooth](../GettingHelp/BluetoothTroubleshooting.md) --- + +(omnipod-dash-delivery-suspended)= + ### Administrarea insulinei suspendată - Nu mai există niciun buton de suspendare. Dacă doriți să "suspendați" pompa, puteți seta o **RBT** zero pentru x minute. diff --git a/docs/CROWDIN/ro/images/DASH_images/DASH_Drift/dash_drift_enable_file.png b/docs/CROWDIN/ro/images/DASH_images/DASH_Drift/dash_drift_enable_file.png new file mode 100644 index 000000000000..917f90c264b5 Binary files /dev/null and b/docs/CROWDIN/ro/images/DASH_images/DASH_Drift/dash_drift_enable_file.png differ diff --git a/docs/CROWDIN/ro/images/DASH_images/DASH_Drift/dash_drift_pod_mgmt.png b/docs/CROWDIN/ro/images/DASH_images/DASH_Drift/dash_drift_pod_mgmt.png new file mode 100644 index 000000000000..5b9a8485a40b Binary files /dev/null and b/docs/CROWDIN/ro/images/DASH_images/DASH_Drift/dash_drift_pod_mgmt.png differ diff --git a/docs/CROWDIN/ro/images/DASH_images/DASH_Drift/dash_drift_pod_stats_end.png b/docs/CROWDIN/ro/images/DASH_images/DASH_Drift/dash_drift_pod_stats_end.png new file mode 100644 index 000000000000..5b268b517df0 Binary files /dev/null and b/docs/CROWDIN/ro/images/DASH_images/DASH_Drift/dash_drift_pod_stats_end.png differ diff --git a/docs/CROWDIN/ro/images/DASH_images/DASH_Drift/dash_drift_pod_stats_start.png b/docs/CROWDIN/ro/images/DASH_images/DASH_Drift/dash_drift_pod_stats_start.png new file mode 100644 index 000000000000..2863168f7b19 Binary files /dev/null and b/docs/CROWDIN/ro/images/DASH_images/DASH_Drift/dash_drift_pod_stats_start.png differ diff --git a/docs/CROWDIN/ro/images/DASH_images/DASH_Drift/dash_drift_tab_pod_mgmt.png b/docs/CROWDIN/ro/images/DASH_images/DASH_Drift/dash_drift_tab_pod_mgmt.png new file mode 100644 index 000000000000..30a5edb90b1d Binary files /dev/null and b/docs/CROWDIN/ro/images/DASH_images/DASH_Drift/dash_drift_tab_pod_mgmt.png differ diff --git a/docs/CROWDIN/ro/images/DASH_images/DASH_Drift/dash_drift_tdd.png b/docs/CROWDIN/ro/images/DASH_images/DASH_Drift/dash_drift_tdd.png new file mode 100644 index 000000000000..28b7685fa5bd Binary files /dev/null and b/docs/CROWDIN/ro/images/DASH_images/DASH_Drift/dash_drift_tdd.png differ diff --git a/docs/CROWDIN/ru/CompatiblePumps/OmnipodDASH.md b/docs/CROWDIN/ru/CompatiblePumps/OmnipodDASH.md index 9083dae041fd..2d9b0d5955d4 100644 --- a/docs/CROWDIN/ru/CompatiblePumps/OmnipodDASH.md +++ b/docs/CROWDIN/ru/CompatiblePumps/OmnipodDASH.md @@ -19,8 +19,8 @@ These are the specifications of the **Omnipod DASH** ('DASH') and what different ## Известные ограничения и проблемы с Omnipod DASH в AAPS - Android 16 требует **AAPS** версии 3.3.2.1 или выше. - Общий совет — использовать **AAPS** на Android 14 или 16. Пользователи сообщают о большом количестве [проблем](https://github.com/nightscout/AndroidAPS/issues/3471) при использовании с Android 15. However, if you do run on Android 15 you will likely need to enable Bluetooth Bonding to successfully activate and use Pods, see [General Troubleshooting](../GettingHelp/GeneralTroubleshooting.md) for more info on the Bonding settings. -- Too frequent basal updates may cause basal insulin delivery [problems](https://github.com/nightscout/AndroidAPS/issues/4158) with Omnipod Dash. When using **SMB**, limit the interval to 5 minutes minimum to avoid this issue. -- Dash only supports basal rate in 0.05 U/h steps. If you try to set basal with 0.01 steps in your **AAPS profile**, AAPS will not give a warning even though the pod will round up the rate into 0.05 steps. If you view POD MGMT/Pod History it will display that 0.05 basal was set. This also means the lowest basal rate allowed by the DASH in **AAPS** is 0.05U/h. +- Temporary Basal rate changes (which occur frequently when the loop is active, especially overnight) result in under-delivery of insulin. This is effectively a hardware limitation of the Omnipod DASH. The issue has been addressed in AAPS 3.4.2.3, but the functionality is currently opt-in. Follow the [Basal Drift Fix Instructions ](#omnipod-dash-Basal-drift-fix) instructions to enable it. For more information regarding the fix see [Github Issue - 4783](https://github.com/nightscout/AndroidAPS/issues/4783) for more info. +- Dash only supports basal rate in 0.05 U/h steps. If you try to set Basal with 0.01 steps in your **AAPS profile**, AAPS will not give a warning even though the pod will round up the rate into 0.05 steps. If you view POD MGMT/Pod History it will display that 0.05 basal was set. This also means the lowest basal rate allowed by the DASH in **AAPS** is 0.05U/h. - The activation status of a Pod is stored in the settings file, if you export a settings file with an active pod. Then change to a new pod, then restore the settings from your previous export you will have now restored the old pod activation and removed the new pod activation. This is why we recommend to export settings after each pod activation to allow a restore of that pods activation state if something happens to your rig. - When setting a new basal profile, DASH will suspend delivery before setting the new basal **Profile**. If there is a communication interruption or error, the basal profile won't automatically re-start. See section [Resuming Insulin Delivery](#omnipod-dash-resuming-insulin-delivery) for details. - If alerts are configured, and the pod is about to expire, the pod will keep beeping until alerts are silenced, see [Silencing Pod Alerts](#omnipod-dash-silencing-pod-alerts) for details. @@ -70,7 +70,7 @@ As long as **AAPS** is operational it will send basal rate adjustment commands t When for some reason the pod does not receive any new commands (for instance because communication was lost due to Pod ➜ phone distance) the pod will automatically fall back to default basal rates as defined in your [**Profile**](../SettingUpAaps/YourAapsProfile.md). ### **AAPS Profile(s) do not support 30 minute basal rate time frames** -If you are new to **AAPS** and are setting up your basal rate [**Profile**](../SettingUpAaps/YourAapsProfile.md) for the first time, please be aware that basal rates starting on a half-hour basis are not supported. For example, on your Omnipod PDM, if you have a basal rate of 1.1 units which starts at 09:30 and has a duration of 2 hours ending at 11:30, it is not possible replicate this exact basil **Profile** in **AAPS**. +If you are new to **AAPS** and are setting up your basal rate [**Profile**](../SettingUpAaps/YourAapsProfile.md) for the first time, please be aware that basal rates starting on a half-hour basis are not supported. For example, on your Omnipod PDM, if you have a basal rate of 1.1 units which starts at 09:30 and has a duration of 2 hours ending at 11:30, it is not possible replicate this exact Basal **Profile** in **AAPS**. You will need to change this 1.1 unit basal rate to a time range of either 9:00-11:00 or 10:00-12:00. Even though the DASH hardware itself supports the 30 minute basal rate **Profile** increments, **AAPS** does NOT support this feature. ### **0U/h Profile basal rates are NOT supported in AAPS** @@ -480,11 +480,46 @@ Additional note: * **SMS** - В SMS сообщается реальный остаток в ед. или 50+ед * **Nightscout** - при более чем 50 единиц в Nightscout выгружается значение 50 ед.(версия 14.07 и старше). Более новые версии покажут 50 + когда более 50 единиц. -(omnipod-dash-troubleshooting)= +(omnipod-dash-known-issues-workarounds)= + +## Known Issues Workarounds + +This section covers common workarounds and settings that need to be changed to enable a feature to work around a community reported issue that has a fix. Например, the Basal drift enable process is documented here. + +(#omnipod-dash-Basal-drift-fix)= + +### Basal Drift Fix Instructions + +The Omnipod Dash pump has a limitation that can cause it to deliver less basal insulin than **AAPS** expects, see [Issue #4783](https://github.com/nightscout/AndroidAPS/issues/4783) for more technical details. + +The Dash uses an internal timer to determine when a basal pulse of 0.05 U is delivered. Once the timer interval elapses, the pulse is delivered. However, this timer is restarted whenever a basal rate change occurs e.g when **AAPS** sends a new Basal rate. + +When used in combination with looping, this leads to under-delivery of basal insulin, as the algorithm updates the basal rate on the pump frequently. + +The issue is most apparent during the night. During daytime operation, SMBs often result in a basal rate of 0, which masks the effect. In observed usage, this results in approximately 10% of the expected Total Daily Dose (TDD) not being delivered over a 24-hour period. Additionally, glucose targets are often not reached overnight, particularly after meals with prolonged glucose impact (e.g. pasta). + +***NOTE:** This issue is especially important to understand for people on very small dosages of insulin, Children for example.* + +#### Enable Basal Drift Fix in AAPS + +You must be running AAPS Version 3.4.2.3 or later for this feature. + +The Basal Drift Fix is not enabled by default on AAPS. + +**To enable it:** + +1. Create an empty file named `omnipod_drift_compensation` (2) in the `extra` (1) subfolder of your phone [AAPS directory](#preferences-maintenance-settings). + + ![dash_drift_enable_file](../images/DASH_images/DASH_Drift/dash_drift_enable_file.png) + + ***NOTE:** Ensure you check in the AAPS settings where your AAPS Directory is, and that you placed the file in the correct one, a number of several have been caught out putting the file into the wrong folder.* + +2. Restart **AAPS**. This must be done for it to recognise the file is present and enable the drift compensation feature. +3. Please visit this [Github issue #4783](https://github.com/nightscout/AndroidAPS/issues/4783) and thumbs up the first post indicating you are using this feature, we need this data to help demonstrate the feature is widely used. Once there is significant community adoption the removal of the enable file will be possible, we appreciate your support here. ## Устранение неполадок -(omnipod-dash-delivery-suspended)= +(omnipod-dash-troubleshooting)= This section covers common known issues and solutions for Omnipod DASH use with AAPS. There is also [General Troubleshooting](../GettingHelp/GeneralTroubleshooting.md) section in the documentation that should be reviewed as it covers relevant topics for some Pod issues too. @@ -497,6 +532,9 @@ This section covers common known issues and solutions for Omnipod DASH use with For known issues with Bluetooth connections, dropouts of pump/pods, or activation and connection issues [Bluetooth Troubleshooting](../GettingHelp/BluetoothTroubleshooting.md) --- + +(omnipod-dash-delivery-suspended)= + ### Delivery suspended - Кнопки приостановки больше нет. If you want to "suspend" the pod, you can set a zero **TBR** for x minutes. diff --git a/docs/CROWDIN/ru/images/DASH_images/DASH_Drift/dash_drift_enable_file.png b/docs/CROWDIN/ru/images/DASH_images/DASH_Drift/dash_drift_enable_file.png new file mode 100644 index 000000000000..917f90c264b5 Binary files /dev/null and b/docs/CROWDIN/ru/images/DASH_images/DASH_Drift/dash_drift_enable_file.png differ diff --git a/docs/CROWDIN/ru/images/DASH_images/DASH_Drift/dash_drift_pod_mgmt.png b/docs/CROWDIN/ru/images/DASH_images/DASH_Drift/dash_drift_pod_mgmt.png new file mode 100644 index 000000000000..5b9a8485a40b Binary files /dev/null and b/docs/CROWDIN/ru/images/DASH_images/DASH_Drift/dash_drift_pod_mgmt.png differ diff --git a/docs/CROWDIN/ru/images/DASH_images/DASH_Drift/dash_drift_pod_stats_end.png b/docs/CROWDIN/ru/images/DASH_images/DASH_Drift/dash_drift_pod_stats_end.png new file mode 100644 index 000000000000..5b268b517df0 Binary files /dev/null and b/docs/CROWDIN/ru/images/DASH_images/DASH_Drift/dash_drift_pod_stats_end.png differ diff --git a/docs/CROWDIN/ru/images/DASH_images/DASH_Drift/dash_drift_pod_stats_start.png b/docs/CROWDIN/ru/images/DASH_images/DASH_Drift/dash_drift_pod_stats_start.png new file mode 100644 index 000000000000..2863168f7b19 Binary files /dev/null and b/docs/CROWDIN/ru/images/DASH_images/DASH_Drift/dash_drift_pod_stats_start.png differ diff --git a/docs/CROWDIN/ru/images/DASH_images/DASH_Drift/dash_drift_tab_pod_mgmt.png b/docs/CROWDIN/ru/images/DASH_images/DASH_Drift/dash_drift_tab_pod_mgmt.png new file mode 100644 index 000000000000..30a5edb90b1d Binary files /dev/null and b/docs/CROWDIN/ru/images/DASH_images/DASH_Drift/dash_drift_tab_pod_mgmt.png differ diff --git a/docs/CROWDIN/ru/images/DASH_images/DASH_Drift/dash_drift_tdd.png b/docs/CROWDIN/ru/images/DASH_images/DASH_Drift/dash_drift_tdd.png new file mode 100644 index 000000000000..28b7685fa5bd Binary files /dev/null and b/docs/CROWDIN/ru/images/DASH_images/DASH_Drift/dash_drift_tdd.png differ diff --git a/docs/CROWDIN/sk/CompatiblePumps/OmnipodDASH.md b/docs/CROWDIN/sk/CompatiblePumps/OmnipodDASH.md index cbb861d809c9..3c255d534ffa 100644 --- a/docs/CROWDIN/sk/CompatiblePumps/OmnipodDASH.md +++ b/docs/CROWDIN/sk/CompatiblePumps/OmnipodDASH.md @@ -19,8 +19,8 @@ These are the specifications of the **Omnipod DASH** ('DASH') and what different ## Omnipod DASH known AAPS constraints/issues - Android 16 requires **AAPS** version 3.3.2.1 or later. - General advice is to run **AAPS** on Android 14 or 16. Android 15 has many reported [issues](https://github.com/nightscout/AndroidAPS/issues/3471) from the community. However, if you do run on Android 15 you will likely need to enable Bluetooth Bonding to successfully activate and use Pods, see [General Troubleshooting](../GettingHelp/GeneralTroubleshooting.md) for more info on the Bonding settings. -- Too frequent basal updates may cause basal insulin delivery [problems](https://github.com/nightscout/AndroidAPS/issues/4158) with Omnipod Dash. When using **SMB**, limit the interval to 5 minutes minimum to avoid this issue. -- Dash only supports basal rate in 0.05 U/h steps. If you try to set basal with 0.01 steps in your **AAPS profile**, AAPS will not give a warning even though the pod will round up the rate into 0.05 steps. If you view POD MGMT/Pod History it will display that 0.05 basal was set. This also means the lowest basal rate allowed by the DASH in **AAPS** is 0.05U/h. +- Temporary Basal rate changes (which occur frequently when the loop is active, especially overnight) result in under-delivery of insulin. This is effectively a hardware limitation of the Omnipod DASH. The issue has been addressed in AAPS 3.4.2.3, but the functionality is currently opt-in. Follow the [Basal Drift Fix Instructions ](#omnipod-dash-Basal-drift-fix) instructions to enable it. For more information regarding the fix see [Github Issue - 4783](https://github.com/nightscout/AndroidAPS/issues/4783) for more info. +- Dash only supports basal rate in 0.05 U/h steps. If you try to set Basal with 0.01 steps in your **AAPS profile**, AAPS will not give a warning even though the pod will round up the rate into 0.05 steps. If you view POD MGMT/Pod History it will display that 0.05 basal was set. This also means the lowest basal rate allowed by the DASH in **AAPS** is 0.05U/h. - The activation status of a Pod is stored in the settings file, if you export a settings file with an active pod. Then change to a new pod, then restore the settings from your previous export you will have now restored the old pod activation and removed the new pod activation. This is why we recommend to export settings after each pod activation to allow a restore of that pods activation state if something happens to your rig. - When setting a new basal profile, DASH will suspend delivery before setting the new basal **Profile**. If there is a communication interruption or error, the basal profile won't automatically re-start. See section [Resuming Insulin Delivery](#omnipod-dash-resuming-insulin-delivery) for details. - If alerts are configured, and the pod is about to expire, the pod will keep beeping until alerts are silenced, see [Silencing Pod Alerts](#omnipod-dash-silencing-pod-alerts) for details. @@ -70,7 +70,7 @@ As long as **AAPS** is operational it will send basal rate adjustment commands t When for some reason the pod does not receive any new commands (for instance because communication was lost due to Pod ➜ phone distance) the pod will automatically fall back to default basal rates as defined in your [**Profile**](../SettingUpAaps/YourAapsProfile.md). ### **AAPS Profile(s) do not support 30 minute basal rate time frames** -If you are new to **AAPS** and are setting up your basal rate [**Profile**](../SettingUpAaps/YourAapsProfile.md) for the first time, please be aware that basal rates starting on a half-hour basis are not supported. For example, on your Omnipod PDM, if you have a basal rate of 1.1 units which starts at 09:30 and has a duration of 2 hours ending at 11:30, it is not possible replicate this exact basil **Profile** in **AAPS**. +If you are new to **AAPS** and are setting up your basal rate [**Profile**](../SettingUpAaps/YourAapsProfile.md) for the first time, please be aware that basal rates starting on a half-hour basis are not supported. For example, on your Omnipod PDM, if you have a basal rate of 1.1 units which starts at 09:30 and has a duration of 2 hours ending at 11:30, it is not possible replicate this exact Basal **Profile** in **AAPS**. You will need to change this 1.1 unit basal rate to a time range of either 9:00-11:00 or 10:00-12:00. Even though the DASH hardware itself supports the 30 minute basal rate **Profile** increments, **AAPS** does NOT support this feature. ### **0U/h Profile basal rates are NOT supported in AAPS** @@ -480,11 +480,46 @@ Additional note: * **SMS** - Returns value or 50+U for SMS responses * **Nightscout** - Uploads value of 50 when over 50 units to Nightscout (version 14.07 and older). Newer versions will report a value of 50+ when over 50 units. -(omnipod-dash-troubleshooting)= +(omnipod-dash-known-issues-workarounds)= + +## Known Issues Workarounds + +This section covers common workarounds and settings that need to be changed to enable a feature to work around a community reported issue that has a fix. E.g. the Basal drift enable process is documented here. + +(#omnipod-dash-Basal-drift-fix)= + +### Basal Drift Fix Instructions + +The Omnipod Dash pump has a limitation that can cause it to deliver less basal insulin than **AAPS** expects, see [Issue #4783](https://github.com/nightscout/AndroidAPS/issues/4783) for more technical details. + +The Dash uses an internal timer to determine when a basal pulse of 0.05 U is delivered. Once the timer interval elapses, the pulse is delivered. However, this timer is restarted whenever a basal rate change occurs e.g when **AAPS** sends a new Basal rate. + +When used in combination with looping, this leads to under-delivery of basal insulin, as the algorithm updates the basal rate on the pump frequently. + +The issue is most apparent during the night. During daytime operation, SMBs often result in a basal rate of 0, which masks the effect. In observed usage, this results in approximately 10% of the expected Total Daily Dose (TDD) not being delivered over a 24-hour period. Additionally, glucose targets are often not reached overnight, particularly after meals with prolonged glucose impact (e.g. pasta). + +***NOTE:** This issue is especially important to understand for people on very small dosages of insulin, Children for example.* + +#### Enable Basal Drift Fix in AAPS + +You must be running AAPS Version 3.4.2.3 or later for this feature. + +The Basal Drift Fix is not enabled by default on AAPS. + +**To enable it:** + +1. Create an empty file named `omnipod_drift_compensation` (2) in the `extra` (1) subfolder of your phone [AAPS directory](#preferences-maintenance-settings). + + ![dash_drift_enable_file](../images/DASH_images/DASH_Drift/dash_drift_enable_file.png) + + ***NOTE:** Ensure you check in the AAPS settings where your AAPS Directory is, and that you placed the file in the correct one, a number of several have been caught out putting the file into the wrong folder.* + +2. Restart **AAPS**. This must be done for it to recognise the file is present and enable the drift compensation feature. +3. Please visit this [Github issue #4783](https://github.com/nightscout/AndroidAPS/issues/4783) and thumbs up the first post indicating you are using this feature, we need this data to help demonstrate the feature is widely used. Once there is significant community adoption the removal of the enable file will be possible, we appreciate your support here. ## Troubleshooting -(omnipod-dash-delivery-suspended)= +(omnipod-dash-troubleshooting)= This section covers common known issues and solutions for Omnipod DASH use with AAPS. There is also [General Troubleshooting](../GettingHelp/GeneralTroubleshooting.md) section in the documentation that should be reviewed as it covers relevant topics for some Pod issues too. @@ -497,6 +532,9 @@ This section covers common known issues and solutions for Omnipod DASH use with For known issues with Bluetooth connections, dropouts of pump/pods, or activation and connection issues [Bluetooth Troubleshooting](../GettingHelp/BluetoothTroubleshooting.md) --- + +(omnipod-dash-delivery-suspended)= + ### Delivery suspended - There is no suspend button anymore. If you want to "suspend" the pod, you can set a zero **TBR** for x minutes. diff --git a/docs/CROWDIN/sk/images/DASH_images/DASH_Drift/dash_drift_enable_file.png b/docs/CROWDIN/sk/images/DASH_images/DASH_Drift/dash_drift_enable_file.png new file mode 100644 index 000000000000..917f90c264b5 Binary files /dev/null and b/docs/CROWDIN/sk/images/DASH_images/DASH_Drift/dash_drift_enable_file.png differ diff --git a/docs/CROWDIN/sk/images/DASH_images/DASH_Drift/dash_drift_pod_mgmt.png b/docs/CROWDIN/sk/images/DASH_images/DASH_Drift/dash_drift_pod_mgmt.png new file mode 100644 index 000000000000..5b9a8485a40b Binary files /dev/null and b/docs/CROWDIN/sk/images/DASH_images/DASH_Drift/dash_drift_pod_mgmt.png differ diff --git a/docs/CROWDIN/sk/images/DASH_images/DASH_Drift/dash_drift_pod_stats_end.png b/docs/CROWDIN/sk/images/DASH_images/DASH_Drift/dash_drift_pod_stats_end.png new file mode 100644 index 000000000000..5b268b517df0 Binary files /dev/null and b/docs/CROWDIN/sk/images/DASH_images/DASH_Drift/dash_drift_pod_stats_end.png differ diff --git a/docs/CROWDIN/sk/images/DASH_images/DASH_Drift/dash_drift_pod_stats_start.png b/docs/CROWDIN/sk/images/DASH_images/DASH_Drift/dash_drift_pod_stats_start.png new file mode 100644 index 000000000000..2863168f7b19 Binary files /dev/null and b/docs/CROWDIN/sk/images/DASH_images/DASH_Drift/dash_drift_pod_stats_start.png differ diff --git a/docs/CROWDIN/sk/images/DASH_images/DASH_Drift/dash_drift_tab_pod_mgmt.png b/docs/CROWDIN/sk/images/DASH_images/DASH_Drift/dash_drift_tab_pod_mgmt.png new file mode 100644 index 000000000000..30a5edb90b1d Binary files /dev/null and b/docs/CROWDIN/sk/images/DASH_images/DASH_Drift/dash_drift_tab_pod_mgmt.png differ diff --git a/docs/CROWDIN/sk/images/DASH_images/DASH_Drift/dash_drift_tdd.png b/docs/CROWDIN/sk/images/DASH_images/DASH_Drift/dash_drift_tdd.png new file mode 100644 index 000000000000..28b7685fa5bd Binary files /dev/null and b/docs/CROWDIN/sk/images/DASH_images/DASH_Drift/dash_drift_tdd.png differ diff --git a/docs/CROWDIN/tr/CompatiblePumps/OmnipodDASH.md b/docs/CROWDIN/tr/CompatiblePumps/OmnipodDASH.md index 3ca7e4f1ffea..e48c7e68ca69 100644 --- a/docs/CROWDIN/tr/CompatiblePumps/OmnipodDASH.md +++ b/docs/CROWDIN/tr/CompatiblePumps/OmnipodDASH.md @@ -19,8 +19,8 @@ These are the specifications of the **Omnipod DASH** ('DASH') and what different ## Omnipod DASH known AAPS constraints/issues - Android 16 requires **AAPS** version 3.3.2.1 or later. - General advice is to run **AAPS** on Android 14 or 16. Android 15 has many reported [issues](https://github.com/nightscout/AndroidAPS/issues/3471) from the community. However, if you do run on Android 15 you will likely need to enable Bluetooth Bonding to successfully activate and use Pods, see [General Troubleshooting](../GettingHelp/GeneralTroubleshooting.md) for more info on the Bonding settings. -- Too frequent basal updates may cause basal insulin delivery [problems](https://github.com/nightscout/AndroidAPS/issues/4158) with Omnipod Dash. When using **SMB**, limit the interval to 5 minutes minimum to avoid this issue. -- Dash only supports basal rate in 0.05 U/h steps. If you try to set basal with 0.01 steps in your **AAPS profile**, AAPS will not give a warning even though the pod will round up the rate into 0.05 steps. If you view POD MGMT/Pod History it will display that 0.05 basal was set. This also means the lowest basal rate allowed by the DASH in **AAPS** is 0.05U/h. +- Temporary Basal rate changes (which occur frequently when the loop is active, especially overnight) result in under-delivery of insulin. This is effectively a hardware limitation of the Omnipod DASH. The issue has been addressed in AAPS 3.4.2.3, but the functionality is currently opt-in. Follow the [Basal Drift Fix Instructions ](#omnipod-dash-Basal-drift-fix) instructions to enable it. For more information regarding the fix see [Github Issue - 4783](https://github.com/nightscout/AndroidAPS/issues/4783) for more info. +- Dash only supports basal rate in 0.05 U/h steps. If you try to set Basal with 0.01 steps in your **AAPS profile**, AAPS will not give a warning even though the pod will round up the rate into 0.05 steps. If you view POD MGMT/Pod History it will display that 0.05 basal was set. This also means the lowest basal rate allowed by the DASH in **AAPS** is 0.05U/h. - The activation status of a Pod is stored in the settings file, if you export a settings file with an active pod. Then change to a new pod, then restore the settings from your previous export you will have now restored the old pod activation and removed the new pod activation. This is why we recommend to export settings after each pod activation to allow a restore of that pods activation state if something happens to your rig. - When setting a new basal profile, DASH will suspend delivery before setting the new basal **Profile**. If there is a communication interruption or error, the basal profile won't automatically re-start. See section [Resuming Insulin Delivery](#omnipod-dash-resuming-insulin-delivery) for details. - If alerts are configured, and the pod is about to expire, the pod will keep beeping until alerts are silenced, see [Silencing Pod Alerts](#omnipod-dash-silencing-pod-alerts) for details. @@ -70,7 +70,7 @@ As long as **AAPS** is operational it will send basal rate adjustment commands t When for some reason the pod does not receive any new commands (for instance because communication was lost due to Pod ➜ phone distance) the pod will automatically fall back to default basal rates as defined in your [**Profile**](../SettingUpAaps/YourAapsProfile.md). ### **AAPS Profile(s) do not support 30 minute basal rate time frames** -If you are new to **AAPS** and are setting up your basal rate [**Profile**](../SettingUpAaps/YourAapsProfile.md) for the first time, please be aware that basal rates starting on a half-hour basis are not supported. For example, on your Omnipod PDM, if you have a basal rate of 1.1 units which starts at 09:30 and has a duration of 2 hours ending at 11:30, it is not possible replicate this exact basil **Profile** in **AAPS**. +If you are new to **AAPS** and are setting up your basal rate [**Profile**](../SettingUpAaps/YourAapsProfile.md) for the first time, please be aware that basal rates starting on a half-hour basis are not supported. For example, on your Omnipod PDM, if you have a basal rate of 1.1 units which starts at 09:30 and has a duration of 2 hours ending at 11:30, it is not possible replicate this exact Basal **Profile** in **AAPS**. You will need to change this 1.1 unit basal rate to a time range of either 9:00-11:00 or 10:00-12:00. Even though the DASH hardware itself supports the 30 minute basal rate **Profile** increments, **AAPS** does NOT support this feature. ### **0U/h Profile basal rates are NOT supported in AAPS** @@ -480,11 +480,46 @@ Additional note: * **SMS** - SMS yanıtlarında insülin seviyesi 50+Ü veya değer görünür. * **Nightscout** - Nightscout'a (sürüm 14.07 ve daha eski) 50 üniteden fazla olduğunda 50 değerini yükler. Daha yeni sürümler, 50 ünite üzerinde olduğunda 50+ değerini bildirir. -(omnipod-dash-troubleshooting)= +(omnipod-dash-known-issues-workarounds)= + +## Known Issues Workarounds + +This section covers common workarounds and settings that need to be changed to enable a feature to work around a community reported issue that has a fix. Ör. the Basal drift enable process is documented here. + +(#omnipod-dash-Basal-drift-fix)= + +### Basal Drift Fix Instructions + +The Omnipod Dash pump has a limitation that can cause it to deliver less basal insulin than **AAPS** expects, see [Issue #4783](https://github.com/nightscout/AndroidAPS/issues/4783) for more technical details. + +The Dash uses an internal timer to determine when a basal pulse of 0.05 U is delivered. Once the timer interval elapses, the pulse is delivered. However, this timer is restarted whenever a basal rate change occurs e.g when **AAPS** sends a new Basal rate. + +When used in combination with looping, this leads to under-delivery of basal insulin, as the algorithm updates the basal rate on the pump frequently. + +The issue is most apparent during the night. During daytime operation, SMBs often result in a basal rate of 0, which masks the effect. In observed usage, this results in approximately 10% of the expected Total Daily Dose (TDD) not being delivered over a 24-hour period. Additionally, glucose targets are often not reached overnight, particularly after meals with prolonged glucose impact (e.g. pasta). + +***NOTE:** This issue is especially important to understand for people on very small dosages of insulin, Children for example.* + +#### Enable Basal Drift Fix in AAPS + +You must be running AAPS Version 3.4.2.3 or later for this feature. + +The Basal Drift Fix is not enabled by default on AAPS. + +**To enable it:** + +1. Create an empty file named `omnipod_drift_compensation` (2) in the `extra` (1) subfolder of your phone [AAPS directory](#preferences-maintenance-settings). + + ![dash_drift_enable_file](../images/DASH_images/DASH_Drift/dash_drift_enable_file.png) + + ***NOTE:** Ensure you check in the AAPS settings where your AAPS Directory is, and that you placed the file in the correct one, a number of several have been caught out putting the file into the wrong folder.* + +2. Restart **AAPS**. This must be done for it to recognise the file is present and enable the drift compensation feature. +3. Please visit this [Github issue #4783](https://github.com/nightscout/AndroidAPS/issues/4783) and thumbs up the first post indicating you are using this feature, we need this data to help demonstrate the feature is widely used. Once there is significant community adoption the removal of the enable file will be possible, we appreciate your support here. ## Troubleshooting -(omnipod-dash-delivery-suspended)= +(omnipod-dash-troubleshooting)= This section covers common known issues and solutions for Omnipod DASH use with AAPS. There is also [General Troubleshooting](../GettingHelp/GeneralTroubleshooting.md) section in the documentation that should be reviewed as it covers relevant topics for some Pod issues too. @@ -497,6 +532,9 @@ This section covers common known issues and solutions for Omnipod DASH use with For known issues with Bluetooth connections, dropouts of pump/pods, or activation and connection issues [Bluetooth Troubleshooting](../GettingHelp/BluetoothTroubleshooting.md) --- + +(omnipod-dash-delivery-suspended)= + ### Delivery suspended - Artık iletimi askıya alma butonu yok. If you want to "suspend" the pod, you can set a zero **TBR** for x minutes. diff --git a/docs/CROWDIN/tr/images/DASH_images/DASH_Drift/dash_drift_enable_file.png b/docs/CROWDIN/tr/images/DASH_images/DASH_Drift/dash_drift_enable_file.png new file mode 100644 index 000000000000..917f90c264b5 Binary files /dev/null and b/docs/CROWDIN/tr/images/DASH_images/DASH_Drift/dash_drift_enable_file.png differ diff --git a/docs/CROWDIN/tr/images/DASH_images/DASH_Drift/dash_drift_pod_mgmt.png b/docs/CROWDIN/tr/images/DASH_images/DASH_Drift/dash_drift_pod_mgmt.png new file mode 100644 index 000000000000..5b9a8485a40b Binary files /dev/null and b/docs/CROWDIN/tr/images/DASH_images/DASH_Drift/dash_drift_pod_mgmt.png differ diff --git a/docs/CROWDIN/tr/images/DASH_images/DASH_Drift/dash_drift_pod_stats_end.png b/docs/CROWDIN/tr/images/DASH_images/DASH_Drift/dash_drift_pod_stats_end.png new file mode 100644 index 000000000000..5b268b517df0 Binary files /dev/null and b/docs/CROWDIN/tr/images/DASH_images/DASH_Drift/dash_drift_pod_stats_end.png differ diff --git a/docs/CROWDIN/tr/images/DASH_images/DASH_Drift/dash_drift_pod_stats_start.png b/docs/CROWDIN/tr/images/DASH_images/DASH_Drift/dash_drift_pod_stats_start.png new file mode 100644 index 000000000000..2863168f7b19 Binary files /dev/null and b/docs/CROWDIN/tr/images/DASH_images/DASH_Drift/dash_drift_pod_stats_start.png differ diff --git a/docs/CROWDIN/tr/images/DASH_images/DASH_Drift/dash_drift_tab_pod_mgmt.png b/docs/CROWDIN/tr/images/DASH_images/DASH_Drift/dash_drift_tab_pod_mgmt.png new file mode 100644 index 000000000000..30a5edb90b1d Binary files /dev/null and b/docs/CROWDIN/tr/images/DASH_images/DASH_Drift/dash_drift_tab_pod_mgmt.png differ diff --git a/docs/CROWDIN/tr/images/DASH_images/DASH_Drift/dash_drift_tdd.png b/docs/CROWDIN/tr/images/DASH_images/DASH_Drift/dash_drift_tdd.png new file mode 100644 index 000000000000..28b7685fa5bd Binary files /dev/null and b/docs/CROWDIN/tr/images/DASH_images/DASH_Drift/dash_drift_tdd.png differ diff --git a/docs/CROWDIN/zh_CN/CompatiblePumps/OmnipodDASH.md b/docs/CROWDIN/zh_CN/CompatiblePumps/OmnipodDASH.md index 436962611378..cb36cf101859 100644 --- a/docs/CROWDIN/zh_CN/CompatiblePumps/OmnipodDASH.md +++ b/docs/CROWDIN/zh_CN/CompatiblePumps/OmnipodDASH.md @@ -19,8 +19,8 @@ These instructions are for configuring the **Omnipod DASH** generation pump **(N ## Omnipod DASH known AAPS constraints/issues - Android 16 requires **AAPS** version 3.3.2.1 or later. - General advice is to run **AAPS** on Android 14 or 16. Android 15 has many reported [issues](https://github.com/nightscout/AndroidAPS/issues/3471) from the community. However, if you do run on Android 15 you will likely need to enable Bluetooth Bonding to successfully activate and use Pods, see [General Troubleshooting](../GettingHelp/GeneralTroubleshooting.md) for more info on the Bonding settings. -- Too frequent basal updates may cause basal insulin delivery [problems](https://github.com/nightscout/AndroidAPS/issues/4158) with Omnipod Dash. When using **SMB**, limit the interval to 5 minutes minimum to avoid this issue. -- Dash only supports basal rate in 0.05 U/h steps. If you try to set basal with 0.01 steps in your **AAPS profile**, AAPS will not give a warning even though the pod will round up the rate into 0.05 steps. If you view POD MGMT/Pod History it will display that 0.05 basal was set. This also means the lowest basal rate allowed by the DASH in **AAPS** is 0.05U/h. +- Temporary Basal rate changes (which occur frequently when the loop is active, especially overnight) result in under-delivery of insulin. This is effectively a hardware limitation of the Omnipod DASH. The issue has been addressed in AAPS 3.4.2.3, but the functionality is currently opt-in. Follow the [Basal Drift Fix Instructions ](#omnipod-dash-Basal-drift-fix) instructions to enable it. For more information regarding the fix see [Github Issue - 4783](https://github.com/nightscout/AndroidAPS/issues/4783) for more info. +- Dash only supports basal rate in 0.05 U/h steps. If you try to set Basal with 0.01 steps in your **AAPS profile**, AAPS will not give a warning even though the pod will round up the rate into 0.05 steps. If you view POD MGMT/Pod History it will display that 0.05 basal was set. This also means the lowest basal rate allowed by the DASH in **AAPS** is 0.05U/h. - The activation status of a Pod is stored in the settings file, if you export a settings file with an active pod. Then change to a new pod, then restore the settings from your previous export you will have now restored the old pod activation and removed the new pod activation. This is why we recommend to export settings after each pod activation to allow a restore of that pods activation state if something happens to your rig. - When setting a new basal profile, DASH will suspend delivery before setting the new basal **Profile**. If there is a communication interruption or error, the basal profile won't automatically re-start. See section [Resuming Insulin Delivery](#omnipod-dash-resuming-insulin-delivery) for details. - If alerts are configured, and the pod is about to expire, the pod will keep beeping until alerts are silenced, see [Silencing Pod Alerts](#omnipod-dash-silencing-pod-alerts) for details. @@ -70,7 +70,7 @@ As long as **AAPS** is operational it will send basal rate adjustment commands t When for some reason the pod does not receive any new commands (for instance because communication was lost due to Pod ➜ phone distance) the pod will automatically fall back to default basal rates as defined in your [**Profile**](../SettingUpAaps/YourAapsProfile.md). ### **AAPS Profile(s) do not support 30 minute basal rate time frames** -If you are new to **AAPS** and are setting up your basal rate [**Profile**](../SettingUpAaps/YourAapsProfile.md) for the first time, please be aware that basal rates starting on a half-hour basis are not supported. For example, on your Omnipod PDM, if you have a basal rate of 1.1 units which starts at 09:30 and has a duration of 2 hours ending at 11:30, it is not possible replicate this exact basil **Profile** in **AAPS**. +If you are new to **AAPS** and are setting up your basal rate [**Profile**](../SettingUpAaps/YourAapsProfile.md) for the first time, please be aware that basal rates starting on a half-hour basis are not supported. For example, on your Omnipod PDM, if you have a basal rate of 1.1 units which starts at 09:30 and has a duration of 2 hours ending at 11:30, it is not possible replicate this exact Basal **Profile** in **AAPS**. You will need to change this 1.1 unit basal rate to a time range of either 9:00-11:00 or 10:00-12:00. Even though the DASH hardware itself supports the 30 minute basal rate **Profile** increments, **AAPS** does NOT support this feature. ### **0U/h Profile basal rates are NOT supported in AAPS** @@ -480,11 +480,46 @@ DASH概览标签页将显示如下内容： * **短信查询** - 短信回复将返回实际数值或"50+单位" * **Nightscout** - 当药量超过50单位时，会向Nightscout上传50的数值（14.07及更早版本）。 较新版本在药量超过50单位时将报告"50+"的数值。 -(omnipod-dash-troubleshooting)= +(omnipod-dash-known-issues-workarounds)= + +## Known Issues Workarounds + +This section covers common workarounds and settings that need to be changed to enable a feature to work around a community reported issue that has a fix. 例如 the Basal drift enable process is documented here. + +(#omnipod-dash-Basal-drift-fix)= + +### Basal Drift Fix Instructions + +The Omnipod Dash pump has a limitation that can cause it to deliver less basal insulin than **AAPS** expects, see [Issue #4783](https://github.com/nightscout/AndroidAPS/issues/4783) for more technical details. + +The Dash uses an internal timer to determine when a basal pulse of 0.05 U is delivered. Once the timer interval elapses, the pulse is delivered. However, this timer is restarted whenever a basal rate change occurs e.g when **AAPS** sends a new Basal rate. + +When used in combination with looping, this leads to under-delivery of basal insulin, as the algorithm updates the basal rate on the pump frequently. + +The issue is most apparent during the night. During daytime operation, SMBs often result in a basal rate of 0, which masks the effect. In observed usage, this results in approximately 10% of the expected Total Daily Dose (TDD) not being delivered over a 24-hour period. Additionally, glucose targets are often not reached overnight, particularly after meals with prolonged glucose impact (e.g. pasta). + +***NOTE:** This issue is especially important to understand for people on very small dosages of insulin, Children for example.* + +#### Enable Basal Drift Fix in AAPS + +You must be running AAPS Version 3.4.2.3 or later for this feature. + +The Basal Drift Fix is not enabled by default on AAPS. + +**To enable it:** + +1. Create an empty file named `omnipod_drift_compensation` (2) in the `extra` (1) subfolder of your phone [AAPS directory](#preferences-maintenance-settings). + + ![dash_drift_enable_file](../images/DASH_images/DASH_Drift/dash_drift_enable_file.png) + + ***NOTE:** Ensure you check in the AAPS settings where your AAPS Directory is, and that you placed the file in the correct one, a number of several have been caught out putting the file into the wrong folder.* + +2. Restart **AAPS**. This must be done for it to recognise the file is present and enable the drift compensation feature. +3. Please visit this [Github issue #4783](https://github.com/nightscout/AndroidAPS/issues/4783) and thumbs up the first post indicating you are using this feature, we need this data to help demonstrate the feature is widely used. Once there is significant community adoption the removal of the enable file will be possible, we appreciate your support here. ## 故障排除 -(omnipod-dash-delivery-suspended)= +(omnipod-dash-troubleshooting)= This section covers common known issues and solutions for Omnipod DASH use with AAPS. There is also [General Troubleshooting](../GettingHelp/GeneralTroubleshooting.md) section in the documentation that should be reviewed as it covers relevant topics for some Pod issues too. @@ -497,6 +532,9 @@ This section covers common known issues and solutions for Omnipod DASH use with For known issues with Bluetooth connections, dropouts of pump/pods, or activation and connection issues [Bluetooth Troubleshooting](../GettingHelp/BluetoothTroubleshooting.md) --- + +(omnipod-dash-delivery-suspended)= + ### Delivery suspended - 不再设有暂停按钮。 如需"暂停"储药器，可设置持续时间为X分钟的零值**临时基础率(TBR)**。 diff --git a/docs/CROWDIN/zh_CN/images/DASH_images/DASH_Drift/dash_drift_enable_file.png b/docs/CROWDIN/zh_CN/images/DASH_images/DASH_Drift/dash_drift_enable_file.png new file mode 100644 index 000000000000..917f90c264b5 Binary files /dev/null and b/docs/CROWDIN/zh_CN/images/DASH_images/DASH_Drift/dash_drift_enable_file.png differ diff --git a/docs/CROWDIN/zh_CN/images/DASH_images/DASH_Drift/dash_drift_pod_mgmt.png b/docs/CROWDIN/zh_CN/images/DASH_images/DASH_Drift/dash_drift_pod_mgmt.png new file mode 100644 index 000000000000..5b9a8485a40b Binary files /dev/null and b/docs/CROWDIN/zh_CN/images/DASH_images/DASH_Drift/dash_drift_pod_mgmt.png differ diff --git a/docs/CROWDIN/zh_CN/images/DASH_images/DASH_Drift/dash_drift_pod_stats_end.png b/docs/CROWDIN/zh_CN/images/DASH_images/DASH_Drift/dash_drift_pod_stats_end.png new file mode 100644 index 000000000000..5b268b517df0 Binary files /dev/null and b/docs/CROWDIN/zh_CN/images/DASH_images/DASH_Drift/dash_drift_pod_stats_end.png differ diff --git a/docs/CROWDIN/zh_CN/images/DASH_images/DASH_Drift/dash_drift_pod_stats_start.png b/docs/CROWDIN/zh_CN/images/DASH_images/DASH_Drift/dash_drift_pod_stats_start.png new file mode 100644 index 000000000000..2863168f7b19 Binary files /dev/null and b/docs/CROWDIN/zh_CN/images/DASH_images/DASH_Drift/dash_drift_pod_stats_start.png differ diff --git a/docs/CROWDIN/zh_CN/images/DASH_images/DASH_Drift/dash_drift_tab_pod_mgmt.png b/docs/CROWDIN/zh_CN/images/DASH_images/DASH_Drift/dash_drift_tab_pod_mgmt.png new file mode 100644 index 000000000000..30a5edb90b1d Binary files /dev/null and b/docs/CROWDIN/zh_CN/images/DASH_images/DASH_Drift/dash_drift_tab_pod_mgmt.png differ diff --git a/docs/CROWDIN/zh_CN/images/DASH_images/DASH_Drift/dash_drift_tdd.png b/docs/CROWDIN/zh_CN/images/DASH_images/DASH_Drift/dash_drift_tdd.png new file mode 100644 index 000000000000..28b7685fa5bd Binary files /dev/null and b/docs/CROWDIN/zh_CN/images/DASH_images/DASH_Drift/dash_drift_tdd.png differ diff --git a/docs/CROWDIN/zh_TW/CompatiblePumps/OmnipodDASH.md b/docs/CROWDIN/zh_TW/CompatiblePumps/OmnipodDASH.md index 8af54988f990..d2297bb2c32c 100644 --- a/docs/CROWDIN/zh_TW/CompatiblePumps/OmnipodDASH.md +++ b/docs/CROWDIN/zh_TW/CompatiblePumps/OmnipodDASH.md @@ -19,8 +19,8 @@ ## Omnipod DASH 已知的 AAPS 限制／問題 - Android 16 需要 AAPS 版本 3.3.2.1 或更新版本。 - 一般建議在 Android 14 或 16 上執行 AAPS。 Android 15 有許多社群回報的 [問題](https://github.com/nightscout/AndroidAPS/issues/3471)。 不過，若你在 Android 15 上執行，可能需要啟用藍牙配對（Bonding）才能成功註冊並使用 Pod；關於配對設定的更多資訊，請參閱 [一般疑難排解](../GettingHelp/GeneralTroubleshooting.md)。 -- 過於頻繁的基礎率更新，可能在 Omnipod Dash 上導致基礎胰島素輸注的問題。 使用微量注射時，請將間隔至少設為 5 分鐘以避免此問題。 -- Dash 僅支援以 0.05 U/h 步階設定的基礎率。 如果你在 AAPS 設定檔中嘗試以 0.01 的步階設定基礎率，即使 Pod 會將速率進位到 0.05 的步階，AAPS 也不會發出警示。 若你查看 POD MGMT/Pod History，會顯示已設定 0.05 的基礎率。 這也表示在 AAPS 中，DASH 允許的最低基礎率為 0.05 U/h。 +- Temporary Basal rate changes (which occur frequently when the loop is active, especially overnight) result in under-delivery of insulin. This is effectively a hardware limitation of the Omnipod DASH. The issue has been addressed in AAPS 3.4.2.3, but the functionality is currently opt-in. Follow the [Basal Drift Fix Instructions ](#omnipod-dash-Basal-drift-fix) instructions to enable it. For more information regarding the fix see [Github Issue - 4783](https://github.com/nightscout/AndroidAPS/issues/4783) for more info. +- Dash 僅支援以 0.05 U/h 步階設定的基礎率。 If you try to set Basal with 0.01 steps in your **AAPS profile**, AAPS will not give a warning even though the pod will round up the rate into 0.05 steps. 若你查看 POD MGMT/Pod History，會顯示已設定 0.05 的基礎率。 這也表示在 AAPS 中，DASH 允許的最低基礎率為 0.05 U/h。 - Pod 的註冊狀態會儲存在設定檔案中，如果你在 Pod 已註冊的狀態下匯出設定檔案。 接著更換為新的 Pod，然後再從先前匯出的設定還原，這會還原舊 Pod 的註冊狀態，並移除新 Pod 的註冊狀態。 因此建議每次註冊 Pod 後都匯出設定，以便在你的裝置出狀況時，能還原該 Pod 的註冊狀態。 - 當設定新的基礎率設定檔時，DASH 會先暫停輸注，然後再設定新的基礎率設定檔。 若通訊中斷或發生錯誤，基礎率設定檔不會自動重新開始。 詳細內容請參閱 [恢復胰島素輸注](#omnipod-dash-resuming-insulin-delivery) 章節。 - 如果已設定警示，且 Pod 即將到期，Pod 會持續發出嗶聲，直到將警示靜音為止；詳情請參閱 [靜音 Pod 警示](#omnipod-dash-silencing-pod-alerts)。 @@ -70,8 +70,8 @@ 若因任何原因 Pod 未收到新指令（例如 Pod 與 手機 距離過遠導致通訊中斷），Pod 會自動回復到您[**設定檔**](../SettingUpAaps/YourAapsProfile.md)中定義的預設基礎率。 ### **AAPS 的設定檔不支援 30 分鐘為單位的基礎率時間區段** -若您是 AAPS 新手並首次建立基礎率[**設定檔**](../SettingUpAaps/YourAapsProfile.md)，請注意：不支援以半小時為起點的基礎率。 例如：在您的 Omnipod PDM 上，若您有 1.1 單位、於 09:30 開始並持續 2 小時至 11:30 結束的基礎率，則無法在 **AAPS** 中完全複製相同的基礎**設定檔**。 -您需要將這個 1.1 單位的基礎率調整為 9:00–11:00 或 10:00–12:00 的時間範圍。 即使 DASH 硬體本身支援 30 分鐘增量的基礎率**設定檔**，**AAPS** 仍不支援此功能。 +若您是 AAPS 新手並首次建立基礎率[**設定檔**](../SettingUpAaps/YourAapsProfile.md)，請注意：不支援以半小時為起點的基礎率。 For example, on your Omnipod PDM, if you have a basal rate of 1.1 units which starts at 09:30 and has a duration of 2 hours ending at 11:30, it is not possible replicate this exact Basal **Profile** in **AAPS**. +You will need to change this 1.1 unit basal rate to a time range of either 9:00-11:00 or 10:00-12:00. 即使 DASH 硬體本身支援 30 分鐘增量的基礎率**設定檔**，**AAPS** 仍不支援此功能。 ### **AAPS 不支援 0 U/h 的設定檔基礎率** 雖然 DASH 支援零基礎率，**AAPS** 會以使用者**設定檔**的基礎率倍數來決定自動治療；因此無法在零基礎率下運作。 @@ -480,11 +480,46 @@ DASH 概覽標籤將顯示如下所述： * **SMS** - 短訊回報數值為 50+ 單位。 * **Nightscout** - 當超過 50 單位時，向 Nightscout 上傳數值為 50（版本 14.07 及更早版本）。 更新版本將在超過 50 單位時報告數值為 50+。 -(omnipod-dash-troubleshooting)= +(omnipod-dash-known-issues-workarounds)= + +## Known Issues Workarounds + +This section covers common workarounds and settings that need to be changed to enable a feature to work around a community reported issue that has a fix. 例如： the Basal drift enable process is documented here. + +(#omnipod-dash-Basal-drift-fix)= + +### Basal Drift Fix Instructions + +The Omnipod Dash pump has a limitation that can cause it to deliver less basal insulin than **AAPS** expects, see [Issue #4783](https://github.com/nightscout/AndroidAPS/issues/4783) for more technical details. + +The Dash uses an internal timer to determine when a basal pulse of 0.05 U is delivered. Once the timer interval elapses, the pulse is delivered. However, this timer is restarted whenever a basal rate change occurs e.g when **AAPS** sends a new Basal rate. + +When used in combination with looping, this leads to under-delivery of basal insulin, as the algorithm updates the basal rate on the pump frequently. + +The issue is most apparent during the night. During daytime operation, SMBs often result in a basal rate of 0, which masks the effect. In observed usage, this results in approximately 10% of the expected Total Daily Dose (TDD) not being delivered over a 24-hour period. Additionally, glucose targets are often not reached overnight, particularly after meals with prolonged glucose impact (e.g. pasta). + +***NOTE:** This issue is especially important to understand for people on very small dosages of insulin, Children for example.* + +#### Enable Basal Drift Fix in AAPS + +You must be running AAPS Version 3.4.2.3 or later for this feature. + +The Basal Drift Fix is not enabled by default on AAPS. + +**To enable it:** + +1. Create an empty file named `omnipod_drift_compensation` (2) in the `extra` (1) subfolder of your phone [AAPS directory](#preferences-maintenance-settings). + + ![dash_drift_enable_file](../images/DASH_images/DASH_Drift/dash_drift_enable_file.png) + + ***NOTE:** Ensure you check in the AAPS settings where your AAPS Directory is, and that you placed the file in the correct one, a number of several have been caught out putting the file into the wrong folder.* + +2. Restart **AAPS**. This must be done for it to recognise the file is present and enable the drift compensation feature. +3. Please visit this [Github issue #4783](https://github.com/nightscout/AndroidAPS/issues/4783) and thumbs up the first post indicating you are using this feature, we need this data to help demonstrate the feature is widely used. Once there is significant community adoption the removal of the enable file will be possible, we appreciate your support here. ## 問題排除 -(omnipod-dash-delivery-suspended)= +(omnipod-dash-troubleshooting)= 本節涵蓋使用 **AAPS** 搭配 Omnipod DASH 的常見已知問題與解決方案。 文件中也有 [一般疑難排解](../GettingHelp/GeneralTroubleshooting.md) 章節，請參閱，因為其中的相關主題也適用於部分 Pod 問題。 @@ -497,6 +532,9 @@ DASH 概覽標籤將顯示如下所述： 若遇到藍牙連線、幫浦 / Pods 中斷，或註冊與連線等已知問題，請參閱 [藍牙疑難排解](../GettingHelp/BluetoothTroubleshooting.md) --- + +(omnipod-dash-delivery-suspended)= + ### 暫停輸送 - 現在已無暫停按鈕。 如果你想要「暫停」藥量，你可以將臨時基礎率設置為零，持續 x 分鐘。 diff --git a/docs/CROWDIN/zh_TW/images/DASH_images/DASH_Drift/dash_drift_enable_file.png b/docs/CROWDIN/zh_TW/images/DASH_images/DASH_Drift/dash_drift_enable_file.png new file mode 100644 index 000000000000..917f90c264b5 Binary files /dev/null and b/docs/CROWDIN/zh_TW/images/DASH_images/DASH_Drift/dash_drift_enable_file.png differ diff --git a/docs/CROWDIN/zh_TW/images/DASH_images/DASH_Drift/dash_drift_pod_mgmt.png b/docs/CROWDIN/zh_TW/images/DASH_images/DASH_Drift/dash_drift_pod_mgmt.png new file mode 100644 index 000000000000..5b9a8485a40b Binary files /dev/null and b/docs/CROWDIN/zh_TW/images/DASH_images/DASH_Drift/dash_drift_pod_mgmt.png differ diff --git a/docs/CROWDIN/zh_TW/images/DASH_images/DASH_Drift/dash_drift_pod_stats_end.png b/docs/CROWDIN/zh_TW/images/DASH_images/DASH_Drift/dash_drift_pod_stats_end.png new file mode 100644 index 000000000000..5b268b517df0 Binary files /dev/null and b/docs/CROWDIN/zh_TW/images/DASH_images/DASH_Drift/dash_drift_pod_stats_end.png differ diff --git a/docs/CROWDIN/zh_TW/images/DASH_images/DASH_Drift/dash_drift_pod_stats_start.png b/docs/CROWDIN/zh_TW/images/DASH_images/DASH_Drift/dash_drift_pod_stats_start.png new file mode 100644 index 000000000000..2863168f7b19 Binary files /dev/null and b/docs/CROWDIN/zh_TW/images/DASH_images/DASH_Drift/dash_drift_pod_stats_start.png differ diff --git a/docs/CROWDIN/zh_TW/images/DASH_images/DASH_Drift/dash_drift_tab_pod_mgmt.png b/docs/CROWDIN/zh_TW/images/DASH_images/DASH_Drift/dash_drift_tab_pod_mgmt.png new file mode 100644 index 000000000000..30a5edb90b1d Binary files /dev/null and b/docs/CROWDIN/zh_TW/images/DASH_images/DASH_Drift/dash_drift_tab_pod_mgmt.png differ diff --git a/docs/CROWDIN/zh_TW/images/DASH_images/DASH_Drift/dash_drift_tdd.png b/docs/CROWDIN/zh_TW/images/DASH_images/DASH_Drift/dash_drift_tdd.png new file mode 100644 index 000000000000..28b7685fa5bd Binary files /dev/null and b/docs/CROWDIN/zh_TW/images/DASH_images/DASH_Drift/dash_drift_tdd.png differ