----------------------------------------------------------------------------- Mauna Loa Solar Observatory Observer's Log ----------------------------------------------------------------------------- Thu Dec 3 17:05:15 GMT 1998 Year: 98 Doy: 337 Observer: koon WEATHER COMMENT: Thu Dec 3 17:05:17 GMT 1998 Thick altocumulus overcast, wind is gusty and 30+ mph, temp=36 F. COMMENT: Thu Dec 3 17:10:02 GMT 1998 Mel called and said the extension cord for the UPS is ready for pickup, I'll get it later today. MKIII COMMENT: Thu Dec 3 17:13:55 GMT 1998 The console screen was locked up so I couldn't type in "Run", and the startup script didn't finish executing. So I reset the KCC to get control again, that worked. **LOW-L PROBLEM**: Thu Dec 3 17:17:34 GMT 1998 Data are going to L00561 in drive #1, but L00560 only had about 10 files on it yesterday (drive #0). Removed L00560 and installed L00562 in drive #0. MKIV COMMENT: Thu Dec 3 20:20:42 GMT 1998 **MKIV PROBLEM**: Thu Dec 3 20:20:53 GMT 1998 I talked to David about any tests I could do to the instrument that don't require sunlight. One test is to watch the yellow LEDs on the transformation board to see if more than one illuminates, only one illuminate normally. There are 4 yellow LEDs on the top of the board and they are visible from the back of the cabinet if you open the back door. **LOW-L PROBLEM**: Thu Dec 3 20:24:33 GMT 1998 The clock finally jumped ahead exactly one hour again. I'm going to stop the program and check the clock board time another way. **LOW-L PROBLEM**: Thu Dec 3 20:39:40 GMT 1998 After I exited the program I checked the cts10 clock using the ctconfig program and it was correct. I then restarted the program by typing in "lowl" and it started up with the correct time. I didn't reboot the computer or cycle the computer power. Thu Dec 3 20:42:00 GMT 1998 MKIII Start Patrol **LOW-L PROBLEM**: Thu Dec 3 20:52:24 GMT 1998 I moved L00561 to drive #0 since it didn't have any data on it, and moved L00562 into drive #2. If the manual clock reading showed the wrong time then that would have proven the board or antennae were bad, but it showed the correct time. Restarting the program may correct the time, it did this time, but in the past 2 times that I've seen this I cycled the PC power to correct the time, I didn't try just restarting the program those first two times. It is also possible that checking the time with ctconfig corrects the time. So nothing concrete was learned from that test. Thu Dec 3 21:01:27 GMT 1998 MKIII End Patrol **MKIV PROBLEM**: Thu Dec 3 21:02:35 GMT 1998 The same, frontmost, LED remained illuminated during the span of 4 scans, no other LEDs lit up. **MKIV PROBLEM**: Thu Dec 3 21:13:07 GMT 1998 Talked to David again about the LED test. Will have to wait for sunlight before continuing the testing. Probably will shorten the exposure time for the two "reads" that happen between each index pulse from the waveplate. The index pulses should be good or the MKIII wouldn't be working. **LOW-L PROBLEM**: Thu Dec 3 21:15:27 GMT 1998 Talked to David again about this problem. The whole system is going to be replaced in a few months, so hopefully this strange time problem won't happen very often until then. But if it does, it may be possible to change the software to fix the problem, assuming the time board is always correct and the program wasn't picking it up correctly. The program gets the time from the time board by checking it every 15 seconds currently. This is one of those strange intermittent problems that are easiest to troubleshoot by swapping the board itself as a primary test, but if the whole system is going to be changed to use GPS or another type of timesetting protocol then it could be a waste of money to get a new CTS10 card at this time. Thu Dec 3 21:33:13 GMT 1998 MkIII 20_42.rawmk3 20_48.rawmk3 20_55.rawmk3 20_45.rawmk3 20_51.rawmk3 20_58.rawmk3