Date: Sun, 5 Nov 2000 15:10:29 -0700 (MST)
From: Craig Loomis
Subject: Re: 2.5m Obslog 20001104 (MJD 51853)
  I don't know what work was done after the night log was sent out, but here's
what I found.
  The Error light on the Paralan FO-SCSI converter at the instrument was on.
Hoping to quickly determine whether a fiber was bad, I swapped TX & RX at that
end and went back to the computer room to swap the other end. But the TX SC
connector turned out not to be seated well; I stuck it in, and the system seems
to work. The fibers have been swapped back to their original state.
  I'll remind folks of some Sensys/Paralan/Guider Mac arcana. Most of this
doesn't apply to this case, but it might be useful to get it all down in one
place.
 - The Paralan FO-SCSI converter FO link is independent of the liveness of both
the SCSI device (the Photometrics A2S converter) and the SCSI host (the Mac). If
the Error lights are off at both ends, the link is probably OK, and the Mac
should be able to see the A2S. [We have two spare Paralans in the computer room
spares cabinet].
 - The Mac sees the A2S as a SCSI device, which is why one should boot the
system like a PC with SCSI drives: power off the Mac, power cycle the A2S, power
up the Mac. The error 86 is shown on the listing at the Mac as a SCSI error "no
device or termination". In this case, the A2S was OK (it is an uninformative
black box, though: one power light, one orange error light. Both site A2Ses have
failed, and we do have a spare in a box above the computer room spares cabinet.)
 - The SCSI id of the A2S must be 5 (there's a thumbwheel on the A2S).
 - The scant documentation on the Sensys head proper (i.e. the LEDs) is in the
documentation cabinet.
 - If the A2S is not visible to the Mac, the CamTest program always gives that
particular and incorrect error message. The CamTest program is really only
useful if you suspect something wrong in the camera head.
 - craig
> While testing the health of the spectrographs, we found a problem with
> the guider camera. We checked the fiber connections, the camera
> connections, and with Jon Brinkmann's guidance, the other Paralan
> connections inside the guider electronics box. All appeared okay. The
> camera is getting power and the fibers are set up properly (The Paralan
> shows a green LED and communicates "busy" when the guider Mac reboots).
> We power cycled the guider and rebooted the guider Mac. No Luck. Here
> are the error messages:
>
> TCC says:
>
> 0 0 I Modu="prt_Init_Forth"; Text="initializing TCC_GCAM1; obtaining
> lock"
> 0 0 I Modu="prt_Init_Forth"; Text="resynchronizing I/O stream"
> 0 0 I Modu="prt_Init_Forth"; Text="sending initialization command"
> 0 0 F Modu="prt_ReadReplySet"; Text="too many replies on port LTA11:"
> 0 0 I Modu="prt_ReadReplySet"; Text="the following replies were read:"
> 0 0 I Modu="prt_ReadReplySet"; Text="Cannot open camera :SenSys:; ppk
> error: Error code = 86"
> 0 0 F Modu="prt_Init_Forth"; Text="initialization command init failed"
> 0 0 W Modu="prt_ChangeDev"; Text="the guide camera TCC_GCAM1 will not be
> usable until you fix the problem"
> 0 0 W Modu="prt_ChangeDev"; Text="could not initialize new device:
> TCC_GCAM1"
> 0 0 I Modu="prt_ChangeDev"; Text="this instrument does not have a:
> TCC_GMECH"
>
> The CamTest program on the guider Mac says:
>
> There is no PVCAM available. This application requires that one or more
> be present to operate. Check your HCK diskette for the appropriate
> control panel to load into your System folder.
>
> Could there be a failed component in the guider camera electronics?
> Could there be a corrupted file(s) on the guider Mac?