Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fault by syncing the pump history medtrum nano patch MD0201 #3244

Closed
Waardevol opened this issue Feb 29, 2024 · 1 comment
Closed

Fault by syncing the pump history medtrum nano patch MD0201 #3244

Waardevol opened this issue Feb 29, 2024 · 1 comment

Comments

@Waardevol
Copy link

Aaps logfiles.zip

Received an error message in AAPS 3.2.0.2 when medtrum nano patch pump MD0201 was active for almost 20 hours.

Fault by syncing the history of the pump: one record has been skipped.
Check the treatment tab of the bolus is correctly synced. Delay the alarm and replace the patch or pump base when the error keeps coming back.

When I refreshed the pump from the pump tab the error still was reoccurring. However I was still able to perform bolus in AAPS and getting SMB's from AAPS. pump was functionally accordingly. I have used the patch with the error for the full day. Error was started around 04:00A.M. at 28th of February and I replaced the patch at the end of the day at 7:30 P.M.
Replaced the patch at the end of the day and the error disappeared.

@jbr7rr
Copy link

jbr7rr commented Feb 29, 2024

Issue is cause by wrong data in notification packet:

04:04:01.161 [Binder:30353_5] D/PUMPBTCOMM: [BLEComm$mGattCallback$1.onCharacteristicChanged():248]: onCharacteristicChanged data: [32, 34, 17, -128, 4, -2, 20, -1, -89, 5, 6, 0, 18, 64, 35, 0, -54] UUID: 669a9120-0008-968f-e311-6050405558b3
04:04:01.162 [Binder:30353_5] D/PUMPCOMM: [MedtrumService.onNotification():782]: <<<<< onNotification[32, 34, 17, -128, 4, -2, 20, -1, -89, 5, 6, 0, 18, 64, 35, 0, -54]
04:04:01.163 [Binder:30353_5] D/PUMPCOMM: [NotificationPacket.handleNotification():109]: Notification state: ACTIVE, current state: ACTIVE
04:04:01.164 [Binder:30353_5] D/PUMPCOMM: [NotificationPacket.handleMaskedMessage():134]: Message field mask: 4386
04:04:01.165 [Binder:30353_5] D/PUMPCOMM: [NotificationPacket.handleNormalBolus():184]: Normal bolus notification received
04:04:01.167 [Binder:30353_5] D/PUMPCOMM: [NotificationPacket.handleNormalBolus():189]: Bolus type: 0, bolusData: 128 bolus completed: true, bolus delivered: 3251.4
04:04:01.168 [Binder:30353_5] D/PUMP: [MedtrumPump.handleBolusStatusUpdate():396]: handleBolusStatusUpdate: bolusType: 0 bolusCompleted: true amountDelivered: 3251.4
04:04:01.169 [Binder:30353_5] D/PUMPCOMM: [NotificationPacket.handleReservoir():228]: Reservoir notification received
04:04:01.169 [DefaultDispatcher-worker-21] D/PUMP: [MedtrumOverviewViewModel$3$1.emit():130]: MedtrumViewModel bolusAmountDeliveredFlow: 3251.4
04:04:01.170 [Binder:30353_5] D/PUMPCOMM: [NotificationPacket.handleReservoir():230]: Reservoir: 3265.0
04:04:01.171 [Binder:30353_5] D/PUMPCOMM: [NotificationPacket.handleStorage():256]: Storage notification received
04:04:01.172 [Binder:30353_5] W/PUMPCOMM: [NotificationPacket.handleStorage():263]: handleMaskedMessage: We got wrong patch id!
04:04:01.174 [Binder:30353_5] D/PUMPCOMM: [NotificationPacket.handleStorage():270]: Last known sequence number: 1447, patch id: 6
04:04:01.176 [Binder:30353_5] D/PUMPCOMM: [NotificationPacket.handleUnusedCGM():317]: Unused CGM notification received, not handled!
04:04:01.177 [Binder:30353_5] D/PUMPCOMM: [NotificationPacket.handleUnusedCGM():318]: Unused CGM data: 867585703954

Will add additional checks to the Notification packet

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants