Date: Mon, 7 May 2018 15:20:19 -0600
Subject: Re: [sloan-25mlog 4066] 2.5m obslog 20180506 (SJD 58245)
From: "Daniel Oravetz"
Hi John,
> That sounds more like the motor...
>
> Did you notice if it was moving slowly before it stopped?
We didn't notice how petal #5 was moving before it stopped. Earlier in the
night (e.g., when we opened) #5 didn't open when all the petals were
commanded open, but toggling the FFS closed and then open again did result
in #5 opening with normal speed alongside the others.
Dan
>>
>> =====
>> Notes
>> =====
>> (1) 1um dust: sum=11755.58
>>
>> (2) FF petal #5 was misbehaving again tonight, although this time it
>> seemed as
>> though the 'open' and 'close' commands weren't even attempted by its FF
>> motor.
>> After we opened the telescope, petal #5 would receive the 'open' or
>> 'close'
>> command and try to get there and after a minute or so would eventually
>> arrive.
>> Sometimes cycling the petals with the 'open' or 'closed' buttons was
>> enough to
>> "kick" the petal into reacting to the command. So while the behavior
>> wasn't
>> normal, at least it was attempting to do as commanded.
>>
>> Later in the night, however, #5 didn't move at all. We could get the MCP
>> to
>> report a 'closed' status or an 'open' status if we manually held the
>> petal in a
>> closed or open state (i.e., the switch seemed to trigger appropriately),
>> but
>> even then we did not physically see any motor movement when any
>> attempted
>> commands were sent to open or close. See Log for additional details.
>>
>> Note that at the time we were working on #5 it was still rather cloudy
>> and once
>> we were on sky afterwards (we left petal #5 open and just used the 'ffs'
>> bypass
>> the remainder of the night) the first APOGEE exposure was "bad"
>> according to
>> APOGEE-QL. So we didn't count any time lost to hardware since the
>> weather still
>> wasn't cooperative.
>>
>