Date: Sat, 22 Jan 2000 01:45:38 -0700 (MST)
From: Ellyne Kinney
Subject: 2.5m obslog 000121 (MJD 51564)
                        Friday, January 21, 2000
                    Apache Point Observatory SDSS 2.5m
                             Observing Log
Observing Team: Ellyne Kinney (APO)
		Steve Kent (FNAL)
Weather:  Partly Cloudy.
French turned the telescope over to us at ~4:30 pm.  We were able to start
up the TPM logging facility today without any problems.  The TPM log is in
/mcptpm with the filename tpm51564.dat.  We also tried starting up the
tpmrt tool today, but just got an empty dialog box when the tool was
invoked. We wanted to use the Real-Time display to watch the Altitude
drive voltages while we tested the balance.  We used the tool in
/usrdevel/peregrin/tpm/tpmrt.  Is this the proper version of the tool to
use?  (PR# tpm/682) [section 9 of the shakedown test]
We then went on to test the balance as outlined in section 4.3 of the 2.5m
shakedown plan.  The telescope did not come out of closed loop during the
test when the telescope was balance or when the telescope was
out-of-balance by 100 units.
We then crossed the fiducials for all three axes.  The only difficulty
we noted was that the valid fiducial on the rotator was initially
identified as fiducial #81 and was identified as #83 for all subsequent
crossings? (PR# mcp/683) [section 4.1.6 of the shakedown test]
The alignment clamp was tested and engages properly through the MCP.  The
clamp status is also being correctly reported as being engaged or
disengaged.  We did not see a status of 'neither' for the alignment clamp
in the interlocks display. [section 4.1.11 of the shakedown test]
The brake status for both the Az and Alt was incorrectly reading a status
of 'neither' in the interlocks display.  When the brakes were cleared
(in both the MCP and TCC interfaces) the brake status will change to 'off
for a few (~5) seconds and then change to 'neither'.  We noted that the
alt_brake_dis and az_brake_dis were both bad (red).  We interpret this to
mean that the brake in not registering as disengaged.  (PR# mcp/684)
[sections 4.1.1 and 4.2.1 of the shakedown test]
French mentioned to us he saw the problem of the amp getting into a
confused state we reported on Thursday (PR# 25m-amp/679), if you asserted
and cleared the brakes from the MCP Menu 3 times in a row.   We were able
to reproduce this problem if we cycled the Az brakes on/off very quickly.
If we waited ~15seconds after asserting the brakes to clear them again the
brakes/amps did not get confused.  This happen to coincide with the time
needed to get a 'neither' status (PR# mcp/684) in the interlocks display.
We tried introducing this problem in the Alt brakes/amps and were not able
to confuse the amp no matter how quickly we cycled the brake on/off.  We
were able to reproduce this problem in Az with the TCC interface by
issuing a new slew command while a slew was already in progress.  French
mentioned that he was able to clear the confused amp by turning off the
monitoring system in the MCP, clearing the amp and brake and then turning
the monitor back on. (The & sign in the MCP Menu will toggle the monitor
on and off.)  We were also able to clear the amp status in this way.
(PR# mcp/685) [sections 4.1.1 and 4.2.1 of the shakedown test]
We then tested slews in the TCC interface by issuing several slews in
varying directions in the following coordinate systems: mount, observed,
and fk5.  The slews worked as expected and we were able to issue 'axis
stop' and 'axis init' command during a slew without any problems.  We were
not able to issue a second slew while a slew was already in progress,
because as we noted above the Az amp/brake would become confused.
[sections 4.2.2-4.2.5 of the shakedown test]
We tested the 'offset calib' command while tracking in fk5 coordinates. We
were able to confirm that calib offsets behave like object offsets.  Large
offsets work in positive directions, but not negative ones. (See PR# mcp\
680) [sections 4.2.7, 4.2.9 and 5.6 of the shakedown test]
We were able to confirm that the track and guide commands in the TCC
work as expected.  We were also able to confirm that slews in the TCC that
were beyond the soft limits were rejected. [sections 5.2, 5.3 and 5.7 of
the shakedown test]
We confirmed that the counterweights can be moved from the MCP and the
controls in the lower enclosure. [sections 7.1 and 7.2 of the shakedown
test]
We could not move the telescope using the manual pendant.  The wind screen
would hit the telescope and then the brakes would engage.  Do we need to
have the MCP monitor turned off to use the manual pendant? (PR#
2_5m-telescope\686) [section 6.2 of the shakedown test]
We tested the show command in the TCC.  All keywords returned reasonable
values (keywords and values are appended below). [section 5.1 of the
shakedown test]
TCC keywords and values
=======================
database	entries used, available  12, 20
		memory  used, available 24240, 30000
exptime		5.0
focus		0
gfliter		0
gscansize	.1, .1
gstats		'not enough points'
inst		engcam
max users	50
mount		NaN, NaN
mynum		1
phys		345, 30.8, 13.17
ptrefrad	8
predfwhm	.0004
ptscansize	.1, .1
scalefactor	1
stat		(telscope position)
stinterval 	10,2
time		(LST)
version		2.2.2 Jan 4,2000
wavelenth	5500 (object)
weather		(weather info from 3.5m?)
*****************************************************************************
Ellyne K. Kinney
SDSS Observer                   INTERNET: ekinney@apo.nmsu.edu
Apache Point Observatory        Voice: (505) 437-6822
Sunspot, NM 88349
*****************************************************************************