search

nightscout / AndroidAPS

Opensource automated insulin delivery system (closed loop)
https://wiki.aaps.app
GNU Affero General Public License v3.0
724 stars 1.76k forks source link

Medtrum: Priming screen returns to Change Patch screen #3365

Open dar-kod opened 5 months ago

dar-kod commented 5 months ago

I had a similar problem with several patches. This time (before 16:23 today), when I clicked to start priming, the screen immediately returned to the start screen if nothing had been started, but I could hear clicks. I could see a very short failure message, but it did not appear on the overview screen. When I tried to detect "activation in progress", the process of reading the activation status never finished. I found this very annoying. I had to discard the patch.

The first time I discarded the patch I could hear clicks, but not like before, there was a pause after every 4, 5 or 6 clicks. It finished priming and I had to activate the patch (apply the needle). I simply removed a sticker where the needle is, but then it happened again in a similar way to the first priming.

The second time I discarded the patch I managed to activate it. There was still a problem with the priming. The third priming time I wanted to be sure that the base was well connected, and it was not, as the priming did not work. The needle seems to play an important role here. I pressed the needle to get it out of the patch and a lot of insulin came out, but the priming was successful. I then applied the patch. I follow the strict instructions and wonder why there was a problem with priming the first time. I suspect I let too much air out of the patch and it couldn't start the priming process. The log file is attached.

AndroidAPS._2024-06-1300-00-00.285.zip

jbr7rr commented 5 months ago

Logs are not complete, there are no logs related to any priming or activation, do you still happen to have the complete logs ?

dar-kod commented 5 months ago

No. For the next time, is the AndroidARS.log file that contains this information?

jbr7rr commented 4 months ago

No. For the next time, is the AndroidARS.log file that contains this information?

Everything in the log folder, best to zip the whole folder, or use the export log function in aaps itself and mail it to yourself and share that zip

dar-kod commented 4 months ago

It happened again, very similar. What is new, and what I didn't report before but have seen, is that after the priming screen returned to the attached screen (which comes after the first Change Patch screen), the message "Pump time updated" came up at the same time. Please see a screenshot of this. I didn't apply the patch immediately, but waited perhaps 3–5 minutes to prepare to apply it. It seems that the driver forgets the patch because of the waiting.

1719234780257

I still managed to activate the patch after pressing discard and repeating the process.

The full zipped log files are attached.

files.zip

dar-kod commented 3 months ago

Sorry. My zip file from last time was empty.

I had a similar problem again. This time I had the patch on the body when the screen that comes after the Priming screen went back to the Change Patch screen. This happened at about 8:05 in the morning. Again, the process of reading the activation status never finished. I tried to see if Exit would help, but it didn't. I tried detach the pump base 2 times. If I remember correctly, the first time the pump state showed PATCH_FAULT2 (8:16) after unsuccessful priming, the priming was not completed after reaching 100% (8:12). I understood that there was some misunderstanding between the driver and the patch, but I didn't want to lose the patch. When I tried to read the activation status, the only option was to deactivate the patch. So I understood that I had to insert the needle to try the last option. I did so and exited AAPS. The patch was ready to be activated again with the previously removed pump base (I don't remember exactly when I did this), but with a needle in the body. I simply added 2 units without bolusing.

files.zip

I1985 commented 2 months ago

I've had something similar at least twice. But only when I took quite long to apply it. I figured there might be some kind of timeout in the script that caused it to fail. Since I make sure I have everything ready before I start. Including filling the syringe and wiping the infusion spot. Only then I'll start the process in AAPS and attach the pumpbase to the new patch.

Since doing it this way I haven't had any issues. So I suspect it might be a timeout in the script?