----------------------------------------------------------------------------- Mauna Loa Solar Observatory Observer's Log ----------------------------------------------------------------------------- Wed Jan 27 17:55:50 GMT 1999 Year: 99 Doy: 027 Observer: koon Wed Jan 27 17:59:36 GMT 1999 CHIP Startup--Initializing new tape Wed Jan 27 17:59:42 GMT 1999 MKIII Start Patrol WEATHER COMMENT: Wed Jan 27 17:59:58 GMT 1999 Clear sky, wind=10 mph from the SE, temp=34 F. atrol Wed Jan 27 18:57:55 GMT 1999 MKIII Start Cal Wed Jan 27 19:00:56 GMT 1999 CHIP Bias Wed Jan 27 19:02:08 GMT 1999 CHIP End Bias Wed Jan 27 19:02:18 GMT 1999 CHIP Water Wed Jan 27 19:02:58 GMT 1999 CHIP End Water Wed Jan 27 19:18:07 GMT 1999 MKIII Start Patrol Wed Jan 27 20:00:48 GMT 1999 CHIP Gain Wed Jan 27 20:05:27 GMT 1999 CHIP End Gain Wed Jan 27 20:05:37 GMT 1999 CHIP Bias Wed Jan 27 20:06:27 GMT 1999 CHIP End Bias Wed Jan 27 20:06:42 GMT 1999 CHIP Water Wed Jan 27 20:07:22 GMT 1999 CHIP End Water WEATHER COMMENT: Wed Jan 27 20:34:22 GMT 1999 A very thin cirrostratus started moving in about 30 minutes ago and it has been steadily getting thicker. Wed Jan 27 21:01:48 GMT 1999 CHIP Bias Wed Jan 27 21:02:44 GMT 1999 CHIP End Bias Wed Jan 27 21:02:54 GMT 1999 CHIP Water Wed Jan 27 21:03:32 GMT 1999 CHIP End Water From koon@hao.ucar.edu Wed Jan 27 16:05 MST 1999 Date: Wed, 27 Jan 1999 12:58:53 -1000 From: Darryl Koon Organization: Mauna Loa Solar Observatory To: elmore@hao.ucar.edu, kvs@hao.ucar.edu, alice@hao.ucar.edu, mlso@hao.ucar.edu Subject: Nahenahe and KCC problem Hello, At around 2145 Nahenahe and Kii crashed. MK3 and 4 were at az=184, just starting a new scan. The Nahenahe screen was frozen and I couldn't get control of it. I was able to do Kill on Kii but couldn't get the End Tape task to work, it just stalled. I tried resetting the KCC and that caused the red Fail LEDs on the Corr. and Micro boards to light up, Nahenahe still frozen. STOP-A didn't work, cycled power to Nahenahe and it rebooted up to the point where it showed System ready ReadKCC then there were error messages about remote chassis power being off or a cable disconnected. Maybe that was refering to the KCC? I tried resetting the KCC again and cycling Nahenahe power again in different orders, but still couldn't get past Fail LEDs on KCC boards and incomplete reboot on Nahenahe. Does this sound familiar to anyone? The crash took place while I was trying to fix a PSPT problem so I'm not sure exactly when it happened. The Nahenahe computer is now turned off as is the KCC. I can't finish or send logs, files won't be transferred tonight, etcetera. I need to get to an appointment so I can't stay late to work on it but I'll be back tomorrow morning. Aloha, Darryl **MKIV PROBLEM**: I'm writing this in the log on 1/28 so until late on 1/28 the log entries are going to look funny. There was a crash around 21:45 on 1/27 ut that caused the Nahenahe computer and the KCC to lockup. No further MKIV or MKIII observations can be done until this problem is fixed, there is more information about this on tomorrow's log (1/28 ut). I couldn't rlogin to Nahenahe from Nene, and all the fails LEDs were lit on the KCC. I tried various things like rebooting Nahenahe and the KCC in various different orders but was unable to fix the problem. **PSPT PROBLEM**: No times due to problem with Nahenahe as mentioned above. On the 2200 ut set of observations I noticed the image vignetting again, it always seems to happen later in the day like that. The declination wasn't at a limit. I checked the shutter operation but was unable to see any problems there, it might be worth it to just change the shutter to see if the problem ends. While I was checking the shutter I blocked the beam and the telescope started pointing more and more to the West, and the Mirror On LED stayed lit, I don't understand that, I thought it was lit only when the mirror was locked on the sun? **LOWL PROBLEM**: No time given due to Nahenahe problem explained above. The Lowl crashed at 2236 with those old rectangular graphics characters on the screen. I removed L00576 from drive #0, moved L00577 from #1 to #0, installed L00578 in #1, and restarted the observations. TAPES: ****** MKIV: 99027 CHIP: C00769 LOWL: L00576 and L00577 in drive #0 PICS: Down for repairs. 17_59.rawmk3 18_48.rawmk3 19_47.rawmk3 20_35.rawmk3 21_24.rawmk3 18_03.rawmk3 18_51.rawmk3 19_50.rawmk3 20_38.rawmk3 21_27.rawmk3 18_06.rawmk3 18_54.rawmk3 19_53.rawmk3 20_42.rawmk3 21_30.rawmk3 18_09.rawmk3 19_01.rawmk3 19_56.rawmk3 20_45.rawmk3 21_33.rawmk3 18_12.rawmk3 19_08.rawmk3 20_00.rawmk3 20_48.rawmk3 21_37.rawmk3 18_16.rawmk3 19_14.rawmk3 20_03.rawmk3 20_51.rawmk3 21_40.rawmk3 18_19.rawmk3 19_18.rawmk3 20_06.rawmk3 20_55.rawmk3 21_43.rawmk3 18_22.rawmk3 19_21.rawmk3 20_09.rawmk3 20_58.rawmk3 21_46.rawmk3 18_25.rawmk3 19_24.rawmk3 20_13.rawmk3 21_01.rawmk3 c18_58.rawmk3 18_28.rawmk3 19_27.rawmk3 20_16.rawmk3 21_04.rawmk3 c19_04.rawmk3 18_32.rawmk3 19_31.rawmk3 20_19.rawmk3 21_07.rawmk3 c19_11.rawmk3 18_35.rawmk3 19_34.rawmk3 20_22.rawmk3 21_11.rawmk3 18_38.rawmk3 19_37.rawmk3 20_26.rawmk3 21_14.rawmk3 18_41.rawmk3 19_40.rawmk3 20_29.rawmk3 21_17.rawmk3 18_45.rawmk3 19_44.rawmk3 20_32.rawmk3 21_20.rawmk3