Hi! Recently I had a problem with a lot of my omnipods (7 boxes) fail giving the error 092.
Insulet is refusing to replace all of them, they say they cant replace that many pods- anything I can do?
If anyone has extra omnipods that I could use, would be very helpful to have them
Any advice on what may be causing the error? They are not priming (i dont even hear the ticking sounds you’re supposed to when the pod is priming). I dont think it’s me doing something wrong as I have been on the pod for quite some time now without issues- but if there’s something i can stay extra cautious of, would be good to know
Things I’ve tried basis internet:
Ensuring minimal air bubbles in insulin
not overfilling the pod with insulin
keeping the phone away from old pod
Breaking the previous pod’s circuit via the green hole generally used to silence screaming pods
Letting the pod sit a few minutes post filling insulin, before initiating priming
trying with both a controller and a different phone- same error
Different models of pod look almost identical. The pharmacy often confuses them. Check each box of pods for the model type. Check the pods inside the box.
Omnipod classic/euro pods have a tab that is clear in color.
Omnipod dash has a blue tab.
Omnipod 5 and dash are the same pod model? Or different?
Sounds like the pod isn’t communicating with the receiver at all.
What model of pump are you using?
“Decimal fault values less than 152 are common to both Eros and DASH pods while values more than 152 are BLE specific pod faults obtained from an examination of the DASH PDM firmware.”
QUESTION: Are you comfortable falling back on manual injection insulin? You will need to.
You need to report that to the FDA. Some people won’t be as familiar with the device or the failure and might get hurt. If someone has a kid on this pump and sends them off to school with repeatedly defective pods, it’s a problem.
You won’t see faults like this very often. You discovered something. You should 100% report it. They owe you replacement pods. Try to get the best documentation you can because they will call you a liar. You might take a phone video of the failure or some photos. Medical Device Reporting (MDR): How to Report Medical Device Problems | FDA
Best to include:
Model of pump
Lot number for the box of pods
Details about how it fails (just like you provided here)
Version of the software application that you are using on your phone (and the name of the application)
Model of phone you are using & the version of the operating system it is running
You might want to include photos of the error or a video of the device failing
We can’t look up error codes without knowing the model of the pump. But, this is not your fault and it is not something we will be able to fix. It’s failing to prime. You should not be using those pods.
mohe0001 is asking about which model so we can help. Please confirm that you are having a problem with the Omnipod 5 and not the Dash with Loop/Trio/APS/etc.
Since the pods are prescription items site rules mean members can’t share a pod. Call tech support back, another rep should be more helpful. Refer them to the logs showing the timestamped errors if they give you any more trouble. How are you doing at hitting the flea sized fill port with the syringe? Probably a dumb question, the pods sound defective from your description, just thinking of other possibilities.
Thanks! I haven’t used it so I’m not much help. I took a quick look at the recent code changes on github, there are obvious changes in 0.2.8 that could be related, what version(s) are you using?
When you get this sorted if you’re willing please post a topic about Trio. I think there’s lots of people who would like to read about it.
I had a similar error and I had the omnipod 5 pods but they were for g6 not the g7 and the error didn’t show up until it finished its 25 min pairing thing it does when you start a new pod with an existing sensor.
So I got the correct ones and I haven’t seen that error since. There is almost no difference in these pods , only the outside box says G7 on them.
Also I have seen the pod not be communicate during start up, with the phone a few times, but then if I just try again it usually works.
I also clear out my blue tooth every once in a while because I believe too many devices linked can overwhelm the memory in your phone.
Absolutely, I will do that soon, next weekend or something. I believe the pod issue is quite unrelated to trio given I tried using it with PDM also to no avail
Hey @Robot2135, just to be super clear, I was not suggesting you use a different version. I don’t use Trio, I know nothing about the risks, pros, cons, build safety, etc. I was asking you what version(s) you used so @mohe0001 would have more info to help you.
The Loopers weren’t 100% certain of what the source of error code 64 was, but they noticed it during Loop testing. It seems to be a pump problem that is throwing off Trio. Trio might not be programmed to fail nicely when it sees this unusual error code. I think its probably Trios fault. The problem originates in the pump, but then Trio doesn’t communicate with the pump in repsponse to the safety test in a way that allows the pump to continue functioning in 100% of cases. It just errors out.
Are the failures occurring on the third day in the life of the pod when it is said to run these safety checks?
Have you seen a failure using a traditional Dash controller? Do u still have that traditional controller laying around? Insulet might be attributing the failure to Trio. You might not see those errors if you use the dash controller.
@Robot2135 said that 80% of the pods fail to make any priming clicks (error code 092) and 20% fail between 15 and 24 hours with error code 064. I.e. none of them fail at 3 days (96 hours).
I use Dash pods, they are primed from AndroidAPS. I get a 90 day supply so the lots I get will pretty much for certain be different. The only issue I’ve noticed is that some pods (from, I think, a single lot) would prime fine but then fail to insert; I had to flick them with my finger to get the insert. This has been reported on-and-off before.
@Robot2135 this is certainly an issue for the Trio support groups. That’s because you might have built it wrong or accidentally deleted a line from the program. It’s easy to do.
If you want to report it to Insulet stop using Trio and use the Insulet PDM; an up-to-date one since they’ve recalled them a couple of times. It’s easy and if your remaining two boxes from the lots work with the PDM you know it’s a Trio bug. Unless you are absolutely sure you have fixed the Trio bug do not use Trio!
That’s a bit of a bug The G6 doesn’t require pairing on a new sensor because the pairing is to the transmitter and the transmitter doesn’t change, but at the least the PDM or app should have insisted you pair the transmitter before starting the sensor; it should know you have a G6 pod and haven’t yet paired a G6 transmitter.
Not related to this topic though; this is about Dash pods with a FOSS AIDS.
The G6 doesn’t require pairing on a new sensor because the pairing is to the transmitter and the transmitter doesn’t change, but at the least the PDM or app should have insisted you pair the transmitter before starting the sensor; it should know you have a G6 pod and haven’t yet paired a G6 transmitter.