-
Notifications
You must be signed in to change notification settings - Fork 46
Evaluating 6a Failure with long status response error
Joe Moran edited this page Apr 17, 2019
·
19 revisions
All 4 Pods failed in the second basal entry after a first successful status response after returning an ACK instead of response.
2 hours next segment + 10 minutes into the second segment.
GMT+0000 GMT-0600 Event
20:30:00 0.60U for 3.5 hours
03:31:52 21:31:52 Start Pod
05:44:05 23:44:05 Last successful Status response
05:49:47 23:49:47 response with ACK (10 minutes remaining to next segment)
00:00:00 0.45U for 2 hours
02:00:00 0.30U for 2.5 hours
10:10:15 04:10:15 Pod failure $6a (10 minutes into last 1/2 hour)
04:30:00 Basal entry (0.45U for 2.5 hours)
+36 minutes into alternating second segment
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 Last successful status response (+ 6 minutes in 1/2 hour)
00:41:07 16:41:07 response with ACK
18:00:00 0.90U for 2 hours
20:00:00 1.10U for 4 hours
04:36:04 20:36:04 Pod failure $6a (+6 minutes in alternating napp (= + 30 minutes))
00:00:00 Basal entry (0.80U for 2,5 hours)
2 hours of previous segment into second segment.
GMT+0000 GMT-0800 Event
18:48:21 10:48:21 Pod started
20:00 1.1 U/h for 4 hours
06:46:18 22:46:18 Message Log start
00:00 0.8 U/h for 3 hours
10:26:02 02:26:02 one status request command with no response
10:26:03 02:26:03 send status request command with B9 == 04 (ACK instead of response)
03:00 0.9 U/h for 2 hours
05:00 0.85 U/h for 8 hours alternating
13:58:04 05:58:04 start of 7 request commands with no response
14:04:09 06:04:09 send status request command with B9 == 04 (ACK instead of response)
16:48:59 08:48:59 start of 4 request commands with no response
16:51:53 08:51:53 send status request command with B9 == 04 (ACK instead of response)
18:52:38 10:52:38 receive Pod failure $69 response
13:00:00 0.85 U/h for 2 hours alternating
16 minutes into last 1/2 hour (+3 hours does not fit in 2 hour segment) issue report (Running with new continuous counting sequence and message B9.)
GMT+0000 GMT-0800 Event
20:00:00 1.10 U/h for 4 hours
06:09:28 22:09:28 Start Pod
07:08:48 23:08:48 1f0d26bd1c0a1d28003220000000efff01eb
07:12:51 23:12:51 1f0d26bd
07:13:52 23:13:52 1f0d26bd240a1d280034a000000103ff8060
07:52:22 23:52:22 1f0d26bd
07:53:22 23:53:22 1f0d26bd2c0a1d28003f30000001a3ff0080
00:00:00 0.80 U/h for 3 hours
03:00:00 0.90 U/h for 2 hours
12:46:30 04:46:30 $6a Fault (16 minutes into last 1/2 hour)
05:00:00 0.85 U/h
Fault seems to have same time around 10:30 as the 68 fault issue report
GMT+0000 GMT-0800 Event
19:05:22 11:05:22 Pod started
00:00:00 0.80 U/h
09:48:02 01:48:02 ACK instead of CON
03:00:00 0.90 U/h
05:00:00 0.85 U/h
18:12:46 10:12:46 Fault (-48 minutes till end of 24 day)
19:05:22 11:05:22 24 hour active
13:00:00 0.85 U/h
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
8h 2.5h
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
0.80 0.90 0.85 0.85 0.70 0.90 1.10
8h 2h
1a LL NNNNNNNN 00 CCCC HH SSSS PPPP napp napp napp napp napp napp napp
1a 1a 851072aa 00 0242 2a 1e50 0006 5008 3009 f808 3808 5007 3009 700b
1a LL NNNNNNNN 00 CCCC HH SSSS PPPP napp napp napp napp napp napp napp 13 LL BO MM NNNN XXXXXXXX YYYY ZZZZZZZZ YYYY ZZZZZZZZ YYYY ZZZZZZZZ YYYY ZZZZZZZZ YYYY ZZZZZZZZ
PDM 1a 1a eee08af4 00 038a 2e 1c88 0007 680e 400d 0010 100e 000f f80e f80e 13 26 40 04 00db 0067a788 03f7 00bd6b61 028a 00d34689 00a0 00aba950 0087 00cb7355 1342 00bd6b61 81ab
Loop 1a 1a e4d963c1 00 03d2 2d 30b8 000c 680e 400d 0010 100e 000f f80e f80e 13 26 00 04 01a0 006f0556 03f7 00bd6b61 028a 00d34689 00a0 00aba950 0087 00cb7355 1342 00bd6b61 001c