DASH POD ON LOOP ERROR oxcb: #2169
Comments
|
This is a pod error that can happen sometimes with pods. It is not caused by Loop. It is always important to have a backup method for insulin delivery whether using Loop or the Insulet-provided PDM. If I plan to be away from home, I carry a small kit with insulin syringes and a vial with a small amount of insulin. Some people carry pens. Others pack one or two pods with insulin so they can change pods if needed. |
|
I am not convinced that this is not caused by Loop since this happens to me all the time on the 3rd day. I would say once or twice a month. When I have used the standard DASH PDM I have never received the 0xcb error. This error is related to low battery power so I believe that Loop is draining down the POD battery more than the standard PDM. I have also noticed that the 0xcb happens more when I have auto bolus enabled. This makes sense since auto-bolus is not a standard feature of the DASH PDM. The DASH protocol was reversed engineered from my understanding for use with Loop. These are just my observations and my 2 cents. |
Do you have any suggestions to prevent it. I also have auto bolus ON. |
|
As Marion had mentioned, you should always have a backup when traveling away from home. There are many other reasons for POD failures that can occur from time to time even with the DASH PDM. Even the occasional 0xcb I would assume so I would always have a backup. The Omnipod DASH is by know means perfect but I do get annoyed at the number Oxcb errors that I see with Loop. |
|
https://loopkit.github.io/loopdocs/faqs/omnipod-faqs/#is-there-an-increase-in-pod-failures-on-loop I run autobolus and almost never get a screaming pod. I routinely get 80 hours of use with pods. |
|
I think there are a lot of factors that can contribute to the 0xcb battery fault failures including the number of boluses, communication retry attempts, malfunctioning Bluetooth chip, etc. FWIW I have gone to the Apple Store twice to have diagnostics run on my iPhone 12 to see if my Bluetooth was functioning normally and it passed both times. I live in Massachusetts and one of my neighbors works at Insulet (headquarters is 2 towns over) and he has told me that they have a rigorous testing or QA process due to the FDA approval process that they must go through. The code testing is very rigorous for their PDA software to detect things such as excessive battery drain on the POD. I'm not trying to conclude that this problem with Loop is being caused by excessive battery drain but am just pointing out that it is possibility since the rigorousness of Loop testing would not be the same as to what Insulet performs. |
|
Literally just got an 0xcb with 15 hours left on the POD. Issue report attached. |
That sucks , call insulet to tell them ur pod fell off to get a new one 😅 |
|
My neighbor from Insulet keeps telling me switch over to the Omnipod 5 but I keep pointing out that it hasn't been released for iPhone yet. 🫤 |
|
I suspect the difference in your (@rolandet) experience and mine is the heavier pod delivery levels compared to my usage and perhaps a batch of pods with less robust batteries. (Sorry I failed to mention the battery load in my first response.) I don't see anything obvious in your Loop Report. And your range setting of 105 to 115 mg/dL looks reasonable too. If you want to add a LoopReport @mahmoud1803, I will examine yours too. As an aside: When we were developing support for DASH pods, the community donated hundreds of pods, many that were expired. There were several boxes that would not wake up when pods were filled or failed very quickly with low-battery type of faults. The lot numbers for these boxes indicated the age of the pods, and they were interspersed with other lot numbers that had no issues with the battery (even much older lots). |
|
The current box of DASH pods expires in June 2024. I also am a little suspicious of the battery life of the pods as I was sent a batch that had already expired a couple of years ago. I do believe my bolus delivery usage is much higher than average. But, during the first year of DASH usage I was using the PDM and never had one Oxcb error. I had other failures such as Occlusions, etc but not a 0xcb error. |
|
We have never found any evidence that Loop is issuing any incorrect commands that can cause a 0xCB (203) fault (along with many other fault types) other than producing a higher pod/battery load which does increase the probability of a pod fault for a marginal pod (with weaker batteries &/or some mechanical issues requiring a bit more juice) particularly when Loop is issuing a higher # of commands due to poor communications &/or the particular therapy settings being using used. Using older pods &/or higher bolus delivery are definite factors that increase the likelihood of 0xCB pod faults. In this particular Loop Report, the 0xCB fault occurred in the middle of a modest sized 3.2U bolus after delivering over 161U over 56-1/2 hours which looks like a classic case excessive pod/battery load with a marginal pod. Having multiple 0xCB pod faults from the same lot is additional evidence of marginal pods. Insulet should be willing to replace any faulted pod [for anything other than an 0x31 (049) fault]. |
|
I’ve been following this thread for a while,
We’ve been looping for nearly 5 years now,
3 years on EROS
2 years on Dash,
In the 5 total years we’ve maybe seen this error a total of 3 times. Never on a dash POD. I know this is something people see, since this is not the first time it’s come up. I think the LOT factor and possibly device type/ habits may have something to do with it. By habits I mean distance of device to POD, model etc.
We have always run DEV, and I keep the app mostly up to date based on inbound PR/merges as Pete makes updates.
We've used only 2 devices original device was an iPhone XR 64 GB (4ish years)
6 months ago I gave her my old iPhone 12 Pro
Just adding context for everyone :)
Good luck!
Ben
…________________________________
From: Joe Moran ***@***.***>
Sent: Wednesday, May 22, 2024 12:15:31 AM
To: LoopKit/Loop ***@***.***>
Cc: Subscribed ***@***.***>
Subject: Re: [LoopKit/Loop] DASH POD ON LOOP ERROR oxcb: (Issue #2169)
We have never found any evidence that Loop is issuing any incorrect commands that can cause a 0xCB (203) fault (along with many other fault types) other than producing a higher pod/battery load which does increase the probability of a pod fault for a marginal pod (with weaker batteries &/or some mechanical issues requiring a bit more juice) particularly when Loop is issuing a higher # of commands due to poor communications &/or the particular therapy settings being using used. Using older pods &/or higher bolus delivery are definite factors that increase the likelihood of 0xCB pod faults.
In this particular Loop Report, the 0xCB fault occurred in the middle of a modest sized 3.2U bolus after delivering over 161U over 56-1/2 hours which looks like a classic case excessive pod/battery load with a marginal pod. Having multiple 0xCB pod faults from the same lot is additional evidence of marginal pods. Insulet should be willing to replace any faulted pod [for anything other than an 0x31 (049) fault].
—
Reply to this email directly, view it on GitHub<#2169 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ACWNLO2HRTRRKMB6REX4UNDZDRAZHAVCNFSM6AAAAABH5RG3XGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMRUGAZTSOJRGU>.
You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
|
Hi,
yesterday I got the following error Pod Fault Details
Fault Event Code Oxcb: Unknown Fault
Ref: 19-00868-11751-203 which my pod stopped working after that I had arround 6 hours left before expiration of the pod and I was out of home when it happened. It was my first time that it happened to me on the LOOP since it is been a week I am using the loop app. I just wanted to know if theres a way to avoid that error again in the future because it got me stress out since i was out from home and i was 45 min
away.To Reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Phone
Loop Version
CGM
Pump
The text was updated successfully, but these errors were encountered: