Omnipod DASH

These instructions are for configuring the Omnipod DASH generation pump (NOT Omnipod Eros), available in AAPS from version 3.0.

Omnipod DASH özellikleri

These are the specifications of the Omnipod DASH (‘DASH’) and what differentiates it from the Omnipod EROS (‘EROS’):

  • The DASH pods are identified by a blue needle cap (EROS has a clear needle cap). The pods are otherwise identical in terms of physical dimensions.

  • DASH does not require a BLE link/bridge device (NO RileyLink, OrangeLink, or EmaLink needed).

  • The DASH’s Bluetooth connection is used only when sending a command (e.g a Bolus), and disconnects right after issuing the command.

  • No more “no connection to link device / pod” errors with DASH.

  • AAPS will wait for pod’s accessibility to send commands.

  • On pod activation, AAPS will find and connect to a new DASH pod.

  • Expected range from phone: 5-10 meters (YMMV).

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 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 for more info on the Bonding settings.

  • Too frequent basal updates may cause basal insulin delivery problems 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 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 for details.

  • There are a number of known issues with Bluetooth which can cause pod activation problems. See Bluetooth Troubleshooting for the known issue and solutions to these problems.

Donanım/Yazılım Gereksinimleri

  • Omnipod DASH is identified by the blue needle cap.

Omnipod Pod

  • A Compatible Android phone with a Bluetooth Low Energy (BLE) (see Phones 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.

      • NOT:

        • 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 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 for advice on other Bluetooth issues) specifically the Bluetooth related issues section.

    • For Android 15 or below: You MUST use Version 3.0 or newer of AAPS using the Build APK 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 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.

  • A supported Continuous Glucose Monitor (CGM)

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.

Başlamadan önce

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 to avoid running into a known problem.

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)

  5. Correct version of AAPS built and installed

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.

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 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.

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 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.

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.

Selecting Dash in AAPS

There are two available options to configure Omnipod in AAPS:

Option 1: New installations

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

When in doubt you can also select “Virtual Pump” and select “DASH” later, after setting up AAPS (See Option 2).

Option 2: The Config Builder

On an existing installation you can select the DASH pump from the Config builder:

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 can be found below in the DASH settings section of this document.

Enable_Dash_3

Verification of Omnipod Driver Selection

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

Dash Konfigürasyonu

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 ‘Refresh’ pod connectivity and status, be able to silence pod alarms when the pod beeps

POD_MGMT_LOGO ‘Pod Management’ (Activate, Deactivate, Play test beep, and Pod history)

Activate Pod

  1. DASH sekmesine gidin. POD YNTM (1) butonuna ve ardından **Pod Etkinleştir (2) **butonuna tıklayın.

    Activate_Pod_1

    Activate_Pod_2

  2. Podu Doldur ekranı görüntülenir. 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.

    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.

    Activate_Pod_3

    Activate_Pod_4

    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

  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 hazırlama işlemini tamamlamak ve Pod Ekle ekranını görüntülemek için İleri butonunu tıklayın.

    Activate_Pod_5 Activate_Pod_6

  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.
    If you get skin irritation from the adhesive consider using a Barrier Wipe or Barrier Spray.

    Remove the pod’s blue plastic needle cap. 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.

    Bitirdiğinizde, İleri butonunu tıklayın.

    Activate_Pod_8

  5. Pod Ekle iletişim kutusu şimdi görünecektir. click on the OK button ONLY if you are ready to deploy the cannula!

    Activate_Pod_9

  6. After pressing OK, it may take some time before the DASH responds and inserts the cannula (1-2 minutes maximum). Be patient!

    NOTE: Before the cannula is inserted, it is good practice to pinch the skin near the cannula insertion point. Bu iğnenin düzgün bir şekilde yerleştirilmesini sağlar ve tıkanıklık oluşturma şansınızı azaltır.

    Activate_Pod_10 Activate_Pod_11

  7. 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.

    Activate_Pod_12

  8. Pod etkinleştirildi ekranı görüntülenir.

    Yeşil Bitti düğmesini tıklayın.

    Tebrikler! You have now started a new pod session.

    Activate_Pod_13

  9. Pod yönetimi menüsünde şimdi Pod Etkinleştir (1) butonu <em x-id”3”=>devre dışı olmalı ve Pod’u Devre Dışı Bırak (2) butonu aktif olmalıdır.. Bunun nedeni, bir podun artık etkin olması ve o anda etkin olan podu devre dışı bırakmadan ek bir pod etkinleştirememenizdendir.

    DASH sekme ekranına dönmek için telefonunuzdaki geri düğmesini tıklayın. Şimdi aktif pod oturumunuz için mevcut bazal oran, pod rezervuar seviyesi, iletilen insülin, pod hataları ve uyarılar dahil Pod bilgileri görüntülenecektir.

    NOTE: For more details on the information displayed go to the DASH Tab section of this document.

    Activate_Pod_14

    Activate_Pod_15

    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).

