From: John Barentine
Subject: Re: 2.5m obslog 20050701 (MJD 53553)
Date: Sat, 2 Jul 2005 23:04:48 -0600
--Apple-Mail-1-325967374
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=US-ASCII;
	delsp=yes;
	format=flowed
On Jul 2, 2005, at 10:01 PM, Russell E Owen wrote:
>>
>> The Procedure on sdsshost says to send all the actuators back to
>> nominal
>> zeroes (much like for M1 it says to send actuators to the starting
>> values in
>> PrimDesOrient read at the beginning of a slew to 121,70), though
>> Howard tells
>> me that they are supposed to be set back to "current" values from
>> a recent
>> on-sky night.  Last night I sent the M1 actuators back to nominal
>> commanded
>> values from MJD 53536; tonight I am sending the M2 actuators to
>> the commanded
>> values from the same night.  A=1619120, B=1604909, C=1528405
>>
>
> For M2 it is perfectly reasonable to send them to nominal 0.
> However, you then have to issue a TRACK command to have the TCC
> send the mirror to the correct position for that altitude.
I did issue a track command after this, although it was with the axes
halted.  After finishing the home/relax, I returned to the telescope
and send it to stow (121,30) and halted the axes.  To get the mirror
numbers, I did a fake slew to 121,30 with a track/mount command and
axes halted.  What I don't know offhand is whether it changed the
mirror position then (I didn't check).
So I went ahead and repeated the relax/home of M2 tonight, ending
with sending axes A,B,C to the nominal "zero" per the instructions on
sdsshost.  Now it's clear to me that the procedure as written is
correct... what threw me off is that the procedures tell the user to
send M1 back to the positions in the PrimDesOrient after finishing
the home/relax routine.  Can you explain this better to me, Russell?
The procedure I am referring to is on:
     http://www.apo.nmsu.edu/Telescopes/TCC/
OperatorsManual.html#HomingSDSSPrimary
>> Attempting to get mirror numbers through logTool still doesn't work.
>
> How were you doing your homing? Typically one either logs into the
> terminal server or uses the HOST program on the TCC. Either way,
> the TCC cannot talk to M2 reliably until you close the telnet
> session or get out of HOST.
I did the homing via a HOST session to TCC_SEC, and attempted to grab
mirror numbers a couple of hours later as I was filling out the log,
after I'd quit the host session.
> That was the reason the TCC could not see M2 a few days ago (kudos
> to whoever solved that one).
Right, and that was thanks to French.  Howard astutely caught in the
day logs that work had been done on the M2 galil recently and he
wondered aloud whether something was left *physically* disconnected,
causing our problems two nights ago.  Luckily that was not the case,
and there was simply a telnet session to M2 that had been left open
inadvertently.
John
--Apple-Mail-1-325967374
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=ISO-8859-1
On Jul 2, 2005, at =
10:01 PM, Russell E Owen wrote:The Procedure on sdsshost says to send all the =
actuators back to nominalzeroes (much =
like for M1 it says to send actuators to the starting values =
inPrimDesOrient read at the beginning of a slew =
to 121,70), though Howard tellsme that they =
are supposed to be set back to "current" values from a recenton-sky night.=A0=
 Last night I sent the M1 actuators back to nominal =
commandedvalues from MJD 53536; tonight I =
am sending the M2 actuators to the commandedvalues from the same night.=A0 A=3D1619120, B=3D1604909, =
C=3D1528405 For M2 it is perfectly =
reasonable to send them to nominal 0. However, you then have to issue a =
TRACK command to have the TCC send the mirror to the correct position =
for that altitude.I did issue a track command =
after this, although it was with the axes halted.=A0 After finishing the =
home/relax, I returned to the telescope and send it to stow (121,30) and =
halted the axes.=A0 To get the mirror numbers, I did a fake slew to =
121,30 with a track/mount command and axes halted.=A0 What I don't know =
offhand is whether it changed the mirror position then (I didn't =
check).=A0=A0So I went ahead and =
repeated the relax/home of M2 tonight, ending with sending axes A,B,C to =
the nominal "zero" per the instructions on sdsshost.=A0 Now it's clear =
to me that the procedure as written is correct... what threw me off is =
that the procedures tell the user to send M1 back to the positions in =
the PrimDesOrient after finishing the home/relax routine.=A0 Can you =
explain this better to me, Russell?=A0 The procedure I am referring to =
is on:=A0=A0 =
=A0http://www.apo.nmsu.edu/Telescopes/TCC/OperatorsManual.html#H=
omingSDSSPrimaryAttempting to =
get mirror numbers through logTool still doesn't work.=A0How were =
you doing your homing? Typically one either logs into the terminal =
server or uses the HOST program on the TCC. Either way, the TCC cannot =
talk to M2 reliably until you close the telnet session or get out of =
HOST.I did the homing via a HOST =
session to TCC_SEC, and attempted to grab mirror numbers a couple of =
hours later as I was filling out the log, after I'd quit the host =
session.=A0=A0That was the reason the TCC could not see M2 a few =
days ago (kudos to whoever solved that =
one).Right, and that was =
thanks to French.=A0 Howard astutely caught in the day logs that work =
had been done on the M2 galil recently and he wondered aloud whether =
something was left *physically* disconnected, causing our problems two =
nights ago.=A0 Luckily that was not the case, and there was simply a =
telnet session to M2 that had been left open =
inadvertently.=A0=A0John=
--Apple-Mail-1-325967374--