diff --git a/docs/CROWDIN/cs/CompatiblePumps/OmnipodDASH.md b/docs/CROWDIN/cs/CompatiblePumps/OmnipodDASH.md index 7fa50130d094..27ac0357bf28 100644 --- a/docs/CROWDIN/cs/CompatiblePumps/OmnipodDASH.md +++ b/docs/CROWDIN/cs/CompatiblePumps/OmnipodDASH.md @@ -18,7 +18,13 @@ These are the specifications of the **Omnipod DASH** ('DASH') and what different * On pod activation, **AAPS** will find and connect to a new DASH pod. * Expected range: 5-10 meters (YMMV). -WARNING: There are currently reported Bluetooth connection issues with the following combination of **AAPS** / DASH / Android 15. **AAPS** should not be used in combination with Android 15 and DASH unless the user has checked the following [**List**](https://docs.google.com/spreadsheets/u/1/d/e/2PACX-1vScCNaIguEZVTVFAgpv1kXHdsHl3fs6xT6RB2Z1CeVJ561AvvqGwxMhlmSHk4J056gMCAQE02sAWJvT/pubhtml?gid=683363241&single=true) and verified that their phone is not a known reported issue. **AAPS** is currently working to resolve this issue. +```{admonition} Android 15 +:class: warning + +There are currently reported Bluetooth connection issues with the following combination of **AAPS**: DASH + Android 15. +Please refrain from upgrading your phone to Android 15 unless you have checked the following [**list**](https://docs.google.com/spreadsheets/u/1/d/e/2PACX-1vScCNaIguEZVTVFAgpv1kXHdsHl3fs6xT6RB2Z1CeVJ561AvvqGwxMhlmSHk4J056gMCAQE02sAWJvT/pubhtml?gid=683363241&single=true) and verified that your phone is not a known reported issue. +If you experience frequent disconnection; try to enable Bond BT as described in: [**Bluetooth Issues**](../GettingHelp/GeneralTroubleshooting.md). +``` ## Hardware/Software Requirements @@ -37,7 +43,7 @@ The instructions below explain how to activate a new pod session. Wait to close **SAFETY FIRST** - you should not try to connect **AAPS** to a pod for the first time without having access to extra pods, insulin, and phone devices are a must have. -**Your Omnipod Dash PDM will become redundant after the AAPS Dash driver activates your pod.** Previously a user may have operated a PDM to send commands to your DASH. A DASH will only faciiliate a single device to send commands to communicate with it. Zařízení, které úspěšně aktivuje POD, je jediné, které může od tohoto okamžiku komunikovat s pumpou. This means that once you activate a DASH with your Android phone through the **AAPS**, **you will no longer be able to use your PDM with that pod**. The **AAPS** Dash driver in your Android phone is now your acting PDM. +**Your Omnipod Dash PDM will become redundant after the AAPS Dash driver activates your pod.** Previously a user may have operated a PDM to send commands to your DASH. A DASH will only faciiliate a single device to send commands to communicate with it. The device that successfully activates the pod is the only device allowed to communicate with it from that point forward. This means that once you activate a DASH with your Android phone through the **AAPS**, **you will no longer be able to use your PDM with that pod**. The **AAPS** Dash driver in your Android phone is now your acting PDM. *This does NOT mean you should throw away your PDM, it is recommended to keep it around as a backup and for emergencies, for instance when your phone gets lost or AAPS is not working correctly.* diff --git a/docs/CROWDIN/cs/CompatiblePumps/OmnipodEros.md b/docs/CROWDIN/cs/CompatiblePumps/OmnipodEros.md index 760738c4d660..74f189578ba4 100644 --- a/docs/CROWDIN/cs/CompatiblePumps/OmnipodEros.md +++ b/docs/CROWDIN/cs/CompatiblePumps/OmnipodEros.md @@ -43,7 +43,7 @@ These instructions will assume that you are starting a new pod session; if this **BEZPEČNOST PŘEDEVŠÍM** - nepokoušejte se používat zařízení v prostředí, ve kterém nedokážete snadno opravit případné chyby (dodatečné pody, inzulín, musíte mít k dispozici možnost nabití RileyLink a telefonu). -**Your Omnipod PDM will no longer work after the AAPS Omnipod driver activates your pod**. Dříve jste používali Omnipod PDM k odesílání příkazů do pumpy Omnipod Eros. Ale Omnipod Eros umožňuje připojení pouze jediného zařízení, se kterým komunikuje. Zařízení, které úspěšně aktivuje POD, je jediné, které může od tohoto okamžiku komunikovat s pumpou. This means that once you activate an Omnipod Eros pod with your RileyLink through the AAPS Omnipod driver, **you will no longer be able to use your PDM with your pod**. AAPS s ovladačem pro pumpu Omnipod a RileyLink představuje váš nový PDM. *This does NOT mean you should throw away your PDM, it is recommended to keep it around as a backup, and for emergencies with AAPS is not working correctly.* +**Your Omnipod PDM will no longer work after the AAPS Omnipod driver activates your pod**. Dříve jste používali Omnipod PDM k odesílání příkazů do pumpy Omnipod Eros. Ale Omnipod Eros umožňuje připojení pouze jediného zařízení, se kterým komunikuje. The device that successfully activates the pod is the only device allowed to communicate with it from that point forward. This means that once you activate an Omnipod Eros pod with your RileyLink through the AAPS Omnipod driver, **you will no longer be able to use your PDM with your pod**. AAPS s ovladačem pro pumpu Omnipod a RileyLink představuje váš nový PDM. *This does NOT mean you should throw away your PDM, it is recommended to keep it around as a backup, and for emergencies with AAPS is not working correctly.* **Můžete nakonfigurovat několik zařízení RileyLink, ale v každém okamžiku může být připojen k pumpě pouze jedno.** AAPS ovladač pro Omnipod umožňuje mít uložených více zařízení RileyLink současně, nicméně pouze jeden RileyLink může být použit pro aktuální komunikaci. diff --git a/docs/CROWDIN/cs/GettingHelp/GeneralTroubleshooting.md b/docs/CROWDIN/cs/GettingHelp/GeneralTroubleshooting.md index 5e97b4378d63..65bdf8d44488 100644 --- a/docs/CROWDIN/cs/GettingHelp/GeneralTroubleshooting.md +++ b/docs/CROWDIN/cs/GettingHelp/GeneralTroubleshooting.md @@ -37,14 +37,37 @@ Ignore it: More details, Install anyway. * [SMS commands](#SMSCommands-troubleshooting) -### Frequent bluetooth connection problems +### Frequent Bluetooth connection problems -This can happen with various pumps. Apart from excluding AAPS from any battery optimization, you can also exclude the system bluetooth app from battery optimization. This can help in some cases. Depending on the phone you use, you will find the bluetooth app differently. +#### Android 15 + +```{warning} +Developers are working on this issue impacting **AAPS** on some Samsung and Pixel phones. +``` + +After upgrading Android or moving to a recent phone, **AAPS** frequently loses Bluetooth connection to the pump. The problem disappears temporarily when restarting the phone. If the phone runs Android 15, you can try to enable the following: + +1) **Open preferences** by clicking the three-dot menu on the top right side of the home screen. + + +![Open preferences](../images/Pref2020_Open2.png) + +2. Scroll down and open the **Confirmation beeps** / **Advanced** submenu. Enable **Bond BT device on Android 15+**. + + ![BondBT](../images/troubleshooting/BondBT.png) + +3. If the pump asks for a pairing request, accept it. + +4. Restart your phone. + +#### Battery optimization + +This can happen with various pumps. Apart from excluding AAPS from any battery optimization, you can also exclude the system Bluetooth app from battery optimization. This can help in some cases. Depending on the phone you use, you will find the Bluetooth app differently. Here are examples how to find them on specific android phones. -#### Pixel phones (stock android) +##### Pixel phones (stock Android) * Go to the android settings, select "Apps". @@ -67,7 +90,7 @@ Here are examples how to find them on specific android phones. ![BT Battery optimization](../images/troubleshooting/pixel/04_btunrestricted.png) -#### Samsung phones +##### Samsung phones * Go to the android settings, select "Apps" diff --git a/docs/CROWDIN/cs/images/troubleshooting/BondBT.png b/docs/CROWDIN/cs/images/troubleshooting/BondBT.png new file mode 100644 index 000000000000..96b2fb272d90 Binary files /dev/null and b/docs/CROWDIN/cs/images/troubleshooting/BondBT.png differ diff --git a/docs/CROWDIN/cs/images/troubleshooting/samsung/01_BondBT_20250526.png b/docs/CROWDIN/cs/images/troubleshooting/samsung/01_BondBT_20250526.png new file mode 100644 index 000000000000..74c3525959ed Binary files /dev/null and b/docs/CROWDIN/cs/images/troubleshooting/samsung/01_BondBT_20250526.png differ diff --git a/docs/CROWDIN/cs/images/troubleshooting/samsung/02_BondBT_20250526.png b/docs/CROWDIN/cs/images/troubleshooting/samsung/02_BondBT_20250526.png new file mode 100644 index 000000000000..444013b29146 Binary files /dev/null and b/docs/CROWDIN/cs/images/troubleshooting/samsung/02_BondBT_20250526.png differ diff --git a/docs/CROWDIN/cs/images/troubleshooting/samsung/03_BondBT_20250526.png b/docs/CROWDIN/cs/images/troubleshooting/samsung/03_BondBT_20250526.png new file mode 100644 index 000000000000..9caa7a484581 Binary files /dev/null and b/docs/CROWDIN/cs/images/troubleshooting/samsung/03_BondBT_20250526.png differ diff --git a/docs/CROWDIN/cs/images/troubleshooting/samsung/04_BondBT_20250526.png b/docs/CROWDIN/cs/images/troubleshooting/samsung/04_BondBT_20250526.png new file mode 100644 index 000000000000..b25c1469f58e Binary files /dev/null and b/docs/CROWDIN/cs/images/troubleshooting/samsung/04_BondBT_20250526.png differ diff --git a/docs/CROWDIN/de/CompatiblePumps/MedtrumNano.md b/docs/CROWDIN/de/CompatiblePumps/MedtrumNano.md index 41fdcb42c5a3..71ae6deb1583 100644 --- a/docs/CROWDIN/de/CompatiblePumps/MedtrumNano.md +++ b/docs/CROWDIN/de/CompatiblePumps/MedtrumNano.md @@ -39,9 +39,9 @@ Diese Software ist Teil einer DIY-Lösung (Do It Yourself = Eigenbau) und kein k **Deine Pumpe wird auch dann Insulin abgeben, wenn es sie nicht mit AAPS verbunden ist**. Die Basalrate des aktiven AAPS Profils ist in der Patch-Pumpe hinterlegt. Eine funktionsfähiges AAPS, sendet Basalraten-Befehle, die maximal 120 Minuten abdecken. Sollte die Pumpe aus irgendeinem Grund keine neuen Befehle erhalten (z.B. weil die Pumpe und das Smartphone zu weit voneinander entfernt sind), wird die Pumpe auf die in der Pumpe hinterlegte Standardbasalrate zurückfallen, sobald die temporäre Basalrate endet. -**Basalraten-Profile mit 30-Minuten-Schritten werden in AAPS NICHT unterstützt.** Wenn Du AAPS als Neuling nutzt und zum ersten Mal Dein Basalprofil einrichtest, beachte bitte, dass Deine Basalraten im Profil nur zur vollen Stunde starten und 60 Minuten dauern. Basalraten, die zu einer halben Stunde beginnen und/oder 30 Minuten dauern, werden nicht unterstützt und führen zu Fehlern. Wenn Du zum Beispiel eine Basalrate von 1,1 Einheiten hast, die um 9:30 Uhr startet und zwei Stunden bis 11:30 Uhr läuft, wird dies nicht funktionieren. Du muss diese 1,1 IE Basalrate auf einen Zeitraum von entweder 9:00 - 11:00 Uhr oder 10:00 - 12:00 Uhr einstellen. Der in AAPS verwendete Algorithmus kann halbstündige Basalraten nicht verarbeiten, auch wenn die Hardware der Medtrum-Pumpe dies unterstützen könnte. +**Basalraten-Profile mit 30-Minuten-Schritten werden in AAPS NICHT unterstützt.** Wenn Du AAPS als Neuling nutzt und zum ersten Mal Dein Basalprofil einrichtest, beachte bitte, dass Deine Basalraten im Profil nur zur vollen Stunde starten und 60 Minuten dauern. Basalraten, die zu einer halben Stunde beginnen und/oder 30 Minuten dauern, werden nicht unterstützt und führen zu Fehlern. Wenn Du zum Beispiel eine Basalrate von 1,1 Einheiten hast, die um 9:30 Uhr startet und zwei Stunden bis 11:30 Uhr läuft, wird dies nicht funktionieren. 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. Der in AAPS verwendete Algorithmus kann halbstündige Basalraten nicht verarbeiten, auch wenn die Hardware der Medtrum-Pumpe dies unterstützen könnte. -Gleiches gilt auch für 'Null-Basalraten'. **Basalraten mit 0 IE/h werden in AAPS NICHT unterstützt**. AAPS benutzt Vielfache der im Profil hinterlegten Basalrate, um die benötigte Insulinmenge zu berechnen. Mit 'Null-Basalraten' funktioniert diese Berechnungn nicht, auch wenn die Metrum-Pumpe diese unterstützen könnte. Eine temporäre Null-Basalrate kann durch die Funktion PUMPE TRENNEN oder durch eine Kombination aus LOOP DEAKTIVIEREN/TEMP BASALRATE oder LOOP PAUSIEREN/TEMP BASALRATE erreicht werden. +Gleiches gilt auch für 'Null-Basalraten'. **Basalraten mit 0 IE/h werden in AAPS NICHT unterstützt**. AAPS benutzt Vielfache der im Profil hinterlegten Basalrate, um die benötigte Insulinmenge zu berechnen. Mit 'Null-Basalraten' funktioniert diese Berechnungn nicht, auch wenn die Metrum-Pumpe diese unterstützen könnte. A temporary zero basal rate can be achieved through the "Disconnect pump" function or through a combination of Disable Loop/Temp Basal Rate or Suspend Loop/Temp Basal Rate. ## Einrichtung diff --git a/docs/CROWDIN/de/CompatiblePumps/OmnipodDASH.md b/docs/CROWDIN/de/CompatiblePumps/OmnipodDASH.md index 397e4cdd76e5..39689b14ec23 100644 --- a/docs/CROWDIN/de/CompatiblePumps/OmnipodDASH.md +++ b/docs/CROWDIN/de/CompatiblePumps/OmnipodDASH.md @@ -18,7 +18,13 @@ Hier finden sich die besonderen Merkmale des **Omnipod DASH** („DASH“) und d * Bei Aktivierung des Pods wird **AAPS** den neuen DASH-Pod finden und sich mit ihm verbinden. * Reichweite für die BT-Verbindung: 5-10 Meter (je nach Umgebung). -WARNUNG: Derzeit werden Bluetooth-Verbindungsprobleme in der Kombination **AAPS** / DASH / Android 15 gemeldet. **AAPS** sollte nicht in der Kombination Android 15 mit DASH genutzt werden, es sei denn, Du hast die folgende [**Liste**](https://docs.google.com/spreadsheets/u/1/d/e/2PACX-1vScCNaIguEZVTVFAgpv1kXHdsHl3fs6xT6RB2Z1CeVJ561AvvqGwxMhlmSHk4J056gMCAQE02sAWJvT/pubhtml?gid=683363241&single=true) geprüft und Dein Smartphone ist dort nicht als problematisch aufgeführt. Das **AAPS**-Team arbeitet daran, dieses Problem zu beheben. +```{admonition} Android 15 +:class: warning + +There are currently reported Bluetooth connection issues with the following combination of **AAPS**: DASH + Android 15. +Please refrain from upgrading your phone to Android 15 unless you have checked the following [**list**](https://docs.google.com/spreadsheets/u/1/d/e/2PACX-1vScCNaIguEZVTVFAgpv1kXHdsHl3fs6xT6RB2Z1CeVJ561AvvqGwxMhlmSHk4J056gMCAQE02sAWJvT/pubhtml?gid=683363241&single=true) and verified that your phone is not a known reported issue. +If you experience frequent disconnection; try to enable Bond BT as described in: [**Bluetooth Issues**](../GettingHelp/GeneralTroubleshooting.md). +``` ## Hardware- und Software-Anforderungen @@ -31,59 +37,59 @@ WARNUNG: Derzeit werden Bluetooth-Verbindungsprobleme in der Kombination **AAPS* - **AAPS Version 3.0. oder neuer erstellt und installiert** mit der Anleitung aus dem Abschnitt [**AAPS erstellen**](../SettingUpAaps/BuildingAaps.md). * [**Kontinuierliche Glukosemessung (CGM)**](../Getting-Started/CompatiblesCgms.md) -In den folgenden Anweisungen wird erklärt, wie Du eine neue Pod-Sitzung aktiviert. Warte bis die aktuelle Pod-Sitzung fast abgelaufen ist, bevor Du versuchst **AAPS** mit einem neuen Pod zu verbinden. Sobald ein Pod „abgebrochen“ wurde, kann er nicht noch einmal genutzt werden und die Verbindung ist endgültig nicht wiederherstellbar. +The instructions below explain how to activate a new pod session. Wait to close to expiry of a current pod session before trying to connect **AAPS** with a new pod. Once a pod is is cancelled it cannot reused and the disconnection will be final. ## Bevor Du anfängst -**SICHERHEIT GEHT VOR** - Versuche nicht **AAPS** erstmalig mit einem Pod zu verbinden, ohne dass Du Ersatz-Pods in Reichweite hast. Insulin und ein Smartphone sind ebenfalls ein Muss. +**SAFETY FIRST** - you should not try to connect **AAPS** to a pod for the first time without having access to extra pods, insulin, and phone devices are a must have. -**Sobald AAPS Deinen Pod aktiviert hat, wird Dein Omnipod Dash PDM überflüssig.** Davor wurde der PDM möglicherweise zum Senden von Befehlen an den DASH genutzt. Ein DASH kann nur mit einem einzigen Gerät kommunizieren und über dieses Befehle senden. Das Gerät, das den Pod erfolgreich aktiviert, ist das einzige Gerät, das von diesem Zeitpunkt an mit ihm kommunizieren darf. Das bedeutet, dass, sobald Du einen DASH-Pod mit Deinem Smartphone über den **AAPS** DASH-Treiber aktiviert hast, **Du den PDM nicht mehr mit diesem Pod** verwenden kannst. Der **AAPS**-DASH Treiber in Deinem Android-Smartphone ist jetzt Dein PDM. +**Your Omnipod Dash PDM will become redundant after the AAPS Dash driver activates your pod.** Previously a user may have operated a PDM to send commands to your DASH. A DASH will only faciiliate a single device to send commands to communicate with it. The device that successfully activates the pod is the only device allowed to communicate with it from that point forward. This means that once you activate a DASH with your Android phone through the **AAPS**, **you will no longer be able to use your PDM with that pod**. The **AAPS** Dash driver in your Android phone is now your acting PDM. -*Dies bedeutet NICHT, dass Du Deinen PDM wegwerfen solltest. Es wird empfohlen, ihn als Backup zu behalten und für Notfälle, falls das Telefon verloren geht oder AAPS nicht korrekt funktioniert.* +*This does NOT mean you should throw away your PDM, it is recommended to keep it around as a backup and for emergencies, for instance when your phone gets lost or AAPS is not working correctly.* -**Dein Pod gibt auch dann Insulin ab, wenn keine AAPS-Verbindung besteht**. Die in Deinem aktuell aktiven **Profil** definierten Standard-Basalraten werden bei der Aktivierung auf den Pod übertragen. Eine funktionsfähiges **AAPS**, sendet Basalraten-Befehle, die maximal 120 Minuten abdecken. Wenn der Pod aus irgendeinem Grund keine neuen Befehle erhält (zum Beispiel, weil die Kommunikation aufgrund eines zu großen Abstandes zwischen Pod und Telefon verloren gegangen ist), fällt der Pod automatisch auf die Standard-Basalraten zurück. +**Your pod will not stop delivering insulin when it is not connected to AAPS**. Default basal rates are programmed on the pod on activation as defined in the current active **Profile**. As long as **AAPS** is operational it will send basal rate commands that run for a maximum of 120 minutes. 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. -**In AAPS-Profilen können 30-minütige Basalraten nicht hinterlegt werden**. Wenn Du noch neu im Thema **AAPS** bist und Dein Basalraten-**Profil** zum ersten Mal einrichtest, beachte bitte, dass Basalraten nur zur vollen Stunde beginnen können. Hast Du beispielsweise eine Basalrate von 1,1 IE, die um 09.30h startet und um 11:30h endet, wird es nicht möglich sein, diese so in **AAPS** zu übernehmen. Du muss diese 1,1 IE Basalrate auf einen Zeitraum von entweder 9:00 - 11:00 Uhr oder 10:00 - 12:00 Uhr einstellen. Auch wenn die DASH-Hardware 30-minütige-Segmente im Basalraten-**Profil** managen kann, unterstützt **AAPS** dieses Feature nicht. +**AAPS Profile does not support a 30 minute basal rate time frame** If you are new to **AAPS** and are setting up your basal rate **Profile** for the first time, please be aware that basal rates starting on a half-hour basis are not supported, and programmes on an hourly basis. For example, 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 im **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 support this feature. -Gleiches gilt auch für „Null-Basalraten“. **Basalraten mit 0 IE/h werden in AAPS NICHT unterstützt**. **AAPS** benutzt Vielfache der im **Profil** hinterlegten Basalrate, um die benötigte Insulinmenge zu berechnen. Mit „Null-Basalraten“ funktioniert diese Berechnung nicht, auch wenn der DASH diese unterstützt. Eine temporäre Null-Basalrate kann durch die Funktion PUMPE TRENNEN oder durch eine Kombination aus LOOP DEAKTIVIEREN/TEMP BASALRATE oder LOOP PAUSIEREN/TEMP BASALRATE erreicht werden. Die kleinste in **AAPS** mögliche Basalrate beträgt 0,05 IE/h. +**0U/h profile basal rates are NOT supported in AAPS** While the DASH does support a zero basal rate, since **AAPS** uses multiples of the user's **Profile** basal rate to determine automated treatment; it cannot function with a zero basal rate. A temporary zero basal rate can be achieved through the "Disconnect pump" function or through a combination of Disable Loop/Temp Basal Rate or Suspend Loop/Temp Basal Rate. The lowest basal rate allowed in **AAPS** is 0.05U/h. ## DASH in AAPS auswählen -Es gibt **zwei Wege**: +There are **two ways**: ### Option 1: Neue Installation -Bei der **AAPS**-Erstinstallation wird Dich der **Einrichtungsassistent** durch die wesentlichen **AAPS**-Funktionen und Installations-Anforderungen leiten. Wähle "DASH" aus, wenn Du die Pumpenauswahl erreichst. +When installing **AAPS** for the first time, the **Setup Wizard** will guide new users through key features and installation requirements for **AAPS**. Select “DASH” when you reach Pump selection. ![Enable_Dash_1](../images/DASH_images/Enable_Dash/Enable_Dash_1.png) -Falls Du unsicher sein solltest, kannst Du auch zunächst die „Virtuelle Pumpe“ und dann später, nach abgeschlossener **AAPS**-Einrichtung, „DASH“ wählen (siehe Option 2). +When in doubt you can also select “Virtual Pump” and select “DASH” later, after setting up **AAPS** (see option 2). ### Option 2: Der Konfigurations-Generator -Bei einer vorhandenen Installation von AAPS kannst Du **DASH** als Pumpe unter "Konfiguration" auswählen: +On an existing installation you can select the **DASH** pump from the Config builder: -Über das **Hamburger Menü** oben links unter **Konfiguration (1)** \ ➜\ **Pumpe** \ ➜ \ **Dash** \ ➜\ **Zahnrad (3)** über das **Auswahlfeld (2)** für **DASH**. +On the top-left hand corner **hamburger menu** select **Config Builder (1)**\ ➜\ **Pump**\ ➜\ **Dash**\ ➜\ **Settings Gear (3)** by selecting the **radio button (2)** titled **Dash**. -Wenn Du das **Kontrollkästchen (4)** neben dem **Zahnrad (3)** wählst, wird das DASH-Menü als Registerkarte im **AAPS**-Interface mit dem Titel **DASH** als eigener Tab angezeigt. Wenn Du dieses Kästchen aktivierst, wird der Zugriff auf die DASH-Befehle bei der Verwendung von **AAPS** erleichtert. +Selecting the **checkbox (4)** next to the **Settings Gear (3)** will allow the DASH menu to be displayed as a tab in the **AAPS** interface titled **DASH**. Checking this box will facilitate your access to the DASH commands when using **AAPS**. -**HINWEIS:** Eine schnellere Möglichkeit, zu den [**DASH-Einstellungen**](#dash-settings) zu gelangen, findest Du im Abschnitt DASH-Einstellungen weiter unten in diesem Dokument. +**NOTE:** A faster way to access the [**Dash settings**](#dash-settings) can be found below in the DASH settings section of this document. ![Enable_Dash_3](../images/DASH_images/Enable_Dash/Enable_Dash_3.png) ### Überprüfung der Omnipod-Treiberauswahl -Wenn Du das Kästchen (4) aktiviert hast und prüfen möchtest, ob Du den DASH in **AAPS** tatsächlich ausgewählt hast, **wische von der Übersicht aus nach links** und es sollte ein Tab **DASH** in **AAPS** zu sehen sein. Wenn diese Option nicht aktiviert ist, finden die DASH Registerkarte links oben im Hamburger-Menü. +To verify that you have selected the DASH in **AAPS**, if you have checked the box (4), **swipe to the left** from the **Overview** tab, where you will now see a **DASH** tab on **AAPS**. If this box is left unchecked, you’ll find the DASH tab in the hamburger menu upper left. ![Enable_Dash_4](../images/DASH_images/Enable_Dash/Enable_Dash_4.jpg) ## DASH Konfiguration -Bitte **wische nach links **zur **DASH** Registerkarte, wo du alle Pod Funktionen verwalten kannst (einige dieser Funktionen sind ohne aktive Pod Sitzung nicht aktiviert oder nicht sichtbar): +Please **swipe left** to the **DASH** tab where you will be able to manage all pod functions (some of these functions are not enabled or visible without an active pod session): -![Refresh_LOGO](../images/DASH_images/Refresh_LOGO.png) „Aktualisieren“ von Pod-Verbindungen und -Status, Abstellen von Alarmen, wenn der Pod piept +![Refresh_LOGO](../images/DASH_images/Refresh_LOGO.png) 'Refresh' pod connectivity and status, be able to silence pod alarms when the pod beeps -![POD_MGMT_LOGO](../images/DASH_images/POD_MGMT_LOGO.png) „Pod-Management“ (Aktivieren, Deaktivieren, Testsignal und Pod-Historie) +![POD_MGMT_LOGO](../images/DASH_images/POD_MGMT_LOGO.png) 'Pod Management' (Activate, Deactivate, Play test beep, and Pod history) ### Pod aktivieren @@ -98,9 +104,9 @@ Bitte **wische nach links **zur **DASH** Registerkarte, wo du alle Pod Funktione ![Activate_Pod_3](../images/DASH_images/Activate_Pod/Activate_Pod_3.png) ![Activate_Pod_4](../images/DASH_images/Activate_Pod/Activate_Pod_4.jpg) -Stelle sicher, dass der neue Pod und das Smartphone, auf dem **AAPS** läuft, nah beieinander liegen und klicke auf den Button **Weiter**. +Ensure that the new pod and the phone running **AAPS** are within close proximity of each other and click the **Next** button. -**HINWEIS**: wenn die Fehlermeldung _„Konnte keinen verfügbaren Pod für die Aktivierung finden“_ (das kann passieren) erscheint: keine Panik. Klicke auf den **Wiederholen-Button**. In den meisten Fällen wird die Aktivierung dann erfolgreich fortgesetzt. +**NOTE**: if the error message below pops up _'Could not find an available pod for activation'_ (this can happen), do not panic. Click on the **Retry** button. In most situations activation will continue successfully. ![Activate_Pod_3](../images/DASH_images/Activate_pod_error.png) @@ -140,16 +146,16 @@ Stelle sicher, dass der neue Pod und das Smartphone, auf dem **AAPS** läuft, na ​ ![Activate_Pod_15](../images/DASH_images/Activate_Pod/Activate_Pod_15.jpg) -Es ist zu empfehlen, NACH der Aktivierung des Pods die Einstellungen zu exportieren. Exportiere mit jedem Wechsel eines Pods und einmal im Monat die Einstellungen und kopiere die exportierte Datei in Deinen Cloudspeicher. Details hierzu findest Du in [**Erstellen und Wiederherstellen von Backups**](../Maintenance/ExportImportSettings.md). +It is good practice to export settings AFTER activating the pod. Export settings should be done at each pod change and once a month, copy the exported file to your internet drive. see [**Export settings Doc**](../Maintenance/ExportImportSettings.md). (OmnipodDASH-deactivate-pod)= ### Pod deaktivieren -Unter normalen Umständen beträgt die erwartete Lebensdauer eines Pods drei Tage (72 Stunden) und zusätzliche 8 Stunden nach der Pod-Ablaufwarnung und somit insgesamt 80 Stunden. +Under normal circumstances, the expected lifetime of a pod is three days (72 hours) and an additional 8 hours after the pod expiration warning for a total of 80 hours of pod usage. -Gehe wie folgt vor, um einen Pod zu deaktivieren (entweder vor dem Ablaufen der Nutzungsdauer oder wegen eines Pod-Fehlers): +To deactivate a pod (either from expiration or from a pod failure): 1. Gehe zur Registerkarte **DASH** und klicke auf **POD MGMT (1)** und dann auf dem **Pod Management** Bildschirm klicke auf den **Pod deaktivieren (2)** Button. @@ -180,9 +186,9 @@ Gehe wie folgt vor, um einen Pod zu deaktivieren (entweder vor dem Ablaufen der ### Insulinabgabe fortsetzen -**Hinweis**: Während eines **Profilwechsels**, muss der DASH vor dem Setzen eines neuen Basal-**Profils** die Insulinabgabe stoppen, da die Insulinabgabe unterbrochen sein kann. Lies [**Insulinabgabe unterbrochen**](#delivery-suspended) im Abschnitt Problembehandlung für weitere Details. +**Note**: During **Profile Switches**, DASH must suspend delivery before setting the new basal **Profile** as delivery can be suspended. Read [**Delivery suspended**](#delivery-suspended) in the troubleshooting section for more details. -Benutze diesen Befehl, um den aktiven, derzeit pausierten Pod anzuweisen, die Insulinabgabe fortzusetzen. Nachdem der Befehl erfolgreich verarbeitet wurde, wird die normale Insulinabgabe mit der aktuellen Basalrate fortgesetzt. Grundlage dafür ist das zu dieser Zeit aktive Basal**profil**. Der Pod akzeptiert dann wieder Befehle für Bolus, **TBR**und **SMB**. +Use this command to instruct the active, currently suspended pod to resume insulin delivery. After the command is successfully processed, insulin will resume normal delivery using the current basal rate based on the current time from the active basal **Profile**. The pod will again accept commands for bolus, **TBR**, and **SMB**. 1. Gehe zur Registerkarte **DASH** und stelle sicher, dass der **Pod Status (1)** **unterbrochen** anzeigt, drücke dann die **Abgabe fortsetzen (2)** Taste, um den aktuellen Pod anzuweisen, die normale Insulinabgabe fortzusetzen. Eine Nachricht **RESUME DELIVERY** wird im Feld **Pod Status (3)** angezeigt. @@ -198,9 +204,9 @@ Benutze diesen Befehl, um den aktiven, derzeit pausierten Pod anzuweisen, die In ### Pod Alarme stummschalten -*HINWEIS: Die 'Alarme stummschalten' Schaltfläche ist nur auf der Registerkarte **DASH** verfügbar, wenn der Alarm 'Pod Ablauf' oder 'niedriger Reservoirstand' ausgelöst wurde. Wenn die 'Alarme stummschalten' Schaltfläche nicht sichtbar ist und Du Pieptöne vom Pod hörst, versuche 'Aktualisieren' in der Registerkarte DASH.* +*NOTE - The SILENCE ALERTS button is only available on the **DASH** tab when the pod expiration or low reservoir alert has been triggered. If the SILENCE ALERTS button is not visible and you hear beep sounds from the pod, try to 'Refresh pod status'.* -In dem folgenden Prozess wird gezeigt, wie Warntöne bestätigt und stummgeschaltet werden können, die auftreten, wenn die Laufzeit des aktiven Pods den Grenzwert für die Warnung vor dem Ablauf von 72 Stunden (3 Tage) erreicht. Dieser Grenzwert für die Laufzeit ist unter **Stunden bis zum Podende** in den DASH-Einstellungen 'Alarme' definiert. Die maximale Nutzungsdauer eines Pods beträgt 80 Stunden (3 Tage und 8 Stunden), dennoch empfiehlt der Hersteller, 72 Stunden (3 Tage) nicht zu überschreiten. +The process below will show you how to acknowledge and dismiss pod beeps when the active pod time reaches the warning time limit before the pod expiration of 72 hours (3 days). This warning time limit is defined in the **Hours before shutdown** Dash alerts setting. The maximum life of a pod is 80 hours (3 days 8 hours), however Insulet recommends not exceeding the 72 hours (3 days) limit. 1. Wenn die definierte **Stunden bis zum Podende** Vorwarnzeit erreicht ist, gibt der Pod Warnungen aus, um Dir mitzuteilen, dass er sich seiner Ablaufzeit nähert und bald ein Wechsel des Pods erforderlich sein wird. Du kannst dies auf der Registerkarte **DASH** überprüfen; das **Pod läuft ab: (1)** Feld zeigt die genaue Zeit an, zu der der Pod ablaufen wird (72 Stunden nach der Aktivierung), und dieser Text wird **rot** angezeigt, wenn dieser Zeitpunkt überschritten ist. Unter dem Feld **aktive Pod-Warnungen (2)** wird die Statusmeldung **Pod läuft in Kürze ab** angezeigt. Dadurch wird auch die Schaltfläche **Alarme stummschalten (3)** angezeigt. @@ -221,11 +227,11 @@ In dem folgenden Prozess wird gezeigt, wie Warntöne bestätigt und stummgeschal ### Anzeige Pod-Historie -In diesem Abschnitt wird erklärt, wie Du Deine Pod-Historie überprüfen und nach verschiedenen Aktionskategorien filtern kannst. Mit dem Werkzeug 'Pod Historie' kannst Du die Aktionen und Ergebnisse deines jeweils aktiven Pod während dessen dreitägigem Lebenszyklus (72 - 80 Stunden) ansehen. +This section explains how to review your active pod history and filter by different action categories. The pod history tool allows you to view the actions and results committed to your currently active pod during its three days (72 - 80 hours) life. -Diese Funktion ist hilfreich bei der Überprüfung von Bolus-, TBR- und Basalraten-Befehlen, die an den Pod gesendet wurden. Die übrigen Kategorien sind hilfreich bei der Problembehebung und zur Bestimmung der Reihenfolge von Ereignissen, die zu einem Fehler geführt haben. +This feature is helpful in verifying boluses, TBRs and basal commands that were sent to the pod. The remaining categories are useful for troubleshooting issues and determining the order of events that occurred leading up to a failure. -*HINWEIS:* **Nur der letzte Befehl kann 'unsicher' sein**. Neue Befehle *werden nicht gesendet*, bis der **zuvor als 'unsicher' eingestufte entweder bestätigt oder abgelehnt wurde**. Der Weg unsichere Befehle zu beheben, ist den Pod Status zu **Aktualisieren**. +*NOTE:* **Only the last command can be uncertain**. New commands *will not be sent* until the **last 'uncertain' command becomes 'confirmed' or 'denied'**. The way to 'fix' uncertain commands is to **'refresh pod status'**. 1. Gehe zur Registerkarte **DASH** und klicke auf **POD MGMT (1)** und dann auf dem **Pod Management** Bildschirm klicke auf den **Pod Historie (2)** Button. @@ -246,9 +252,9 @@ Diese Funktion ist hilfreich bei der Überprüfung von Bolus-, TBR- und Basalrat ## Registerkarte DASH -Im Folgenden werden die Anordnung und die Bedeutung der Symbole und Statusfelder auf der Registerkarte **DASH** des AAPS-Hauptbildschims erläutert. +Below is an explanation of the layout and meaning of the icons and status fields on the **DASH** tab in the main AAPS interface. -*HINWEIS: Wenn in einem der Statusfelder der Registerkarte **DASH** die Meldung 'unsicher' erscheint, musst Du die Schaltfläche 'Aktualisieren' drücken, um sie zu löschen und den Pod-Status zu aktualisieren.* +*NOTE: If any message in the **DASH** tab status fields report (uncertain), then you will need to press the Refresh button to clear it and refresh the pod status.* ![DASH_Tab_1](../images/DASH_images/DASH_Tab/DASH_Tab_1.png) @@ -283,23 +289,23 @@ Im Folgenden werden die Anordnung und die Bedeutung der Symbole und Statusfelder ### Schaltflächen -![Refresh_Icon](../images/DASH_images/Refresh_LOGO.png) : Sendet einen Befehl an den aktiven Pod, um die Kommunikation zu aktualisieren. +![Refresh_Icon](../images/DASH_images/Refresh_LOGO.png) : Sends a refresh command to the active pod to update communication. * Verwende diese Option, um den Pod-Status zu aktualisieren und die Statusfelder zu erneuern, die den Text 'unsicher' enthalten. * Weitere Informationen findest Du im Abschnitt Fehlerbehebung. -![POD_MGMT_Icon](../images/DASH_images/POD_MGMT_LOGO.png) : Öffnet den Pod-Management Bildschirm. +![POD_MGMT_Icon](../images/DASH_images/POD_MGMT_LOGO.png) : Navigates to the Pod management menu. -![ack_alert_logo](../images/DASH_images/ack_alert_logo.png) : drücken, um die Pod-Alarme und Benachrichtigungen (Ende der Laufzeit, niedriges Reservoir) stummzuschalten. +![ack_alert_logo](../images/DASH_images/ack_alert_logo.png) : When pressed this will disable the pod alerts beeps and notifications (expiry, low reservoir..). * Der Button wird nur angezeigt, wenn die aktuelle Zeit des Pods nach dem Pod-Ablaufdatum liegt. * Nach erfolgreicher Bestätigung wird dieses Symbol nicht mehr angezeigt. -![RESUME_Icon](../images/DASH_images/DASH_tab_icons/RESUME_Icon.png) : setzt eine ausgesetzte Insulinabgabe im aktiven Pod fort. +![RESUME_Icon](../images/DASH_images/DASH_tab_icons/RESUME_Icon.png) : Resumes the currently suspended insulin delivery in the active pod. ### Pod Management Menu -Im Folgenden ist die Bedeutung der Symbole im **Pod Management**-Bildschirm zu sehen, die Du durch Drücken des **POD MGMT (1)** Buttons in der Registerkarte **DASH** erreichst. +Below is the meaning of the icons on the **Pod Management** menu accessed by pressing **POD MGMT (1)** button from the **DASH** tab. ![DASH_Tab_2](../images/DASH_images/Deactivate_Pod/Deactivate_Pod_1.jpg) @@ -314,25 +320,25 @@ Im Folgenden ist die Bedeutung der Symbole im **Pod Management**-Bildschirm zu s ## DASH-Einstellungen -Über das **Hamburger Menü** oben links unter **Konfiguration (1)** \ ➜\ **Pumpe** \ ➜ \ **DASH** \ ➜\ **Einstellungsrädchen (3)** über das **Auswahlfeld (2)** für **DASH**. Wenn Du das **Kontrollkästchen (4)** neben dem **Zahnrad (3)** aktivierst, wird das DASH-Menü als Registerkarte im **AAPS**-Interface mit dem Titel **DASH** als eigener Tab angezeigt. +The Dash driver settings are configurable from the top-left hand corner **hamburger menu** under **Config Builder (1)**\ ➜\ **Pump**\ ➜\ **Dash**\ ➜\ **Settings Gear (3)** by selecting the **radio button (2)** titled **Dash**. Selecting the **checkbox (4)** next to the **Settings Gear (3)** will allow the Dash menu to be displayed as a tab in the **AAPS** interface titled **DASH**. ![Dash_settings_1](../images/DASH_images/Enable_Dash/Enable_Dash_3.png) -**HINWEIS:** Einen schnelleren Zugriff auf die **DASH-Einstellungen** erlaubt das **3-Punkt-Menü (1)** in der oberen rechten Ecke der Registerkarte **DASH** und die Auswahl **DASH-Einstellungen (2)** aus dem Dropdown-Menü. +**NOTE:** A faster way to access the **Dash settings** is by accessing the **3 dot menu (1)** in the upper right hand corner of the **DASH** tab and selecting **Dash preferences (2)** from the dropdown menu. ![Dash_settings_3](../images/DASH_images/Dash_settings/Dash_settings_3.png) -Die Einstellungen sind nach Gruppen sortiert unten aufgelistet. Du kannst die meisten der Einstellungen über einen Kippschalter aktivieren oder deaktivieren: +The settings groups are listed below; you can enable or disable via a toggle switch for most entries described below: -*HINWEIS: Ein Sternchen (\*) bedeutet, dass "aktiviert" der Standardwert für eine Einstellung ist.* +*NOTE: An asterisk (\*) denotes the default setting is enabled.* ### Bestätigungstöne ![Dash_settings_4](../images/DASH_images/Dash_settings/Dash_settings_4.jpg) -Bestätigt mit Signaltönen des Pods die Abgabe und Änderung von Bolus, Basalrate, SMB und TBR. +Provides confirmation beeps from the pod for bolus, basal, SMB, and TBR delivery and changes. * **Bolus-Piep aktiviert:** Aktiviert oder deaktiviert Bestätigungstöne bei Abgabe eines Bolus. * **Basal-Piep aktiviert:** Aktiviert oder deaktiviert Bestätigungstöne bei Einstellung einer neuen, Abbruch der aktiven oder Änderung der aktuellen Basalrate. @@ -343,9 +349,9 @@ Bestätigt mit Signaltönen des Pods die Abgabe und Änderung von Bolus, Basalra ![Dash_settings_5](../images/DASH_images/Dash_settings/Dash_settings_5.jpg) -Einstellungen für **AAPS**-Alarme für Ablauferinnerung, Zeit bis Pod-Ende und niedrigen Reservoirstand basierend auf den definierten Schwelleneinheiten. +Provides **AAPS** alerts for pod expiration, shutdown, low reservoir based on the defined threshold units. -*Beachte, dass eine AAPS-Benachrichtigung IMMER für jeden Alarm nach der ersten Kommunikation mit dem Pod ausgegeben wird, da der Alarm ausgelöst wurde. Wenn Du die Benachrichtigung löschst, wird der Alarm NICHT gelöscht, AUSSER wenn die automatische Bestätigung von Pod-Alarmen aktiviert ist. Um den Alarm MANUELL zu löschen, musst Du auf der Registerkarte **DASH** den **Alarm stummschalten** Button drücken.* +*Note an AAPS notification will ALWAYS be issued for any alert after the initial communication with the pod since the alert was triggered. Dismissing the notification will NOT dismiss the alert UNLESS automatically acknowledge Pod alerts is enabled. To MANUALLY dismiss the alert you must visit the **DASH** tab and press the **Silence ALERTS button**.* * **Ablauferinnerung aktiviert:** Aktiviere oder deaktiviere die Pod-Ablauferinnerung, die ausgelöst wird, wenn die festgelegte Anzahl von Stunden vor dem Podende erreicht ist. * **Stunden bis zum Podende:** Legt die Anzahl der Stunden vor der Abschaltung des aktiven Pods fest, die den Alarm zur Pod-Ablauferinnerung auslöst. @@ -356,9 +362,9 @@ Einstellungen für **AAPS**-Alarme für Ablauferinnerung, Zeit bis Pod-Ende und ![Dash_settings_6](../images/DASH_images/Dash_settings/Dash_settings_6.jpg) -Im Benachrichtigungsabschnitt kannst Du für den Fall, dass nicht klar ist, ob TBR, SMB, Bolus oder eine Unterbrechnung der Insulinabgabe erfolgreich ausgeführt wurden, entsprechende Benachrichtigungen und akustischen Smartphone-Warnungen aktivieren. +The Notification section allows the user to so select their preferred notifications and audible phone alerts when it is uncertain if TBR, SMB, or bolus, and delivery suspended events were successful. -*HINWEIS: Dies sind nur Benachrichtigungen, es werden keine akustischen Signale ausgegeben.* +*NOTE: These are notifications only, no audible beep alerts are made.* * **Ton für unsichere TBR-Benachrichtigung aktiviert:** Aktiviere oder deaktiviere diese Einstellung, um einen akustischen Alarm und eine visuelle Benachrichtigung auszulösen, wenn **AAPS** unsicher ist, ob eine TBR erfolgreich gesetzt wurde. * **Ton für unsichere SMB-Benachrichtigung aktiviert:** Aktiviere oder deaktiviere diese Einstellung, um einen akustischen Alarm und eine visuelle Benachrichtigung auszulösen, wenn **AAPS** unsicher ist, ob ein SMB erfolgreich abgegeben wurde. @@ -367,7 +373,7 @@ Im Benachrichtigungsabschnitt kannst Du für den Fall, dass nicht klar ist, ob T ## Aktionen (AKT) Tab -Diese Registerkarte ist in der **AAPS**-Dokumentation gut beschrieben, aber es gibt einige Punkte auf dieser Registerkarte, die sich speziell darauf beziehen, wie sich der DASH von schlauchbasierten Pumpen unterscheidet, insbesondere nach dem Anbringen eines neuen Pods. +This tab is well documented in the main**AAPS**documentation but there are a few items on this tab that are specific to how the DASH differs from tube based pumps, especially after the processes of applying a new pod. 1. Gehe von der **AAPS**-Übersicht zur Registerkarte **Aktionen (AKT)**. @@ -379,12 +385,12 @@ Diese Registerkarte ist in der **AAPS**-Dokumentation gut beschrieben, aber es g **Insulin Level** -Der angezeigte Insulinlevel ist der vom DASH gemeldete Betrag der verbleibenden Einheiten. Der Pod meldet allerdings den tatsächlichen Insulinlevel erst dann, wenn er unter 50 Einheiten liegt. Bis dahin wird „Über 50 Einheiten“ angezeigt. Die gemeldete Menge ist nicht genau: Wenn der Pod „leer“ meldet, wird das Reservoir in den meisten Fällen noch einige zusätzliche Einheiten Insulin enthalten. Auf der Registerkarte DASH wird die Übersicht wie unten beschrieben angezeigt: +Insulin level displayed is the amount reported by DASH. However, the pod only reports the actual insulin reservoir level when it is below 50 units. Until then “Above 50 units” will be displayed. The amount reported is not exact: when the pod reports ‘empty’ in most cases the reservoir will still have some additional units of insulin left. The DASH overview tab will display as described the below: * **Mehr als 50 IE verbleibend** - Der Pod meldet mehr als 50 Einheiten im Reservoir. * **Unter 50 Einheiten** - Die Menge an Insulin, die noch im Reservoir vorhanden ist, wie vom Pod gemeldet. -Sonstiges +Additional note: * **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. @@ -402,43 +408,43 @@ Sonstiges - Wenn **AAPS** die Abgabe nicht alleine fortsetzen kann (dies geschieht, wenn der Pod nicht erreichbar ist, der Ton stumm geschaltet ist, etc.), beginnt der Pod für 3 Minuten jede Minute viermal zu piepen. Das wird, wenn die Abgabe für mehr als 20 Minuten ausgesetzt ist, alle 15 Minuten wiederholt. * Für unbestätigte Befehle sollte "Aktualisieren" des Podstatus diese bestätigen oder ablehnen. -**Hinweis:** Wenn Du Pieptöne vom Pod hörst, kannst Du nicht davon ausgehen, dass die Insulinabgabe ohne Überprüfung im Smartphone fortgesetzt wird. Die Abgabe könnte weiterhin ausgesetzt bleiben, **also musst Du prüfen, was los ist!** +**Note:** When you hear beeps from the pod, do not assume that delivery will continue without checking the phone, delivery might stay suspended, **so you need to check !** ### Pod Fehler -Pods fallen gelegentlich aus unterschiedlichen Gründen aus, u. a. wegen Hardwareproblemen mit dem Pod selbst. Am besten ist es, diese nicht bei Insulet anzugeben, da AAPS kein zugelassener Anwendungsfall ist. Eine Liste der Fehlercodes [**findet sich hier**](https://github.com/openaps/openomni/wiki/Fault-event-codes), um die Ursache zu ermitteln. +Pods fail occasionally due to a variety of issues, including hardware issues with the Pod itself. It is best practice not to call these into Insulet, since AAPS is not an approved use case. A list of fault codes can be [**found here**](https://github.com/openaps/openomni/wiki/Fault-event-codes) to help determine the cause. ### Verhindere Pod Fehler 49 -Dieser Fehler hängt mit einem fehlerhaften Pod-Status für einen Befehl oder einem Fehler während der Insulinabgabe zusammen. Dies ist der Fall, wenn der AAPS-Treiber und der Pod unterschiedliche Angaben zum aktuellen Status haben. The Pod (out of a built-in safety measure) then reacts with an unrecoverable error code 49 (0x31) ending up with what is know as a “screamer”: the long irritating beep that can only be stopped by punching a hole at the appropriate location at the back of the Pod. Der genaue Ursprung eines „Pod Fehlers 49“ ist oft schwer zu ermitteln. Situationen, die für das Auftreten dieses Fehlers vermutet werden (z.B. bei einem Absturz der Anwendung, beim Ausführen einer Entwicklungsversion oder bei einer Neuinstallation). +This failure is related to an incorrect pod state for a command or an error during an insulin delivery command. This is when the driver and Pod disagree on the actual state. The Pod (out of a built-in safety measure) then reacts with an unrecoverable error code 49 (0x31) ending up with what is know as a “screamer”: the long irritating beep that can only be stopped by punching a hole at the appropriate location at the back of the Pod. The exact origin of a “49 pod failure” often is hard to trace. In situations that are suspected for this failure to occur (for instance on application crashes, running a development version or re-installation). ### Pumpe nicht erreichbar Alarme -Wenn für eine voreingestellte Zeitspanne keine Kommunikation mit dem Pod hergestellt werden kann, wird eine „Pumpe nicht erreichbar“ Alarmmeldung angezeigt. Pump nicht erreichbar Alarme können über das Drei-Punkte-Menü oben rechts konfiguriert werden. Wählen Sie **Einstellungen** \ ➜ \ **Lokale Alarme** \ ➜ \ ** Grenzwert Pumpe ist nicht erreichbar [min]**. Empfohlener Wert ist eine Alarmierung nach **120** Minuten. +When no communication can be established with the pod for a preconfigured time a “Pump unreachable” alert will be raised. Pump unreachable alerts can be configured by going to the top right-hand side three-dot menu, selecting **Preferences**\ ➜\ **Local Alerts**\ ➜\ **Pump unreachable threshold [min]**. Recommended value is alerting after **120** minutes. ### Exporteinstellungen -Durch den Export der **AAPS**-Einstellungen kannst Du alle Deine Einstellungen - und vielleicht noch wichtiger - alle Deine Objectives (Ziele) wiederherstellen. Es kann passieren, dass die Einstellungen in der „letzten bekannten funktionierenden Fassung“ wieder hergestellt werden müssen, etwa nach der Deinstallation/Neuinstallation von **AAPS** oder im Falle eines Smartphone-Verlustes. +Exporting **AAPS** settings enables you to restore all your settings, and maybe more importantly, all your Objectives. You may need to restore settings to the “last known working situation” or after uninstalling/reinstalling **AAPS** or in case of phone loss, reinstalling on the new phone. -Hinweis: Die Informationen des aktiven Pod sind in den exportierten Einstellungen enthalten. Wenn Du eine „alte“ Exportdatei importierst, wird Dein aktueller Pod „sterben“. Es gibt hierzu keine Alternative. In einigen Fällen (wie bei einem _geplanten_ Austausch Deines Smartphones) musst Du unter Umständen die exportierte Datei verwenden, um **AAPS**-Einstellungen wiederherzustellen, **um so den aktuell aktiven Pod** weiter nutzen zu können. In diesem Fall ist es wichtig, nur die zuletzt exportierte Einstellungsdatei zu verwenden, die den aktuell aktiven Pod enthält. +Note: The active pod information is included in the exported settings. If you import an "old" exported file, your actual pod will "die". There is no other alternative. In some cases (like a _programmed_ phone change), you may need to use the exported file to restore **AAPS'** settings **while keeping the current active Pod**. In this case it is important to only use the recently exported settings file containing the pod currently active. -**Es ist eine gute Idee, einen Export sofort nach der Aktivierung eines Pods durchzuführen.** Auf diese Weise wirst Du immer in der Lage sein, die Verbindung den aktuell aktiven Pod im Falle eines Problems wiederherzustellen. Zum Beispiel, wenn Du auf ein anderes Smartphone wechseln willst. +**It is good practice to do an export immediately after activating a pod**. This way you will always be able to restore the current active pod in case of a problem. For instance when moving to another backup phone. -Kopiere die exportierten Einstellungen regelmäßig an einen sicheren Ort (z. B. in der Cloud), der bei Bedarf von jedem Telefon aus zugänglich ist (z. B. im Falle eines Telefonverlustes oder dem Rücksetzen auf die Werkseinstellung des aktuellen Telefons). +Regularly copy your exported settings to a safe place (as a cloud drive) that can be accessible by any phone when needed (e.g. in case of a phone loss or factory reset of the actual phone). ### Importeinstellungen -**WARNUNG** Bitte beachte, dass durch das Importieren von Einstellungen möglicherweise ein veralteter Pod-Status importiert wird. Dadurch besteht die Gefahr, dass der aktive Pod eingebüßt wird! (siehe **Exporteinstellungen**). Es ist besser, dies nur dann auszuprobieren, wenn keine anderen Optionen verfügbar sind. +**WARNING** Please note that importing settings will possibly import an outdated Pod status. As a result, there is a risk of losing the active Pod! (see **Exporting Settings**). It is better to only try it when no other options are available. -Wenn Du die Einstellungen mit einem aktiven Pod importierst, stelle sicher, dass der Export ebenfalls mit diesem Pod durchgeführt wurde. +When importing settings with an active Pod, make sure the export was done with the currently active pod. -**Importieren während ein Pod aktiv ist:** (Du riskierst den Pod!) +**Importing while on an active Pod:** (you risk losing the Pod!) 1. Stelle sicher, dass Du Einstellungen importierst, die kürzlich mit dem aktuell aktiven Pod exportiert wurden. 2. Einstellungen importieren 3. Alle Voreinstellungen kontrollieren. -**Importieren ohne aktiven Pod** +**Importing (no active Pod session)** 1. Importieren aller kürzlichen Exporte sollte funktionieren (siehe oben) 2. Einstellungen importieren @@ -447,15 +453,15 @@ Wenn Du die Einstellungen mit einem aktiven Pod importierst, stelle sicher, dass ### Importieren von Einstellungen, die den Pod-Status von einem inaktiven Pod enthalten -Wenn Du Einstellungen für einen mittlerweile inaktiven Pod importierst, wird AAPS versuchen sich mit diesem Pod zu verbinden. Dies wird logischerweise scheitern. Du kannst in dieser Situation keinen neuen Pod aktivieren. +When importing settings containing data for a Pod that is no longer active, AAPS will try to connect with it, which will obviously fail. You can not activate a new Pod in this situation. -Um die alte Pod-Sitzung zu löschen, „versuche“ den Pod zu deaktivieren. Die Deaktivierung wird fehlschlagen. Wähle "Wiederholen". Nach der zweiten oder dritten Wiederholung erhälst Du die Möglichkeit, den Pod zu entfernen. Sobald der alte Pod gelöscht ist, kannst Du einen neuen Pod aktivieren. +To remove the old pod session “try” to de-activate the Pod. The de-activation will fail. Select “Retry”. After the second or third retry you will get the option to remove the pod. Once the old pod is removed you will be able to activate a new pod. ### Neuinstallation von AAPS -Beim Deinstallieren von **AAPS** verlierst Du alle Einstellungen, Objectives (Ziele) und die laufende Pod-Sitzung. Um sie wiederherzustellen, stelle sicher, dass Du eine kürzlich exportierte Einstellungsdatei zur Verfügung hast! +When uninstalling**AAPS** you will lose all your settings, objectives and the current Pod session. To restore them make sure you have a recent exported settings file available! -Wenn ein Pod aktiv ist, stelle sicher, dass Du einen Export für die aktuelle Pod-Sitzung hast oder Du wirst den aktuell aktiven Pod durch das Importieren der älteren Einstellungen verlieren. +When on an active Pod, make sure that you have an export for the current pod session or you will lose the currently active pod when importing older settings. 1. Exportiere deine Einstellungen und bewahre eine Kopie an einem sicheren Ort auf. 2. Deinstalliere **AAPS** und starte Dein Smartphone neu. @@ -467,7 +473,7 @@ Wenn ein Pod aktiv ist, stelle sicher, dass Du einen Export für die aktuelle Po ### AAPS auf eine neuere Version aktualisieren -In den meisten Fällen ist eine Deinstallation nicht erforderlich. Du kannst eine „in-place“ Installation durchführen, indem Du die Installation für die neue Version startest. Dies ist auch möglich, wenn ein Pod aktiv ist. +In most cases there is no need to uninstall. You can do an “in-place” install by starting the installation for the new version. This is also possible when on an active Pod session. 1. Exportiere Deine Einstellungen. 2. Installiere die neue **AAPS**-Version. @@ -477,7 +483,7 @@ In den meisten Fällen ist eine Deinstallation nicht erforderlich. Du kannst ein ### Omnipod-Treiberwarnungen -Bitte beachte, dass der Omnipod-Treiber auf der Registerkarte **DASH** eine Vielzahl eindeutiger Warnungen anzeigt. Die meisten davon sind informativ und können ignoriert werden, während einige dem Benutzer eine Aktion vorschlagen, um die Ursache für die ausgelöste Warnung zu beheben. Im Folgenden findest du eine Zusammenfassung der wichtigsten Warnmeldungen, die dir begegnen können: +Please note that the Omnipod Dash driver presents a variety of unique alerts on the **Overview tab**, most of them are informational and can be dismissed while some provide the user with an action to take to resolve the cause of the triggered alert. A summary of the main alerts that you may encounter is listed below: * Keine aktive Pod-Sitzung erkannt. Dieser Alarm kann vorübergehend durch Drücken von **Schlummern** deaktiviert werden, wird aber weiterhin ausgelöst, solange kein neuer Pod aktiviert wurde. Einmal aktiviert, wird dieser Alarm automatisch ausgeschaltet. * Pod unterbrochen Hinweis, dass der Pod angehalten wurde. @@ -487,7 +493,7 @@ Bitte beachte, dass der Omnipod-Treiber auf der Registerkarte **DASH** eine Viel ## Wo ich Hilfe zum DASH finde -Die gesamte Entwicklungsarbeit für den DASH wird von der Community durch **Freiwillige** geleistet; bitte berücksichtige das und gehe durch die folgenden Schritte bevor Du um Hilfe bittest: +All of the development work for the DASH is done by the community on a **volunteer** basis; please keep this in mind and use the following guidelines before requesting assistance: - **Level 0:** Lies den entsprechenden Abschnitt dieser Dokumentation um sicherzustellen, dass du verstehst, wie die Funktion, mit der Du Schwierigkeiten hast, funktionieren soll. - **Level 1:** Wenn Du immer noch Probleme, die Du mit diesem Dokument nicht lösen kannst, haben solltest, gehe **Discord-**Kanal *#AAPS*. Nutze dazu [diesen Einladungslink ](https://discord.gg/4fQUWHZ4Mw). diff --git a/docs/CROWDIN/de/CompatiblePumps/OmnipodEros.md b/docs/CROWDIN/de/CompatiblePumps/OmnipodEros.md index 43d90ffecbfd..5c3774578081 100644 --- a/docs/CROWDIN/de/CompatiblePumps/OmnipodEros.md +++ b/docs/CROWDIN/de/CompatiblePumps/OmnipodEros.md @@ -43,7 +43,7 @@ Diese Anleitung geht davon aus, dass Du eine neue Pod-Sitzung startest. Falls di **Sicherheit geht vor** - Stelle sicher, dass Du auf eventuell auftretende Fehler reagieren kannst, bevor Du diesen Prozess beginnst: zusätzliche Pods, Insulin, geladener RileyLink und Smartphone mit vollem Akku sind unbedingt notwendig. -**Dein Omnipod PDM funktioniert nicht mehr, wenn der AAPS Omnipod Treiber Deinen Pod aktiviert hat**. Bisher hast Du Deinen Omnipod PDM verwendet, um Befehle an Deinen Omnipod Eros Pod zu senden. Ein Omnipod Eros Pod kann sich nur mit einem einzigen Gerät verbinden. Das Gerät, das den Pod erfolgreich aktiviert, ist das einzige Gerät, das von diesem Zeitpunkt an mit ihm kommunizieren darf. Dies bedeutet, dass, sobald Du einen Omnipod Eros Pod mit Deinem RileyLink über den AAPS Omnipod Treiber aktiviert hast, **wirst Du Deinen PDM nicht mehr mit diesem Pod** verwenden können. Der AAPS Omnipod Treiber mit dem RileyLink ist dann Dein aktiver PDM. *Dies bedeutet NICHT, dass Du Deinen PDM wegwerfen solltest. Es wird empfohlen, ihn als Backup zu behalten und für Notfälle, falls AAPS nicht korrekt funktioniert.* +**Dein Omnipod PDM funktioniert nicht mehr, wenn der AAPS Omnipod Treiber Deinen Pod aktiviert hat**. Bisher hast Du Deinen Omnipod PDM verwendet, um Befehle an Deinen Omnipod Eros Pod zu senden. Ein Omnipod Eros Pod kann sich nur mit einem einzigen Gerät verbinden. The device that successfully activates the pod is the only device allowed to communicate with it from that point forward. Dies bedeutet, dass, sobald Du einen Omnipod Eros Pod mit Deinem RileyLink über den AAPS Omnipod Treiber aktiviert hast, **wirst Du Deinen PDM nicht mehr mit diesem Pod** verwenden können. Der AAPS Omnipod Treiber mit dem RileyLink ist dann Dein aktiver PDM. *Dies bedeutet NICHT, dass Du Deinen PDM wegwerfen solltest. Es wird empfohlen, ihn als Backup zu behalten und für Notfälle, falls AAPS nicht korrekt funktioniert.* **Du kannst mehrere RileyLinks konfigurieren, aber nur ein RileyLink kann gleichzeitig mit einem Pod kommunizieren.** Der AAPS Omnipod Treiber unterstützt die Möglichkeit, mehrere RileyLinks in der RileyLink-Konfiguration hinzuzufügen, jedoch kann nur ein RileyLink gleichzeitig für das Senden und Empfangen der Kommunikation ausgewählt werden. @@ -191,7 +191,7 @@ Bevor Du einen Pod aktivieren kannst, stelle sicher, dass Du Deine RileyLink-Ver Unter normalen Umständen beträgt die Lebensdauer eines Pods drei Tage (72 Stunden) und zusätzlich 8 Stunden nach der Pod-Ablaufwarnung und somit insgesamt 80 Stunden. -Gehe wie folgt vor, um einen Pod zu deaktivieren (entweder vor dem Ablaufen der Nutzungsdauer oder wegen eines Pod-Fehlers): +To deactivate a pod (either from expiration or from a pod failure): 1. Navigiere zur Registerkarte **Omnipod (POD)** und klicke auf den **POD MGMT (1)** Button und dann im **Pod Management** Screen klicke auf den **Pod deaktivieren (2)** Button. @@ -245,7 +245,7 @@ Verwende diesen Befehl, um den aktiven Pod in den Status 'unterbrochen' zu verse #### Insulinabgabe fortsetzen -Benutze diesen Befehl, um den aktiven, derzeit pausierten Pod anzuweisen, die Insulinabgabe fortzusetzen. Nachdem der Befehl erfolgreich verarbeitet wurde, wird die normale Insulinabgabe mit der aktuellen Basalrate fortgesetzt. Grundlage dafür ist das aktive Basalprofil zur aktuellen Uhrzeit. Der Pod akzeptiert wieder Befehle für Bolus, TBR und SMB. +Use this command to instruct the active, currently suspended pod to resume insulin delivery. Nachdem der Befehl erfolgreich verarbeitet wurde, wird die normale Insulinabgabe mit der aktuellen Basalrate fortgesetzt. Grundlage dafür ist das aktive Basalprofil zur aktuellen Uhrzeit. Der Pod akzeptiert wieder Befehle für Bolus, TBR und SMB. 1. Gehe zum Tab **Omnipod (POD)** und stelle sicher, dass das **Pod Status (1)** Feld zeigt **Suspended**, drücke dann den **Weiterlieferung (2)** Button, um den Prozess zu starten und den aktuellen Pod anzuweisen, die normale Insulinlieferung wieder fortzusetzen. Eine Nachricht **RESUME DELIVERY** wird im Feld **Pod Status (3)** angezeigt und signalisiert, dass der RileyLink den Befehl aktiv an den suspendierten Pod sendet. @@ -574,7 +574,7 @@ Die Omnipod Treibereinstellungen sind aus der oberen linken Ecke **Hamburger Men ![Omnipod_Settings_2](../images/omnipod/Omnipod_Settings_2.png) -Die Einstellungen sind nach Gruppen sortiert unten aufgelistet. Du kannst die meisten der Einstellungen über einen Kippschalter aktivieren oder deaktivieren: +The settings groups are listed below; you can enable or disable via a toggle switch for most entries described below: ![Omnipod_Settings_3](../images/omnipod/Omnipod_Settings_3.png) @@ -595,7 +595,7 @@ Ermöglicht das Scannen eines Pod-Kommunikationsgeräts. Der Omnipod-Treiber kan ### Bestätigungstöne -Bestätigt mit Signaltönen des Pods die Abgabe und Änderung von Bolus, Basalrate, SMB und TBR. +Provides confirmation beeps from the pod for bolus, basal, SMB, and TBR delivery and changes. - **\*Bolus-Töne aktiviert:** Aktiviert oder deaktiviert Bestätigungstöne, wenn ein Bolus abgegeben wird. - **\*Basal-Töne aktiviert:** Aktiviert oder deaktiviert die Bestätigungstöne, wenn eine neue Basalrate eingestellt wird, eine aktive Basalrate abgebrochen oder die aktuelle Basalrate geändert wird. @@ -606,7 +606,7 @@ Bestätigt mit Signaltönen des Pods die Abgabe und Änderung von Bolus, Basalra Bietet AAPS-Warnungen und Nightscout-Ankündigungen für den Ablauf eines Pods, die Abschaltung oder einen niedrigen Füllstand basierend auf den definierten Schwellenwerten. -*Beachte, dass eine AAPS-Benachrichtigung IMMER für jeden Alarm nach der ersten Kommunikation mit dem Pod ausgegeben wird, da der Alarm ausgelöst wurde. Wenn Du die Benachrichtigung löschst, wird der Alarm NICHT gelöscht, AUSSER wenn die automatische Bestätigung von Pod-Alarmen aktiviert ist. Um den Alarm MANUELL zu deaktivieren, musst du die Registerkarte Omnipod (POD) aufrufen und die Schaltfläche AKK ALERTS drücken.* +*Note an AAPS notification will ALWAYS be issued for any alert after the initial communication with the pod since the alert was triggered. Dismissing the notification will NOT dismiss the alert UNLESS automatically acknowledge Pod alerts is enabled. Um den Alarm MANUELL zu deaktivieren, musst du die Registerkarte Omnipod (POD) aufrufen und die Schaltfläche AKK ALERTS drücken.* - **\*Ablauferinnerung aktiviert:** Aktiviere oder deaktiviere die Pod-Ablauferinnerung, die ausgelöst wird, wenn die festgelegte Anzahl von Stunden vor dem Herunterfahren erreicht ist. - **Stunden bis zum Podende:** Legt die Anzahl der Stunden vor der Abschaltung des aktiven Pods fest, die den Alarm zur Pod-Ablauferinnerung auslöst. @@ -618,7 +618,7 @@ Bietet AAPS-Warnungen und Nightscout-Ankündigungen für den Ablauf eines Pods, Meldet AAPS-Benachrichtigungen und akustische Telefonwarnungen, wenn unsicher ist, ob TBR-, SMB- oder Bolus-Ereignisse erfolgreich waren. -*HINWEIS: Dies sind nur Benachrichtigungen, es werden keine akustischen Signale ausgegeben.* +*NOTE: These are notifications only, no audible beep alerts are made.* - **Ton für unsichere TBR-Benachrichtigung aktiviert:** Aktiviere oder deaktiviere diese Einstellung, um einen akustischen Alarm und eine visuelle Benachrichtigung auszulösen, wenn AAPS unsicher ist, ob eine TBR erfolgreich gesetzt wurde. - **\*Ton für Benachrichtigung bei unsicheren SMB-Ereignis aktiviert:** Aktiviere oder deaktiviere diese Einstellung, um einen akustischen Alarm und eine visuelle Benachrichtigung auszulösen, wenn AAPS unsicher ist, ob eine SMB erfolgreich zugestellt wurde. @@ -716,11 +716,11 @@ Die Batteriestandsmeldung ist eine Einstellung, die aktiviert werden kann, um de ### Pod Fehler -Pods fallen gelegentlich aus unterschiedlichen Gründen aus, u. a. wegen Hardwareproblemen mit dem Pod selbst. Am besten ist es, diese nicht bei Insulet anzugeben, da AAPS kein zugelassener Anwendungsfall ist. Eine Liste an Fehlercodes findest du [hier](https://github.com/openaps/openomni/wiki/Fault-event-codes), um die Ursache zu ermitteln. +Pods fail occasionally due to a variety of issues, including hardware issues with the Pod itself. It is best practice not to call these into Insulet, since AAPS is not an approved use case. Eine Liste an Fehlercodes findest du [hier](https://github.com/openaps/openomni/wiki/Fault-event-codes), um die Ursache zu ermitteln. ### Verhindere Pod Fehler 49 -Dieser Fehler hängt mit einem fehlerhaften Pod-Status für einen Befehl oder einem Fehler während der Insulinabgabe zusammen. Wir empfehlen Benutzern, in den Nightscout-Client Einstellungen *nur hochladen (Sync-deaktivieren)* auszuwählen, um mögliche Fehler zu vermeiden. +This failure is related to an incorrect pod state for a command or an error during an insulin delivery command. Wir empfehlen Benutzern, in den Nightscout-Client Einstellungen *nur hochladen (Sync-deaktivieren)* auszuwählen, um mögliche Fehler zu vermeiden. ### Pumpe nicht erreichbar Alarme @@ -739,7 +739,7 @@ Bitte beachte, dass beim Importieren von Einstellungen die Möglichkeit besteht, ### Omnipod-Treiberwarnungen -Bitte beachte, dass der Omnipod-Treiber auf der Registerkarte **Übersicht** eine Vielzahl einzigartiger Warnungen anzeigt. Die meisten davon sind informativ und können ignoriert werden, während einige dem Benutzer eine Aktion vorschlagen, um die Ursache für die ausgelöste Warnung zu beheben. Im Folgenden findest du eine Zusammenfassung der wichtigsten Warnmeldungen, die dir begegnen können: +Bitte beachte, dass der Omnipod-Treiber auf der Registerkarte **Übersicht** eine Vielzahl einzigartiger Warnungen anzeigt. Die meisten davon sind informativ und können ignoriert werden, während einige dem Benutzer eine Aktion vorschlagen, um die Ursache für die ausgelöste Warnung zu beheben. A summary of the main alerts that you may encounter is listed below: #### Kein aktiver Pod diff --git a/docs/CROWDIN/de/GettingHelp/GeneralTroubleshooting.md b/docs/CROWDIN/de/GettingHelp/GeneralTroubleshooting.md index 3774d76863d7..ab00637b0f73 100644 --- a/docs/CROWDIN/de/GettingHelp/GeneralTroubleshooting.md +++ b/docs/CROWDIN/de/GettingHelp/GeneralTroubleshooting.md @@ -37,14 +37,37 @@ Ignoriere sie: Weitere Details, Trotzdem installieren. * [SMS-Befehle](#SMSCommands-troubleshooting) -### Häufige Bluetooth-Verbindungsprobleme +### Frequent Bluetooth connection problems -Der Fehler kann bei verschiedenen Insulinpumpen auftreten. Außer AAPS von jeder Batterieoptimierung auszuschließen, kannst Du auch die Bluetooth-App des Systems von der Batterieoptimierung ausschließen. In einigen Fällen hilft das. Je nach verwendetem Smartphone findet sich die Bluetooth-App an anderen Stellen. +#### Android 15 + +```{warning} +Developers are working on this issue impacting **AAPS** on some Samsung and Pixel phones. +``` + +After upgrading Android or moving to a recent phone, **AAPS** frequently loses Bluetooth connection to the pump. The problem disappears temporarily when restarting the phone. If the phone runs Android 15, you can try to enable the following: + +1) **Open preferences** by clicking the three-dot menu on the top right side of the home screen. + + +![Einstellungen öffnen](../images/Pref2020_Open2.png) + +2. Scroll down and open the **Confirmation beeps** / **Advanced** submenu. Enable **Bond BT device on Android 15+**. + + ![BondBT](../images/troubleshooting/BondBT.png) + +3. If the pump asks for a pairing request, accept it. + +4. Restart your phone. + +#### Battery optimization + +Der Fehler kann bei verschiedenen Insulinpumpen auftreten. Apart from excluding AAPS from any battery optimization, you can also exclude the system Bluetooth app from battery optimization. In einigen Fällen hilft das. Depending on the phone you use, you will find the Bluetooth app differently. Hier sind Beispiele wie, Du die Einstellungen auf einzelnen Android-Smartphones findest. -#### Pixel Smartphones (unverändertes Android) +##### Pixel phones (stock Android) * Gehe zu Einstellungen > Apps @@ -67,7 +90,7 @@ Hier sind Beispiele wie, Du die Einstellungen auf einzelnen Android-Smartphones ![Bluetooth Akku-Optimierung](../images/troubleshooting/pixel/04_btunrestricted.png) -#### Samsung Smartphones +##### Samsung Smartphones * Gehe zu Einstellungen > Apps diff --git a/docs/CROWDIN/de/images/troubleshooting/BondBT.png b/docs/CROWDIN/de/images/troubleshooting/BondBT.png new file mode 100644 index 000000000000..96b2fb272d90 Binary files /dev/null and b/docs/CROWDIN/de/images/troubleshooting/BondBT.png differ diff --git a/docs/CROWDIN/de/images/troubleshooting/samsung/01_BondBT_20250526.png b/docs/CROWDIN/de/images/troubleshooting/samsung/01_BondBT_20250526.png new file mode 100644 index 000000000000..74c3525959ed Binary files /dev/null and b/docs/CROWDIN/de/images/troubleshooting/samsung/01_BondBT_20250526.png differ diff --git a/docs/CROWDIN/de/images/troubleshooting/samsung/02_BondBT_20250526.png b/docs/CROWDIN/de/images/troubleshooting/samsung/02_BondBT_20250526.png new file mode 100644 index 000000000000..444013b29146 Binary files /dev/null and b/docs/CROWDIN/de/images/troubleshooting/samsung/02_BondBT_20250526.png differ diff --git a/docs/CROWDIN/de/images/troubleshooting/samsung/03_BondBT_20250526.png b/docs/CROWDIN/de/images/troubleshooting/samsung/03_BondBT_20250526.png new file mode 100644 index 000000000000..9caa7a484581 Binary files /dev/null and b/docs/CROWDIN/de/images/troubleshooting/samsung/03_BondBT_20250526.png differ diff --git a/docs/CROWDIN/de/images/troubleshooting/samsung/04_BondBT_20250526.png b/docs/CROWDIN/de/images/troubleshooting/samsung/04_BondBT_20250526.png new file mode 100644 index 000000000000..b25c1469f58e Binary files /dev/null and b/docs/CROWDIN/de/images/troubleshooting/samsung/04_BondBT_20250526.png differ diff --git a/docs/CROWDIN/el/CompatiblePumps/OmnipodDASH.md b/docs/CROWDIN/el/CompatiblePumps/OmnipodDASH.md index 99858bc2c15a..e214813cf186 100644 --- a/docs/CROWDIN/el/CompatiblePumps/OmnipodDASH.md +++ b/docs/CROWDIN/el/CompatiblePumps/OmnipodDASH.md @@ -18,7 +18,13 @@ These are the specifications of the **Omnipod DASH** ('DASH') and what different * On pod activation, **AAPS** will find and connect to a new DASH pod. * Expected range: 5-10 meters (YMMV). -WARNING: There are currently reported Bluetooth connection issues with the following combination of **AAPS** / DASH / Android 15. **AAPS** should not be used in combination with Android 15 and DASH unless the user has checked the following [**List**](https://docs.google.com/spreadsheets/u/1/d/e/2PACX-1vScCNaIguEZVTVFAgpv1kXHdsHl3fs6xT6RB2Z1CeVJ561AvvqGwxMhlmSHk4J056gMCAQE02sAWJvT/pubhtml?gid=683363241&single=true) and verified that their phone is not a known reported issue. **AAPS** is currently working to resolve this issue. +```{admonition} Android 15 +:class: warning + +There are currently reported Bluetooth connection issues with the following combination of **AAPS**: DASH + Android 15. +Please refrain from upgrading your phone to Android 15 unless you have checked the following [**list**](https://docs.google.com/spreadsheets/u/1/d/e/2PACX-1vScCNaIguEZVTVFAgpv1kXHdsHl3fs6xT6RB2Z1CeVJ561AvvqGwxMhlmSHk4J056gMCAQE02sAWJvT/pubhtml?gid=683363241&single=true) and verified that your phone is not a known reported issue. +If you experience frequent disconnection; try to enable Bond BT as described in: [**Bluetooth Issues**](../GettingHelp/GeneralTroubleshooting.md). +``` ## Hardware/Software Requirements diff --git a/docs/CROWDIN/el/GettingHelp/GeneralTroubleshooting.md b/docs/CROWDIN/el/GettingHelp/GeneralTroubleshooting.md index bf83afbfa8a8..b94ae30f6dcd 100644 --- a/docs/CROWDIN/el/GettingHelp/GeneralTroubleshooting.md +++ b/docs/CROWDIN/el/GettingHelp/GeneralTroubleshooting.md @@ -37,14 +37,37 @@ Ignore it: More details, Install anyway. * [SMS commands](#SMSCommands-troubleshooting) -### Frequent bluetooth connection problems +### Frequent Bluetooth connection problems -This can happen with various pumps. Apart from excluding AAPS from any battery optimization, you can also exclude the system bluetooth app from battery optimization. This can help in some cases. Depending on the phone you use, you will find the bluetooth app differently. +#### Android 15 + +```{warning} +Developers are working on this issue impacting **AAPS** on some Samsung and Pixel phones. +``` + +After upgrading Android or moving to a recent phone, **AAPS** frequently loses Bluetooth connection to the pump. The problem disappears temporarily when restarting the phone. If the phone runs Android 15, you can try to enable the following: + +1) **Open preferences** by clicking the three-dot menu on the top right side of the home screen. + + +![Open preferences](../images/Pref2020_Open2.png) + +2. Scroll down and open the **Confirmation beeps** / **Advanced** submenu. Enable **Bond BT device on Android 15+**. + + ![BondBT](../images/troubleshooting/BondBT.png) + +3. If the pump asks for a pairing request, accept it. + +4. Restart your phone. + +#### Battery optimization + +This can happen with various pumps. Apart from excluding AAPS from any battery optimization, you can also exclude the system Bluetooth app from battery optimization. This can help in some cases. Depending on the phone you use, you will find the Bluetooth app differently. Here are examples how to find them on specific android phones. -#### Pixel phones (stock android) +##### Pixel phones (stock Android) * Go to the android settings, select "Apps". @@ -67,7 +90,7 @@ Here are examples how to find them on specific android phones. ![BT Battery optimization](../images/troubleshooting/pixel/04_btunrestricted.png) -#### Samsung phones +##### Samsung phones * Go to the android settings, select "Apps" diff --git a/docs/CROWDIN/el/images/troubleshooting/BondBT.png b/docs/CROWDIN/el/images/troubleshooting/BondBT.png new file mode 100644 index 000000000000..96b2fb272d90 Binary files /dev/null and b/docs/CROWDIN/el/images/troubleshooting/BondBT.png differ diff --git a/docs/CROWDIN/el/images/troubleshooting/samsung/01_BondBT_20250526.png b/docs/CROWDIN/el/images/troubleshooting/samsung/01_BondBT_20250526.png new file mode 100644 index 000000000000..74c3525959ed Binary files /dev/null and b/docs/CROWDIN/el/images/troubleshooting/samsung/01_BondBT_20250526.png differ diff --git a/docs/CROWDIN/el/images/troubleshooting/samsung/02_BondBT_20250526.png b/docs/CROWDIN/el/images/troubleshooting/samsung/02_BondBT_20250526.png new file mode 100644 index 000000000000..444013b29146 Binary files /dev/null and b/docs/CROWDIN/el/images/troubleshooting/samsung/02_BondBT_20250526.png differ diff --git a/docs/CROWDIN/el/images/troubleshooting/samsung/03_BondBT_20250526.png b/docs/CROWDIN/el/images/troubleshooting/samsung/03_BondBT_20250526.png new file mode 100644 index 000000000000..9caa7a484581 Binary files /dev/null and b/docs/CROWDIN/el/images/troubleshooting/samsung/03_BondBT_20250526.png differ diff --git a/docs/CROWDIN/el/images/troubleshooting/samsung/04_BondBT_20250526.png b/docs/CROWDIN/el/images/troubleshooting/samsung/04_BondBT_20250526.png new file mode 100644 index 000000000000..b25c1469f58e Binary files /dev/null and b/docs/CROWDIN/el/images/troubleshooting/samsung/04_BondBT_20250526.png differ diff --git a/docs/CROWDIN/es/CompatiblePumps/OmnipodDASH.md b/docs/CROWDIN/es/CompatiblePumps/OmnipodDASH.md index cae79ce5bf6a..a865b38a74bb 100644 --- a/docs/CROWDIN/es/CompatiblePumps/OmnipodDASH.md +++ b/docs/CROWDIN/es/CompatiblePumps/OmnipodDASH.md @@ -18,7 +18,13 @@ These are the specifications of the **Omnipod DASH** ('DASH') and what different * On pod activation, **AAPS** will find and connect to a new DASH pod. * Expected range: 5-10 meters (YMMV). -WARNING: There are currently reported Bluetooth connection issues with the following combination of **AAPS** / DASH / Android 15. **AAPS** should not be used in combination with Android 15 and DASH unless the user has checked the following [**List**](https://docs.google.com/spreadsheets/u/1/d/e/2PACX-1vScCNaIguEZVTVFAgpv1kXHdsHl3fs6xT6RB2Z1CeVJ561AvvqGwxMhlmSHk4J056gMCAQE02sAWJvT/pubhtml?gid=683363241&single=true) and verified that their phone is not a known reported issue. **AAPS** is currently working to resolve this issue. +```{admonition} Android 15 +:class: warning + +There are currently reported Bluetooth connection issues with the following combination of **AAPS**: DASH + Android 15. +Please refrain from upgrading your phone to Android 15 unless you have checked the following [**list**](https://docs.google.com/spreadsheets/u/1/d/e/2PACX-1vScCNaIguEZVTVFAgpv1kXHdsHl3fs6xT6RB2Z1CeVJ561AvvqGwxMhlmSHk4J056gMCAQE02sAWJvT/pubhtml?gid=683363241&single=true) and verified that your phone is not a known reported issue. +If you experience frequent disconnection; try to enable Bond BT as described in: [**Bluetooth Issues**](../GettingHelp/GeneralTroubleshooting.md). +``` ## Hardware/Software Requirements diff --git a/docs/CROWDIN/es/GettingHelp/GeneralTroubleshooting.md b/docs/CROWDIN/es/GettingHelp/GeneralTroubleshooting.md index 36cf77da947d..284b0fbbffa2 100644 --- a/docs/CROWDIN/es/GettingHelp/GeneralTroubleshooting.md +++ b/docs/CROWDIN/es/GettingHelp/GeneralTroubleshooting.md @@ -37,14 +37,37 @@ Ignore it: More details, Install anyway. * [SMS commands](#SMSCommands-troubleshooting) -### Frequent bluetooth connection problems +### Frequent Bluetooth connection problems -This can happen with various pumps. Apart from excluding AAPS from any battery optimization, you can also exclude the system bluetooth app from battery optimization. This can help in some cases. Depending on the phone you use, you will find the bluetooth app differently. +#### Android 15 + +```{warning} +Developers are working on this issue impacting **AAPS** on some Samsung and Pixel phones. +``` + +After upgrading Android or moving to a recent phone, **AAPS** frequently loses Bluetooth connection to the pump. The problem disappears temporarily when restarting the phone. If the phone runs Android 15, you can try to enable the following: + +1) **Open preferences** by clicking the three-dot menu on the top right side of the home screen. + + +![Open preferences](../images/Pref2020_Open2.png) + +2. Scroll down and open the **Confirmation beeps** / **Advanced** submenu. Enable **Bond BT device on Android 15+**. + + ![BondBT](../images/troubleshooting/BondBT.png) + +3. If the pump asks for a pairing request, accept it. + +4. Restart your phone. + +#### Battery optimization + +This can happen with various pumps. Apart from excluding AAPS from any battery optimization, you can also exclude the system Bluetooth app from battery optimization. This can help in some cases. Depending on the phone you use, you will find the Bluetooth app differently. Here are examples how to find them on specific android phones. -#### Pixel phones (stock android) +##### Pixel phones (stock Android) * Go to the android settings, select "Apps". @@ -67,7 +90,7 @@ Here are examples how to find them on specific android phones. ![BT Battery optimization](../images/troubleshooting/pixel/04_btunrestricted.png) -#### Samsung phones +##### Samsung phones * Go to the android settings, select "Apps" diff --git a/docs/CROWDIN/es/images/troubleshooting/BondBT.png b/docs/CROWDIN/es/images/troubleshooting/BondBT.png new file mode 100644 index 000000000000..96b2fb272d90 Binary files /dev/null and b/docs/CROWDIN/es/images/troubleshooting/BondBT.png differ diff --git a/docs/CROWDIN/es/images/troubleshooting/samsung/01_BondBT_20250526.png b/docs/CROWDIN/es/images/troubleshooting/samsung/01_BondBT_20250526.png new file mode 100644 index 000000000000..74c3525959ed Binary files /dev/null and b/docs/CROWDIN/es/images/troubleshooting/samsung/01_BondBT_20250526.png differ diff --git a/docs/CROWDIN/es/images/troubleshooting/samsung/02_BondBT_20250526.png b/docs/CROWDIN/es/images/troubleshooting/samsung/02_BondBT_20250526.png new file mode 100644 index 000000000000..444013b29146 Binary files /dev/null and b/docs/CROWDIN/es/images/troubleshooting/samsung/02_BondBT_20250526.png differ diff --git a/docs/CROWDIN/es/images/troubleshooting/samsung/03_BondBT_20250526.png b/docs/CROWDIN/es/images/troubleshooting/samsung/03_BondBT_20250526.png new file mode 100644 index 000000000000..9caa7a484581 Binary files /dev/null and b/docs/CROWDIN/es/images/troubleshooting/samsung/03_BondBT_20250526.png differ diff --git a/docs/CROWDIN/es/images/troubleshooting/samsung/04_BondBT_20250526.png b/docs/CROWDIN/es/images/troubleshooting/samsung/04_BondBT_20250526.png new file mode 100644 index 000000000000..b25c1469f58e Binary files /dev/null and b/docs/CROWDIN/es/images/troubleshooting/samsung/04_BondBT_20250526.png differ diff --git a/docs/CROWDIN/fr/CompatiblePumps/MedtrumNano.md b/docs/CROWDIN/fr/CompatiblePumps/MedtrumNano.md index 2ecb44cd5fd5..899456e7cd52 100644 --- a/docs/CROWDIN/fr/CompatiblePumps/MedtrumNano.md +++ b/docs/CROWDIN/fr/CompatiblePumps/MedtrumNano.md @@ -39,7 +39,7 @@ Ce logiciel est une partie d'un système de pancréas artificiel "Do it yourself **Your pump will not stop delivering insulin when it is not connected to AAPS** Default basal rates are programmed on the pump as defined in the current active profile. As long as AAPS is operational, it will send temporary basal rate commands that run for a maximum of 120 minutes. If for some reason the pump does not receive any new commands (for instance because communication was lost due to pump - phone distance) the pump will fall back to the default basal rate programmed on the pump once the Temporary Basal Rate ends. -**30 min Basal Rate Profiles are NOT supported in AAPS.** **The AAPS Profile does not support a 30 minute basal rate time frame** If you are new to AAPS and are setting up your basal rate profile for the first time, please be aware that basal rates starting on a half-hour basis are not supported, and you will need to adjust your basal rate profile to start on the hour. Par exemple, si vous avez un débit de basal de 1,1 unités qui commence à 09h30 et a une durée de 2 heures se terminant à 11h30, cela ne marchera pas. Vous devrez mettre à jour ce taux de basal de 1,1 sur une plage horaire de 9h00 à 11h00 ou de 10h00 à 12h00. Even though the Medtrum pump hardware itself supports the 30 min basal rate profile increments, AAPS is not able to take them into account with its algorithms currently. +**30 min Basal Rate Profiles are NOT supported in AAPS.** **The AAPS Profile does not support a 30 minute basal rate time frame** If you are new to AAPS and are setting up your basal rate profile for the first time, please be aware that basal rates starting on a half-hour basis are not supported, and you will need to adjust your basal rate profile to start on the hour. Par exemple, si vous avez un débit de basal de 1,1 unités qui commence à 09h30 et a une durée de 2 heures se terminant à 11h30, cela ne marchera pas. 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 Medtrum pump hardware itself supports the 30 min basal rate profile increments, AAPS is not able to take them into account with its algorithms currently. **0U/h profile basal rates are NOT supported in AAPS** While the Medtrum pump does support a zero basal rate, AAPS uses multiples of the profile basal rate to determine automated treatment and therefore cannot function with a zero basal rate. A temporary zero basal rate can be achieved through the "Disconnect pump" function or through a combination of Disable Loop/Temp Basal Rate or Suspend Loop/Temp Basal Rate. diff --git a/docs/CROWDIN/fr/CompatiblePumps/OmnipodDASH.md b/docs/CROWDIN/fr/CompatiblePumps/OmnipodDASH.md index b5e82fdc12ea..f4fc6912207f 100644 --- a/docs/CROWDIN/fr/CompatiblePumps/OmnipodDASH.md +++ b/docs/CROWDIN/fr/CompatiblePumps/OmnipodDASH.md @@ -18,7 +18,13 @@ These are the specifications of the **Omnipod DASH** ('DASH') and what different * On pod activation, **AAPS** will find and connect to a new DASH pod. * Expected range: 5-10 meters (YMMV). -WARNING: There are currently reported Bluetooth connection issues with the following combination of **AAPS** / DASH / Android 15. **AAPS** should not be used in combination with Android 15 and DASH unless the user has checked the following [**List**](https://docs.google.com/spreadsheets/u/1/d/e/2PACX-1vScCNaIguEZVTVFAgpv1kXHdsHl3fs6xT6RB2Z1CeVJ561AvvqGwxMhlmSHk4J056gMCAQE02sAWJvT/pubhtml?gid=683363241&single=true) and verified that their phone is not a known reported issue. **AAPS** is currently working to resolve this issue. +```{admonition} Android 15 +:class: warning + +There are currently reported Bluetooth connection issues with the following combination of **AAPS**: DASH + Android 15. +Please refrain from upgrading your phone to Android 15 unless you have checked the following [**list**](https://docs.google.com/spreadsheets/u/1/d/e/2PACX-1vScCNaIguEZVTVFAgpv1kXHdsHl3fs6xT6RB2Z1CeVJ561AvvqGwxMhlmSHk4J056gMCAQE02sAWJvT/pubhtml?gid=683363241&single=true) and verified that your phone is not a known reported issue. +If you experience frequent disconnection; try to enable Bond BT as described in: [**Bluetooth Issues**](../GettingHelp/GeneralTroubleshooting.md). +``` ## Configuration matérielle et logicielle requise @@ -37,13 +43,13 @@ The instructions below explain how to activate a new pod session. Wait to close **SAFETY FIRST** - you should not try to connect **AAPS** to a pod for the first time without having access to extra pods, insulin, and phone devices are a must have. -**Your Omnipod Dash PDM will become redundant after the AAPS Dash driver activates your pod.** Previously a user may have operated a PDM to send commands to your DASH. A DASH will only faciiliate a single device to send commands to communicate with it. L'appareil qui active le pod avec succès est le seul appareil autorisé à communiquer avec lui à partir de ce moment. This means that once you activate a DASH with your Android phone through the **AAPS**, **you will no longer be able to use your PDM with that pod**. The **AAPS** Dash driver in your Android phone is now your acting PDM. +**Your Omnipod Dash PDM will become redundant after the AAPS Dash driver activates your pod.** Previously a user may have operated a PDM to send commands to your DASH. A DASH will only faciiliate a single device to send commands to communicate with it. The device that successfully activates the pod is the only device allowed to communicate with it from that point forward. This means that once you activate a DASH with your Android phone through the **AAPS**, **you will no longer be able to use your PDM with that pod**. The **AAPS** Dash driver in your Android phone is now your acting PDM. -*Cela ne veut pas dire que vous pouvez jeter votre PDM, il est recommandé de le garder comme une sauvegarde, et en cas d'urgence dans le cas où vous perdez votre téléphone ou AAPS ne fonctionne pas correctement.* +*This does NOT mean you should throw away your PDM, it is recommended to keep it around as a backup and for emergencies, for instance when your phone gets lost or AAPS is not working correctly.* -**Your pod will not stop delivering insulin when it is not connected to AAPS**. Default basal rates are programmed on the pod on activation as defined in the current active **Profile**. As long as **AAPS** is operational it will send basal rate commands that run for a maximum of 120 minutes. Lorsque, pour une raison quelconque, le pod ne reçoit pas de nouvelles commandes (par exemple parce que la communication a été perdue à cause de la distance Pod - téléphone) le pod retourne automatiquement aux débits de basal par défaut. +**Your pod will not stop delivering insulin when it is not connected to AAPS**. Default basal rates are programmed on the pod on activation as defined in the current active **Profile**. As long as **AAPS** is operational it will send basal rate commands that run for a maximum of 120 minutes. 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. -**AAPS Profile does not support a 30 minute basal rate time frame** If you are new to **AAPS** and are setting up your basal rate **Profile** for the first time, please be aware that basal rates starting on a half-hour basis are not supported, and programmes on an hourly basis. For example, 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 im **AAPS**. Vous devrez mettre à jour ce taux de basal de 1,1 sur une plage horaire de 9h00 à 11h00 ou de 10h00 à 12h00. Even though the DASH hardware itself supports the 30 minute basal rate **Profile** increments, **AAPS** does support this feature. +**AAPS Profile does not support a 30 minute basal rate time frame** If you are new to **AAPS** and are setting up your basal rate **Profile** for the first time, please be aware that basal rates starting on a half-hour basis are not supported, and programmes on an hourly basis. For example, 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 im **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 support this feature. **0U/h profile basal rates are NOT supported in AAPS** While the DASH does support a zero basal rate, since **AAPS** uses multiples of the user's **Profile** basal rate to determine automated treatment; it cannot function with a zero basal rate. A temporary zero basal rate can be achieved through the "Disconnect pump" function or through a combination of Disable Loop/Temp Basal Rate or Suspend Loop/Temp Basal Rate. The lowest basal rate allowed in **AAPS** is 0.05U/h. diff --git a/docs/CROWDIN/fr/CompatiblePumps/OmnipodEros.md b/docs/CROWDIN/fr/CompatiblePumps/OmnipodEros.md index 184491a363e1..925c4142775c 100644 --- a/docs/CROWDIN/fr/CompatiblePumps/OmnipodEros.md +++ b/docs/CROWDIN/fr/CompatiblePumps/OmnipodEros.md @@ -43,7 +43,7 @@ Ces instructions supposent que vous commencez une nouvelle session pod; si ce n' **SÉCURITÉ D'ABORD** - ne pas essayer ce processus dans un environnement où vous ne pouvez pas récupérer une erreur (pods supplémentaires, insuline, RileyLink chargé et les smartphones sont nécessaires). -**Votre PDM Omnipod ne fonctionnera plus après l'activation de votre pod par le driver AAPS Omnipod**. Vous avez précédemment utilisé votre PDM Omnipod pour envoyer des commandes à votre pod Omnipod Eros. Un pod Omnipod Eros ne permet qu'à un seul appareil de la communiquer avec lui. L'appareil qui active le pod avec succès est le seul appareil autorisé à communiquer avec lui à partir de ce moment. Cela signifie qu'une fois que vous activez un pod Omnipod Eros avec votre RileyLink via le pilote AAPS Omnipod, **vous ne pourrez plus utiliser votre PDM avec votre pod**. Le pilote AAPS Omnipod avec le RileyLink est maintenant votre PDM. *Cela ne veut pas dire que vous pouvez jeter votre PDM, il est recommandé de le garder comme une sauvegarde, et en cas d'urgence si jamais AAPS ne fonctionnait pas correctement.* +**Votre PDM Omnipod ne fonctionnera plus après l'activation de votre pod par le driver AAPS Omnipod**. Vous avez précédemment utilisé votre PDM Omnipod pour envoyer des commandes à votre pod Omnipod Eros. Un pod Omnipod Eros ne permet qu'à un seul appareil de la communiquer avec lui. The device that successfully activates the pod is the only device allowed to communicate with it from that point forward. Cela signifie qu'une fois que vous activez un pod Omnipod Eros avec votre RileyLink via le pilote AAPS Omnipod, **vous ne pourrez plus utiliser votre PDM avec votre pod**. Le pilote AAPS Omnipod avec le RileyLink est maintenant votre PDM. *Cela ne veut pas dire que vous pouvez jeter votre PDM, il est recommandé de le garder comme une sauvegarde, et en cas d'urgence si jamais AAPS ne fonctionnait pas correctement.* **Vous pouvez configurer plusieurs RileyLinks, mais un seul RileyLink à la fois peut communiquer avec un pod.** Le pilote AAPS Omnipod supporte la possibilité d'ajouter plusieurs RileyLinks dans la configuration de RileyLink, cependant, un seul RileyLink à la fois peut être sélectionné pour la communication. diff --git a/docs/CROWDIN/fr/GettingHelp/GeneralTroubleshooting.md b/docs/CROWDIN/fr/GettingHelp/GeneralTroubleshooting.md index 3d3e528ef1ca..04af5a4b9a26 100644 --- a/docs/CROWDIN/fr/GettingHelp/GeneralTroubleshooting.md +++ b/docs/CROWDIN/fr/GettingHelp/GeneralTroubleshooting.md @@ -37,14 +37,37 @@ Ignore it: More details, Install anyway. * [Commandes SMS](#SMSCommands-troubleshooting) -### Problèmes de connexion bluetooth fréquents +### Frequent Bluetooth connection problems -Cela peut se produire avec diverses pompes. En plus d'exclure AAPS de toute optimisation de batterie, vous pouvez également exclure l'application Bluetooth du système de l'optimisation de la batterie. Cela peut être utile dans certains cas. Selon le téléphone que vous utilisez, vous trouverez l'application bluetooth différemment. +#### Android 15 + +```{warning} +Developers are working on this issue impacting **AAPS** on some Samsung and Pixel phones. +``` + +After upgrading Android or moving to a recent phone, **AAPS** frequently loses Bluetooth connection to the pump. The problem disappears temporarily when restarting the phone. If the phone runs Android 15, you can try to enable the following: + +1) **Open preferences** by clicking the three-dot menu on the top right side of the home screen. + + +![Open preferences](../images/Pref2020_Open2.png) + +2. Scroll down and open the **Confirmation beeps** / **Advanced** submenu. Enable **Bond BT device on Android 15+**. + + ![BondBT](../images/troubleshooting/BondBT.png) + +3. If the pump asks for a pairing request, accept it. + +4. Restart your phone. + +#### Battery optimization + +Cela peut se produire avec diverses pompes. Apart from excluding AAPS from any battery optimization, you can also exclude the system Bluetooth app from battery optimization. Cela peut être utile dans certains cas. Depending on the phone you use, you will find the Bluetooth app differently. Voici des exemples pour les trouver sur des téléphones Android spécifiques. -#### Téléphones Pixel (Android standard) +##### Pixel phones (stock Android) * Allez dans les paramètres d'Android, sélectionnez "Applications". @@ -67,7 +90,7 @@ Voici des exemples pour les trouver sur des téléphones Android spécifiques. ![Optimisation batterie BT](../images/troubleshooting/pixel/04_btunrestricted.png) -#### Téléphone Samsung +##### Téléphone Samsung * Allez dans les paramètres d'Android, sélectionnez "Applications" diff --git a/docs/CROWDIN/fr/images/troubleshooting/BondBT.png b/docs/CROWDIN/fr/images/troubleshooting/BondBT.png new file mode 100644 index 000000000000..96b2fb272d90 Binary files /dev/null and b/docs/CROWDIN/fr/images/troubleshooting/BondBT.png differ diff --git a/docs/CROWDIN/fr/images/troubleshooting/samsung/01_BondBT_20250526.png b/docs/CROWDIN/fr/images/troubleshooting/samsung/01_BondBT_20250526.png new file mode 100644 index 000000000000..74c3525959ed Binary files /dev/null and b/docs/CROWDIN/fr/images/troubleshooting/samsung/01_BondBT_20250526.png differ diff --git a/docs/CROWDIN/fr/images/troubleshooting/samsung/02_BondBT_20250526.png b/docs/CROWDIN/fr/images/troubleshooting/samsung/02_BondBT_20250526.png new file mode 100644 index 000000000000..444013b29146 Binary files /dev/null and b/docs/CROWDIN/fr/images/troubleshooting/samsung/02_BondBT_20250526.png differ diff --git a/docs/CROWDIN/fr/images/troubleshooting/samsung/03_BondBT_20250526.png b/docs/CROWDIN/fr/images/troubleshooting/samsung/03_BondBT_20250526.png new file mode 100644 index 000000000000..9caa7a484581 Binary files /dev/null and b/docs/CROWDIN/fr/images/troubleshooting/samsung/03_BondBT_20250526.png differ diff --git a/docs/CROWDIN/fr/images/troubleshooting/samsung/04_BondBT_20250526.png b/docs/CROWDIN/fr/images/troubleshooting/samsung/04_BondBT_20250526.png new file mode 100644 index 000000000000..b25c1469f58e Binary files /dev/null and b/docs/CROWDIN/fr/images/troubleshooting/samsung/04_BondBT_20250526.png differ diff --git a/docs/CROWDIN/he/CompatiblePumps/MedtrumNano.md b/docs/CROWDIN/he/CompatiblePumps/MedtrumNano.md index dafa02ded9b5..4c0652111621 100644 --- a/docs/CROWDIN/he/CompatiblePumps/MedtrumNano.md +++ b/docs/CROWDIN/he/CompatiblePumps/MedtrumNano.md @@ -39,7 +39,7 @@ These instructions are for configuring the Medtrum insulin pump. **Your pump will not stop delivering insulin when it is not connected to AAPS** Default basal rates are programmed on the pump as defined in the current active profile. As long as AAPS is operational, it will send temporary basal rate commands that run for a maximum of 120 minutes. If for some reason the pump does not receive any new commands (for instance because communication was lost due to pump - phone distance) the pump will fall back to the default basal rate programmed on the pump once the Temporary Basal Rate ends. -**פרופילי בזאלי המתחילים בשעות לא עגולות אינם נתמכים ב-AndroidAPS.** **פרופיל ברירת המחדל ב-AndroidAPS אינו תומך במסגרת זמן של מינון בזאלי של 30 דקות** אם אתם חדשים ב-AndroidAPS ואתם מגדירים את הפרופיל הבזאלי הבסיסי שלך בפעם הראשונה, חשוב לשים לב שמינונים שמתחילים בשעה לא עגולה אינם נתמכים, ותצטרכו להתאים את פרופיל הבזאלי שלך כך שמינון יתחיל בשעה עגולה. לדוגמה, אם יש מינון בזאלי של למשל 1.1 יחידות שמתחיל בשעה 09:30 ויש לו משך של שעתיים ומסתיים בשעה 11:30, זה לא יעבוד. יהיה עליכם לעדכן את המינון של 1.1 יחידות לטווח זמן של 09:00-11:00 או 10:00-12:00. Even though the Medtrum pump hardware itself supports the 30 min basal rate profile increments, AAPS is not able to take them into account with its algorithms currently. +**פרופילי בזאלי המתחילים בשעות לא עגולות אינם נתמכים ב-AndroidAPS.** **פרופיל ברירת המחדל ב-AndroidAPS אינו תומך במסגרת זמן של מינון בזאלי של 30 דקות** אם אתם חדשים ב-AndroidAPS ואתם מגדירים את הפרופיל הבזאלי הבסיסי שלך בפעם הראשונה, חשוב לשים לב שמינונים שמתחילים בשעה לא עגולה אינם נתמכים, ותצטרכו להתאים את פרופיל הבזאלי שלך כך שמינון יתחיל בשעה עגולה. לדוגמה, אם יש מינון בזאלי של למשל 1.1 יחידות שמתחיל בשעה 09:30 ויש לו משך של שעתיים ומסתיים בשעה 11:30, זה לא יעבוד. 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 Medtrum pump hardware itself supports the 30 min basal rate profile increments, AAPS is not able to take them into account with its algorithms currently. **0U/h profile basal rates are NOT supported in AAPS** While the Medtrum pump does support a zero basal rate, AAPS uses multiples of the profile basal rate to determine automated treatment and therefore cannot function with a zero basal rate. A temporary zero basal rate can be achieved through the "Disconnect pump" function or through a combination of Disable Loop/Temp Basal Rate or Suspend Loop/Temp Basal Rate. diff --git a/docs/CROWDIN/he/CompatiblePumps/OmnipodDASH.md b/docs/CROWDIN/he/CompatiblePumps/OmnipodDASH.md index 10040c384836..718c30d7254c 100644 --- a/docs/CROWDIN/he/CompatiblePumps/OmnipodDASH.md +++ b/docs/CROWDIN/he/CompatiblePumps/OmnipodDASH.md @@ -18,7 +18,13 @@ These are the specifications of the **Omnipod DASH** ('DASH') and what different * On pod activation, **AAPS** will find and connect to a new DASH pod. * Expected range: 5-10 meters (YMMV). -WARNING: There are currently reported Bluetooth connection issues with the following combination of **AAPS** / DASH / Android 15. **AAPS** should not be used in combination with Android 15 and DASH unless the user has checked the following [**List**](https://docs.google.com/spreadsheets/u/1/d/e/2PACX-1vScCNaIguEZVTVFAgpv1kXHdsHl3fs6xT6RB2Z1CeVJ561AvvqGwxMhlmSHk4J056gMCAQE02sAWJvT/pubhtml?gid=683363241&single=true) and verified that their phone is not a known reported issue. **AAPS** is currently working to resolve this issue. +```{admonition} Android 15 +:class: warning + +There are currently reported Bluetooth connection issues with the following combination of **AAPS**: DASH + Android 15. +Please refrain from upgrading your phone to Android 15 unless you have checked the following [**list**](https://docs.google.com/spreadsheets/u/1/d/e/2PACX-1vScCNaIguEZVTVFAgpv1kXHdsHl3fs6xT6RB2Z1CeVJ561AvvqGwxMhlmSHk4J056gMCAQE02sAWJvT/pubhtml?gid=683363241&single=true) and verified that your phone is not a known reported issue. +If you experience frequent disconnection; try to enable Bond BT as described in: [**Bluetooth Issues**](../GettingHelp/GeneralTroubleshooting.md). +``` ## דרישות חומרה ותוכנה @@ -37,13 +43,13 @@ The instructions below explain how to activate a new pod session. Wait to close **SAFETY FIRST** - you should not try to connect **AAPS** to a pod for the first time without having access to extra pods, insulin, and phone devices are a must have. -**Your Omnipod Dash PDM will become redundant after the AAPS Dash driver activates your pod.** Previously a user may have operated a PDM to send commands to your DASH. A DASH will only faciiliate a single device to send commands to communicate with it. המכשיר שמפעיל את הפוד הוא המכשיר היחיד שמורשה לתקשר איתו מאותה נקודה ואילך. This means that once you activate a DASH with your Android phone through the **AAPS**, **you will no longer be able to use your PDM with that pod**. The **AAPS** Dash driver in your Android phone is now your acting PDM. +**Your Omnipod Dash PDM will become redundant after the AAPS Dash driver activates your pod.** Previously a user may have operated a PDM to send commands to your DASH. A DASH will only faciiliate a single device to send commands to communicate with it. The device that successfully activates the pod is the only device allowed to communicate with it from that point forward. This means that once you activate a DASH with your Android phone through the **AAPS**, **you will no longer be able to use your PDM with that pod**. The **AAPS** Dash driver in your Android phone is now your acting PDM. -*זה לא אומר שצריך לזרוק את ה-PDM, מומלץ לשמור אותו בסביבה כגיבוי למקרי חירום, למשל כאשר הטלפון הולך לאיבוד או AAPS אינו פועל כהלכה.* +*This does NOT mean you should throw away your PDM, it is recommended to keep it around as a backup and for emergencies, for instance when your phone gets lost or AAPS is not working correctly.* -**הפוד לא יפסיק לספק אינסולין אם הוא מאבד חיבור ל-AndroidAPS**. Default basal rates are programmed on the pod on activation as defined in the current active **Profile**. As long as **AAPS** is operational it will send basal rate commands that run for a maximum of 120 minutes. כאשר מסיבה כלשהי הפוד אינו מקבל פקודות חדשות (למשל בגלל שהתקשורת אבדה עקב מרחק גדול מהטלפון) הפוד יחזור אוטומטית למינוני הבזאלי המוגדרים כברירת מחדל. +**Your pod will not stop delivering insulin when it is not connected to AAPS**. Default basal rates are programmed on the pod on activation as defined in the current active **Profile**. As long as **AAPS** is operational it will send basal rate commands that run for a maximum of 120 minutes. 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. -**AAPS Profile does not support a 30 minute basal rate time frame** If you are new to **AAPS** and are setting up your basal rate **Profile** for the first time, please be aware that basal rates starting on a half-hour basis are not supported, and programmes on an hourly basis. For example, 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 im **AAPS**. יהיה עליכם לעדכן את המינון של 1.1 יחידות לטווח זמן של 09:00-11:00 או 10:00-12:00. Even though the DASH hardware itself supports the 30 minute basal rate **Profile** increments, **AAPS** does support this feature. +**AAPS Profile does not support a 30 minute basal rate time frame** If you are new to **AAPS** and are setting up your basal rate **Profile** for the first time, please be aware that basal rates starting on a half-hour basis are not supported, and programmes on an hourly basis. For example, 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 im **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 support this feature. **0U/h profile basal rates are NOT supported in AAPS** While the DASH does support a zero basal rate, since **AAPS** uses multiples of the user's **Profile** basal rate to determine automated treatment; it cannot function with a zero basal rate. A temporary zero basal rate can be achieved through the "Disconnect pump" function or through a combination of Disable Loop/Temp Basal Rate or Suspend Loop/Temp Basal Rate. The lowest basal rate allowed in **AAPS** is 0.05U/h. @@ -53,7 +59,7 @@ There are **two ways**: ### אפשרות 1: התקנות חדשות -When installing **AAPS** for the first time, the **Setup Wizard** will guide new users through key features and installation requirements for **AAPS**. בחרו "DASH" כשתגיעו לחלק של בחירת המשאבה. +When installing **AAPS** for the first time, the **Setup Wizard** will guide new users through key features and installation requirements for **AAPS**. Select “DASH” when you reach Pump selection. ![Enable_Dash_1](../images/DASH_images/Enable_Dash/Enable_Dash_1.png) @@ -61,9 +67,9 @@ When in doubt you can also select “Virtual Pump” and select “DASH” later ### אפשרות 2: בונה התצורה -בהתקנה קיימת, תוכלו לבחור במשאבת **DASH** בבונה התצורה: +On an existing installation you can select the **DASH** pump from the Config builder: -בפינה הימנית-עליונה **בתפריט ההמבורגר (☰)** בחרו **בונה התצורה (1)** ← **משאבה** ← **Dash** ← **בחירת הכפתור העגול ("כפתור רדיו") (2) ← גלגל שיניים (3)**. +On the top-left hand corner **hamburger menu** select **Config Builder (1)**\ ➜\ **Pump**\ ➜\ **Dash**\ ➜\ **Settings Gear (3)** by selecting the **radio button (2)** titled **Dash**. Selecting the **checkbox (4)** next to the **Settings Gear (3)** will allow the DASH menu to be displayed as a tab in the **AAPS** interface titled **DASH**. Checking this box will facilitate your access to the DASH commands when using **AAPS**. @@ -79,7 +85,7 @@ To verify that you have selected the DASH in **AAPS**, if you have checked the b ## תצורת Dash -אנא **החליקו שמאלה** ללשונית **DASH** בה תוכלו לנהל את כל פונקציות הפוד (חלק מהפונקציות הללו אינן מופעלות או גלויות ללא פוד פעיל): +Please **swipe left** to the **DASH** tab where you will be able to manage all pod functions (some of these functions are not enabled or visible without an active pod session): ![Refresh_LOGO](../images/DASH_images/Refresh_LOGO.png) 'Refresh' pod connectivity and status, be able to silence pod alarms when the pod beeps @@ -100,7 +106,7 @@ To verify that you have selected the DASH in **AAPS**, if you have checked the b Ensure that the new pod and the phone running **AAPS** are within close proximity of each other and click the **Next** button. -**NOTE**: if the error message below pops up _'Could not find an available pod for activation'_ (this can happen), do not panic. לחצו על **נסה שוב**. ברוב המצבים ההפעלה תימשך בהצלחה. +**NOTE**: if the error message below pops up _'Could not find an available pod for activation'_ (this can happen), do not panic. Click on the **Retry** button. In most situations activation will continue successfully. ![Activate_Pod_3](../images/DASH_images/Activate_pod_error.png) @@ -140,16 +146,16 @@ Ensure that the new pod and the phone running **AAPS** are within close proximit ​ ![Activate_Pod_15](../images/DASH_images/Activate_Pod/Activate_Pod_15.jpg) -מומלץ לייצא הגדרות לאחר הפעלת הפוד. Export settings should be done at each pod change and once a month, copy the exported file to your internet drive. see [**Export settings Doc**](../Maintenance/ExportImportSettings.md). +It is good practice to export settings AFTER activating the pod. Export settings should be done at each pod change and once a month, copy the exported file to your internet drive. see [**Export settings Doc**](../Maintenance/ExportImportSettings.md). (OmnipodDASH-deactivate-pod)= ### Deactivate Pod -בנסיבות רגילות, פוד אמור לפעול שלושה ימים (72 שעות) ועוד 8 שעות לאחר אזהרת תפוגתו, סך הכל 80 שעות שימוש בפוד. +Under normal circumstances, the expected lifetime of a pod is three days (72 hours) and an additional 8 hours after the pod expiration warning for a total of 80 hours of pod usage. -כיצד להשבית את הפוד (מתוקף התפוגה או בעקבות כשל של הפוד): +To deactivate a pod (either from expiration or from a pod failure): 1. נווטו ללשונית **DASH** ולחצו על **ניהול הפוד (1)** ולאחר מכן בחרו **ניהול פוד** ואז **כבה פוד**. @@ -182,7 +188,7 @@ Ensure that the new pod and the phone running **AAPS** are within close proximit **Note**: During **Profile Switches**, DASH must suspend delivery before setting the new basal **Profile** as delivery can be suspended. Read [**Delivery suspended**](#delivery-suspended) in the troubleshooting section for more details. -השתמשו בפקודה זו כדי להנחות את הפוד הפעיל כעת לחדש את אספקת האינסולין. After the command is successfully processed, insulin will resume normal delivery using the current basal rate based on the current time from the active basal **Profile**. The pod will again accept commands for bolus, **TBR**, and **SMB**. +Use this command to instruct the active, currently suspended pod to resume insulin delivery. After the command is successfully processed, insulin will resume normal delivery using the current basal rate based on the current time from the active basal **Profile**. The pod will again accept commands for bolus, **TBR**, and **SMB**. 1. נווטו אל הלשונית **DASH** וודאו שהשדה **סטטוס הפוד (1)** מציג את **מופסק**, לאחר מכן הקישו על **חידוש הזרקה (2)** כדי להתחיל בתהליך הוראה לפוד הנוכחי לחדש את הזרקת האינסולין. ההודעה **חידוש הזרקה** תוצג בשדה **סטטוס הפוד (3)**. @@ -198,9 +204,9 @@ Ensure that the new pod and the phone running **AAPS** are within close proximit ### השתקת התראות פוד -*הערה - הלחצן 'השתקה' זמין רק בלשונית **DASH** כאשר הופעלה התראה על תפוגת הפוד או התראת מכל נמוך. אם לחצן השתקת ההתראות לא גלוי ואתם שומעים צפצוף מהפוד, נסו ללחוץ על 'רענן סטטוס הפוד'.* +*NOTE - The SILENCE ALERTS button is only available on the **DASH** tab when the pod expiration or low reservoir alert has been triggered. If the SILENCE ALERTS button is not visible and you hear beep sounds from the pod, try to 'Refresh pod status'.* -התהליך שלהלן יראה כיצד לאשר ולבטל צפצופים של הפוד המתרחשים כאשר זמן פעולת הפוד מתקרב למגבלת הזמן של הפוד של 72 שעות (3 ימים). מגבלת זמן אזהרה זו מוגדרת ב**שעות לפני כיבוי** שבהגדרת התראות ה-Dash. אורך החיים המרבי של פוד הוא 80 שעות (3 ימים ו-8 שעות), אולם היצרן ממליץ שלא לחרוג מ-72 השעות (3 ימים). +The process below will show you how to acknowledge and dismiss pod beeps when the active pod time reaches the warning time limit before the pod expiration of 72 hours (3 days). This warning time limit is defined in the **Hours before shutdown** Dash alerts setting. The maximum life of a pod is 80 hours (3 days 8 hours), however Insulet recommends not exceeding the 72 hours (3 days) limit. 1. כאשר הפוד יגיע לזמן האזהרה **שעות לפני כיבוי**, הוא יצפצף צפצוף אזהרה כדי להודיע שהוא מתקרב לזמן התפוגה שלו ובקרוב תידרש החלפת פוד. אפשר לאמת זאת בלשונית **DASH**, השדה **תפוגת הפוד: (1)** יציג את השעה המדויקת בה הפוד יפוג (72 שעות לאחר ההפעלה) והטקסט יצבע ב**אדום** לאחר שהזמן הזה יעבור. בשדה **התראות פוד פעילות (2)** מוצגת הודעת המצב **תוקף הפוד יפוג בקרוב**. כעת יופעל הלחצן **השתקת התראות (3)**. @@ -221,11 +227,11 @@ Ensure that the new pod and the phone running **AAPS** are within close proximit ### הצגת היסטוריית הפוד -This section explains how to review your active pod history and filter by different action categories. כלי היסטוריית הפוד מאפשר לצפות בפעולות והתוצאותיהן שנעשו בעת השימוש בפוד במהלך השימוש בו (72 - 80 שעות). +This section explains how to review your active pod history and filter by different action categories. The pod history tool allows you to view the actions and results committed to your currently active pod during its three days (72 - 80 hours) life. -תכונה זו מועילה לאימות בולוסים, בזאלים זמניים ופקודות בזאליות שנשלחו לפוד. הקטגוריות הנותרות שימושיות באופן כללי לפתרון בעיות וקביעת סדר האירועים שהתרחשו עד לכשל. +This feature is helpful in verifying boluses, TBRs and basal commands that were sent to the pod. The remaining categories are useful for troubleshooting issues and determining the order of events that occurred leading up to a failure. -*הערה:* **רק הפקודה האחרונה יכולה להיות לא ודאית**. פקודות חדשות *לא יישלחו* עד שהפקודה "הלא ודאית" האחרונה תהפוך ל'אושרה' או 'נדחתה'. הדרך 'לתקן' פקודות לא ודאיות היא **'רענון סטטוס הפוד'**. +*NOTE:* **Only the last command can be uncertain**. New commands *will not be sent* until the **last 'uncertain' command becomes 'confirmed' or 'denied'**. The way to 'fix' uncertain commands is to **'refresh pod status'**. 1. נווטו ללשונית **DASH** ולחצו על **ניהול הפוד (1)** ולאחר מכן בחרו **היסטוריית פוד (2)** כדי לפתוח את מסך היסטוריית הפוד. @@ -246,9 +252,9 @@ This section explains how to review your active pod history and filter by differ ## לשונית DASH -להלן הסבר על מבנה ומשמעות הסמלים ושדות הסטטוס בלשונית **DASH** בממשק הראשי של AAPS. +Below is an explanation of the layout and meaning of the icons and status fields on the **DASH** tab in the main AAPS interface. -*הערה: אם הודעה כלשהי בשדות הסטטוס מדווחת "(לא בטוח)", יהיה עליכם ללחוץ על כפתור הרענון כדי לרענן את מצב הפוד.* +*NOTE: If any message in the **DASH** tab status fields report (uncertain), then you will need to press the Refresh button to clear it and refresh the pod status.* ![DASH_Tab_1](../images/DASH_images/DASH_Tab/DASH_Tab_1.png) @@ -283,19 +289,19 @@ This section explains how to review your active pod history and filter by differ ### מקשים -![Refresh_Icon](../images/DASH_images/Refresh_LOGO.png) : שולח פקודת רענון לפוד לעדכון התקשורת. +![Refresh_Icon](../images/DASH_images/Refresh_LOGO.png) : Sends a refresh command to the active pod to update communication. * השתמשו כדי לרענן את מצב הפוד ולבטל סטטוסים המכילים את הטקסט "(לא ודאי)". * לקריאה נוספת ראו את הפרק פתרון בעיות מטה. -![POD_MGMT_Icon](../images/DASH_images/POD_MGMT_LOGO.png) : מנווט אל תפריט ניהול הפוד. +![POD_MGMT_Icon](../images/DASH_images/POD_MGMT_LOGO.png) : Navigates to the Pod management menu. -![ack_alert_logo](../images/DASH_images/ack_alert_logo.png) : לחיצה תשבית את הצפצופים והתראות של הפוד (תפוגה, מכל מרוקן...). +![ack_alert_logo](../images/DASH_images/ack_alert_logo.png) : When pressed this will disable the pod alerts beeps and notifications (expiry, low reservoir..). * הלחצן מוצג רק לאחר אזהרת התפוגה של הפוד. * לאחר קבלת ההתראה, אייקון זה יפסיק להופיע. -![RESUME_Icon](../images/DASH_images/DASH_tab_icons/RESUME_Icon.png) : מחדש את הזרקת האינסולין שהושהתה בפוד הנוכחי. +![RESUME_Icon](../images/DASH_images/DASH_tab_icons/RESUME_Icon.png) : Resumes the currently suspended insulin delivery in the active pod. ### תפריט ניהול הפוד @@ -314,25 +320,25 @@ Below is the meaning of the icons on the **Pod Management** menu accessed by pre ## הגדרות Dash -בפינה הימנית-עליונה **בתפריט ההמבורגר (☰)** בחרו **בונה התצורה (1)** ← **משאבה** ← **Dash** ← **בחירת הכפתור העגול ("כפתור רדיו") (2) ← גלגל שיניים (3)**. Selecting the **checkbox (4)** next to the **Settings Gear (3)** will allow the Dash menu to be displayed as a tab in the **AAPS** interface titled **DASH**. +The Dash driver settings are configurable from the top-left hand corner **hamburger menu** under **Config Builder (1)**\ ➜\ **Pump**\ ➜\ **Dash**\ ➜\ **Settings Gear (3)** by selecting the **radio button (2)** titled **Dash**. Selecting the **checkbox (4)** next to the **Settings Gear (3)** will allow the Dash menu to be displayed as a tab in the **AAPS** interface titled **DASH**. ![Dash_settings_1](../images/DASH_images/Enable_Dash/Enable_Dash_3.png) -**הערה:** דרך מהירה יותר לגשת ל**הגדרות Dash** היא על ידי פתיחת**תפריט 3 הנקודות (⋮) (1)** בפינה הימנית העליונה של הלשונית **DASH** ובחירה ב**העדפות Dash (2)** מהתפריט שנפתח. +**NOTE:** A faster way to access the **Dash settings** is by accessing the **3 dot menu (1)** in the upper right hand corner of the **DASH** tab and selecting **Dash preferences (2)** from the dropdown menu. ![Dash_settings_3](../images/DASH_images/Dash_settings/Dash_settings_3.png) -להלן קבוצות ההגדרות; תוכלו להפעילן או להשביתן באמצעות מתגים שיש לרוב ההגדרות המתוארות להלן: +The settings groups are listed below; you can enable or disable via a toggle switch for most entries described below: -*הערה: כוכבית (*) מציינת את ברירת המחדל של הגדרה מופעלת.* +*NOTE: An asterisk (\*) denotes the default setting is enabled.* ### צפצופי אישור ![Dash_settings_4](../images/DASH_images/Dash_settings/Dash_settings_4.jpg) -מספק צפצופי אישור מהפוד על ביצוע בולוס, שינויים במינון הבזאלי, בזאלי זמני, SMB ושינויים אחרים. +Provides confirmation beeps from the pod for bolus, basal, SMB, and TBR delivery and changes. * **צפצופי בולוס מופעלים:** הפעלה או השבתת צפצופי אישור כאשר מוזרק בולוס. * **צפצופי בזאלי מופעלים:** הפעלת או השבתת צפצופי אישור כאשר נקבע מינון בזאלי חדש, המינון הבזאלי הפעיל מבוטל או המינון הבזאלי הנוכחי משתנה. @@ -345,7 +351,7 @@ Below is the meaning of the icons on the **Pod Management** menu accessed by pre Provides **AAPS** alerts for pod expiration, shutdown, low reservoir based on the defined threshold units. -*שימו לב כי הודעת AAPS תינתן תמיד לכל התראה לאחר התקשורת הראשונית עם הפוד מאז הופעלה ההתראה. דחיית ההודעה לא תבטל את ההתראה, אלא אם כן מופעל אישור התראות פוד אוטומטי. כדי לבטל את ההתראה באופן ידני, יש לבקר בלשונית **DASH** וללחוץ על **השתקת התראות**.* +*Note an AAPS notification will ALWAYS be issued for any alert after the initial communication with the pod since the alert was triggered. Dismissing the notification will NOT dismiss the alert UNLESS automatically acknowledge Pod alerts is enabled. To MANUALLY dismiss the alert you must visit the **DASH** tab and press the **Silence ALERTS button**.* * **תזכורת לתפוגה מופעלת:** הפעילו או השביתו תזכורת לתפוגת הפוד שתופעל כאשר יגיע מספר השעות שהגדרתם לפני ההשבתה. * **שעות לפני כיבוי:** מגדיר את מספר השעות לפני כיבוי הפוד הפעיל, שלאחר מכן תופעל תזכורת לתפוגה. @@ -358,7 +364,7 @@ Provides **AAPS** alerts for pod expiration, shutdown, low reservoir based on th The Notification section allows the user to so select their preferred notifications and audible phone alerts when it is uncertain if TBR, SMB, or bolus, and delivery suspended events were successful. -*הערה: אלה הן התראות בלבד, לא מתבצעות התראות מסוג צפצופים.* +*NOTE: These are notifications only, no audible beep alerts are made.* * **Sound for uncertain TBR notifications enabled:** Enable or disable this setting to trigger an audible alert and visual notification when **AAPS** is uncertain if a TBR was successfully set. * **Sound for uncertain SMB notifications enabled:** Enable or disable this setting to trigger an audible alert and visual notification when **AAPS**is uncertain if an SMB was successfully delivered. @@ -377,14 +383,14 @@ This tab is well documented in the main**AAPS**documentation but there are a few ### כמות במכל -**יתרת אינסולין** +**Insulin Level** -Insulin level displayed is the amount reported by DASH. עם זאת, הוא מדווח רק על יתרת אינסולין מדוייקת רק כאשר היא מתחת ל-50 יחידות. עד אז יוצג "מעל 50 יחידות". הכמות המדווחת אינה מדויקת: כאשר הפוד מדווח על 'ריק' ברוב המקרים עדיין יישארו מספר יחידות אינסולין נוספות. The DASH overview tab will display as described the below: +Insulin level displayed is the amount reported by DASH. However, the pod only reports the actual insulin reservoir level when it is below 50 units. Until then “Above 50 units” will be displayed. The amount reported is not exact: when the pod reports ‘empty’ in most cases the reservoir will still have some additional units of insulin left. The DASH overview tab will display as described the below: * **Above 50 Units** - The pod reports more than 50 units currently in the reservoir. * **מתחת ל-50 יחידות** - כמות האינסולין שנותרה במכל כפי שדווח על ידי הפוד. -הערות נוספות: +Additional note: * **SMS** - מחזירה ערך או 50+U בתגובות של SMS * **נייטסקאוט** - העלאת ערך של 50 כאשר מעל 50 יחידות לנייטסקאוט (גרסה 14.07 ומעלה). גרסאות חדשות יותר ידווחו על ערך של 50+ כאשר מעל 50 יחידות. @@ -402,43 +408,43 @@ Insulin level displayed is the amount reported by DASH. עם זאת, הוא מד - If **AAPS** fails to resume delivery on its own (this happens if the pod is unreachable, sound is muted, etc), the pod will start beeping 4 times every minute for 3 minutes, then repeated every 15 minutes if delivery is still suspended for more than 20 minutes. * עבור פקודות לא ודאיות, "רענון סטטוס הפוד" אמור לאשר\לדחות אותן. -**הערה:** כאשר שומעים צפצופים מהפוד, אל תניחו שההזרקה תימשך מבלי לבדוק את הטלפון, ההזרקה עלולה להישאר מופסקת **ולכן עליכם לוודא!** +**Note:** When you hear beeps from the pod, do not assume that delivery will continue without checking the phone, delivery might stay suspended, **so you need to check !** ### שגיאות בפוד -פודים נכשלים מדי פעם בשל מגוון בעיות, כולל בעיות חומרה של הפוד עצמו. הנוהג הטוב ביותר הוא לא להודיע אותם למשווק המשאבה, מכיוון ש- AAPS אינו מקרה שימוש מאושר. ניתן [**למצוא כאן**](https://github.com/openaps/openomni/wiki/Fault-event-codes) רשימה של קודי תקלות כדי לסייע בקביעת הסיבה. +Pods fail occasionally due to a variety of issues, including hardware issues with the Pod itself. It is best practice not to call these into Insulet, since AAPS is not an approved use case. A list of fault codes can be [**found here**](https://github.com/openaps/openomni/wiki/Fault-event-codes) to help determine the cause. ### מניעת שגיאה 49 - כישלונות פוד -כשל זה קשור למצב פוד שגוי עבור פקודה או שגיאה במהלך פקודת אספקת אינסולין. זה קורה כאשר מנהל ההתקן והפוד אינם מסכימים על המצב בפועל. The Pod (out of a built-in safety measure) then reacts with an unrecoverable error code 49 (0x31) ending up with what is know as a “screamer”: the long irritating beep that can only be stopped by punching a hole at the appropriate location at the back of the Pod. לעתים קרובות קשה לברר את המקור המדויק של "כשל פוד 49". מצבים שיש חשד לכישלון זה (למשל בקריסות אפליקציה, הפעלת גרסת פיתוח או התקנה מחדש). +This failure is related to an incorrect pod state for a command or an error during an insulin delivery command. This is when the driver and Pod disagree on the actual state. The Pod (out of a built-in safety measure) then reacts with an unrecoverable error code 49 (0x31) ending up with what is know as a “screamer”: the long irritating beep that can only be stopped by punching a hole at the appropriate location at the back of the Pod. The exact origin of a “49 pod failure” often is hard to trace. In situations that are suspected for this failure to occur (for instance on application crashes, running a development version or re-installation). ### התראות המשאבה אינה נגישה -כאשר לא ניתן ליצור תקשורת עם הפוד למשך זמן מוגדר מראש תוצג התראה "משאבה בלתי ניתנת להשגה". ניתן להגדיר התראות על שלא ניתן להגיע למשאבה על ידי מעבר לתפריט שלוש הנקודות בצד שמאל למעלה, בחירה ב**העדפות** ← **התראות מקומיות** ← ** סף משאבה בלתי נגישה [min]**. הערך המומלץ הוא התראה לאחר **120** דקות. +When no communication can be established with the pod for a preconfigured time a “Pump unreachable” alert will be raised. Pump unreachable alerts can be configured by going to the top right-hand side three-dot menu, selecting **Preferences**\ ➜\ **Local Alerts**\ ➜\ **Pump unreachable threshold [min]**. Recommended value is alerting after **120** minutes. ### ייצוא הגדרות Exporting **AAPS** settings enables you to restore all your settings, and maybe more importantly, all your Objectives. You may need to restore settings to the “last known working situation” or after uninstalling/reinstalling **AAPS** or in case of phone loss, reinstalling on the new phone. -הערה: מידע הפוד הפעיל כלול בהגדרות המיוצאות. אם אתה תייבאו קובץ מיוצא "ישן", הפוד הנוכחי "ימות". אין אלטרנטיבה אחרת. In some cases (like a _programmed_ phone change), you may need to use the exported file to restore **AAPS'** settings **while keeping the current active Pod**. במקרה זה חשוב להשתמש רק בקובץ ההגדרות שיוצא לאחרונה המכיל את הפוד הפעיל כעת. +Note: The active pod information is included in the exported settings. If you import an "old" exported file, your actual pod will "die". There is no other alternative. In some cases (like a _programmed_ phone change), you may need to use the exported file to restore **AAPS'** settings **while keeping the current active Pod**. In this case it is important to only use the recently exported settings file containing the pod currently active. -**מומלץ לבצע ייצוא מיד לאחר הפעלת פוד**. This way you will always be able to restore the current active pod in case of a problem. למשל במקרה של מעבר לטלפון רזרבי. +**It is good practice to do an export immediately after activating a pod**. This way you will always be able to restore the current active pod in case of a problem. For instance when moving to another backup phone. -העתיקו באופן קבוע את ההגדרות המיוצאות למקום בטוח (לדוגמה לכונן ענן) שניתן לגשת אליו בכל טלפון בעת הצורך (למשל במקרה של אובדן טלפון או איפוס להגדרות היצרן של הטלפון). +Regularly copy your exported settings to a safe place (as a cloud drive) that can be accessible by any phone when needed (e.g. in case of a phone loss or factory reset of the actual phone). ### יבוא הגדרות -**אזהרה** שימו לב שייבוא הגדרות עלול לייבא סטטוס פוד מיושן. כתוצאה מכך, קיים סיכון לאיבוד הפוד הפעיל! (ראו **ייצוא הגדרות**). עדיף לנסות זאת רק כאשר אין אפשרויות אחרות זמינות. +**WARNING** Please note that importing settings will possibly import an outdated Pod status. As a result, there is a risk of losing the active Pod! (see **Exporting Settings**). It is better to only try it when no other options are available. -בעת ייבוא הגדרות עם פוד פעיל, ודאו שהייצוא בוצע עם הפוד הפעיל הנוכחי. +When importing settings with an active Pod, make sure the export was done with the currently active pod. -**ייבוא תוך כדי פוד פעיל:** (אתם מסתכנים באיבוד הפוד!) +**Importing while on an active Pod:** (you risk losing the Pod!) 1. ודאו שאתם מייבאים הגדרות שיוצאו לאחרונה עם הפוד הפעיל כעת. 2. ייבאו את ההגדרות. 3. בדיקת על ההגדרות. -**ייבוא (ללא פוד פעיל)** +**Importing (no active Pod session)** 1. ייבוא כל קובץ מיוצא עדכני אמור לעבוד (ראה למעלה) 2. ייבאו את ההגדרות. @@ -447,13 +453,13 @@ Exporting **AAPS** settings enables you to restore all your settings, and maybe ### ייבוא הגדרות המכילות מצב פוד מפוד לא פעיל -בעת ייבוא הגדרות המכילות נתונים עבור פוד שכבר אינו פעיל, AndroidAPS ינסה להתחבר אליו, מה שכמובן ייכשל. אין באפשרותכם להפעיל פוד חדש במצב זה. +When importing settings containing data for a Pod that is no longer active, AAPS will try to connect with it, which will obviously fail. You can not activate a new Pod in this situation. -To remove the old pod session “try” to de-activate the Pod. הכיבוי ייכשל. בחרו "נסה שוב". לאחר הניסיון השני או השלישי תקבלו את האפשרות להסיר את הפוד. Once the old pod is removed you will be able to activate a new pod. +To remove the old pod session “try” to de-activate the Pod. The de-activation will fail. Select “Retry”. After the second or third retry you will get the option to remove the pod. Once the old pod is removed you will be able to activate a new pod. ### התקנה מחדש של AndroidAPS -When uninstalling**AAPS** you will lose all your settings, objectives and the current Pod session. ע"מ לשחזר אותם ודאו שיש לכם קובץ הגדרות שיוצא לאחרונה זמין! +When uninstalling**AAPS** you will lose all your settings, objectives and the current Pod session. To restore them make sure you have a recent exported settings file available! When on an active Pod, make sure that you have an export for the current pod session or you will lose the currently active pod when importing older settings. @@ -467,7 +473,7 @@ When on an active Pod, make sure that you have an export for the current pod ses ### עדכון AndroidAPS לגרסה חדשה יותר -ברוב המקרים אין צורך להסיר את ההתקנה. ניתן לבצע התקנה "דורסת" על ידי התחלת ההתקנה של הגרסה החדשה. זה אפשרי גם עם פוד פעיל. +In most cases there is no need to uninstall. You can do an “in-place” install by starting the installation for the new version. This is also possible when on an active Pod session. 1. ייבאו את ההגדרות. 2. Install the new **AAPS** version. @@ -477,7 +483,7 @@ When on an active Pod, make sure that you have an export for the current pod ses ### התראות פוד -לידיעתכם, מנהל ההתקן של Dash מציג מגוון התראות ייחודיות בלשונית **סקירה כללית**, רובן אינפורמטיביות וניתנות לביטול בעוד שחלקן מספקות למשתמש פעולה לבצע על מנת לפתור את הסיבה להתראה המופעלת. להלן סיכום של ההתראות העיקריות בהן אתם עשויים להיתקל: +Please note that the Omnipod Dash driver presents a variety of unique alerts on the **Overview tab**, most of them are informational and can be dismissed while some provide the user with an action to take to resolve the cause of the triggered alert. A summary of the main alerts that you may encounter is listed below: * No active Pod session detected. ניתן לבטל התראה זו זמנית על ידי לחיצה על **השתקה** אך היא תמשיך לפעול כל עוד לא הופעל פוד חדש. Once activated this alert is automatically silenced. * Pod suspended Informational alert that pod has been suspended. diff --git a/docs/CROWDIN/he/CompatiblePumps/OmnipodEros.md b/docs/CROWDIN/he/CompatiblePumps/OmnipodEros.md index f59845335ffa..c9eaf58a9419 100644 --- a/docs/CROWDIN/he/CompatiblePumps/OmnipodEros.md +++ b/docs/CROWDIN/he/CompatiblePumps/OmnipodEros.md @@ -43,7 +43,7 @@ These instructions will assume that you are starting a new pod session; if this **SAFETY FIRST** - do not attempt this process in an environment where you cannot recover from an error (extra pods, insulin, charged RileyLink, and phone devices are must-haves). -**Your Omnipod PDM will no longer work after the AAPS Omnipod driver activates your pod**. Previously you used your Omnipod PDM to send commands to your Omnipod Eros pod. An Omnipod Eros pod only allows a single device to send communication to it. המכשיר שמפעיל את הפוד הוא המכשיר היחיד שמורשה לתקשר איתו מאותה נקודה ואילך. This means that once you activate an Omnipod Eros pod with your RileyLink through the AAPS Omnipod driver, **you will no longer be able to use your PDM with your pod**. The AAPS Omnipod driver with the RileyLink is now your acting PDM. *This does NOT mean you should throw away your PDM, it is recommended to keep it around as a backup, and for emergencies with AAPS is not working correctly.* +**Your Omnipod PDM will no longer work after the AAPS Omnipod driver activates your pod**. Previously you used your Omnipod PDM to send commands to your Omnipod Eros pod. An Omnipod Eros pod only allows a single device to send communication to it. The device that successfully activates the pod is the only device allowed to communicate with it from that point forward. This means that once you activate an Omnipod Eros pod with your RileyLink through the AAPS Omnipod driver, **you will no longer be able to use your PDM with your pod**. The AAPS Omnipod driver with the RileyLink is now your acting PDM. *This does NOT mean you should throw away your PDM, it is recommended to keep it around as a backup, and for emergencies with AAPS is not working correctly.* **You can configure multiple RileyLinks, but only one selected RileyLink at a time can communicate with a pod.** The AAPS Omnipod driver supports the ability to add multiple RileyLinks in the RileyLink configuration, however, only one RileyLink at a time can be selected to be used for sending and receiving communication. @@ -191,7 +191,7 @@ Before you can activate a pod please ensure you have properly configured and con Under normal circumstances, the life of a pod should run for three days (72 hours) and an additional 8 hours after the pod expiration warning for a total of 80 hours of pod usage. -כיצד להשבית את הפוד (מתוקף התפוגה או בעקבות כשל של הפוד): +To deactivate a pod (either from expiration or from a pod failure): 1. Go to the **Omnipod (POD)** tab, click on the **POD MGMT (1)** button, on the **Pod management** screen click on the **Deactivate Pod (2)** button. @@ -245,7 +245,7 @@ Use this command to put the active pod into a suspended state. In this suspended #### חידוש הזרקת האינסולין -השתמשו בפקודה זו כדי להנחות את הפוד הפעיל כעת לחדש את אספקת האינסולין. לאחר עיבוד הפקודה, מתן האינסולין יחודש לפי המינון הבזאלי הנוכחי בהתאם להגדרתו בפרופיל. הפוד יקבל שוב פקודות עבור בולוס, מינון בזאלי זמני ו-SMB. +Use this command to instruct the active, currently suspended pod to resume insulin delivery. לאחר עיבוד הפקודה, מתן האינסולין יחודש לפי המינון הבזאלי הנוכחי בהתאם להגדרתו בפרופיל. הפוד יקבל שוב פקודות עבור בולוס, מינון בזאלי זמני ו-SMB. 1. Go to the **Omnipod (POD)** tab and ensure the **Pod status (1)** field displays **Suspended**, then press the **Resume Delivery (2)** button to start the process to instruct the current pod to resume normal insulin delivery. A message **RESUME DELIVERY** will display in the **Pod status (3)** field, signifying the RileyLink is actively sending the command to the suspended pod. @@ -574,7 +574,7 @@ The Omnipod driver settings are configurable from the top-left hand corner **ham ![Omnipod_Settings_2](../images/omnipod/Omnipod_Settings_2.png) -להלן קבוצות ההגדרות; תוכלו להפעילן או להשביתן באמצעות מתגים שיש לרוב ההגדרות המתוארות להלן: +The settings groups are listed below; you can enable or disable via a toggle switch for most entries described below: ![Omnipod_Settings_3](../images/omnipod/Omnipod_Settings_3.png) @@ -595,7 +595,7 @@ Allows for scanning of a pod communication device. The Omnipod driver cannot sel ### צפצופי אישור -מספק צפצופי אישור מהפוד על ביצוע בולוס, שינויים במינון הבזאלי, בזאלי זמני, SMB ושינויים אחרים. +Provides confirmation beeps from the pod for bolus, basal, SMB, and TBR delivery and changes. - **\*Bolus beeps enabled:** Enable or disable confirmation beeps when a bolus is delivered. - **\*Basal beeps enabled:** Enable or disable confirmation beeps when a new basal rate is set, active basal rate is canceled or current basal rate is changed. @@ -606,7 +606,7 @@ Allows for scanning of a pod communication device. The Omnipod driver cannot sel Provides AAPS alerts and Nightscout announcements for pod expiration, shutdown, low reservoir based on the defined threshold units. -*שימו לב כי הודעת AAPS תינתן תמיד לכל התראה לאחר התקשורת הראשונית עם הפוד מאז הופעלה ההתראה. דחיית ההודעה לא תבטל את ההתראה, אלא אם כן מופעל אישור התראות פוד אוטומטי. To MANUALLY dismiss the alert you must visit the Omnipod (POD) tab and press the ACK ALERTS button.* +*Note an AAPS notification will ALWAYS be issued for any alert after the initial communication with the pod since the alert was triggered. Dismissing the notification will NOT dismiss the alert UNLESS automatically acknowledge Pod alerts is enabled. To MANUALLY dismiss the alert you must visit the Omnipod (POD) tab and press the ACK ALERTS button.* - **\*Expiration reminder enabled:** Enable or disable the pod expiration reminder set to trigger when the defined number of hours before shutdown is reached. - **שעות לפני כיבוי:** מגדיר את מספר השעות לפני כיבוי הפוד הפעיל, שלאחר מכן תופעל תזכורת לתפוגה. @@ -618,7 +618,7 @@ Provides AAPS alerts and Nightscout announcements for pod expiration, shutdown, Provides AAPS notifications and audible phone alerts when it is uncertain if TBR, SMB, or bolus events were successful. -*הערה: אלה הן התראות בלבד, לא מתבצעות התראות מסוג צפצופים.* +*NOTE: These are notifications only, no audible beep alerts are made.* - **התראת צליל של בזאלי זמני לא ברור מאופשרת:** הפעילו או השביתו הגדרה זו כדי להפעיל התראה קולית והתראה חזותית כאשר AAPS לא בטוח אם מינון בזאלי זמני הוגדר בהצלחה. - **\*Sound for uncertain SMB notifications enabled:** Enable or disable this setting to trigger an audible alert and visual notification when AAPS is uncertain if an SMB was successfully delivered. @@ -690,7 +690,7 @@ This tab is well documented in the main AAPS documentation but there are a few i ### Levels -**יתרת אינסולין** +**Insulin Level** Reporting of the amount of insulin in the Omnipod Eros Pod is not exact. This is because it is not known exactly how much insulin was put in the pod, only that when the 2 beeps are triggered while filling the pod that over 85 units have been injected. A Pod can hold a maximum of 200 units. Priming can also introduce variance as it is not and exact process. With both of these factors, the Omnipod driver has been written to give the best approximation of insulin remaining in the reservoir. @@ -716,11 +716,11 @@ Battery level reporting is a setting that can be enabled to return the current b ### שגיאות בפוד -פודים נכשלים מדי פעם בשל מגוון בעיות, כולל בעיות חומרה של הפוד עצמו. הנוהג הטוב ביותר הוא לא להודיע אותם למשווק המשאבה, מכיוון ש- AAPS אינו מקרה שימוש מאושר. A list of fault codes can be found [here](https://github.com/openaps/openomni/wiki/Fault-event-codes) to help determine the cause. +Pods fail occasionally due to a variety of issues, including hardware issues with the Pod itself. It is best practice not to call these into Insulet, since AAPS is not an approved use case. A list of fault codes can be found [here](https://github.com/openaps/openomni/wiki/Fault-event-codes) to help determine the cause. ### מניעת שגיאה 49 - כישלונות פוד -כשל זה קשור למצב פוד שגוי עבור פקודה או שגיאה במהלך פקודת אספקת אינסולין. We recommend users to switch to the Nightscout client to *upload only (Disable sync)* under the **Config Builder**➜**General**➜**NSClient**➜**cog wheel**➜**Advanced Settings** to prevent possible failures. +This failure is related to an incorrect pod state for a command or an error during an insulin delivery command. We recommend users to switch to the Nightscout client to *upload only (Disable sync)* under the **Config Builder**➜**General**➜**NSClient**➜**cog wheel**➜**Advanced Settings** to prevent possible failures. ### התראות המשאבה אינה נגישה @@ -739,7 +739,7 @@ Please note that importing settings has the possibility to import an outdated Po ### התראות פוד -please note that the Omnipod driver presents a variety of unique alerts on the **Overview tab**, most of them are informational and can be dismissed while some provide the user with an action to take to resolve the cause of the triggered alert. להלן סיכום של ההתראות העיקריות בהן אתם עשויים להיתקל: +please note that the Omnipod driver presents a variety of unique alerts on the **Overview tab**, most of them are informational and can be dismissed while some provide the user with an action to take to resolve the cause of the triggered alert. A summary of the main alerts that you may encounter is listed below: #### No active Pod diff --git a/docs/CROWDIN/he/GettingHelp/GeneralTroubleshooting.md b/docs/CROWDIN/he/GettingHelp/GeneralTroubleshooting.md index 75dfdfd383e5..8bd4d06f2c7c 100644 --- a/docs/CROWDIN/he/GettingHelp/GeneralTroubleshooting.md +++ b/docs/CROWDIN/he/GettingHelp/GeneralTroubleshooting.md @@ -37,14 +37,37 @@ Ignore it: More details, Install anyway. * [SMS commands](#SMSCommands-troubleshooting) -### Frequent bluetooth connection problems +### Frequent Bluetooth connection problems -This can happen with various pumps. Apart from excluding AAPS from any battery optimization, you can also exclude the system bluetooth app from battery optimization. This can help in some cases. Depending on the phone you use, you will find the bluetooth app differently. +#### Android 15 + +```{warning} +Developers are working on this issue impacting **AAPS** on some Samsung and Pixel phones. +``` + +After upgrading Android or moving to a recent phone, **AAPS** frequently loses Bluetooth connection to the pump. The problem disappears temporarily when restarting the phone. If the phone runs Android 15, you can try to enable the following: + +1) **Open preferences** by clicking the three-dot menu on the top right side of the home screen. + + +![Open preferences](../images/Pref2020_Open2.png) + +2. Scroll down and open the **Confirmation beeps** / **Advanced** submenu. Enable **Bond BT device on Android 15+**. + + ![BondBT](../images/troubleshooting/BondBT.png) + +3. If the pump asks for a pairing request, accept it. + +4. Restart your phone. + +#### Battery optimization + +This can happen with various pumps. Apart from excluding AAPS from any battery optimization, you can also exclude the system Bluetooth app from battery optimization. This can help in some cases. Depending on the phone you use, you will find the Bluetooth app differently. Here are examples how to find them on specific android phones. -#### Pixel phones (stock android) +##### Pixel phones (stock Android) * Go to the android settings, select "Apps". @@ -67,7 +90,7 @@ Here are examples how to find them on specific android phones. ![BT Battery optimization](../images/troubleshooting/pixel/04_btunrestricted.png) -#### Samsung phones +##### Samsung phones * Go to the android settings, select "Apps" diff --git a/docs/CROWDIN/he/images/troubleshooting/BondBT.png b/docs/CROWDIN/he/images/troubleshooting/BondBT.png new file mode 100644 index 000000000000..96b2fb272d90 Binary files /dev/null and b/docs/CROWDIN/he/images/troubleshooting/BondBT.png differ diff --git a/docs/CROWDIN/he/images/troubleshooting/samsung/01_BondBT_20250526.png b/docs/CROWDIN/he/images/troubleshooting/samsung/01_BondBT_20250526.png new file mode 100644 index 000000000000..74c3525959ed Binary files /dev/null and b/docs/CROWDIN/he/images/troubleshooting/samsung/01_BondBT_20250526.png differ diff --git a/docs/CROWDIN/he/images/troubleshooting/samsung/02_BondBT_20250526.png b/docs/CROWDIN/he/images/troubleshooting/samsung/02_BondBT_20250526.png new file mode 100644 index 000000000000..444013b29146 Binary files /dev/null and b/docs/CROWDIN/he/images/troubleshooting/samsung/02_BondBT_20250526.png differ diff --git a/docs/CROWDIN/he/images/troubleshooting/samsung/03_BondBT_20250526.png b/docs/CROWDIN/he/images/troubleshooting/samsung/03_BondBT_20250526.png new file mode 100644 index 000000000000..9caa7a484581 Binary files /dev/null and b/docs/CROWDIN/he/images/troubleshooting/samsung/03_BondBT_20250526.png differ diff --git a/docs/CROWDIN/he/images/troubleshooting/samsung/04_BondBT_20250526.png b/docs/CROWDIN/he/images/troubleshooting/samsung/04_BondBT_20250526.png new file mode 100644 index 000000000000..b25c1469f58e Binary files /dev/null and b/docs/CROWDIN/he/images/troubleshooting/samsung/04_BondBT_20250526.png differ diff --git a/docs/CROWDIN/ko/CompatiblePumps/OmnipodDASH.md b/docs/CROWDIN/ko/CompatiblePumps/OmnipodDASH.md index 7463422a252c..16fb7e93d7cb 100644 --- a/docs/CROWDIN/ko/CompatiblePumps/OmnipodDASH.md +++ b/docs/CROWDIN/ko/CompatiblePumps/OmnipodDASH.md @@ -18,7 +18,13 @@ These are the specifications of the **Omnipod DASH** ('DASH') and what different * On pod activation, **AAPS** will find and connect to a new DASH pod. * Expected range: 5-10 meters (YMMV). -WARNING: There are currently reported Bluetooth connection issues with the following combination of **AAPS** / DASH / Android 15. **AAPS** should not be used in combination with Android 15 and DASH unless the user has checked the following [**List**](https://docs.google.com/spreadsheets/u/1/d/e/2PACX-1vScCNaIguEZVTVFAgpv1kXHdsHl3fs6xT6RB2Z1CeVJ561AvvqGwxMhlmSHk4J056gMCAQE02sAWJvT/pubhtml?gid=683363241&single=true) and verified that their phone is not a known reported issue. **AAPS** is currently working to resolve this issue. +```{admonition} Android 15 +:class: warning + +There are currently reported Bluetooth connection issues with the following combination of **AAPS**: DASH + Android 15. +Please refrain from upgrading your phone to Android 15 unless you have checked the following [**list**](https://docs.google.com/spreadsheets/u/1/d/e/2PACX-1vScCNaIguEZVTVFAgpv1kXHdsHl3fs6xT6RB2Z1CeVJ561AvvqGwxMhlmSHk4J056gMCAQE02sAWJvT/pubhtml?gid=683363241&single=true) and verified that your phone is not a known reported issue. +If you experience frequent disconnection; try to enable Bond BT as described in: [**Bluetooth Issues**](../GettingHelp/GeneralTroubleshooting.md). +``` ## Hardware/Software Requirements diff --git a/docs/CROWDIN/ko/GettingHelp/GeneralTroubleshooting.md b/docs/CROWDIN/ko/GettingHelp/GeneralTroubleshooting.md index 78cc005f56e0..ac52a0acafab 100644 --- a/docs/CROWDIN/ko/GettingHelp/GeneralTroubleshooting.md +++ b/docs/CROWDIN/ko/GettingHelp/GeneralTroubleshooting.md @@ -37,14 +37,37 @@ Ignore it: More details, Install anyway. * [SMS commands](#SMSCommands-troubleshooting) -### Frequent bluetooth connection problems +### Frequent Bluetooth connection problems -This can happen with various pumps. Apart from excluding AAPS from any battery optimization, you can also exclude the system bluetooth app from battery optimization. This can help in some cases. Depending on the phone you use, you will find the bluetooth app differently. +#### Android 15 + +```{warning} +Developers are working on this issue impacting **AAPS** on some Samsung and Pixel phones. +``` + +After upgrading Android or moving to a recent phone, **AAPS** frequently loses Bluetooth connection to the pump. The problem disappears temporarily when restarting the phone. If the phone runs Android 15, you can try to enable the following: + +1) **Open preferences** by clicking the three-dot menu on the top right side of the home screen. + + +![Open preferences](../images/Pref2020_Open2.png) + +2. Scroll down and open the **Confirmation beeps** / **Advanced** submenu. Enable **Bond BT device on Android 15+**. + + ![BondBT](../images/troubleshooting/BondBT.png) + +3. If the pump asks for a pairing request, accept it. + +4. Restart your phone. + +#### Battery optimization + +This can happen with various pumps. Apart from excluding AAPS from any battery optimization, you can also exclude the system Bluetooth app from battery optimization. This can help in some cases. Depending on the phone you use, you will find the Bluetooth app differently. Here are examples how to find them on specific android phones. -#### Pixel phones (stock android) +##### Pixel phones (stock Android) * Go to the android settings, select "Apps". @@ -67,7 +90,7 @@ Here are examples how to find them on specific android phones. ![BT Battery optimization](../images/troubleshooting/pixel/04_btunrestricted.png) -#### Samsung phones +##### Samsung phones * Go to the android settings, select "Apps" diff --git a/docs/CROWDIN/ko/images/troubleshooting/BondBT.png b/docs/CROWDIN/ko/images/troubleshooting/BondBT.png new file mode 100644 index 000000000000..96b2fb272d90 Binary files /dev/null and b/docs/CROWDIN/ko/images/troubleshooting/BondBT.png differ diff --git a/docs/CROWDIN/ko/images/troubleshooting/samsung/01_BondBT_20250526.png b/docs/CROWDIN/ko/images/troubleshooting/samsung/01_BondBT_20250526.png new file mode 100644 index 000000000000..74c3525959ed Binary files /dev/null and b/docs/CROWDIN/ko/images/troubleshooting/samsung/01_BondBT_20250526.png differ diff --git a/docs/CROWDIN/ko/images/troubleshooting/samsung/02_BondBT_20250526.png b/docs/CROWDIN/ko/images/troubleshooting/samsung/02_BondBT_20250526.png new file mode 100644 index 000000000000..444013b29146 Binary files /dev/null and b/docs/CROWDIN/ko/images/troubleshooting/samsung/02_BondBT_20250526.png differ diff --git a/docs/CROWDIN/ko/images/troubleshooting/samsung/03_BondBT_20250526.png b/docs/CROWDIN/ko/images/troubleshooting/samsung/03_BondBT_20250526.png new file mode 100644 index 000000000000..9caa7a484581 Binary files /dev/null and b/docs/CROWDIN/ko/images/troubleshooting/samsung/03_BondBT_20250526.png differ diff --git a/docs/CROWDIN/ko/images/troubleshooting/samsung/04_BondBT_20250526.png b/docs/CROWDIN/ko/images/troubleshooting/samsung/04_BondBT_20250526.png new file mode 100644 index 000000000000..b25c1469f58e Binary files /dev/null and b/docs/CROWDIN/ko/images/troubleshooting/samsung/04_BondBT_20250526.png differ diff --git a/docs/CROWDIN/lt/CompatiblePumps/OmnipodDASH.md b/docs/CROWDIN/lt/CompatiblePumps/OmnipodDASH.md index cd6113011870..d5f0f58e29af 100644 --- a/docs/CROWDIN/lt/CompatiblePumps/OmnipodDASH.md +++ b/docs/CROWDIN/lt/CompatiblePumps/OmnipodDASH.md @@ -18,7 +18,13 @@ These are the specifications of the **Omnipod DASH** ('DASH') and what different * On pod activation, **AAPS** will find and connect to a new DASH pod. * Expected range: 5-10 meters (YMMV). -WARNING: There are currently reported Bluetooth connection issues with the following combination of **AAPS** / DASH / Android 15. **AAPS** should not be used in combination with Android 15 and DASH unless the user has checked the following [**List**](https://docs.google.com/spreadsheets/u/1/d/e/2PACX-1vScCNaIguEZVTVFAgpv1kXHdsHl3fs6xT6RB2Z1CeVJ561AvvqGwxMhlmSHk4J056gMCAQE02sAWJvT/pubhtml?gid=683363241&single=true) and verified that their phone is not a known reported issue. **AAPS** is currently working to resolve this issue. +```{admonition} Android 15 +:class: warning + +There are currently reported Bluetooth connection issues with the following combination of **AAPS**: DASH + Android 15. +Please refrain from upgrading your phone to Android 15 unless you have checked the following [**list**](https://docs.google.com/spreadsheets/u/1/d/e/2PACX-1vScCNaIguEZVTVFAgpv1kXHdsHl3fs6xT6RB2Z1CeVJ561AvvqGwxMhlmSHk4J056gMCAQE02sAWJvT/pubhtml?gid=683363241&single=true) and verified that your phone is not a known reported issue. +If you experience frequent disconnection; try to enable Bond BT as described in: [**Bluetooth Issues**](../GettingHelp/GeneralTroubleshooting.md). +``` ## Hardware/Software Requirements diff --git a/docs/CROWDIN/lt/GettingHelp/GeneralTroubleshooting.md b/docs/CROWDIN/lt/GettingHelp/GeneralTroubleshooting.md index e3b8cb322797..1b49b419dd77 100644 --- a/docs/CROWDIN/lt/GettingHelp/GeneralTroubleshooting.md +++ b/docs/CROWDIN/lt/GettingHelp/GeneralTroubleshooting.md @@ -37,14 +37,37 @@ Ignore it: More details, Install anyway. * [SMS commands](#SMSCommands-troubleshooting) -### Frequent bluetooth connection problems +### Frequent Bluetooth connection problems -This can happen with various pumps. Apart from excluding AAPS from any battery optimization, you can also exclude the system bluetooth app from battery optimization. This can help in some cases. Depending on the phone you use, you will find the bluetooth app differently. +#### Android 15 + +```{warning} +Developers are working on this issue impacting **AAPS** on some Samsung and Pixel phones. +``` + +After upgrading Android or moving to a recent phone, **AAPS** frequently loses Bluetooth connection to the pump. The problem disappears temporarily when restarting the phone. If the phone runs Android 15, you can try to enable the following: + +1) **Open preferences** by clicking the three-dot menu on the top right side of the home screen. + + +![Open preferences](../images/Pref2020_Open2.png) + +2. Scroll down and open the **Confirmation beeps** / **Advanced** submenu. Enable **Bond BT device on Android 15+**. + + ![BondBT](../images/troubleshooting/BondBT.png) + +3. If the pump asks for a pairing request, accept it. + +4. Restart your phone. + +#### Battery optimization + +This can happen with various pumps. Apart from excluding AAPS from any battery optimization, you can also exclude the system Bluetooth app from battery optimization. This can help in some cases. Depending on the phone you use, you will find the Bluetooth app differently. Here are examples how to find them on specific android phones. -#### Pixel phones (stock android) +##### Pixel phones (stock Android) * Go to the android settings, select "Apps". @@ -67,7 +90,7 @@ Here are examples how to find them on specific android phones. ![BT Battery optimization](../images/troubleshooting/pixel/04_btunrestricted.png) -#### Samsung phones +##### Samsung phones * Go to the android settings, select "Apps" diff --git a/docs/CROWDIN/lt/images/troubleshooting/BondBT.png b/docs/CROWDIN/lt/images/troubleshooting/BondBT.png new file mode 100644 index 000000000000..96b2fb272d90 Binary files /dev/null and b/docs/CROWDIN/lt/images/troubleshooting/BondBT.png differ diff --git a/docs/CROWDIN/lt/images/troubleshooting/samsung/01_BondBT_20250526.png b/docs/CROWDIN/lt/images/troubleshooting/samsung/01_BondBT_20250526.png new file mode 100644 index 000000000000..74c3525959ed Binary files /dev/null and b/docs/CROWDIN/lt/images/troubleshooting/samsung/01_BondBT_20250526.png differ diff --git a/docs/CROWDIN/lt/images/troubleshooting/samsung/02_BondBT_20250526.png b/docs/CROWDIN/lt/images/troubleshooting/samsung/02_BondBT_20250526.png new file mode 100644 index 000000000000..444013b29146 Binary files /dev/null and b/docs/CROWDIN/lt/images/troubleshooting/samsung/02_BondBT_20250526.png differ diff --git a/docs/CROWDIN/lt/images/troubleshooting/samsung/03_BondBT_20250526.png b/docs/CROWDIN/lt/images/troubleshooting/samsung/03_BondBT_20250526.png new file mode 100644 index 000000000000..9caa7a484581 Binary files /dev/null and b/docs/CROWDIN/lt/images/troubleshooting/samsung/03_BondBT_20250526.png differ diff --git a/docs/CROWDIN/lt/images/troubleshooting/samsung/04_BondBT_20250526.png b/docs/CROWDIN/lt/images/troubleshooting/samsung/04_BondBT_20250526.png new file mode 100644 index 000000000000..b25c1469f58e Binary files /dev/null and b/docs/CROWDIN/lt/images/troubleshooting/samsung/04_BondBT_20250526.png differ diff --git a/docs/CROWDIN/nl/CompatiblePumps/OmnipodDASH.md b/docs/CROWDIN/nl/CompatiblePumps/OmnipodDASH.md index d073e96b58a2..52fedcc23657 100644 --- a/docs/CROWDIN/nl/CompatiblePumps/OmnipodDASH.md +++ b/docs/CROWDIN/nl/CompatiblePumps/OmnipodDASH.md @@ -18,7 +18,13 @@ These are the specifications of the **Omnipod DASH** ('DASH') and what different * On pod activation, **AAPS** will find and connect to a new DASH pod. * Expected range: 5-10 meters (YMMV). -WARNING: There are currently reported Bluetooth connection issues with the following combination of **AAPS** / DASH / Android 15. **AAPS** should not be used in combination with Android 15 and DASH unless the user has checked the following [**List**](https://docs.google.com/spreadsheets/u/1/d/e/2PACX-1vScCNaIguEZVTVFAgpv1kXHdsHl3fs6xT6RB2Z1CeVJ561AvvqGwxMhlmSHk4J056gMCAQE02sAWJvT/pubhtml?gid=683363241&single=true) and verified that their phone is not a known reported issue. **AAPS** is currently working to resolve this issue. +```{admonition} Android 15 +:class: warning + +There are currently reported Bluetooth connection issues with the following combination of **AAPS**: DASH + Android 15. +Please refrain from upgrading your phone to Android 15 unless you have checked the following [**list**](https://docs.google.com/spreadsheets/u/1/d/e/2PACX-1vScCNaIguEZVTVFAgpv1kXHdsHl3fs6xT6RB2Z1CeVJ561AvvqGwxMhlmSHk4J056gMCAQE02sAWJvT/pubhtml?gid=683363241&single=true) and verified that your phone is not a known reported issue. +If you experience frequent disconnection; try to enable Bond BT as described in: [**Bluetooth Issues**](../GettingHelp/GeneralTroubleshooting.md). +``` ## Hardware/Software Requirements @@ -37,7 +43,7 @@ The instructions below explain how to activate a new pod session. Wait to close **SAFETY FIRST** - you should not try to connect **AAPS** to a pod for the first time without having access to extra pods, insulin, and phone devices are a must have. -**Your Omnipod Dash PDM will become redundant after the AAPS Dash driver activates your pod.** Previously a user may have operated a PDM to send commands to your DASH. A DASH will only faciiliate a single device to send commands to communicate with it. Het apparaat dat de pod activeert is het enige apparaat dat vanaf dat moment met de pod kan communiceren. This means that once you activate a DASH with your Android phone through the **AAPS**, **you will no longer be able to use your PDM with that pod**. The **AAPS** Dash driver in your Android phone is now your acting PDM. +**Your Omnipod Dash PDM will become redundant after the AAPS Dash driver activates your pod.** Previously a user may have operated a PDM to send commands to your DASH. A DASH will only faciiliate a single device to send commands to communicate with it. The device that successfully activates the pod is the only device allowed to communicate with it from that point forward. This means that once you activate a DASH with your Android phone through the **AAPS**, **you will no longer be able to use your PDM with that pod**. The **AAPS** Dash driver in your Android phone is now your acting PDM. *This does NOT mean you should throw away your PDM, it is recommended to keep it around as a backup and for emergencies, for instance when your phone gets lost or AAPS is not working correctly.* diff --git a/docs/CROWDIN/nl/CompatiblePumps/OmnipodEros.md b/docs/CROWDIN/nl/CompatiblePumps/OmnipodEros.md index 21098447be47..2a31157971b8 100644 --- a/docs/CROWDIN/nl/CompatiblePumps/OmnipodEros.md +++ b/docs/CROWDIN/nl/CompatiblePumps/OmnipodEros.md @@ -43,7 +43,7 @@ These instructions will assume that you are starting a new pod session; if this **SAFETY FIRST** - do not attempt this process in an environment where you cannot recover from an error (extra pods, insulin, charged RileyLink, and phone devices are must-haves). -**Your Omnipod PDM will no longer work after the AAPS Omnipod driver activates your pod**. Previously you used your Omnipod PDM to send commands to your Omnipod Eros pod. An Omnipod Eros pod only allows a single device to send communication to it. Het apparaat dat de pod activeert is het enige apparaat dat vanaf dat moment met de pod kan communiceren. This means that once you activate an Omnipod Eros pod with your RileyLink through the AAPS Omnipod driver, **you will no longer be able to use your PDM with your pod**. The AAPS Omnipod driver with the RileyLink is now your acting PDM. *This does NOT mean you should throw away your PDM, it is recommended to keep it around as a backup, and for emergencies with AAPS is not working correctly.* +**Your Omnipod PDM will no longer work after the AAPS Omnipod driver activates your pod**. Previously you used your Omnipod PDM to send commands to your Omnipod Eros pod. An Omnipod Eros pod only allows a single device to send communication to it. The device that successfully activates the pod is the only device allowed to communicate with it from that point forward. This means that once you activate an Omnipod Eros pod with your RileyLink through the AAPS Omnipod driver, **you will no longer be able to use your PDM with your pod**. The AAPS Omnipod driver with the RileyLink is now your acting PDM. *This does NOT mean you should throw away your PDM, it is recommended to keep it around as a backup, and for emergencies with AAPS is not working correctly.* **You can configure multiple RileyLinks, but only one selected RileyLink at a time can communicate with a pod.** The AAPS Omnipod driver supports the ability to add multiple RileyLinks in the RileyLink configuration, however, only one RileyLink at a time can be selected to be used for sending and receiving communication. diff --git a/docs/CROWDIN/nl/GettingHelp/GeneralTroubleshooting.md b/docs/CROWDIN/nl/GettingHelp/GeneralTroubleshooting.md index aaace21245f1..5496df1b02c6 100644 --- a/docs/CROWDIN/nl/GettingHelp/GeneralTroubleshooting.md +++ b/docs/CROWDIN/nl/GettingHelp/GeneralTroubleshooting.md @@ -37,14 +37,37 @@ Ignore it: More details, Install anyway. * [SMS commands](#SMSCommands-troubleshooting) -### Frequent bluetooth connection problems +### Frequent Bluetooth connection problems -This can happen with various pumps. Apart from excluding AAPS from any battery optimization, you can also exclude the system bluetooth app from battery optimization. This can help in some cases. Depending on the phone you use, you will find the bluetooth app differently. +#### Android 15 + +```{warning} +Developers are working on this issue impacting **AAPS** on some Samsung and Pixel phones. +``` + +After upgrading Android or moving to a recent phone, **AAPS** frequently loses Bluetooth connection to the pump. The problem disappears temporarily when restarting the phone. If the phone runs Android 15, you can try to enable the following: + +1) **Open preferences** by clicking the three-dot menu on the top right side of the home screen. + + +![Open preferences](../images/Pref2020_Open2.png) + +2. Scroll down and open the **Confirmation beeps** / **Advanced** submenu. Enable **Bond BT device on Android 15+**. + + ![BondBT](../images/troubleshooting/BondBT.png) + +3. If the pump asks for a pairing request, accept it. + +4. Restart your phone. + +#### Battery optimization + +This can happen with various pumps. Apart from excluding AAPS from any battery optimization, you can also exclude the system Bluetooth app from battery optimization. This can help in some cases. Depending on the phone you use, you will find the Bluetooth app differently. Here are examples how to find them on specific android phones. -#### Pixel phones (stock android) +##### Pixel phones (stock Android) * Go to the android settings, select "Apps". @@ -67,7 +90,7 @@ Here are examples how to find them on specific android phones. ![BT Battery optimization](../images/troubleshooting/pixel/04_btunrestricted.png) -#### Samsung phones +##### Samsung phones * Go to the android settings, select "Apps" diff --git a/docs/CROWDIN/nl/images/troubleshooting/BondBT.png b/docs/CROWDIN/nl/images/troubleshooting/BondBT.png new file mode 100644 index 000000000000..96b2fb272d90 Binary files /dev/null and b/docs/CROWDIN/nl/images/troubleshooting/BondBT.png differ diff --git a/docs/CROWDIN/nl/images/troubleshooting/samsung/01_BondBT_20250526.png b/docs/CROWDIN/nl/images/troubleshooting/samsung/01_BondBT_20250526.png new file mode 100644 index 000000000000..74c3525959ed Binary files /dev/null and b/docs/CROWDIN/nl/images/troubleshooting/samsung/01_BondBT_20250526.png differ diff --git a/docs/CROWDIN/nl/images/troubleshooting/samsung/02_BondBT_20250526.png b/docs/CROWDIN/nl/images/troubleshooting/samsung/02_BondBT_20250526.png new file mode 100644 index 000000000000..444013b29146 Binary files /dev/null and b/docs/CROWDIN/nl/images/troubleshooting/samsung/02_BondBT_20250526.png differ diff --git a/docs/CROWDIN/nl/images/troubleshooting/samsung/03_BondBT_20250526.png b/docs/CROWDIN/nl/images/troubleshooting/samsung/03_BondBT_20250526.png new file mode 100644 index 000000000000..9caa7a484581 Binary files /dev/null and b/docs/CROWDIN/nl/images/troubleshooting/samsung/03_BondBT_20250526.png differ diff --git a/docs/CROWDIN/nl/images/troubleshooting/samsung/04_BondBT_20250526.png b/docs/CROWDIN/nl/images/troubleshooting/samsung/04_BondBT_20250526.png new file mode 100644 index 000000000000..b25c1469f58e Binary files /dev/null and b/docs/CROWDIN/nl/images/troubleshooting/samsung/04_BondBT_20250526.png differ diff --git a/docs/CROWDIN/pb/CompatiblePumps/OmnipodDASH.md b/docs/CROWDIN/pb/CompatiblePumps/OmnipodDASH.md index 99858bc2c15a..e214813cf186 100644 --- a/docs/CROWDIN/pb/CompatiblePumps/OmnipodDASH.md +++ b/docs/CROWDIN/pb/CompatiblePumps/OmnipodDASH.md @@ -18,7 +18,13 @@ These are the specifications of the **Omnipod DASH** ('DASH') and what different * On pod activation, **AAPS** will find and connect to a new DASH pod. * Expected range: 5-10 meters (YMMV). -WARNING: There are currently reported Bluetooth connection issues with the following combination of **AAPS** / DASH / Android 15. **AAPS** should not be used in combination with Android 15 and DASH unless the user has checked the following [**List**](https://docs.google.com/spreadsheets/u/1/d/e/2PACX-1vScCNaIguEZVTVFAgpv1kXHdsHl3fs6xT6RB2Z1CeVJ561AvvqGwxMhlmSHk4J056gMCAQE02sAWJvT/pubhtml?gid=683363241&single=true) and verified that their phone is not a known reported issue. **AAPS** is currently working to resolve this issue. +```{admonition} Android 15 +:class: warning + +There are currently reported Bluetooth connection issues with the following combination of **AAPS**: DASH + Android 15. +Please refrain from upgrading your phone to Android 15 unless you have checked the following [**list**](https://docs.google.com/spreadsheets/u/1/d/e/2PACX-1vScCNaIguEZVTVFAgpv1kXHdsHl3fs6xT6RB2Z1CeVJ561AvvqGwxMhlmSHk4J056gMCAQE02sAWJvT/pubhtml?gid=683363241&single=true) and verified that your phone is not a known reported issue. +If you experience frequent disconnection; try to enable Bond BT as described in: [**Bluetooth Issues**](../GettingHelp/GeneralTroubleshooting.md). +``` ## Hardware/Software Requirements diff --git a/docs/CROWDIN/pb/GettingHelp/GeneralTroubleshooting.md b/docs/CROWDIN/pb/GettingHelp/GeneralTroubleshooting.md index 53f458bdece5..53a847b4f4b2 100644 --- a/docs/CROWDIN/pb/GettingHelp/GeneralTroubleshooting.md +++ b/docs/CROWDIN/pb/GettingHelp/GeneralTroubleshooting.md @@ -37,14 +37,37 @@ Ignore it: More details, Install anyway. * [SMS commands](#SMSCommands-troubleshooting) -### Frequent bluetooth connection problems +### Frequent Bluetooth connection problems -This can happen with various pumps. Apart from excluding AAPS from any battery optimization, you can also exclude the system bluetooth app from battery optimization. This can help in some cases. Depending on the phone you use, you will find the bluetooth app differently. +#### Android 15 + +```{warning} +Developers are working on this issue impacting **AAPS** on some Samsung and Pixel phones. +``` + +After upgrading Android or moving to a recent phone, **AAPS** frequently loses Bluetooth connection to the pump. The problem disappears temporarily when restarting the phone. If the phone runs Android 15, you can try to enable the following: + +1) **Open preferences** by clicking the three-dot menu on the top right side of the home screen. + + +![Open preferences](../images/Pref2020_Open2.png) + +2. Scroll down and open the **Confirmation beeps** / **Advanced** submenu. Enable **Bond BT device on Android 15+**. + + ![BondBT](../images/troubleshooting/BondBT.png) + +3. If the pump asks for a pairing request, accept it. + +4. Restart your phone. + +#### Battery optimization + +This can happen with various pumps. Apart from excluding AAPS from any battery optimization, you can also exclude the system Bluetooth app from battery optimization. This can help in some cases. Depending on the phone you use, you will find the Bluetooth app differently. Here are examples how to find them on specific android phones. -#### Pixel phones (stock android) +##### Pixel phones (stock Android) * Go to the android settings, select "Apps". @@ -67,7 +90,7 @@ Here are examples how to find them on specific android phones. ![BT Battery optimization](../images/troubleshooting/pixel/04_btunrestricted.png) -#### Samsung phones +##### Samsung phones * Go to the android settings, select "Apps" diff --git a/docs/CROWDIN/pb/images/troubleshooting/BondBT.png b/docs/CROWDIN/pb/images/troubleshooting/BondBT.png new file mode 100644 index 000000000000..96b2fb272d90 Binary files /dev/null and b/docs/CROWDIN/pb/images/troubleshooting/BondBT.png differ diff --git a/docs/CROWDIN/pb/images/troubleshooting/samsung/01_BondBT_20250526.png b/docs/CROWDIN/pb/images/troubleshooting/samsung/01_BondBT_20250526.png new file mode 100644 index 000000000000..74c3525959ed Binary files /dev/null and b/docs/CROWDIN/pb/images/troubleshooting/samsung/01_BondBT_20250526.png differ diff --git a/docs/CROWDIN/pb/images/troubleshooting/samsung/02_BondBT_20250526.png b/docs/CROWDIN/pb/images/troubleshooting/samsung/02_BondBT_20250526.png new file mode 100644 index 000000000000..444013b29146 Binary files /dev/null and b/docs/CROWDIN/pb/images/troubleshooting/samsung/02_BondBT_20250526.png differ diff --git a/docs/CROWDIN/pb/images/troubleshooting/samsung/03_BondBT_20250526.png b/docs/CROWDIN/pb/images/troubleshooting/samsung/03_BondBT_20250526.png new file mode 100644 index 000000000000..9caa7a484581 Binary files /dev/null and b/docs/CROWDIN/pb/images/troubleshooting/samsung/03_BondBT_20250526.png differ diff --git a/docs/CROWDIN/pb/images/troubleshooting/samsung/04_BondBT_20250526.png b/docs/CROWDIN/pb/images/troubleshooting/samsung/04_BondBT_20250526.png new file mode 100644 index 000000000000..b25c1469f58e Binary files /dev/null and b/docs/CROWDIN/pb/images/troubleshooting/samsung/04_BondBT_20250526.png differ diff --git a/docs/CROWDIN/pl/CompatiblePumps/OmnipodDASH.md b/docs/CROWDIN/pl/CompatiblePumps/OmnipodDASH.md index 99858bc2c15a..e214813cf186 100644 --- a/docs/CROWDIN/pl/CompatiblePumps/OmnipodDASH.md +++ b/docs/CROWDIN/pl/CompatiblePumps/OmnipodDASH.md @@ -18,7 +18,13 @@ These are the specifications of the **Omnipod DASH** ('DASH') and what different * On pod activation, **AAPS** will find and connect to a new DASH pod. * Expected range: 5-10 meters (YMMV). -WARNING: There are currently reported Bluetooth connection issues with the following combination of **AAPS** / DASH / Android 15. **AAPS** should not be used in combination with Android 15 and DASH unless the user has checked the following [**List**](https://docs.google.com/spreadsheets/u/1/d/e/2PACX-1vScCNaIguEZVTVFAgpv1kXHdsHl3fs6xT6RB2Z1CeVJ561AvvqGwxMhlmSHk4J056gMCAQE02sAWJvT/pubhtml?gid=683363241&single=true) and verified that their phone is not a known reported issue. **AAPS** is currently working to resolve this issue. +```{admonition} Android 15 +:class: warning + +There are currently reported Bluetooth connection issues with the following combination of **AAPS**: DASH + Android 15. +Please refrain from upgrading your phone to Android 15 unless you have checked the following [**list**](https://docs.google.com/spreadsheets/u/1/d/e/2PACX-1vScCNaIguEZVTVFAgpv1kXHdsHl3fs6xT6RB2Z1CeVJ561AvvqGwxMhlmSHk4J056gMCAQE02sAWJvT/pubhtml?gid=683363241&single=true) and verified that your phone is not a known reported issue. +If you experience frequent disconnection; try to enable Bond BT as described in: [**Bluetooth Issues**](../GettingHelp/GeneralTroubleshooting.md). +``` ## Hardware/Software Requirements diff --git a/docs/CROWDIN/pl/GettingHelp/GeneralTroubleshooting.md b/docs/CROWDIN/pl/GettingHelp/GeneralTroubleshooting.md index b621d12d2808..b6e4672ba37d 100644 --- a/docs/CROWDIN/pl/GettingHelp/GeneralTroubleshooting.md +++ b/docs/CROWDIN/pl/GettingHelp/GeneralTroubleshooting.md @@ -37,14 +37,37 @@ Ignore it: More details, Install anyway. * [SMS commands](#SMSCommands-troubleshooting) -### Frequent bluetooth connection problems +### Frequent Bluetooth connection problems -This can happen with various pumps. Apart from excluding AAPS from any battery optimization, you can also exclude the system bluetooth app from battery optimization. This can help in some cases. Depending on the phone you use, you will find the bluetooth app differently. +#### Android 15 + +```{warning} +Developers are working on this issue impacting **AAPS** on some Samsung and Pixel phones. +``` + +After upgrading Android or moving to a recent phone, **AAPS** frequently loses Bluetooth connection to the pump. The problem disappears temporarily when restarting the phone. If the phone runs Android 15, you can try to enable the following: + +1) **Open preferences** by clicking the three-dot menu on the top right side of the home screen. + + +![Open preferences](../images/Pref2020_Open2.png) + +2. Scroll down and open the **Confirmation beeps** / **Advanced** submenu. Enable **Bond BT device on Android 15+**. + + ![BondBT](../images/troubleshooting/BondBT.png) + +3. If the pump asks for a pairing request, accept it. + +4. Restart your phone. + +#### Battery optimization + +This can happen with various pumps. Apart from excluding AAPS from any battery optimization, you can also exclude the system Bluetooth app from battery optimization. This can help in some cases. Depending on the phone you use, you will find the Bluetooth app differently. Here are examples how to find them on specific android phones. -#### Pixel phones (stock android) +##### Pixel phones (stock Android) * Go to the android settings, select "Apps". @@ -67,7 +90,7 @@ Here are examples how to find them on specific android phones. ![BT Battery optimization](../images/troubleshooting/pixel/04_btunrestricted.png) -#### Samsung phones +##### Samsung phones * Go to the android settings, select "Apps" diff --git a/docs/CROWDIN/pl/images/troubleshooting/BondBT.png b/docs/CROWDIN/pl/images/troubleshooting/BondBT.png new file mode 100644 index 000000000000..96b2fb272d90 Binary files /dev/null and b/docs/CROWDIN/pl/images/troubleshooting/BondBT.png differ diff --git a/docs/CROWDIN/pl/images/troubleshooting/samsung/01_BondBT_20250526.png b/docs/CROWDIN/pl/images/troubleshooting/samsung/01_BondBT_20250526.png new file mode 100644 index 000000000000..74c3525959ed Binary files /dev/null and b/docs/CROWDIN/pl/images/troubleshooting/samsung/01_BondBT_20250526.png differ diff --git a/docs/CROWDIN/pl/images/troubleshooting/samsung/02_BondBT_20250526.png b/docs/CROWDIN/pl/images/troubleshooting/samsung/02_BondBT_20250526.png new file mode 100644 index 000000000000..444013b29146 Binary files /dev/null and b/docs/CROWDIN/pl/images/troubleshooting/samsung/02_BondBT_20250526.png differ diff --git a/docs/CROWDIN/pl/images/troubleshooting/samsung/03_BondBT_20250526.png b/docs/CROWDIN/pl/images/troubleshooting/samsung/03_BondBT_20250526.png new file mode 100644 index 000000000000..9caa7a484581 Binary files /dev/null and b/docs/CROWDIN/pl/images/troubleshooting/samsung/03_BondBT_20250526.png differ diff --git a/docs/CROWDIN/pl/images/troubleshooting/samsung/04_BondBT_20250526.png b/docs/CROWDIN/pl/images/troubleshooting/samsung/04_BondBT_20250526.png new file mode 100644 index 000000000000..b25c1469f58e Binary files /dev/null and b/docs/CROWDIN/pl/images/troubleshooting/samsung/04_BondBT_20250526.png differ diff --git a/docs/CROWDIN/pt/CompatiblePumps/OmnipodDASH.md b/docs/CROWDIN/pt/CompatiblePumps/OmnipodDASH.md index 99858bc2c15a..e214813cf186 100644 --- a/docs/CROWDIN/pt/CompatiblePumps/OmnipodDASH.md +++ b/docs/CROWDIN/pt/CompatiblePumps/OmnipodDASH.md @@ -18,7 +18,13 @@ These are the specifications of the **Omnipod DASH** ('DASH') and what different * On pod activation, **AAPS** will find and connect to a new DASH pod. * Expected range: 5-10 meters (YMMV). -WARNING: There are currently reported Bluetooth connection issues with the following combination of **AAPS** / DASH / Android 15. **AAPS** should not be used in combination with Android 15 and DASH unless the user has checked the following [**List**](https://docs.google.com/spreadsheets/u/1/d/e/2PACX-1vScCNaIguEZVTVFAgpv1kXHdsHl3fs6xT6RB2Z1CeVJ561AvvqGwxMhlmSHk4J056gMCAQE02sAWJvT/pubhtml?gid=683363241&single=true) and verified that their phone is not a known reported issue. **AAPS** is currently working to resolve this issue. +```{admonition} Android 15 +:class: warning + +There are currently reported Bluetooth connection issues with the following combination of **AAPS**: DASH + Android 15. +Please refrain from upgrading your phone to Android 15 unless you have checked the following [**list**](https://docs.google.com/spreadsheets/u/1/d/e/2PACX-1vScCNaIguEZVTVFAgpv1kXHdsHl3fs6xT6RB2Z1CeVJ561AvvqGwxMhlmSHk4J056gMCAQE02sAWJvT/pubhtml?gid=683363241&single=true) and verified that your phone is not a known reported issue. +If you experience frequent disconnection; try to enable Bond BT as described in: [**Bluetooth Issues**](../GettingHelp/GeneralTroubleshooting.md). +``` ## Hardware/Software Requirements diff --git a/docs/CROWDIN/pt/GettingHelp/GeneralTroubleshooting.md b/docs/CROWDIN/pt/GettingHelp/GeneralTroubleshooting.md index 3d206e4c4ba6..9e8ae5a1621b 100644 --- a/docs/CROWDIN/pt/GettingHelp/GeneralTroubleshooting.md +++ b/docs/CROWDIN/pt/GettingHelp/GeneralTroubleshooting.md @@ -37,14 +37,37 @@ Ignore it: More details, Install anyway. * [SMS commands](#SMSCommands-troubleshooting) -### Frequent bluetooth connection problems +### Frequent Bluetooth connection problems -This can happen with various pumps. Apart from excluding AAPS from any battery optimization, you can also exclude the system bluetooth app from battery optimization. This can help in some cases. Depending on the phone you use, you will find the bluetooth app differently. +#### Android 15 + +```{warning} +Developers are working on this issue impacting **AAPS** on some Samsung and Pixel phones. +``` + +After upgrading Android or moving to a recent phone, **AAPS** frequently loses Bluetooth connection to the pump. The problem disappears temporarily when restarting the phone. If the phone runs Android 15, you can try to enable the following: + +1) **Open preferences** by clicking the three-dot menu on the top right side of the home screen. + + +![Open preferences](../images/Pref2020_Open2.png) + +2. Scroll down and open the **Confirmation beeps** / **Advanced** submenu. Enable **Bond BT device on Android 15+**. + + ![BondBT](../images/troubleshooting/BondBT.png) + +3. If the pump asks for a pairing request, accept it. + +4. Restart your phone. + +#### Battery optimization + +This can happen with various pumps. Apart from excluding AAPS from any battery optimization, you can also exclude the system Bluetooth app from battery optimization. This can help in some cases. Depending on the phone you use, you will find the Bluetooth app differently. Here are examples how to find them on specific android phones. -#### Pixel phones (stock android) +##### Pixel phones (stock Android) * Go to the android settings, select "Apps". @@ -67,7 +90,7 @@ Here are examples how to find them on specific android phones. ![BT Battery optimization](../images/troubleshooting/pixel/04_btunrestricted.png) -#### Samsung phones +##### Samsung phones * Go to the android settings, select "Apps" diff --git a/docs/CROWDIN/pt/images/troubleshooting/BondBT.png b/docs/CROWDIN/pt/images/troubleshooting/BondBT.png new file mode 100644 index 000000000000..96b2fb272d90 Binary files /dev/null and b/docs/CROWDIN/pt/images/troubleshooting/BondBT.png differ diff --git a/docs/CROWDIN/pt/images/troubleshooting/samsung/01_BondBT_20250526.png b/docs/CROWDIN/pt/images/troubleshooting/samsung/01_BondBT_20250526.png new file mode 100644 index 000000000000..74c3525959ed Binary files /dev/null and b/docs/CROWDIN/pt/images/troubleshooting/samsung/01_BondBT_20250526.png differ diff --git a/docs/CROWDIN/pt/images/troubleshooting/samsung/02_BondBT_20250526.png b/docs/CROWDIN/pt/images/troubleshooting/samsung/02_BondBT_20250526.png new file mode 100644 index 000000000000..444013b29146 Binary files /dev/null and b/docs/CROWDIN/pt/images/troubleshooting/samsung/02_BondBT_20250526.png differ diff --git a/docs/CROWDIN/pt/images/troubleshooting/samsung/03_BondBT_20250526.png b/docs/CROWDIN/pt/images/troubleshooting/samsung/03_BondBT_20250526.png new file mode 100644 index 000000000000..9caa7a484581 Binary files /dev/null and b/docs/CROWDIN/pt/images/troubleshooting/samsung/03_BondBT_20250526.png differ diff --git a/docs/CROWDIN/pt/images/troubleshooting/samsung/04_BondBT_20250526.png b/docs/CROWDIN/pt/images/troubleshooting/samsung/04_BondBT_20250526.png new file mode 100644 index 000000000000..b25c1469f58e Binary files /dev/null and b/docs/CROWDIN/pt/images/troubleshooting/samsung/04_BondBT_20250526.png differ diff --git a/docs/CROWDIN/ro/CompatiblePumps/OmnipodDASH.md b/docs/CROWDIN/ro/CompatiblePumps/OmnipodDASH.md index 6f2323cfad64..cb3d2479d69e 100644 --- a/docs/CROWDIN/ro/CompatiblePumps/OmnipodDASH.md +++ b/docs/CROWDIN/ro/CompatiblePumps/OmnipodDASH.md @@ -18,7 +18,13 @@ These are the specifications of the **Omnipod DASH** ('DASH') and what different * On pod activation, **AAPS** will find and connect to a new DASH pod. * Expected range: 5-10 meters (YMMV). -WARNING: There are currently reported Bluetooth connection issues with the following combination of **AAPS** / DASH / Android 15. **AAPS** should not be used in combination with Android 15 and DASH unless the user has checked the following [**List**](https://docs.google.com/spreadsheets/u/1/d/e/2PACX-1vScCNaIguEZVTVFAgpv1kXHdsHl3fs6xT6RB2Z1CeVJ561AvvqGwxMhlmSHk4J056gMCAQE02sAWJvT/pubhtml?gid=683363241&single=true) and verified that their phone is not a known reported issue. **AAPS** is currently working to resolve this issue. +```{admonition} Android 15 +:class: warning + +There are currently reported Bluetooth connection issues with the following combination of **AAPS**: DASH + Android 15. +Please refrain from upgrading your phone to Android 15 unless you have checked the following [**list**](https://docs.google.com/spreadsheets/u/1/d/e/2PACX-1vScCNaIguEZVTVFAgpv1kXHdsHl3fs6xT6RB2Z1CeVJ561AvvqGwxMhlmSHk4J056gMCAQE02sAWJvT/pubhtml?gid=683363241&single=true) and verified that your phone is not a known reported issue. +If you experience frequent disconnection; try to enable Bond BT as described in: [**Bluetooth Issues**](../GettingHelp/GeneralTroubleshooting.md). +``` ## Hardware/Software Requirements diff --git a/docs/CROWDIN/ro/GettingHelp/GeneralTroubleshooting.md b/docs/CROWDIN/ro/GettingHelp/GeneralTroubleshooting.md index ad8d846b0ff1..a9876ed0640e 100644 --- a/docs/CROWDIN/ro/GettingHelp/GeneralTroubleshooting.md +++ b/docs/CROWDIN/ro/GettingHelp/GeneralTroubleshooting.md @@ -37,14 +37,37 @@ Ignore it: More details, Install anyway. * [SMS commands](#SMSCommands-troubleshooting) -### Frequent bluetooth connection problems +### Frequent Bluetooth connection problems -This can happen with various pumps. Apart from excluding AAPS from any battery optimization, you can also exclude the system bluetooth app from battery optimization. This can help in some cases. Depending on the phone you use, you will find the bluetooth app differently. +#### Android 15 + +```{warning} +Developers are working on this issue impacting **AAPS** on some Samsung and Pixel phones. +``` + +After upgrading Android or moving to a recent phone, **AAPS** frequently loses Bluetooth connection to the pump. The problem disappears temporarily when restarting the phone. If the phone runs Android 15, you can try to enable the following: + +1) **Open preferences** by clicking the three-dot menu on the top right side of the home screen. + + +![Open preferences](../images/Pref2020_Open2.png) + +2. Scroll down and open the **Confirmation beeps** / **Advanced** submenu. Enable **Bond BT device on Android 15+**. + + ![BondBT](../images/troubleshooting/BondBT.png) + +3. If the pump asks for a pairing request, accept it. + +4. Restart your phone. + +#### Battery optimization + +This can happen with various pumps. Apart from excluding AAPS from any battery optimization, you can also exclude the system Bluetooth app from battery optimization. This can help in some cases. Depending on the phone you use, you will find the Bluetooth app differently. Here are examples how to find them on specific android phones. -#### Pixel phones (stock android) +##### Pixel phones (stock Android) * Go to the android settings, select "Apps". @@ -67,7 +90,7 @@ Here are examples how to find them on specific android phones. ![BT Battery optimization](../images/troubleshooting/pixel/04_btunrestricted.png) -#### Samsung phones +##### Samsung phones * Go to the android settings, select "Apps" diff --git a/docs/CROWDIN/ro/images/troubleshooting/BondBT.png b/docs/CROWDIN/ro/images/troubleshooting/BondBT.png new file mode 100644 index 000000000000..96b2fb272d90 Binary files /dev/null and b/docs/CROWDIN/ro/images/troubleshooting/BondBT.png differ diff --git a/docs/CROWDIN/ro/images/troubleshooting/samsung/01_BondBT_20250526.png b/docs/CROWDIN/ro/images/troubleshooting/samsung/01_BondBT_20250526.png new file mode 100644 index 000000000000..74c3525959ed Binary files /dev/null and b/docs/CROWDIN/ro/images/troubleshooting/samsung/01_BondBT_20250526.png differ diff --git a/docs/CROWDIN/ro/images/troubleshooting/samsung/02_BondBT_20250526.png b/docs/CROWDIN/ro/images/troubleshooting/samsung/02_BondBT_20250526.png new file mode 100644 index 000000000000..444013b29146 Binary files /dev/null and b/docs/CROWDIN/ro/images/troubleshooting/samsung/02_BondBT_20250526.png differ diff --git a/docs/CROWDIN/ro/images/troubleshooting/samsung/03_BondBT_20250526.png b/docs/CROWDIN/ro/images/troubleshooting/samsung/03_BondBT_20250526.png new file mode 100644 index 000000000000..9caa7a484581 Binary files /dev/null and b/docs/CROWDIN/ro/images/troubleshooting/samsung/03_BondBT_20250526.png differ diff --git a/docs/CROWDIN/ro/images/troubleshooting/samsung/04_BondBT_20250526.png b/docs/CROWDIN/ro/images/troubleshooting/samsung/04_BondBT_20250526.png new file mode 100644 index 000000000000..b25c1469f58e Binary files /dev/null and b/docs/CROWDIN/ro/images/troubleshooting/samsung/04_BondBT_20250526.png differ diff --git a/docs/CROWDIN/ru/CompatiblePumps/MedtrumNano.md b/docs/CROWDIN/ru/CompatiblePumps/MedtrumNano.md index b32ab92a2ab8..81ec90e287a5 100644 --- a/docs/CROWDIN/ru/CompatiblePumps/MedtrumNano.md +++ b/docs/CROWDIN/ru/CompatiblePumps/MedtrumNano.md @@ -39,9 +39,9 @@ orphan: true **Помпа не перестанет доставлять инсулин, если она не подключена к AAPS** Скорости Базала запрограммированы на помпе, как указано в текущем активном профиле. Когда работает AAPS, он будет отправлять временные команды на изменение базала, каждая из которх устанавливает базал максимум на 120 минут. Если по каким-то причинам помпа не получаетновых команд (например, из-за потери связи с помпой из-за расстояния до телефона), то после окончания временной базальной скорости. помпа вернется к стандартному базалу, предустановленному на помпе. -**30 -минутные профили базала НЕ поддерживаются в AAPS.** **Профиль AAPS не поддерживает 30-минутный базальный интервал** Если вы новичок в AAPS и устанавливаете базальный профиль впервые, имейте в виду, что получасовые базальные скорости не поддерживаются в AAPS, и следует настроить свой базальный профиль на часовые интервалы. Например, если ваша базальная скорость 1,1 ед., начинается в 09:30, длится 2 часа и заканчивается в 11:30, такие настройки работать не будут. Следует изменить базал в 1,1 единицы на диапазон времени с 9:00 до 11:00 или с 10:00 до 12:00. Несмотря на то, что аппаратное обеспечение помпы Medtrum поддерживает профили с 30-минутными отрезками базальной скорости, AAPS в настоящее время не в состоянии учесть их с помощью своих алгоритмов. +**30 -минутные профили базала НЕ поддерживаются в AAPS.** **Профиль AAPS не поддерживает 30-минутный базальный интервал** Если вы новичок в AAPS и устанавливаете базальный профиль впервые, имейте в виду, что получасовые базальные скорости не поддерживаются в AAPS, и следует настроить свой базальный профиль на часовые интервалы. Например, если ваша базальная скорость 1,1 ед., начинается в 09:30, длится 2 часа и заканчивается в 11:30, такие настройки работать не будут. 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. Несмотря на то, что аппаратное обеспечение помпы Medtrum поддерживает профили с 30-минутными отрезками базальной скорости, AAPS в настоящее время не в состоянии учесть их с помощью своих алгоритмов. -**Скорость базала 0 ед/ч НЕ поддерживается в AAPS** Помпа Medtrum не поддерживает нулевую базальную скорость; AAPS использует множество базальных профилей для автоматической терапии и поэтому не может функционировать с нулевой базовой скоростью. Нулевая временная скорость базала может быть достигнута с помощью функции "Отсоединить помпу" или путем комбинации команд Деактивировать цикл/Временная базальная скорость или Приостановить цикл/Временная базальная скорость. +**Скорость базала 0 ед/ч НЕ поддерживается в AAPS** Помпа Medtrum не поддерживает нулевую базальную скорость; AAPS использует множество базальных профилей для автоматической терапии и поэтому не может функционировать с нулевой базовой скоростью. A temporary zero basal rate can be achieved through the "Disconnect pump" function or through a combination of Disable Loop/Temp Basal Rate or Suspend Loop/Temp Basal Rate. ## Setup diff --git a/docs/CROWDIN/ru/CompatiblePumps/OmnipodDASH.md b/docs/CROWDIN/ru/CompatiblePumps/OmnipodDASH.md index 1dc457afa068..6661018b81fa 100644 --- a/docs/CROWDIN/ru/CompatiblePumps/OmnipodDASH.md +++ b/docs/CROWDIN/ru/CompatiblePumps/OmnipodDASH.md @@ -18,13 +18,19 @@ These are the specifications of the **Omnipod DASH** ('DASH') and what different * On pod activation, **AAPS** will find and connect to a new DASH pod. * Expected range: 5-10 meters (YMMV). -WARNING: There are currently reported Bluetooth connection issues with the following combination of **AAPS** / DASH / Android 15. **AAPS** should not be used in combination with Android 15 and DASH unless the user has checked the following [**List**](https://docs.google.com/spreadsheets/u/1/d/e/2PACX-1vScCNaIguEZVTVFAgpv1kXHdsHl3fs6xT6RB2Z1CeVJ561AvvqGwxMhlmSHk4J056gMCAQE02sAWJvT/pubhtml?gid=683363241&single=true) and verified that their phone is not a known reported issue. **AAPS** is currently working to resolve this issue. +```{admonition} Android 15 +:class: warning + +There are currently reported Bluetooth connection issues with the following combination of **AAPS**: DASH + Android 15. +Please refrain from upgrading your phone to Android 15 unless you have checked the following [**list**](https://docs.google.com/spreadsheets/u/1/d/e/2PACX-1vScCNaIguEZVTVFAgpv1kXHdsHl3fs6xT6RB2Z1CeVJ561AvvqGwxMhlmSHk4J056gMCAQE02sAWJvT/pubhtml?gid=683363241&single=true) and verified that your phone is not a known reported issue. +If you experience frequent disconnection; try to enable Bond BT as described in: [**Bluetooth Issues**](../GettingHelp/GeneralTroubleshooting.md). +``` ## Требования к аппаратному и программному обеспечению * DASH is identified by blue needle cap. -![Под Omnipod](../images/DASH_images/Omnipod_Pod.png) +![Omnipod Pod](../images/DASH_images/Omnipod_Pod.png) * **Compatible Android phone** with a BLE Bluetooth connection Be aware that **AAPS** Omnipod Dash driver connects with the DASH via Bluetooth every time it sends a command, and it disconnects right after. The Bluetooth connection can be disturbed by other bluetooth devices linked to the phone that is running **AAPS**, like earbuds etc... (which might cause, in rare occasions, connection issue or pod errors/loss on activation or afterwards in some phone models), or be disturbed by it. @@ -37,15 +43,15 @@ The instructions below explain how to activate a new pod session. Wait to close **SAFETY FIRST** - you should not try to connect **AAPS** to a pod for the first time without having access to extra pods, insulin, and phone devices are a must have. -**Your Omnipod Dash PDM will become redundant after the AAPS Dash driver activates your pod.** Previously a user may have operated a PDM to send commands to your DASH. A DASH will only faciiliate a single device to send commands to communicate with it. Устройство, которое успешно активирует под - единственное устройство, которому с этого момента будет разрешено с ним общаться. This means that once you activate a DASH with your Android phone through the **AAPS**, **you will no longer be able to use your PDM with that pod**. The **AAPS** Dash driver in your Android phone is now your acting PDM. +**Your Omnipod Dash PDM will become redundant after the AAPS Dash driver activates your pod.** Previously a user may have operated a PDM to send commands to your DASH. A DASH will only faciiliate a single device to send commands to communicate with it. The device that successfully activates the pod is the only device allowed to communicate with it from that point forward. This means that once you activate a DASH with your Android phone through the **AAPS**, **you will no longer be able to use your PDM with that pod**. The **AAPS** Dash driver in your Android phone is now your acting PDM. -*Это НЕ означает, что вы должны выбросить PDM, рекомендуется хранить его как запасной на случай чрезвычайных ситуаций, например, когда телефон потеряется или AAPS работает неправильно.* +*This does NOT mean you should throw away your PDM, it is recommended to keep it around as a backup and for emergencies, for instance when your phone gets lost or AAPS is not working correctly.* -**Ваш под не перестанет вводить инсулин, если он не подключён к AAPS**. Default basal rates are programmed on the pod on activation as defined in the current active **Profile**. As long as **AAPS** is operational it will send basal rate commands that run for a maximum of 120 minutes. Если по каким-то причинам под не получает никаких новых команд (например, вследствие потери связи с подом из-за расстояния до телефона), он автоматически вернется к базальной скорости по умолчанию. +**Your pod will not stop delivering insulin when it is not connected to AAPS**. Default basal rates are programmed on the pod on activation as defined in the current active **Profile**. As long as **AAPS** is operational it will send basal rate commands that run for a maximum of 120 minutes. 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. -**AAPS Profile does not support a 30 minute basal rate time frame** If you are new to **AAPS** and are setting up your basal rate **Profile** for the first time, please be aware that basal rates starting on a half-hour basis are not supported, and programmes on an hourly basis. For example, 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 im **AAPS**. Следует изменить базал в 1,1 единицы на диапазон времени с 9:00 до 11:00 или с 10:00 до 12:00. Even though the DASH hardware itself supports the 30 minute basal rate **Profile** increments, **AAPS** does support this feature. +**AAPS Profile does not support a 30 minute basal rate time frame** If you are new to **AAPS** and are setting up your basal rate **Profile** for the first time, please be aware that basal rates starting on a half-hour basis are not supported, and programmes on an hourly basis. For example, 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 im **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 support this feature. -**0U/h profile basal rates are NOT supported in AAPS** While the DASH does support a zero basal rate, since **AAPS** uses multiples of the user's **Profile** basal rate to determine automated treatment; it cannot function with a zero basal rate. Нулевая временная скорость базала может быть достигнута с помощью функции "Отсоединить помпу" или путем комбинации команд Деактивировать цикл/Временная базальная скорость или Приостановить цикл/Временная базальная скорость. The lowest basal rate allowed in **AAPS** is 0.05U/h. +**0U/h profile basal rates are NOT supported in AAPS** While the DASH does support a zero basal rate, since **AAPS** uses multiples of the user's **Profile** basal rate to determine automated treatment; it cannot function with a zero basal rate. A temporary zero basal rate can be achieved through the "Disconnect pump" function or through a combination of Disable Loop/Temp Basal Rate or Suspend Loop/Temp Basal Rate. The lowest basal rate allowed in **AAPS** is 0.05U/h. ## Selecting Dash in AAPS @@ -53,82 +59,82 @@ There are **two ways**: ### Вариант 1: При начальной установке -When installing **AAPS** for the first time, the **Setup Wizard** will guide new users through key features and installation requirements for **AAPS**. Когда дойдете до выбора помпы, выбирайте DASH. +When installing **AAPS** for the first time, the **Setup Wizard** will guide new users through key features and installation requirements for **AAPS**. Select “DASH” when you reach Pump selection. -![Включить Dash_1](../images/DASH_images/Enable_Dash/Enable_Dash_1.png) +![Enable_Dash_1](../images/DASH_images/Enable_Dash/Enable_Dash_1.png) When in doubt you can also select “Virtual Pump” and select “DASH” later, after setting up **AAPS** (see option 2). ### Вариант 2: Конфигуратор -После установки AAPS можно выбрать помпу **DASH**в конфигураторе: +On an existing installation you can select the **DASH** pump from the Config builder: -В левом верхнем углу из **выпадающего меню** выберите **Конфигуратор**\ ➜\ **Помпа**\ ➜\ **Dash**\, включив кнопку **Dash**. +On the top-left hand corner **hamburger menu** select **Config Builder (1)**\ ➜\ **Pump**\ ➜\ **Dash**\ ➜\ **Settings Gear (3)** by selecting the **radio button (2)** titled **Dash**. Selecting the **checkbox (4)** next to the **Settings Gear (3)** will allow the DASH menu to be displayed as a tab in the **AAPS** interface titled **DASH**. Checking this box will facilitate your access to the DASH commands when using **AAPS**. **NOTE:** A faster way to access the [**Dash settings**](#dash-settings) can be found below in the DASH settings section of this document. -![Включить Dash_3](../images/DASH_images/Enable_Dash/Enable_Dash_3.png) +![Enable_Dash_3](../images/DASH_images/Enable_Dash/Enable_Dash_3.png) ### Верификация выбора драйвера Omnipod To verify that you have selected the DASH in **AAPS**, if you have checked the box (4), **swipe to the left** from the **Overview** tab, where you will now see a **DASH** tab on **AAPS**. If this box is left unchecked, you’ll find the DASH tab in the hamburger menu upper left. -![Включить Dash_4](../images/DASH_images/Enable_Dash/Enable_Dash_4.jpg) +![Enable_Dash_4](../images/DASH_images/Enable_Dash/Enable_Dash_4.jpg) ## Настройка помпы Omnipod Dash -**Смахните главный экран влево** до появления вкладки **DASH**, на которой вы сможете управлять всеми функциями пода (некоторые из них неактивны или невидимы вне действующей сессии пода): +Please **swipe left** to the **DASH** tab where you will be able to manage all pod functions (some of these functions are not enabled or visible without an active pod session): -![Обновить Лого](../images/DASH_images/Refresh_LOGO.png) 'Refresh' pod connectivity and status, be able to silence pod alarms when the pod beeps +![Refresh_LOGO](../images/DASH_images/Refresh_LOGO.png) 'Refresh' pod connectivity and status, be able to silence pod alarms when the pod beeps -![УПРАВЛЕНИЕ ПОМПОЙ](../images/DASH_images/POD_MGMT_LOGO.png) 'Pod Management' (Activate, Deactivate, Play test beep, and Pod history) +![POD_MGMT_LOGO](../images/DASH_images/POD_MGMT_LOGO.png) 'Pod Management' (Activate, Deactivate, Play test beep, and Pod history) ### Активация Pod 1. Перейдите на вкладку **DASH**, нажмите кнопку **УПРАВЛЕНИЕ помпой (1)**, затем нажмите **Активировать Pod (2)**. -![Активировать Pod_1](../images/DASH_images/Activate_Pod/Activate_Pod_1.png) +![Activate_Pod_1](../images/DASH_images/Activate_Pod/Activate_Pod_1.png) -​ ![Активировать Pod_2](../images/DASH_images/Activate_Pod/Activate_Pod_2.png) +​ ![Activate_Pod_2](../images/DASH_images/Activate_Pod/Activate_Pod_2.png) 2. Появится экран **Заполнить Pod**. Заполните новый Pod по меньшей мере 80 единицами инсулина и дождитесь двух звуковых сигналов, подтверждающих, что Pod готов к первичному заполнению катетера. При подсчете общего количества инсулина на 3 дня, учитывайте, что первичное заполнение катетера Pod потребует около 3-10 единиц инсулина. -![Активировать Pod_3](../images/DASH_images/Activate_Pod/Activate_Pod_3.png) ![Активировать Pod_4](../images/DASH_images/Activate_Pod/Activate_Pod_4.jpg) +![Activate_Pod_3](../images/DASH_images/Activate_Pod/Activate_Pod_3.png) ![Activate_Pod_4](../images/DASH_images/Activate_Pod/Activate_Pod_4.jpg) Ensure that the new pod and the phone running **AAPS** are within close proximity of each other and click the **Next** button. -**NOTE**: if the error message below pops up _'Could not find an available pod for activation'_ (this can happen), do not panic. Нажмите на кнопку **Повторить**. В большинстве случаев активация будет продолжена успешно. +**NOTE**: if the error message below pops up _'Could not find an available pod for activation'_ (this can happen), do not panic. Click on the **Retry** button. In most situations activation will continue successfully. -![Активировать Pod_3](../images/DASH_images/Activate_pod_error.png) +![Activate_Pod_3](../images/DASH_images/Activate_pod_error.png) 3. На экране **Инициализация Pod**, Pod начнет первичное заполнение ( вы услышите щелчок с серией последующих тикающих звуков пока заполняется под). По завершении первичного заполнения на экране появится зеленая галочка и и станет активной кнопка **Далее**. Нажмите на кнопку **Далее** для завершения инициализации и появления экрана **Подключить Pod**. -![Активировать Pod_5](../images/DASH_images/Activate_Pod/Activate_Pod_5.jpg) ![Активировать Pod_6](../images/DASH_images/Activate_Pod/Activate_Pod_6.jpg) +![Activate_Pod_5](../images/DASH_images/Activate_Pod/Activate_Pod_5.jpg) ![Activate_Pod_6](../images/DASH_images/Activate_Pod/Activate_Pod_6.jpg) 4. Next, prepare the infusion site ready to receive the new pod. Wash hands to avoid any risk of infection. Clean the infusion site by either using soap and water or an alcohol wipe to disinfect and let the skin air dry completely before proceeding. Remove the pod's blue plastic needle cap. If you see something that sticks out of the pod or unusual, cancel the process and start with a new pod. If everything looks OK, proceed to take off the white paper backing from the adhesive and apply the pod to the selected site on your body. По завершении нажмите кнопку **Далее**. -![Активировать Pod_8](../images/DASH_images/Activate_Pod/Activate_Pod_8.jpg) +![Activate_Pod_8](../images/DASH_images/Activate_Pod/Activate_Pod_8.jpg) 5. Теперь появится диалоговое окно **Подключить Pod**. **нажимайте на кнопку OK ТОЛЬКО если вы готовы к установке катетера**. -![Активировать Pod_9](../images/DASH_images/Activate_Pod/Activate_Pod_9.jpg) +![Activate_Pod_9](../images/DASH_images/Activate_Pod/Activate_Pod_9.jpg) 6. After pressing **OK**, it may take some time before the DASH responds and inserts the cannula (1-2 minutes maximum). Be patient. *ПРИМЕЧАНИЕ: Перед установкой катетера рекомендуется ущипнуть кожу рядом с местом ввода катетера. Это уменьшает болевые ощущения при вводе иглы и снижает шансы на развитие окклюзий.* -![Активировать Pod_10](../images/DASH_images/Activate_Pod/Activate_Pod_10.png) ![Активировать Pod_11](../images/DASH_images/Activate_Pod/Activate_Pod_11.jpg) +![Activate_Pod_10](../images/DASH_images/Activate_Pod/Activate_Pod_10.png) ![Activate_Pod_11](../images/DASH_images/Activate_Pod/Activate_Pod_11.jpg) 7. При успешном вводе катетера появляется зеленая галочка и активируется кнопка **Далее**. Нажмите на кнопку **Далее**. -![Активировать Pod_12](../images/DASH_images/Activate_Pod/Activate_Pod_12.jpg) +![Activate_Pod_12](../images/DASH_images/Activate_Pod/Activate_Pod_12.jpg) 9. Появится экран **Pod активирован**. Нажмите на зеленую кнопку **Завершено**. Поздравляем! You have now started a new pod session. -![Активировать Pod_13](../images/DASH_images/Activate_Pod/Activate_Pod_13.jpg) +![Activate_Pod_13](../images/DASH_images/Activate_Pod/Activate_Pod_13.jpg) 10. На экране меню **управления Pod** кнопка **Активировать Pod (1)** теперь *выключена* и **Деактивировать Pod (2)** *включена*. Это потому, что под активен и вы не можете активировать дополнительный под без деактивации текущего. @@ -136,71 +142,71 @@ Ensure that the new pod and the phone running **AAPS** are within close proximit Подробнее об информации на дисплее см в разделе [**Вкладка DASH**](#dash-tab) документации. -![Активировать Pod_14](../images/DASH_images/Activate_Pod/Activate_Pod_14.png) +![Activate_Pod_14](../images/DASH_images/Activate_Pod/Activate_Pod_14.png) -​ ![Активировать Pod_15](../images/DASH_images/Activate_Pod/Activate_Pod_15.jpg) +​ ![Activate_Pod_15](../images/DASH_images/Activate_Pod/Activate_Pod_15.jpg) -Настройки лучше всего экспортировать ПОСЛЕ активации Pod. Export settings should be done at each pod change and once a month, copy the exported file to your internet drive. см. [**Экспорт настроек Doc**](../Maintenance/ExportImportSettings.md). +It is good practice to export settings AFTER activating the pod. Export settings should be done at each pod change and once a month, copy the exported file to your internet drive. see [**Export settings Doc**](../Maintenance/ExportImportSettings.md). -(OmnipodDASH-деактивация-пода)= +(OmnipodDASH-deactivate-pod)= ### Деактивация Pod -При нормальных условиях ожидаемое время жизни пода 3 дня (72 часа) и дополнительно 8 часов после предупреждения об истечении срока действия, в общей сложности 80 часов. +Under normal circumstances, the expected lifetime of a pod is three days (72 hours) and an additional 8 hours after the pod expiration warning for a total of 80 hours of pod usage. -Для деактивации пода (либо по истечении срока действия, либо из-за сбоя в работе): +To deactivate a pod (either from expiration or from a pod failure): 1. Зайдите на вкладку **DASH**, нажмите на кнопку **УПРАВЛЕНИЕ ПОМПОЙ(1)** на экране **Управление помпой Omnipod** и нажмите на кнопку **Деактивировать Pod(2)**. -![Деактивировать Pod_1](../images/DASH_images/Deactivate_Pod/Deactivate_Pod_1.jpg) +![Deactivate_Pod_1](../images/DASH_images/Deactivate_Pod/Deactivate_Pod_1.jpg) -​ ![Деактивировать Pod_2](../images/DASH_images/Deactivate_Pod/Deactivate_Pod_2.png) +​ ![Deactivate_Pod_2](../images/DASH_images/Deactivate_Pod/Deactivate_Pod_2.png) 2. На экране **Деактивировать Pod** нажмите кнопку **Далее** для начала процесса деактивации пода. Вы получите подтверждающий звуковой сигнал о том, что деактивация прошла успешно. -![Деактивировать Pod_3](../images/DASH_images/Deactivate_Pod/Deactivate_Pod_3.jpg) +![Deactivate_Pod_3](../images/DASH_images/Deactivate_Pod/Deactivate_Pod_3.jpg) - ![Отключить Pod_4](../images/DASH_images/Deactivate_Pod/Deactivate_Pod_4.jpg) + ![Deactivate_Pod_4](../images/DASH_images/Deactivate_Pod/Deactivate_Pod_4.jpg) 3. После успешной деактивации на экране появится зеленая галочка. Нажмите на кнопку **Далее**, чтобы отобразился экран Pod деактивирован. Теперь вы можете удалить свой pod так как активная сессия завершена. -![Деактивировать Pod_5](../images/DASH_images/Deactivate_Pod/Deactivate_Pod_5.jpg) +![Deactivate_Pod_5](../images/DASH_images/Deactivate_Pod/Deactivate_Pod_5.jpg) 4. Для возврата на экран **Управление помпой Omnipod** нажмите на зеленую кнопку. -![Деактивировать Pod_6](../images/DASH_images/Deactivate_Pod/Deactivate_Pod_6.jpg) +![Deactivate_Pod_6](../images/DASH_images/Deactivate_Pod/Deactivate_Pod_6.jpg) 5. Теперь вы оказались в меню **Управление помпой Omnipodt**; нажмите кнопку "Назад" на телефоне, чтобы вернуться на вкладку **DASH**. Убедитесь, что **Статус помпы:** отображает сообщение **Нет активных Pod**. -![Деактивировать Pod_2](../images/DASH_images/Deactivate_Pod/Deactivate_Pod_2.png) +![Deactivate_Pod_2](../images/DASH_images/Deactivate_Pod/Deactivate_Pod_2.png) - ![Деактивировать Pod_8](../images/DASH_images/Enable_Dash/Enable_Dash_4.jpg) + ![Deactivate_Pod_8](../images/DASH_images/Enable_Dash/Enable_Dash_4.jpg) ### Возобновление подачи инсулина -**Note**: During **Profile Switches**, DASH must suspend delivery before setting the new basal **Profile** as delivery can be suspended. См. раздел [**Приостановка подачи инсулина **](#delivery-suspended) для более подробной информации. +**Note**: During **Profile Switches**, DASH must suspend delivery before setting the new basal **Profile** as delivery can be suspended. Read [**Delivery suspended**](#delivery-suspended) in the troubleshooting section for more details. -Применяйте эту команду, чтобы приостановленный Pod возобновил подачу инсулина. After the command is successfully processed, insulin will resume normal delivery using the current basal rate based on the current time from the active basal **Profile**. The pod will again accept commands for bolus, **TBR**, and **SMB**. +Use this command to instruct the active, currently suspended pod to resume insulin delivery. After the command is successfully processed, insulin will resume normal delivery using the current basal rate based on the current time from the active basal **Profile**. The pod will again accept commands for bolus, **TBR**, and **SMB**. 1. Перейдите на вкладку **DASH** и убедитесь, что поле **статус Pod (1)** отображает **ПОМПА ОСТАНОВЛЕНА (ПРИОСТАНОВЛЕНО)**, затем нажмите кнопку **ВОЗОБНОВИТЬ ПОДАЧУ(2)** для передачи команды на Pod о возобновлении подачи инсулина. В поле **Статус Pod (3)** будет отображаться **ПОДАЧА ВОЗОБНОВЛЕНА**. -![Возобновить 1](../images/DASH_images/Resume/Resume_1.jpg) ![Возобновить_2](../images/DASH_images/Resume/Resume_2.jpg) +![Resume_1](../images/DASH_images/Resume/Resume_1.jpg) ![Resume_2](../images/DASH_images/Resume/Resume_2.jpg) 2. Когда команда Возобновить подачу прошла успешно, в диалоговом окне подтверждения будет показано сообщение **Подача инсулина возобновлена**. Нажмите **OK** для подтверждения и продолжения. -![Возобновить 3](../images/DASH_images/Resume/Resume_3.png) +![Resume_3](../images/DASH_images/Resume/Resume_3.png) 3. Вкладка **DASH** обновит поле **статус помпы (1)**и отобразит **ВЫПОЛНЯЕТСЯ,** кнопка **Возобновить подачу** больше не будет отображаться -![Возобновить_4](../images/DASH_images/Resume/Resume_4.jpg) +![Resume_4](../images/DASH_images/Resume/Resume_4.jpg) ### Отключение звуковых оповещений пода -*ПРИМЕЧАНИЕ - Кнопка ЗАГЛУШИТЬ СИГНАЛЫ ОПОВЕЩЕНИЯ доступна на вкладке **DASH** только когда срабатывают оповещения об истечении срока действия пода или о малом количестве инсулина в резервуаре. Если кнопка ЗАГЛУШИТЬ СИГНАЛЫ ОПОВЕЩЕНИЯ не видна, но вы слышите звуковые сигналы из Pod, попробуйте "Обновить статус Pod".* +*NOTE - The SILENCE ALERTS button is only available on the **DASH** tab when the pod expiration or low reservoir alert has been triggered. If the SILENCE ALERTS button is not visible and you hear beep sounds from the pod, try to 'Refresh pod status'.* -Дальнейшее описание поможет вам подтверждать получение и убирать звуковые сигналы, когда активное время Pod достигнет 72 часов (3х суток). Этот предел времени для оповещения определен в настройках сигналов **Времени до выключения** Dash. Максимальная продолжительность работы Pod составляет 80 часов (3е суток + 8 часов), однако производитель (Insulet) рекомендует не превышать 72 часа (3х суток). +The process below will show you how to acknowledge and dismiss pod beeps when the active pod time reaches the warning time limit before the pod expiration of 72 hours (3 days). This warning time limit is defined in the **Hours before shutdown** Dash alerts setting. The maximum life of a pod is 80 hours (3 days 8 hours), however Insulet recommends not exceeding the 72 hours (3 days) limit. 1. По достижении заданного времени предупреждения об ** отключении**, под начнет издавать сигналы о сроке отключения и приближении времени замены. Проверить срок замены можно на вкладке **DASH** в поле **Срок действия Пода истекает(1)**, где показывается точное время с момента активации и текст этот становится **красным** спустя 72 часа после активации. В поле **Активные оповещения помпы (2)** отображается сообщение о статусе **Срок работы Pod истекает**. Также появится кнопка **заглушить сигналы оповещения (3)**. @@ -217,38 +223,38 @@ Ensure that the new pod and the phone running **AAPS** are within close proximit 4. Перейдите на вкладку **DASH**. В поле **оповещения активного Pod ** больше не отображается предупреждение об истечении срока действия. -(OmnipodDASH--просмотр-истории) = +(OmnipodDASH-view-pod-history)= ### Просмотр истории Pod -This section explains how to review your active pod history and filter by different action categories. Инструмент истории пода позволяет просматривать действия текущего активного пода за трое суток (72 - 80 часов). +This section explains how to review your active pod history and filter by different action categories. The pod history tool allows you to view the actions and results committed to your currently active pod during its three days (72 - 80 hours) life. -Эта функция полезна для верификации болюсов, временной скорости базала TBR и команд на изменение базала, которые были отправлены на под. Остальные категории полезны для решения проблем, а также для определения хода событий, приводящих к сбою. +This feature is helpful in verifying boluses, TBRs and basal commands that were sent to the pod. The remaining categories are useful for troubleshooting issues and determining the order of events that occurred leading up to a failure. -*ПРИМЕЧАНИЕ:* **Только последняя команда может быть неопределенной**. Новые команды *не отправляются/0> пока **последняя команда 'не подтверждено' не станет 'подтверждено' или 'отклонено'**. 'Исправить' неопределенную команду можно нажав **обновить статус пода **.

+*NOTE:* **Only the last command can be uncertain**. New commands *will not be sent* until the **last 'uncertain' command becomes 'confirmed' or 'denied'**. The way to 'fix' uncertain commands is to **'refresh pod status'**. 1. Перейдите на вкладку **DASH**, нажмите на кнопку **УПРАВЛЕНИЕ ПОМПОЙ(1)** чтобы вызвать меню **Управление помпой Omnipod** и нажмите на кнопку **История Pod(2)** для вызова экрана истории. -![Под_история_1](../images/DASH_images/Deactivate_Pod/Deactivate_Pod_1.jpg) +![Pod_history_1](../images/DASH_images/Deactivate_Pod/Deactivate_Pod_1.jpg) - ![Под_история_2](../images/DASH_images/Pod_History/Pod_history_2.jpg) + ![Pod_history_2](../images/DASH_images/Pod_History/Pod_history_2.jpg) 2. На экране **под историей** по умолчанию отображается категория **Все (1)** и показывает **Дату и время (2)** всех подов **Действия (3)** и **Результаты (4)** в обратном хронологическом порядке,. Use your phone’s **back button 2 times** to return to the **DASH** tab in the main **AAPS** interface. -![Под-история_3](../images/DASH_images/Pod_History/Pod_history_3.jpg) ![Под_история_4](../images/DASH_images/Pod_History/Pod_history_4.jpg) +![Pod_history_3](../images/DASH_images/Pod_History/Pod_history_3.jpg) ![Pod_history_4](../images/DASH_images/Pod_History/Pod_history_4.jpg) -(OmnipodDASH-dash-вкладка)= +(OmnipodDASH-dash-tab)= ## Вкладка DASH -Ниже приведено объяснение расположения и значения иконок и информационных полей на вкладке **DASH** в главном интерфейсе AAPS. +Below is an explanation of the layout and meaning of the icons and status fields on the **DASH** tab in the main AAPS interface. -*ПРИМЕЧАНИЕ: Если в каком-то из информационных полей вкладки **DASH**появляется сообщение "не подтверждено" нажмите кнопку Обновить для получения точного статуса.* +*NOTE: If any message in the **DASH** tab status fields report (uncertain), then you will need to press the Refresh button to clear it and refresh the pod status.* ![DASH_Tab_1](../images/DASH_images/DASH_Tab/DASH_Tab_1.png) @@ -283,23 +289,23 @@ This section explains how to review your active pod history and filter by differ ### Кнопки -![Обновить](../images/DASH_images/Refresh_LOGO.png) : Отправляет команду refresh в активный Pod для обновления коммуникации. +![Refresh_Icon](../images/DASH_images/Refresh_LOGO.png) : Sends a refresh command to the active pod to update communication. * Используйте для обновления статуса pod и сброса полей статуса, содержащих текст (не подтверждено). * Дополнительную информацию см. в разделе Устранение неполадок ниже. -![Значок POD_MGMT_](../images/DASH_images/POD_MGMT_LOGO.png) : Перейдите в меню управления Pod. +![POD_MGMT_Icon](../images/DASH_images/POD_MGMT_LOGO.png) : Navigates to the Pod management menu. -![ack_alert_logo](../images/DASH_images/ack_alert_logo.png) : При нажатии отключает звуки и уведомления (истечение срока действия, мало инсулина в резервуаре..). +![ack_alert_logo](../images/DASH_images/ack_alert_logo.png) : When pressed this will disable the pod alerts beeps and notifications (expiry, low reservoir..). * Кнопка отображается только после появления предупреждения об истечении срока действия. * После успешного сброса, этот значок не будет отображаться. -![Значок RESUME_](../images/DASH_images/DASH_tab_icons/RESUME_Icon.png) : Возобновляет приостановленную подачу инсулина в активном Pod. +![RESUME_Icon](../images/DASH_images/DASH_tab_icons/RESUME_Icon.png) : Resumes the currently suspended insulin delivery in the active pod. ### Меню управления помпой -Ниже приведено значение пиктограмм в меню **Управление помпой **, доступном после нажатием кнопки **УПРАВЛЕНМЕ ПОМПОЙ (1)** на вкладке **DASH**. +Below is the meaning of the icons on the **Pod Management** menu accessed by pressing **POD MGMT (1)** button from the **DASH** tab. ![DASH_Tab_2](../images/DASH_images/Deactivate_Pod/Deactivate_Pod_1.jpg) @@ -314,25 +320,25 @@ This section explains how to review your active pod history and filter by differ ## Настройки Dash -Настройки помпы Dash доступны из левого верхнего **выпадающего меню** выберите **Конфигуратор(1)**\ ➜\ **Помпа**\ ➜\ **Dash**\ ➜\ **Шестеренка настроек (3)** включив ** радио кнопку (2) **с маркировкой **Dash**. Selecting the **checkbox (4)** next to the **Settings Gear (3)** will allow the Dash menu to be displayed as a tab in the **AAPS** interface titled **DASH**. +The Dash driver settings are configurable from the top-left hand corner **hamburger menu** under **Config Builder (1)**\ ➜\ **Pump**\ ➜\ **Dash**\ ➜\ **Settings Gear (3)** by selecting the **radio button (2)** titled **Dash**. Selecting the **checkbox (4)** next to the **Settings Gear (3)** will allow the Dash menu to be displayed as a tab in the **AAPS** interface titled **DASH**. -![Dash_settings 1](../images/DASH_images/Enable_Dash/Enable_Dash_3.png) +![Dash_settings_1](../images/DASH_images/Enable_Dash/Enable_Dash_3.png) -**ПРИМЕЧАНИЕ:** Более быстрый способ доступа к настройкам **Dash** - через меню **3 точки (1)** в правом верхнем углу вкладки **DASH** выбрать **Настройки Dash (2)** из выпадающего меню. +**NOTE:** A faster way to access the **Dash settings** is by accessing the **3 dot menu (1)** in the upper right hand corner of the **DASH** tab and selecting **Dash preferences (2)** from the dropdown menu. -![Dash_settings 3](../images/DASH_images/Dash_settings/Dash_settings_3.png) +![Dash_settings_3](../images/DASH_images/Dash_settings/Dash_settings_3.png) -Группы настроек перечислены ниже; вы можете включить или отключить их через переключатель большинства функций описанных ниже: +The settings groups are listed below; you can enable or disable via a toggle switch for most entries described below: -*ПРИМЕЧАНИЕ: Знак (\*) обозначает значение по умолчанию.* +*NOTE: An asterisk (\*) denotes the default setting is enabled.* ### Звуковые сигналы подтверждения ![Dash_settings_4](../images/DASH_images/Dash_settings/Dash_settings_4.jpg) -Обеспечивает звуковые сигналы подтверждения от Pod об успешной подаче болюса, изменении базала, SMB и TBR. +Provides confirmation beeps from the pod for bolus, basal, SMB, and TBR delivery and changes. * **Звуковой сигнал болюса включен** Включить или отключить подтверждающие сигналы при подаче болюса. * **Звуковой сигнал базала включен:** Включить или отключить звуки подтверждения, когда установлена новая базальная скорость, отменена или изменена действующая базальная скорость. @@ -341,11 +347,11 @@ This section explains how to review your active pod history and filter by differ ### Оповещения -![Настройки Dash 5](../images/DASH_images/Dash_settings/Dash_settings_5.jpg) +![Dash_settings_5](../images/DASH_images/Dash_settings/Dash_settings_5.jpg) Provides **AAPS** alerts for pod expiration, shutdown, low reservoir based on the defined threshold units. -*Примечание: уведомления AAPS выдаются ВСЕГДА для любого оповещения после связи с pod с момента срабатывания оповещения. Сброс уведомления НЕ удалит оповещение, ЕСЛИ НЕ включено автоматическое подтверждение получения оповещений. Чтобы ВРУЧНУЮ убрать оповещение следует открыть вкладку **DASH** и нажать кнопку **Заглущать СИГНАЛЫ ОПОВЕЩЕНИЯ**.* +*Note an AAPS notification will ALWAYS be issued for any alert after the initial communication with the pod since the alert was triggered. Dismissing the notification will NOT dismiss the alert UNLESS automatically acknowledge Pod alerts is enabled. To MANUALLY dismiss the alert you must visit the **DASH** tab and press the **Silence ALERTS button**.* * **Включено напоминание об истечении срока действия:** Включение или отключение напоминания о истечении срока действия струи для срабатывания по достижении определенного количества часов до завершения работы. * **Время до выключения**. @@ -354,11 +360,11 @@ Provides **AAPS** alerts for pod expiration, shutdown, low reservoir based on th ### Уведомления -![Настройки Dash 6](../images/DASH_images/Dash_settings/Dash_settings_6.jpg) +![Dash_settings_6](../images/DASH_images/Dash_settings/Dash_settings_6.jpg) The Notification section allows the user to so select their preferred notifications and audible phone alerts when it is uncertain if TBR, SMB, or bolus, and delivery suspended events were successful. -*ПРИМЕЧАНИЕ: Это только уведомления, звуковые оповещения об ошибках не производится.* +*NOTE: These are notifications only, no audible beep alerts are made.* * **Sound for uncertain TBR notifications enabled:** Enable or disable this setting to trigger an audible alert and visual notification when **AAPS** is uncertain if a TBR was successfully set. * **Sound for uncertain SMB notifications enabled:** Enable or disable this setting to trigger an audible alert and visual notification when **AAPS**is uncertain if an SMB was successfully delivered. @@ -377,14 +383,14 @@ This tab is well documented in the main**AAPS**documentation but there are a few ### Уровень -**Уровень инсулина** +**Insulin Level** -Insulin level displayed is the amount reported by DASH. Вместе с тем Pod сообщает только о фактическом уровне инсулина, когда он ниже 50 единиц. До этого будет отображаться "выше 50 единиц". Уровень, указанный помпой, в большинстве случаев не является точным: в резервуар будет оставаться несколько дополнительных единиц инсулина. The DASH overview tab will display as described the below: +Insulin level displayed is the amount reported by DASH. However, the pod only reports the actual insulin reservoir level when it is below 50 units. Until then “Above 50 units” will be displayed. The amount reported is not exact: when the pod reports ‘empty’ in most cases the reservoir will still have some additional units of insulin left. The DASH overview tab will display as described the below: * **Above 50 Units** - The pod reports more than 50 units currently in the reservoir. * **Ниже 50 ед.**- Количество инсулина, остающегося в резервуаре по данным, полученным от Pod. -Дополнительные замечания: +Additional note: * **SMS** - В SMS сообщается реальный остаток в ед. или 50+ед * **Nightscout** - при более чем 50 единиц в Nightscout выгружается значение 50 ед.(версия 14.07 и старше). Более новые версии покажут 50 + когда более 50 единиц. @@ -402,43 +408,43 @@ Insulin level displayed is the amount reported by DASH. Вместе с тем P - If **AAPS** fails to resume delivery on its own (this happens if the pod is unreachable, sound is muted, etc), the pod will start beeping 4 times every minute for 3 minutes, then repeated every 15 minutes if delivery is still suspended for more than 20 minutes. * Для неподтвержденных команд "Обновить статус помпы" их подтвердит/запретит. -**Примечание:** При получении звуковых сигналов от пода, не следует полагать, что подача будет продолжена без проверки телефона, она может остаться приостановленой, **поэтому следует это проверить!** +**Note:** When you hear beeps from the pod, do not assume that delivery will continue without checking the phone, delivery might stay suspended, **so you need to check !** ### Сбои в работе Pod -Поды иногда подводят из-за различных проблем, включая аппаратные неполадки в самих Pod. В Insulet с этим лучше не обращаться в, поскольку приложение AAPS пока не получила официального одобрения. Список ошибок [**можно найти здесь**](https://github.com/openaps/openomni/wiki/Fault-event-codes) для помощи в определении причины. +Pods fail occasionally due to a variety of issues, including hardware issues with the Pod itself. It is best practice not to call these into Insulet, since AAPS is not an approved use case. A list of fault codes can be [**found here**](https://github.com/openaps/openomni/wiki/Fault-event-codes) to help determine the cause. ### Предотвращение ошибки 49 при сбоях Pod -Эта неисправность связана с некорректным состоянием Pod во время команды или ошибки при подаче инсулина. В этот момент драйвер и Pod не согласны с фактическим состоянием. The Pod (out of a built-in safety measure) then reacts with an unrecoverable error code 49 (0x31) ending up with what is know as a “screamer”: the long irritating beep that can only be stopped by punching a hole at the appropriate location at the back of the Pod. Точное происхождение "ошибки 49" зачастую трудно отследить. В ситуациях, когда имеются подозрения в возникновении такой ошибки (например, при сбоях приложения, выполнении версии разработки или переустановке). +This failure is related to an incorrect pod state for a command or an error during an insulin delivery command. This is when the driver and Pod disagree on the actual state. The Pod (out of a built-in safety measure) then reacts with an unrecoverable error code 49 (0x31) ending up with what is know as a “screamer”: the long irritating beep that can only be stopped by punching a hole at the appropriate location at the back of the Pod. The exact origin of a “49 pod failure” often is hard to trace. In situations that are suspected for this failure to occur (for instance on application crashes, running a development version or re-installation). ### Оповещения о недоступности помпы -Когда связь с стружкой не может быть установлена в течение запланированного времени, дается оповещение «Помпа недоступна». Оповещения о недоступности помпы можно настроить перейдя в верхнее правое трехточечное меню, выбрав **Настройки**\ ➜\ **Локальные оповещения**\ ➜\ **Порог оповещения Помпа недоступна [min]**. Рекомендуемое величина задержки оповещания **120** минут. +When no communication can be established with the pod for a preconfigured time a “Pump unreachable” alert will be raised. Pump unreachable alerts can be configured by going to the top right-hand side three-dot menu, selecting **Preferences**\ ➜\ **Local Alerts**\ ➜\ **Pump unreachable threshold [min]**. Recommended value is alerting after **120** minutes. ### Настройки экспорта Exporting **AAPS** settings enables you to restore all your settings, and maybe more importantly, all your Objectives. You may need to restore settings to the “last known working situation” or after uninstalling/reinstalling **AAPS** or in case of phone loss, reinstalling on the new phone. -Примечание: Активная информация о поде включена в экспортируемые настройки. Если вы импортируете "старый" файл, ваш реальный под "недействителен". Других альтернатив нет. In some cases (like a _programmed_ phone change), you may need to use the exported file to restore **AAPS'** settings **while keeping the current active Pod**. В этом случае необходимо использовать только недавно экспортированный файл настроек, содержащий именно этот под. +Note: The active pod information is included in the exported settings. If you import an "old" exported file, your actual pod will "die". There is no other alternative. In some cases (like a _programmed_ phone change), you may need to use the exported file to restore **AAPS'** settings **while keeping the current active Pod**. In this case it is important to only use the recently exported settings file containing the pod currently active. -**Полезно сделать экспорт сразу же после активации пода**. This way you will always be able to restore the current active pod in case of a problem. Например, при перемещении на другой резервный телефон. +**It is good practice to do an export immediately after activating a pod**. This way you will always be able to restore the current active pod in case of a problem. For instance when moving to another backup phone. -Регулярно копируйте экспортированные настройки в безопасное место (как облачный диск), которые могут быть доступны по мере необходимости на любом телефоне (eнапример, в случае потери телефона или сбросе актуального телефона). +Regularly copy your exported settings to a safe place (as a cloud drive) that can be accessible by any phone when needed (e.g. in case of a phone loss or factory reset of the actual phone). ### Импорт настроек -**ВНИМАНИЕ** Обратите внимание, что при импорте настроек может быть импортирован устаревший статус пода. В результате существует риск потери активного Pod! (см. **Экспорт настроек**). Лучше пробовать этот вариант только когда другие опции не доступны. +**WARNING** Please note that importing settings will possibly import an outdated Pod status. As a result, there is a risk of losing the active Pod! (see **Exporting Settings**). It is better to only try it when no other options are available. -При импорте настроек с активным Pod, убедитесь, что экспорт был сделан с активныого pod. +When importing settings with an active Pod, make sure the export was done with the currently active pod. -**Импорт во время активного Pod:** (вы рискуете потерять Pod!) +**Importing while on an active Pod:** (you risk losing the Pod!) 1. Убедитесь, что вы импортируете настройки, которые были недавно экспортированы с текущим активным Pod. 2. Импортируйте настройки. 3. Проверьте все настройки. -**Импорт (нет активных сессий Pod)** +**Importing (no active Pod session)** 1. Должен работать импорт последнего экспорта (см. выше) 2. Импортируйте настройки. @@ -447,13 +453,13 @@ Exporting **AAPS** settings enables you to restore all your settings, and maybe ### Импорт настроек, которые содержат состояние Pod из неактивного Pod -При импорте параметров, содержащих данные Pod, которые больше не активны, AAPS попытается соединиться с ним, что не сработает. В этой ситуации невозможно активировать новый Pod. +When importing settings containing data for a Pod that is no longer active, AAPS will try to connect with it, which will obviously fail. You can not activate a new Pod in this situation. -To remove the old pod session “try” to de-activate the Pod. Деактивация не удастся. Выберите "Повторить". После второго или третьего повтора вы получите возможность удалить Pod. Once the old pod is removed you will be able to activate a new pod. +To remove the old pod session “try” to de-activate the Pod. The de-activation will fail. Select “Retry”. After the second or third retry you will get the option to remove the pod. Once the old pod is removed you will be able to activate a new pod. ### Переустановка AAPS -When uninstalling**AAPS** you will lose all your settings, objectives and the current Pod session. Чтобы восстановить их, убедитесь, что у вас есть недавний экспортированный файл настроек! +When uninstalling**AAPS** you will lose all your settings, objectives and the current Pod session. To restore them make sure you have a recent exported settings file available! When on an active Pod, make sure that you have an export for the current pod session or you will lose the currently active pod when importing older settings. @@ -467,7 +473,7 @@ When on an active Pod, make sure that you have an export for the current pod ses ### Обновление AAPS до более новой версии -В большинстве случаев нет необходимости удалять. Вы можете установить "на месте", начав установку новой версии. Это также возможно при активном Pod. +In most cases there is no need to uninstall. You can do an “in-place” install by starting the installation for the new version. This is also possible when on an active Pod session. 1. Экспортируйте настройки. 2. Install the new **AAPS** version. @@ -477,7 +483,7 @@ When on an active Pod, make sure that you have an export for the current pod ses ### Оповещения драйвера Omnipod -Обратите внимание, что драйвер Omnipod Dash содержит множество уоповещений на вкладке **Начало**, большинство из них являются информационными и могут быть отключены, в то время как некоторые предоставляют пользователю возможности устранения причин оповещения. Ниже приводится краткая информация об основных оповещениях: +Please note that the Omnipod Dash driver presents a variety of unique alerts on the **Overview tab**, most of them are informational and can be dismissed while some provide the user with an action to take to resolve the cause of the triggered alert. A summary of the main alerts that you may encounter is listed below: * Активный сеанс Pod не обнаружен. Это предупреждение можно временно отклонить, нажав **УБРАТЬ**, но оно будет продолжать срабатывать до тех пор, пока не активирован новый Pod. После активации предупреждение автоматически заглушается. * Pod suspended Informational alert that pod has been suspended. diff --git a/docs/CROWDIN/ru/CompatiblePumps/OmnipodEros.md b/docs/CROWDIN/ru/CompatiblePumps/OmnipodEros.md index 551bd3fba0c5..8508427abf95 100644 --- a/docs/CROWDIN/ru/CompatiblePumps/OmnipodEros.md +++ b/docs/CROWDIN/ru/CompatiblePumps/OmnipodEros.md @@ -43,7 +43,7 @@ orphan: true **БЕЗОПАСНОСТЬ на первом месте** Не пытайтесь выполнять этот процесс в среде, где нет возможности исправить ошибку (дополнительные поды, инсулин, устройства управления помпой обязательны). -**Ваш PDM Omnipod не будет работать после того, как драйвер Omnipod активирует ваш под**. Раньше вы использовали Omnipod PDM для отправки команд на Omnipod Eros. Под Omnipod Eros позволяет коммуникацию только с одним устройством. Устройство, которое успешно активирует под - единственное устройство, которому с этого момента будет разрешено с ним общаться. Это означает, что после активации пода с телефона через драйвер AAPS Eros, **вы больше не сможете пользоваться пультом PDM с этим подом**. Драйвер AAPS Omnipod с RileyLink теперь является вашим действующим PDM. *Это НЕ означает, что вы должны выкинуть PDM, рекомендуется хранить его в резерве и для чрезвычайных ситуаций, если ААПС работает неправильно.* +**Ваш PDM Omnipod не будет работать после того, как драйвер Omnipod активирует ваш под**. Раньше вы использовали Omnipod PDM для отправки команд на Omnipod Eros. Под Omnipod Eros позволяет коммуникацию только с одним устройством. The device that successfully activates the pod is the only device allowed to communicate with it from that point forward. Это означает, что после активации пода с телефона через драйвер AAPS Eros, **вы больше не сможете пользоваться пультом PDM с этим подом**. Драйвер AAPS Omnipod с RileyLink теперь является вашим действующим PDM. *Это НЕ означает, что вы должны выкинуть PDM, рекомендуется хранить его в резерве и для чрезвычайных ситуаций, если ААПС работает неправильно.* **Можно настроить несколько устройств RileyLink, но только один RileyLink будет обмениваться с подом** Драйвер AAPS Omnipod поддерживает возможность добавления нескольких RileyLink в конфигурацию RileyLink, однако, можно выбрать только один RileyLink, который будет использоваться для коммуникации. @@ -135,21 +135,21 @@ orphan: true 01. Перейдите на вкладку **Omnipod (POD)**, нажмите кнопку **УПРАВЛЕНИЕ помпой (1)**, затем нажмите **Активировать Pod (2)**. - > ![Активировать Pod_1](../images/omnipod/Activate_Pod_1.png) ![Активировать Pod_2](../images/omnipod/Activate_Pod_2.png) + > ![Activate_Pod_1](../images/omnipod/Activate_Pod_1.png) ![Activate_Pod_2](../images/omnipod/Activate_Pod_2.png) 02. Появится экран **Заполнить Pod**. Заполните новый Pod по меньшей мере 80 единицами инсулина и дождитесь двух звуковых сигналов, подтверждающих, что Pod готов к первичному заполнению катетера. При подсчете общего количества инсулина на 3 дня, учитывайте, что первичное заполнение катетера Pod потребует 12-15 единиц инсулина. - > ![Активировать Pod_3](../images/omnipod/Activate_Pod_3.png) + > ![Activate_Pod_3](../images/omnipod/Activate_Pod_3.png) > > Убедитесь, что новый Pod и телефон с запущенным AAPS находятся в непосредственной близости друг от друга и нажмите кнопку **Далее**. 03. На экране **Инициализация Pod**, Pod начнет первичное заполнение ( вы услышите щелчок с серией последующих тикающих звуков пока заполняется под). Если RileyLink при активации находится вне диапазона, вы получите сообщение об ошибке **Нет ответа от Pod**. Если это происходит, переместите RileyLink ближе (30 см или менее) но не поверх или совсем рядом с Pod и нажмите кнопку **Повторить**. - > ![Активировать Pod_4](../images/omnipod/Activate_Pod_4.png) ![Активировать Pod_5](../images/omnipod/Activate_Pod_5.png) + > ![Activate_Pod_4](../images/omnipod/Activate_Pod_4.png) ![Activate_Pod_5](../images/omnipod/Activate_Pod_5.png) 04. После успешного заполнения катетера появится зеленая галочка, и станет активной кнопка **Далее**. Нажмите на кнопку **Далее** для завершения инициализации и появления экрана **Подключить Pod**. - > ![Активировать Pod_6](../images/omnipod/Activate_Pod_6.png) + > ![Activate_Pod_6](../images/omnipod/Activate_Pod_6.png) 05. Затем подготавливаем инфузионный отсек нового пода. Снимите пластмассовый колпачок с иглы, белую бумажную защиту с клеевого слоя и прижмите к обычно выбранному месту на теле. По завершении нажмите кнопку **Далее**. @@ -157,7 +157,7 @@ orphan: true 06. Теперь появится диалоговое окно **Подключить Pod**. **нажимайте на кнопку OK ТОЛЬКО если вы готовы к установке катетера**. - > ![Активировать Pod_8](../images/omnipod/Activate_Pod_8.png) + > ![Activate_Pod_8](../images/omnipod/Activate_Pod_8.png) 07. После нажатия **OK**, понадобится некоторое время для реакции Pod и введения катетера (1-2 минуты максимум), так что наберитесь терпения. @@ -167,17 +167,17 @@ orphan: true > > *ПРИМЕЧАНИЕ: Перед установкой катетера рекомендуется ущипнуть кожу рядом с местом ввода катетера. Это уменьшает болевые ощущения при вводе иглы и снижает шансы на развитие окклюзий.* > - > ![Активировать Pod_9](../images/omnipod/Activate_Pod_9.png) + > ![Activate_Pod_9](../images/omnipod/Activate_Pod_9.png) > - > ![Активировать Pod_10](../images/omnipod/Activate_Pod_10.png) ![Активировать Pod_11](../images/omnipod/Activate_Pod_11.png) + > ![Activate_Pod_10](../images/omnipod/Activate_Pod_10.png) ![Activate_Pod_11](../images/omnipod/Activate_Pod_11.png) 08. При успешном вводе катетера появляется зеленая галочка и активируется кнопка **Далее**. Нажмите на кнопку **Далее**. - > ![Активировать Pod_12](../images/omnipod/Activate_Pod_12.png) + > ![Activate_Pod_12](../images/omnipod/Activate_Pod_12.png) 09. Появится экран **Pod активирован**. Нажмите на зеленую кнопку **Завершено**. Поздравляем! Вы начали новую активную сессию Pod. - > ![Активировать Pod_13](../images/omnipod/Activate_Pod_13.png) + > ![Activate_Pod_13](../images/omnipod/Activate_Pod_13.png) 10. На экране меню **управления Pod** кнопка **Активировать Pod (1)** теперь *выключена*, а **Деактивировать Pod (2)** *включена*. Это потому, что под активен и вы не можете активировать дополнительный под без деактивации текущего. @@ -185,29 +185,29 @@ orphan: true Более подробно о показываемой информации в разделе [](#omnipod-pod-tab)Вкладка Omnipod (POD) этого документа. - ![Активировать Pod_14](../images/omnipod/Activate_Pod_14.png) ![Активировать Pod_15](../images/omnipod/Activate_Pod_15.png) + ![Activate_Pod_14](../images/omnipod/Activate_Pod_14.png) ![Activate_Pod_15](../images/omnipod/Activate_Pod_15.png) ### Деактивация Pod При нормальных условиях ожидаемое время жизни пода 3 дня (72 часа) и дополнительно 8 часов после предупреждения об истечении срока действия, в общей сложности 80 часов. -Для деактивации пода (либо по истечении срока действия, либо из-за сбоя в работе): +To deactivate a pod (either from expiration or from a pod failure): 1. Зайдите на вкладку **Omnipod (POD)**, нажмите на кнопку **УПРАВЛЕНИЕ ПОМПОЙ(1)** на экране **Управление помпой Omnipod** нажмите кнопку **Деактивировать Pod(2)**. - > ![Деактивировать Pod_1](../images/omnipod/Deactivate_Pod_1.png) ![Деактивировать Pod_2](../images/omnipod/Deactivate_Pod_2.png) + > ![Deactivate_Pod_1](../images/omnipod/Deactivate_Pod_1.png) ![Deactivate_Pod_2](../images/omnipod/Deactivate_Pod_2.png) 2. На экране **Деактивировать Pod** сначала убедитесь, что RileyLink находится в непосредственной близости от Pod, но не на самом устройстве или совсем рядом с ними, затем нажмите на кнопку **Далее** для начала процесса деактивации Pod. - > ![Деактивировать Pod_3](../images/omnipod/Deactivate_Pod_3.png) + > ![Deactivate_Pod_3](../images/omnipod/Deactivate_Pod_3.png) 3. Появится экран **Деактивация Pod**, и мы получим подтверждение от Pod, что деактивация прошла успешно. - > ![Отключить Pod_4](../images/omnipod/Deactivate_Pod_4.png) + > ![Deactivate_Pod_4](../images/omnipod/Deactivate_Pod_4.png) > > **Если деактивация не удалась** и звуковое подтверждение не прозвучало, может появиться сообщение **Нет ответа от RileyLink** или **Нет ответа от Pod **. Нажмите на кнопку **Повторить (1)** для повторной попытки деактивации. Если деактивация по-прежнему не удается, пожалуйста, нажмите на кнопку **Завершить пользование Подом(2)** для утилизации Pod. Теперь вы можете удалить свой pod так как активная сессия завершена. Если Pod запрограмирован на громкие звуковые сигналы, возможно потребуется вручную заглушить их, (используя булавкут или скрепку), поскольку кнопка **Завершить пользование Pod (2)** не уберет их. > - > > ![Деактивировать Pod_5](../images/omnipod/Deactivate_Pod_5.png) ![Деактивировать Pod_6](../images/omnipod/Deactivate_Pod_6.png) + > > ![Deactivate_Pod_5](../images/omnipod/Deactivate_Pod_5.png) ![Deactivate_Pod_6](../images/omnipod/Deactivate_Pod_6.png) 4. После успешной деактивации на экране появится зеленая галочка. Нажмите на кнопку **Далее**, чтобы отобразился экран Pod деактивирован. Теперь вы можете удалить свой pod так как активная сессия завершена. @@ -215,7 +215,7 @@ orphan: true 5. Для возврата на экран **Управление помпой Omnipod** нажмите на зеленую кнопку. - > ![Деактивировать Pod_8](../images/omnipod/Deactivate_Pod_8.png) + > ![Deactivate_Pod_8](../images/omnipod/Deactivate_Pod_8.png) 6. Теперь вы оказались в меню **Управление помпой Omnipodt**; нажмите кнопку "Назад" на телефоне, чтобы вернуться на вкладку **Omnipod (POD)**. Убедитесь, что в поле **Статус RileyLink:** отображается **Подключено**, а поле **Статус помпы:** поле отображает сообщение**Нет активных Pod**. @@ -245,7 +245,7 @@ orphan: true #### Возобновление подачи инсулина -Применяйте эту команду, чтобы приостановленный Pod возобновил подачу инсулина. После успешной обработки команды, нормальная подача инсулина возобновится в соответствии с текущим активным профилем базала. Pod снова будет принимать команды на болюс, TBR и SMB. +Use this command to instruct the active, currently suspended pod to resume insulin delivery. После успешной обработки команды, нормальная подача инсулина возобновится в соответствии с текущим активным профилем базала. Pod снова будет принимать команды на болюс, TBR и SMB. 1. Перейдите на вкладку **Omnipod (POD** и убедитесь, что поле **статус помпы (1)** отображает **ПОМПА ОСТАНОВЛЕНА (ПРИОСТАНОВЛЕНО)**, затем нажмите кнопку **ВОЗОБНОВИТЬ ПОДАЧУ(2)** для передачи команды на Pod о возобновлении подачи инсулина. Сообщение **Возобновить подачу** будет отображаться в поле **Статус Pod (3)**, показывая, что RileyLink активно отправляет команду на остановленный Pod. @@ -574,7 +574,7 @@ orphan: true ![Параметры_Omnipod_2](../images/omnipod/Omnipod_Settings_2.png) -Группы настроек перечислены ниже; вы можете включить или отключить их через переключатель большинства функций описанных ниже: +The settings groups are listed below; you can enable or disable via a toggle switch for most entries described below: ![Параметры_Omnipod_3](../images/omnipod/Omnipod_Settings_3.png) @@ -595,7 +595,7 @@ orphan: true ### Звуковые сигналы подтверждения -Обеспечивает звуковые сигналы подтверждения от Pod об успешной подаче болюса, изменении базала, SMB и TBR. +Provides confirmation beeps from the pod for bolus, basal, SMB, and TBR delivery and changes. - **Звуковой сигнал болюса включен** Включить или отключить подтверждающие сигналы при подаче болюса. - **Звуковой сигнал базала включен:** Включить или отключить звуки подтверждения, когда установлена новая базальная скорость, отменена или изменена действующая базальная скорость. @@ -606,7 +606,7 @@ orphan: true Оповещения AAPS и Nightscout об истечении срока, выключении, низком резервуаре на основе заданных пороговых значений. -*Примечание: уведомления AAPS выдаются ВСЕГДА для любого оповещения после связи с pod с момента срабатывания оповещения. Сброс уведомления НЕ удалит оповещение, ЕСЛИ НЕ включено автоматическое подтверждение получения оповещений. Чтобы ВРУЧНУЮ убрать оповещение следует открыть вкладку Omnipod (POD) и нажать кнопку Заглушать СИГНАЛЫ ОПОВЕЩЕНИЯ.* +*Note an AAPS notification will ALWAYS be issued for any alert after the initial communication with the pod since the alert was triggered. Dismissing the notification will NOT dismiss the alert UNLESS automatically acknowledge Pod alerts is enabled. Чтобы ВРУЧНУЮ убрать оповещение следует открыть вкладку Omnipod (POD) и нажать кнопку Заглушать СИГНАЛЫ ОПОВЕЩЕНИЯ.* - ***Включено напоминание об истечении срока действия:** Включение или отключение напоминания о истечении срока действия струи для срабатывания по достижении определенного количества часов до завершения работы. - **Время до выключения**. @@ -618,7 +618,7 @@ orphan: true Выдает уведомления AAPS и звуковые оповещения, когда нет уверенности в успешных TBR, SMB, болюсах или приостановленных событиях. -*ПРИМЕЧАНИЕ: Это только уведомления, звуковые оповещения об ошибках не производится.* +*NOTE: These are notifications only, no audible beep alerts are made.* - **Звук для неопределенных уведомлений TBR включен:** Включите или отключите этот параметр, чтобы вызвать звуковое оповещение и визуальное уведомление, когда AAPs неизвестно, был ли установлен TBR. - **Звук для неопределенных уведомлений SMB включен:** Включите или отключите этот параметр, чтобы вызвать звуковое оповещение и визуальное уведомление, когда AAPs неизвестно, был ли успешно подан микроболюс SMB. @@ -690,7 +690,7 @@ orphan: true ### Уровни -**Уровень инсулина** +**Insulin Level** Информация о количестве инсулина в Omnipod Eros не является точной. Это потому, что точно не известно сколько инсулина было заправлено в Pod, и только при срабатывании 2 звуковых сигналов при заполнении пода, станет понятно, что заправлено 85 единиц инсулина. Под может вместить максимум 200 единиц. Заполнение катетера также может добавить неточности, поскольку это не точный процесс. Учитывая оба этих фактора и был написан драйвер Omnipod, который дает максимально точное приближение к количеству остающегося в резервуаре инсулина. @@ -716,11 +716,11 @@ orphan: true ### Сбои в работе Pod -Поды иногда подводят из-за различных проблем, включая аппаратные неполадки в самих Pod. В Insulet с этим лучше не обращаться в, поскольку приложение AAPS пока не получила официального одобрения. Список ошибок можно найти [здесь](https://github.com/openaps/openomni/wiki/Fault-event-codes) для помощи в определении причины. +Pods fail occasionally due to a variety of issues, including hardware issues with the Pod itself. It is best practice not to call these into Insulet, since AAPS is not an approved use case. Список ошибок можно найти [здесь](https://github.com/openaps/openomni/wiki/Fault-event-codes) для помощи в определении причины. ### Предотвращение ошибки 49 при сбоях Pod -Эта неисправность связана с некорректным состоянием Pod во время команды или ошибки при подаче инсулина. Чтобы предотвратить возможные сбои рекомендуем пользователям переключиться на клиент Nightscout на *только загружать (отключить синхронизацию)* в **Конфигураторе**➜**Общие**➜**NSClient**➜**шестеренка настроек**➜**Расширенные настройки**,. +This failure is related to an incorrect pod state for a command or an error during an insulin delivery command. Чтобы предотвратить возможные сбои рекомендуем пользователям переключиться на клиент Nightscout на *только загружать (отключить синхронизацию)* в **Конфигураторе**➜**Общие**➜**NSClient**➜**шестеренка настроек**➜**Расширенные настройки**,. ### Оповещения о недоступности помпы @@ -739,7 +739,7 @@ orphan: true ### Оповещения драйвера Omnipod -обратите внимание, что драйвер Omnipod Erosсодержит множество оповещений на вкладке **Начало**, большинство из них являются информационными и могут быть отключены, в то время как некоторые предоставляют пользователю возможности устранения причин оповещения. Ниже приводится краткая информация об основных оповещениях: +обратите внимание, что драйвер Omnipod Erosсодержит множество оповещений на вкладке **Начало**, большинство из них являются информационными и могут быть отключены, в то время как некоторые предоставляют пользователю возможности устранения причин оповещения. A summary of the main alerts that you may encounter is listed below: #### Нет активных Pod diff --git a/docs/CROWDIN/ru/GettingHelp/GeneralTroubleshooting.md b/docs/CROWDIN/ru/GettingHelp/GeneralTroubleshooting.md index 2dab1509b2c3..cf1e5612e774 100644 --- a/docs/CROWDIN/ru/GettingHelp/GeneralTroubleshooting.md +++ b/docs/CROWDIN/ru/GettingHelp/GeneralTroubleshooting.md @@ -37,14 +37,37 @@ Ignore it: More details, Install anyway. * [SMS-команды](#SMSCommands-troubleshooting) -### Частые проблемы с подключением Bluetooth +### Frequent Bluetooth connection problems -Это может произойти с различными помпами. Помимо того, что AAPS должен быть исключен из оптимизации батареи, можно также исключить системное приложение Bluetooth из оптимизации батареи. В некоторых случаях это может помочь. В зависимости от используемого телефона приложение bluetooth находится по-разному. +#### Android 15 + +```{warning} +Developers are working on this issue impacting **AAPS** on some Samsung and Pixel phones. +``` + +After upgrading Android or moving to a recent phone, **AAPS** frequently loses Bluetooth connection to the pump. The problem disappears temporarily when restarting the phone. If the phone runs Android 15, you can try to enable the following: + +1) **Open preferences** by clicking the three-dot menu on the top right side of the home screen. + + +![Open preferences](../images/Pref2020_Open2.png) + +2. Scroll down and open the **Confirmation beeps** / **Advanced** submenu. Enable **Bond BT device on Android 15+**. + + ![BondBT](../images/troubleshooting/BondBT.png) + +3. If the pump asks for a pairing request, accept it. + +4. Restart your phone. + +#### Battery optimization + +Это может произойти с различными помпами. Apart from excluding AAPS from any battery optimization, you can also exclude the system Bluetooth app from battery optimization. В некоторых случаях это может помочь. Depending on the phone you use, you will find the Bluetooth app differently. Вот примеры того, как найти их на конкретных Android-телефонах. -#### ТелефоныPixel (стоковый android) +##### Pixel phones (stock Android) * Перейдите в настройки Android и выберите "Приложения". @@ -67,7 +90,7 @@ Ignore it: More details, Install anyway. ![Оптимизация батареи BT](../images/troubleshooting/pixel/04_btunrestricted.png) -#### Телефоны Samsung +##### Телефоны Samsung * Перейдите в настройки Android и выберите "Приложения" diff --git a/docs/CROWDIN/ru/images/troubleshooting/BondBT.png b/docs/CROWDIN/ru/images/troubleshooting/BondBT.png new file mode 100644 index 000000000000..96b2fb272d90 Binary files /dev/null and b/docs/CROWDIN/ru/images/troubleshooting/BondBT.png differ diff --git a/docs/CROWDIN/ru/images/troubleshooting/samsung/01_BondBT_20250526.png b/docs/CROWDIN/ru/images/troubleshooting/samsung/01_BondBT_20250526.png new file mode 100644 index 000000000000..74c3525959ed Binary files /dev/null and b/docs/CROWDIN/ru/images/troubleshooting/samsung/01_BondBT_20250526.png differ diff --git a/docs/CROWDIN/ru/images/troubleshooting/samsung/02_BondBT_20250526.png b/docs/CROWDIN/ru/images/troubleshooting/samsung/02_BondBT_20250526.png new file mode 100644 index 000000000000..444013b29146 Binary files /dev/null and b/docs/CROWDIN/ru/images/troubleshooting/samsung/02_BondBT_20250526.png differ diff --git a/docs/CROWDIN/ru/images/troubleshooting/samsung/03_BondBT_20250526.png b/docs/CROWDIN/ru/images/troubleshooting/samsung/03_BondBT_20250526.png new file mode 100644 index 000000000000..9caa7a484581 Binary files /dev/null and b/docs/CROWDIN/ru/images/troubleshooting/samsung/03_BondBT_20250526.png differ diff --git a/docs/CROWDIN/ru/images/troubleshooting/samsung/04_BondBT_20250526.png b/docs/CROWDIN/ru/images/troubleshooting/samsung/04_BondBT_20250526.png new file mode 100644 index 000000000000..b25c1469f58e Binary files /dev/null and b/docs/CROWDIN/ru/images/troubleshooting/samsung/04_BondBT_20250526.png differ diff --git a/docs/CROWDIN/sk/CompatiblePumps/OmnipodDASH.md b/docs/CROWDIN/sk/CompatiblePumps/OmnipodDASH.md index 99858bc2c15a..e214813cf186 100644 --- a/docs/CROWDIN/sk/CompatiblePumps/OmnipodDASH.md +++ b/docs/CROWDIN/sk/CompatiblePumps/OmnipodDASH.md @@ -18,7 +18,13 @@ These are the specifications of the **Omnipod DASH** ('DASH') and what different * On pod activation, **AAPS** will find and connect to a new DASH pod. * Expected range: 5-10 meters (YMMV). -WARNING: There are currently reported Bluetooth connection issues with the following combination of **AAPS** / DASH / Android 15. **AAPS** should not be used in combination with Android 15 and DASH unless the user has checked the following [**List**](https://docs.google.com/spreadsheets/u/1/d/e/2PACX-1vScCNaIguEZVTVFAgpv1kXHdsHl3fs6xT6RB2Z1CeVJ561AvvqGwxMhlmSHk4J056gMCAQE02sAWJvT/pubhtml?gid=683363241&single=true) and verified that their phone is not a known reported issue. **AAPS** is currently working to resolve this issue. +```{admonition} Android 15 +:class: warning + +There are currently reported Bluetooth connection issues with the following combination of **AAPS**: DASH + Android 15. +Please refrain from upgrading your phone to Android 15 unless you have checked the following [**list**](https://docs.google.com/spreadsheets/u/1/d/e/2PACX-1vScCNaIguEZVTVFAgpv1kXHdsHl3fs6xT6RB2Z1CeVJ561AvvqGwxMhlmSHk4J056gMCAQE02sAWJvT/pubhtml?gid=683363241&single=true) and verified that your phone is not a known reported issue. +If you experience frequent disconnection; try to enable Bond BT as described in: [**Bluetooth Issues**](../GettingHelp/GeneralTroubleshooting.md). +``` ## Hardware/Software Requirements diff --git a/docs/CROWDIN/sk/GettingHelp/GeneralTroubleshooting.md b/docs/CROWDIN/sk/GettingHelp/GeneralTroubleshooting.md index 53f458bdece5..53a847b4f4b2 100644 --- a/docs/CROWDIN/sk/GettingHelp/GeneralTroubleshooting.md +++ b/docs/CROWDIN/sk/GettingHelp/GeneralTroubleshooting.md @@ -37,14 +37,37 @@ Ignore it: More details, Install anyway. * [SMS commands](#SMSCommands-troubleshooting) -### Frequent bluetooth connection problems +### Frequent Bluetooth connection problems -This can happen with various pumps. Apart from excluding AAPS from any battery optimization, you can also exclude the system bluetooth app from battery optimization. This can help in some cases. Depending on the phone you use, you will find the bluetooth app differently. +#### Android 15 + +```{warning} +Developers are working on this issue impacting **AAPS** on some Samsung and Pixel phones. +``` + +After upgrading Android or moving to a recent phone, **AAPS** frequently loses Bluetooth connection to the pump. The problem disappears temporarily when restarting the phone. If the phone runs Android 15, you can try to enable the following: + +1) **Open preferences** by clicking the three-dot menu on the top right side of the home screen. + + +![Open preferences](../images/Pref2020_Open2.png) + +2. Scroll down and open the **Confirmation beeps** / **Advanced** submenu. Enable **Bond BT device on Android 15+**. + + ![BondBT](../images/troubleshooting/BondBT.png) + +3. If the pump asks for a pairing request, accept it. + +4. Restart your phone. + +#### Battery optimization + +This can happen with various pumps. Apart from excluding AAPS from any battery optimization, you can also exclude the system Bluetooth app from battery optimization. This can help in some cases. Depending on the phone you use, you will find the Bluetooth app differently. Here are examples how to find them on specific android phones. -#### Pixel phones (stock android) +##### Pixel phones (stock Android) * Go to the android settings, select "Apps". @@ -67,7 +90,7 @@ Here are examples how to find them on specific android phones. ![BT Battery optimization](../images/troubleshooting/pixel/04_btunrestricted.png) -#### Samsung phones +##### Samsung phones * Go to the android settings, select "Apps" diff --git a/docs/CROWDIN/sk/images/troubleshooting/BondBT.png b/docs/CROWDIN/sk/images/troubleshooting/BondBT.png new file mode 100644 index 000000000000..96b2fb272d90 Binary files /dev/null and b/docs/CROWDIN/sk/images/troubleshooting/BondBT.png differ diff --git a/docs/CROWDIN/sk/images/troubleshooting/samsung/01_BondBT_20250526.png b/docs/CROWDIN/sk/images/troubleshooting/samsung/01_BondBT_20250526.png new file mode 100644 index 000000000000..74c3525959ed Binary files /dev/null and b/docs/CROWDIN/sk/images/troubleshooting/samsung/01_BondBT_20250526.png differ diff --git a/docs/CROWDIN/sk/images/troubleshooting/samsung/02_BondBT_20250526.png b/docs/CROWDIN/sk/images/troubleshooting/samsung/02_BondBT_20250526.png new file mode 100644 index 000000000000..444013b29146 Binary files /dev/null and b/docs/CROWDIN/sk/images/troubleshooting/samsung/02_BondBT_20250526.png differ diff --git a/docs/CROWDIN/sk/images/troubleshooting/samsung/03_BondBT_20250526.png b/docs/CROWDIN/sk/images/troubleshooting/samsung/03_BondBT_20250526.png new file mode 100644 index 000000000000..9caa7a484581 Binary files /dev/null and b/docs/CROWDIN/sk/images/troubleshooting/samsung/03_BondBT_20250526.png differ diff --git a/docs/CROWDIN/sk/images/troubleshooting/samsung/04_BondBT_20250526.png b/docs/CROWDIN/sk/images/troubleshooting/samsung/04_BondBT_20250526.png new file mode 100644 index 000000000000..b25c1469f58e Binary files /dev/null and b/docs/CROWDIN/sk/images/troubleshooting/samsung/04_BondBT_20250526.png differ diff --git a/docs/CROWDIN/tr/CompatiblePumps/MedtrumNano.md b/docs/CROWDIN/tr/CompatiblePumps/MedtrumNano.md index bc6184c96b15..93300d0297d5 100644 --- a/docs/CROWDIN/tr/CompatiblePumps/MedtrumNano.md +++ b/docs/CROWDIN/tr/CompatiblePumps/MedtrumNano.md @@ -39,9 +39,9 @@ Bu yazılım bir DIY (Kendin Yap) yapay pankreas çözümünün bir parçasıdı **Your pump will not stop delivering insulin when it is not connected to AAPS** Default basal rates are programmed on the pump as defined in the current active profile. As long as AAPS is operational, it will send temporary basal rate commands that run for a maximum of 120 minutes. If for some reason the pump does not receive any new commands (for instance because communication was lost due to pump - phone distance) the pump will fall back to the default basal rate programmed on the pump once the Temporary Basal Rate ends. -**30 dk Bazal Oranı Profilleri AAPS'de DESTEKLENMEZ.** **AndroidAPS Profili, 30 dakikalık bir bazal oran zaman dilimini desteklemiyor.** AAPS'de yeniyseniz ve bazal oran profilinizi ilk kez oluşturuyorsanız, yarım saatlik bazal oranların desteklenmediğini ve başlangıç için bazal oran profilinizi saatlik olarak ayarlamanız gerekeceğini lütfen unutmayın. Örneğin, 09:30'da başlayan ve 11:30'da biten 2 saatlik bir süresi olan 1,1 birimlik bir bazal oranınız varsa, bu çalışmayacaktır. Bu 1,1 birim bazal oranını 9:00-11:00 veya 10:00-12:00 zaman aralığına değiştirmeniz gerekecektir. Even though the Medtrum pump hardware itself supports the 30 min basal rate profile increments, AAPS is not able to take them into account with its algorithms currently. +**30 dk Bazal Oranı Profilleri AAPS'de DESTEKLENMEZ.** **AndroidAPS Profili, 30 dakikalık bir bazal oran zaman dilimini desteklemiyor.** AAPS'de yeniyseniz ve bazal oran profilinizi ilk kez oluşturuyorsanız, yarım saatlik bazal oranların desteklenmediğini ve başlangıç için bazal oran profilinizi saatlik olarak ayarlamanız gerekeceğini lütfen unutmayın. Örneğin, 09:30'da başlayan ve 11:30'da biten 2 saatlik bir süresi olan 1,1 birimlik bir bazal oranınız varsa, bu çalışmayacaktır. 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 Medtrum pump hardware itself supports the 30 min basal rate profile increments, AAPS is not able to take them into account with its algorithms currently. -**0U/h profile basal rates are NOT supported in AAPS** While the Medtrum pump does support a zero basal rate, AAPS uses multiples of the profile basal rate to determine automated treatment and therefore cannot function with a zero basal rate. "Pompa bağlantısını kes" işleviyle veya Döngüyü devre dışı bırak/Geçici bazal hızı veya Döngüyü Askıya Al/Geçici bazal hızı kombinasyonu aracılığıyla geçici bir sıfır bazal hız elde edilebilir. +**0U/h profile basal rates are NOT supported in AAPS** While the Medtrum pump does support a zero basal rate, AAPS uses multiples of the profile basal rate to determine automated treatment and therefore cannot function with a zero basal rate. A temporary zero basal rate can be achieved through the "Disconnect pump" function or through a combination of Disable Loop/Temp Basal Rate or Suspend Loop/Temp Basal Rate. ## Kurulum diff --git a/docs/CROWDIN/tr/CompatiblePumps/OmnipodDASH.md b/docs/CROWDIN/tr/CompatiblePumps/OmnipodDASH.md index ee34affa00d3..c18943b21525 100644 --- a/docs/CROWDIN/tr/CompatiblePumps/OmnipodDASH.md +++ b/docs/CROWDIN/tr/CompatiblePumps/OmnipodDASH.md @@ -18,7 +18,13 @@ These are the specifications of the **Omnipod DASH** ('DASH') and what different * On pod activation, **AAPS** will find and connect to a new DASH pod. * Expected range: 5-10 meters (YMMV). -WARNING: There are currently reported Bluetooth connection issues with the following combination of **AAPS** / DASH / Android 15. **AAPS** should not be used in combination with Android 15 and DASH unless the user has checked the following [**List**](https://docs.google.com/spreadsheets/u/1/d/e/2PACX-1vScCNaIguEZVTVFAgpv1kXHdsHl3fs6xT6RB2Z1CeVJ561AvvqGwxMhlmSHk4J056gMCAQE02sAWJvT/pubhtml?gid=683363241&single=true) and verified that their phone is not a known reported issue. **AAPS** is currently working to resolve this issue. +```{admonition} Android 15 +:class: warning + +There are currently reported Bluetooth connection issues with the following combination of **AAPS**: DASH + Android 15. +Please refrain from upgrading your phone to Android 15 unless you have checked the following [**list**](https://docs.google.com/spreadsheets/u/1/d/e/2PACX-1vScCNaIguEZVTVFAgpv1kXHdsHl3fs6xT6RB2Z1CeVJ561AvvqGwxMhlmSHk4J056gMCAQE02sAWJvT/pubhtml?gid=683363241&single=true) and verified that your phone is not a known reported issue. +If you experience frequent disconnection; try to enable Bond BT as described in: [**Bluetooth Issues**](../GettingHelp/GeneralTroubleshooting.md). +``` ## Donanım/Yazılım Gereksinimleri @@ -37,15 +43,15 @@ The instructions below explain how to activate a new pod session. Wait to close **SAFETY FIRST** - you should not try to connect **AAPS** to a pod for the first time without having access to extra pods, insulin, and phone devices are a must have. -**Your Omnipod Dash PDM will become redundant after the AAPS Dash driver activates your pod.** Previously a user may have operated a PDM to send commands to your DASH. A DASH will only faciiliate a single device to send commands to communicate with it. Podu başarıyla etkinleştiren cihaz, o andan itibaren onunla iletişim kurmasına izin verilen tek cihazdır. This means that once you activate a DASH with your Android phone through the **AAPS**, **you will no longer be able to use your PDM with that pod**. The **AAPS** Dash driver in your Android phone is now your acting PDM. +**Your Omnipod Dash PDM will become redundant after the AAPS Dash driver activates your pod.** Previously a user may have operated a PDM to send commands to your DASH. A DASH will only faciiliate a single device to send commands to communicate with it. The device that successfully activates the pod is the only device allowed to communicate with it from that point forward. This means that once you activate a DASH with your Android phone through the **AAPS**, **you will no longer be able to use your PDM with that pod**. The **AAPS** Dash driver in your Android phone is now your acting PDM. -*Bu PDM'nizi atmanız gerektiği anlamına GELMEZ, yedek olarak ve örneğin telefonunuz kaybolduğunda veya AAPS düzgün çalışmadığında acil durumlar için bir kenarda tutmanız önerilir.* +*This does NOT mean you should throw away your PDM, it is recommended to keep it around as a backup and for emergencies, for instance when your phone gets lost or AAPS is not working correctly.* -**Podunuz, AAPS'e bağlı olmadığında insülin vermeyi durdurmaz**. Default basal rates are programmed on the pod on activation as defined in the current active **Profile**. As long as **AAPS** is operational it will send basal rate commands that run for a maximum of 120 minutes. Herhangi bir nedenle pod herhangi bir yeni komut almadığında (örneğin, Pod - telefon mesafesi nedeniyle iletişimin kesilmesi) pod otomatik olarak varsayılan bazal oranlarına geri dönecektir. +**Your pod will not stop delivering insulin when it is not connected to AAPS**. Default basal rates are programmed on the pod on activation as defined in the current active **Profile**. As long as **AAPS** is operational it will send basal rate commands that run for a maximum of 120 minutes. 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. -**AAPS Profile does not support a 30 minute basal rate time frame** If you are new to **AAPS** and are setting up your basal rate **Profile** for the first time, please be aware that basal rates starting on a half-hour basis are not supported, and programmes on an hourly basis. For example, 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 im **AAPS**. Bu 1,1 birim bazal oranını 9:00-11:00 veya 10:00-12:00 zaman aralığına değiştirmeniz gerekecektir. Even though the DASH hardware itself supports the 30 minute basal rate **Profile** increments, **AAPS** does support this feature. +**AAPS Profile does not support a 30 minute basal rate time frame** If you are new to **AAPS** and are setting up your basal rate **Profile** for the first time, please be aware that basal rates starting on a half-hour basis are not supported, and programmes on an hourly basis. For example, 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 im **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 support this feature. -**0U/h profile basal rates are NOT supported in AAPS** While the DASH does support a zero basal rate, since **AAPS** uses multiples of the user's **Profile** basal rate to determine automated treatment; it cannot function with a zero basal rate. "Pompa bağlantısını kes" işleviyle veya Döngüyü devre dışı bırak/Geçici bazal hızı veya Döngüyü Askıya Al/Geçici bazal hızı kombinasyonu aracılığıyla geçici bir sıfır bazal hız elde edilebilir. The lowest basal rate allowed in **AAPS** is 0.05U/h. +**0U/h profile basal rates are NOT supported in AAPS** While the DASH does support a zero basal rate, since **AAPS** uses multiples of the user's **Profile** basal rate to determine automated treatment; it cannot function with a zero basal rate. A temporary zero basal rate can be achieved through the "Disconnect pump" function or through a combination of Disable Loop/Temp Basal Rate or Suspend Loop/Temp Basal Rate. The lowest basal rate allowed in **AAPS** is 0.05U/h. ## Selecting Dash in AAPS @@ -53,7 +59,7 @@ There are **two ways**: ### Seçenek 1: Yeni kurulum -When installing **AAPS** for the first time, the **Setup Wizard** will guide new users through key features and installation requirements for **AAPS**. Pompa seçimine ulaştığınızda “DASH” seçeneğini seçin. +When installing **AAPS** for the first time, the **Setup Wizard** will guide new users through key features and installation requirements for **AAPS**. Select “DASH” when you reach Pump selection. ![Enable_Dash_1](../images/DASH_images/Enable_Dash/Enable_Dash_1.png) @@ -61,9 +67,9 @@ When in doubt you can also select “Virtual Pump” and select “DASH” later ### Seçenek 2: Konfigürasyon ayarları -Mevcut bir kurulumda, Konfigürasyon ayarları altında **DASH** pompasını seçebilirsiniz: +On an existing installation you can select the **DASH** pump from the Config builder: -Sol üst köşede **hamburger menüsü** seçilip **Konfigürasyon ayarları (1)**\ ➜\ **Pompa**\ ➜\ **Dash**\ ➜**Dişli Çark (3)** Dash satırındaki ** radyo butonu (2)** seçilir. +On the top-left hand corner **hamburger menu** select **Config Builder (1)**\ ➜\ **Pump**\ ➜\ **Dash**\ ➜\ **Settings Gear (3)** by selecting the **radio button (2)** titled **Dash**. Selecting the **checkbox (4)** next to the **Settings Gear (3)** will allow the DASH menu to be displayed as a tab in the **AAPS** interface titled **DASH**. Checking this box will facilitate your access to the DASH commands when using **AAPS**. @@ -79,7 +85,7 @@ To verify that you have selected the DASH in **AAPS**, if you have checked the b ## Dash Konfigürasyonu -Lütfen **sola kaydırıp** tüm pod işlevlerini yönetebileceğiniz **DASH** sekmesine ulaşın.(bu işlevlerden bazıları etkin bir pod oturumu olmadan etkinleştirilmez veya görünmez): +Please **swipe left** to the **DASH** tab where you will be able to manage all pod functions (some of these functions are not enabled or visible without an active pod session): ![Refresh_LOGO](../images/DASH_images/Refresh_LOGO.png) 'Refresh' pod connectivity and status, be able to silence pod alarms when the pod beeps @@ -100,7 +106,7 @@ Lütfen **sola kaydırıp** tüm pod işlevlerini yönetebileceğiniz **DASH** s Ensure that the new pod and the phone running **AAPS** are within close proximity of each other and click the **Next** button. -**NOTE**: if the error message below pops up _'Could not find an available pod for activation'_ (this can happen), do not panic. **TEKRAR DENE** butonunu tıklayın. Çoğu durumda etkinleştirme başarıyla devam eder. +**NOTE**: if the error message below pops up _'Could not find an available pod for activation'_ (this can happen), do not panic. Click on the **Retry** button. In most situations activation will continue successfully. ![Activate_Pod_3](../images/DASH_images/Activate_pod_error.png) @@ -140,16 +146,16 @@ Ensure that the new pod and the phone running **AAPS** are within close proximit ​ ![Activate_Pod_15](../images/DASH_images/Activate_Pod/Activate_Pod_15.jpg) -Podu etkinleştirdikten SONRA ayarları dışa aktarmak akıllıca olacaktır. Export settings should be done at each pod change and once a month, copy the exported file to your internet drive. see [**Export settings Doc**](../Maintenance/ExportImportSettings.md). +It is good practice to export settings AFTER activating the pod. Export settings should be done at each pod change and once a month, copy the exported file to your internet drive. see [**Export settings Doc**](../Maintenance/ExportImportSettings.md). (OmnipodDASH-deactivate-pod)= ### Pod'u Devre Dışı Bırakma -Normal koşullar altında, bir podun beklenen ömrü üç gündür. (72 saat) Pod sona erme uyarısından sonra ek 8 saattlik süre ile toplam 80 saat olabilir. +Under normal circumstances, the expected lifetime of a pod is three days (72 hours) and an additional 8 hours after the pod expiration warning for a total of 80 hours of pod usage. -Bir Podu devre dışı bırakmak (süre sonundan veya bir pod hatasından dolayı): +To deactivate a pod (either from expiration or from a pod failure): 1. **DASH** sekmesine gidin, **POD YNTM (1)** butonunu tıklayın, **pod yönetimi** ekranında **Pod'u Devre Dışı Bırak (2)** butonunu tıklayın. @@ -182,7 +188,7 @@ Bir Podu devre dışı bırakmak (süre sonundan veya bir pod hatasından dolay **Note**: During **Profile Switches**, DASH must suspend delivery before setting the new basal **Profile** as delivery can be suspended. Read [**Delivery suspended**](#delivery-suspended) in the troubleshooting section for more details. -İletimi askıya alınmış Pod'unuzun insülin iletimini yeniden başlatma talimatı vermek için bu komutu kullanın. After the command is successfully processed, insulin will resume normal delivery using the current basal rate based on the current time from the active basal **Profile**. The pod will again accept commands for bolus, **TBR**, and **SMB**. +Use this command to instruct the active, currently suspended pod to resume insulin delivery. After the command is successfully processed, insulin will resume normal delivery using the current basal rate based on the current time from the active basal **Profile**. The pod will again accept commands for bolus, **TBR**, and **SMB**. 1. **DASH** sekmesine gidin ve **Pod durumu (1)** satırında **ASKIYA ALINDI** mesajının görünmesi gerekir, ardından mevcut podun normal insülin iletimini sürdürmesi talimatını vermek için **İLETİME DEVAM ET (2)** butonuna basın. **Pod Durumu (3)** satırında **İleme Devam Et** mesajı görüntülenir. @@ -198,9 +204,9 @@ Bir Podu devre dışı bırakmak (süre sonundan veya bir pod hatasından dolay ### Pod Alarmlarını Susturma -*NOT - ALARMLARI SUSTUR butonu yalnızca **DASH** sekmesinde pod sona erme veya düşük rezervuar uyarısı tetiklendiğinde kullanılabilir. Alarmları Sustur butonu görünmüyorsa ve poddan bip sesleri duyuyorsanız, 'Pod durumunu yenilemeyi' deneyin.* +*NOTE - The SILENCE ALERTS button is only available on the **DASH** tab when the pod expiration or low reservoir alert has been triggered. If the SILENCE ALERTS button is not visible and you hear beep sounds from the pod, try to 'Refresh pod status'.* -Aşağıdaki süreç, aktif 72 saatlik (3 gün) pod süresi sona ermeden önce uyarı süresi sınırına ulaştığında pod bip seslerini nasıl onaylayacağınızı ve kapatacağınızı gösterecektir. Bu uyarı zaman sınırı, Dash uyarıları ayarında **Kapanmadan kaç saat önce?** satırında tanımlanır. Bir pod'un maksimum ömrü 80 saattir (3 gün 8 saat), ancak Insulet 72 saat (3 gün) sınırının aşılmamasını önermektedir. +The process below will show you how to acknowledge and dismiss pod beeps when the active pod time reaches the warning time limit before the pod expiration of 72 hours (3 days). This warning time limit is defined in the **Hours before shutdown** Dash alerts setting. The maximum life of a pod is 80 hours (3 days 8 hours), however Insulet recommends not exceeding the 72 hours (3 days) limit. 1. Tanımlanan **Kapanmadan kaç saat önce?** uyarı süresi sınırına ulaşıldığında, pod sona erme zamanına yaklaştığını size bildirmek için uyarı bip sesleri çıkaracak ve yakında pod değişikliği gerekecektir. Bunu **DASH** sekmesinde doğrulayabilirsiniz, **Pod Sona Erme: (1)** satırı tam zamanı gösterecektir. Pod'un süresi dolar (etkinleştirmeden 72 saat sonra) ve bu süre geçerse metin **kırmızı** olacaktır. **Etkin pod alarmları (2)** satırında, **Pod'un süresi yakında dolacak** durum mesajı görüntülenir. Bu aynı zamanda **ALARMLARI SUSTUR (3)** butonunun görüntülenmesini de tetikler. @@ -221,11 +227,11 @@ Aşağıdaki süreç, aktif 72 saatlik (3 gün) pod süresi sona ermeden önce u ### Pod Geçmişini Görüntüle -This section explains how to review your active pod history and filter by different action categories. Pod geçmişi aracı, üç günlük (72 - 80 saat) ömrü boyunca şu anda etkin olan pod'unuza yönelik eylemleri ve sonuçları görüntülemenize olanak tanır. +This section explains how to review your active pod history and filter by different action categories. The pod history tool allows you to view the actions and results committed to your currently active pod during its three days (72 - 80 hours) life. -Bu özellik, pod'a gönderilen bolusların, GBO'larin ve bazal komutların doğrulanmasında yardımcı olur. Kalan kategoriler, genel olarak sorunları gidermek ve bir arızaya yol açan olayların sırasını belirlemek için kullanışlıdır. +This feature is helpful in verifying boluses, TBRs and basal commands that were sent to the pod. The remaining categories are useful for troubleshooting issues and determining the order of events that occurred leading up to a failure. -*NOT:* **Yalnızca son komut belirsiz olabilir**. **son 'belirsiz' komut 'onaylanan' veya 'reddedilen'** olana kadar yeni komutlar *gönderilmeyecektir*. Belirsiz komutları 'düzeltmenin' yolu, **'pod durumunu yenilemek'**tir. +*NOTE:* **Only the last command can be uncertain**. New commands *will not be sent* until the **last 'uncertain' command becomes 'confirmed' or 'denied'**. The way to 'fix' uncertain commands is to **'refresh pod status'**. 1. **DASH** sekmesine gidin ve **POD YNTM (1)** butonuna basarak **Pod Yönetimi** menüsüne gidin ve ardından pod geçmişi ekranına erişmek için **Pod geçmişi (2)** butonuna basın. @@ -246,9 +252,9 @@ Bu özellik, pod'a gönderilen bolusların, GBO'larin ve bazal komutların doğr ## DASH Sekmesi -Aşağıda, ana AAPS arayüzündeki **DASH** sekmesindeki simgelerin ve durum satırlarının düzeninin ve anlamının bir açıklaması bulunmaktadır. +Below is an explanation of the layout and meaning of the icons and status fields on the **DASH** tab in the main AAPS interface. -*NOT: **DASH** sekmesi durum satırları raporunda herhangi bir mesaj varsa (belirsiz), bunu temizlemek ve pod durumunu yenilemek için Yenile butonuna basmanız gerekir.* +*NOTE: If any message in the **DASH** tab status fields report (uncertain), then you will need to press the Refresh button to clear it and refresh the pod status.* ![DASH_Tab_1](../images/DASH_images/DASH_Tab/DASH_Tab_1.png) @@ -402,25 +408,25 @@ Additional note: - If **AAPS** fails to resume delivery on its own (this happens if the pod is unreachable, sound is muted, etc), the pod will start beeping 4 times every minute for 3 minutes, then repeated every 15 minutes if delivery is still suspended for more than 20 minutes. * Onaylanmamış komutlar için "pod durumunu yenile" komutu, bunları onaylamalı/reddetmelidir. -**Not:** Pod bip seslerini duyduğunuzda, telefonu kontrol etmeden iletimin devam ettiğini varsaymayın, iletim askıya alınmış olabilir, **bu yüzden kontrol etmeniz gerekiyor!** +**Note:** When you hear beeps from the pod, do not assume that delivery will continue without checking the phone, delivery might stay suspended, **so you need to check !** ### Pod Hataları -Pod'larda, kendisiyle ilgili donanım sorunları da dahil olmak üzere çeşitli sorunlar nedeniyle ara sıra hatalar olabiliyor. AAPS onaylanmış bir kullanım şekli olmadığından, bunları Insulet'e bildirmemek en iyi seçenektir. Nedenini belirlemeye yardımcı olacak hata kodlarının bir listesi [**burada bulunabilir.**](https://github.com/openaps/openomni/wiki/Fault-event-codes) +Pods fail occasionally due to a variety of issues, including hardware issues with the Pod itself. It is best practice not to call these into Insulet, since AAPS is not an approved use case. A list of fault codes can be [**found here**](https://github.com/openaps/openomni/wiki/Fault-event-codes) to help determine the cause. ### 49 numaralı Pod hatasını önleme -Bu hata bir komut için yanlış bir pod durumu veya bir insülin iletim komutu sırasındaki bir hata ile ilgilidir. Bu, sürücü ve Pod'un gerçek durum üzerinde anlaşamadığı zaman meydana gelir. The Pod (out of a built-in safety measure) then reacts with an unrecoverable error code 49 (0x31) ending up with what is know as a “screamer”: the long irritating beep that can only be stopped by punching a hole at the appropriate location at the back of the Pod. "49 pod arızasının" kesin kök nedenini izlemek çoğu zaman zordur. Bu hatanın meydana gelmesinde şüphelenilen durumlar, örneğin uygulama çökmeleri, bir geliştirme sürümünün çalıştırılması veya yeniden kurulumdur. +This failure is related to an incorrect pod state for a command or an error during an insulin delivery command. This is when the driver and Pod disagree on the actual state. The Pod (out of a built-in safety measure) then reacts with an unrecoverable error code 49 (0x31) ending up with what is know as a “screamer”: the long irritating beep that can only be stopped by punching a hole at the appropriate location at the back of the Pod. The exact origin of a “49 pod failure” often is hard to trace. In situations that are suspected for this failure to occur (for instance on application crashes, running a development version or re-installation). ### Pompaya Ulaşılamıyor Uyarıları -Önceden yapılandırılmış bir süre boyunca pod ile iletişim kurulamadığında, "Pompaya ulaşılamıyor" uyarısı verilir. Pompaya erişilemiyor uyarıları, sağ üst taraftaki üç noktalı menüye gidip **Tercihler**\ ➜\ **Yerel uyarılar**\ ➜\ **Pompa ulaşılamaz eşiği [dk]** öğesi seçilerek yapılandırılabilir. Önerilen değer, **120** dakika sonra uyarı vermesidir. +When no communication can be established with the pod for a preconfigured time a “Pump unreachable” alert will be raised. Pump unreachable alerts can be configured by going to the top right-hand side three-dot menu, selecting **Preferences**\ ➜\ **Local Alerts**\ ➜\ **Pump unreachable threshold [min]**. Recommended value is alerting after **120** minutes. ### Ayarları Dışa Aktarma Exporting **AAPS** settings enables you to restore all your settings, and maybe more importantly, all your Objectives. You may need to restore settings to the “last known working situation” or after uninstalling/reinstalling **AAPS** or in case of phone loss, reinstalling on the new phone. -Not: Aktif pod bilgileri, dışa aktarılan ayarlara dahildir. If you import an "old" exported file, your actual pod will "die". There is no other alternative. In some cases (like a _programmed_ phone change), you may need to use the exported file to restore **AAPS'** settings **while keeping the current active Pod**. In this case it is important to only use the recently exported settings file containing the pod currently active. +Note: The active pod information is included in the exported settings. If you import an "old" exported file, your actual pod will "die". There is no other alternative. In some cases (like a _programmed_ phone change), you may need to use the exported file to restore **AAPS'** settings **while keeping the current active Pod**. In this case it is important to only use the recently exported settings file containing the pod currently active. **It is good practice to do an export immediately after activating a pod**. This way you will always be able to restore the current active pod in case of a problem. For instance when moving to another backup phone. @@ -447,13 +453,13 @@ When importing settings with an active Pod, make sure the export was done with t ### Etkin olmayan bir pod durumunu içeren ayarları içe aktarma -Aktif olmayan bir pod verileri içeren ayarları içe aktarırken, AAPS onunla bağlanmaya çalışacak ve başarısız olacaktır. Bu durumda yeni bir Pod etkinleştiremezsiniz. +When importing settings containing data for a Pod that is no longer active, AAPS will try to connect with it, which will obviously fail. You can not activate a new Pod in this situation. -To remove the old pod session “try” to de-activate the Pod. Devre dışı bırakma başarısız olur. “Yeniden Dene”yi seçin. İkinci veya üçüncü denemeden sonra pod'u kaldırma seçeneğine sahip olacaksınız. Once the old pod is removed you will be able to activate a new pod. +To remove the old pod session “try” to de-activate the Pod. The de-activation will fail. Select “Retry”. After the second or third retry you will get the option to remove the pod. Once the old pod is removed you will be able to activate a new pod. ### AAPS'i yeniden yükleme -When uninstalling**AAPS** you will lose all your settings, objectives and the current Pod session. Bunları geri yüklemek için, yakın zamanda dışa aktarılmış bir ayar dosyanız olduğundan emin olun! +When uninstalling**AAPS** you will lose all your settings, objectives and the current Pod session. To restore them make sure you have a recent exported settings file available! When on an active Pod, make sure that you have an export for the current pod session or you will lose the currently active pod when importing older settings. @@ -467,7 +473,7 @@ When on an active Pod, make sure that you have an export for the current pod ses ### AAPS'i daha yeni bir sürüme güncelleme -Çoğu durumda, mevcut kurulumu kaldırmaya gerek yoktur. Yeni sürüm için kurulumu başlatarak “üzerine” kurulum yapabilirsiniz. Bu aktif bir Pod kullanırken de mümkündür. +In most cases there is no need to uninstall. You can do an “in-place” install by starting the installation for the new version. This is also possible when on an active Pod session. 1. Ayarlarınızı dışa aktarın. 2. Install the new **AAPS** version. @@ -477,7 +483,7 @@ When on an active Pod, make sure that you have an export for the current pod ses ### Omnipod sürücü uyarıları -Omnipod Dash sürücüsü **Giriş sekmesinde** çeşitli uyarılar sunmakla birlikte bunların çoğu bilgi amaçlıdır ve kapatılabilirken, bazıları da kullanıcıya tetiklenen uyarının nedenini çözmek için bir eylemde bulunmasını sağlar. Karşılaşabileceğiniz başlıca uyarıların bir özeti aşağıda listelenmiştir: +Please note that the Omnipod Dash driver presents a variety of unique alerts on the **Overview tab**, most of them are informational and can be dismissed while some provide the user with an action to take to resolve the cause of the triggered alert. A summary of the main alerts that you may encounter is listed below: * Aktif bir Pod oturumu algılanamadı. Bu uyarı, **ERTELE**'ye basılarak geçici olarak kapatılabilir, ancak yeni bir pod etkinleştirilmedikçe tetiklenmeye devam edecektir. Etkinleştirildiğinde bu uyarı otomatik olarak susacaktır. * Pod suspended Informational alert that pod has been suspended. diff --git a/docs/CROWDIN/tr/CompatiblePumps/OmnipodEros.md b/docs/CROWDIN/tr/CompatiblePumps/OmnipodEros.md index 97854d5e8fa8..2c1884ca2144 100644 --- a/docs/CROWDIN/tr/CompatiblePumps/OmnipodEros.md +++ b/docs/CROWDIN/tr/CompatiblePumps/OmnipodEros.md @@ -43,7 +43,7 @@ Bu talimatlar, yeni bir pod oturumu başlattığınızı varsayar; durum böyle **ÖNCE GÜVENLİK** - bir hatadan kurtulamayacağınız bir ortamda bu işlemi denemeyin (ekstra pod, insülin ve telefon cihazları olmazsa olmazdır). -**Omnipod PDM'niz, AAPS Omnipod sürücüsü podunuzu etkinleştirdikten sonra artık çalışmayacaktır**. Önceden Omnipod Eros Podunuz'a komutlar göndermek için Omnipod PDM'nizi kullanıyordunuz. Bir Omnipod Eros podu, yalnızca tek bir cihazın kendisine iletişim göndermesine izin verir. Podu başarıyla etkinleştiren cihaz, o andan itibaren onunla iletişim kurmasına izin verilen tek cihazdır. Bu AAPS Omnipod sürücüsü aracılığıyla RileyLink'inizle bir Omnipod Eros podunu etkinleştirdiğinizde, ** artık PDM'niz ile podunuzu kullanamayacağınız anlamına gelir**. RileyLink'li AAPS Omnipod sürücüsü artık bir nevi yeni PDM'niz olur. *Bu, PDM'nizi çöpe atmanız gerektiği anlamına GELMEZ, yedek olarak saklamanız şiddetle önerilir ve AAPS düzgün çalışmadığı acil durumlar için gereklidir.* +**Omnipod PDM'niz, AAPS Omnipod sürücüsü podunuzu etkinleştirdikten sonra artık çalışmayacaktır**. Önceden Omnipod Eros Podunuz'a komutlar göndermek için Omnipod PDM'nizi kullanıyordunuz. Bir Omnipod Eros podu, yalnızca tek bir cihazın kendisine iletişim göndermesine izin verir. The device that successfully activates the pod is the only device allowed to communicate with it from that point forward. Bu AAPS Omnipod sürücüsü aracılığıyla RileyLink'inizle bir Omnipod Eros podunu etkinleştirdiğinizde, ** artık PDM'niz ile podunuzu kullanamayacağınız anlamına gelir**. RileyLink'li AAPS Omnipod sürücüsü artık bir nevi yeni PDM'niz olur. *Bu, PDM'nizi çöpe atmanız gerektiği anlamına GELMEZ, yedek olarak saklamanız şiddetle önerilir ve AAPS düzgün çalışmadığı acil durumlar için gereklidir.* **Birden çok RileyLink yapılandırabilirsiniz, ancak bir seferde yalnızca bir seçili RileyLink bir podla iletişim kurabilir.** AAPS Omnipod sürücüsü, RileyLink yapılandırmasına birden çok RileyLink ekleme özelliğini destekler, ancak iletişim göndermek ve almak için kullanılmak üzere bir seferde yalnızca bir RileyLink seçilebilir. @@ -191,7 +191,7 @@ Bir podu etkinleştirmeden önce lütfen Omnipod ayarlarında RileyLink bağlant Normal şartlar altında toplam 80 saatlik pod kullanımı için, üç günlük (72 saat) pod kullanım ömrüne ilaveten, sona erme uyarısından sonra 8 saat daha çalışmalıdır. -Bir Podu devre dışı bırakmak (süre sonundan veya bir pod hatasından dolayı): +To deactivate a pod (either from expiration or from a pod failure): 1. **Omnipod (POD)** sekmesine gidin, **POD YNTM (1)** butonunu tıklayın, **pod yönetimi** ekranında **Pod'u Devre Dışı Bırak (2)** butonunu tıklayın. @@ -245,7 +245,7 @@ Etkin podu askıya alınmış duruma getirmek için bu komutu kullanın. Bu ask #### İnsülin İletimini Sürdür -İletimi askıya alınmış Pod'unuzun insülin iletimini yeniden başlatma talimatı vermek için bu komutu kullanın. Komut başarıyla işlendikten sonra, aktif bazal profildeki geçerli zamana dayalı mevcut bazal oranı kullanılarak normal insülin iletimi sürdürülecektir. Pod bolus, GBO ve SMB için komutları tekrar kabul edecektir. +Use this command to instruct the active, currently suspended pod to resume insulin delivery. Komut başarıyla işlendikten sonra, aktif bazal profildeki geçerli zamana dayalı mevcut bazal oranı kullanılarak normal insülin iletimi sürdürülecektir. Pod bolus, GBO ve SMB için komutları tekrar kabul edecektir. 1. **Omnipod (POD)** sekmesine gidin ve **Pod durumu (1)** satırında **ASKIYA ALINDI** mesajının görünmesi gerekir, ardından mevcut podun normal insülin iletimini sürdürmesi talimatını vermek için **İLETİME DEVAM ET (2)** butonuna basın. **Pod durumu (3)** alanında, RileyLink'in aktif olarak askıya alınan pod'a komutu gönderdiğini belirten bir **İLETİME DEVAM ET** mesajı görüntülenecektir. @@ -716,11 +716,11 @@ Pil seviyesi bildirimi, OrangeLink, EmaLink veya DiaLink gibi pod iletişim ciha ### Pod Hataları -Pod'larda, kendisiyle ilgili donanım sorunları da dahil olmak üzere çeşitli sorunlar nedeniyle ara sıra hatalar olabiliyor. AAPS onaylanmış bir kullanım şekli olmadığından, bunları Insulet'e bildirmemek en iyi seçenektir. Nedeni belirlemeye yardımcı olması için [burada](https://github.com/openaps/openomni/wiki/Fault-event-codes) hata kodlarının bir listesi bulunmaktadır. +Pods fail occasionally due to a variety of issues, including hardware issues with the Pod itself. It is best practice not to call these into Insulet, since AAPS is not an approved use case. Nedeni belirlemeye yardımcı olması için [burada](https://github.com/openaps/openomni/wiki/Fault-event-codes) hata kodlarının bir listesi bulunmaktadır. ### 49 numaralı Pod hatasını önleme -Bu hata bir komut için yanlış bir pod durumu veya bir insülin iletim komutu sırasındaki bir hata ile ilgilidir. Nightscout client kullanıcılarının, olası arızaları önlemek için **Konfigürasyon ayarları**➜**Genel**➜**NSClient**➜**dişli çark**➜**Gelişmiş Ayarlar** altında *yalnızca yükleme (Senkronizasyonu devre dışı bırak)* seçeneğini etkinleştirmelerini öneririz. +This failure is related to an incorrect pod state for a command or an error during an insulin delivery command. Nightscout client kullanıcılarının, olası arızaları önlemek için **Konfigürasyon ayarları**➜**Genel**➜**NSClient**➜**dişli çark**➜**Gelişmiş Ayarlar** altında *yalnızca yükleme (Senkronizasyonu devre dışı bırak)* seçeneğini etkinleştirmelerini öneririz. ### Pompaya Ulaşılamıyor Uyarıları @@ -739,7 +739,7 @@ Ayarları içe aktarmanın, eski bir Pod durumunu içe aktarma olanağına sahip ### Omnipod sürücü uyarıları -Omnipod ürücüsü **Giriş sekmesinde** çeşitli uyarılar sunmakla birlikte bunların çoğu bilgi amaçlıdır ve kapatılabilirken, bazıları da kullanıcıya tetiklenen uyarının nedenini çözmek için bir eylemde bulunmasını sağlar. Karşılaşabileceğiniz başlıca uyarıların bir özeti aşağıda listelenmiştir: +Omnipod ürücüsü **Giriş sekmesinde** çeşitli uyarılar sunmakla birlikte bunların çoğu bilgi amaçlıdır ve kapatılabilirken, bazıları da kullanıcıya tetiklenen uyarının nedenini çözmek için bir eylemde bulunmasını sağlar. A summary of the main alerts that you may encounter is listed below: #### Aktif Pod Yok diff --git a/docs/CROWDIN/tr/GettingHelp/GeneralTroubleshooting.md b/docs/CROWDIN/tr/GettingHelp/GeneralTroubleshooting.md index 86361c8ca98b..9d1be16340f6 100644 --- a/docs/CROWDIN/tr/GettingHelp/GeneralTroubleshooting.md +++ b/docs/CROWDIN/tr/GettingHelp/GeneralTroubleshooting.md @@ -37,14 +37,37 @@ Ignore it: More details, Install anyway. * [SMS Komutları](#SMSCommands-troubleshooting) -### Sık bluetooth bağlantı sorunları +### Frequent Bluetooth connection problems -Bu, çeşitli pompalarda olabilir. AAPS'i pil optimizasyonunun dışında tutmanın yanı sıra, sistem bluetooth uygulamasını da pil optimizasyonunun dışında tutabilirsiniz. Bu, bazı durumlarda yardımcı olabilir. Kullandığınız telefona bağlı olarak, bluetooth ayarları farklı olacaktır. +#### Android 15 + +```{warning} +Developers are working on this issue impacting **AAPS** on some Samsung and Pixel phones. +``` + +After upgrading Android or moving to a recent phone, **AAPS** frequently loses Bluetooth connection to the pump. The problem disappears temporarily when restarting the phone. If the phone runs Android 15, you can try to enable the following: + +1) **Open preferences** by clicking the three-dot menu on the top right side of the home screen. + + +![Open preferences](../images/Pref2020_Open2.png) + +2. Scroll down and open the **Confirmation beeps** / **Advanced** submenu. Enable **Bond BT device on Android 15+**. + + ![BondBT](../images/troubleshooting/BondBT.png) + +3. If the pump asks for a pairing request, accept it. + +4. Restart your phone. + +#### Battery optimization + +Bu, çeşitli pompalarda olabilir. Apart from excluding AAPS from any battery optimization, you can also exclude the system Bluetooth app from battery optimization. Bu, bazı durumlarda yardımcı olabilir. Depending on the phone you use, you will find the Bluetooth app differently. Bunları belirli android telefonlarda nasıl bulacağınıza dair örnekler aşağıda verilmiştir. -#### Pixel telefonlar (stok android) +##### Pixel phones (stock Android) * Android ayarlarına gidin, "Uygulamalar" ı seçin. @@ -67,7 +90,7 @@ Bunları belirli android telefonlarda nasıl bulacağınıza dair örnekler aşa ![BT Pil optimizasyonu](../images/troubleshooting/pixel/04_btunrestricted.png) -#### Samsung telefonlar +##### Samsung telefonlar * Android ayarlarına gidin, "Uygulamalar" ı seçin diff --git a/docs/CROWDIN/tr/images/troubleshooting/BondBT.png b/docs/CROWDIN/tr/images/troubleshooting/BondBT.png new file mode 100644 index 000000000000..96b2fb272d90 Binary files /dev/null and b/docs/CROWDIN/tr/images/troubleshooting/BondBT.png differ diff --git a/docs/CROWDIN/tr/images/troubleshooting/samsung/01_BondBT_20250526.png b/docs/CROWDIN/tr/images/troubleshooting/samsung/01_BondBT_20250526.png new file mode 100644 index 000000000000..74c3525959ed Binary files /dev/null and b/docs/CROWDIN/tr/images/troubleshooting/samsung/01_BondBT_20250526.png differ diff --git a/docs/CROWDIN/tr/images/troubleshooting/samsung/02_BondBT_20250526.png b/docs/CROWDIN/tr/images/troubleshooting/samsung/02_BondBT_20250526.png new file mode 100644 index 000000000000..444013b29146 Binary files /dev/null and b/docs/CROWDIN/tr/images/troubleshooting/samsung/02_BondBT_20250526.png differ diff --git a/docs/CROWDIN/tr/images/troubleshooting/samsung/03_BondBT_20250526.png b/docs/CROWDIN/tr/images/troubleshooting/samsung/03_BondBT_20250526.png new file mode 100644 index 000000000000..9caa7a484581 Binary files /dev/null and b/docs/CROWDIN/tr/images/troubleshooting/samsung/03_BondBT_20250526.png differ diff --git a/docs/CROWDIN/tr/images/troubleshooting/samsung/04_BondBT_20250526.png b/docs/CROWDIN/tr/images/troubleshooting/samsung/04_BondBT_20250526.png new file mode 100644 index 000000000000..b25c1469f58e Binary files /dev/null and b/docs/CROWDIN/tr/images/troubleshooting/samsung/04_BondBT_20250526.png differ diff --git a/docs/CROWDIN/zh_CN/CompatiblePumps/MedtrumNano.md b/docs/CROWDIN/zh_CN/CompatiblePumps/MedtrumNano.md index 0ae1968d1aa5..b41ab6c8be3d 100644 --- a/docs/CROWDIN/zh_CN/CompatiblePumps/MedtrumNano.md +++ b/docs/CROWDIN/zh_CN/CompatiblePumps/MedtrumNano.md @@ -39,9 +39,9 @@ orphan: true **当未连接AAPS时，您的胰岛素泵不会停止输注胰岛素** 胰岛素泵将按照当前使用方案中设定的基础率持续输注。 只要AAPS处于运行状态，就会发送最长持续120分钟的临时基础率指令。 若因某些原因（如因胰岛素泵与手机距离过远导致通信中断）泵体未能接收到新指令，临时基础率结束后将自动恢复为泵体预设的基础率。 -**AAPS不支持30分钟基础率方案。****AAPS配置方案不支持30分钟基础率时间间隔。**若您初次使用AAPS并首次设置基础率方案，请注意系统不支持半点起始的基础率设置，您需要将基础率方案调整为整点起始。 例如，若您设置了09:30开始、持续2小时至11:30结束的1.1单位基础率，该设置将无法生效。 您需要将这个1.1单位的基础率时间段调整为9:00-11:00或10:00-12:00。 尽管移宇胰岛素泵硬件本身支持30分钟基础率间隔设置，但AAPS当前算法尚无法兼容此类设置。 +**AAPS不支持30分钟基础率方案。****AAPS配置方案不支持30分钟基础率时间间隔。**若您初次使用AAPS并首次设置基础率方案，请注意系统不支持半点起始的基础率设置，您需要将基础率方案调整为整点起始。 例如，若您设置了09:30开始、持续2小时至11:30结束的1.1单位基础率，该设置将无法生效。 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. 尽管移宇胰岛素泵硬件本身支持30分钟基础率间隔设置，但AAPS当前算法尚无法兼容此类设置。 -**AAPS不支持0U/h基础率方案设置**。虽然移宇胰岛素泵确实支持零基础率，但AAPS需基于基础率倍数进行自动化治疗计算，因此无法兼容零基础率设置。 可通过"断开泵连接"功能，或结合停用循环/临时基础率与暂停循环/临时基础率功能，实现临时零基础率设置。 +**AAPS不支持0U/h基础率方案设置**。虽然移宇胰岛素泵确实支持零基础率，但AAPS需基于基础率倍数进行自动化治疗计算，因此无法兼容零基础率设置。 A temporary zero basal rate can be achieved through the "Disconnect pump" function or through a combination of Disable Loop/Temp Basal Rate or Suspend Loop/Temp Basal Rate. ## 设置 diff --git a/docs/CROWDIN/zh_CN/CompatiblePumps/OmnipodDASH.md b/docs/CROWDIN/zh_CN/CompatiblePumps/OmnipodDASH.md index f7c26583a642..636e257991c0 100644 --- a/docs/CROWDIN/zh_CN/CompatiblePumps/OmnipodDASH.md +++ b/docs/CROWDIN/zh_CN/CompatiblePumps/OmnipodDASH.md @@ -18,7 +18,13 @@ orphan: true * 在储药器激活时，**AAPS** 将自动搜寻并连接新的 DASH 储药器。 * 预期连接范围：5-10米（实际效果可能因环境而异）。 -警告：目前收到关于以下组合的蓝牙连接问题报告：**AAPS** / DASH / Android 15。 除非用户已查阅以下[**列表**](https://docs.google.com/spreadsheets/u/1/d/e/2PACX-1vScCNaIguEZVTVFAgpv1kXHdsHl3fs6xT6RB2Z1CeVJ561AvvqGwxMhlmSHk4J056gMCAQE02sAWJvT/pubhtml?gid=683363241&single=true)并确认其手机不在已知问题报告范围内，否则不应将**AAPS**与Android 15和DASH组合使用。 **AAPS**目前正在努力解决该问题。 +```{admonition} Android 15 +:class: warning + +There are currently reported Bluetooth connection issues with the following combination of **AAPS**: DASH + Android 15. +Please refrain from upgrading your phone to Android 15 unless you have checked the following [**list**](https://docs.google.com/spreadsheets/u/1/d/e/2PACX-1vScCNaIguEZVTVFAgpv1kXHdsHl3fs6xT6RB2Z1CeVJ561AvvqGwxMhlmSHk4J056gMCAQE02sAWJvT/pubhtml?gid=683363241&single=true) and verified that your phone is not a known reported issue. +If you experience frequent disconnection; try to enable Bond BT as described in: [**Bluetooth Issues**](../GettingHelp/GeneralTroubleshooting.md). +``` ## 硬件/软件要求 @@ -31,59 +37,59 @@ orphan: true - **使用[**构建APK**](../SettingUpAaps/BuildingAaps.md)说明构建并安装AAPS 3.0或更高版本**。 * [**持续血糖监测仪（CGM）**](../Getting-Started/CompatiblesCgms.md) -以下说明将指导您如何激活新的储药器会话。 请等待当前储药器会话接近到期时，再尝试将**AAPS**与新储药器连接。 储药器一旦被取消便无法重复使用，断开连接后将永久失效。 +The instructions below explain how to activate a new pod session. Wait to close to expiry of a current pod session before trying to connect **AAPS** with a new pod. Once a pod is is cancelled it cannot reused and the disconnection will be final. ## 开始前的准备工作 -**安全第一** - 首次尝试将**AAPS**连接至储药器时，必须确保备有额外的储药器、胰岛素及通讯设备。 +**SAFETY FIRST** - you should not try to connect **AAPS** to a pod for the first time without having access to extra pods, insulin, and phone devices are a must have. -**当AAPS的Dash驱动激活您的储药器后，Omnipod Dash PDM将不再需要。**此前用户可能需要通过PDM向DASH发送指令。 DASH 仅允许单一设备与其通信并发送指令。 成功激活储药器的设备将成为此后唯一获准与其通信的设备。 这意味着当您通过**AAPS**用安卓手机激活DASH后，**该储药器将无法再与您的PDM配合使用**。 您安卓手机中的**AAPS** Dash驱动现已作为您的PDM使用。 +**Your Omnipod Dash PDM will become redundant after the AAPS Dash driver activates your pod.** Previously a user may have operated a PDM to send commands to your DASH. A DASH will only faciiliate a single device to send commands to communicate with it. The device that successfully activates the pod is the only device allowed to communicate with it from that point forward. This means that once you activate a DASH with your Android phone through the **AAPS**, **you will no longer be able to use your PDM with that pod**. The **AAPS** Dash driver in your Android phone is now your acting PDM. -*这并不意味着您应该丢弃PDM，建议将其保留作为备用设备以应对紧急情况，例如手机丢失或AAPS运行异常时使用。* +*This does NOT mean you should throw away your PDM, it is recommended to keep it around as a backup and for emergencies, for instance when your phone gets lost or AAPS is not working correctly.* -**储药器在未连接AAPS时不会停止胰岛素输注**。 储药器激活时会根据当前生效的**配置文件**预设基础率参数。 只要**AAPS**正常运行，它就会发送最长持续120分钟的基础率指令。 当储药器因某些原因（如因储药器与手机距离过远导致通信中断）未能接收到新指令时，将自动切换至预设基础率模式运行。 +**Your pod will not stop delivering insulin when it is not connected to AAPS**. Default basal rates are programmed on the pod on activation as defined in the current active **Profile**. As long as **AAPS** is operational it will send basal rate commands that run for a maximum of 120 minutes. 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. -**AAPS配置文件不支持30分钟基础率时间框架。** 如果您是**AAPS**的新用户并首次设置基础率**配置文件**，请注意不支持以半小时为单位的基础率设置，仅支持整点设置。 例如，若您设有从09:30开始、持续2小时至11:30结束的1.1单位基础率，则无法在**AAPS**中完全复制该设置。 您需要将这个1.1单位的基础率时间段调整为9:00-11:00或10:00-12:00。 虽然DASH硬件本身支持30分钟基础率**配置文件**增量设置，但**AAPS**目前并不支持此功能。 +**AAPS Profile does not support a 30 minute basal rate time frame** If you are new to **AAPS** and are setting up your basal rate **Profile** for the first time, please be aware that basal rates starting on a half-hour basis are not supported, and programmes on an hourly basis. For example, 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 im **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 support this feature. -**AAPS不支持0U/h的基础率配置.** 虽然DASH硬件支持零基础率设置，但由于**AAPS**依赖用户**配置文件**基础率的倍数进行自动治疗决策，系统无法在零基础率状态下运行。 可通过"断开泵连接"功能，或结合停用循环/临时基础率与暂停循环/临时基础率功能，实现临时零基础率设置。 **AAPS**允许的最低基础率为0.05单位/小时。 +**0U/h profile basal rates are NOT supported in AAPS** While the DASH does support a zero basal rate, since **AAPS** uses multiples of the user's **Profile** basal rate to determine automated treatment; it cannot function with a zero basal rate. A temporary zero basal rate can be achieved through the "Disconnect pump" function or through a combination of Disable Loop/Temp Basal Rate or Suspend Loop/Temp Basal Rate. The lowest basal rate allowed in **AAPS** is 0.05U/h. ## 在AAPS中选择Dash -有两种方式： +There are **two ways**: ### 方式一：全新安装 -首次安装**AAPS**时，**设置向导**将引导新用户了解**AAPS**的关键功能和安装要求。 当进入泵选择环节时，请选择“DASH”。 +When installing **AAPS** for the first time, the **Setup Wizard** will guide new users through key features and installation requirements for **AAPS**. Select “DASH” when you reach Pump selection. ![Enable_Dash_1](../images/DASH_images/Enable_Dash/Enable_Dash_1.png) -若不确定，您也可先选择"虚拟泵"，待**AAPS**设置完成后再切换至"DASH"（参见选项2）。 +When in doubt you can also select “Virtual Pump” and select “DASH” later, after setting up **AAPS** (see option 2). ### 选项2：配置构建器 -在现有安装中，您可以通过配置构建器选择**DASH**泵： +On an existing installation you can select the **DASH** pump from the Config builder: -点击左上角**汉堡菜单**，依次选择**配置构建器(1)** ➜ **胰岛素泵** ➜ **Dash** ➜ 通过选中**Dash(2)**单选按钮进入**设置齿轮图标(3)**。 +On the top-left hand corner **hamburger menu** select **Config Builder (1)**\ ➜\ **Pump**\ ➜\ **Dash**\ ➜\ **Settings Gear (3)** by selecting the **radio button (2)** titled **Dash**. -勾选**设置齿轮图标(3)**旁的**复选框(4)**后，DASH菜单将作为标签页显示在**AAPS**界面中，标题为**DASH**。 勾选此选项后，您在使用**AAPS**时将能更便捷地调用DASH指令功能。 +Selecting the **checkbox (4)** next to the **Settings Gear (3)** will allow the DASH menu to be displayed as a tab in the **AAPS** interface titled **DASH**. Checking this box will facilitate your access to the DASH commands when using **AAPS**. -**注意：** 您可在本文档的DASH设置章节找到更快捷访问[**Dash设置**](#dash-settings)的方法。 +**NOTE:** A faster way to access the [**Dash settings**](#dash-settings) can be found below in the DASH settings section of this document. ![Enable_Dash_3](../images/DASH_images/Enable_Dash/Enable_Dash_3.png) ### Omnipod驱动选择验证 -要确认您已在**AAPS**中选择了DASH，若您已勾选复选框(4)，从**总览**标签页**向左滑动**，即可在**AAPS**界面中看到新增的**DASH**标签页。 若未勾选此选项，您仍可在左上角汉堡菜单中找到DASH标签页。 +To verify that you have selected the DASH in **AAPS**, if you have checked the box (4), **swipe to the left** from the **Overview** tab, where you will now see a **DASH** tab on **AAPS**. If this box is left unchecked, you’ll find the DASH tab in the hamburger menu upper left. ![Enable_Dash_4](../images/DASH_images/Enable_Dash/Enable_Dash_4.jpg) ## Dash配置 -请**向左滑动**至**DASH**标签页，您将在此管理所有储药器功能（部分功能需在储药器激活会话中才会启用或显示）： +Please **swipe left** to the **DASH** tab where you will be able to manage all pod functions (some of these functions are not enabled or visible without an active pod session): -![Refresh_LOGO](../images/DASH_images/Refresh_LOGO.png) "刷新"（刷新储药器连接状态，并可在储药器发出警报时进行消音操作） +![Refresh_LOGO](../images/DASH_images/Refresh_LOGO.png) 'Refresh' pod connectivity and status, be able to silence pod alarms when the pod beeps -![POD_MGMT_LOGO](../images/DASH_images/POD_MGMT_LOGO.png) "储药器管理"（激活、停用、测试蜂鸣音、查看使用记录） +![POD_MGMT_LOGO](../images/DASH_images/POD_MGMT_LOGO.png) 'Pod Management' (Activate, Deactivate, Play test beep, and Pod history) ### 激活Pod @@ -98,9 +104,9 @@ orphan: true ![Activate_Pod_3](../images/DASH_images/Activate_Pod/Activate_Pod_3.png) ![Activate_Pod_4](../images/DASH_images/Activate_Pod/Activate_Pod_4.jpg) -确保新储药器与运行**AAPS**的手机保持近距离，然后点击**下一步**按钮。 +Ensure that the new pod and the phone running **AAPS** are within close proximity of each other and click the **Next** button. -**注意**：若弹出错误提示_"未找到可用的待激活储药器"_（这种情况可能发生），请勿惊慌。 点击**重试**按钮。 在大多数情况下，激活程序将能继续顺利完成。 +**NOTE**: if the error message below pops up _'Could not find an available pod for activation'_ (this can happen), do not panic. Click on the **Retry** button. In most situations activation will continue successfully. ![Activate_Pod_3](../images/DASH_images/Activate_pod_error.png) @@ -140,16 +146,16 @@ orphan: true ​ ![Activate_Pod_15](../images/DASH_images/Activate_Pod/Activate_Pod_15.jpg) -建议在激活储药器后导出设置。 应在每次更换储药器时导出设置，并每月将导出文件备份至云存储。 参见[**导出设置文档**](../Maintenance/ExportImportSettings.md)。 +It is good practice to export settings AFTER activating the pod. Export settings should be done at each pod change and once a month, copy the exported file to your internet drive. see [**Export settings Doc**](../Maintenance/ExportImportSettings.md). (OmnipodDASH-deactivate-pod)= ### 停用Pod -正常情况下，储药器标准使用周期为3天（72小时），在触发过期警告后仍可继续使用8小时，总使用时长可达80小时。 +Under normal circumstances, the expected lifetime of a pod is three days (72 hours) and an additional 8 hours after the pod expiration warning for a total of 80 hours of pod usage. -要停用储药器（无论是因到期还是故障）： +To deactivate a pod (either from expiration or from a pod failure): 1. 进入**DASH**标签页，点击**储药器管理(1)**按钮，在**储药器管理**界面点击**停用储药器(2)**按钮。 @@ -180,9 +186,9 @@ orphan: true ### 恢复胰岛素输注 -**注意**：在执行**配置文件切换**时，DASH必须先暂停输注才能设置新的基础**配置文件**，因为输注功能可能被暂停。 详情请参阅故障排除章节中的[**输注暂停**](#delivery-suspended)部分。 +**Note**: During **Profile Switches**, DASH must suspend delivery before setting the new basal **Profile** as delivery can be suspended. Read [**Delivery suspended**](#delivery-suspended) in the troubleshooting section for more details. -此指令用于命令当前暂停中的储药器恢复胰岛素输注。 指令成功执行后，系统将根据当前激活的基础**配置文件**，按当前时间对应的基础率恢复胰岛素正常输注。 储药器将重新接受大剂量注射、**临时基础率**和**超微大剂量**指令。 +Use this command to instruct the active, currently suspended pod to resume insulin delivery. After the command is successfully processed, insulin will resume normal delivery using the current basal rate based on the current time from the active basal **Profile**. The pod will again accept commands for bolus, **TBR**, and **SMB**. 1. 请进入**DASH**标签页，确认**储药器状态(1)**字段显示为**已暂停**，然后点击**恢复输注(2)**按钮启动流程，指示当前储药器恢复正常胰岛素输注。 **恢复输注**信息将显示在**储药器状态(3)**字段中。 @@ -198,9 +204,9 @@ orphan: true ### 静音储药器警报 -*注意 - 仅当触发储药器过期或低药量警报时，**DASH**标签页才会显示静音警报按钮。 若未显示静音警报按钮但储药器发出提示音，请尝试"刷新储药器状态"。* +*NOTE - The SILENCE ALERTS button is only available on the **DASH** tab when the pod expiration or low reservoir alert has been triggered. If the SILENCE ALERTS button is not visible and you hear beep sounds from the pod, try to 'Refresh pod status'.* -以下流程将说明当储药器使用时间接近72小时（3天）有效期前的警告时限时，如何确认并消除储药器提示音。 该警告时限由**关机前小时数**的Dash警报设置定义。 储药器最长使用时限为80小时（3天8小时），但Insulet建议不要超过72小时（3天）的标准周期。 +The process below will show you how to acknowledge and dismiss pod beeps when the active pod time reaches the warning time limit before the pod expiration of 72 hours (3 days). This warning time limit is defined in the **Hours before shutdown** Dash alerts setting. The maximum life of a pod is 80 hours (3 days 8 hours), however Insulet recommends not exceeding the 72 hours (3 days) limit. 1. 当达到设定的**关机前小时数**警告时限时，储药器将发出提示音，提醒您其即将到期，需要尽快更换储药器。 您可在**DASH**标签页进行确认：**储药器到期时间：(1)**字段会显示储药器失效的具体时间（激活后72小时），超过此时限后该文本将变为**红色**。 在**使用中储药器警报(2)**字段下会显示状态信息**储药器即将到期**。 同时会触发显示**静音警报(3)**按钮。 @@ -221,11 +227,11 @@ orphan: true ### 查看 Pod 历史 -本节说明如何查看使用中储药器的历史记录，并按不同操作类别进行筛选。 储药器历史工具可让您查看当前使用中储药器在其3天（72-80小时）使用周期内执行的操作及结果记录。 +This section explains how to review your active pod history and filter by different action categories. The pod history tool allows you to view the actions and results committed to your currently active pod during its three days (72 - 80 hours) life. -此功能有助于核验已发送至储药器的大剂量注射、临时基础率和基础率指令。 其余分类有助于故障排除，并确定导致故障发生的事件顺序。 +This feature is helpful in verifying boluses, TBRs and basal commands that were sent to the pod. The remaining categories are useful for troubleshooting issues and determining the order of events that occurred leading up to a failure. -*注意：* **仅最后一条指令可能显示不确定状态**。 新指令*将不会被发送*，直到**最后一条"不确定"指令变为"已确认"或"已拒绝"**。 解决不确定指令的方法是执行**'刷新储药器状态'**操作。 +*NOTE:* **Only the last command can be uncertain**. New commands *will not be sent* until the **last 'uncertain' command becomes 'confirmed' or 'denied'**. The way to 'fix' uncertain commands is to **'refresh pod status'**. 1. 请进入**DASH**标签页，点击**储药器管理(1)**按钮进入**储药器管理**菜单，然后点击**储药器历史(2)**按钮访问历史记录界面。 @@ -246,9 +252,9 @@ orphan: true ## DASH标签页 -以下说明主AAPS界面中**DASH**标签页的布局及图标与状态字段的含义。 +Below is an explanation of the layout and meaning of the icons and status fields on the **DASH** tab in the main AAPS interface. -*注意：若**DASH**标签页状态字段中任何信息显示为（不确定），则需点击刷新按钮以清除该状态并更新储药器状态。* +*NOTE: If any message in the **DASH** tab status fields report (uncertain), then you will need to press the Refresh button to clear it and refresh the pod status.* ![DASH_Tab_1](../images/DASH_images/DASH_Tab/DASH_Tab_1.png) @@ -283,23 +289,23 @@ orphan: true ### 按钮 -![Refresh_Icon](../images/DASH_images/Refresh_LOGO.png) ：向活动储药器发送刷新指令以更新通信状态。 +![Refresh_Icon](../images/DASH_images/Refresh_LOGO.png) : Sends a refresh command to the active pod to update communication. * 用于刷新储药器状态并清除显示（不确定）的状态字段。 * 更多信息请参阅下文"故障排除"章节。 -![POD_MGMT_Icon](../images/DASH_images/POD_MGMT_LOGO.png) ：跳转至储药器管理菜单。 +![POD_MGMT_Icon](../images/DASH_images/POD_MGMT_LOGO.png) : Navigates to the Pod management menu. -![ack_alert_logo](../images/DASH_images/ack_alert_logo.png) ：按下后将禁用储药器警报提示音和通知（如到期提醒、低药量警报等）。 +![ack_alert_logo](../images/DASH_images/ack_alert_logo.png) : When pressed this will disable the pod alerts beeps and notifications (expiry, low reservoir..). * 该按钮仅在储药器时间超过到期警告时间后显示。 * 成功取消后，该图标将不再显示。 -![RESUME_Icon](../images/DASH_images/DASH_tab_icons/RESUME_Icon.png) ：恢复当前活动储药器中暂停的胰岛素输注。 +![RESUME_Icon](../images/DASH_images/DASH_tab_icons/RESUME_Icon.png) : Resumes the currently suspended insulin delivery in the active pod. ### Pod 管理菜单 -以下是**储药器管理**菜单中图标的含义，该菜单可通过在**DASH**标签页按下**储药器管理(1)**按钮进入。 +Below is the meaning of the icons on the **Pod Management** menu accessed by pressing **POD MGMT (1)** button from the **DASH** tab. ![DASH_Tab_2](../images/DASH_images/Deactivate_Pod/Deactivate_Pod_1.jpg) @@ -314,25 +320,25 @@ orphan: true ## DASH设置 -DASH驱动程序设置可通过左上角**汉堡菜单**中的**配置构建器(1)**→**胰岛素泵**→**DASH**→**设置齿轮图标(3)**进行配置，选择标有**DASH**的**单选按钮(2)**即可。 勾选**设置齿轮图标(3)**旁的**复选框(4)**，即可在**AAPS**界面中将DASH菜单显示为名为**DASH**的标签页。 +The Dash driver settings are configurable from the top-left hand corner **hamburger menu** under **Config Builder (1)**\ ➜\ **Pump**\ ➜\ **Dash**\ ➜\ **Settings Gear (3)** by selecting the **radio button (2)** titled **Dash**. Selecting the **checkbox (4)** next to the **Settings Gear (3)** will allow the Dash menu to be displayed as a tab in the **AAPS** interface titled **DASH**. ![Dash_settings_1](../images/DASH_images/Enable_Dash/Enable_Dash_3.png) -**注意：** 访问**DASH设置**的快捷方式是通过**DASH**标签页右上角的**三点菜单(1)**，然后从下拉菜单中选择**DASH偏好设置(2)**。 +**NOTE:** A faster way to access the **Dash settings** is by accessing the **3 dot menu (1)** in the upper right hand corner of the **DASH** tab and selecting **Dash preferences (2)** from the dropdown menu. ![Dash_settings_3](../images/DASH_images/Dash_settings/Dash_settings_3.png) -以下是设置分组列表，您可通过切换开关启用或禁用下文所述的大多数选项： +The settings groups are listed below; you can enable or disable via a toggle switch for most entries described below: -*注：带星号(*)表示默认启用该设置。* +*NOTE: An asterisk (\*) denotes the default setting is enabled.* ### 确认提示音 ![Dash_settings_4](../images/DASH_images/Dash_settings/Dash_settings_4.jpg) -提供储药器对大剂量注射、基础率、超微大剂量(SMB)和临时基础率(TBR)输送及变更的确认提示音。 +Provides confirmation beeps from the pod for bolus, basal, SMB, and TBR delivery and changes. * **启用大剂量提示音：** 控制大剂量输注时是否发出确认提示音。 * **启用基础率提示音：** 控制设置新基础率、取消活动基础率或变更当前基础率时是否发出确认提示音。 @@ -343,9 +349,9 @@ DASH驱动程序设置可通过左上角**汉堡菜单**中的**配置构建器( ![Dash_settings_5](../images/DASH_images/Dash_settings/Dash_settings_5.jpg) -当储药器达到过期、关机或根据设定阈值单位检测到低药量时，提供**AAPS**警报提示。 +Provides **AAPS** alerts for pod expiration, shutdown, low reservoir based on the defined threshold units. -*请注意：自警报触发后与储药器首次通信时，AAPS将始终针对任何警报发出通知。 除非启用"自动确认储药器警报"功能，否则仅消除通知并不会消除警报状态。 要手动消除警报，必须访问**DASH**标签页并点击**静音警报按钮**。* +*Note an AAPS notification will ALWAYS be issued for any alert after the initial communication with the pod since the alert was triggered. Dismissing the notification will NOT dismiss the alert UNLESS automatically acknowledge Pod alerts is enabled. To MANUALLY dismiss the alert you must visit the **DASH** tab and press the **Silence ALERTS button**.* * **启用过期提醒：** 控制是否在储药器达到设定的关机前小时数时触发过期提醒。 * **关机前小时数：** 设定活动储药器关机前触发过期提醒警报的小时数。 @@ -356,9 +362,9 @@ DASH驱动程序设置可通过左上角**汉堡菜单**中的**配置构建器( ![Dash_settings_6](../images/DASH_images/Dash_settings/Dash_settings_6.jpg) -通知设置部分允许用户选择偏好的通知方式和手机提示音，用于在临时基础率(TBR)、超微大剂量(SMB)、大剂量注射或输注暂停事件是否成功执行存在不确定性时发出提醒。 +The Notification section allows the user to so select their preferred notifications and audible phone alerts when it is uncertain if TBR, SMB, or bolus, and delivery suspended events were successful. -*注：这些仅为手机通知，不会触发储药器声音提示。* +*NOTE: These are notifications only, no audible beep alerts are made.* * **启用临时基础率不确定通知提示音：** 当**AAPS**无法确认临时基础率(TBR)是否成功设置时，控制是否触发声音警报及视觉通知。 * **启用超微大剂量不确定通知提示音：** 当**AAPS**无法确认超微大剂量(SMB)是否成功输注时，控制是否触发声音警报及视觉通知。 @@ -367,7 +373,7 @@ DASH驱动程序设置可通过左上角**汉堡菜单**中的**配置构建器( ## 操作 (ACT) 标签页 -该标签页在**AAPS**主文档中已有详细说明，但其中部分条目专门体现了DASH与管路泵的区别特性，特别是在更换新储药器后的操作流程方面。 +This tab is well documented in the main**AAPS**documentation but there are a few items on this tab that are specific to how the DASH differs from tube based pumps, especially after the processes of applying a new pod. 1. 请前往**AAPS**主界面中的**操作(ACT)**标签页。 @@ -377,14 +383,14 @@ DASH驱动程序设置可通过左上角**汉堡菜单**中的**配置构建器( ### 余量水平 -**胰岛素储药量** +**Insulin Level** -显示的胰岛素储药量为DASH报告的药量。 但储药器仅在剩余药量低于50单位时才会报告实际胰岛素储药量。 在此之前将始终显示"高于50单位"。 报告数值并不精确：当储药器显示"空"时，多数情况下储药器内仍会残留若干单位的胰岛素。 DASH概览标签页将显示如下内容： +Insulin level displayed is the amount reported by DASH. However, the pod only reports the actual insulin reservoir level when it is below 50 units. Until then “Above 50 units” will be displayed. The amount reported is not exact: when the pod reports ‘empty’ in most cases the reservoir will still have some additional units of insulin left. The DASH overview tab will display as described the below: * **高于50单位** - 储药器报告当前药量超过50单位。 * **低于50单位** - 储药器报告的剩余胰岛素实际药量。 -补充说明： +Additional note: * **短信查询** - 短信回复将返回实际数值或"50+单位" * **Nightscout** - 当药量超过50单位时，会向Nightscout上传50的数值（14.07及更早版本）。 较新版本在药量超过50单位时将报告"50+"的数值。 @@ -402,43 +408,43 @@ DASH驱动程序设置可通过左上角**汉堡菜单**中的**配置构建器( - 若**AAPS**自动恢复输注失败（当储药器无法连接、静音等情况发生时），储药器将每分钟发出4次蜂鸣、持续3分钟；若暂停状态超过20分钟仍未恢复，则每15分钟重复此警报模式。 * 对于未确认的指令，"刷新储药器状态"操作可予以确认或否决。 -**注意：**当听到储药器发出蜂鸣声时，切勿未经查看手机就假定输注会继续——输注可能仍处于暂停状态，**因此必须进行检查！** +**Note:** When you hear beeps from the pod, do not assume that delivery will continue without checking the phone, delivery might stay suspended, **so you need to check !** ### Pod 故障 -储药器偶尔会因各种问题发生故障，包括储药器自身的硬件问题。 最佳做法是不要向Insulet公司报修，因为AAPS并非官方认可的使用方案。 故障代码列表可[**在此查阅**](https://github.com/openaps/openomni/wiki/Fault-event-codes)以帮助判断故障原因。 +Pods fail occasionally due to a variety of issues, including hardware issues with the Pod itself. It is best practice not to call these into Insulet, since AAPS is not an approved use case. A list of fault codes can be [**found here**](https://github.com/openaps/openomni/wiki/Fault-event-codes) to help determine the cause. ### 预防49号储药器故障 -该故障与指令对应的储药器状态错误或胰岛素输注指令执行出错有关。 此时驱动程序和储药器对实际状态的判断出现分歧。 出于内置安全机制，储药器会触发不可恢复的49号错误代码(0x31)，导致俗称"尖叫器"的状态——这种持续恼人的蜂鸣声只能通过在储药器背面指定位置打孔来停止。 "49号储药器故障"的具体成因通常难以追溯。 在怀疑可能发生此类故障的情况下（例如应用程序崩溃、运行开发版本或重新安装时）。 +This failure is related to an incorrect pod state for a command or an error during an insulin delivery command. This is when the driver and Pod disagree on the actual state. The Pod (out of a built-in safety measure) then reacts with an unrecoverable error code 49 (0x31) ending up with what is know as a “screamer”: the long irritating beep that can only be stopped by punching a hole at the appropriate location at the back of the Pod. The exact origin of a “49 pod failure” often is hard to trace. In situations that are suspected for this failure to occur (for instance on application crashes, running a development version or re-installation). ### 泵体失联警报 -当超过预设时间仍无法与储药器建立通信时，系统将触发"泵体不可达"警报。 可通过右上角三点菜单配置泵体失联警报：选择**偏好设置**→**本地警报**→**泵体失联阈值[分钟]**进行设置。 建议将警报阈值设置为**120**分钟后触发。 +When no communication can be established with the pod for a preconfigured time a “Pump unreachable” alert will be raised. Pump unreachable alerts can be configured by going to the top right-hand side three-dot menu, selecting **Preferences**\ ➜\ **Local Alerts**\ ➜\ **Pump unreachable threshold [min]**. Recommended value is alerting after **120** minutes. ### 导出设置 -导出**AAPS**设置可让您恢复所有配置参数，更重要的是能完整保留所有目标进度状态。 当需要恢复到"最后已知的正常状态"、或卸载重装**AAPS**后、以及手机丢失需在新设备上重新安装时，均可通过该功能还原设置。 +Exporting **AAPS** settings enables you to restore all your settings, and maybe more importantly, all your Objectives. You may need to restore settings to the “last known working situation” or after uninstalling/reinstalling **AAPS** or in case of phone loss, reinstalling on the new phone. -注：当前使用中的储药器信息也会包含在导出设置中。 若导入"旧版"导出文件，您当前使用的储药器将"失效"。 别无他法。 在某些情况下（例如_计划性_更换手机时），您可能需要使用导出文件来恢复**AAPS**设置，**同时保留当前正在使用的储药器**。 在这种情况下，必须使用最近导出的、包含当前使用中储药器信息的设置文件。 +Note: The active pod information is included in the exported settings. If you import an "old" exported file, your actual pod will "die". There is no other alternative. In some cases (like a _programmed_ phone change), you may need to use the exported file to restore **AAPS'** settings **while keeping the current active Pod**. In this case it is important to only use the recently exported settings file containing the pod currently active. -**最佳做法是在激活储药器后立即进行设置导出**。 如此可在出现问题时随时恢复当前使用中的储药器状态。 例如在切换到备用手机时。 +**It is good practice to do an export immediately after activating a pod**. This way you will always be able to restore the current active pod in case of a problem. For instance when moving to another backup phone. -请定期将导出的设置文件备份至云端等安全位置，确保任何手机在需要时（如设备丢失或恢复出厂设置时）都能随时获取。 +Regularly copy your exported settings to a safe place (as a cloud drive) that can be accessible by any phone when needed (e.g. in case of a phone loss or factory reset of the actual phone). ### 导入设置 -**警告** 请注意：导入设置可能会引入过期的储药器状态数据。 这将导致当前使用中的储药器存在失效风险！ （参见**导出设置**章节）。 建议仅在无其他解决方案时尝试此操作。 +**WARNING** Please note that importing settings will possibly import an outdated Pod status. As a result, there is a risk of losing the active Pod! (see **Exporting Settings**). It is better to only try it when no other options are available. -导入含激活状态储药器的设置时，请确认该导出文件包含当前使用中的储药器信息。 +When importing settings with an active Pod, make sure the export was done with the currently active pod. -**在储药器激活状态下导入：**（可能导致储药器失效！） +**Importing while on an active Pod:** (you risk losing the Pod!) 1. 请确保导入的是最近导出且包含当前使用中储药器信息的设置文件。 2. 导入您的设置文件。 3. 请核对所有偏好设置项。 -**导入设置（无激活状态的储药器会话）** +**Importing (no active Pod session)** 1. 导入任何近期导出的文件均可生效（参见上文说明） 2. 导入您的设置文件。 @@ -447,15 +453,15 @@ DASH驱动程序设置可通过左上角**汉堡菜单**中的**配置构建器( ### 导入包含非活跃状态储药器数据的设置文件 -当导入包含已停用储药器数据的设置时，AAPS将尝试与其建立连接，这显然会导致失败。 在此情况下您将无法激活新储药器。 +When importing settings containing data for a Pod that is no longer active, AAPS will try to connect with it, which will obviously fail. You can not activate a new Pod in this situation. -要清除旧储药器会话，请"尝试"执行停用操作。 停用操作将会失败。 选择"重试"。 经过两到三次重试后，系统将提供移除储药器的选项。 待旧储药器移除后，即可激活新储药器。 +To remove the old pod session “try” to de-activate the Pod. The de-activation will fail. Select “Retry”. After the second or third retry you will get the option to remove the pod. Once the old pod is removed you will be able to activate a new pod. ### 重新安装AAPS -卸载**AAPS**时，所有设置、目标进度及当前储药器会话都将丢失。 请确保已备份最新导出的设置文件以便恢复！ +When uninstalling**AAPS** you will lose all your settings, objectives and the current Pod session. To restore them make sure you have a recent exported settings file available! -当使用激活状态的储药器时，请确保已备份当前储药器会话的导出文件，否则导入旧版设置将导致当前使用中的储药器失效。 +When on an active Pod, make sure that you have an export for the current pod session or you will lose the currently active pod when importing older settings. 1. 请导出您的设置文件并妥善保存副本。 2. 卸载**AAPS**并重启您的手机。 @@ -467,7 +473,7 @@ DASH驱动程序设置可通过左上角**汉堡菜单**中的**配置构建器( ### 升级AAPS至新版本 -多数情况下无需卸载旧版本。 您可直接安装新版本进行"就地升级"。 该操作在储药器激活状态下同样适用。 +In most cases there is no need to uninstall. You can do an “in-place” install by starting the installation for the new version. This is also possible when on an active Pod session. 1. 请导出您的设置文件。 2. 安装新版**AAPS**。 @@ -477,7 +483,7 @@ DASH驱动程序设置可通过左上角**汉堡菜单**中的**配置构建器( ### Omnipod驱动警报 -请注意：Omnipod Dash驱动会在**概览页**显示多种特有警报，多数为提示性信息可手动关闭，部分警报会要求用户执行操作以消除触发警报的原因。 以下是您可能会遇到的主要警报摘要： +Please note that the Omnipod Dash driver presents a variety of unique alerts on the **Overview tab**, most of them are informational and can be dismissed while some provide the user with an action to take to resolve the cause of the triggered alert. A summary of the main alerts that you may encounter is listed below: * 未检测到活动的Pod会话。 该警报可通过点击**暂缓**临时关闭，但在新储药器激活前将持续触发。 该警报激活后将自动静音。 * 储药器已暂停 提示性警报，表明储药器处于暂停状态。 @@ -487,7 +493,7 @@ DASH驱动程序设置可通过左上角**汉堡菜单**中的**配置构建器( ## DASH系统求助渠道 -DASH系统的所有开发工作均由社区**志愿者**无偿完成；在请求协助前，请谨记以下准则： +All of the development work for the DASH is done by the community on a **volunteer** basis; please keep this in mind and use the following guidelines before requesting assistance: - **第0级：**查阅本文档相关章节，确保您已理解遇到问题的功能模块的正确运作方式。 - **第1级：**若参照本文档仍无法解决问题，请通过[此邀请链接](https://discord.gg/4fQUWHZ4Mw)加入**Discord**平台的*#AAPS*频道寻求帮助。 diff --git a/docs/CROWDIN/zh_CN/CompatiblePumps/OmnipodEros.md b/docs/CROWDIN/zh_CN/CompatiblePumps/OmnipodEros.md index 19ee0c9a87c3..bbe4687c551d 100644 --- a/docs/CROWDIN/zh_CN/CompatiblePumps/OmnipodEros.md +++ b/docs/CROWDIN/zh_CN/CompatiblePumps/OmnipodEros.md @@ -43,7 +43,7 @@ orphan: true **安全第一** - 请勿在无法处理突发故障的环境中操作（必须备有备用储药器、胰岛素、电量充足的RileyLink及手机设备）。 -**AAPS Omnipod驱动激活储药器后，您的Omnipod PDM将无法继续使用**。 此前您通过Omnipod PDM向Eros储药器发送指令。 Eros储药器仅允许单一设备与其建立通信连接。 成功激活储药器的设备将成为此后唯一获准与其通信的设备。 这意味着当您通过AAPS Omnipod驱动使用RileyLink激活Eros储药器后，**PDM将无法再控制该储药器**。 配备RileyLink的AAPS Omnipod驱动现已成为您的实际控制设备。 *这并不意味着您应该丢弃PDM，建议将其保留作为备用设备，以防AAPS运行异常时应急使用。* +**AAPS Omnipod驱动激活储药器后，您的Omnipod PDM将无法继续使用**。 此前您通过Omnipod PDM向Eros储药器发送指令。 Eros储药器仅允许单一设备与其建立通信连接。 The device that successfully activates the pod is the only device allowed to communicate with it from that point forward. 这意味着当您通过AAPS Omnipod驱动使用RileyLink激活Eros储药器后，**PDM将无法再控制该储药器**。 配备RileyLink的AAPS Omnipod驱动现已成为您的实际控制设备。 *这并不意味着您应该丢弃PDM，建议将其保留作为备用设备，以防AAPS运行异常时应急使用。* **可配置多个RileyLink设备，但同一时间仅能选择一个RileyLink与储药器通信。** AAPS Omnipod驱动支持在RileyLink配置中添加多个设备，但每次仅能启用一个RileyLink进行收发通信。 @@ -191,7 +191,7 @@ orphan: true 正常情况下，储药器使用寿命为3天（72小时），触发过期警告后仍可延长使用8小时，总使用时长达80小时。 -要停用储药器（无论是因到期还是故障）： +To deactivate a pod (either from expiration or from a pod failure): 1. 请进入**Omnipod(POD)**标签页 → 点击**储药器管理(1)**按钮 → 在**储药器管理**界面选择**停用储药器(2)**功能。 @@ -245,7 +245,7 @@ orphan: true #### 恢复胰岛素输注 -此指令用于命令当前暂停中的储药器恢复胰岛素输注。 命令成功处理后，胰岛素将根据当前时间从活动基础配置文件中恢复使用当前基础率进行正常输注。 Pod将重新接受大剂量、临时基础率和超微大剂量的指令。 +Use this command to instruct the active, currently suspended pod to resume insulin delivery. 命令成功处理后，胰岛素将根据当前时间从活动基础配置文件中恢复使用当前基础率进行正常输注。 Pod将重新接受大剂量、临时基础率和超微大剂量的指令。 1. 请前往**Omnipod(POD)**标签页，确认**Pod状态(1)**字段显示为**已暂停**，然后点击**恢复输注(2)**按钮启动流程，指示当前pod恢复正常胰岛素输注。 **Pod状态(3)**字段将显示**恢复输注**信息，表明RileyLink正在向暂停中的pod发送该指令。 @@ -574,7 +574,7 @@ Omnipod驱动设置可通过左上角**汉堡菜单**中的**配置构建器** ![Omnipod_Settings_2](../images/omnipod/Omnipod_Settings_2.png) -以下是设置分组列表，您可通过切换开关启用或禁用下文所述的大多数选项： +The settings groups are listed below; you can enable or disable via a toggle switch for most entries described below: ![Omnipod_Settings_3](../images/omnipod/Omnipod_Settings_3.png) @@ -595,7 +595,7 @@ Omnipod驱动设置可通过左上角**汉堡菜单**中的**配置构建器** ### 确认提示音 -提供储药器对大剂量注射、基础率、超微大剂量(SMB)和临时基础率(TBR)输送及变更的确认提示音。 +Provides confirmation beeps from the pod for bolus, basal, SMB, and TBR delivery and changes. - ***启用大剂量提示音：** 设置是否在大剂量给药时播放确认提示音。 - ***基础率提示音启用：** 设置是否在以下情况播放确认提示音：新基础率设定时、活动基础率取消时或当前基础率变更时。 @@ -606,7 +606,7 @@ Omnipod驱动设置可通过左上角**汉堡菜单**中的**配置构建器** 当pod到期、关机或根据设定的阈值单位检测到储药器药量不足时，提供AAPS警报和Nightscout通知。 -*请注意：自警报触发后与储药器首次通信时，AAPS将始终针对任何警报发出通知。 除非启用"自动确认储药器警报"功能，否则仅消除通知并不会消除警报状态。 要手动消除警报，必须访问Omnipod(POD)标签页并按下"确认警报"按钮。* +*Note an AAPS notification will ALWAYS be issued for any alert after the initial communication with the pod since the alert was triggered. Dismissing the notification will NOT dismiss the alert UNLESS automatically acknowledge Pod alerts is enabled. 要手动消除警报，必须访问Omnipod(POD)标签页并按下"确认警报"按钮。* - ***启用到期提醒：** 设置是否在达到关机前设定小时数时触发pod到期提醒。 - **关机前小时数：** 设定活动储药器关机前触发过期提醒警报的小时数。 @@ -618,7 +618,7 @@ Omnipod驱动设置可通过左上角**汉堡菜单**中的**配置构建器** 当不确定临时基础率(TBR)、超微大剂量(SMB)或大剂量给药是否成功时，提供AAPS通知和手机声音警报。 -*注：这些仅为手机通知，不会触发储药器声音提示。* +*NOTE: These are notifications only, no audible beep alerts are made.* - **不确定TBR通知的声音已启用:** 启用或禁用此设置，当AAPs不确定是否成功设置TBR时，触发声音警报和视觉通知。 - ***不确定超微大剂量通知的声音已启用:** 启用或禁用此设置，当AAPS不确定是否成功输注超微大剂量时，触发声音警报和视觉通知。 @@ -690,7 +690,7 @@ Omnipod驱动设置可通过左上角**汉堡菜单**中的**配置构建器** ### 余量水平 -**胰岛素储药量** +**Insulin Level** Omnipod Eros Pod中的胰岛素量报告不精确。 这是因为无法精确知道Pod中注入了多少胰岛素，只能通过填充Pod时触发的2声提示音来判断已注入超过85单位。 单个Pod最多可容纳200单位胰岛素。 初始化过程也可能引入误差，因为这不是一个精确的操作流程。 基于这两个因素，Omnipod驱动程序的编写旨在提供储药器中剩余胰岛素的最佳估算值。 @@ -716,11 +716,11 @@ Omnipod Eros Pod中的胰岛素量报告不精确。 这是因为无法精确 ### Pod 故障 -储药器偶尔会因各种问题发生故障，包括储药器自身的硬件问题。 最佳做法是不要向Insulet公司报修，因为AAPS并非官方认可的使用方案。 故障代码列表可[在此处](https://github.com/openaps/openomni/wiki/Fault-event-codes)查看，以帮助确定原因。 +Pods fail occasionally due to a variety of issues, including hardware issues with the Pod itself. It is best practice not to call these into Insulet, since AAPS is not an approved use case. 故障代码列表可[在此处](https://github.com/openaps/openomni/wiki/Fault-event-codes)查看，以帮助确定原因。 ### 预防49号储药器故障 -该故障与指令对应的储药器状态错误或胰岛素输注指令执行出错有关。 我们建议用户在**配置构建器**➜**通用**➜**NS客户端**➜**齿轮图标**➜**高级设置**下切换为仅上传模式(禁用同步)，以防止可能出现的问题。 +This failure is related to an incorrect pod state for a command or an error during an insulin delivery command. 我们建议用户在**配置构建器**➜**通用**➜**NS客户端**➜**齿轮图标**➜**高级设置**下切换为仅上传模式(禁用同步)，以防止可能出现的问题。 ### 泵体失联警报 @@ -739,7 +739,7 @@ Omnipod Eros Pod中的胰岛素量报告不精确。 这是因为无法精确 ### Omnipod驱动警报 -请注意：Omnipod驱动程序在**概览标签页**会显示多种独特警报，其中大部分为信息类警报可忽略，但部分警报会提示用户需采取相应操作来解决触发警报的原因。 以下是您可能会遇到的主要警报摘要： +请注意：Omnipod驱动程序在**概览标签页**会显示多种独特警报，其中大部分为信息类警报可忽略，但部分警报会提示用户需采取相应操作来解决触发警报的原因。 A summary of the main alerts that you may encounter is listed below: #### 无活动Pod diff --git a/docs/CROWDIN/zh_CN/Getting-Started/Introduction.md b/docs/CROWDIN/zh_CN/Getting-Started/Introduction.md index 0dbf30c34f92..9799bc3b3721 100644 --- a/docs/CROWDIN/zh_CN/Getting-Started/Introduction.md +++ b/docs/CROWDIN/zh_CN/Getting-Started/Introduction.md @@ -12,24 +12,24 @@ 在不远的将来，既能输注胰岛素也能输注胰高糖素的“双激素”系统，将能够预防严重低血糖，进而实现更加严格的血糖控制。 -人工胰腺可被视为[“糖尿病的自动驾驶仪”](https://www.artificialpancreasbook.com/)。 这是什么意思呢？ +人工胰腺可被视为[“糖尿病的自动驾驶系统”](https://www.artificialpancreasbook.com/)。 这意味着什么？ -飞机的自动驾驶模式不可能完全取代飞行员，要不然飞行员就可以全程睡觉了。 但自动驾驶能给飞行员提供帮助， 让他们不用只盯着飞机的状态，而是可以把注意力放在更广泛的飞行状况管理上。 自动驾驶装置从各种传感器接收信号，按照飞行员的设置来评估这些信号，然后按需调整飞行参数，有需要注意的问题就提醒飞行员。 飞行员就不用事必躬亲了。 +在航空领域，自动驾驶系统不可能完全取代飞行员，要不然飞行员就可以全程睡觉了。 自动驾驶系统的作用在于辅助飞行员操作。 让飞行员得以从持续监控飞行状态的负荷中解脱，转而专注于更高层次的全局监控与策略制定。 自动驾驶系统通过持续处理各类传感器信号，结合飞行员预设的参数进行综合运算，进而自动执行必要的飞行姿态调整。当系统识别到潜在风险时，会立即向飞行员发出警报提示。 这样飞行员就不用事必躬亲了。 ![image](../images/autopilot.png) (Introduction-what-does-hybrid-closed-loop-mean)= ## 什么是混合闭环（hybrid closed loop）？ -1型糖尿病的最佳疗法应该是“恢复功能”（比如移植能受免疫系统保护的胰腺细胞）。 但这种疗法我们还不知道什么时候能实现，那么“全闭环”人工胰腺应该是次优选择。 也就是无需用户输入任何信息就能把血糖水平控的很好的科技系统（像是餐前大剂量胰岛素、计划之内的运动等信息都不用输入）。 目前应用比较广泛的闭环系统都不是真正的“全闭环”，还是需要用户输入一些数据。 这样的系统采用了自动处理和用户输入相结合的方式，所以被称为“混合闭环”。 +针对1型糖尿病的最佳解决方案是"功能性治愈"（比如通过移植受免疫保护的胰岛细胞实现）。 但这种疗法我们还不知道什么时候能实现，那么“全闭环”人工胰腺应该是次优选择。 这种技术系统无需任何用户输入（如针对饮食的大剂量注射或运动前告知），即可实现良好的血糖调控。 目前应用比较广泛的闭环系统都不是真正的“全闭环”，还是需要用户输入一些数据。 因此被称为"混合"闭环系统，即自动化技术与人工干预相结合。 ## 闭环的由来？ -用于1型糖尿病患者（T1D）的商业化技术发展的很慢。 2013年，T1D社区发起了#WeAreNotWaiting（我们不想等下去）运动。 他们利用胰岛素泵、血糖仪等目前可用的技术自己开发了各种系统来改进血糖控制方式、增强安全性、提高生活质量。 这些系统被称为DIY（do-it-yourself，自己动手制作）系统，因为它们没有得到过卫生机构（FDA、NHS等）的正式批准。 目前主要有四种 DIY 系统： [OpenAPS](https://openaps.org/what-is-openaps/)、**AAPS**、[Loop](https://loopkit.github.io/loopdocs/#what-is-loop)和[ iAPS](https://github.com/Artificial-Pancreas/iAPS?fbclid=IwAR2fA9Y9YqYzpKSrtEsotfXl5b67UclDkKgyrv52tQLzYbOoBeNGRmjlJJI)。 +1型糖尿病（T1D）领域商业化技术的发展进程极为缓慢。 2013年，T1D患者群体发起了#WeAreNotWaiting（#我们不再等待）运动。 他们利用胰岛素泵、血糖仪等目前可用的技术自己开发了各种系统来改进血糖控制方式、增强安全性、提高生活质量。 这些系统被称为DIY（do-it-yourself，自己动手制作）系统，因其未获得医疗监管机构（如FDA、NHS等）正式认证。 目前主要有四种 DIY 系统： [OpenAPS](https://openaps.org/what-is-openaps/)、**AAPS**、[Loop](https://loopkit.github.io/loopdocs/#what-is-loop)和[ iAPS](https://github.com/Artificial-Pancreas/iAPS?fbclid=IwAR2fA9Y9YqYzpKSrtEsotfXl5b67UclDkKgyrv52tQLzYbOoBeNGRmjlJJI)。 -要想理解 DIY 闭环的基础原理，最好是阅读Dana Lewis的著作《自动胰岛素输注》（Automated Insulin Delivery）。（中文书籍推荐马学毅的《胰岛素泵治疗糖尿病》）。 您可以在[这里](https://www.artificialpancreasbook.com/)免费获取第一本书(或购买该书的印刷版)。 如果您想更多地了解**AAPS**的前身[OpenAPS](https://openaps.org/what-is-openaps/)，[OpenAPS 网站](https://openaps.org/what-is-openaps/)有很多好资源。 +要想理解 DIY 闭环的基础原理，最好是阅读Dana Lewis的著作《自动胰岛素输注》（Automated Insulin Delivery）。（中文书籍推荐马学毅的《胰岛素泵治疗糖尿病》）。 您可通过[此链接](https://www.artificialpancreasbook.com/)免费获取电子版(或购买实体书)。 如果您想更多地了解**AAPS**的开发基础——[OpenAPS](https://openaps.org/what-is-openaps/)的详细信息，[OpenAPS 官网](https://openaps.org/what-is-openaps/)提供了丰富的学习资源。 -一些商用混合闭环系统已经推出，其中最新的是[CamAPS FX](https://camdiab.com/)（英国和欧盟）和 [Omnipod 5](https://www.omnipod.com/en-gb/what-is-omnipod/omnipod-5)（美国和欧盟）。 这些商业化的系统与 DIY 系统有很大差异，主要因为他们都带有“自学习算法”，可以根据近几天你的胰岛素需求量来调整给药量。 在DIY社区，许多人已经尝试过这些商业系统，并将其与DIY系统进行了比较。 您可以在这些系统的专门 Facebook 群组、[AAPS Facebook](https://www.facebook.com/groups/AndroidAPSUsers/) 群组或 [Discord](https://discord.com/invite/4fQUWHZ4Mw) 上询问，以了解不同系统的比较情况。 +目前已有若干商用混合闭环系统面市，其中最新的是[CamAPS FX](https://camdiab.com/)（英国和欧盟）和 [Omnipod 5](https://www.omnipod.com/en-gb/what-is-omnipod/omnipod-5)（美国和欧盟）。 这些商业化的系统与 DIY 系统有很大差异，主要因为他们都带有“自学习算法”，可以根据用户近几天胰岛素需求量来调整给药量。 在DIY社区，许多人已经尝试过这些商业系统，并将其与DIY系统进行了比较。 欲了解不同系统的详细比较，您可以在相关系统的专属 Facebook 群组、[AAPS Facebook](https://www.facebook.com/groups/AndroidAPSUsers/) 群组或 [Discord](https://discord.com/invite/4fQUWHZ4Mw) 上询问。 ## 什么是 Android APS (AAPS)？ @@ -37,54 +37,54 @@ **图1** Android APS (Artificial Pancreas System，人工胰腺系统)，AAPS的基本构成。 -安卓 APS（**AAPS**）是一个混合闭环系统，或称人工胰腺系统（APS）。 它使用 #WeAreNotWaiting 1 型糖尿病社区开发的 [OpenAPS 算法](https://openaps.org/)（一套计算规则）进行胰岛素剂量计算。 +安卓 APS（**AAPS**）是一款混合闭环系统，或称人工胰腺系统（APS）。 它使用 #WeAreNotWaiting 1 型糖尿病社区开发的 [OpenAPS 算法](https://openaps.org/)（规则集）进行胰岛素剂量计算。 -由于 OpenAPS 只与某些较老的胰岛素泵兼容，因此 **AAPS**（可与更广泛的胰岛素泵配合使用）是 Milos Kozak 于 2016 年为一位患有 1 型糖尿病的家庭成员开发的。 自那时起， 很多与1型糖尿病有关的志愿者和技术爱好者加入了进来，不断开发和完善**AAPS** 。 目前， **AAPS** 已经被近万人使用。 这是一个高度可定制且多功能的系统，由于它是开源的，因此也能轻松兼容许多其他开源糖尿病软件和平台。 现行 **AAPS** 系统的基本组成部分如上**图 1** 所示。 +由于 OpenAPS 只与某些较老的胰岛素泵兼容，Milos Kozak于2016年为其罹患1型糖尿病的家庭成员开发了**AAPS**（适配更广泛的胰岛素泵型号）。 自那时起， 很多与1型糖尿病有关的志愿者计算机开发团队和技术爱好者加入了进来，不断优化升级**AAPS** 。 目前， **AAPS** 已经被近万人使用。 AAPS是一个高度可定制且多功能的系统，由于它是开源的，因此与众多开源糖尿病软件及平台实现良好兼容。 目前 **AAPS** 系统的基本组件架构如上**图 1** 所示。 -## AAPS的基本组成部分有哪些？ +## AAPS的基本组件有哪些？ -AAPS的“核心”是您自己构建的 **应用程序**。 这方面有详细的步骤说明。 然后你需要在一部[兼容的](../Getting-Started/Phones.md)**安卓智能手机**上安装**AAPS 应用程序**（**1**）。 有的用户倾向于用一部专门的手机来安装闭环，而非平时用的手机。 这样（尤其是苹果手机用户）就不用非得换到安卓手机上处理日常事务，只是用它来运行AAPS闭环就行。 +AAPS的“中枢”是您自己构建的 **应用程序**。 构建过程有详细的逐步操作指南。 然后你需要在一部[兼容的](../Getting-Started/Phones.md)**安卓智能手机**上安装**AAPS 应用程序**（**1**）。 有的用户倾向于用一部专门的手机来安装闭环，而非平时用的手机。 这样（尤其是苹果手机用户）就无需将生活中的其他事务迁移至安卓平台，仅需通过该安卓设备运行AAPS闭环即可。 -除了 **AAPS** 之外，**安卓智能手机**还需要安装另一个 App。 这个[附加应用程序](../Getting-Started/CompatiblesCgms.md)通过蓝牙从传感器（**2**）接收血糖数据，然后将数据通过手机内部传输到**AAPS应用**。 +除了 **AAPS** 之外，**安卓智能手机**还需要安装另一个 App。 这个[附加应用程序](../Getting-Started/CompatiblesCgms.md)通过蓝牙从探头（**2**）接收血糖数据，然后在手机内部将数据传输至**AAPS应用**。 -**AAPS** 采用的是 OpenAPS 的决策过程(也就是**算法**)。 初学者最开始用基础的 **oref0** 算法，对AAPS比较熟悉之后可以切换到新的 **oref1** 算法。 使用哪个算法 (oref0或 oref1) 取决于哪个算法最适合你的具体情况。 在这两种情况下，算法都会考虑多种因素，并且每次从动态血糖仪获得新的数据时都进行快速计算。 然后，算法通过蓝牙向胰岛素泵（**3**）发送指令，告诉它需要输送多少胰岛素。 所有信息都可以通过移动数据或无线网络发送到互联网（**4**）上。 如果需要的话，这些数据也可以分享给别人或者收集起来以供分析。 +**AAPS** 采用的是 OpenAPS 的决策过程(也就是**算法**)。 初学者最开始用基础的 **oref0** 算法，对AAPS比较熟悉之后可以切换到新的 **oref1** 算法。 使用哪个算法 (oref0或 oref1) 取决于哪个算法最适合你的具体情况。 两种算法均通过整合多维度参数，在每次接收探头新数据时进行实时运算， 随后通过蓝牙向胰岛素泵（**3**）发送输注指令，告诉它需要输注多少胰岛素。 所有运行数据可通过移动网络或Wi-Fi传输至互联网（**4**）， 如果需要的话，这些数据也可以分享给别人或者收集起来以供分析。 ## AAPS系统有哪些优势？ -**AAPS**采用的 OpenAPS算法能在无需用户输入的情况下自动控制血糖水平，会每5分钟根据用户定义的参数（主要是基础率、胰岛素敏感度、碳水系数、活性胰岛素持续时间等）和收到的动态血糖数据做出一次反应。 对患者或者护理人员来说，使用AAPS的优点主要包括能对各种参数进行广泛的微调，自动化操作以及系统运行情况的高度透明。 这样可以更好地控制您（或您的家属）的糖尿病，从而提高生活质量，让您更安心。 +**AAPS**采用的OpenAPS算法根据用户定义的参数（关键参数包括基础率、胰岛素敏感系数（ISF）、碳水系数（IC）、胰岛素作用时长（DIA）等），在无需人工干预的情况下，每5分钟响应探头新数据以调控血糖水平。 使用AAPS的已报告优势包括：丰富的可调参数选项、自动化规则（automations）以及系统对患者/护理者操作过程的可视化。 这些特性可助您（或受监护者）实现更优的糖尿病管理，从而提升生活质量与心理安全感。 ### **具体优势包括：** -#### 1) 内置安全性 -如需了解被称为 oref0 和 oref1 的算法的安全特性，[请点击此处](https://openaps.org/reference-design/)。 用户可控制自己的安全限制。 +#### 1) 算法安全特性 +要了解oref0与oref1算法的内置安全机制，[请点击此处](https://openaps.org/reference-design/)。 用户可自主设定安全限制参数。 #### 2) **硬件灵活性** -**AAPS** 可与多种胰岛素泵和传感器配合使用。 例如，如果你用德康（Dexcom）的动态，但对它底板上的胶过敏，那你还可以换成雅培的Libre动态。 这让我们能够灵活应对生活中的变化。 您无需重建或重新安装 **AAPS** 应用程序，只需在应用程序中勾选不同的选项即可更换硬件。 AAPS 独立于特定的泵驱动程序，还包含一个 "虚拟泵"，因此用户在自己使用之前可以安全地进行实验。 +**AAPS** 兼容多种胰岛素泵与传感器。 例如，如果你用德康（Dexcom）的动态，但对它底板上的胶过敏，那你还可以换成雅培的Libre动态。 这种设计赋予系统高度适应性，可随生活环境变化灵活调整。 您无需重新构建或重新安装 **AAPS** 应用程序，仅需在应用程序中勾选不同的选项即可完成硬件切换。 AAPS不依赖特定泵驱动模块，并内置"虚拟泵（virtual pump）"功能，便于用户在实际应用前进行安全测试。 #### 3) **高度可定制，有丰富的参数可以调节** -用户可以轻松添加或删除模块或功能，而且 **AAPS** 对开环和闭环模式都支持。 下面举例说明 **AAPS** 系统的一些可能性： +用户可便捷地添加或删除功能模块，而且 **AAPS** 对开环和闭环模式都支持。 以下是**AAPS**系统的潜在功能示例： - a) 可在进食前 30 分钟设定较低的血糖目标值；目标值可低至 72 mg/dL（4.0 mmol/L）。 + a) 可在进食前 30 分钟设定较低的临时目标（TT）；目标值可低至 72 mg/dL（4.0 mmol/L）。 - b) 如果您因胰岛素抵抗导致血糖过高，**AAPS** 允许您设置一条**自动**规则，当血糖升至 8 mmol/L （144 mg/dL）以上时启动，（例如）切换到 120% 配置文件（与正常**配置文件**设置相比，基础率增加 20%，其他因素也得到加强）。 这种自动操作会在您预设的时间内持续作用。 可以设定为一周之内的某几天、一天之内的某几个时间点甚至在某些具体地点起作用。 + b) 若存在胰岛素抵抗导致血糖升高，**AAPS** 允许您设置一条**自动化规则（automations）**，当血糖超过 8 mmol/L （144 mg/dL）时自动切换至120%的配置文件（profile）（与正常**配置文件**设置相比，基础率增加 20%并强化其他调控参数）。 该自动化规则将根据您预设的持续时间内生效， 并可限定仅在一周内的特定日期、每日具体时段，甚至特定地理位置触发。 - 3）如果您的孩子没打招呼就跳上了蹦床疯玩起来，**AAPS**可以让你通过手机直接在一定时间内暂停胰岛素输注。 + c）如果您的孩子没打招呼就跳上了蹦床疯玩起来，**AAPS**可以让你通过手机直接在一定时间内暂停胰岛素输注。 - d) 在重新连接因游泳而断开的管道泵后，**AAPS** 将根据您当前的血糖值，计算您在断开连接期间所错过的基础胰岛素，并小心地输送胰岛素。 如果不需要这些胰岛素，只要手动“取消”这种后补基础率就可以了。 + d) 当管路泵因游泳断开后重新连接时，**AAPS** 将自动计算断连期间缺失的基础胰岛素量，并根据当前血糖水平进行谨慎输注。 若系统计算的补充剂量超出实际需求，用户可通过"取消"功能直接中止缺失基础胰岛素的补注。 - e) **AAPS** 具有针对不同情况设置不同配置文件的功能，并可在不同配置文件之间轻松切换。 例如，如果您担心夜间低血糖，可以把采用了更快降低血糖的算法的功能（如微型大剂量（"**SMB**"）、未声明碳水（"**UAM**"）设置为只在白天起效。 + e) **AAPS** 支持为不同场景创建多个配置文件（profile），并支持便捷切换。 例如，如果您担心夜间低血糖，可将加速降低高血糖的功能（如超微大剂量（SMB）、未声明膳食（UAM）等）设置为仅在白天生效。 -以上仅为举例，全套功能为日常生活提供了极大的灵活性，包括运动、疾病、激素周期_等_。 最终，还是需要用户来决定如何灵活运用这些功能，没有放之四海而皆准的自动化解决方案。 +以上均为示例，全套功能为日常生活提供了极大的灵活性，包括运动、疾病、激素周期_等_。 最终，还是需要用户来决定如何灵活运用这些功能，而且没有放之四海而皆准的通用自动化规则（automations）。 #### 4) **远程监控** -存在多种可能的监控渠道（Sugarmate、Dexcom Follow、xDrip+、Android Auto_等_），这些渠道适用于需要在特定场景（睡眠/驾驶）中接收可定制警报的家长/护理人员和成人。 在某些应用（如xDrip+）中，您还可以完全关闭警报，这对于刚启动预热还不准备联进闭环的新探头非常有用。 +存在多种可选的监控渠道（Sugarmate、Dexcom Follow、xDrip+、Android Auto_等_），可为父母/照护者及处于特定场景（如睡眠/驾驶）的成人用户提供可自定义的警报。 在某些应用（如xDrip+）中，您还可以完全关闭警报，这对于刚启动预热还不准备联进闭环的新探头非常有用。 #### 5) **远程控制** -与商业系统相比，**AAPS** 的一个显著优势是，监护人尤其是糖宝家长可以使用经过验证的文本（短信）命令或通过 App（[Nightscout](https://nightscout.github.io/) 或 AAPSClient）向 **AAPS** 系统发回各种命令。 这个功能1型糖宝的父母用的比较多。 例如，孩子在操场上忙着玩，一会要吃点小零食，这时你就可以用手机给个提前大剂量。 可以通过智能设备监控系统（_例如_Fitbit）、发送基本指令（_例如_三星Galaxy Watch 4），甚至在高性能智能手表（**5**）（_例如_LEMFO）上运行完整的AAPS系统。 最后这种情况下，你就可以抛开手机运行AAPS。 随着手表电池续航时间的延长和技术的日益稳定，最后一种选择可能会变得越来越有吸引力。 +与商业系统相比，**AAPS** 的核心优势在于，监护人尤其是糖宝家长可以使用经过验证的短信（SMS）命令或通过 App（[Nightscout](https://nightscout.github.io/) 或 AAPSClient）向 **AAPS** 系统发送各种命令。 这个功能1型糖宝的父母用的比较多。 例如，孩子在操场上忙着玩，一会要吃点小零食，这时你就可以用手机给个提前大剂量。 可以通过智能设备（_例如_Fitbit）来监控系统、发送基本指令（_例如_三星Galaxy Watch 4），甚至在高性能智能手表（**5**）（_例如_LEMFO）上运行完整的AAPS系统。 最后这种情况下，你就可以抛开手机运行AAPS。 随着手表电池续航时间的延长和技术的日益稳定，最后一种选择可能会变得越来越有吸引力。 #### 6) **得益于应用程序的开源，不受商业限制** 除了采用开放源代码的方法，允许随时查看 **AAPS** 的源代码之外，提供标准开放式编程接口也给其他开发人员提供了贡献新想法的机会。 **AAPS** 与 Nightscout 紧密集成。 这加快了开发速度，并允许用户添加功能，使糖尿病患者的生活更加方便。 此类集成的优秀示例包括[Nightscout](https://nightscout.github.io/)、[Nightscout Reporter](https://nightscout-reporter.zreptil.de/)、[xDrip+](https://xdrip.readthedocs.io/en/latest/install/usethedoc/)、[M5 stack](https://github.com/mlukasek/M5_NightscoutMon/wiki)等。 开源开发者和商业系统开发者之间一直在进行对话。 许多 DIY 创新逐渐被商业系统采用，而商业系统的开发速度较慢是可以理解的，部分原因是不同公司的系统（泵、App、传感器_等_）之间的接口需要仔细协商并获得许可。 这也会延缓那些方便患者（或有特殊需求的小部分患者）但不能产生可观利润的创新。 diff --git a/docs/CROWDIN/zh_CN/GettingHelp/GeneralTroubleshooting.md b/docs/CROWDIN/zh_CN/GettingHelp/GeneralTroubleshooting.md index 7896a953241d..a379a862f64f 100644 --- a/docs/CROWDIN/zh_CN/GettingHelp/GeneralTroubleshooting.md +++ b/docs/CROWDIN/zh_CN/GettingHelp/GeneralTroubleshooting.md @@ -37,14 +37,37 @@ * [短信指令](#SMSCommands-troubleshooting) -### 频繁的蓝牙连接问题 +### Frequent Bluetooth connection problems -这种情况可能发生在多种胰岛素泵上。 除了将 AAPS 排除在电池优化之外，您还可以将系统蓝牙应用排除在电池优化之外。 这在某些情况下可能有所帮助。 根据您使用的手机型号，查找蓝牙应用的位置会有所不同。 +#### Android 15 + +```{warning} +Developers are working on this issue impacting **AAPS** on some Samsung and Pixel phones. +``` + +After upgrading Android or moving to a recent phone, **AAPS** frequently loses Bluetooth connection to the pump. The problem disappears temporarily when restarting the phone. If the phone runs Android 15, you can try to enable the following: + +1) **Open preferences** by clicking the three-dot menu on the top right side of the home screen. + + +![打开参数设置](../images/Pref2020_Open2.png) + +2. Scroll down and open the **Confirmation beeps** / **Advanced** submenu. Enable **Bond BT device on Android 15+**. + + ![BondBT](../images/troubleshooting/BondBT.png) + +3. If the pump asks for a pairing request, accept it. + +4. Restart your phone. + +#### Battery optimization + +这种情况可能发生在多种胰岛素泵上。 Apart from excluding AAPS from any battery optimization, you can also exclude the system Bluetooth app from battery optimization. 这在某些情况下可能有所帮助。 Depending on the phone you use, you will find the Bluetooth app differently. 以下是特定 Android 手机上的示例操作步骤： -#### Pixel 手机（原生 Android 系统） +##### Pixel phones (stock Android) * 进入 Android 设置，选择"应用" @@ -67,7 +90,7 @@ ![蓝牙电池优化](../images/troubleshooting/pixel/04_btunrestricted.png) -#### 三星手机 +##### 三星手机 * 进入 Android 设置，选择"应用" @@ -92,7 +115,7 @@ ## CGM -* [一般](#general-cgm-troubleshooting) +* [常规](#general-cgm-troubleshooting) * [Dexcom G6](#DexcomG6-troubleshooting-g6) * [Libre 3](#libre3-experiences-and-troubleshooting) * [Libre 2](#Libre2-experiences-and-troubleshooting) diff --git a/docs/CROWDIN/zh_CN/images/troubleshooting/BondBT.png b/docs/CROWDIN/zh_CN/images/troubleshooting/BondBT.png new file mode 100644 index 000000000000..96b2fb272d90 Binary files /dev/null and b/docs/CROWDIN/zh_CN/images/troubleshooting/BondBT.png differ diff --git a/docs/CROWDIN/zh_CN/images/troubleshooting/samsung/01_BondBT_20250526.png b/docs/CROWDIN/zh_CN/images/troubleshooting/samsung/01_BondBT_20250526.png new file mode 100644 index 000000000000..74c3525959ed Binary files /dev/null and b/docs/CROWDIN/zh_CN/images/troubleshooting/samsung/01_BondBT_20250526.png differ diff --git a/docs/CROWDIN/zh_CN/images/troubleshooting/samsung/02_BondBT_20250526.png b/docs/CROWDIN/zh_CN/images/troubleshooting/samsung/02_BondBT_20250526.png new file mode 100644 index 000000000000..444013b29146 Binary files /dev/null and b/docs/CROWDIN/zh_CN/images/troubleshooting/samsung/02_BondBT_20250526.png differ diff --git a/docs/CROWDIN/zh_CN/images/troubleshooting/samsung/03_BondBT_20250526.png b/docs/CROWDIN/zh_CN/images/troubleshooting/samsung/03_BondBT_20250526.png new file mode 100644 index 000000000000..9caa7a484581 Binary files /dev/null and b/docs/CROWDIN/zh_CN/images/troubleshooting/samsung/03_BondBT_20250526.png differ diff --git a/docs/CROWDIN/zh_CN/images/troubleshooting/samsung/04_BondBT_20250526.png b/docs/CROWDIN/zh_CN/images/troubleshooting/samsung/04_BondBT_20250526.png new file mode 100644 index 000000000000..b25c1469f58e Binary files /dev/null and b/docs/CROWDIN/zh_CN/images/troubleshooting/samsung/04_BondBT_20250526.png differ diff --git a/docs/CROWDIN/zh_TW/CompatiblePumps/MedtrumNano.md b/docs/CROWDIN/zh_TW/CompatiblePumps/MedtrumNano.md index f80a7b405276..e837a7ac6d06 100644 --- a/docs/CROWDIN/zh_TW/CompatiblePumps/MedtrumNano.md +++ b/docs/CROWDIN/zh_TW/CompatiblePumps/MedtrumNano.md @@ -39,9 +39,9 @@ orphan: true **你的幫浦在未連線至AAPS時不會停止輸送胰島素** 預設的基礎率已經在幫浦上設定，並在目前啟動的設定檔中定義。 只要AAPS運作正常，他將發送臨時基礎率指令，最多持續120分鐘。 如果由於任何原因幫浦未接收到新指令（例如由於幫浦與手機距離過遠導致通訊中斷），當臨時基礎率結束時，幫浦將回到預設的基礎率。 -**AAPS 不支援 30 分鐘基礎率設定檔。** **AAPS 設定檔不支援 30 分鐘的基礎率時間框架** 如果你是 AAPS 新手並首次設置基礎率設定檔，請注意，基礎率從半小時開始的設定不被支援，你需要調整你的基礎率設定檔以從整點開始。 例如，如果你的基礎率為 1.1 單位，並於 09:30 開始，持續時間為 2 小時，於 11:30 結束，這將無法正常工作。 你需要將此 1.1 單位的基礎率更改為 9:00-11:00 或 10:00-12:00 的時間範圍。 儘管Medtrum幫浦硬體本身支援30分鐘基礎率增量，但AAPS目前無法在其算法中考慮這些增量。 +**AAPS 不支援 30 分鐘基礎率設定檔。** **AAPS 設定檔不支援 30 分鐘的基礎率時間框架** 如果你是 AAPS 新手並首次設置基礎率設定檔，請注意，基礎率從半小時開始的設定不被支援，你需要調整你的基礎率設定檔以從整點開始。 例如，如果你的基礎率為 1.1 單位，並於 09:30 開始，持續時間為 2 小時，於 11:30 結束，這將無法正常工作。 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. 儘管Medtrum幫浦硬體本身支援30分鐘基礎率增量，但AAPS目前無法在其算法中考慮這些增量。 -**AAPS不支援0U/h的設定檔基礎率** 儘管Medtrum幫浦支援零基礎率，但AAPS使用設定檔基礎率的倍數來確定自動治療，因此無法使用零基礎率。 可以透過“中斷幫浦”功能或停用循環/臨時基礎率或暫停循環/臨時基礎率的組合來實現臨時的 0 單位基礎率。 +**AAPS不支援0U/h的設定檔基礎率** 儘管Medtrum幫浦支援零基礎率，但AAPS使用設定檔基礎率的倍數來確定自動治療，因此無法使用零基礎率。 A temporary zero basal rate can be achieved through the "Disconnect pump" function or through a combination of Disable Loop/Temp Basal Rate or Suspend Loop/Temp Basal Rate. ## 設定 diff --git a/docs/CROWDIN/zh_TW/CompatiblePumps/OmnipodDASH.md b/docs/CROWDIN/zh_TW/CompatiblePumps/OmnipodDASH.md index 4a6c37f59295..c4b8a51e74f1 100644 --- a/docs/CROWDIN/zh_TW/CompatiblePumps/OmnipodDASH.md +++ b/docs/CROWDIN/zh_TW/CompatiblePumps/OmnipodDASH.md @@ -18,7 +18,13 @@ orphan: true * Pod 啟動時，**AAPS**將尋找並連接到新的DASH Pod 。 * 預期範圍：5-10公尺（依個人情況而異）。 -警告：目前報告有以下組合的藍牙連線問題**AAPS** / DASH / Android 15。 **AAPS** 不應與 Android 15 和 DASH 一起使用，除非使用者已檢查以下[**清單**](https://docs.google.com/spreadsheets/u/1/d/e/2PACX-1vScCNaIguEZVTVFAgpv1kXHdsHl3fs6xT6RB2Z1CeVJ561AvvqGwxMhlmSHk4J056gMCAQE02sAWJvT/pubhtml?gid=683363241&single=true)並確認其手機不是已知的報告問題。 **AAPS** 目前正在努力解決此問題。 +```{admonition} Android 15 +:class: warning + +There are currently reported Bluetooth connection issues with the following combination of **AAPS**: DASH + Android 15. +Please refrain from upgrading your phone to Android 15 unless you have checked the following [**list**](https://docs.google.com/spreadsheets/u/1/d/e/2PACX-1vScCNaIguEZVTVFAgpv1kXHdsHl3fs6xT6RB2Z1CeVJ561AvvqGwxMhlmSHk4J056gMCAQE02sAWJvT/pubhtml?gid=683363241&single=true) and verified that your phone is not a known reported issue. +If you experience frequent disconnection; try to enable Bond BT as described in: [**Bluetooth Issues**](../GettingHelp/GeneralTroubleshooting.md). +``` ## 硬體/軟體要求 @@ -31,59 +37,59 @@ orphan: true - **使用 [**Build APK**](../SettingUpAaps/BuildingAaps.md) 指示構建和安裝的 AAPS 版本 3.0 或更高版本**。 * [**連續血糖監測儀（CGM）**](../Getting-Started/CompatiblesCgms.md) -下面的指示說明如何啟動新的 Pod 會話。 在嘗試將**AAPS**與新的 Pod 連接之前，請等待當前 Pod 會話接近到期。 一旦 Pod 被取消，將會中斷 Pod ，無法重新使用。 +The instructions below explain how to activate a new pod session. Wait to close to expiry of a current pod session before trying to connect **AAPS** with a new pod. Once a pod is is cancelled it cannot reused and the disconnection will be final. ## 在你開始之前 -**安全第一** - 在沒有額外 Pod 、胰島素及手機設備的情況下，不應嘗試首次將**AAPS**連接至 Pod 。 +**SAFETY FIRST** - you should not try to connect **AAPS** to a pod for the first time without having access to extra pods, insulin, and phone devices are a must have. -**你的 Omnipod Dash PDM 在 AAPS Dash 驅動程式啟動 Pod 後將無需使用。** 在這之前用戶可以使用PDM 向 DASH 發送指令。 一個 DASH 將只能夠讓一個設備發送指令以與其進行通訊。 從那時起，成功啟動 Pod 的裝置將是唯一能夠與其通訊的裝置。 這意味著當你透過**AAPS**用Android手機啟動DASH後，**你將無法再使用PDM與該 Pod 連線**。 你Android手機中的**AAPS** Dash驅動程式現在是你的代替PDM。 +**Your Omnipod Dash PDM will become redundant after the AAPS Dash driver activates your pod.** Previously a user may have operated a PDM to send commands to your DASH. A DASH will only faciiliate a single device to send commands to communicate with it. The device that successfully activates the pod is the only device allowed to communicate with it from that point forward. This means that once you activate a DASH with your Android phone through the **AAPS**, **you will no longer be able to use your PDM with that pod**. The **AAPS** Dash driver in your Android phone is now your acting PDM. -*這並不意代表你應該丟棄 PDM，建議仍留作備用和應急使用，例如手機遺失或 AAPS 無法正常工作時。* +*This does NOT mean you should throw away your PDM, it is recommended to keep it around as a backup and for emergencies, for instance when your phone gets lost or AAPS is not working correctly.* -**當 Pod 未連線到 AAPS 時，Pod 不會停止輸送胰島素**。 預設的基礎率在 Pod 啟動時進行編程，如當前的活動**設定檔**所定義。 只要**AAPS**運行，它將發送基礎率命令，最多可運行120分鐘。 當因某些原因 Pod 未接收到任何新指令（例如，因 Pod 與手機的距離過遠而失去連線）時，Pod 會自動恢復為預設基礎率。 +**Your pod will not stop delivering insulin when it is not connected to AAPS**. Default basal rates are programmed on the pod on activation as defined in the current active **Profile**. As long as **AAPS** is operational it will send basal rate commands that run for a maximum of 120 minutes. 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. -**AAPS設定檔不支援30分鐘的基礎率時間框架** 如果你是首次接觸**AAPS**並設置基礎率**設定檔**，請注意不支援以半小時為單位的基礎率開始，程序為按小時為單位。 例如，如果你的基礎率為1.1單位，於09:30開始，持續2小時在11:30結束，則無法在**AAPS**中重現此項。 你需要將此 1.1 單位的基礎率更改為 9:00-11:00 或 10:00-12:00 的時間範圍。 儘管DASH硬體本身支援30分鐘的基礎率**設定檔**增量，但**AAPS**不支援此特性。 +**AAPS Profile does not support a 30 minute basal rate time frame** If you are new to **AAPS** and are setting up your basal rate **Profile** for the first time, please be aware that basal rates starting on a half-hour basis are not supported, and programmes on an hourly basis. For example, 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 im **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 support this feature. -**0U/h的設定檔基礎率在AAPS中不被支援** 雖然DASH支援零基礎率，但由於**AAPS**使用用戶的**設定檔**基礎率的倍數來確定自動化治療，因此無法以零基礎率運作。 可以透過“中斷幫浦”功能或停用循環/臨時基礎率或暫停循環/臨時基礎率的組合來實現臨時的 0 單位基礎率。 在**AAPS**中允許的最低基礎率為0.05U/h。 +**0U/h profile basal rates are NOT supported in AAPS** While the DASH does support a zero basal rate, since **AAPS** uses multiples of the user's **Profile** basal rate to determine automated treatment; it cannot function with a zero basal rate. A temporary zero basal rate can be achieved through the "Disconnect pump" function or through a combination of Disable Loop/Temp Basal Rate or Suspend Loop/Temp Basal Rate. The lowest basal rate allowed in **AAPS** is 0.05U/h. ## 在AAPS中選擇DASH -有**兩種方法**： +There are **two ways**: ### 選項 1：新安裝 -首次安裝**AAPS**時，**設定嚮導**將引導新用戶了解**AAPS**的主要功能和安裝要求。 當達到幫浦選擇時，選擇“DASH”。 +When installing **AAPS** for the first time, the **Setup Wizard** will guide new users through key features and installation requirements for **AAPS**. Select “DASH” when you reach Pump selection. ![Enable_Dash_1](../images/DASH_images/Enable_Dash/Enable_Dash_1.png) -如果有疑慮，你也可以選擇“虛擬幫浦”，稍後在設置**AAPS**後選擇“DASH”（請參見選項2）。 +When in doubt you can also select “Virtual Pump” and select “DASH” later, after setting up **AAPS** (see option 2). ### 選項 2：組態建置工具 -在現有安裝中，你可以從組態建置工具中選擇**DASH**幫浦： +On an existing installation you can select the **DASH** pump from the Config builder: -在左上角的**漢堡選單**中，選擇**組態建置工具（1）**\ ➜\ **幫浦**\ ➜\ **Dash**\ ➜\ 選擇**Dash**的**設置齒輪（3）**旁的**選項按鈕（2）**。 +On the top-left hand corner **hamburger menu** select **Config Builder (1)**\ ➜\ **Pump**\ ➜\ **Dash**\ ➜\ **Settings Gear (3)** by selecting the **radio button (2)** titled **Dash**. -選中**設定齒輪(3)**旁邊的**復選框(4)**將使DASH選單顯示為**AAPS**介面的標籤**DASH**。 勾選此框將方便你在使用**AAPS**時訪問DASH指令。 +Selecting the **checkbox (4)** next to the **Settings Gear (3)** will allow the DASH menu to be displayed as a tab in the **AAPS** interface titled **DASH**. Checking this box will facilitate your access to the DASH commands when using **AAPS**. -**注意：** 有一個更快速的方式可以在本文件的DASH設定部分中找到，訪問[**Dash設定**](#dash-settings)。 +**NOTE:** A faster way to access the [**Dash settings**](#dash-settings) can be found below in the DASH settings section of this document. ![Enable_Dash_3](../images/DASH_images/Enable_Dash/Enable_Dash_3.png) ### 驗證 Omnipod 驅動程式選擇 -要確認你在**AAPS**中已選擇DASH，請檢查是否已勾選該框(4)，然後**從總覽選項卡向左滑動**，你會在**AAPS**看到一個**DASH**標籤。 如果此框未勾選，則DASH標籤將位於左上角的漢堡選單中。 +To verify that you have selected the DASH in **AAPS**, if you have checked the box (4), **swipe to the left** from the **Overview** tab, where you will now see a **DASH** tab on **AAPS**. If this box is left unchecked, you’ll find the DASH tab in the hamburger menu upper left. ![Enable_Dash_4](../images/DASH_images/Enable_Dash/Enable_Dash_4.jpg) ## Dash 配置 -請**向左滑動**到**DASH**標籤，在那裡你將能管理所有 Pod 功能（在沒有註冊 Pod 會話的情況下，某些功能將不可用或不可見）： +Please **swipe left** to the **DASH** tab where you will be able to manage all pod functions (some of these functions are not enabled or visible without an active pod session): -![Refresh_LOGO](../images/DASH_images/Refresh_LOGO.png) “重新整理” Pod 的連接性和狀態，能夠靜音 Pod 在發出嗶聲時的警報。 +![Refresh_LOGO](../images/DASH_images/Refresh_LOGO.png) 'Refresh' pod connectivity and status, be able to silence pod alarms when the pod beeps -![POD_MGMT_LOGO](../images/DASH_images/POD_MGMT_LOGO.png) “ Pod 管理”（啟動、停用、播放測試嗶聲及 Pod 歷史） +![POD_MGMT_LOGO](../images/DASH_images/POD_MGMT_LOGO.png) 'Pod Management' (Activate, Deactivate, Play test beep, and Pod history) ### 註冊 Pod @@ -92,15 +98,15 @@ orphan: true ![Activate_Pod_1](../images/DASH_images/Activate_Pod/Activate_Pod_1.png) -​![Activate_Pod_2](../images/DASH_images/Activate_Pod/Activate_Pod_2.png) +​ ![Activate_Pod_2](../images/DASH_images/Activate_Pod/Activate_Pod_2.png) 2. 顯示**填充 Pod**畫面。 將至少 80 單位的胰島素注入新的 Pod，等聽到兩聲嗶聲，表示 Pod 準備就緒並可續繼將胰島素輸入完。 計算 3 天所需的胰島素總量時，請考慮 Pod 本身的排空會占用約 3-10 單位。 ![Activate_Pod_3](../images/DASH_images/Activate_Pod/Activate_Pod_3.png) ![Activate_Pod_4](../images/DASH_images/Activate_Pod/Activate_Pod_4.jpg) -確保新的 Pod 與運行**AAPS**的手機處於近距離內，然後單擊**下一步**按鈕。 +Ensure that the new pod and the phone running **AAPS** are within close proximity of each other and click the **Next** button. -**注意**: 如果出現錯誤提示_“找不到可用的 Pod 以進行啟動”_（這可能會發生），請不要驚慌。 點擊 **重試** 按鈕。 在大多數情況下，註冊將繼續成功進行。 +**NOTE**: if the error message below pops up _'Could not find an available pod for activation'_ (this can happen), do not panic. Click on the **Retry** button. In most situations activation will continue successfully. ![Activate_Pod_3](../images/DASH_images/Activate_pod_error.png) @@ -138,24 +144,24 @@ orphan: true ![Activate_Pod_14](../images/DASH_images/Activate_Pod/Activate_Pod_14.png) -​![Activate_Pod_15](../images/DASH_images/Activate_Pod/Activate_Pod_15.jpg) +​ ![Activate_Pod_15](../images/DASH_images/Activate_Pod/Activate_Pod_15.jpg) -在註冊 Pod 後匯出設置是一個好習慣。 每次更換藥量時應該進行匯出設置，並每月將匯出的檔案複製到你的雲端儲存。 請見[**匯出設定文件**](../Maintenance/ExportImportSettings.md)。 +It is good practice to export settings AFTER activating the pod. Export settings should be done at each pod change and once a month, copy the exported file to your internet drive. see [**Export settings Doc**](../Maintenance/ExportImportSettings.md). (OmnipodDASH-deactivate-pod)= ### 停用 Pod -在正常情況下，Pod 的預期壽命為三天（72 小時），並且在 Pod 過期警告後還有額外的 8 小時，總共可以使用 80 小時。 +Under normal circumstances, the expected lifetime of a pod is three days (72 hours) and an additional 8 hours after the pod expiration warning for a total of 80 hours of pod usage. -要停用 Pod（不論是過期還是 Pod 故障）： +To deactivate a pod (either from expiration or from a pod failure): 1. 進入 **DASH** 標籤，點擊 **POD 管理 (1)** 按鈕，然後在 **Pod 管理** 畫面中點擊 **停用 Pod (2)** 按鈕。 ![Deactivate_Pod_1](../images/DASH_images/Deactivate_Pod/Deactivate_Pod_1.jpg) -​![Deactivate_Pod_2](../images/DASH_images/Deactivate_Pod/Deactivate_Pod_2.png) +​ ![Deactivate_Pod_2](../images/DASH_images/Deactivate_Pod/Deactivate_Pod_2.png) 2. 在 **停用 Pod** 畫面上，點擊 **下一步** 按鈕開始停用 Pod 的流程。 你會收到來自 Pod 的確認嗶聲，表明停用成功。 @@ -180,9 +186,9 @@ orphan: true ### 恢復胰島素輸送 -**注意**：在**設定檔切換**期間，DASH 必須在設置新的基礎**設定檔**之前中斷送藥，因為送藥可能會被暫停。 在問題排除部分閱讀[**暫停交付**](#delivery-suspended)以獲取更多詳細資訊。 +**Note**: During **Profile Switches**, DASH must suspend delivery before setting the new basal **Profile** as delivery can be suspended. Read [**Delivery suspended**](#delivery-suspended) in the troubleshooting section for more details. -使用此指令指示目前暫停的活動 Pod 恢復胰島素輸送。 命令成功處理後，胰島素將根據當前時間從活動的基礎**設定檔**恢復正常送藥。 藥量將再次接受注射、**TB** 和**SMB**的命令。 +Use this command to instruct the active, currently suspended pod to resume insulin delivery. After the command is successfully processed, insulin will resume normal delivery using the current basal rate based on the current time from the active basal **Profile**. The pod will again accept commands for bolus, **TBR**, and **SMB**. 1. 進入 **DASH** 標籤，確認 **Pod 狀態 (1)** 欄位顯示 **已暫停**，然後按下 **恢復輸送 (2)** 按鈕以開始流程，指示目前的 Pod 恢復正常的胰島素輸送。 訊息 **恢復輸送** 將顯示在 **Pod 狀態 (3)** 欄位中。 @@ -198,9 +204,9 @@ orphan: true ### 靜音 Pod 警報 -*注意 - 僅當觸發 Pod 過期或低儲液量警報時，**靜音警報** 按鈕才會在 **DASH** 標籤上顯示。 如果未顯示靜音警報按鈕且你聽到 Pod 的嗶聲，請嘗試“重新整理 Pod 狀態”。* +*NOTE - The SILENCE ALERTS button is only available on the **DASH** tab when the pod expiration or low reservoir alert has been triggered. If the SILENCE ALERTS button is not visible and you hear beep sounds from the pod, try to 'Refresh pod status'.* -以下流程將向你展示當 Pod 的使用時間接近72小時（3天）到期的警告時，如何確認並關閉 Pod 的嗶聲。 此警告時間限制定義在 **距關閉時間的時數** Dash 警報設置中。 Pod 的最大使用壽命為 80 小時（3 天 8 小時），但 Insulet 建議不要超過 72 小時（3 天）限制。 +The process below will show you how to acknowledge and dismiss pod beeps when the active pod time reaches the warning time limit before the pod expiration of 72 hours (3 days). This warning time limit is defined in the **Hours before shutdown** Dash alerts setting. The maximum life of a pod is 80 hours (3 days 8 hours), however Insulet recommends not exceeding the 72 hours (3 days) limit. 1. 當達到定義的 **距關閉時間的時數** 警告時間限制時，Pod 會發出警告嗶聲，通知你即將過期並需要更換 Pod。 你可以在 **DASH** 標籤上進行驗證，**Pod 過期：** 欄位將顯示 Pod 的確切過期時間（註冊後 72 小時），且文字會在此時間過後變為 **紅色**。 在 **啟用 Pod 警報 (2)** 欄位下，狀態訊息會顯示 **Pod 即將過期**。 這也會觸發顯示 **靜音警報 (3)** 按鈕。 @@ -221,11 +227,11 @@ orphan: true ### 查看 Pod 歷史紀錄 -本節解釋如何檢視你的活動藥量歷史，並按不同操作類別進行篩選。 Pod 歷史工具允許你查看在其三天（72 - 80 小時）使用壽命期間提交到目前活動 Pod 的操作和結果。 +This section explains how to review your active pod history and filter by different action categories. The pod history tool allows you to view the actions and results committed to your currently active pod during its three days (72 - 80 hours) life. -此功能有助於驗證發送到 Pod 的注射劑量、臨時基礎率和基礎指令。 其餘類別對於排除故障和確定發生失敗前的事件順序很有幫助。 +This feature is helpful in verifying boluses, TBRs and basal commands that were sent to the pod. The remaining categories are useful for troubleshooting issues and determining the order of events that occurred leading up to a failure. -*注意：* **只有最後一個指令可能是不確定的**。 在**最後的“不確定”指令被“確認”或“拒絕”**之前，*不會發送新的指令*。 “修復”不確定指令的方法是按下 **“重新整理 Pod 狀態”**。 +*NOTE:* **Only the last command can be uncertain**. New commands *will not be sent* until the **last 'uncertain' command becomes 'confirmed' or 'denied'**. The way to 'fix' uncertain commands is to **'refresh pod status'**. 1. 進入 **DASH** 標籤，按下 **POD 管理 (1)** 按鈕以進入 **Pod 管理** 選單，然後按下 **Pod 歷史紀錄 (2)** 按鈕以進入 Pod 歷史紀錄畫面。 @@ -246,9 +252,9 @@ orphan: true ## DASH 標籤 -以下是主 AAPS 介面中 **DASH** 標籤的佈局說明及圖示和狀態欄位的含義。 +Below is an explanation of the layout and meaning of the icons and status fields on the **DASH** tab in the main AAPS interface. -*注意：如果 **DASH** 標籤的狀態欄位中顯示 (不確定)，則你需要按下重新整理按鈕來清除此訊息並重新整理 Pod 狀態。* +*NOTE: If any message in the **DASH** tab status fields report (uncertain), then you will need to press the Refresh button to clear it and refresh the pod status.* ![DASH_Tab_1](../images/DASH_images/DASH_Tab/DASH_Tab_1.png) @@ -283,23 +289,23 @@ orphan: true ### 按鈕 -![重新整理圖示](../images/DASH_images/Refresh_LOGO.png) ：向啟用的 Pod 發送重新整理指令以更新通訊。 +![Refresh_Icon](../images/DASH_images/Refresh_LOGO.png) : Sends a refresh command to the active pod to update communication. * 用於重新整理 Pod 狀態並消除顯示 (不確定) 訊息的狀態欄位。 * 請參閱下面的問題排除部分以獲取更多訊息。 -![POD 管理圖示](../images/DASH_images/POD_MGMT_LOGO.png) ：導航到 Pod 管理選單。 +![POD_MGMT_Icon](../images/DASH_images/POD_MGMT_LOGO.png) : Navigates to the Pod management menu. -![警報消音圖示](../images/DASH_images/ack_alert_logo.png) ：按下此按鈕可停用 Pod 警報嗶聲和通知（過期、儲液量低等）。 +![ack_alert_logo](../images/DASH_images/ack_alert_logo.png) : When pressed this will disable the pod alerts beeps and notifications (expiry, low reservoir..). * 該按鈕僅在 Pod 過期警告時間已過時顯示。 * 成功解除後，此圖示將不再顯示。 -![恢復圖示](../images/DASH_images/DASH_tab_icons/RESUME_Icon.png) ：恢復目前暫停的活動 Pod 胰島素輸送。 +![RESUME_Icon](../images/DASH_images/DASH_tab_icons/RESUME_Icon.png) : Resumes the currently suspended insulin delivery in the active pod. ### Pod 管理選單 -以下是通過按下**POD MGMT (1)**按鈕從**DASH**選單進入的**Pod 管理**菜單中圖示的含義。 +Below is the meaning of the icons on the **Pod Management** menu accessed by pressing **POD MGMT (1)** button from the **DASH** tab. ![DASH_Tab_2](../images/DASH_images/Deactivate_Pod/Deactivate_Pod_1.jpg) @@ -314,25 +320,25 @@ orphan: true ## Dash 設定 -你可以從左上角 **漢堡選單** 下的 **組態建置工具 (1)**\ ➜\ **幫浦**\ ➜\ **Dash**\ ➜\ **設定齒輪 (3)** 中進行 Dash 驅動設定，方法是選擇標題為 **Dash** 的 **單選按鈕 (2)**。 選擇**選框 (4)**旁邊的**設置齒輪 (3)**將允許 Dash 菜單在**AAPS**介面中作為標籤顯示，標題為**DASH**。 +The Dash driver settings are configurable from the top-left hand corner **hamburger menu** under **Config Builder (1)**\ ➜\ **Pump**\ ➜\ **Dash**\ ➜\ **Settings Gear (3)** by selecting the **radio button (2)** titled **Dash**. Selecting the **checkbox (4)** next to the **Settings Gear (3)** will allow the Dash menu to be displayed as a tab in the **AAPS** interface titled **DASH**. ![Dash_settings_1](../images/DASH_images/Enable_Dash/Enable_Dash_3.png) -**注意：** 查看 **Dash 設定** 的更快方式是查看 **DASH** 標籤右上角的 **三點選單 (1)** 並從下拉選單中選擇 **Dash 偏好設定 (2)**。 +**NOTE:** A faster way to access the **Dash settings** is by accessing the **3 dot menu (1)** in the upper right hand corner of the **DASH** tab and selecting **Dash preferences (2)** from the dropdown menu. ![Dash_settings_3](../images/DASH_images/Dash_settings/Dash_settings_3.png) -下方列出了設定組；大多數項目可透過切換開關啟用或停用： +The settings groups are listed below; you can enable or disable via a toggle switch for most entries described below: -*注意：星號 (\*) 表示預設為啟用。* +*NOTE: An asterisk (\*) denotes the default setting is enabled.* ### 確認嗶聲提示 ![Dash_settings_4](../images/DASH_images/Dash_settings/Dash_settings_4.jpg) -提供來自藥筒的確認聲音提示，用於注射、基礎輸注、SMB以及TBR輸送和變更。 +Provides confirmation beeps from the pod for bolus, basal, SMB, and TBR delivery and changes. * **啟用注射嗶聲：** 啟用或停用注射時的確認嗶聲。 * **啟用基礎率嗶聲：** 啟用或停用設置新基礎率、取消啟用的基礎率或更改目前基礎率時的確認嗶聲。 @@ -343,9 +349,9 @@ orphan: true ![Dash_settings_5](../images/DASH_images/Dash_settings/Dash_settings_5.jpg) -提供**AAPS**的藥量過期、關閉、低藥量的警報，根據所定義的門檻值單位。 +Provides **AAPS** alerts for pod expiration, shutdown, low reservoir based on the defined threshold units. -*請注意，Pod 觸發警報後，AAPS 通知將始終發出。 解除通知不會取消警報，除非啟用了自動確認 Pod 警報功能。 若要手動解除警報，你必須進入 **DASH** 標籤，並按下 **靜音警報按鈕**。* +*Note an AAPS notification will ALWAYS be issued for any alert after the initial communication with the pod since the alert was triggered. Dismissing the notification will NOT dismiss the alert UNLESS automatically acknowledge Pod alerts is enabled. To MANUALLY dismiss the alert you must visit the **DASH** tab and press the **Silence ALERTS button**.* * **啟用到期提醒：** 啟用或停用在達到設定的到期時間前的 Pod 到期提醒。 * **關閉前的時數：** 定義 Pod 關閉前的幾小時，這將觸發到期提醒警報。 @@ -356,9 +362,9 @@ orphan: true ![Dash_settings_6](../images/DASH_images/Dash_settings/Dash_settings_6.jpg) -通知部分允許使用者選擇其偏好的通知和手機音訊提醒，以便在無法確定 TBR、SMB 或注射及輸送暫停事件是否成功時收到警示。 +The Notification section allows the user to so select their preferred notifications and audible phone alerts when it is uncertain if TBR, SMB, or bolus, and delivery suspended events were successful. -*注意：這些僅是通知，沒有嗶聲警報。* +*NOTE: These are notifications only, no audible beep alerts are made.* * **已啟用不確定 TBR 通知的音效：** 啟用或停用此設定，以在 **AAPS** 無法確定 TBR 是否成功設定時觸發音訊提醒和視覺通知。 * **已啟用不確定 SMB 通知的音效：** 啟用或停用此設定，以在 **AAPS** 無法確定 SMB 是否成功輸送時觸發音訊提醒和視覺通知。 @@ -367,7 +373,7 @@ orphan: true ## 手動操作 (ACT) 標籤 -此標籤在主**AAPS**文件中有詳細說明，但這個標籤中有一些項目是針對 DASH 與管式幫浦的不同之處，特別是在應用新的藥量後的過程中。 +This tab is well documented in the main**AAPS**documentation but there are a few items on this tab that are specific to how the DASH differs from tube based pumps, especially after the processes of applying a new pod. 1. 前往主**AAPS**介面的**操作 (ACT)**標籤。 @@ -377,14 +383,14 @@ orphan: true ### 等級 -**胰島素等級** +**Insulin Level** -顯示的胰島素水平是 DASH 報告的數量。 然而，Pod 僅在儲液器低於 50 單位時報告實際的胰島素儲液量。 在此之前，會顯示「超過 50 單位」。 報告的數量並不精準：當 Pod 報告「空」時，大多數情況下儲液器仍有一些剩餘的胰島素單位。 DASH 概覽標籤將顯示如下所述： +Insulin level displayed is the amount reported by DASH. However, the pod only reports the actual insulin reservoir level when it is below 50 units. Until then “Above 50 units” will be displayed. The amount reported is not exact: when the pod reports ‘empty’ in most cases the reservoir will still have some additional units of insulin left. The DASH overview tab will display as described the below: * **超過 50 單位** - 藥量報告目前儲存庫中有超過 50 單位。 * **少於 50 單位** - Pod 報告的儲液器中剩餘的胰島素量。 -附加說明： +Additional note: * **SMS** - 短訊回報數值為 50+ 單位。 * **Nightscout** - 當超過 50 單位時，向 Nightscout 上傳數值為 50（版本 14.07 及更早版本）。 更新版本將在超過 50 單位時報告數值為 50+。 @@ -402,43 +408,43 @@ orphan: true - 如果**AAPS**無法自行恢復送藥（如果藥量無法連線、聲音被靜音等情況會發生），藥量每分鐘將發出 4 次嗶聲，持續 3 分鐘，然後如果送藥暫停超過 20 分鐘將每 15 分鐘重複這個過程。 * 對於未確認的指令，「重新整理 Pod 狀態」應能確認/否認他們。 -<**注意：** 當你聽到 Pod 發出嗶聲時，不要假設胰島素會繼續注射而不檢查手機，注射可能已暫停，**所以一定要檢查！** +**Note:** When you hear beeps from the pod, do not assume that delivery will continue without checking the phone, delivery might stay suspended, **so you need to check !** ### Pod 故障 -Pod 會因多種問題偶爾發生故障，包括 Pod 本身的硬體問題。 最佳做法是不要向 Insulet 報告，因為 AAPS 並非經過認證的使用情況。 一份故障代碼列表可在 [**這裡找到**](https://github.com/openaps/openomni/wiki/Fault-event-codes)，以幫助確定原因。 +Pods fail occasionally due to a variety of issues, including hardware issues with the Pod itself. It is best practice not to call these into Insulet, since AAPS is not an approved use case. A list of fault codes can be [**found here**](https://github.com/openaps/openomni/wiki/Fault-event-codes) to help determine the cause. ### 防止 49 號錯誤 Pod 故障 -此故障與指令的 Pod 狀態不正確或胰島素輸送指令中的錯誤有關。 這是當驅動程式和 Pod 對實際狀態存在分歧時發生的情況。 Pod（出於內建安全措施）隨後對不可恢復的錯誤代碼 49（0x31）作出反應，最終產生所謂的「尖叫聲」：那聲長且令人惱怒的嗶聲，只有在在 Pod 背面適當位置打個洞才能停止。 「49 Pod 故障」的確切原因通常難以追溯。 在某些情況下，這種故障可能發生（例如應用程式崩潰、運作開發版本或重新安裝）。 +This failure is related to an incorrect pod state for a command or an error during an insulin delivery command. This is when the driver and Pod disagree on the actual state. The Pod (out of a built-in safety measure) then reacts with an unrecoverable error code 49 (0x31) ending up with what is know as a “screamer”: the long irritating beep that can only be stopped by punching a hole at the appropriate location at the back of the Pod. The exact origin of a “49 pod failure” often is hard to trace. In situations that are suspected for this failure to occur (for instance on application crashes, running a development version or re-installation). ### 幫浦無法連線警報 -當無法在預設的時間內與 Pod 建立通訊時，將會發出「無法到達幫浦」的警報。 可透過進入右上角的三點選單，選擇 **偏好設定**\ ➜\ **本地警報**\ ➜\ **無法到達幫浦的門檻值 [分鐘]** 來配置無法到達幫浦的警報。 建議設置的值是**120** 分鐘後提醒。 +When no communication can be established with the pod for a preconfigured time a “Pump unreachable” alert will be raised. Pump unreachable alerts can be configured by going to the top right-hand side three-dot menu, selecting **Preferences**\ ➜\ **Local Alerts**\ ➜\ **Pump unreachable threshold [min]**. Recommended value is alerting after **120** minutes. ### 匯出設定 -匯出**AAPS**設置可讓你恢復所有設置，可能更重要的是，恢復所有目標。 你可能需要將設置恢復至「最後一次正常運作的狀況」，或在卸載/重新安裝**AAPS**後，或在手機遺失的情況下，在新手機上重新安裝。 +Exporting **AAPS** settings enables you to restore all your settings, and maybe more importantly, all your Objectives. You may need to restore settings to the “last known working situation” or after uninstalling/reinstalling **AAPS** or in case of phone loss, reinstalling on the new phone. -注意：匯出的設定中包含啟用的 Pod 資訊。 如果你匯入了「舊」的匯出檔案，你的目前 Pod 會「失效」。 沒有其他選擇。 在某些情況下（如_程式化_的手機更換），你可能需要使用匯出的檔案來恢復**AAPS'**設置**同時保持當前活動的藥量**。 在這種情況下，重要的是需要包含目前啟用 Pod 的最新匯出設定檔案。 +Note: The active pod information is included in the exported settings. If you import an "old" exported file, your actual pod will "die". There is no other alternative. In some cases (like a _programmed_ phone change), you may need to use the exported file to restore **AAPS'** settings **while keeping the current active Pod**. In this case it is important to only use the recently exported settings file containing the pod currently active. -**啟動 Pod 後立即匯出是一種好習慣**。 這樣，你將能夠在發生問題時恢復當前活動的藥量。 例如，當你更換備用手機時。 +**It is good practice to do an export immediately after activating a pod**. This way you will always be able to restore the current active pod in case of a problem. For instance when moving to another backup phone. -定期將匯出的設定檔案複製到安全的地方（例如雲端硬碟），這樣在需要時，任何手機都能存取（例如手機遺失或實際手機的出廠重置情況下）。 +Regularly copy your exported settings to a safe place (as a cloud drive) that can be accessible by any phone when needed (e.g. in case of a phone loss or factory reset of the actual phone). ### 匯入設定 -**警告** 請注意，匯入設定可能會匯入過時的 Pod 狀態。 結果會是失去已啟用的 Pod ！ （參見 **匯出設定**）。 最好僅在沒有其他選擇時才嘗試這樣做。 +**WARNING** Please note that importing settings will possibly import an outdated Pod status. As a result, there is a risk of losing the active Pod! (see **Exporting Settings**). It is better to only try it when no other options are available. -當匯入具有啟用的 Pod 設定時，請確保匯出是在目前啟用的 Pod 下進行的。 +When importing settings with an active Pod, make sure the export was done with the currently active pod. -**在有啟用 Pod 的情況下匯入：**（你有失去 Pod 的風險！） +**Importing while on an active Pod:** (you risk losing the Pod!) 1. 確保你匯入的設定是最近在目前啟用 Pod 下匯出的。 2. 匯入你的設定。 3. 檢查所有偏好設定。 -**匯入（沒有啟用的 Pod 連線）** +**Importing (no active Pod session)** 1. 匯入任何最近的匯出應該可以工作（見上文）。 2. 匯入你的設定。 @@ -447,15 +453,15 @@ Pod 會因多種問題偶爾發生故障，包括 Pod 本身的硬體問題。 ### 匯入包含非活動 Pod 狀態的設定 -當匯入包含已不再啟用的 Pod 資料時，AAPS 將嘗試與其連線，這顯然會失敗。 在這種情況下，你無法啟動新 Pod。 +When importing settings containing data for a Pod that is no longer active, AAPS will try to connect with it, which will obviously fail. You can not activate a new Pod in this situation. -要移除舊的藥量會話，請「嘗試」停用藥量。 停用將失敗。 選擇「重試」。 在第二次或第三次重試後，你將獲得移除 Pod 的選項。 一旦舊藥量被移除，你將能夠啟動新的藥量。 +To remove the old pod session “try” to de-activate the Pod. The de-activation will fail. Select “Retry”. After the second or third retry you will get the option to remove the pod. Once the old pod is removed you will be able to activate a new pod. ### 重新安裝 AAPS -卸載**AAPS**時，你將失去所有的設置、目標和當前的藥量會話。 為了恢復他們，請確保有一個最近匯出的設定檔案可用！ +When uninstalling**AAPS** you will lose all your settings, objectives and the current Pod session. To restore them make sure you have a recent exported settings file available! -當在活動藥量中時，請確保你有當前藥量會話的匯出，否則在匯入舊設置時將失去目前的活動藥量。 +When on an active Pod, make sure that you have an export for the current pod session or you will lose the currently active pod when importing older settings. 1. 匯出你的設定並將副本存儲在安全的地方。 2. 卸載**AAPS**並重新啟動你的手機。 @@ -467,7 +473,7 @@ Pod 會因多種問題偶爾發生故障，包括 Pod 本身的硬體問題。 ### 更新 AAPS 至新版本 -在大多數情況下，無需卸載。 你可以透過啟動新版本的安裝進行「就地」安裝。 這在啟用 Pod 在使用期間也是可以的。 +In most cases there is no need to uninstall. You can do an “in-place” install by starting the installation for the new version. This is also possible when on an active Pod session. 1. 匯出你的設定。 2. 安裝新的**AAPS**版本。 @@ -477,7 +483,7 @@ Pod 會因多種問題偶爾發生故障，包括 Pod 本身的硬體問題。 ### Omnipod 驅動程式警報 -請注意，Omnipod Dash 驅動程式會在**首頁總覽標籤**中顯示各種獨特的警報，其中大多數是資訊性的，可以忽略，而有些會提供使用者解決觸發警報原因的操作。 你可能會遇到的主要警報總結如下： +Please note that the Omnipod Dash driver presents a variety of unique alerts on the **Overview tab**, most of them are informational and can be dismissed while some provide the user with an action to take to resolve the cause of the triggered alert. A summary of the main alerts that you may encounter is listed below: * 未偵測到啟動的幫浦會話。 按下**稍後提醒**可以暫時忽略此警報，但只要未啟動新 Pod，他就會持續觸發。 當此警報啟動後，會自動靜音。 * 藥量已暫停 資訊警報，藥量已被暫停。 @@ -487,7 +493,7 @@ Pod 會因多種問題偶爾發生故障，包括 Pod 本身的硬體問題。 ## 有關 DASH 的幫助資訊 -所有 DASH 的開發工作都是由社區以**志願者**的身份進行的；請記住這一點，在要求協助之前使用以下準則： +All of the development work for the DASH is done by the community on a **volunteer** basis; please keep this in mind and use the following guidelines before requesting assistance: - **等級 0：** 閱讀此文件的相關部分，以確保你了解遇到困難的功能應如何工作。 - **等級 1：** 如果你仍然遇到無法解決的問題，請使用[此邀請鏈接](https://discord.gg/4fQUWHZ4Mw)進入**Discord**的*#AAPS* 頻道。 diff --git a/docs/CROWDIN/zh_TW/CompatiblePumps/OmnipodEros.md b/docs/CROWDIN/zh_TW/CompatiblePumps/OmnipodEros.md index a9b5f55f301e..ff7997a63425 100644 --- a/docs/CROWDIN/zh_TW/CompatiblePumps/OmnipodEros.md +++ b/docs/CROWDIN/zh_TW/CompatiblePumps/OmnipodEros.md @@ -43,7 +43,7 @@ orphan: true **安全第一** - 不要在無法從錯誤中恢復的環境中嘗試此過程（必備項包括額外的 pod、胰島素、已充電的 RileyLink 和手機設備）。 -**當 AAPS Omnipod 驅動程式啟用你的 pod 後，你的 Omnipod PDM 將無法再運作**。 以往你使用 Omnipod PDM 向 Omnipod Eros pod 發送指令。 Omnipod Eros pod 只允許單一裝置向其發送通訊。 從那時起，成功啟動 Pod 的裝置將是唯一能夠與其通訊的裝置。 這意味著你透過 AAPS Omnipod 驅動程式和 RileyLink 啟用了 Omnipod Eros pod，**你將無法再使用你的 PDM 與 pod 通訊**。 AAPS Omnipod 驅動程式與 RileyLink 現在是你的替代 PDM。 *這並不意味著你應該丟掉你的 PDM，建議保留他作為備用並在 AAPS 運作不正常時使用。* +**當 AAPS Omnipod 驅動程式啟用你的 pod 後，你的 Omnipod PDM 將無法再運作**。 以往你使用 Omnipod PDM 向 Omnipod Eros pod 發送指令。 Omnipod Eros pod 只允許單一裝置向其發送通訊。 The device that successfully activates the pod is the only device allowed to communicate with it from that point forward. 這意味著你透過 AAPS Omnipod 驅動程式和 RileyLink 啟用了 Omnipod Eros pod，**你將無法再使用你的 PDM 與 pod 通訊**。 AAPS Omnipod 驅動程式與 RileyLink 現在是你的替代 PDM。 *這並不意味著你應該丟掉你的 PDM，建議保留他作為備用並在 AAPS 運作不正常時使用。* **你可以配置多個 RileyLink，但一次只能選擇一個 RileyLink 與 pod 通訊。** AAPS Omnipod 驅動程式支援在 RileyLink 配置中添加多個 RileyLink，但一次只能選擇一個 RileyLink 用來發送和接收通訊。 @@ -191,7 +191,7 @@ orphan: true 在正常情況下，幫浦的壽命應為三天（72 小時），並在提示幫浦過期警告後額外持續8小時，總計80小時的幫浦使用。 -要停用 Pod（不論是過期還是 Pod 故障）： +To deactivate a pod (either from expiration or from a pod failure): 1. 轉到 **Omnipod (POD)** 標籤，點擊 **幫浦管理 (1)** 按鈕，在 **幫浦管理** 畫面上點擊 **停用幫浦 (2)** 按鈕。 @@ -245,7 +245,7 @@ orphan: true #### 恢復胰島素輸送 -使用此指令指示目前暫停的活動 Pod 恢復胰島素輸送。 指令成功處理後，胰島素將根據目前時間並使用活動基礎率設定檔恢復正常輸送。 Pod 將再次接受注射、TBR 和 SMB 的指令。 +Use this command to instruct the active, currently suspended pod to resume insulin delivery. 指令成功處理後，胰島素將根據目前時間並使用活動基礎率設定檔恢復正常輸送。 Pod 將再次接受注射、TBR 和 SMB 的指令。 1. 進入**Omnipod（POD）**頁籤，確保** POD 狀態（1）**欄位顯示**已暫停**，然後按下**恢復輸送（2）**按鈕以啟動流程，指示目前 POD 恢復正常的胰島素輸送。 **恢復輸送**訊息將顯示在** POD 狀態（3）**欄位，表示 RileyLink 正在積極向暫停的 POD 發送指令。 @@ -574,7 +574,7 @@ Omnipod 驅動程式設置可透過左上角的**漢堡選單**中的**設置生 ![Omnipod_設置_2](../images/omnipod/Omnipod_Settings_2.png) -下方列出了設定組；大多數項目可透過切換開關啟用或停用： +The settings groups are listed below; you can enable or disable via a toggle switch for most entries described below: ![Omnipod_設置_3](../images/omnipod/Omnipod_Settings_3.png) @@ -595,7 +595,7 @@ Omnipod 驅動程式設置可透過左上角的**漢堡選單**中的**設置生 ### 確認嗶聲提示 -提供來自藥筒的確認聲音提示，用於注射、基礎輸注、SMB以及TBR輸送和變更。 +Provides confirmation beeps from the pod for bolus, basal, SMB, and TBR delivery and changes. - **\*注射嗶聲啟用：**啟用或停用在注射送達時的確認嗶聲聲。 - **\*基礎率嗶聲啟用：**啟用或停用在設定新基礎率、取消啟動基礎率或更改目前基礎率時的確認嗶聲聲。 @@ -606,7 +606,7 @@ Omnipod 驅動程式設置可透過左上角的**漢堡選單**中的**設置生 根據設定的門檻值單位，提供 AAPS 警告和 Nightscout 通知以提示幫浦到期、關閉或低庫存。 -*請注意，Pod 觸發警報後，AAPS 通知將始終發出。 解除通知不會取消警報，除非啟用了自動確認 Pod 警報功能。 要手動解除警告，你必須查看 Omnipod (幫浦) 分頁並按下確認警告按鈕。* +*Note an AAPS notification will ALWAYS be issued for any alert after the initial communication with the pod since the alert was triggered. Dismissing the notification will NOT dismiss the alert UNLESS automatically acknowledge Pod alerts is enabled. 要手動解除警告，你必須查看 Omnipod (幫浦) 分頁並按下確認警告按鈕。* - **\*到期提醒啟用：**啟用或停用設定的幫浦到期提醒，當到達設定的關機時間前的幾個小時時觸發。 - **關閉前的時數：** 定義 Pod 關閉前的幾小時，這將觸發到期提醒警報。 @@ -618,7 +618,7 @@ Omnipod 驅動程式設置可透過左上角的**漢堡選單**中的**設置生 當不確定 TBR、SMB 或注射事件是否成功時，提供 AAPS 通知和手機警報。 -*注意：這些僅是通知，沒有嗶聲警報。* +*NOTE: These are notifications only, no audible beep alerts are made.* - **啟用不確定 TBR 通知音效：** 啟用或停用此設定，以在 AAPS 不確定 TBR 是否成功設置時觸發提示音和視覺通知。 - **\*不確定 SMB 通知聲音啟用：**啟用或停用此設置以在 AAPS 不確定 SMB 是否成功送達時觸發警報聲和視覺通知。 @@ -690,7 +690,7 @@ Omnipod 驅動程式設置可透過左上角的**漢堡選單**中的**設置生 ### 層級 -**胰島素等級** +**Insulin Level** Omnipod Eros 幫浦中的胰島素量報告並不精準。 這是因為無法確定幫浦中實際注入了多少胰島素，只知道當填充幫浦時觸發了兩次嗶聲，這表示已注入超過 85 單位。 一個幫浦最多可容納 200 單位。 啟動過程也會引入一些變化，因為這並不是一個精準的過程。 考慮到這些因素，Omnipod 驅動程式已經編寫為盡可能準確地估算幫浦內剩餘的胰島素量。 @@ -716,11 +716,11 @@ Omnipod Eros 幫浦中的胰島素量報告並不精準。 這是因為無法 ### Pod 故障 -Pod 會因多種問題偶爾發生故障，包括 Pod 本身的硬體問題。 最佳做法是不要向 Insulet 報告，因為 AAPS 並非經過認證的使用情況。 你可以在[這裡](https://github.com/openaps/openomni/wiki/Fault-event-codes)找到錯誤代碼列表，以幫助確定原因。 +Pods fail occasionally due to a variety of issues, including hardware issues with the Pod itself. It is best practice not to call these into Insulet, since AAPS is not an approved use case. 你可以在[這裡](https://github.com/openaps/openomni/wiki/Fault-event-codes)找到錯誤代碼列表，以幫助確定原因。 ### 防止 49 號錯誤 Pod 故障 -此故障與指令的 Pod 狀態不正確或胰島素輸送指令中的錯誤有關。 我們建議使用者切換至 Nightscout 客戶端，並在**設置生成器**➜**一般**➜**NSClient**➜**齒輪圖示**➜**進階設定**中**僅上傳 (停用同步)**，以防止可能的故障。 +This failure is related to an incorrect pod state for a command or an error during an insulin delivery command. 我們建議使用者切換至 Nightscout 客戶端，並在**設置生成器**➜**一般**➜**NSClient**➜**齒輪圖示**➜**進階設定**中**僅上傳 (停用同步)**，以防止可能的故障。 ### 幫浦無法連線警報 @@ -739,7 +739,7 @@ Pod 會因多種問題偶爾發生故障，包括 Pod 本身的硬體問題。 ### Omnipod 驅動程式警報 -請注意，Omnipod 驅動程式在**首頁總覽分頁**中會呈現各種獨特的警報，其中大多數是資訊性的，可以忽略，然而有些會要求使用者採取行動以解決警報原因。 你可能會遇到的主要警報總結如下： +請注意，Omnipod 驅動程式在**首頁總覽分頁**中會呈現各種獨特的警報，其中大多數是資訊性的，可以忽略，然而有些會要求使用者採取行動以解決警報原因。 A summary of the main alerts that you may encounter is listed below: #### 沒有啟動幫浦 diff --git a/docs/CROWDIN/zh_TW/GettingHelp/GeneralTroubleshooting.md b/docs/CROWDIN/zh_TW/GettingHelp/GeneralTroubleshooting.md index 35320d0cb979..f82007ba3cb1 100644 --- a/docs/CROWDIN/zh_TW/GettingHelp/GeneralTroubleshooting.md +++ b/docs/CROWDIN/zh_TW/GettingHelp/GeneralTroubleshooting.md @@ -37,14 +37,37 @@ * [SMS 指令](#SMSCommands-troubleshooting) -### 頻繁的藍牙連線問題 +### Frequent Bluetooth connection problems -這可能會發生在各種幫浦上。 除了將 AAPS 排除在任何電池優化之外，你還可以將系統的藍牙應用程式排除在電池優化之外。 這在某些情況下有幫助。 根據你使用的手機，你會以不同方式找到藍牙應用程式。 +#### Android 15 + +```{warning} +Developers are working on this issue impacting **AAPS** on some Samsung and Pixel phones. +``` + +After upgrading Android or moving to a recent phone, **AAPS** frequently loses Bluetooth connection to the pump. The problem disappears temporarily when restarting the phone. If the phone runs Android 15, you can try to enable the following: + +1) **Open preferences** by clicking the three-dot menu on the top right side of the home screen. + + +![打開偏好設定](../images/Pref2020_Open2.png) + +2. Scroll down and open the **Confirmation beeps** / **Advanced** submenu. Enable **Bond BT device on Android 15+**. + + ![BondBT](../images/troubleshooting/BondBT.png) + +3. If the pump asks for a pairing request, accept it. + +4. Restart your phone. + +#### Battery optimization + +這可能會發生在各種幫浦上。 Apart from excluding AAPS from any battery optimization, you can also exclude the system Bluetooth app from battery optimization. 這在某些情況下有幫助。 Depending on the phone you use, you will find the Bluetooth app differently. 這裡是一些如何在特定 Android 手機上找到他們的範例。 -#### Pixel 手機（原生 Android） +##### Pixel phones (stock Android) * 進入 Android 設定，選擇「應用程式」。 @@ -67,7 +90,7 @@ ![藍牙電池優化](../images/troubleshooting/pixel/04_btunrestricted.png) -#### Samsung 手機 +##### Samsung 手機 * 進入 Android 設定，選擇「應用程式」 diff --git a/docs/CROWDIN/zh_TW/Maintenance/UpdateAaps3204.md b/docs/CROWDIN/zh_TW/Maintenance/UpdateAaps3204.md index 3e53d122a362..d2ec28d2f4b9 100644 --- a/docs/CROWDIN/zh_TW/Maintenance/UpdateAaps3204.md +++ b/docs/CROWDIN/zh_TW/Maintenance/UpdateAaps3204.md @@ -67,7 +67,7 @@ Gradle版本與源代碼相連結，下載/更新源代碼時，你將始終獲 此頁面提供 **新** 與舊 (**Classic**) Android Studio 使用者介面的範例圖片。 ``` -## 更新 3.2.0.x 至 3.2.0.4 的概覽 +## 更新 3.2.0.x 至 3.2.0.4 的總覽 ```{contents} Steps for updating to 3.2.0.4 :depth: 1 diff --git a/docs/CROWDIN/zh_TW/images/troubleshooting/BondBT.png b/docs/CROWDIN/zh_TW/images/troubleshooting/BondBT.png new file mode 100644 index 000000000000..96b2fb272d90 Binary files /dev/null and b/docs/CROWDIN/zh_TW/images/troubleshooting/BondBT.png differ diff --git a/docs/CROWDIN/zh_TW/images/troubleshooting/samsung/01_BondBT_20250526.png b/docs/CROWDIN/zh_TW/images/troubleshooting/samsung/01_BondBT_20250526.png new file mode 100644 index 000000000000..74c3525959ed Binary files /dev/null and b/docs/CROWDIN/zh_TW/images/troubleshooting/samsung/01_BondBT_20250526.png differ diff --git a/docs/CROWDIN/zh_TW/images/troubleshooting/samsung/02_BondBT_20250526.png b/docs/CROWDIN/zh_TW/images/troubleshooting/samsung/02_BondBT_20250526.png new file mode 100644 index 000000000000..444013b29146 Binary files /dev/null and b/docs/CROWDIN/zh_TW/images/troubleshooting/samsung/02_BondBT_20250526.png differ diff --git a/docs/CROWDIN/zh_TW/images/troubleshooting/samsung/03_BondBT_20250526.png b/docs/CROWDIN/zh_TW/images/troubleshooting/samsung/03_BondBT_20250526.png new file mode 100644 index 000000000000..9caa7a484581 Binary files /dev/null and b/docs/CROWDIN/zh_TW/images/troubleshooting/samsung/03_BondBT_20250526.png differ diff --git a/docs/CROWDIN/zh_TW/images/troubleshooting/samsung/04_BondBT_20250526.png b/docs/CROWDIN/zh_TW/images/troubleshooting/samsung/04_BondBT_20250526.png new file mode 100644 index 000000000000..b25c1469f58e Binary files /dev/null and b/docs/CROWDIN/zh_TW/images/troubleshooting/samsung/04_BondBT_20250526.png differ