Deactivate 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.

To deactivate a pod (either from expiration or from a pod failure):

  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.

    Deactivate_Pod_1

    Deactivate_Pod_2

  2. Pod’u Devre Dışı Bırak ekranında, podu devre dışı bırakma işlemini başlatmak için İleri butonunu tıklayın.

    Devre dışı bırakmanın başarılı olduğuna dair poddan bir onay bip sesi alacaksınız.

    Deactivate_Pod_3

    Deactivate_Pod_4

  3. A green checkmark will be displayed upon successful deactivation. Pod devre dışı ekranını görüntülemek için İleri butonunu tıklayın.

    Etkin oturum devre dışı bırakıldığı için artık podunuzu çıkartabilirsiniz.

    Deactivate_Pod_5

  4. Pod Yönetimi ekranına dönmek için yeşil butona tıklayın.

    Deactivate_Pod_6

  5. Artık Pod Yönetimi menüsündesiniz; DASH sekmesine dönmek için telefonunuzdaki geri butonuna basın.

    Pod durumu: alanında bir Aktif pod yok mesajının görüntülendiğini doğrulayın.

    Deactivate_Pod_2

    Deactivate_Pod_8

Resuming Insulin Delivery

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 in the troubleshooting section for more details.

When insulin delivery is suspended you will need to issue a 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.

    Resume_1 Resume_2

  2. İletimi sürdür komutu başarılı olduğunda, bir onay iletişim kutusu İnsülin iletimi yeniden başlatıldı. mesajını görüntüler. Onaylamak ve devam etmek için Tamam’ı tıklayın.

    Resume_3

  3. DASH sekmesi, Pod durumu (1) satırını ÇALIŞIYOR olarak günceller ve İletime Devam Et butonu artık görüntülenmez.

    Resume_4

Silencing Pod Alerts

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.

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’.

  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. Bu aynı zamanda ALARMLARI SUSTUR (3) butonunun görüntülenmesini de tetikler.

    ACK_alerts_1

  2. Go to the DASH tab and press the SILENCE ALERTS (2) button. AAPS sends the command to the pod to deactivate the pod expiration warning beeps and updates the Pod status (1) field with ACKNOWLEDGE ALERTS.

    ACK_alerts_2

  3. Uyarıların başarıyla devre dışı bırakılması üzerine, etkin pod tarafından 2 bip sesi verilir ve bir onay iletişim kutusunda Etkin alarmlar susturuldu. mesajı görüntülenir. İletişim kutusunu onaylamak ve kapatmak için Tamam butonunu tıklayın.

    ACK_alerts_3

  4. DASH sekmesine gidin. Etkin Pod Alarmları satırında, uyarı mesajı artık görüntülenmez ve etkin pod artık sona erme uyarısı bip sesi vermez.

View Pod History

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 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.

    Pod_history_1
    Pod_history_2

  2. **Pod geçmişi ** ekranında, All (1) (Tümü) varsayılan kategorisi ile tüm pod Eylemleri (3) ve Sonuçları (4) Tarih ve Saat (2) ters kronolojik sırada görüntülenir. Use your phone’s back button 2 times to return to the DASH tab in the main AAPS interface.

    Pod_history_3 Pod_history_4

DASH Sekmesi

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

Fields

  • Bluetooth Adresi: Bağlı Pod’un mevcut bluetooth adresini görüntüler.

  • Bluetooth Status: Displays the current connection status.

  • Sıra Numarası: Etkin POD’un sıra numarasını görüntüler.

  • Firmware Versiyonu: Etkin bağlantının firmware sürümünü görüntüler.

  • Pod üzerindeki zaman: Pod üzerindeki geçerli saati görüntüler.

  • Pod durumu: Pod durumunu görüntüler.

  • Son bağlantı: Pod ile son iletişimin zamanını görüntüler.

    • Biraz önce - 20 saniyeden kısa bir süre önce.

    • Bir dakikadan kısa bir süre önce - 20 saniyeden uzun, ancak 60 saniyeden kısa bir süre önce.

    • 1 dakika önce - 60 saniyeden uzun ancak 120 saniyeden kısa (2 dakika)

    • XX dakika önce - XX değeriyle tanımlanan 2 dakikadan daha uzun bir süre önce

  • Son bolus: Etkin pod’dan gönderilen son bolus miktarını ve ne kadar süre önce verildiğini parantez içinde görüntüler.

  • Bazal oranı: Bazal oran profilinden geçerli zaman için programlanmış bazal oranı görüntüler.

  • Geçici bazal oranı: Şu anda çalışmakta olan Geçici Bazal Oranı aşağıdaki biçimde görüntüler

    • {Units per hour} @{TBR start time} ({minutes run}/{total minutes TBR will be run})

    • Example:* 0.00U/h @18:25 ( 90/120 minutes)

  • Rezervuar: Rezervuarda 50 üniteden fazla insülin olduğuda 50+Ü’den fazla kalanı gösterir. 50 Ü’nin altında, tam birimler görüntülenir.

  • Toplam iletilen: Rezervuardan iletilen toplam insülin ünite miktarını görüntüler. Bu miktar etkinleştirme ve hazırlama için kullanılan insülini de içerir.

  • Hatalar: Karşılaşılan son hatayı görüntüler. Review the Pod history and log files for past errors and more detailed information.

  • Etkin pod alarmları: Etkin pod alarmlarını gösteren satırdır.

