Skip to content

Commit d6b48cc

Browse files
committed
minor updates
1 parent e588ef5 commit d6b48cc

File tree

3 files changed

+12
-7
lines changed

3 files changed

+12
-7
lines changed

docs/build/phone.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -40,7 +40,8 @@ These phones require *iOS* 26 and `Loop version 3.8.x` or newer
4040

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

43-
- 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)
43+
- iPhone 16, all variants: **not recommended for use with Omnipod**
44+
* iPhone 16 is compatible but see [InPlay DASH pod](../faqs/omnipod-faqs.md#iphone-16-and-atlas-or-inplay-dash-pods){: target="_blank" } warning)
4445

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

docs/faqs/omnipod-faqs.md

Lines changed: 9 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -31,11 +31,13 @@ DASH pumps communicate with the phone via Bluetooth so they do not require a Ril
3131

3232
**Other phones, including iPhone 17, work fine with InPlay DASH pods**
3333

34-
Some of the DASH pods produced in 2025 have different chips and firmware. The only way to tell the difference before use is to examine the paper cover over the pods inside the box as shown in the graphic below.
34+
Beginning in 2025, some of the DASH pods are produced with a newer version of chips and firmware. The only way to tell the difference before use is to examine the paper cover over the pods inside the box for the word `Atlas` (newer) or `SAW` (older) as shown in the graphic below. It is anticipated that `Atlas` pods, which report electronically as `InPlay BLE`, will become more common.
3535

36-
* The left images show the SAW marking for "TWI Board" DASH pods
37-
* The right images show the Atlas marking for "InPlay BLE" DASH pods
38-
* The exact location of the marking varies according to manufacture location and date but the SAW and Atlas indicates the internal BLE configuration for that pod
36+
**If you do not already own an iPhone 16, it is strongly suggested you choose an older (iPhone 15 or SE or older) or newer (iPhone 17) phone.**
37+
38+
* The left images show the SAW marking for `TWI Board` DASH pods
39+
* The right images show the Atlas marking for `InPlay BLE` DASH pods
40+
* The exact location of the marking varies according to manufacture location and date but the `SAW` or `Atlas` notation indicates the internal BLE configuration for that pod
3941

4042
![identifying marks for SAW and Atlas DASH pods](img/saw-atlas-identifiers.svg){width="750"}
4143
{align="center"}
@@ -57,7 +59,9 @@ Some of the DASH pods produced in 2025 have different chips and firmware. The on
5759

5860
> 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 including the iPhone 16.
5961
60-
> Some InPlay DASH pods were manufactured in Feb 2025. Some TWI DASH pods were manufactured in May 2025. We have no insight into the deployment plans from Insulet. Just pay attention if you have an iPhone 16. Otherwise, you won't notice a difference.
62+
> The earliest `Atlas` DASH pods noticed by the OS-AID community were manufactured in Feb 2025. Some TWI DASH pods were manufactured in May 2025. Later in 2025, `Atlas` DASH pods with July 2025 and later manufacture dates were seen.
63+
64+
We have no insight into the deployment plans from Insulet. Just pay attention if you have an iPhone 16. Otherwise, you won't notice a difference.
6165

6266

6367
- - -

docs/version/development.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -63,7 +63,7 @@ The experimental `pod-keep-alive` branch has a new "Pod Keep Alive" option at th
6363

6464
It was tested for LoopWorkspace and Trio.
6565

66-
The concept is by choosing one of the Pod Keep Alive choices, the app sends a getStatus to the pod before the 3 minute disconnect happens. Therefore, so long as you and the pod stay close to the phone, the pod will be connected for a bolus (either manual or automatic) or temp basal or command to modify scheduled basal rates.
66+
The concept is by choosing one of the Pod Keep Alive choices, the app sends a getStatus to the pod before the 3 minute disconnect happens. Therefore, so long as you and the pod stay close to the phone, the pod will be connected for any command (either manual or automatic) including bolus, temp basal, modify scheduled basal rates, suspend, or deactivate.
6767

6868
The selection for Pod Keep Alive is found at the bottom of the Pod settings screen.
6969

0 commit comments

Comments
 (0)