Subject: Re: [sloan-25mlog 2209] 2.5m obslog 20150404 (SJD 57117)
From: Kaike Pan
Date: Tue, 7 Apr 2015 09:09:02 -0600
Hello All,
  I went through night logs in Feb, March, and April, with my memory, I =
summarize known problems that
may somewhat relate to the new tcc along with my temporary fixes (from =
night operation aspect) in SDSS
Observing Plan page:=20
=
https://trac.sdss.org/wiki/APO/Observatory/ObserverForum/SDSSIVObsPlans/Ap=
r2015#Knownnewtccproblems
   Please let me know if there are more new tcc related issues that =
observers should know, and if these
temporary fixes make sense. Thanks,
-kaike
> On Apr 5, 2015, at 9:37 AM, Kaike Pan  wrote:
>=20
>=20
>> On Apr 5, 2015, at 9:27 AM, Dan Long  wrote:
>>=20
>>=20
>> On Apr 5, 2015, at 9:11 AM, Kaike Pan wrote:
>>=20
>>>=20
>>>> On Apr 5, 2015, at 8:54 AM, Dan Long  wrote:
>>>>=20
>>>>=20
>>>> On Apr 5, 2015, at 8:35 AM, Kaike Pan wrote:
>>>>=20
>>>>>=20
>>>>>> On Apr 5, 2015, at 6:12 AM, dmbiz@apo.nmsu.edu wrote:
>>>>>>=20
>>>>>>=20
>>>>>>                  APACHE POINT OBSERVATORY SDSS 2.5M
>>>>>>=20
>>>>>>                            OBSERVING LOG
>>>>>>                     Saturday April 04, 2015
>>>>>>=20
>>>>>>                             (SJD 57117)
>>>>>>=20
>>>>>> ----  Observing Team ----
>>>>>>=20
>>>>>> Gordon Freischlad
>>>>>> Dmitry Bizyaev
>>>>>> Dan Long (phone)
>>>>>> Connor Sayres (stui chat)
>>>>>> John Parejko (stui chat)
>>>>>> Jon Brinkmann (phone)
>>>>>>=20
>>>>>> ---- Observing Summary ----
>>>>>>=20
>>>>>> Mostly cloudy - to almost clear night with decent seeing.
>>>>>>=20
>>>>>> APOGEE plates exposed:
>>>>>> 1 8045 176+00   1xABBA+1xAB+MANGA. 3 missing fibers, 2 faint
>>>>>> 4 8052 270+60   2xABBA+MANGA, 6 missing, 3 faint
>>>>>> 9 8467 ORPHAN-2 2xABBA, 2 missing, 2 faint
>>>>>> 8 8472 ORPHAN-4 2xABBA, 4 missing, 3 faint
>>>>>> 7 8351 URMINOR  1xABBAx1000 sec, 1 missing, 3 faint
>>>>>> 5 7955 M5PAL5   2xBAAB+1xBA, 4 missing, 3faint
>>>>>> 6 8477 025+12   2xABBA, 2 missing, 7 faint
>>>>>>=20
>>>>>>=20
>>>>>> There were issues with bias exposures during afternoon=20
>>>>>> checkout.=20
>>>>>> AZ axis did not move, and we spent significant time on
>>>>>> fixing it, with JP, CS, DL, and JB on the phone.=20
>>>>>> See the afternoon section of the log for details.
>>>>>> Some 30 min of observing time was lost due to this problem
>>>>>> (with partly cloudy sky and engineering time, any way)
>>>>>> We collected some 15K dust-hours on the optics. Please check.=20
>>>>>>=20
>>>>>=20
>>>>> Thank Dmitry for the details in the log.=20
>>>>>=20
>>>>> We saw the same problem with a older version (2 versions older) of =
the new tcc.
>>>>> Basically, no error, but the telescope doesn=92t response to =93tcc =
track=94 command,
>>>>> and that the telescope moves normally with mcp, and that rebooting =
mcp from
>>>>> mcpMenu (with hard option) does fixed the problem. Instead, the =
mcp needs
>>>>> to be rebooted from the crate. That said, this does=92t looks like =
a problem with
>>>>> the only new version tcc. But I thought that this is a problem =
that the new version=20
>>>>> tcc tried to fix: Communication issue between multiplexor and tcc, =
 Conor, is this
>>>>> true?=20
>>>>>=20
>>>>=20
>>>> There was an interesting and perhaps significant difference between =
this and the previous failure you mention.  In this case only one axis =
(azimuth) failed to respond to the track command.
>>>=20
>>> Last time, it was altitude that didn=92t response to track command.  =
But we didn=92t try to move the telescope on other axes. It still could =
be the same=20
>>> problem but on a different axis.=20
>>=20
>> If I remember right, we opened (using the menu to move alt) and tried =
slewing in all axes when the enclosure was off, and nothing moved.  At =
least that is what I think was going on (I was in the control room at =
the time).
>=20
> I don=92t recall that we tried to move the telescope on other axes.  I =
will dig into logs to find it out tonight.=20
>=20
>>=20
>>>=20
>>>> It does appear that somehow occasionally when restarting the new =
TCC (or changing versions), the mcp gets affected in a way that causes =
at least some communications from the TCC to get ignored.
>>>>=20
>>>> -Dan
>=20
> ____________________________________________________________
> Logs of Nightly APO Activities
> =
https://trac.sdss.org/tracmailman/browser/private/sloan-25mlog/index.html