Subject: Re: [sdss3-25mlog 491] Re: 2.5m obslog 20120129 (MJD 55956)
From: Elena Malanushenko
Date: Mon, 30 Jan 2012 12:32:48 -0700
On Jan 30, 2012, at 12:11 PM, Kaike Pan wrote:
> Hi All,
>=20
>  Looks like we have a very confusing situation here:
>=20
>  All collimators actuators (a,b,c) on SP1 were commanded to move -3264=20=
> steps by quick hartmann in "gotoFeild".  However, collimator motor c =
only moved=20
> -2270 steps while a and b did make to their destination positions. =20
10:12:17  hartSp1: r=3D248, b=3D0.9, txt=3DOK, sp1Temp =3D 2.9 ;=20
10:12:17  sos.sp1AverageMove =3D -3264
10:12:27 motorPos.sp1.move:  -1000,   -1001,   -2000; =20
I think a and b moved only -1000, they did not go to their destination =
position either.=20
And c moved -2000.=20
> The net
> result was that XMIDs was shifted by -10 pixels on b1 and r1. =
Unfortunately, we=20
> were still within spec, did not lost on sky time for this.
>=20
>    I just moved SP1 collimators up and down, and verified that all =
collimators
> were far away from either forward or reverse limits: 18000 steps from =
forward limit,
> 30000 steps from reverse limit. So neither actuator should have hit =
either forward
> nor reserve limit.  I am really puzzled by what could have caused the =
actuator c=20
> -1000 step short from its goal position. Any thought? I feel we need =
to understand
> this, it will cause us on sky time sooner or later if it is not fixed.
>=20
> -kaike
>=20
>=20
>>=20
>> We may have hit a limit on the sp1 collimator actuators during =
cartridge 18
>> observations (see log body for details), but were still able to take =
in-spec
>> data without stopping to adjust the center of the collimator range.
>>=20
>>=20
>> Received the following error:
>> 10:11:18 client.v4.sos 134 boss w text=3D"reversed a =
(requested=3D-1000; moved=3D1)"
>> 10:11:18 client.v4.sos 134 boss f text=3D"Motor move on (sp1mech a) =
failed or did
>> not finish: actuator reversed direction"
>> 10:11:18 CmdDone: client.v4.sos 134 boss moveColl spec=3Dsp1 =
piston=3D-3264
>> 10:11:18 APO.viktorm.sop 615 sos f text=3D"collimation process =
failed"
>> 10:11:18 CmdDone: APO.viktorm.sop 615 sos doHartmann
>> 10:11:18 APO.viktorm 193 sop i =
stageState=3D"gotoField.hartmann","failed",0.0,0.0
>> 10:11:18 APO.viktorm 193 sop i
>> gotoFieldState=3D"running","OK","done","failed","pending","pending"
>> 10:11:18 APO.viktorm 193 sop i =
gotoFieldStages=3D"slew","hartmann","calibs","guider"
>> 10:11:18 APO.viktorm 193 sop i gotoFieldState=3D"failed","failed to =
take hartmann
>> sequence","done","failed","pending","pending"
>> 10:11:18 APO.viktorm 193 sop i gotoField_flatTime=3D30.0,30;
>> gotoField_arcTime=3D4.0,4; gotoField_guiderExpTime=3D5.0,5.0;
>> gotoField_guiderFlatTime=3D0.5,0.5
>> 10:11:18 APO.viktorm 193 sop f text=3D"Failed to do Hartmann =
sequence"
>>=20
>> This looks like we may have hit a limit on the sp1 collimator =
actuators.
>> However, the calibrations were all in spec (both in *SIGMA and in =
*MID, although
>> r1 XMID was yellow in S0S), so we ended up very close to where we =
needed to be.
>> We proceeded with science.
>=20
>=20
>=20
> _______________________________________________
> Message 491 of sdss3-25mlog - Logs of nightly APO activities.
> sdss3-25mlog@sdss3.org
> https://sdss3.org/mailman/listinfo/sdss3-25mlog
Elena Malanushenko
elenam@apo.nmsu.edu
All things are difficult before they are easy.