We are sending commands to indiserver that is connected to Temma 2 telescope as a client.
We are able to move and stop moving the telescope using the following commands:
<newSwitchVector device="Temma" name="TELESCOPE_MOTION_NS"> <oneSwitch name="MOTION_SOUTH">On</oneSwitch> </newSwitchVector>
<newSwitchVector device="Temma" name="TELESCOPE_MOTION_NS"> <oneSwitch name="MOTION_SOUTH">Off</oneSwitch> </newSwitchVector>
<newNumberVector device="Temma" name="EQUATORIAL_EOD_COORD"> <oneNumber name="RA">00:00:00</oneNumber> <oneNumber name="DEC">10:00:00</oneNumber> </newNumberVector>
<message device="Temma" timestamp="2018-11-21T17:08:19" message="[ERROR] SendCommand: Timeout error"/>
<defTextVector device="Temma" name="TIME_UTC" label="UTC" group="Site Management" state="Idle" perm="rw" timeout="60" timestamp="2018-11-21T18:13:13">
<defText name="UTC" label="UTC Time"/>
<defText name="OFFSET" label="UTC Offset"/>
</defTextVector>
oh I see. Thanks. it works now. also by the way, in the PDF www.clearskyinstitute.com/INDI/INDI.pdf , page 10, there is a typo where "DEC" was written as "Dec" in the example:
No, "PARK" in "TELESCOPE_PARK" is Off.
Read More...
Hi everyone,
so, we are trying to use INDI protocol to write a client, and connect to indiserver to control a telescope.
But before everything, we are testing the commands through telnet to control a Telescope Simulator in indiserver.
After switching the "CONNECT" switch on, we can:
<getProperties device="Telescope Simulator" version="1.7" name="ON_COORD_SET"/>
<setSwitchVector device="Telescope Simulator" name="ON_COORD_SET" state="Idle" timeout="60" timestamp="2018-10-18T16:07:39">
<oneSwitch name="TRACK">
On
</oneSwitch>
<oneSwitch name="SLEW">
Off
</oneSwitch>
<oneSwitch name="SYNC">
Off
</oneSwitch>
</setSwitchVector>
<getProperties device="Telescope Simulator" version="1.7" name="TELESCOPE_TRACK_RATE"/>
<setNumberVector device="Telescope Simulator" name="TELESCOPE_TRACK_RATE" state="Idle" timeout="60" timestamp="2018-10-18T16:01:22">
<oneNumber name="TRACK_RATE_RA">
15.04106717867020393
</oneNumber>
<oneNumber name="TRACK_RATE_DE">
0
</oneNumber>
</setNumberVector>
<getProperties device="Telescope Simulator" version="1.7" name="EQUATORIAL_EOD_COORD"/>
<setNumberVector device="Telescope Simulator" name="EQUATORIAL_EOD_COORD" state="Idle" timeout="60" timestamp="2018-10-18T16:10:04">
<oneNumber name="RA">
17.966879164642040934
</oneNumber>
<oneNumber name="DEC">
90
</oneNumber>
</setNumberVector>
<newNumberVector device="Telescope Simulator" name="EQUATORIAL_EOD_COORD"> <oneNumber name="RA">10:20:00</oneNumber> <oneNumber name="Dec">45:10:00</oneNumber> </newNumberVector>
<setNumberVector device="Telescope Simulator" name="EQUATORIAL_EOD_COORD" state="Idle" timeout="60" timestamp="2018-10-18T16:26:46">
<oneNumber name="RA">
18.246002905341594413
</oneNumber>
<oneNumber name="DEC">
90
</oneNumber>
</setNumberVector>
<newNumberVector device="Telescope Simulator" name="TELESCOPE_TRACK_RATE"> <oneNumber name="TRACK_RATE_DE">16384.0</oneNumber> </newNumberVector>
<setNumberVector device="Telescope Simulator" name="TELESCOPE_TRACK_RATE" state="Ok" timeout="60" timestamp="2018-10-18T16:30:26">
<oneNumber name="TRACK_RATE_RA">
15.04106717867020393
</oneNumber>
<oneNumber name="TRACK_RATE_DE">
16384
</oneNumber>
</setNumberVector>
<newNumberVector device="Telescope Simulator" name="EQUATORIAL_EOD_COORD"> <oneNumber name="RA">10:20:00</oneNumber> <oneNumber name="Dec">45:10:00</oneNumber> </newNumberVector>
<setNumberVector device="Telescope Simulator" name="EQUATORIAL_EOD_COORD" state="Idle" timeout="60" timestamp="2018-10-18T16:32:28">
<oneNumber name="RA">
18.341391452643488691
</oneNumber>
<oneNumber name="DEC">
90
</oneNumber>
</setNumberVector>
OK thanks so much! and will do.
Read More...
oh ok i see. So only stuff labeled as "oneVetor", "oneText" or "oneSwitch" can be changed by client, the other quantities are controlled by server or driver. Is that correct?
Read More...
Or is that "state" unchangable, and I can only change "CONNECT" and "DISCONNECT"?
I tried to change "CONNECT" to On too and now the state became "Alert"
Read More...
Thanks. I'm still a little confused by how to change a property.
for example, after connecting to the server, if I do:
<getProperties device="Temma" version="1.7" name="CONNECTION"/>
<setSwitchVector device="Temma" name="CONNECTION" state="Idle" timeout="60" timestamp="2018-10-04T19:12:47">
<oneSwitch name="CONNECT">
Off
</oneSwitch>
<oneSwitch name="DISCONNECT">
On
</oneSwitch>
</setSwitchVector>
<newSwitchVector device="Temma" name="CONNECTION"> <oneSwitch name="state">OK</oneSwitch> </newSwitchVector>
The thing is we can't necessarily use c++ but the tutorials are written in c++. By commands i meant the indi XML protocols from the pdf link I attached, where you can talk to indiserver by telnet or socket. I mean sure we can dig through the tutorial to find the functions that use those functions where the commands were called. But it would just be great if there is a list of them so we can just use them.
Read More...
Hi,
yes but we would like to implement something to directly talk to indiserver using probably socket to control our telescope, with the features we need and also without the unnecessary features we don't need.
Would be great if there is a list of commands for client to server communication!
Read More...
I am in a group doing a project using indiserver, and we have to customize our own client to communicate with the server. but we cant really find a good documentation of the commands for client. The only thing we found was:
www.clearskyinstitute.com/INDI/INDI.pdf
and it doesnt list all the commands we can use to communicate with indiserver.
Does anyone know if there's a newer / more complete documentation somewhere?
Thanks!!
Read More...
I am in a group doing a project using indiserver to connect to the telescope, and we have to customize our own client to communicate with the server. but we cant really find a good documentation of the commands for guest. The only thing we can find is:
www.clearskyinstitute.com/INDI/INDI.pdf
and it does not show all the commands to communicate with indiserver.
Does anyone know if there's a newer / more complete documentation somewhere?
Thanks.
Read More...