You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/CROWDIN/el/CompatiblePumps/OmnipodDASH.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -51,29 +51,29 @@ The instructions below explain how to activate a new pod session using **AAPS**.
51
51
52
52
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.
53
53
54
-
####**SAFETY FIRST** - You **SHOULD NOT** try to connect **AAPS** to a pod for the first time without having access to all of the following:
54
+
### **SAFETY FIRST** - You **SHOULD NOT** try to connect **AAPS** to a pod for the first time without having access to all of the following:
55
55
1. Extra pods (3 or more spare)
56
56
2. Spare Insulin and MDI equipment
57
57
3. A working Omnipod PDM (In case **AAPS** fails)
58
58
4. Supported Phones are a must! (See [Hardware/Software Requirements](#hardware-software-requirements))
59
59
5. Correct version of AAPS built and installed
60
60
61
-
####**Your Omnipod Dash PDM will become redundant after the AAPS Dash driver activates your pod.**
61
+
### **Your Omnipod Dash PDM will become redundant after the AAPS Dash driver activates your pod.**
62
62
- 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).
63
63
- The DASH can only facilitate a single Bluetooth device (e.g PDM or Phone) connection to manage and send commands.
64
64
- 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.
65
65
-**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.
66
66
67
-
####Your pod **WILL NOT** stop delivering insulin when it is not connected to AAPS.
67
+
### Your pod **WILL NOT** stop delivering insulin when it is not connected to AAPS.
68
68
Default basal rates are programmed on the pod on activation as defined in the current active [**Profile**](../SettingUpAaps/YourAapsProfile.md).
69
69
As long as **AAPS** is operational it will send basal rate adjustment commands that run for a maximum of 120 minutes.
70
70
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).
71
71
72
-
####**AAPS Profile(s) do not support 30 minute basal rate time frames**
72
+
### **AAPS Profile(s) do not support 30 minute basal rate time frames**
73
73
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**.
74
74
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.
75
75
76
-
####**0U/h Profile basal rates are NOT supported in AAPS**
76
+
### **0U/h Profile basal rates are NOT supported in AAPS**
77
77
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.
78
78
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.
79
79
**NOTE:** The lowest basal rate allowed by the DASH in **AAPS** is 0.05U/h.
0 commit comments