Buttons

Refresh_Icon Sends a refresh command to the active pod to update communication.

  • Pod durumunu yenilemek ve metin içeren (belirsiz) durum satırlarını yenilemek için kullanın.

  • See the Troubleshooting section below for additional information.

POD_MGMT_Icon Navigates to the Pod management menu.

ack_alert_logo When pressed this will disable the pod alerts beeps and notifications (expiry, low reservoir..).

  • Bu buton, yalnızca pod kullanım süresi (72saat) aşılmışsa görüntülenir.

  • Başarılı bir devre dışı bırakmanın ardından bu simge artık görünmeyecektir.

RESUME_Icon Resumes the currently suspended insulin delivery in the active pod.

Pod Management Menu

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_Tab_2

DASH_Tab_3

The table below describes each button and it’s function:

Button

Function

1

Access the Pod Mgmt settings

2

Activate Pod: Primes and activates a new pod.

3

Deactivate Pod: Deactivates the currently active pod.

4

Play Test Beep : Plays a single test beep on the pod when pressed.

5

Pod history : Displays the active pod activity history.

Dash Ayarları

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

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

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.

Confirmation beeps

Dash_settings_4

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.

SMB beeps enabled: Enable or disable confirmation beeps when a SMB is delivered.

TBR beeps enabled: Enable or disable confirmation beeps when a TBR is set or canceled.

Alerts

Dash_settings_5

Provides AAPS alerts for pod expiration, shutdown, low reservoir based on the defined threshold units.

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.

Expiration reminder enabled: Enable or disable the pod expiration reminder set to trigger when the defined number of hours before shutdown is reached.

Hours before shutdown: Defines the number hours before the active pod shutdown occurs, which will then trigger the expiration reminder alert.

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.

Number of units: The number of units at which to trigger the pod low reservoir alert.

Notifications

Dash_settings_6

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.

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.

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.

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.

Eylemler (EYLEM) Sekmesi

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. Go to the Actions (ACT) tab in the main AAPS interface.

  2. Under the Careportal (1) section the Insulin and Cannula fields will have their age reset to 0 days and 0 hours after each pod change. Bu Omnipod pompasının çalışma şekli nedeniyle böyle yapılmaktadır. Pod, kanülü doğrudan pod uygulama bölgesinde deriye yerleştirdiği için, Omnipod pompalarında hortum kullanılmaz. Bu nedenle, bir pod değişikliğinden sonra bu değerlerin her birinin yaşı otomatik olarak sıfırlanır. Pompa pil yaşı pod pili her zaman kendi ömründen daha fazla olacağı için (maksimum 80 saat) rapor edilmez. Pompa pili ve insülin rezervuarı, her pod içinde yer almaktadır.

    ACT_1

Level

Insulin Level

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 Ünitenin Altında - Pod tarafından bildirilen rezervuarda kalan insülin miktarı.

Additional note:

  • SMS - SMS yanıtlarında insülin seviyesi 50+Ü veya değer görünür.

  • Nightscout - Nightscout’a (sürüm 14.07 ve daha eski) 50 üniteden fazla olduğunda 50 değerini yükler. Daha yeni sürümler, 50 ünite üzerinde olduğunda 50+ değerini bildirir.

Troubleshooting

This section covers common known issues and solutions for Omnipod DASH use with AAPS. There is also General Troubleshooting section in the documentation that should be reviewed as it covers relevant topics for some Pod issues too.

Where to get help for 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:

  • Seviye 0: Sorun yaşadığınız işlevin nasıl çalışması gerektiğini anladığınızdan emin olmak için bu dokümantasyonun ilgili bölümünü okuyun.

  • Seviye 1: Bu dokümantasyonu kullanmanıza rağmen hâlâ çözemediğiniz sorunlarla karşılaşıyorsanız, lütfen bu davet bağlantısını kullanarak Discord’da * #AAPS* kanalına gidin. There are also numerous Facebook and other groups you can ask in too (see Getting Help)

  • Level 2: Search existing issues to see if your issue has already been reported at Issues if it exists, please confirm/comment/add information on your problem. If not, please create a new issue and attach your log files.

  • Sabırlı olun - topluluğumuzun üyelerinin çoğu iyi huylu gönüllülerden oluşur ve sorunları çözmek genellikle hem kullanıcılar hem de geliştiriciler için zaman ve sabır gerektirir.

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?