Subject: Re: [sdss3-25mlog 811] Re: 2.5m obslog 20120914 (MJD 56185)
From: Elena Malanushenko
Date: Sat, 15 Sep 2012 15:57:52 -0600
Dmitry,=20
For test, you can just run several lines=20
from stui command line.=20
=20
stui> tcc axis stop
stui> mcp sem_take
stui> mcp alt move 60=20
in 3-5 sec, during the slew, call again to get double call:=20
stui> mcp alt move 60
    and check where you move. My guess it will move far than 60.=20
    Keep stop button in hand to stop if you move too far.
    It will be good if I wrong.=20
=20
stui> mcp sem_give
stui> tcc axis init
=20
I have removed the script from telescope to add some lines.=20
I might cannot complete it by tonight.=20
Russell suggested me some idea for protection.=20
I did not think about possible double call,=20
and single call is working properly.=20
Thanks,=20
Elena
On 09 /15/ 12, at 3:15 PM, dmbiz@apo.nmsu.edu wrote:
> We can test it tonight bu pressing the button twice (and putting hand =
on
> stop button).
> Dmitry
>=20
>=20
>> Garrett,  and all,
>>=20
>> The button was clicked twice.
>> I have records of that two calls.
>> And the script ran twice.
>> =3D=3D start slew 6 =3D=3D 04:29:28
>> =3D=3D start slew 6 =3D=3D 04:29:34
>>=20
>> It does not change the necessity to protect script
>> from multiple calls which I did not predict.
>> I have to do this. I am sorry and happy that you could
>> fix this without any other problem.
>>=20
>> No mcp help for command line operation.
>> The most of previous iop/mcp commands are not available
>>      in stui or not documented. (or I did not find).
>> Some MCP keywords are not carried with its values ("command", =
example).
>> Some Mcp values are not known for tcc/stui (mcp telescope position, =
mcp
>> brakes).
>> MCP does not return the code of  proper completing of its command.
>>     ("mcp alt move 6" does not or I might did not find).
>>=20
>> I think, if we apply "stui>mcp alt move "
>> twice, we might get unpredicted telescope move.
>> I can check this.
>>=20
>> I better like an idea to use high level
>> tcc operation, consistent with stui,
>> and use mcp for emergency or
>> technological low level operation only.
>>=20
>> Elena
>>=20
>>=20
>> On 09 /15/ 12, at 6:25 AM, gebelke@apo.nmsu.edu wrote:
>>=20
>>> After investigating what could have happened, it looks like the =
goto-6
>>> script
>>> command was sent twice (but 6 seconds apart) even though the button =
was
>>> clicked
>>> only once.
>>=20
>> _____________________________________________________
>> Message 811 of sdss3-25mlog - Logs of nightly APO activities.
>> =
https://trac.sdss3.org/tracmailman/browser/private/sdss3-25mlog/all/811.ht=
ml
>> sdss3-25mlog@sdss3.org
>> https://sdss3.org/mailman/listinfo/sdss3-25mlog
>>=20
>=20
>=20