-
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 Nov 30, 2018
·
19 revisions
GMT+0000 GMT-0600 Event
02:30:00 20:30:00 Basal entry 0.60U
03:31:52 21:31:52 Start Pod
05:44:05 23:44:05 Start long status response for 5 minutes
05:49:47 23:49:47 Stop status response with ACK
06:00:00 00:00:00 Basal entry 0.45U
06:14:05 00:14:05 Supposed error after 30 minutes but not occurring because of start new schedule (00:14:05)
08:00:00 02:00:00 Basal entry 0.30U
10:10:15 04:10:15 Pod failure $6a (4 hours and 26 minutes after long status response)
10:30:00 04:30:00 Basal entry 0.45U
Failure after 4 hours (half a segment of 8 hours) and 34 minutes since start long status reponse)
last command below sends ACK
* 2018-11-26 05:44:02 +0000 send 1f07adaf10201a0efc7e6f48010095013840000e000e160e0000008c00c42f36008c00c42f368292
* 2018-11-26 05:44:05 +0000 receive 1f07adaf140a1d280048a00000021fff0272
* 2018-11-26 05:48:45 +0000 send 1f07adaf00030e0100038f
* 2018-11-26 05:49:46 +0000 send 1f07adaf00030e0100038f
* 2018-11-26 05:49:47 +0000 send 1f07adaf04030e01008284
Fault time
* 2018-11-26 10:10:08 +0000 send 1f07adaf00030e0100038f
* 2018-11-26 10:10:10 +0000 receive 1f07adaf04180216020d0000000400be6a018c03ff01910000289f08016e819c
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