Subject: Re: [sdss3-25mlog 1149] 2.5m obslog 20130325 (MJD 56377)
From: "John K. Parejko"
Date: Tue, 26 Mar 2013 16:42:05 -0600
Ah, now that I know what to look for, I agree: "dangerously late" =
appeared before the move started. I was confused because I saw the =
individual MCP move commands (mcp_move) come before the "dangerously =
late" message. But those are just the TCC building the trapezoid, not =
the actual movement itself.
I think the message was probably repeated in STUI: once when it first =
appeared, and again after the slew had failed, as part of the message =
describing why.
Sorry about the confusion, and thanks for the clarification, Dan.
John
=20
On 26Mar 2013, at 14:56, Dan Long wrote:
> Here are the time stamps of the relevant output from the TCC log.  It =
shows the initiation of the slew at 02:10:05, the warning coming at =
02:10:13, the telescope moving between 02:10:14 and 02:10:29, then =
aborting just before the slew end message at 02:10:31.=20
>=20
> 2013-03-26 02:10:05.702Z 451536 2 > Started; Cmd=3D"track 121,90 mount =
/rota=3D0 /rotty=3Dmount"
> 2013-03-26 02:10:06.331Z 451536 2 I =
AxisCmdState=3D"Drifting","Drifting","Drifting"
> 2013-03-26 02:10:13.692Z 451536 2 W Text=3D"the slew was dangerously =
late"; SlewAdvTime=3D0.68
> 2013-03-26 02:10:14.255Z 451536 2 I MoveItems=3D"YYYYYYYYY"; =
SlewBeg=3D4870980631.21; SlewDuration=3D16.97
> .
> .
> .
> 2013-03-26 02:10:14.733Z 0 0 I =
AxisCmdState=3D"Slewing","Slewing","Slewing"
> 2013-03-26 02:10:14.735Z 0 0 I AxisErrCode=3D"OK","OK","OK"
> .
> .
> .
> Lots of status updates showing the rotator only going to 13 degrees
> 2013-03-26 02:10:29.212Z 0 0 I TCCStatus=3D"SSS","NNN"; =
TCCPos=3D121.000,90.000,0.000; AxePos=3D121.000,90.000,13.177
> .
> .
> .
> 2013-03-26 02:10:29.217Z 0 0 W RotStat=3D13.177214, 0.000000, =
4870980629.07321, 0x00000800; BadRotStatus; RotDTime=3D-0.1; RotID=3D1, =
0
> 2013-03-26 02:10:31.933Z 451536 2 : SlewEnd
>=20
> Maybe STUI held back broadcasting the error until the end of the slew?
>=20
>=20
> -Dan
>=20
>=20
> On Mar 26, 2013, at 2:39 PM, John K. Parejko wrote:
>=20
>> A point of clarification,
>>=20
>> On 26Mar 2013, at 08:52, Dan Long wrote:
>>=20
>>> On Mar 26, 2013, at 8:35 AM, Dan Long wrote:
>>>=20
>>>> Hi all,
>>>>=20
>>>> It appears there was some problem with time between the MCP and TCC =
at the start of last night.  Looking at the TCC log, most slews (the =
ones that failed), had a warning about the slew being dangerously late.
>>>>=20
>>>> 2013-03-26 00:39:37.183Z 451356 2 W Text=3D"the slew was =
dangerously late"; SlewAdvTime=3D0.60
>>>=20
>>> I should add that these warnings came at the start of the slew, =
before an axis would start moving.
>>=20
>> As far as I can tell, this is not true. In the cases I checked in the =
log, the message came at the *end* of the slew. Where did you see that =
it came before the start? Am I reading the logs wrong?
>>=20
>> I know I saw that message in the STUI logs after the slews had =
failed, and I mentioned it to the observers, and to Craig (once he was =
online).
>>=20
>> John
>>=20
>> --
>> *************************
>> John Parejko
>> john.parejko@yale.edu
>> http://www.astro.yale.edu/~jp727/
>> 203 432-9759
>> JWG 465
>> Department of Physics
>> Yale University
>> New Haven, CT
>> **************************
>>=20
>>=20
>>=20
>>=20
>>=20
>>=20
--
*************************
John Parejko
john.parejko@yale.edu
http://www.astro.yale.edu/~jp727/
203 432-9759
JWG 465
Department of Physics
Yale University
New Haven, CT
**************************