diff --git a/docs/CROWDIN/cs/CompatiblePumps/Equil5.3.md b/docs/CROWDIN/cs/CompatiblePumps/Equil5.3.md index aae922872e06..e696d6a409bf 100644 --- a/docs/CROWDIN/cs/CompatiblePumps/Equil5.3.md +++ b/docs/CROWDIN/cs/CompatiblePumps/Equil5.3.md @@ -1,4 +1,4 @@ -# Equil 5.3 +# Equil These instructions are for configuring the Equil insulin pump. @@ -9,7 +9,7 @@ These instructions are for configuring the Equil insulin pump. ## Hardwarové a softwarové požadavky * **Compatible Equil hardware** -§todo + Currently Equil 5.3 and 5.4 is supported * [Version 3.3.0.0](#version3300) or newer of AAPS @@ -31,4 +31,6 @@ Navigate to the Equil Tab and press **Pair Equil Patch Pump**. ![activate2.png](../images/Equil/activate2.png) -![activate3.png](../images/Equil/activate3.png) \ No newline at end of file +![activate3.png](../images/Equil/activate3.png) + +If you set different password than default 0000 (recommended for your safety), do not forget to store this password on a safe place. This password is stored to the pump. Then this password is asked on every next pairing attempt until you do proper unpairing in AAPS. This makes the pump also unusable with original PDA until you unpair pump from AAPS. diff --git a/docs/CROWDIN/de/CompatiblePumps/Equil5.3.md b/docs/CROWDIN/de/CompatiblePumps/Equil5.3.md index e43bf4771b0a..6cb8e374d46e 100644 --- a/docs/CROWDIN/de/CompatiblePumps/Equil5.3.md +++ b/docs/CROWDIN/de/CompatiblePumps/Equil5.3.md @@ -1,4 +1,4 @@ -# Equil 5.3 +# Equil Diese Anleitung führt Dich durch die Konfiguration der Equil-Insulinpumpe. @@ -7,15 +7,15 @@ Diese Anleitung führt Dich durch die Konfiguration der Equil-Insulinpumpe. §todo ## Hardware- und Software-Anforderungen -* **Kompatible Equil-Hardware** +* **Compatible Equil hardware** -§todo + Currently Equil 5.3 and 5.4 is supported -* AAPS-[Version 3.3.0.0](#version3300) oder neuer +* [Version 3.3.0.0](#version3300) or newer of AAPS ### Equil-Insulinpumpe auswählen -Wähle in [Konfiguration > Pumpe](#Config-Builder-pump), **Equil 5.3** aus. +In [Config Builder > Pump](#Config-Builder-pump), switch to **Equil 5.3**. ### Einstellungen @@ -23,7 +23,7 @@ Wähle in [Konfiguration > Pumpe](#Config-Builder-pump), **Equil 5.3** aus. ### Patch aktivieren -Navigiere zum Equil-Tab und tippe auf **Equil-Patch-Pumpe koppeln**. +Navigate to the Equil Tab and press **Pair Equil Patch Pump**. ![overview.png](../images/Equil/overview.png) @@ -31,4 +31,6 @@ Navigiere zum Equil-Tab und tippe auf **Equil-Patch-Pumpe koppeln**. ![activate2.png](../images/Equil/activate2.png) -![activate3.png](../images/Equil/activate3.png) \ No newline at end of file +![activate3.png](../images/Equil/activate3.png) + +If you set different password than default 0000 (recommended for your safety), do not forget to store this password on a safe place. This password is stored to the pump. Then this password is asked on every next pairing attempt until you do proper unpairing in AAPS. This makes the pump also unusable with original PDA until you unpair pump from AAPS. diff --git a/docs/CROWDIN/el/CompatiblePumps/Equil5.3.md b/docs/CROWDIN/el/CompatiblePumps/Equil5.3.md index 5d3d60307e62..0a9c1277034d 100644 --- a/docs/CROWDIN/el/CompatiblePumps/Equil5.3.md +++ b/docs/CROWDIN/el/CompatiblePumps/Equil5.3.md @@ -1,4 +1,4 @@ -# Equil 5.3 +# Equil These instructions are for configuring the Equil insulin pump. @@ -9,7 +9,7 @@ These instructions are for configuring the Equil insulin pump. ## Hardware and Software Requirements * **Compatible Equil hardware** -§todo + Currently Equil 5.3 and 5.4 is supported * [Version 3.3.0.0](#version3300) or newer of AAPS @@ -31,4 +31,6 @@ Navigate to the Equil Tab and press **Pair Equil Patch Pump**. ![activate2.png](../images/Equil/activate2.png) -![activate3.png](../images/Equil/activate3.png) \ No newline at end of file +![activate3.png](../images/Equil/activate3.png) + +If you set different password than default 0000 (recommended for your safety), do not forget to store this password on a safe place. This password is stored to the pump. Then this password is asked on every next pairing attempt until you do proper unpairing in AAPS. This makes the pump also unusable with original PDA until you unpair pump from AAPS. diff --git a/docs/CROWDIN/es/CompatiblePumps/Equil5.3.md b/docs/CROWDIN/es/CompatiblePumps/Equil5.3.md index dcc87cc664b4..c33b3a80752f 100644 --- a/docs/CROWDIN/es/CompatiblePumps/Equil5.3.md +++ b/docs/CROWDIN/es/CompatiblePumps/Equil5.3.md @@ -1,4 +1,4 @@ -# Equil 5.3 +# Equil These instructions are for configuring the Equil insulin pump. @@ -9,7 +9,7 @@ These instructions are for configuring the Equil insulin pump. ## Hardware and Software Requirements * **Compatible Equil hardware** -§todo + Currently Equil 5.3 and 5.4 is supported * [Version 3.3.0.0](#version3300) or newer of AAPS @@ -31,4 +31,6 @@ Navigate to the Equil Tab and press **Pair Equil Patch Pump**. ![activate2.png](../images/Equil/activate2.png) -![activate3.png](../images/Equil/activate3.png) \ No newline at end of file +![activate3.png](../images/Equil/activate3.png) + +If you set different password than default 0000 (recommended for your safety), do not forget to store this password on a safe place. This password is stored to the pump. Then this password is asked on every next pairing attempt until you do proper unpairing in AAPS. This makes the pump also unusable with original PDA until you unpair pump from AAPS. diff --git a/docs/CROWDIN/fr/CompatiblePumps/Equil5.3.md b/docs/CROWDIN/fr/CompatiblePumps/Equil5.3.md index d40a1cc9744e..af51231fdb07 100644 --- a/docs/CROWDIN/fr/CompatiblePumps/Equil5.3.md +++ b/docs/CROWDIN/fr/CompatiblePumps/Equil5.3.md @@ -1,4 +1,4 @@ -# Equil 5.3 +# Equil These instructions are for configuring the Equil insulin pump. @@ -9,7 +9,7 @@ These instructions are for configuring the Equil insulin pump. ## Configuration matérielle et logicielle requise * **Compatible Equil hardware** -§todo + Currently Equil 5.3 and 5.4 is supported * [Version 3.3.0.0](#version3300) or newer of AAPS @@ -31,4 +31,6 @@ Navigate to the Equil Tab and press **Pair Equil Patch Pump**. ![activate2.png](../images/Equil/activate2.png) -![activate3.png](../images/Equil/activate3.png) \ No newline at end of file +![activate3.png](../images/Equil/activate3.png) + +If you set different password than default 0000 (recommended for your safety), do not forget to store this password on a safe place. This password is stored to the pump. Then this password is asked on every next pairing attempt until you do proper unpairing in AAPS. This makes the pump also unusable with original PDA until you unpair pump from AAPS. diff --git a/docs/CROWDIN/he/CompatiblePumps/Equil5.3.md b/docs/CROWDIN/he/CompatiblePumps/Equil5.3.md index 7fe69ce63bb8..6481feeea210 100644 --- a/docs/CROWDIN/he/CompatiblePumps/Equil5.3.md +++ b/docs/CROWDIN/he/CompatiblePumps/Equil5.3.md @@ -1,4 +1,4 @@ -# Equil 5.3 +# Equil These instructions are for configuring the Equil insulin pump. @@ -9,7 +9,7 @@ These instructions are for configuring the Equil insulin pump. ## Hardware and Software Requirements * **Compatible Equil hardware** -§todo + Currently Equil 5.3 and 5.4 is supported * [Version 3.3.0.0](#version3300) or newer of AAPS @@ -31,4 +31,6 @@ Navigate to the Equil Tab and press **Pair Equil Patch Pump**. ![activate2.png](../images/Equil/activate2.png) -![activate3.png](../images/Equil/activate3.png) \ No newline at end of file +![activate3.png](../images/Equil/activate3.png) + +If you set different password than default 0000 (recommended for your safety), do not forget to store this password on a safe place. This password is stored to the pump. Then this password is asked on every next pairing attempt until you do proper unpairing in AAPS. This makes the pump also unusable with original PDA until you unpair pump from AAPS. diff --git a/docs/CROWDIN/ko/CompatiblePumps/Equil5.3.md b/docs/CROWDIN/ko/CompatiblePumps/Equil5.3.md index 51d0d1f9014f..cf4ec934d32a 100644 --- a/docs/CROWDIN/ko/CompatiblePumps/Equil5.3.md +++ b/docs/CROWDIN/ko/CompatiblePumps/Equil5.3.md @@ -1,4 +1,4 @@ -# Equil 5.3 +# Equil These instructions are for configuring the Equil insulin pump. @@ -9,7 +9,7 @@ These instructions are for configuring the Equil insulin pump. ## Hardware and Software Requirements * **Compatible Equil hardware** -§todo + Currently Equil 5.3 and 5.4 is supported * [Version 3.3.0.0](#version3300) or newer of AAPS @@ -31,4 +31,6 @@ Navigate to the Equil Tab and press **Pair Equil Patch Pump**. ![activate2.png](../images/Equil/activate2.png) -![activate3.png](../images/Equil/activate3.png) \ No newline at end of file +![activate3.png](../images/Equil/activate3.png) + +If you set different password than default 0000 (recommended for your safety), do not forget to store this password on a safe place. This password is stored to the pump. Then this password is asked on every next pairing attempt until you do proper unpairing in AAPS. This makes the pump also unusable with original PDA until you unpair pump from AAPS. diff --git a/docs/CROWDIN/lt/CompatiblePumps/Equil5.3.md b/docs/CROWDIN/lt/CompatiblePumps/Equil5.3.md index 112d0d17aacc..02d41665d4f8 100644 --- a/docs/CROWDIN/lt/CompatiblePumps/Equil5.3.md +++ b/docs/CROWDIN/lt/CompatiblePumps/Equil5.3.md @@ -1,4 +1,4 @@ -# Equil 5.3 +# Equil These instructions are for configuring the Equil insulin pump. @@ -9,7 +9,7 @@ These instructions are for configuring the Equil insulin pump. ## Hardware and Software Requirements * **Compatible Equil hardware** -§todo + Currently Equil 5.3 and 5.4 is supported * [Version 3.3.0.0](#version3300) or newer of AAPS @@ -31,4 +31,6 @@ Navigate to the Equil Tab and press **Pair Equil Patch Pump**. ![activate2.png](../images/Equil/activate2.png) -![activate3.png](../images/Equil/activate3.png) \ No newline at end of file +![activate3.png](../images/Equil/activate3.png) + +If you set different password than default 0000 (recommended for your safety), do not forget to store this password on a safe place. This password is stored to the pump. Then this password is asked on every next pairing attempt until you do proper unpairing in AAPS. This makes the pump also unusable with original PDA until you unpair pump from AAPS. diff --git a/docs/CROWDIN/nl/CompatiblePumps/Equil5.3.md b/docs/CROWDIN/nl/CompatiblePumps/Equil5.3.md index 151af2b6219a..9fd180c3f6cc 100644 --- a/docs/CROWDIN/nl/CompatiblePumps/Equil5.3.md +++ b/docs/CROWDIN/nl/CompatiblePumps/Equil5.3.md @@ -1,4 +1,4 @@ -# Equil 5.3 +# Equil These instructions are for configuring the Equil insulin pump. @@ -9,7 +9,7 @@ These instructions are for configuring the Equil insulin pump. ## Hardware and Software Requirements * **Compatible Equil hardware** -§todo + Currently Equil 5.3 and 5.4 is supported * [Version 3.3.0.0](#version3300) or newer of AAPS @@ -31,4 +31,6 @@ Navigate to the Equil Tab and press **Pair Equil Patch Pump**. ![activate2.png](../images/Equil/activate2.png) -![activate3.png](../images/Equil/activate3.png) \ No newline at end of file +![activate3.png](../images/Equil/activate3.png) + +If you set different password than default 0000 (recommended for your safety), do not forget to store this password on a safe place. This password is stored to the pump. Then this password is asked on every next pairing attempt until you do proper unpairing in AAPS. This makes the pump also unusable with original PDA until you unpair pump from AAPS. diff --git a/docs/CROWDIN/pb/CompatiblePumps/Equil5.3.md b/docs/CROWDIN/pb/CompatiblePumps/Equil5.3.md index 51d0d1f9014f..cf4ec934d32a 100644 --- a/docs/CROWDIN/pb/CompatiblePumps/Equil5.3.md +++ b/docs/CROWDIN/pb/CompatiblePumps/Equil5.3.md @@ -1,4 +1,4 @@ -# Equil 5.3 +# Equil These instructions are for configuring the Equil insulin pump. @@ -9,7 +9,7 @@ These instructions are for configuring the Equil insulin pump. ## Hardware and Software Requirements * **Compatible Equil hardware** -§todo + Currently Equil 5.3 and 5.4 is supported * [Version 3.3.0.0](#version3300) or newer of AAPS @@ -31,4 +31,6 @@ Navigate to the Equil Tab and press **Pair Equil Patch Pump**. ![activate2.png](../images/Equil/activate2.png) -![activate3.png](../images/Equil/activate3.png) \ No newline at end of file +![activate3.png](../images/Equil/activate3.png) + +If you set different password than default 0000 (recommended for your safety), do not forget to store this password on a safe place. This password is stored to the pump. Then this password is asked on every next pairing attempt until you do proper unpairing in AAPS. This makes the pump also unusable with original PDA until you unpair pump from AAPS. diff --git a/docs/CROWDIN/pl/CompatiblePumps/Equil5.3.md b/docs/CROWDIN/pl/CompatiblePumps/Equil5.3.md index 51d0d1f9014f..cf4ec934d32a 100644 --- a/docs/CROWDIN/pl/CompatiblePumps/Equil5.3.md +++ b/docs/CROWDIN/pl/CompatiblePumps/Equil5.3.md @@ -1,4 +1,4 @@ -# Equil 5.3 +# Equil These instructions are for configuring the Equil insulin pump. @@ -9,7 +9,7 @@ These instructions are for configuring the Equil insulin pump. ## Hardware and Software Requirements * **Compatible Equil hardware** -§todo + Currently Equil 5.3 and 5.4 is supported * [Version 3.3.0.0](#version3300) or newer of AAPS @@ -31,4 +31,6 @@ Navigate to the Equil Tab and press **Pair Equil Patch Pump**. ![activate2.png](../images/Equil/activate2.png) -![activate3.png](../images/Equil/activate3.png) \ No newline at end of file +![activate3.png](../images/Equil/activate3.png) + +If you set different password than default 0000 (recommended for your safety), do not forget to store this password on a safe place. This password is stored to the pump. Then this password is asked on every next pairing attempt until you do proper unpairing in AAPS. This makes the pump also unusable with original PDA until you unpair pump from AAPS. diff --git a/docs/CROWDIN/pt/CompatiblePumps/Equil5.3.md b/docs/CROWDIN/pt/CompatiblePumps/Equil5.3.md index 1671ce5b2023..09badf629194 100644 --- a/docs/CROWDIN/pt/CompatiblePumps/Equil5.3.md +++ b/docs/CROWDIN/pt/CompatiblePumps/Equil5.3.md @@ -1,4 +1,4 @@ -# Equil 5.3 +# Equil These instructions are for configuring the Equil insulin pump. @@ -9,7 +9,7 @@ These instructions are for configuring the Equil insulin pump. ## Hardware and Software Requirements * **Compatible Equil hardware** -§todo + Currently Equil 5.3 and 5.4 is supported * [Version 3.3.0.0](#version3300) or newer of AAPS @@ -31,4 +31,6 @@ Navigate to the Equil Tab and press **Pair Equil Patch Pump**. ![activate2.png](../images/Equil/activate2.png) -![activate3.png](../images/Equil/activate3.png) \ No newline at end of file +![activate3.png](../images/Equil/activate3.png) + +If you set different password than default 0000 (recommended for your safety), do not forget to store this password on a safe place. This password is stored to the pump. Then this password is asked on every next pairing attempt until you do proper unpairing in AAPS. This makes the pump also unusable with original PDA until you unpair pump from AAPS. diff --git a/docs/CROWDIN/ro/CompatiblePumps/Equil5.3.md b/docs/CROWDIN/ro/CompatiblePumps/Equil5.3.md index cf9f2bb5e7ed..dbc65cb880d7 100644 --- a/docs/CROWDIN/ro/CompatiblePumps/Equil5.3.md +++ b/docs/CROWDIN/ro/CompatiblePumps/Equil5.3.md @@ -1,4 +1,4 @@ -# Equil 5.3 +# Equil These instructions are for configuring the Equil insulin pump. @@ -9,7 +9,7 @@ These instructions are for configuring the Equil insulin pump. ## Hardware and Software Requirements * **Compatible Equil hardware** -§todo + Currently Equil 5.3 and 5.4 is supported * [Version 3.3.0.0](#version3300) or newer of AAPS @@ -31,4 +31,6 @@ Navigate to the Equil Tab and press **Pair Equil Patch Pump**. ![activate2.png](../images/Equil/activate2.png) -![activate3.png](../images/Equil/activate3.png) \ No newline at end of file +![activate3.png](../images/Equil/activate3.png) + +If you set different password than default 0000 (recommended for your safety), do not forget to store this password on a safe place. This password is stored to the pump. Then this password is asked on every next pairing attempt until you do proper unpairing in AAPS. This makes the pump also unusable with original PDA until you unpair pump from AAPS. diff --git a/docs/CROWDIN/ru/CompatiblePumps/Equil5.3.md b/docs/CROWDIN/ru/CompatiblePumps/Equil5.3.md index f9e579f305d0..58c35bf245bd 100644 --- a/docs/CROWDIN/ru/CompatiblePumps/Equil5.3.md +++ b/docs/CROWDIN/ru/CompatiblePumps/Equil5.3.md @@ -1,4 +1,4 @@ -# Equil 5.3 +# Equil These instructions are for configuring the Equil insulin pump. @@ -9,7 +9,7 @@ These instructions are for configuring the Equil insulin pump. ## Требования к аппаратному и программному обеспечению * **Compatible Equil hardware** -§todo + Currently Equil 5.3 and 5.4 is supported * [Version 3.3.0.0](#version3300) or newer of AAPS @@ -31,4 +31,6 @@ Navigate to the Equil Tab and press **Pair Equil Patch Pump**. ![activate2.png](../images/Equil/activate2.png) -![activate3.png](../images/Equil/activate3.png) \ No newline at end of file +![activate3.png](../images/Equil/activate3.png) + +If you set different password than default 0000 (recommended for your safety), do not forget to store this password on a safe place. This password is stored to the pump. Then this password is asked on every next pairing attempt until you do proper unpairing in AAPS. This makes the pump also unusable with original PDA until you unpair pump from AAPS. diff --git a/docs/CROWDIN/sk/CompatiblePumps/Equil5.3.md b/docs/CROWDIN/sk/CompatiblePumps/Equil5.3.md index 51d0d1f9014f..cf4ec934d32a 100644 --- a/docs/CROWDIN/sk/CompatiblePumps/Equil5.3.md +++ b/docs/CROWDIN/sk/CompatiblePumps/Equil5.3.md @@ -1,4 +1,4 @@ -# Equil 5.3 +# Equil These instructions are for configuring the Equil insulin pump. @@ -9,7 +9,7 @@ These instructions are for configuring the Equil insulin pump. ## Hardware and Software Requirements * **Compatible Equil hardware** -§todo + Currently Equil 5.3 and 5.4 is supported * [Version 3.3.0.0](#version3300) or newer of AAPS @@ -31,4 +31,6 @@ Navigate to the Equil Tab and press **Pair Equil Patch Pump**. ![activate2.png](../images/Equil/activate2.png) -![activate3.png](../images/Equil/activate3.png) \ No newline at end of file +![activate3.png](../images/Equil/activate3.png) + +If you set different password than default 0000 (recommended for your safety), do not forget to store this password on a safe place. This password is stored to the pump. Then this password is asked on every next pairing attempt until you do proper unpairing in AAPS. This makes the pump also unusable with original PDA until you unpair pump from AAPS. diff --git a/docs/CROWDIN/tr/CompatiblePumps/Equil5.3.md b/docs/CROWDIN/tr/CompatiblePumps/Equil5.3.md index e5c2a69cc274..6bdbe62fe8db 100644 --- a/docs/CROWDIN/tr/CompatiblePumps/Equil5.3.md +++ b/docs/CROWDIN/tr/CompatiblePumps/Equil5.3.md @@ -1,4 +1,4 @@ -# Equil 5.3 +# Equil These instructions are for configuring the Equil insulin pump. @@ -9,7 +9,7 @@ These instructions are for configuring the Equil insulin pump. ## Donanım ve Yazılım Gereksinimleri * **Compatible Equil hardware** -§todo + Currently Equil 5.3 and 5.4 is supported * [Version 3.3.0.0](#version3300) or newer of AAPS @@ -31,4 +31,6 @@ Navigate to the Equil Tab and press **Pair Equil Patch Pump**. ![activate2.png](../images/Equil/activate2.png) -![activate3.png](../images/Equil/activate3.png) \ No newline at end of file +![activate3.png](../images/Equil/activate3.png) + +If you set different password than default 0000 (recommended for your safety), do not forget to store this password on a safe place. This password is stored to the pump. Then this password is asked on every next pairing attempt until you do proper unpairing in AAPS. This makes the pump also unusable with original PDA until you unpair pump from AAPS. diff --git a/docs/CROWDIN/zh_CN/CompatiblePumps/Equil5.3.md b/docs/CROWDIN/zh_CN/CompatiblePumps/Equil5.3.md index b7ea031c40a6..44e4cf2bd12d 100644 --- a/docs/CROWDIN/zh_CN/CompatiblePumps/Equil5.3.md +++ b/docs/CROWDIN/zh_CN/CompatiblePumps/Equil5.3.md @@ -1,4 +1,4 @@ -# Equil 5.3 +# Equil 以下说明用于配置Equil胰岛素泵。 @@ -7,15 +7,15 @@ §todo ## 硬件和软件要求 -* **兼容的Equil硬件设备** +* **Compatible Equil hardware** -§todo + Currently Equil 5.3 and 5.4 is supported -* [版本3.3.0.0](#version3300)或更高版本的AAPS +* [Version 3.3.0.0](#version3300) or newer of AAPS ### 选择 Equil 泵 -在[配置构建器 > 泵](#Config-Builder-pump)中，切换至**Equil 5.3**。 +In [Config Builder > Pump](#Config-Builder-pump), switch to **Equil 5.3**. ### 设置 @@ -23,7 +23,7 @@ ### Activate patch -进入Equil标签页，点击**配对Equil贴片泵**。 +Navigate to the Equil Tab and press **Pair Equil Patch Pump**. ![overview.png](../images/Equil/overview.png) @@ -31,4 +31,6 @@ ![activate2.png](../images/Equil/activate2.png) -![activate3.png](../images/Equil/activate3.png) \ No newline at end of file +![activate3.png](../images/Equil/activate3.png) + +If you set different password than default 0000 (recommended for your safety), do not forget to store this password on a safe place. This password is stored to the pump. Then this password is asked on every next pairing attempt until you do proper unpairing in AAPS. This makes the pump also unusable with original PDA until you unpair pump from AAPS. diff --git a/docs/CROWDIN/zh_TW/CompatiblePumps/Equil5.3.md b/docs/CROWDIN/zh_TW/CompatiblePumps/Equil5.3.md index 136a255185e6..50440fb873ac 100644 --- a/docs/CROWDIN/zh_TW/CompatiblePumps/Equil5.3.md +++ b/docs/CROWDIN/zh_TW/CompatiblePumps/Equil5.3.md @@ -1,4 +1,4 @@ -# Equil 5.3 +# Equil 這些指示是用於配置 Equil 胰島素幫浦。 @@ -9,7 +9,7 @@ ## 硬體和軟體需求 * **相容的 Equil 硬體** -§todo + 目前支援 Equil 5.3 與 5.4。 * [AAPS 版本 3.3.0.0](#version3300) 或更新版本 @@ -31,4 +31,6 @@ ![activate2.png](../images/Equil/activate2.png) -![activate3.png](../images/Equil/activate3.png) \ No newline at end of file +![activate3.png](../images/Equil/activate3.png) + +如果你設定了不同於預設值「0000」的密碼（為了安全性建議這樣做），請務必將此密碼妥善儲存在安全的地方。 此密碼會儲存在幫浦中。 之後在每次嘗試重新配對時，都會要求輸入此密碼，直到你在 AAPS 中正確地解除配對為止。 這會導致在你從 AAPS 中解除配對之前，該幫浦無法與原廠 PDA 一同使用。 diff --git a/docs/CROWDIN/zh_TW/CompatiblePumps/OmnipodDASH.md b/docs/CROWDIN/zh_TW/CompatiblePumps/OmnipodDASH.md index 31170023abe7..d9a2fbcbff11 100644 --- a/docs/CROWDIN/zh_TW/CompatiblePumps/OmnipodDASH.md +++ b/docs/CROWDIN/zh_TW/CompatiblePumps/OmnipodDASH.md @@ -1,118 +1,118 @@ # Omnipod DASH -These instructions are for configuring the **Omnipod DASH** generation pump **(NOT Omnipod Eros)**, available in **AAPS** from version 3.0. +這些說明是用於設定 Omnipod DASH 這一代的幫浦（非 Omnipod Eros），自 AAPS 3.0 版起可用。 ## Omnipod DASH 規格 以下是**Omnipod DASH**（簡稱「DASH」）的規格，以及它與**Omnipod EROS**（簡稱「EROS」）的區別： -- The DASH pods are identified by a **blue needle cap** (EROS has a clear needle cap). 這兩種 Pod 在物理尺寸上是相同的。 +- DASH 的 Pod 可藉由**藍色針帽辨識**（EROS 為透明針帽）。 這兩種 Pod 在物理尺寸上是相同的。 - DASH 不需要 BLE 連結/橋接設備（無需 RileyLink、OrangeLink 或 EmaLink）。 -- The DASH's Bluetooth connection is used only when sending a command (e.g a Bolus), and disconnects right after issuing the command. +- DASH 的藍牙連線僅在傳送指令時（例如進行注射）使用，並會在發出指令後立即中斷連線。 - 使用DASH時再也不會出現「無法連線到連結設備/ Pod 」的錯誤。 - **AAPS**將等候 Pod 的可讀取性以發送指令。 - Pod 啟動時，**AAPS**將尋找並連接到新的DASH Pod 。 -- Expected range from phone: 5-10 meters (YMMV). +- 與手機的預期連線距離：5–10 公尺（實際情況可能不同）。 (#omnipod-dash-constraints)= -## Omnipod DASH known AAPS constraints/issues -- Android 16 requires **AAPS** version 3.3.2.1 or later. -- General advice is to run **AAPS** on Android 14 or 16. Android 15 has many reported [issues](https://github.com/nightscout/AndroidAPS/issues/3471) from the community. However, if you do run on Android 15 you will likely need to enable Bluetooth Bonding to successfully activate and use Pods, see [General Troubleshooting](../GettingHelp/GeneralTroubleshooting.md) for more info on the Bonding settings. -- Too frequent basal updates may cause basal insulin delivery [problems](https://github.com/nightscout/AndroidAPS/issues/4158) with Omnipod Dash. When using **SMB**, limit the interval to 5 minutes minimum to avoid this issue. -- Dash only supports basal rate in 0.05 U/h steps. If you try to set basal with 0.01 steps in your **AAPS profile**, AAPS will not give a warning even though the pod will round up the rate into 0.05 steps. If you view POD MGMT/Pod History it will display that 0.05 basal was set. This also means the lowest basal rate allowed by the DASH in **AAPS** is 0.05U/h. -- The activation status of a Pod is stored in the settings file, if you export a settings file with an active pod. Then change to a new pod, then restore the settings from your previous export you will have now restored the old pod activation and removed the new pod activation. This is why we recommend to export settings after each pod activation to allow a restore of that pods activation state if something happens to your rig. -- When setting a new basal profile, DASH will suspend delivery before setting the new basal **Profile**. If there is a communication interruption or error, the basal profile won't automatically re-start. See section [Resuming Insulin Delivery](#omnipod-dash-resuming-insulin-delivery) for details. -- If alerts are configured, and the pod is about to expire, the pod will keep beeping until alerts are silenced, see [Silencing Pod Alerts](#omnipod-dash-silencing-pod-alerts) for details. -- There are a number of known issues with Bluetooth which can cause pod activation problems. See [Troubleshooting](#troubleshooting) for advice on Bluetooth issues, specifically the [Bluetooth related issues](#omnipod-dash-bluetooth-related-issues) section. +## Omnipod DASH 已知的 AAPS 限制／問題 +- Android 16 需要 AAPS 版本 3.3.2.1 或更新版本。 +- 一般建議在 Android 14 或 16 上執行 AAPS。 Android 15 有許多社群回報的 [問題](https://github.com/nightscout/AndroidAPS/issues/3471)。 不過，若你在 Android 15 上執行，可能需要啟用藍牙配對（Bonding）才能成功註冊並使用 Pod；關於配對設定的更多資訊，請參閱 [一般疑難排解](../GettingHelp/GeneralTroubleshooting.md)。 +- 過於頻繁的基礎率更新，可能在 Omnipod Dash 上導致基礎胰島素輸注的問題。 使用微量注射時，請將間隔至少設為 5 分鐘以避免此問題。 +- Dash 僅支援以 0.05 U/h 步階設定的基礎率。 如果你在 AAPS 設定檔中嘗試以 0.01 的步階設定基礎率，即使 Pod 會將速率進位到 0.05 的步階，AAPS 也不會發出警示。 若你查看 POD MGMT/Pod History，會顯示已設定 0.05 的基礎率。 這也表示在 AAPS 中，DASH 允許的最低基礎率為 0.05 U/h。 +- Pod 的註冊狀態會儲存在設定檔案中，如果你在 Pod 已註冊的狀態下匯出設定檔案。 接著更換為新的 Pod，然後再從先前匯出的設定還原，這會還原舊 Pod 的註冊狀態，並移除新 Pod 的註冊狀態。 因此建議每次註冊 Pod 後都匯出設定，以便在你的裝置出狀況時，能還原該 Pod 的註冊狀態。 +- 當設定新的基礎率設定檔時，DASH 會先暫停輸注，然後再設定新的基礎率設定檔。 若通訊中斷或發生錯誤，基礎率設定檔不會自動重新開始。 詳細內容請參閱 [恢復胰島素輸注](#omnipod-dash-resuming-insulin-delivery) 章節。 +- 如果已設定警示，且 Pod 即將到期，Pod 會持續發出嗶聲，直到將警示靜音為止；詳情請參閱 [靜音 Pod 警示](#omnipod-dash-silencing-pod-alerts)。 +- 有多項已知的藍牙問題可能導致 Pod 註冊異常。 關於藍牙問題的建議，請參閱 [問題排除](#troubleshooting)，特別是[藍牙相關問題](#omnipod-dash-bluetooth-related-issues)章節。 (hardware-software-requirements)= (omnipod-dash-hardware-software-requirements)= ## 硬體/軟體要求 -- Omnipod DASH is identified by the blue needle cap. +- Omnipod DASH 可透過藍色的針頭蓋辨識。 ![Omnipod Pod](../images/DASH_images/Omnipod_Pod.png) -- **A Compatible Android phone** with a Bluetooth Low Energy (BLE) (see [Phones](../Getting-Started/Phones.md) for more info), additionally the following information will help guide you on other key considerations around successfully activating and using the DASH on a compatible phone: - - The **AAPS** Omnipod Dash driver connects with the DASH Pod using Bluetooth. - **AAPS** will automatically establish a new Bluetooth connection to the Pod every time it needs to send a command (e.g a Bolus), after sending the command the Bluetooth connection is immediately disconnected. +- **一支相容的 Android 手機**且具備低功耗藍牙（BLE）（更多資訊請見[Phones](../Getting-Started/Phones.md)），另外，下列資訊可協助您在相容手機上順利註冊與使用 DASH 時的其他關鍵注意事項： + - **AAPS** 的 Omnipod Dash 驅動程式會透過藍牙與 DASH Pod 連線。 + **AAPS** 會在每次需要傳送指令（例如注射）時，自動與 Pod 建立新的藍牙連線；在傳送完成後，會立即中斷連線。 - **注意：** - - The Bluetooth connection can be interrupted/disturbed by other Bluetooth devices linked to the phone that is running **AAPS**, like earbuds etc... Devices like this can cause connection errors or pod activation issues on some models of phones. It's a good idea to review the [tested hardware setups](https://docs.google.com/spreadsheets/u/1/d/e/2PACX-1vScCNaIguEZVTVFAgpv1kXHdsHl3fs6xT6RB2Z1CeVJ561AvvqGwxMhlmSHk4J056gMCAQE02sAWJvT/pubhtml?gid=683363241&single=true) list for known working configurations before committing to a new rig built around Omnipod DASH. - - There are a number of known issues with Bluetooth which can cause pod activation problems (See [Troubleshooting](#troubleshooting) for advice on other Bluetooth issues) specifically the [Bluetooth related issues](#omnipod-dash-bluetooth-related-issues) section. - - For **Android 15** or below: You **MUST** use **Version 3.0 or newer of AAPS** using the [**Build APK**](../SettingUpAaps/BuildingAaps.md) instructions, however it's advisable to run the latest released version. - - For **Android 16**: you **MUST** use **Version 3.3.2.1 or newer of AAPS** using the [**Build APK**](../SettingUpAaps/BuildingAaps.md) instructions, due to Android 16 changing how its Bluetooth works. Any version earlier than 3.3.2.1 will likely cause pod failures and/or activation [issues](https://github.com/nightscout/AndroidAPS/issues/3471). -- A supported [**Continuous Glucose Monitor (CGM)**](../Getting-Started/CompatiblesCgms.md) + - 在執行 **AAPS** 的手機上，其他已連結的藍牙裝置（例如耳機等）可能會干擾或中斷藍牙連線。 這類裝置在某些手機型號上可能導致連線錯誤或 Pod 註冊問題。 在決定以 Omnipod DASH 建置新設備前，建議先查看[已測試的硬體組合](https://docs.google.com/spreadsheets/u/1/d/e/2PACX-1vScCNaIguEZVTVFAgpv1kXHdsHl3fs6xT6RB2Z1CeVJ561AvvqGwxMhlmSHk4J056gMCAQE02sAWJvT/pubhtml?gid=683363241&single=true)清單，以了解已知可運作的設定。 + - 有多項已知的藍牙問題可能導致 Pod 註冊異常（其他藍牙問題的建議請見 [問題排除](#troubleshooting)），特別是[藍牙相關問題](#omnipod-dash-bluetooth-related-issues)章節。 + - 對於 **Android 15** 或更早版本：您**必須**依照 [**Build APK**](../SettingUpAaps/BuildingAaps.md) 指南使用 **AAPS 3.0 或更新版本**；同時建議執行最新釋出的版本。 + - 對於 **Android 16**：因為 Android 16 變更了藍牙的運作方式，您**必須**依照 [**Build APK**](../SettingUpAaps/BuildingAaps.md) 指南使用 **AAPS 3.3.2.1 或更新版本**。 任何早於 3.3.2.1 的版本都很可能造成 Pod 異常與／或註冊[問題](https://github.com/nightscout/AndroidAPS/issues/3471)。 +- 一個受支援的[**連續式血糖監測（CGM）**](../Getting-Started/CompatiblesCgms.md) -The instructions below explain how to activate a new pod session using **AAPS**. You should wait for your current Pod to be close expiry, as you will need to activate a new Pod with **AAPS**. Once a pod is de-activated it cannot be reused/re-activated, the de-activation is final. +以下說明如何使用 **AAPS** 註冊新的 Pod 工作階段。 建議等目前的 Pod 接近到期時再進行，因為您需要使用 **AAPS** 註冊新的 Pod。 Pod 一旦停用後便無法重複使用或再次註冊，此動作為最終狀態。 ## 在你開始之前 -Ensure you have read and understand this whole guide, have read and understand the **Before You Begin** section, as well as **[Omnipod and AAPS Constraints and Issues](#omnipod-dash-constraints)** to avoid running into a known problem. +請確定您已完整閱讀並理解本指南、**開始前**章節，以及 **[Omnipod 與 AAPS 的限制與問題](#omnipod-dash-constraints)**，以避免遇到已知問題。 -#### **SAFETY FIRST** - You **SHOULD NOT** try to connect **AAPS** to a pod for the first time without having access to all of the following: -1. Extra pods (3 or more spare) -2. Spare Insulin and MDI equipment -3. A working Omnipod PDM (In case **AAPS** fails) -4. Supported Phones are a must! (See [Hardware/Software Requirements](#hardware-software-requirements)) -5. Correct version of AAPS built and installed +#### **安全第一**—在無法取得以下所有項目時，您**不應該**首次嘗試將 **AAPS** 連線到 Pod： +1. 備用 Pod（至少 3 顆） +2. 備用胰島素與 MDI 器材 +3. 可正常使用的 Omnipod PDM（以防 **AAPS** 發生異常） +4. 必須使用受支援的手機！ （請參閱[硬體／軟體需求](#hardware-software-requirements)） +5. 已建置並安裝正確版本的 AAPS -#### **Your Omnipod Dash PDM will become redundant after the AAPS Dash driver activates your pod.** -- Before using **AAPS** you or your care giver would have had to manage the Pod using the Omnipod PDM (or in some regions a Phone app) to send commands to your DASH (e.g a Bolus). -- The DASH can only facilitate a single Bluetooth device (e.g PDM or Phone) connection to manage and send commands. -- The device that successfully activates the pod is the only device allowed to communicate with that Pod from that point forward. This means that once you activate a DASH with your Android phone using **AAPS**, **you will no longer be able to use your PDM with that pod!** For the time that Pod is active the **AAPS** Dash driver running on your Android phone is now the new PDM for your pod. -- **DO NOT 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 Dash 驅動程式註冊您的 Pod 後，您的 Omnipod Dash PDM 將形同冗餘。** +- 在使用 **AAPS** 之前，您或照護者必須使用 Omnipod PDM（或在某些地區使用手機 App）來管理 Pod，並向您的 DASH 傳送指令（例如注射）。 +- DASH 一次只能由單一藍牙裝置（例如 PDM 或手機）連線以進行管理與傳送指令。 +- 自成功註冊該 Pod 起，只有完成註冊的那台裝置被允許與該 Pod 通訊。 也就是說，一旦您使用 **AAPS** 透過 Android 手機註冊了 DASH，**之後將無法再用 PDM 操作該 Pod！**在該 Pod 啟動期間，執行於您 Android 手機上的 **AAPS** Dash 驅動程式即成為該 Pod 的新 PDM。 +- **請勿丟棄您的 PDM！**建議保留做為備用與應急之用，例如手機遺失或 **AAPS** 無法正常運作時。 -#### 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**](../SettingUpAaps/YourAapsProfile.md). -As long as **AAPS** is operational it will send basal rate adjustment 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 as defined in your [**Profile**](../SettingUpAaps/YourAapsProfile.md). +#### 您的 Pod 在未連線到 AAPS 時**並不會**停止輸注胰島素。 +依照目前啟用中的[**設定檔**](../SettingUpAaps/YourAapsProfile.md)，Pod 會在註冊時被寫入預設基礎率。 +只要 **AAPS** 正常運作，它就會送出最長 120 分鐘的基礎率調整指令。 +若因任何原因 Pod 未收到新指令（例如 Pod 與 手機 距離過遠導致通訊中斷），Pod 會自動回復到您[**設定檔**](../SettingUpAaps/YourAapsProfile.md)中定義的預設基礎率。 -#### **AAPS Profile(s) do not support 30 minute basal rate time frames** -If you are new to **AAPS** and are setting up your basal rate [**Profile**](../SettingUpAaps/YourAapsProfile.md) for the first time, please be aware that basal rates starting on a half-hour basis are not supported. For example, on your Omnipod PDM, if you have a basal rate of 1.1 units which starts at 09:30 and has a duration of 2 hours ending at 11:30, it is not possible replicate this exact basil **Profile** in **AAPS**. -You will need to change this 1.1 unit basal rate to a time range of either 9:00-11:00 or 10:00-12:00. Even though the DASH hardware itself supports the 30 minute basal rate **Profile** increments, **AAPS** does NOT support this feature. +#### **AAPS 的設定檔不支援 30 分鐘為單位的基礎率時間區段** +若您是 AAPS 新手並首次建立基礎率[**設定檔**](../SettingUpAaps/YourAapsProfile.md)，請注意：不支援以半小時為起點的基礎率。 例如：在您的 Omnipod PDM 上，若您有 1.1 單位、於 09:30 開始並持續 2 小時至 11:30 結束的基礎率，則無法在 **AAPS** 中完全複製相同的基礎**設定檔**。 +您需要將這個 1.1 單位的基礎率調整為 9:00–11:00 或 10:00–12:00 的時間範圍。 即使 DASH 硬體本身支援 30 分鐘增量的基礎率**設定檔**，**AAPS** 仍不支援此功能。 -#### **0U/h Profile basal rates are NOT supported in AAPS** -While the DASH does support a zero basal rate, **AAPS** uses multiples of the user's **Profile** basal rate to determine automated treatment; it cannot function with a zero basal rate. -Instead 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. -**NOTE:** The lowest basal rate allowed by the DASH in **AAPS** is 0.05U/h. +#### **AAPS 不支援 0 U/h 的設定檔基礎率** +雖然 DASH 支援零基礎率，**AAPS** 會以使用者**設定檔**的基礎率倍數來決定自動治療；因此無法在零基礎率下運作。 +您可以改用「中斷幫浦連線」功能，或搭配「停用 循環／臨時基礎率」或「暫停 循環／臨時基礎率」來達成暫時的零基礎率。 +**注意：**在 **AAPS** 中，DASH 允許的最低基礎率為 0.05 U/h。 ## 在AAPS中選擇DASH -There are **two** available options to configure Omnipod in **AAPS**: +在 **AAPS** 中設定 Omnipod 有**兩種**方式： ### 選項 1：新安裝 -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. +首次安裝 **AAPS** 時，**安裝嚮導**會引導新使用者了解 **AAPS** 的重點功能與安裝需求。 +當進入幫浦選擇時，請選擇「DASH」。 ![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). +若不確定，您也可以選擇「Virtual Pump」，待完成 **AAPS** 設定後再選擇「DASH」（見選項 2）。 (omnipod-dash-option-2-config-builder)= ### 選項 2：組態建置工具 在現有安裝中，你可以從組態建置工具中選擇**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**. +在左上角的**漢堡選單**中，選取**組態建置工具 (1)** ➜ **幫浦** ➜ **Dash**；勾選名為 **Dash** 的**單選按鈕 (2)**後，點選**設定齒輪 (3)**。 選中**設定齒輪(3)**旁邊的**復選框(4)**將使DASH選單顯示為**AAPS**介面的標籤**DASH**。 勾選此框將方便你在使用**AAPS**時訪問DASH指令。 -**注意：** 有一個更快速的方式可以在本文件的DASH設定部分中找到，訪問[**Dash設定**](#omnipod-dash-settings)。 +**注意：** 有一個更快速的方式可以在本文件的DASH設定部分中找到，前往[**Dash設定**](#omnipod-dash-settings)。 ![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**. 如果此框未勾選，則DASH標籤將位於左上角的漢堡選單中。 +若要確認您已在 **AAPS** 中選擇了 DASH，當您**勾選核取方塊 (4)**後，請從**總覽**分頁**向左滑**，此時您會在 **AAPS** 中看到 **DASH** 分頁。 如果此框未勾選，則DASH標籤將位於左上角的漢堡選單中。 ![Enable_Dash_4](../images/DASH_images/Enable_Dash/Enable_Dash_4.jpg) ## Dash 配置 -**Swipe left** to the [**DASH tab**](#omnipod-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): +**向左滑**到[**DASH 分頁**](#omnipod-dash-tab)，即可管理所有 Pod 功能（若無作用中的 Pod 工作階段，部分功能不會啟用或顯示）： ![Refresh_LOGO](../images/DASH_images/Refresh_LOGO.png) “重新整理” Pod 的連接性和狀態，能夠靜音 Pod 在發出嗶聲時的警報。 @@ -128,9 +128,9 @@ To verify that you have selected the DASH in **AAPS**, if you have **checked the ![Activate_Pod_2](../images/DASH_images/Activate_Pod/Activate_Pod_2.png) -2. 顯示**填充 Pod**畫面。 Fill a new pod with **at least 80 units** of insulin and listen for two beeps indicating that the pod is ready to be primed. +2. 顯示**填充 Pod**畫面。 為新的 Pod 注入**至少 80 單位**的胰島素，並留意兩聲嗶聲，表示 Pod 已準備好進行灌注。 - ***NOTE:** When calculating the total amount of insulin you need for 3 days, please take into account that priming the pod will use about 3-10 units.* + ***注意：**計算 3 天所需的胰島素總量時，請將灌注 Pod 會消耗約 3–10 單位一併納入。* ![Activate_Pod_3](../images/DASH_images/Activate_Pod/Activate_Pod_3.png) @@ -142,32 +142,32 @@ To verify that you have selected the DASH in **AAPS**, if you have **checked the ![Activate_Pod_3](../images/DASH_images/Activate_pod_error.png) -3. On the **Initialize Pod** screen, the pod will begin priming (you will hear a click followed by a series of ticking sounds as the pod primes itself). - A green checkmark will be shown upon successful priming, and the **Next** button will become enabled. 點擊 **下一步** 按鈕，完成 Pod 排空初始化並顯示 **連線 Pod** 畫面。 +3. 在**初始化 Pod**螢幕上，Pod 會開始灌注（您會聽到一聲卡嗒，接著是一連串的滴答聲，表示 Pod 正在自我灌注）。 + 灌注成功後會顯示綠色勾勾，且**下一步**按鈕會變為可用。 點擊 **下一步** 按鈕，完成 Pod 排空初始化並顯示 **連線 Pod** 畫面。 ![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. 接下來，準備好輸注部位以接收新的 Pod 。 洗手以避免任何感染風險。 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. - If you get skin irritation from the adhesive consider using a Barrier Wipe or Barrier Spray. +4. 接下來，準備好輸注部位以接收新的 Pod 。 洗手以避免任何感染風險。 以肥皂與清水清潔注射部位，或用酒精棉片消毒，並讓肌膚完全自然風乾後再繼續。 + 若膠貼造成肌膚刺激，可考慮使用隔離棉片或隔離噴霧。 - 移除 Pod 的藍色塑料針頭蓋。 If you see something that sticks out of the pod or it looks unusual, **STOP** the process and start with a new pod. If everything looks **OK**, proceed to take off the white paper backing from the adhesive and stick the pod to the selected site on your body. + 移除 Pod 的藍色塑料針頭蓋。 若您看到 Pod 有東西突出或外觀異常，請**立刻停止**操作並改用新的 Pod 重新開始。 若一切看起來 OK，請將黏膠背後的白色背紙撕下，然後把 Pod 貼在你選擇的身體部位。 完成後，點擊 **下一步** 按鈕。 ![Activate_Pod_8](../images/DASH_images/Activate_Pod/Activate_Pod_8.jpg) -6. 現在會出現 **連線 Pod** 對話框。 **click on the OK button ONLY if you are ready to deploy the cannula!** +6. 現在會出現 **連線 Pod** 對話框。 **只有在你已準備好要插入導管時，才點選 OK 按鈕！** ![Activate_Pod_9](../images/DASH_images/Activate_Pod/Activate_Pod_9.jpg) -7. 按下**確定**後，DASH可能需要一些時間才能響應並插入導管（最多1-2分鐘）。 **Be patient!** +7. 按下**確定**後，DASH可能需要一些時間才能響應並插入導管（最多1-2分鐘）。 **請耐心等候！** - ***NOTE:** Before the cannula is inserted, it is good practice to pinch the skin near the cannula insertion point. 這有助於針頭順利插入，並減少堵塞的機會。* + ***注意：**在插入導管前，建議先輕捏導管插入點附近的皮膚。 這有助於針頭順利插入，並減少堵塞的機會。* ![Activate_Pod_10](../images/DASH_images/Activate_Pod/Activate_Pod_10.png) ![Activate_Pod_11](../images/DASH_images/Activate_Pod/Activate_Pod_11.jpg) -8. A green checkmark is shown on the screen, and the **Next** button becomes available to select upon successful cannula insertion. - Click on the **Next** button. +8. 當導管成功插入後，螢幕會顯示綠色核取記號，且 **Next** 按鈕會變為可選取。 + 點選 **Next** 按鈕。 ![Activate_Pod_12](../images/DASH_images/Activate_Pod/Activate_Pod_12.jpg) @@ -183,24 +183,24 @@ To verify that you have selected the DASH in **AAPS**, if you have **checked the 點擊手機上的返回按鈕，返回到 **DASH** 標籤畫面，該畫面現在會顯示你的啟用 Pod 的資訊，包括目前基礎率、Pod 儲液量、輸送的胰島素、Pod 錯誤和警報。 - ***NOTE:** For more details on the information displayed go to the [**DASH Tab**](#omnipod-dash-tab) section of this document.* + ***注意：**如需瞭解顯示資訊的更多詳細內容，請參閱本文件的 [**DASH Tab**](#omnipod-dash-tab) 章節。* ![Activate_Pod_14](../images/DASH_images/Activate_Pod/Activate_Pod_14.png) ![Activate_Pod_15](../images/DASH_images/Activate_Pod/Activate_Pod_15.jpg) - ***NOTE:** It is good practice to export settings AFTER activating the pod. Settings should be exported after each pod change and once a month, ensure you copy the exported settings file to a cloud storage location (e.g. Google Drive) or somewhere off your phone in case you loose your phone (see [**Export settings**](../Maintenance/ExportImportSettings.md)).* + ***注意：**在註冊 Pod 之後匯出設定是很好的做法。 建議每次更換 Pod 後及每月匯出一次設定，並將匯出的設定檔複製到雲端儲存位置（例如 Google Drive）或手機以外的位置，以防手機遺失（請參閱 [**匯出設定**](../Maintenance/ExportImportSettings.md)）。* (omnipod-dash-deactivate-pod)= ### 停用 Pod -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 total pod usage. +一般情況下，Pod 的預期使用壽命為 3 天（72 小時），在 Pod 到期警示後還可再使用 8 小時，總計可使用 80 小時。 要停用 Pod（不論是過期還是 Pod 故障）： -1. Go to the **DASH** tab, click on the **POD MGMT (1)** button, on the **Pod Management** screen click on the **Deactivate Pod (2)** button. +1. 前往 **DASH** 分頁，點選 **POD 管理 (1)** 按鈕，在 **Pod 管理 ** 畫面點選 **停用 Pod (2)** 按鈕。 ![Deactivate_Pod_1](../images/DASH_images/Deactivate_Pod/Deactivate_Pod_1.jpg) @@ -208,15 +208,15 @@ Under normal circumstances, the expected lifetime of a pod is three days (72 hou 2. 在 **停用 Pod** 畫面上，點擊 **下一步** 按鈕開始停用 Pod 的流程。 - 你會收到來自 Pod 的確認嗶聲，表明停用成功。 + 你會收到來自 Pod 的確認嗶聲，表示停用成功。 ![Deactivate_Pod_3](../images/DASH_images/Deactivate_Pod/Deactivate_Pod_3.jpg) ![Deactivate_Pod_4](../images/DASH_images/Deactivate_Pod/Deactivate_Pod_4.jpg) -3. A green checkmark will be displayed upon successful deactivation. 點擊 **下一步** 按鈕以顯示 Pod 停用畫面。 +3. 停用成功後會顯示綠色核取記號。 點擊 **下一步** 按鈕以顯示 Pod 停用畫面。 - 你現在可以移除 Pod，因為該使用階段已停用。 + 你現在可以移除 Pod，該使用階段已停用。 ![Deactivate_Pod_5](../images/DASH_images/Deactivate_Pod/Deactivate_Pod_5.jpg) @@ -237,9 +237,9 @@ Under normal circumstances, the expected lifetime of a pod is three days (72 hou ### 恢復胰島素輸送 -**NOTE**: During **Profile Switches**, like when using the PDM, AAPS must suspend delivery on the Pod before setting the new basal **Profile**. If communication fails between the suspend and resume commands, then delivery can stay suspended, Read [**Delivery suspended**](#omnipod-dash-delivery-suspended) in the troubleshooting section for more details. +**注意**：在進行 **設定檔切換（Profile Switches）** 期間（例如使用 PDM 時），AAPS 必須先在 Pod 上暫停輸注，才能設定新的基礎率 **設定檔**。 若在暫停與恢復指令之間通訊失敗，輸注可能會持續維持在暫停狀態。更多細節請在疑難排解章節閱讀 [**輸注已暫停**](#omnipod-dash-delivery-suspended)。 -When insulin delivery is suspended you will need to issue a command to instruct the active, currently suspended pod to resume insulin delivery. 命令成功處理後，胰島素將根據當前時間從活動的基礎**設定檔**恢復正常送藥。 藥量將再次接受注射、**TB** 和**SMB**的命令。 +當胰島素輸注被暫停時，你需要下達指令，讓作用中但目前暫停的 Pod 恢復胰島素輸注。 命令成功處理後，胰島素將根據當前時間從活動的基礎**設定檔**恢復正常送藥。 藥量將再次接受注射、**TB** 和**SMB**的命令。 1. 進入 **DASH** 標籤，確認 **Pod 狀態 (1)** 欄位顯示 **已暫停**，然後按下 **恢復輸送 (2)** 按鈕以開始流程，指示目前的 Pod 恢復正常的胰島素輸送。 訊息 **恢復輸送** 將顯示在 **Pod 狀態 (3)** 欄位中。 @@ -259,15 +259,15 @@ When insulin delivery is suspended you will need to issue a command to instruct 以下流程將向你展示當 Pod 的使用時間接近72小時（3天）到期的警告時，如何確認並關閉 Pod 的嗶聲。 此警告時間限制定義在 **距關閉時間的時數** Dash 警報設置中。 Pod 的最大使用壽命為 80 小時（3 天 8 小時），但 Insulet 建議不要超過 72 小時（3 天）限制。 -***NOTE**: The **SILENCE ALERTS (3)** 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 到期或低藥量警示時，**DASH** 分頁上才會出現 **靜音警報 (3)** 按鈕。 如果看不到 **靜音警報** 按鈕，但你聽到 Pod 發出嗶聲，請嘗試「重新整理 Pod 狀態」。* -1. When the defined **Hours before shutdown** warning time limit is reached, the pod will issue warning beeps to inform you that it is approaching its expiration time and a pod change will be required soon. - You can verify this on the **DASH** tab, the **Pod expires: (1)** field will show the exact time the pod will expire (72 hours after activation), and the text will turn **red** after this time has passed. - Under the **Active Pod alerts (2)** field the status message **Pod will expire soon** is displayed. 這也會觸發顯示 **靜音警報 (3)** 按鈕。 +1. 當達到已設定的 **停用前的小時數** 警告時間門檻時，Pod 會發出警示嗶聲，提醒即將到期，並且很快需要更換 Pod。 + 你可以在 **DASH** 分頁確認，**Pod 到期 (1)** 欄位會顯示 Pod 的到期時間（註冊後 72 小時），且在超過此時間後文字會變為 **紅色**。 + 在 **啟用的 Pod 警報 (2)** 欄位下方，會顯示狀態訊息 **Pod 即將到期**。 這也會觸發顯示 **靜音警報 (3)** 按鈕。 ![ACK_alerts_1](../images/DASH_images/ACK_Alerts/ACK_ALERTS_1.png) -2. Go to the **DASH** tab and press the **SILENCE ALERTS (2)** button. **AAPS** 發送命令給藥量以停用藥量過期警告嗶聲，並更新**藥量狀態 (1)**字段為**確認警報**。 +2. 前往 **DASH** 分頁，按下 **靜音警報 (2)** 按鈕。 **AAPS** 發送命令給藥量以停用藥量過期警告嗶聲，並更新**藥量狀態 (1)**字段為**確認警報**。 ![ACK_alerts_2](../images/DASH_images/ACK_Alerts/ACK_ALERTS_2.png) @@ -283,9 +283,9 @@ When insulin delivery is suspended you will need to issue a command to instruct 本節解釋如何檢視你的活動藥量歷史，並按不同操作類別進行篩選。 Pod 歷史工具允許你查看在其三天（72 - 80 小時）使用壽命期間提交到目前活動 Pod 的操作和結果。 -此功能有助於驗證發送到 Pod 的注射劑量、臨時基礎率和基礎指令。 其餘類別對於排除故障和確定發生失敗前的事件順序很有幫助。 +此功能有助於驗證發送到 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'**.* +***注意：****只有最後一個指令可能會是未確認狀態**。 在最後一個「未確認」指令變為「已確認」或「已否決」之前，新的指令將不會被送出*。 將「未確認」指令「修復」的方法，是執行 **「重新整理 Pod 狀態」**。* 1. 進入 **DASH** 標籤，按下 **POD 管理 (1)** 按鈕以進入 **Pod 管理** 選單，然後按下 **Pod 歷史紀錄 (2)** 按鈕以進入 Pod 歷史紀錄畫面。 @@ -302,7 +302,7 @@ When insulin delivery is suspended you will need to issue a command to instruct 以下是主 AAPS 介面中 **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** 分頁的狀態欄位看到（不確定），你需要按下重新整理按鈕來清除，並重新整理 Pod 狀態。* ![DASH_Tab_1](../images/DASH_images/DASH_Tab/DASH_Tab_1.png) @@ -312,7 +312,7 @@ When insulin delivery is suspended you will need to issue a command to instruct - **藍牙地址：** 顯示目前連線 Pod 的藍牙地址。 -- **Bluetooth Status:** Displays the current connection status. +- **藍牙狀態：**顯示目前的連線狀態。 - **序列號：** 顯示目前啟用的 Pod 序列號。 @@ -339,7 +339,7 @@ When insulin delivery is suspended you will need to issue a command to instruct - **臨時基礎率：** 以以下格式顯示目前運作的臨時基礎率。 - {每小時單位數} @{TBR 開始時間} ({運作分鐘數}/{TBR 總運作分鐘數}) - - Example:* 0.00U/h @18:25 ( 90/120 minutes) + - 範例：* 0.00U/h @18:25 ( 90/120 minutes) - **儲液量：** 當儲液量超過 50 單位時顯示 50+ 單位。 當儲液量低於 50 單位時，顯示確切的單位數。 @@ -353,47 +353,47 @@ When insulin delivery is suspended you will need to issue a command to instruct ### 按鈕 -![重新整理圖示](../images/DASH_images/Refresh_LOGO.png) Sends a refresh command to the active pod to update communication. +![重新整理圖示](../images/DASH_images/Refresh_LOGO.png) 傳送重新整理指令給作用中的 Pod，以更新通訊。 - *用於重新整理 Pod 狀態並消除顯示 (不確定) 訊息的狀態欄位。* - - *See the [Troubleshooting](#omnipod-dash-troubleshooting) section below for additional information.* + - *更多資訊請參閱下方的 [疑難排解](#omnipod-dash-troubleshooting) 章節。* -![POD 管理圖示](../images/DASH_images/POD_MGMT_LOGO.png) Navigates to the Pod management menu. +![POD 管理圖示](../images/DASH_images/POD_MGMT_LOGO.png) 導向至 Pod 管理選單。 -![警報消音圖示](../images/DASH_images/ack_alert_logo.png) When pressed this will disable the pod alerts beeps and notifications (expiry, low reservoir..). +![警報消音圖示](../images/DASH_images/ack_alert_logo.png) 按下後，會停用 Pod 的警報嗶聲與通知（到期、低藥量等）。 - *該按鈕僅在 Pod 過期警告時間已過時顯示。* - *成功解除後，此圖示將不再顯示。* -![恢復圖示](../images/DASH_images/DASH_tab_icons/RESUME_Icon.png) Resumes the currently suspended insulin delivery in the active pod. +![恢復圖示](../images/DASH_images/DASH_tab_icons/RESUME_Icon.png) 讓作用中、目前處於暫停的 Pod 恢復胰島素輸注。 ### Pod 管理選單 -Below is describes the purpose of each icon on the **Pod Management** menu, accessed by pressing **POD MGMT (1)** button from the **DASH** tab. +下面說明從 **DASH** 分頁按下 **POD 管理 (1)** 按鈕進入的 **Pod 管理** 選單中，各圖示的用途。 ![DASH_Tab_2](../images/DASH_images/Deactivate_Pod/Deactivate_Pod_1.jpg) ![DASH_Tab_3](../images/DASH_images/DASH_Tab/DASH_Tab_3.png) -**The table below describes each button and it's function:** +**下表說明各按鈕及其功能：** -| Button | Function | -| ------ | --------------------------------------------------------------------------------------------- | -| 1 | Access the Pod Mgmt settings | -| 2 | [**Activate Pod**](#omnipod-dash-activate-pod): Primes and activates a new pod. | -| 3 | [**Deactivate Pod**](#omnipod-dash-deactivate-pod): Deactivates the currently active pod. | -| 4 | **Play Test Beep** : Plays a single test beep on the pod when pressed. | -| 5 | [**Pod history**](#omnipod-dash-view-pod-history) : Displays the active pod activity history. | +| 按鈕 | 功能 | +| -- | ---------------------------------------------------------- | +| 1 | 存取 Pod 管理設定 | +| 2 | [**I啟動 Pod**](#omnipod-dash-activate-pod)：為新的 Pod 預充並註冊。 | +| 3 | [**停用 Pod**](#omnipod-dash-deactivate-pod)：停用目前作用中的 Pod。 | +| 4 | **播放測試嗶聲**：按下時在 Pod 上播放一次測試嗶聲。 | +| 5 | [**Pod 歷史**](#omnipod-dash-view-pod-history)：顯示 Pod 的活動紀錄。 | (omnipod-dash-settings)= ## 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**. 選擇**選框 (4)**旁邊的**設置齒輪 (3)**將允許 Dash 菜單在**AAPS**介面中作為標籤顯示，標題為**DASH**。 +Dash 驅動程式設定可在左上角 **漢堡選單** 的 **組態建置工具 (1)** ➜ **幫浦** **Dash** ➜ **設定齒輪 (3)** 中進行，方法是先選取名為 **Dash** 的 **按鈕 (2)**。 選擇**選框 (4)**旁邊的**設置齒輪 (3)**將允許 Dash 菜單在**AAPS**介面中作為標籤顯示，標題為**DASH**。 ![Dash_settings_1](../images/DASH_images/Enable_Dash/Enable_Dash_3.png) @@ -403,21 +403,21 @@ The Dash driver settings are configurable from the top-left hand corner **hambur 下方列出了設定組；大多數項目可透過切換開關啟用或停用： -***NOTE:** An asterisk (\*) denotes the default setting is enabled.* +***注意：**星號（\*）表示此項為預設啟用。* ### 確認嗶聲提示 ![Dash_settings_4](../images/DASH_images/Dash_settings/Dash_settings_4.jpg) -提供來自藥筒的確認聲音提示，用於注射、基礎輸注、SMB以及TBR輸送和變更。 +提供來自藥筒的確認聲音提示，用於注射、基礎輸注、超微劑量(SMB)以及臨時基礎率(TBR)輸送和變更。 -**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. +**基礎嗶聲已啟用：**當設定新的基礎率、取消作用中的基礎率或變更目前的基礎率時，啟用或停用確認嗶聲。 -**SMB beeps enabled:** Enable or disable confirmation beeps when a SMB is delivered. +**微量注射嗶聲已啟用：**在執行 SMB 微量注射時啟用或停用確認嗶聲。 -**TBR beeps enabled:** Enable or disable confirmation beeps when a TBR is set or canceled. +**臨時基礎率嗶聲已啟用：**當設定或取消 TBR 臨時基礎率時，啟用或停用確認嗶聲。 @@ -427,15 +427,15 @@ The Dash driver settings are configurable from the top-left hand corner **hambur 提供**AAPS**的藥量過期、關閉、低藥量的警報，根據所定義的門檻值單位。 -***NOTE:** an AAPS notification will ALWAYS be issued for any alert after the initial communication with the pod since the alert was triggered. 解除通知不會取消警報，除非啟用了自動確認 Pod 警報功能。 若要手動解除警報，你必須進入 **DASH** 標籤，並按下 **靜音警報按鈕**。* +***注意：**自從警示被觸發並與 Pod 完成初次通訊後，AAPS 將一律針對任何警示發出通知。 解除通知不會取消警報，除非啟用了自動確認 Pod 警報功能。 若要手動解除警報，你必須進入 **DASH** 標籤，並按下 **靜音警報按鈕**。* -**Expiration reminder enabled:** Enable or disable the pod expiration reminder set to trigger when the defined number of hours before shutdown is reached. +**到期提醒已啟用：**當達到所設定的停用前小時數時，啟用或停用 Pod 到期提醒。 -**Hours before shutdown:** Defines the number hours before the active pod shutdown occurs, which will then trigger the expiration reminder alert. +**停用前的小時數：**定義作用中 Pod 自動停用前的時數；達到該時數時會觸發到期提醒。 -**Low reservoir alert enabled:** Enable or disable an alert when the pod's remaining units low reservoir limit is reached as defined in the Number of units field. +**低藥量警示已啟用：**當 Pod 剩餘單位數達到「數量」欄位所定義的低藥量門檻時，啟用或停用警示。 -**Number of units:** The number of units at which to trigger the pod low reservoir alert. +**劑量單位數：** 到達此劑量單位數時，觸發 Pod 低儲量警示。 @@ -443,23 +443,23 @@ The Dash driver settings are configurable from the top-left hand corner **hambur ![Dash_settings_6](../images/DASH_images/Dash_settings/Dash_settings_6.jpg) -The Notification section allows the user to select their preferred notifications and audible phone alerts when AAPS is uncertain about the status of TBR, SMB, or bolus, and when delivery suspended events were successful. +「通知」區段可讓使用者選擇偏好的通知與可聽見的手機提醒：當 **AAPS** 無法確定臨時基礎率、微量注射或注射的狀態，或當暫停輸注事件已成功時。 -***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. +**為「無法確定臨時基礎率」的通知啟用音效：** 啟用或停用此設定，當 **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. +**為「無法確定微量注射（SMB）」的通知啟用音效：** 啟用或停用此設定，當 **AAPS** 無法確定微量注射是否成功送達時，觸發可聽見的警示與視覺通知。 -**Sound for uncertain bolus notifications enabled:** Enable or disable this setting to trigger an audible alert and visual notification when **AAPS** is uncertain if a bolus was successfully delivered. +**為「無法確定注射」的通知啟用音效：** 啟用或停用此設定，當 **AAPS** 無法確定注射是否成功送達時，觸發可聽見的警示與視覺通知。 -**Sound when delivery suspended notifications enabled:** Enable or disable this setting to trigger an audible alert and visual notification when suspend delivery was successfully delivered. +**為「輸注已暫停」的通知啟用音效：** 啟用或停用此設定，當暫停輸注已成功時，觸發可聽見的警示與視覺通知。 ## 手動操作 (ACT) 標籤 -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. +此分頁已在 **AAPS** 主文件中有完整說明，但本分頁仍有一些項目是 **DASH** 與有管式幫浦的差異，尤其是在安裝新 Pod 之後的流程。 -1. Go to the **Actions (ACT)** tab in the main **AAPS** interface. +1. 前往 **AAPS** 主介面的 **Actions（ACT）** 分頁。 2. 在**照護入口 (1)**部分，**胰島素**和**導管**字段將在**每次更換藥量後**其**時間重置**為0天和0小時。 這是根據 Omnipod 幫浦的設計和運作方式所設。 由於 Pod 直接將套管插入應用 Pod 的皮膚上，因此 Omnipod 幫浦不使用傳統的管路。 *因此，在更換 Pod 後，這些數值的時間將自動重置為零。* **幫浦電池時間** 不會被報告，因為 Pod 中的電池壽命始終比 Pod 的最大壽命（80 小時）長。 每個 Pod 內都包含 **幫浦電池** 和 **胰島素儲液器**。 @@ -486,101 +486,101 @@ DASH 概覽標籤將顯示如下所述： (omnipod-dash-delivery-suspended)= -This section covers common known issues and solutions for Omnipod DASH use with AAPS. There is also [General Troubleshooting](../GettingHelp/GeneralTroubleshooting.md) section in the documentation that should be reviewed as it covers relevant topics for some Pod issues too. +本節涵蓋使用 **AAPS** 搭配 Omnipod DASH 的常見已知問題與解決方案。 文件中也有 [一般疑難排解](../GettingHelp/GeneralTroubleshooting.md) 章節，請參閱，因為其中的相關主題也適用於部分 Pod 問題。 --- (omnipod-dash-bluetooth-related-issues)= -### Bluetooth related issues +### 藍牙相關問題 -Some members of the community have been running into issues with Pod activation failures and other pod errors related to Bluetooth. Many of these issues can be traced to one of the following issues: +部分社群成員遇到與藍牙相關的 Pod 啟用失敗與其他 Pod 錯誤。 許多問題可追溯至以下其中一項原因： #### **Android 16** -- Android 16 needs at a minimum **AAPS** version 3.3.2.1, as this versions has fixes added to specifically address [known problems](../GettingHelp/GeneralTroubleshooting.md#cannot-start-omnipod-with-android-16) introduced in Android 16 for Omnipod. +- Android 16 至少需要 **AAPS** 版本 3.3.2.1，因為此版本加入了專門針對 Android 16 在 Omnipod 上引入的[已知問題](../GettingHelp/GeneralTroubleshooting.md#cannot-start-omnipod-with-android-16)之修正。 -#### **Apps that use the "Nearby devices" Android permission** +#### **使用 Android「附近裝置」權限的應用程式** -Android allows you to control what each app is able to do or access on your phone via a permission model. For each app installed you can choose to allow or deny specific permissions, e.g. access files on the device, access to bluetooth, scan for nearby devices etc. +Android 透過權限模型讓你控制每個應用程式在手機上能做什麼、能存取什麼。 你可針對每個已安裝的應用程式允許或拒絕特定權限，例如存取裝置上的檔案、存取藍牙、掃描附近裝置等。 -**AAPS** requires a number of specific permission to function, one which is required ensure that Pods work is the "Nearby devices" permission. There are many other applications which also require this permission, the community is finding that a number of applications when they are granted this permission can cause issues with activating new Pods on some devices. +**AAPS** 需要多項特定權限才能運作，其中確保 Pod 正常工作的必要權限是「附近裝置」。 也有許多其他應用程式需要此權限；社群發現，當某些應用被授予此權限時，可能會在部分裝置上導致新 Pod 的啟用發生問題。 -#### **Apps that use "Nearby device" permissions and are known to have caused problems:** +#### **使用「附近裝置」權限且已知會引發問題的應用程式：** -Apps in this list have been discussed in one or more places in the community as causing problems for Omnipod DASH devices. Any advice and links to the information found will be in this table. +此清單中的應用程式已在社群的一處或多處被討論過，確認會對 Omnipod DASH 裝置造成問題。 任何建議與找到的資訊連結都會放在此表格中。 -***NOTE:** If you wish to update any info in this table please ping @XiTatiON on #omnipod-dash Discord channel.* +***注意：** 若想更新此表中的任何資訊，請在 Discord 的 #omnipod-dash 頻道標記 @XiTatiON。* -**myBMW** MyBMW interrupted Medtrum Nano and Omnipod DASH. The MyBMW app prompts regarding permission for "find nearby devices" only once, if you don't grant it, it still works absolutely OK +**myBMW** MyBMW 會干擾 Medtrum Nano 與 Omnipod DASH。 MyBMW App 對「尋找附近裝置」權限只會提示一次；即使不授權，仍可正常運作。 -**Amazon Alexa** Removing "Nearby devices" for Alexa app resolved problem for some people but will break the ability to pair Matter IOT devices +**Amazon Alexa** 對部分使用者，移除 Alexa App 的「附近裝置」權限即可解決問題，但會使配對 Matter 物聯網裝置的功能失效。 -**MINI app** Appears the app is based on myBMW app and might mirror it's behavior as a result +**MINI app** 看起來此 App 是以 myBMW App 為基礎，因此行為可能相同。 -#### **How to revoke "Nearby device" permissions for other apps:** -If you are facing issues activating a new Pod and you are running on the correct supported version of **AAPS** for your version of Android. It may be necessary to revoked the permission for other apps while activating a new Pod. +#### **如何撤銷其他應用程式的「附近裝置」權限：** +如果你在啟用新 Pod 時遇到問題，且你使用的 **AAPS** 版本與你的 Android 版本相容， 在啟用新 Pod 的過程中，可能需要先撤銷其他應用程式的該權限。 -Follow this procedure to revoked the "Nearby device" permission for all apps except **AAPS**: +請依照以下步驟，將除了 **AAPS** 之外的所有應用程式的「附近裝置」權限撤銷： -***NOTE:** The screenshots and instructions in this guide are from a Vanilla Android 16 install on Google Pixel 8 Pro. Other manufactures and devices will likely not exactly match these menus and settings descriptions, adjust the steps to suit the device you have and if you are stuck see [Where to get help for dash](#omnipod-dash-where-to-get-help-for-dash) section on how to reach out to the community for support.* +***注意：** 本指南的螢幕截圖與操作說明來自 Google Pixel 8 Pro 上的原生 Android 16 安裝。 其他廠牌與裝置的選單與設定描述可能不盡相同，請依你的裝置調整步驟；若卡關，請參閱[DASH 求助管道](#omnipod-dash-where-to-get-help-for-dash)章節，了解如何向社群尋求支援。* -1. Open Android settings on your phone, scroll down and press on **Security and privacy (1)**. +1. 打開手機上的 Android 設定，向下捲動並點選**安全與隱私 (1)**。 ![android_settings_sec_priv](../images/android_16/android_settings_sec_priv.png) -2. Scroll down and press on **Privacy controls (1)**. +2. 向下捲動並點選**隱私控制 (1)**。 ![android_sec_priv](../images/android_16/android_sec_priv.png) -3. Press on **Permission manager (1)**. +3. 點選**權限管理員 (1)**。 ![android_priv_control](../images/android_16/android_priv_control.png) -3. Scroll down and press on **Nearby devices (1)**. +3. 向下捲動並點選**附近裝置 (1)**。 ![android_perm_man_nearby_dev](../images/android_16/android_perm_man_nearby_dev.png) -4. Browse the list of apps and press on the app you wish to revoke **Nearby devices** permissions for. +4. 瀏覽應用程式清單，點選你要撤銷**附近裝置**權限的應用程式。 - In this guide **Android Auto (1)** is the app we will revoke the permission on. + 在本指南中，我們以**Android Auto (1)** 作為撤銷權限的示範 App。 - To avoid bricking more pods we advise everyone initially to revoke the permission on all apps except **AAPS**. + 為避免讓更多 Pod 變磚，我們建議一開始先對除 **AAPS** 之外的所有應用程式撤銷該權限。 - ***NOTE:** If you are unsure which app is causing you an issue, disable them all (remember to check the list of known problem apps too and start with those) and if you can spare a few bricked pods on the way, enable the permission on one new app before every new Pod activation, until you can narrow down which app specifically causes your Pod issues. If you do identify new problematic apps please let us know on the #omnipod-dash Discord channel.* + ***注意：** 若不確定是哪個應用程式造成問題，請全部先停用（也記得先查看已知問題 App 清單，從那些開始）。如果你能接受在過程中有幾個 Pod 變磚，就在每次啟用新 Pod 前，僅替一個新的應用程式開啟該權限，逐步縮小範圍，直到找出造成 Pod 問題的特定應用程式。 如果你確定了新的問題應用程式，請在 Discord 的 #omnipod-dash 頻道告訴我們。* ![android_nearby_dev](../images/android_16/android_nearby_dev.png) -5. To revoke the permission Press on **Don't allow (1)**, then Press on **Don't allow anyway (2)**. If done correctly you should see **Don't allow (3)** as the selected Toggle option. You can now go back to the **Nearby device** menu by pressing the **Back arrow (4)** and change this setting on other apps if required. +5. 若要撤銷該權限，請點選 **Don't allow (1)**，然後點選 **Don't allow anyway (2)**。 若操作正確，您應會看到 **Don't allow (3)** 為已選取的切換選項。 現在您可以按下 **Back arrow (4)** 返回 **Nearby device** 選單；如有需要，也可在其他應用程式上變更此設定。 ![android_auto_nearby_dev](../images/android_16/android_auto_nearby_dev.png) ![android_auto_nearby_dev](../images/android_16/android_auto_nearby_dont_allow_anyway.png) ![android_auto_nearby_dev](../images/android_16/android_auto_nearby_dont_allow.png) -#### **How to re-enable "Nearby device" permissions for system apps and other apps:** +#### **如何為系統應用程式與其他應用程式重新啟用「Nearby device」權限：** -1. If required Reference the **"How to revoke "Nearby device" permissions for other apps"** section on how to get to the app privacy settings, then once in the **Nearby device** configuration proceed to 2. +1. 如有需要，請參閱 **「How to revoke "Nearby device" permissions for other apps」** 章節以瞭解如何前往應用程式的隱私設定，進入 **Nearby device** 設定後請繼續第 2 步。 -2. Browse the list of apps and press on the app you wish to allow **Nearby devices** permissions for. +2. 瀏覽應用程式清單，點選您希望允許 **Nearby devices** 權限的應用程式。 - In this guide **Android Auto (1)** is the app we will allow the permission on. + 在本指南中，**Android Auto (1)** 是我們要允許該權限的應用程式。 - You will notice that **Android Auto (1)** is missing in the app list after the permission is revoked. This is because the **Android Auto** app is a **System app** and by default system apps are hidden. + 您會注意到在撤銷權限後，應用程式清單中找不到 **Android Auto (1)**。 這是因為 **Android Auto** 應用程式是 **系統應用程式**，而系統應用程式在預設情況下會被隱藏。 ![android_auto_nearby_dev_missing](../images/android_16/android_auto_nearby_dev_missing.png) -3. To show hidden system apps Press on the **Three Dotted Lines (Hamburger) (1)**, then Press on **"Show System (1)"**. You should now be able to see the hidden system app in the list **Android Auto (3)**. +3. 若要顯示隱藏的系統應用程式，請點選 **三條線（漢堡選單）(1)**，接著點選 **"顯示系統 (1)"**。 現在您應該可以在清單中看到先前隱藏的系統應用程式 **Android Auto (3)**。 - ***NOTE:** If an app is revoked you will need to scroll down until you see the list of revoked apps lower down in the list.* + ***注意：** 如果某個應用程式已被撤銷，您需要往下捲動，直到在清單下方看到已撤銷的應用程式清單。* ![android_auto_nearby_dev_missing_hamburger](../images/android_16/android_auto_nearby_dev_missing_hamburger.png) ![android_auto_nearby_show_system](../images/android_16/android_auto_nearby_show_system.png) ![android_nearby_dev_system](../images/android_16/android_nearby_dev_system.png) -5. Follow the guidance in **"How to revoke "Nearby device" permissions for other apps"** in reverse to re-enable permissions for each app. +5. 請反向依照 **「How to revoke "Nearby device" permissions for other apps」** 的指引，為各個應用程式重新啟用權限。 --- -### 輸送暫停 +### 暫停輸送 - - 現在已無暫停按鈕。 如果你想要「暫停」藥量，你可以將 TBR 設置為零，持續 x 分鐘。 + - 現在已無暫停按鈕。 如果你想要「暫停」藥量，你可以將臨時基礎率設置為零，持續 x 分鐘。 - 在**設定檔切換**期間，DASH 必須在設置新的基礎**設定檔**之前暫停送藥。 如果兩個指令之間的通訊失敗，則輸送可能會保持暫停。 當這種情況發生時： - 將不會有胰島素輸送，包括基礎率、SMB、手動注射等。 - 可能會通知某個指令未確認：這取決於失敗發生的時間。 @@ -590,13 +590,13 @@ Follow this procedure to revoked the "Nearby device" permission for all apps exc - 如果**AAPS**無法自行恢復送藥（如果藥量無法連線、聲音被靜音等情況會發生），藥量每分鐘將發出 4 次嗶聲，持續 3 分鐘，然後如果送藥暫停超過 20 分鐘將每 15 分鐘重複這個過程。 - 對於未確認的指令，「重新整理 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 會因多種問題偶爾發生故障，包括 Pod 本身的硬體問題。 -- It is best practice not to raise support / replacement cases with Insulet, since AAPS is not an approved method of using the Pods. +- 建議不要向 Insulet 提出支援／更換案件，因為 AAPS 並非核准的 Pod 使用方式。 - 一份故障代碼列表可在 [**這裡找到**](https://github.com/openaps/openomni/wiki/Fault-event-codes)，以幫助確定原因。 --- @@ -608,30 +608,30 @@ Follow this procedure to revoked the "Nearby device" permission for all apps exc ### 幫浦無法連線警報 -When no communication can be established with the pod for a pre-configured 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]**. 建議設置的值是**120** 分鐘後提醒。 +當在預先設定的時間內無法與 Pod 建立連線時，會觸發「幫浦無法使用」警示。 您可以前往右上角三點選單，選取 **偏好設定** ➜ **本機警示** ➜ **幫浦無法使用門檻 [分鐘]** 來設定「幫浦無法使用」警示。 建議設置的值是**120** 分鐘後提醒。 --- ### 匯出設定 匯出**AAPS**設置可讓你恢復所有設置，可能更重要的是，恢復所有目標。 你可能需要將設置恢復至「最後一次正常運作的狀況」，或在卸載/重新安裝**AAPS**後，或在手機遺失的情況下，在新手機上重新安裝。 -***NOTE:** The active pod information is included in the exported settings. 如果你匯入了「舊」的匯出檔案，你的目前 Pod 會「失效」。 沒有其他選擇。 在某些情況下（如_程式化_的手機更換），你可能需要使用匯出的檔案來恢復**AAPS'**設置**同時保持當前活動的藥量**。 在這種情況下，重要的是需要包含目前啟用 Pod 的最新匯出設定檔案。* +***注意：** 作用中的 Pod 資訊會包含在匯出的設定中。 如果你匯入了「舊」的匯出檔案，你的目前 Pod 會「失效」。 沒有其他選擇。 在某些情況下（如_程式化_的手機更換），你可能需要使用匯出的檔案來恢復**AAPS'**設置**同時保持當前活動的藥量**。 在這種情況下，重要的是需要包含目前啟用 Pod 的最新匯出設定檔案。* **啟動 Pod 後立即匯出是一種好習慣**。 這樣，你將能夠在發生問題時恢復當前活動的藥量。 例如，當你更換備用手機時。 -Regularly (after each export preferably) copy your exported settings to a safe place (a cloud drive e.g. Google Drive) that is accessible by any phone when needed. This allows you to restore to a phone from anywhere in case of a phone loss or factory reset of your phone while you are not at home. +請定期（最好在每次匯出後）將您匯出的設定複製到安全的位置（例如雲端硬碟，如 Google Drive），以便在需要時任何手機都能存取。 如此一來，若您在外時手機遺失或執行恢復原廠設定，便能從任何地方將設定還原到一支手機。 --- ### 匯入設定 -**WARNING**: Please note that importing settings will possibly import an outdated Pod status (depending when you made the last export/backup). -As a result, there is a **risk of losing the active Pod!** (see **Exporting Settings**). -1. Only try an import when no other options are available. +**警告**：請注意，匯入設定時可能會匯入過期的 Pod 狀態（取決於您上次匯出／備份的時間）。 +因此，**有遺失作用中 Pod 的風險！**（請參閱 **匯出設定**）。 +1. 僅在沒有其他選項時，才嘗試匯入。 2. 當匯入具有啟用的 Pod 設定時，請確保匯出是在目前啟用的 Pod 下進行的。 **在有啟用 Pod 的情況下匯入：**（你有失去 Pod 的風險！） -1. **Make sure you are importing settings that were recently exported with the currently active Pod!** +1. **請確保您匯入的是最近、且與目前作用中 Pod 一同匯出的設定！** 2. 匯入你的設定。 3. 檢查所有偏好設定。 @@ -647,8 +647,8 @@ As a result, there is a **risk of losing the active Pod!** (see **Exporting Sett 當匯入包含已不再啟用的 Pod 資料時，AAPS 將嘗試與其連線，這顯然會失敗。 在這種情況下，你無法啟動新 Pod。 -To remove the old pod session: -1. “try” to de-activate the Pod. The de-activation will likely fail. +要移除舊的 Pod 工作階段： +1. 「嘗試」停用 Pod。 此停用動作很可能會失敗。 2. 選擇「重試」。 3. 在第二次或第三次重試後，你將獲得移除 Pod 的選項。 4. 一旦舊藥量被移除，你將能夠啟動新的藥量。 @@ -656,11 +656,11 @@ To remove the old pod session: --- ### 重新安裝 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!** +當解除安裝 **AAPS** 時，您將會遺失所有設定、目標以及目前的 Pod 工作階段。 **若要還原它們，請務必備妥最新的匯出設定檔！** 當在活動藥量中時，請確保你有當前藥量會話的匯出，否則在匯入舊設置時將失去目前的活動藥量。 -1. Export your settings and store a copy in a safe place (e.g Google Drive). +1. 請匯出您的設定，並將副本儲存在安全的位置（例如 Google Drive）。 2. 卸載**AAPS**並重新啟動你的手機。 3. 安裝新的**AAPS**版本。 4. 匯入你的設定。 @@ -671,7 +671,7 @@ When uninstalling **AAPS** you will lose all your settings, objectives and the c --- ### 更新 AAPS 至新版本 -在大多數情況下，無需卸載。 你可以透過啟動新版本的安裝進行「就地」安裝。 This is also possible when on an active Pod session. +在大多數情況下，無需卸載。 你可以透過啟動新版本的安裝進行「就地」安裝。 即使目前正處於作用中的 Pod 工作階段，也可以這麼做。 1. 匯出你的設定。 2. 安裝新的**AAPS**版本。 @@ -682,7 +682,7 @@ When uninstalling **AAPS** you will lose all your settings, objectives and the c --- ### Omnipod 驅動程式警報 -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 requiring their input to resolve the cause of the triggered alert. +**Omnipod Dash** 驅動程式會在 **總覽 分頁** 顯示多種獨特警示，其中多數為資訊性並可關閉，另有一些會提供需要使用者輸入的動作，以解決觸發該警示的原因。 你可能會遇到的主要警報總結如下： @@ -699,19 +699,19 @@ The Omnipod Dash driver presents a variety of unique alerts on the **Overview ta 所有 DASH 的開發工作都是由社區以**志願者**的身份進行的；請記住這一點，在要求協助之前使用以下準則： - **等級 0：** 閱讀此文件的相關部分，以確保你了解遇到困難的功能應如何工作。 -- **等級 1：** 如果你仍然遇到無法解決的問題，請使用[此邀請鏈接](https://discord.gg/4fQUWHZ4Mw)進入**Discord**的*#AAPS* 頻道。 There are also numerous Facebook and other groups you can ask in too (see [**Getting Help**](../GettingHelp/WhereCanIGetHelp.md)) +- **等級 1：** 如果你仍然遇到無法解決的問題，請使用[此邀請鏈接](https://discord.gg/4fQUWHZ4Mw)進入**Discord**的*#AAPS* 頻道。 也有許多 Facebook 與其他社群可供提問（請參閱 [**Getting Help**](../GettingHelp/WhereCanIGetHelp.md)）。 - **等級 2：** 搜尋現有問題，以查看你的問題是否已被報告，請在[問題](https://github.com/nightscout/AndroidAPS/issues)中確認/評論/添加有關你的問題的訊息。 如果沒有，請建立一個[新問題](https://github.com/nightscout/AndroidAPS/issues)並附上[你的日誌文件](../GettingHelp/AccessingLogFiles.md)。 - **保持耐心——我們社群中的大多數成員都是善良的志願者，解決問題通常需要使用者和開發者雙方的時間和耐心。** -When requesting help come prepared with the following information to help those in the community with your specific questions and problems: -- Android phone make and model -- Android OS version (e.g 15 or 16) - - Did you recently upgrade your Android OS version? -- The version of **AAPS** you are running -- Plain english description of the problem you are facing considering some of the following things - - Was it working before now? - - When did it work or not work? - - Did you make any changes to configuration or profile settings? - - Did you pair a new bluetooth device? - - Did you upgrade or install a new app? - - How long was it working before it stopped working? +當您尋求協助時，請先準備以下資訊，以便社群成員更有效地協助解決您的問題與疑問： +- Android 手機的品牌與型號 +- Android 作業系統版本（例如 15 或 16） + - 您最近是否升級了 Android 作業系統版本？ +- 您正在執行的 **AAPS** 版本 +- 請用簡明的英文描述您遇到的問題，並考量以下事項 + - 之前是否可以正常運作？ + - 從什麼時候開始可以或不可以運作？ + - 您是否變更了任何設定或設定檔的設定？ + - 您是否配對了新的藍牙裝置？ + - 您是否升級或安裝了新的應用程式？ + - 在停止運作之前，它運作了多久？ diff --git a/docs/CROWDIN/zh_TW/CompatiblePumps/OmnipodEros.md b/docs/CROWDIN/zh_TW/CompatiblePumps/OmnipodEros.md index 6ead22bbaad8..de226c8457de 100644 --- a/docs/CROWDIN/zh_TW/CompatiblePumps/OmnipodEros.md +++ b/docs/CROWDIN/zh_TW/CompatiblePumps/OmnipodEros.md @@ -39,7 +39,7 @@ **安全第一** - 不要在無法從錯誤中恢復的環境中嘗試此過程（必備項包括額外的 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 只允許單一裝置向其發送通訊。 從那時起，成功啟動 Pod 的裝置將是唯一能夠與其通訊的裝置。 這意味著你透過 AAPS Omnipod 驅動程式和 RileyLink 啟用了 Omnipod Eros pod，**你將無法再使用你的 PDM 與 pod 通訊**。 AAPS Omnipod 驅動程式與 RileyLink 現在替代你的 PDM。 *這並不意味著你應該丟掉你的 PDM，建議保留他作為備用並在 AAPS 運作不正常時使用。* **你可以配置多個 RileyLink，但一次只能選擇一個 RileyLink 與 pod 通訊。** AAPS Omnipod 驅動程式支援在 RileyLink 配置中添加多個 RileyLink，但一次只能選擇一個 RileyLink 用來發送和接收通訊。 @@ -201,11 +201,11 @@ > ![Deactivate_Pod_4](../images/omnipod/Deactivate_Pod_4.png) > - > **如果停用失敗** 並且你未收到確認嗶聲，你可能會收到 **RileyLink 無回應** 或 **幫浦無回應訊息**。 請按 **重試 (1)** 按鈕再次嘗試停用。 如果停用持續失敗，請點擊 **丟棄幫浦 (2)** 按鈕遺棄幫浦。 你現在可以移除 Pod，因為該使用階段已停用。 如果你的幫浦發出尖叫警報，你可能需要手動將其靜音（使用別針或回形針），因為 **丟棄幫浦 (2)** 按鈕無法使其靜音。 + > **如果停用失敗** 並且你未收到確認嗶聲，你可能會收到 **RileyLink 無回應** 或 **幫浦無回應訊息**。 請按 **重試 (1)** 按鈕再次嘗試停用。 如果停用持續失敗，請點擊 **丟棄幫浦 (2)** 按鈕遺棄幫浦。 你現在可以移除 Pod，該使用階段已停用。 如果你的幫浦發出尖叫警報，你可能需要手動將其靜音（使用別針或回形針），因為 **丟棄幫浦 (2)** 按鈕無法使其靜音。 > > > ![Deactivate_Pod_5](../images/omnipod/Deactivate_Pod_5.png) ![Deactivate_Pod_6](../images/omnipod/Deactivate_Pod_6.png) -4. 停用成功後會顯示綠色勾號。 點擊 **下一步** 按鈕以顯示 Pod 停用畫面。 你現在可以移除 Pod，因為該使用階段已停用。 +4. 停用成功後會顯示綠色勾號。 點擊 **下一步** 按鈕以顯示 Pod 停用畫面。 你現在可以移除 Pod，該使用階段已停用。 > ![Deactivate_Pod_7](../images/omnipod/Deactivate_Pod_7.png) @@ -591,7 +591,7 @@ Omnipod 驅動程式設置可透過左上角的**漢堡選單**中的**設置生 ### 確認嗶聲提示 -提供來自藥筒的確認聲音提示，用於注射、基礎輸注、SMB以及TBR輸送和變更。 +提供來自藥筒的確認聲音提示，用於注射、基礎輸注、超微劑量(SMB)以及臨時基礎率(TBR)輸送和變更。 - **\*注射嗶聲啟用：**啟用或停用在注射送達時的確認嗶聲聲。 - **\*基礎率嗶聲啟用：**啟用或停用在設定新基礎率、取消啟動基礎率或更改目前基礎率時的確認嗶聲聲。