SSOC Tohban Report for Week 24_95 (12 June - 18 June 1995) SSOC: Kano, R., Suematsu, Y. KSC : Ohyama, M., Ichimoto, K. 1. Solar Activity ----------------------------------------------------- Solar activity was very low. The largest flare was B3.3 and only three flares above Class B2 ocurred. 2. Standard Operations ------------------------------------------------ 2.1 SXT Table Uploads : 12 tables --------------------------------------------------------------------- KSC Time (start:JST=UT+9) Pass# Table ID --------------------------------------------------------------------- 12-JUN-95 01:12 1 950611 P1 ARS0 XBP CAMP 12-JUN-95 08:04 5 950611 P5 ARS2 CHROMO CAMP 13-JUN-95 01:30 1 950612 P1 ARS0 XBP CAMP 13-JUN-95 08:24 5 950612 P5 ARS2 CHROMO CAMP 14-JUN-95 01:49 2 950613 P2 ARS0 XBP CAMP 14-JUN-95 07:00 5 950613 P5 ARS2 CHROMO CAMP 15-JUN-95 00:26 1 950614 P1 ARS0 XBP CAMP 15-JUN-95 05:36 4 950614 P4 ARS2 CHROMO CAMP 16-JUN-95 05:55 5 950615 P5 ARS2 CHROMO CAMP 17-JUN-95 02:48 3 950616 P3 ARS0 XBP CAMP 17-JUN-95 06:15 5 950616 P5 ARS1 DKCAL+FILA 18-JUN-95 01:24 3 950617 P3 ARS1 STD+LONG --------------------------------------------------------------------- Every time a block command "BC 8C 05" was also uploaded . This is for dumping SXT patrol images. 2.2 STT Timer Setting The STT Timer was set on June 12 (in UT; 950612-1340). The next setting is due on 19-June (in UT). 3. Errors & Problems ------------------------------------------------- 3.1 SXT Warm Reset Error SXT warm reset error was found in pass #1 on June 15 (in UT; 950615-0929) and the commands Yobi-A and B were executed. The error was recovered in the pass #3. 3.2 X-band off on QL The PB data was not received with S3500 in pass 4 on June 12 (in UT; 950612-1444), and it was found that PB-X-OFF appeared on the QL. The reason of this trouble is not known yet. The reformat data had no problem, because A400 received it correctly. 3.3 KSC AOSLOS OUTPUT Problem KSC could not print out some of the AOSLOS's for Wallops. This problem was temporally fixed by Sakao-san. 3.3 Lost Data See 4.6 & 4.7 Other communication. 3.4 BDR repro problem on June 2: How to respond See Hikitsugi item 8.6. 4. DSN Communications ------------------------------------------------------ 4.1 DSN Strawman Schedule for W27 We cancelled 54 DSN contacts from the strawman schedule for W27. 4.2 DSN Forecast Schedule for W26 We cancelled 34 DSN contacts from the forecast schedule for W26. 4.3 DSN Final Schedule for W25 We cancelled 2 DSN contacts from the final schedule for W25. 4.4 DSN Final Schedule for W24 We cancelled 5 DSN contacts from the final schedule for W24. 4.5 Pass additions None. 4.6 Re-transmission requests We sent re-transmission requests repeatedly for the data, (1) DSS 66, 158/05:32-05:42; (2) DSS 66, 160/04:28-04:38. It turned out, however, that the data DSS 66 158/05:32-05:42 was unrecoverable, and the data DSS 66, 160/04:28-04:38 was broken. Conseqently these two data sets were lost. 4.7 Other communications We sent a transmission request for the delayed data DSS 66, 161/03:04-03:14, and received it soon. The pass DSS-76, 166/06:06-06:18 was canceled in real-time, because of GOES-9 support. However, REPRO was carried out at this pass because of delayed communication, and the data was lost. 5. YOHKOH/ASCA/SFU Pass Conflicts at KSC ---------------------------------- In week 25, there exist 13 conflicts with ASCA and SFU. 6 of them will be lost. 6. Special operation 6.1 Offset Pointing (Terminator Images) 12-Jun-95 04:48 Normal 13-Jun-95 11:36 OG87 14-Jun-95 11:55 OG85 15-Jun-95 04:08 OG85 15-Jun-95 10:37 OG86 15-Jun-95 12:14 OG87 16-Jun-95 02:50 OG86 16-Jun-95 10:57 OG87 17-Jun-95 03:10 OG85 17-Jun-95 06:24 OG86 17-Jun-95 11:16 OG87 6.2 BCS Calibrations BCS STIM CAL was done in pass #4 on June 12 (in UT, 950612-1444). BCS SRC CAL was done 19:39-19:50 UT on June 12 by OP. 7. Holiday Schedule The next holiday will be Sunday, 25 June. ************************************************************************** 8. Hikitsugi Items -------------------------------------------------- 8.1 Tohbans for Week 25 KSC : K.Ichimoto and S.Sano SSOC : H.Nakajima and T.R.Metcalf 8.2 ASCA/SFU pass conflicts (KSC) Toward the regular use of Santiago Station, we negotiate KSC schedules up to 3 weeks ahead. The weekly meeting with ASCA/SFU is held by Nagase-san (ex.2611) on Thursday from 13:30 on A-6F. In this meeting, please fix final KSC schedule on week 26 and negotiate about KSC pass conflicts with ASCA/SFU on week 28. 8.3 DSS-74(Santiago) passes As the data transmitted from Santiago station was correct, operations for Santiago station are done in the same mode as other DSN stations since week 24. Note that Yohkoh and ASCA share 2 Santiago contacts in a day, because of the limitation of the operation time in Santiago. 8.4 DSS-74(Santiago) Transmitted Data Although the data seem to be OK now, SSOC tohban should be still careful and inform detail reason to DSN when problems happen. 8.5 STT timer setting The next STT timer set is due early mornig on Tuesday, June 20 in JST. 8.6 BDR repro problem An abnormal behavior of X-band repro was reported on June 2 in weak 22 as follows: There happened an anomalous thing with BDR or BDR-Monitor, on pass 3 during Friday operation. (1) The BDR-monitoring oscilloscope kept showing the BDR "PAUSE" state 20 sec after a time lapse enough for finishing "REP", while the QL-screen indicated BDR went to STBY mode. (2) The action the KSC took was to send "REP" command, with a suspicion that BDR had stopped just before the end of recorded data. As a result, Yohkoh left the KSC contact with BDR in REP state. (3) BDR turned into "REC" state soon, thanks to the "CYEND REC" command in the KSC LOS OG. On the next contact, pass 5, KSC found the BDR was in REC state as usual. (This interpretation may not be correct. Later checks of the playback data can help us to see what actually happened.) (4) KSC could not find anything wrong with the BDR Monitor by later checks. NEC investigated this problem and concluded that some unidentified trouble took place at the relay switch of X-band in TCU (Watanabe memo). Decision how to respond when this problem happens: We do nothing special, just executing BDR REC at the end of operation as usual. The memorandum of this decision is posted on the whiteboard in B-tou operation room. 8.7 Terminators. The terminator-offpointing program will be continued this week. The SSOC tohbans will be required to manually insert the off-point OGs for the terminators into the OP tables following to suggestion by SXT_CO. After OP_FIRST_GUESS, SSOC tohbans should send drafts of OP to SXT_CO at D-tou. SXT_CO will send a request about terminators and associated offpoints if necessary. We are using the following offpoint OG's and are going through them in sequence cyclically. That is, change each time to the next number please: OG 33 S/C W19 S01 (all OG numbers are decimal) OG 34 S/C W17 N00 OG 35 S/C W10 S01 OG 36 S/C W04 N00 OG 85 S/C W02 N17 OG 86 S/C W19 N01 OG 87 S/C W16 N00 On June 15, Hudson san edited OG#33 from W19 S01 to W03 N00. Before using this new OG#33, we have to execute OG WRITE.