Date: Fri, 28 Jul 2000 17:03:28 -0600 (MDT)
From: Craig Loomis
Subject: Re: 2000-07-28 night log
On Fri, 28 Jul 2000, Camron Hastings wrote:
> Problem #1: Problem Reporting system is out all night. This is a sub
> problem of the next problem.
>
> Problem #2: The entire APO www server had some permission trouble or
> something, nothing is accessible on the website, or on galileo.
  a) The WWW Mac had hung.
  b) I had changed some paths on galileo yesterday, but neglected to adjust the
web server permissions.
> Problem #3: The lightning warnings on the tycho weather window continue
> to give 8 mile lightning warnings when there was none near, at all.
  Lightningstorm.com never sent a "lightning clear" message. I've asked them to
look into it. One worries about missing a "lightning active" message...
> Problem #4: When we tried to open, the echelle slit camera would not
> respond. Started getting Echelle warning email about saddlebags. (Thus,
> we could not update NA1 mirror tilts) I restarted Mac and reinitialized,
> no luck. [(Error code = 86) SCSI trouble or no terminator it states.]
  The power for the slitviewer camera head was found loosely plugged in and was
reconnected. Unfortunately, the A2S converter box on the intermediate level also
failed and has been replaced.
> Problem #5: Decided to use S-H for observing. Tried first slew via
> Remark with no response. Found that the command was passed to the MC but
> then just sat there. The TCC did not seem to receive a slew command. I
> tried to slew with a track command in the TCC and the telescope would
> move fine. The MC would pass a guider focus command and expose command
> to the TCC, so they were talking. I restarted all software multiple
> times without any luck.
>
> Problem #6: When the TCC would move the telescope, Remark would not
> register that any movement was happening. I tried two version, 2.62 and
> 2.55b5 and both acted the same.
  Both the same problem: the MC was rarely connected to the TCC. TCC 2.4 accepts
non-interactive connections slightly differently from earlier versions: until
the TCC is fully up, MC connections are (appropriately) rejected. But the MC
does not know how to retry. For the moment, please wait for the TCC to
completely start before restarting the MC hub.
 - craig