----------------------------------------------------------------- SSOC Tohban's Report for Week 40 (29 Sep 1997 - 5 Oct 1997) ----------------------------------------------------------------- SSOC : M.Sawa & S.Kubo KSC : Y.Iizuka & Y.Saito 0. Meeting attendance (in alphabetical order): Te.Watanabe, A.Sterling, D.McKenzie, J.Lemen, G.Slater, H.Hara, H.Nakajima, T.Magara, M.Sawa, S.Kubo 1. Solar Activity: Solar activity continued to be moderate. The GOES X-ray level was at under-C. Most of the activity was due to AR8088. 3 C-class events were observed. One (C2.6) was observed on AR8088 on 29 Sep 97 (UT). Others(C1.0) were observed on 28 Sep 97 and on 2 Oct 97, respectively. 2. Standard Operation: 2.1 SXT Table Uploads: The following SXT tables were uploaded last week. ------------------------------------------------------------ Pass ID Pass # Table ID ------------------------------------------------------------ Monday 970929-0411 4 970929 P4 ARS1 STD Tuesday 970930-0412 4 970930 P4 ARS1 HRTS Thursday 971002-0310 4 971002 P4 ARS1 DKCAL Friday 971003-0310 4 971003 P4 ARS1 DIFF Saturday 971004-0207 4 971004 P4 ARS1 STD+DKEXP ------------------------------------------------------------ 2.2 STT timer setting: We set the STT timer during pass 2 on 30 Sep, Tuesday (970930-0205). The next STT timer setting is due on 7 Oct, Tuesday. 2.3 Off-pointing for Terminators : None 2.4 HXT, BCS, and WBS calibrations : None 3. Errors and Problems 3.1 SXT Errors and Problems: 3.1.1 SXT Errors One SXT error, 'SXT bit map error', occured at the first pass on 29 Sep (970929-0101). The error was recovered during the same pass. 3.1.2 SXT Table Cancellation The table that was planned to be sent at the fourth pass on 1 Oct was cancelled because of the trouble of KSC's antenna. Same table was sent at the forth pass on next day (2 Oct). 3.2 BCS Errors and Problems: None 3.3 KSC's antenna trouble Because of KSC's antenna trouble on 29-Sep (Wed) (JST), we couldn't send OP and commands to Yohkoh. During mornig on 1-oct and afternoon on 2-oct(PassID : 970930-1547 - 971002-0310), almost data were lost. * cf.op.cit., Appendix 3.4 KSC S3500 Computer Problem The mainframe S3500 at KSC did not work well on Thursday (JST). This was due to a system abort which may have been caused by a sudden voltage drop which in turn caused system trouble. The problem was recovered on Friday evening (JST). * cf.op.cit., Appendix 4. DSN Communications: 4.1 DSN Final Schedule for W40: 7 passes were canceled, because of a trouble of KSC's antenna. 4.2 DSN Preliminary Schedule for W41: 1 pass was canceled by DSN. 4.3 DSN Final Schedule for W41: 2 passes were canceled by DSN. 1 pass was canceled, because of maximum elevation is too low. 4.4 DSN Preliminary Schedule for W42: 1 pass was canceled by DSN. 61 passes were canceled, because these weren't canceled by Strawman cancelation for W42. 4.5 DSN Strawman Schedule for W43: The Strawman schedule didn't arrive as of Friday Oct 3. The meeting for ASCA pass conflicts resolution has been deferred to Monday Oct 6. 4.6 Data Transmission from DSN: (/home/flare1/yohkoh/dsn_corrupt/97_40) 245 76 0431 corrupted tape Requested 05 Sep. corrupted tape Requested 09 Sep. no response tape Requested 12 Sep. no response tape Requested 17 Sep. no response Requested 19 Sep. no response Requested 24 Sep. Closed / same data 246 80 0450 corrupted tape Requested 05 Sep. corrupted tape Requested 09 Sep. no response tape Requested 12 Sep. no response tape Requested 17 Sep. no response Requested 19 Sep. no response Requested 24 Sep. Closed / correct data 246 76 0632 corrupted tape Requested 05 Sep. corrupted tape Requested 09 Sep. no response tape Requested 12 Sep. no response tape Requseted 17 Sep. no response Requested 19 Sep. no response Requested 24 Sep. Closed / correct data 255 76 0046 not received Requested 19 Sep. no response Requested 26 Sep. Closed / correct data 256 76 0104 corrupted tape Requested 19 Sep. no response tape Requseted 26 Sep. Closed/ same data 259 76 2252 corrupted tape Requested 19 Sep. no response tape Requested 26 Sep. Closed/ same data 263 16 0447 corrupted tape Requested 26 Sep. 265 76 0025 not received Requested 26 Sep. Closed / correct data 267 76 2338 corrupted tape Requested 26 Sep. Closed / correct data 4.7 DSN scheduling interface tasks change Starting past week, September 21, 1997, the scheduling interface tasks for Yohkoh and ASCA has been shifted from DSN to the Wallops Flight Facility (WFF). The E-mail mailing list has been updated. 5. KSC Pass Conflicts and Schedule 5.1 YOHKOH/ASCA/AKEBONO/HALCA Pass Conflicts at KSC: Week 40 : 1 pass were canceled due to conflict with HALCA. Week 41 : 1 pass will be canceled due to conflict with AKEBONO. 5.2 Future Schedule: None 6. Special Operations: There were 1 campain operation by sokar roket flight on 30 Sep. The launch time was 20:05 (UT). 8. Hikitsugi Items: 8.1 Tohbans for W41 SSOC : H.Nakajima & T.Magara KSC : Y.Saito & M.Ohyama 8.2 OP and Command Sheet Status The command sheets and the OP for Monday (6-Oct-97) have been created. And the OP has already been transferred. 8.3 STT timer setting STT timer setting is due on 7 Oct, Tuesday. 8.4 Holiday Schedule: The next holiday will be 12 Oct, Sunday. 8.5 OPOGNEW instead of OPOGEDT ----From W37 report ---------------------------- We continued to use the revised version of OPOGEDT, OPOGNEW. OPOGNEW is the same as OPOGEDT except that the printing out of the OP is simpler. The SSOC tohbans should press the PF4 key (`print') on the mainframe and then print out the OP by typing: IDL> print_op CAUTION : The account, `s80670', for FTP transfering OP from main frame is used. This account's password must be changed every month, same as s88239's one. ***** NOTE ******* Similarly, in order to print out the OG, type: IDL> print_ogall IDL> print_ogsel ***** These softwares are not available. See A/I ****** It is also possible to use the mainframe emulator on flare20 instead of the mainframe terminal for some situations: flare20% telnet mainf1 17 s88239 ex op(opognew) PF3 is {Esc}3 PF4 is {Esc}4 etc. --------------------------------------------------------------------------- 8.6 STT_PLOT ----From W37 report ---------------------------- It is possible to check the STT Tracking by using the routine `STT_PLOT': First make sure you are on the HOME directory of the yohkoh account then type: IDL> stt_plot (,'DD-MM-YY') This will plot a time variation of the STT output signal level. If the STT is working properly, the signal level should stay in between 400--800, and should vary only in the time period set by the timer. See sample plots in the tohban's manual. --------------------------------------------------------------------------- 8.7 Sirius Data Nothing to report. 8.8 Suggestion to DSN selection rule: mail from JPL ----Quoted from the previous week's report --------------------------------- I understand that you access RASM and choose the passes that are made available to you. We would like you to use the Wallops (WFF) passes as much as possible. In other words, if a pass from one of the DSN sites (Goldstone, Madrid or Canberra) can be substituted by a WFF pass, please use the WFF pass and delete the DSN pass, instead of vice versa. Please understand we are not asking you to give up any coverage but if the same coverage can be accomplished by using WFF instead of the DSN, we would like you to do so. (Albert Chang) --------------------------------------------------------------------------- 9. Action Items 9.1 Further software development It would be greatly appreciated if the SSOC tohbans could recommend any software development that they think will save future tohbans time and which improves the reliability of their work. 9.2 Week-35-A/I-1 SSOC tohbans The SSOC tohbans should inspect the horizon maps sent by JPL and think about whether it would be possible to determine whether the acceptable minumum altitude (Is 10 degrees really the best estimate or is less accepatble?). Please refer to Hudson-san for further information. 9.3 Week-37-A/I-1 /Hudson/status open The following IDL softwares do not work well. Hudson-san will fix them. IDL> print_ogall IDL> print_ogsel end of report ------------------------------------------------------------------------------- -----< Appendix >-------------------------------------------------------------- Trouble Report 1-Device instrument of 20m ANT(transmitter) trouble When Occur Trouble of transmitter with 20m ANT occurred just before Pass5(30-Sep-97). To reset transmitter, Pass5 finished no problem. But after Pass5, We couldn't do uplink. Then, 1-Oct-97, We did only monitoring. What trouble A device of dry Air filling up(Dehydrator) showed alarm sign. Dehydrator stopped to send hight pressure air at transmitter. Then, transmitter had stopped. What cause Repairmans came from Dehydrator manufacturer and try to find the cause. But detail was unknown. Repairmans guess the cause as follows. (a) Dehydrator's fan had been something worng. (b) Trouble of magnetic pressure adjust valve. Solution To solve this problem, Repairmans changed the current pressure motor and magnetic pressure adjust valve to new one. Now, transmitter with 20m ANT is restoration. 2-S3550 trouble Many problem happened about S3500 from 01-Oct-97 to 02-Oct-97. All problem is complicated each other. So we write these problem at time and Pass No.. After Pass1(01-Oct-97) We tried printout of hard copy about QL status, but failed. Becase printer papers ran out. So we set new papers. But printer couldn't work after that. After finished work at that day, we canselled printout job. And we restart S3500. After that, printer became to work. After all Pass(01-Oct-97) We tried printout AOSLOS. The beep sound started after some time by off and on. The beep didn't stop after one hour. We tried to cansell AOSLOS job, but failed. We had no choice to stop S3500. Before Pass1(02-Oct-97) The beep sound stoped. But, we couldn't start QL system. Error code was "OPEN ERROR / COD = 13". We restarted S3500. QL system was started on SA1, but another CRT had halted. To reset desplay control device, another CRT started. After Pass5(02-Oct-97) Error occured S3500 when we started GPIB of Pass5. Error code was "WRITE ERROR / CODE = 6". We gave up GPIB. Sysytem log message showed "** POWER WARNING(01) **" . FACOM said this message was real time error. 03-Oct-97 All S3500 system turned back normal. FACOM said system and hard was no problem, probably this time trouble was unstable with voltage of a power souce. Now, S3500 is no problem. KSC TOHBAN Y.Iizuka & Y.saitou end