From 87caa118fb9aacc50f306e60d7025429132b69de Mon Sep 17 00:00:00 2001 From: marionbarker Date: Sun, 26 Oct 2025 08:35:57 -0700 Subject: [PATCH 1/4] Move Atlas, InPlay pod info to FAQs --- docs/build/phone.md | 20 +- docs/build/pump.md | 8 +- docs/build/rileylink.md | 7 +- docs/faqs/img/saw-atlas-identifiers.svg | 1093 +++++++++++++++++++++++ docs/faqs/omnipod-faqs.md | 36 + 5 files changed, 1138 insertions(+), 26 deletions(-) create mode 100644 docs/faqs/img/saw-atlas-identifiers.svg diff --git a/docs/build/phone.md b/docs/build/phone.md index a6178c5a97f..bd99b5d30d9 100644 --- a/docs/build/phone.md +++ b/docs/build/phone.md @@ -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. @@ -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-inplay-dash-pods){: target="_blank" } warning) These phones are compatible with *iOS* 17, 18 and 26 diff --git a/docs/build/pump.md b/docs/build/pump.md index 2004a754cc5..160d2278d46 100644 --- a/docs/build/pump.md +++ b/docs/build/pump.md @@ -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). @@ -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. diff --git a/docs/build/rileylink.md b/docs/build/rileylink.md index de225fbbe5e..b40d4429e1e 100644 --- a/docs/build/rileylink.md +++ b/docs/build/rileylink.md @@ -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 diff --git a/docs/faqs/img/saw-atlas-identifiers.svg b/docs/faqs/img/saw-atlas-identifiers.svg new file mode 100644 index 00000000000..90751817af3 --- /dev/null +++ b/docs/faqs/img/saw-atlas-identifiers.svg @@ -0,0 +1,1093 @@ + +image/svg+xmlSAW, "TWI Board"Atlas, "InPlay BLE" diff --git a/docs/faqs/omnipod-faqs.md b/docs/faqs/omnipod-faqs.md index 93d6ea1e8a5..40462a2f0fe 100644 --- a/docs/faqs/omnipod-faqs.md +++ b/docs/faqs/omnipod-faqs.md @@ -23,6 +23,42 @@ You do not need the Omnipod Personal Diabetes Manager (PDM), just the pod suppli DASH pumps communicate with the phone via Bluetooth so they do not require a RileyLink compatible device. + +### iPhone 16 and Atlas or InPlay DASH pods + +!!! warning "iPhone 16 and Omnipod DASH" + **iPhone 16 only** + + **Other phones, including iPhone 17, work fine with InPlay DASH pods** + +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. + +* The left images show the SAW marking for "TWI Board" DASH pods +* The right images show the Atlas marking for "InPlay BLE" DASH pods +* The exact location of the marking varies according to manufacture location and date but the SAW and Atlas determine the internal BLE configuration for that pod + +![identifying marks for SAW and Atlas DASH pods](img/saw-atlas-identifiers.svg){width="750"} +{align="center"} + +#### Characteristics of Atlas with iPhone 16 + +* The Atlas DASH 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 +* Although `InPlay` pods do work with the iPhone 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 + * There is a work-around to keep these pods more connected by issuing a keep-alive message before the 3 minute BLE disconnect; but it uses extra battery for both the phone and the pod + * If you are forced to use an iPhone 16 with InPlay pods, reach out for help and this work-around can be made available + +> 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. + +> 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. + + - - - ## What about *Tidepool Loop*? From 82025082a7daef854ac5d3237c5d364fb97912db Mon Sep 17 00:00:00 2001 From: marionbarker Date: Sun, 26 Oct 2025 08:42:24 -0700 Subject: [PATCH 2/4] fix typo and link --- docs/build/phone.md | 2 +- docs/faqs/omnipod-faqs.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/build/phone.md b/docs/build/phone.md index bd99b5d30d9..e06689b2123 100644 --- a/docs/build/phone.md +++ b/docs/build/phone.md @@ -40,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 (phone is compatible but see [InPlay DASH pod](../faqs/omnipod-faqs.md#iphone-16-and-inplay-dash-pods){: target="_blank" } warning) +- 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 diff --git a/docs/faqs/omnipod-faqs.md b/docs/faqs/omnipod-faqs.md index 40462a2f0fe..22473300a02 100644 --- a/docs/faqs/omnipod-faqs.md +++ b/docs/faqs/omnipod-faqs.md @@ -51,7 +51,7 @@ Some of the DASH pods produced in 2025 have different chips and firmware. The on * 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 - * There is a work-around to keep these pods more connected by issuing a keep-alive message before the 3 minute BLE disconnect; but it uses extra battery for both the phone and the pod + * There is a work-around to keep these pods more connected by issuing a keep-alive message before the 3-minute BLE disconnect; but it uses extra battery for both the phone and the pod * If you are forced to use an iPhone 16 with InPlay pods, reach out for help and this work-around can be made available > 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. From 33a1ad78fb12459311c917067a74edf4d0047b91 Mon Sep 17 00:00:00 2001 From: marionbarker Date: Sun, 26 Oct 2025 09:13:05 -0700 Subject: [PATCH 3/4] better graphic --- docs/faqs/img/saw-atlas-identifiers.svg | 155194 ++++++++++++++++++++- 1 file changed, 155115 insertions(+), 79 deletions(-) diff --git a/docs/faqs/img/saw-atlas-identifiers.svg b/docs/faqs/img/saw-atlas-identifiers.svg index 90751817af3..70e668b131b 100644 --- a/docs/faqs/img/saw-atlas-identifiers.svg +++ b/docs/faqs/img/saw-atlas-identifiers.svg @@ -1,8 +1,8 @@ SAW, "TWI Board"SAW, "TWI Board"Atlas, "InPlay BLE"Atlas, "InPlay BLE" + y="-7380.5786" /> From d2b21ac4d43374ea4fae7a17592e607056d9bd5f Mon Sep 17 00:00:00 2001 From: marionbarker Date: Sun, 26 Oct 2025 09:18:38 -0700 Subject: [PATCH 4/4] minor nit --- docs/faqs/omnipod-faqs.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/faqs/omnipod-faqs.md b/docs/faqs/omnipod-faqs.md index 22473300a02..99eb1b84849 100644 --- a/docs/faqs/omnipod-faqs.md +++ b/docs/faqs/omnipod-faqs.md @@ -35,7 +35,7 @@ Some of the DASH pods produced in 2025 have different chips and firmware. The on * The left images show the SAW marking for "TWI Board" DASH pods * The right images show the Atlas marking for "InPlay BLE" DASH pods -* The exact location of the marking varies according to manufacture location and date but the SAW and Atlas determine the internal BLE configuration for that pod +* 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 ![identifying marks for SAW and Atlas DASH pods](img/saw-atlas-identifiers.svg){width="750"} {align="center"}