Skip to content

Move Atlas, InPlay pod info to Omnipod FAQs #953

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
Oct 26, 2025
Merged

Move Atlas, InPlay pod info to Omnipod FAQs #953

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
87caa11
Move Atlas, InPlay pod info to FAQs
marionbarker Oct 26, 2025
8202508
fix typo and link
marionbarker Oct 26, 2025
33a1ad7
better graphic
marionbarker Oct 26, 2025
d2b21ac
minor nit
marionbarker Oct 26, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 1 addition & 19 deletions docs/build/phone.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -30,24 +30,6 @@ You need a minimum version of the mobile operating software, called the *iOS*, t

* The developers maintain support for the current and one-level earlier *iOS*

### iPhone 16 and InPlay DASH pods

!!! warning "iPhone 16 and Omnipod DASH"
Some of the DASH pods produced in 2025 have different chips and firmware.

* These pods, which advertise a Bluetooth Device name of `InPlay BLE` and indicate `-Atlas` in small print on the paper pod cover are fully compatible with all iPhone models except iPhone 16
* Early reports indicate the `InPlay BLE` pods work fine with iPhone 17
* Although `InPlay` pods do work with the 16 you may notice some communication issues
* It can take many attempts to get the pod to initially connect when pairing; just keep hitting retry
* Once the pod disconnects itself from the phone Bluetooth, the phone is slow to reconnect the pod to the *Loop* app
* Pod firmware initiates the disconnect 3 minutes after the last message exchange
* With other models, the reconnect happens in about 1 sec
* With iPhone 16, this can take many seconds and sometimes a few minutes
* When the pod is not connected, neither automatic nor manual commands can be sent to the pod to modify insulin delivery
* No solution to this issue is known

> DASH pods that advertise a Bluetooth Device name of `TWI Board` and indicate `-SAW` in small print on the paper pod cover are fully compatible with all phones included the iPhone 16.

### Compatible Device

All the devices listed below are currently compatible with Loop. They are separated by the available *iOS* for the phone.
Expand All @@ -58,7 +40,7 @@ These phones require *iOS* 26 and `Loop version 3.8.x` or newer

These phones require *iOS* 18 and are compatible with *iOS* 26

- iPhone 16, all variants
- iPhone 16, all variants (phone is compatible but see [InPlay DASH pod](../faqs/omnipod-faqs.md#iphone-16-and-atlas-or-inplay-dash-pods){: target="_blank" } warning)

These phones are compatible with *iOS* 17, 18 and 26

Expand Down
8 changes: 6 additions & 2 deletions docs/build/pump.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@
- If you have a Medtronic pump, check the [Medtronic Pump Version](#check-medtronic-pump-version) list to ensure compatible model/firmware
- If you use [Omnipod](#omnipod-pumps) - check which kind
- If you use [Dana](#sooil-dana-pumps) - check which kind
- If you use [Medtrum Nano](#medtrum-touchcare-nano) - Check which loop version
- If you use [Medtrum Nano](#medtrum-nano) - Check which loop version

!!! question "FAQs"
- **"How can I find a compatible Medtronic pump?"** Refer to [Finding a Medtronic Pump](#finding-a-medtronic-pump).
Expand Down Expand Up @@ -226,7 +226,11 @@ The DanaRS was first released in 2002, with firmware version v1 which is not sup
## Medtrum Nano

!!! warning "You must build feat/dev-medtrum branch to use Medtrum patch pumps"
The Medtrum patch pump is in feat/dev-medtrum (as of version v3.9.0) and is experimental as of now
The Medtrum patch pump is in feat/dev-medtrum (as of version v3.9.0) and is experimental as of now.

**Be very careful running this. The initial version had a bug where a delivered bolus was not always recorded properly. This is just one example of why only experts should volunteer to test experimental code.**

Follow along in the [zulipchat Medtrum channel](https://loop.zulipchat.com/#narrow/channel/144182-development/topic/Medtrum.20Nano.20-.20pumps.20for.20development.20use/with/481836247).

!!! info "All versions are supported!"
Both 200U (MD0201 & MD8201) and 300U (MD8301) version are supported with the correct version of the *Loop* app.
Expand Down
7 changes: 2 additions & 5 deletions docs/build/rileylink.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,14 +1,11 @@
## Order a RileyLink Compatible Device

**Not needed for any pump that supports direct Bluetooth BLE commands**

* **Dana**
* **DASH**
**Not needed for any pump that supports direct Bluetooth BLE commands such as Dana, DASH and Medtrum**

**Required when using an older Medtronic pump or Omnipod Eros pods**

!!! info "Time Estimate"
- 0 minutes if you plan to use a Dana pump or a DASH Omnipod pump - you don't need one
- 0 minutes if you plan to use a pump that supports direct BLE communication - you don't need one
- 15-20 minutes to read about RileyLink compatible devices
- 15 minutes to order a device

Expand Down
Loading