-
Notifications
You must be signed in to change notification settings - Fork 46
Evaluating 6a Failure with long status response error
Eelke Jager edited this page Dec 2, 2018
·
19 revisions
Both Pods failed in the second basal entry after a status response ran for 5 minutes.
GMT+0000 GMT-0600 Event
20:30:00 Basal entry (0.60U for 3,5 hours)
03:31:52 21:31:52 Start Pod
05:44:05 23:44:05 Status response (sending for 5 minutes)
05:49:47 23:49:47 ACK status response
00:00:00 1st Basal entry after ACK (0.45U for 2 hours)
02:00:00 2nd Basal entry after ACK (0.30U for 2.5 hours)
10:10:15 04:10:15 Pod failure $6a (last 1/2 hour)
04:30:00 Basal entry (0.45U for 2.5 hours)
GMT+0000 GMT-0800 Event
05:00:00 Basal entry 0.85U for 7,5 hours
22:09:52 14:09:52 Start Pod
15:00:00 Basal entry 0.70U for 1 hour
00:36:03 16:36:03 Start response (sending for 5 minutes)
00:41:07 16:41:07 Stop response with ACK
18:00:00 1st Basal entry after ACK (0.90U for 2 hours)
20:00:00 2nd Basal entry after ACK (1.10U for 4 hours)
04:36:04 20:36:04 Pod failure $6a (end of first 1/2 hour)
00:00:00 Basal entry (0.80U for 2,5 hours)
hour U/h
00:00 0.80
03:00 0.90
05:00 0.85
07:30 0.85
12:30 0.85
15:00 0.70
18:00 0.90
20:00 1.10
hour U/h
00:00 0.45
02:00 0.3
04:30 0.45
07:00 0.6
10:00 0.4
12:00 0.4
15:00 0.4
20:30 0.6
0.45 0.3 0.45 0.6 0.4 0.4 0.6
1a LL NNNNNNNN 00 CCCC HH SSSS PPPP napp napp napp napp napp napp napp
1a 1a 318a1e4a 00 0190 1f 0098 0000 3804 4003 4804 5006 f004 4004 6006