Date: Wed, 24 Mar 1999 17:55:39 -0800
From: Russell E Owen
Subject: Re: 3.5m Night Log 990320 (followup)
> * There was a repeat of the problem described yesterday during stow
> procedures; since it now appears to be repeatable, I detailed it in
> a problem report. Another interesting matter came up, however. This
> time, when the alt motors began to complain, I issued an "axis
> stop" to stop the telescope, which seemed to work. But when I sent
> a new rotate command, the azimuth and altitude axes both started
> moving as well. This sounds like a potential problem.
I have made the following changes to the TCC as part of the guider
overhaul. These changes will not be available on the 3.5m for awhile
(though they can be implemented sooner if there's a big demand).
track/stop explicitly halts the rotator, as well as azimuth and
altitude. Unlike axis init and axis stop, it is impossible to restart
from track/stop because the TCC intentionally sets the coordinate
system and (in the new TCC code) the rotation type to "none".
the rotate command uses /norestart by default. You have to explicitly
specify /restart to get it to restart azimuth and altitude.
Again, these changes have only been implemented in the guider
overhaul. They are not yet available on the 3.5m telescope. They are
documented in the prerelease commands manual (which is on the web,
see the main TCC documents page for a pointer).
Regards,
-- Russell