Mail Gethyn
I believe the ETB tests and reboots were on these dates:
1. 2nd Aug 2022 Reboot while PAS was powering up
2. 3rd Aug 2022 Reboot while PAS in BM
3. 14th Oct Reboot
4. 14th Oct another reboot at 21:08 PAS in BM
5. 18th Oct another reboot
6. 1st Dec Successful power up. Any reboots?
I think the only way to know if it is an uncontrolled reboot or a NCR reboot is in the Boot report.2022/08/02 - 2022/08/03
Data download
# Download TCs
$ pm EDDS batch_TC 2022-08-01T00 P5D
20220801_000000_20220805_000000.swa-batch-tc.xml
# Convert to various formats
$ pm batch_TC 20220801_000000_20220806_000000.swa-batch-tc.xml
20220801_000000_20220806_000000.swa-batch-tc.xml 260/1018 TC disabled
Writing : 20220801_000000_20220806_000000.swa-batch-tc.txt
Writing : 20220801_000000_20220806_000000.swa-batch-tc.hex
Writing : 20220801_000000_20220806_000000.swa-batch-tc.bin
# Download TM
$ pm EDDS batch_TM 2022-08-01T00 P5D
20220801_000000_20220806_000000.swa-batch-tm.binReprocessing
# Create L0 files and reprocess
$ pm make_L0 2018-10-11 20220801_000000_20220806_000000.swa-batch-tc.bin 20220801_000000_20220806_000000.swa-batch-tm.bin
$ pm make_L0 2018-10-12 20220801_000000_20220806_000000.swa-batch-tc.bin 20220801_000000_20220806_000000.swa-batch-tm.bin
$ REPROCESS 2018-10-11
$ REPROCESS 2018-10-12Timetags
ETB gives TM data timetagged from 2018-10-11 and 2018-10-12
A rough correlation can be obtained comparating TC timeline and TC acks
$ cat 20220801_000000_20220806_000000.swa-batch-tc.txt | grep STAY
2022-08-02T11:45:03.815110Z 2022-08-02T11:45:03.940045Z AIAF012B ZIA58734 SWA_TC_STAY_BOOT_MODE
$ SWA_TC 2018-10-11 | grep ZIA58734
2018-10-11T11:44:14.272 OK 2018-10-11T11:44:14.280 OK 2 TC(200,200) ZIA58734 SWA TC DPU stay in boot mode2022-08-02T11:45:03 == 2018-10-11T11:44:14
2018-10-11 correspond to 2022-08-02, we must add 49s to get approximative UTC
Reboots on 2022-08-02
link:/document/ETB/2022
First reboot at 12:36
APID ( 99, 7) TM ( 5, 1) SEQ (00000,3) Size = 2 2018-10-11T12:36:11.411 : SID 43796 : SWA_E_BOOT_EVENT
APID ( 99, 7) TM ( 5, 1) SEQ (00001,3) Size = 2 2018-10-11T12:37:31.498 : SID 43540 : SWA_E_END_OF_BOOT
APID ( 99, 7) TM ( 5, 1) SEQ (00015,3) Size = 6 2018-10-11T12:40:11.748 : SID 43559 : SWA_E_RECOVERY_TERMINATEDPAS was not yet in science mode. Error in commanding or NCR ?
Second reboot at 15:01
APID ( 99, 7) TM ( 5, 1) SEQ (00000,3) Size = 2 2018-10-11T15:01:26.287 : SID 43796 : SWA_E_BOOT_EVENT
APID ( 99, 7) TM ( 5, 1) SEQ (00001,3) Size = 2 2018-10-11T15:02:47.403 : SID 43540 : SWA_E_END_OF_BOOT
APID ( 99, 7) TM ( 5, 1) SEQ (00000,3) Size = 2 2018-10-11T15:03:42.345 : SID 43796 : SWA_E_BOOT_EVENT
APID ( 99, 7) TM ( 5, 1) SEQ (00001,3) Size = 2 2018-10-11T15:05:02.462 : SID 43540 : SWA_E_END_OF_BOOT
APID ( 99, 7) TM ( 5, 1) SEQ (00008,3) Size = 6 2018-10-11T15:06:58.748 : SID 43559 : SWA_E_RECOVERY_TERMINATED-
It seems there are 2 BOOT Events at 15:01 and 15:03 ?
PAS was in burst mode (each 15 minutes) and the reboot occurs during the first one
2018-10-11T14:59:11.627 OK 2018-10-11T14:59:13.999 OK 20 TC(200,160) ZIA58726 SWA TC enter all sensor in Burst Mode
-- -- 20 TC(200,160) ZIA58726 SWA TC enter all sensor in Burst Mode
-- -- 20 TC(200,160) ZIA58726 SWA TC enter all sensor in Burst ModeReboots on 2022-08-03
There was a new reboot at 10:03
APID ( 99, 7) TM ( 5, 1) SEQ (00000,3) Size = 2 2018-10-12T10:03:45.408 : SID 43796 : SWA_E_BOOT_EVENT
APID ( 99, 7) TM ( 5, 1) SEQ (00001,3) Size = 2 2018-10-12T10:05:06.582 : SID 43540 : SWA_E_END_OF_BOOT
APID ( 99, 7) TM ( 5, 1) SEQ (00000,3) Size = 2 2018-10-12T10:06:01.525 : SID 43796 : SWA_E_BOOT_EVENT
APID ( 99, 7) TM ( 5, 1) SEQ (00001,3) Size = 2 2018-10-12T10:07:21.642 : SID 43540 : SWA_E_END_OF_BOOT
APID ( 99, 7) TM ( 5, 1) SEQ (00009,3) Size = 6 2018-10-12T10:09:17.748 : SID 43559 : SWA_E_RECOVERY_TERMINATEDHere also, 2 BOOT events at 10:03 and 10:06
PAS was in normal mode during this test (no burst) but Powering off at the time of reboot.
2018-10-12T09:49:21.125 OK 2018-10-12T09:49:21.250 OK 4 TC(203,140) ZIA58862 SWA TC PAS write Pre-Amp power Control register
2018-10-12T09:49:22.125 OK 2018-10-12T10:03:38.750 OK 10 TC(203,135) ZIA58857 PAS HV Ramp DOWN
2018-10-12T10:03:38.876 OK -- 6 TC(203,141) ZIA58863 SWA TC PAS write Master Control register
-- -- 2 TC(203,137) ZIA58859 PAS Normal Power OFF2022-10-13 / 2022-10-17
Data download
$ pm EDDS batch_TC 2022-10-13T00 P6D
20221013_000000_20221019_000000.swa-batch-tc.xml
$ pm batch_TC 20221013_000000_20221019_000000.swa-batch-tc.xml
20221013_000000_20221019_000000.swa-batch-tc.xml 11/6547 TC disabled
Writing : 20221013_000000_20221019_000000.swa-batch-tc.txt
Writing : 20221013_000000_20221019_000000.swa-batch-tc.hex
Writing : 20221013_000000_20221019_000000.swa-batch-tc.bin
$ pm EDDS batch_TM 2022-10-03T00 P6D
20221013_000000_20221019_000000.swa-batch-tm.binReprocessing
$ pm make_L0 2018-10-10 20221013_000000_20221019_000000.swa-batch-tc.bin 20221013_000000_20221019_000000.swa-batch-tm.bin
$ pm make_L0 2018-10-11 20221013_000000_20221019_000000.swa-batch-tc.bin 20221013_000000_20221019_000000.swa-batch-tm.bin
$ pm make_L0 2018-10-12 20221013_000000_20221019_000000.swa-batch-tc.bin 20221013_000000_20221019_000000.swa-batch-tm.bin
$ pm make_L0 2018-10-13 20221013_000000_20221019_000000.swa-batch-tc.bin 20221013_000000_20221019_000000.swa-batch-tm.bin
$ pm make_L0 2018-10-14 20221013_000000_20221019_000000.swa-batch-tc.bin 20221013_000000_20221019_000000.swa-batch-tm.bin
$ pm make_L0 2018-10-15 20221013_000000_20221019_000000.swa-batch-tc.bin 20221013_000000_20221019_000000.swa-batch-tm.bin
$ REPROCESS 2018-10-10
$ REPROCESS 2018-10-11
$ REPROCESS 2018-10-12
$ REPROCESS 2018-10-13
$ REPROCESS 2018-10-14
$ REPROCESS 2018-10-15Timetags
ETB gives TM data timetagged from 2018-10-10 to 2018-10-15
A rough correlation can be otained comparing TC timeline and TC acks
$ cat 20221013_000000_20221019_000000.swa-batch-tc.txt | grep ZIA58734
2022-10-13T11:05:51.351296Z 2022-10-13T11:05:51.476039Z AIAF012A ZIA58734 SWA_TC_STAY_BOOT_MODE
$ SWA_TC 2018-10-10 | grep ZIA58734
2018-10-10T10:47:31.043 OK 2018-10-10T10:47:31.051 OK 2 TC(200,200) ZIA58734 SWA TC DPU stay in boot mode2022-10-13T11:05:51.476039Z == 2018-10-10T10:47:31.051
To get approximative UTC timestamps, add 3 days and 18 minutes
DPU Reboots
First reboot 2018-10-11 05:53
APID ( 99, 7) TM ( 5, 1) SEQ (00000,3) Size = 2 2018-10-11T05:53:09.900 : SID 43796 : SWA_E_BOOT_EVENT
APID ( 99, 7) TM ( 5, 1) SEQ (00001,3) Size = 2 2018-10-11T05:54:31.082 : SID 43540 : SWA_E_END_OF_BOOT
APID ( 99, 7) TM ( 5, 1) SEQ (00017,3) Size = 6 2018-10-11T05:57:14.748 : SID 43559 : SWA_E_RECOVERY_TERMINATEDSecond reboot 2018-10-11
APID ( 99, 7) TM ( 5, 1) SEQ (00000,3) Size = 2 2018-10-11T21:06:20.465 : SID 43796 : SWA_E_BOOT_EVENT
APID ( 99, 7) TM ( 5, 1) SEQ (00001,3) Size = 2 2018-10-11T21:07:41.091 : SID 43540 : SWA_E_END_OF_BOOT
APID ( 99, 7) TM ( 5, 1) SEQ (00019,3) Size = 6 2018-10-11T21:10:24.748 : SID 43559 : SWA_E_RECOVERY_TERMINATED
Third reboot 2018-10-14 17:29:59
APID ( 99, 7) TM ( 5, 1) SEQ (00000,3) Size = 2 2018-10-14T17:29:59.574 : SID 43796 : SWA_E_BOOT_EVENT
APID ( 99, 7) TM ( 5, 1) SEQ (00001,3) Size = 2 2018-10-14T17:31:20.629 : SID 43540 : SWA_E_END_OF_BOOT
APID ( 99, 7) TM ( 5, 1) SEQ (00015,3) Size = 6 2018-10-14T17:34:00.748 : SID 43559 : SWA_E_RECOVERY_TERMINATEDIn these 3 reboots, PAS was in Burst mode (each 15 minutes)
2022/11/28 - 2022/11/30
Download data
Reprocessing