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>
etc. for North, West, East

But we cannot set the coordinates to move the telescope using RA and DEC(in TRACK mode), or to synch the coordinates(in SYNC mode) using the commands:
<newNumberVector device="Temma" name="EQUATORIAL_EOD_COORD"> <oneNumber name="RA">00:00:00</oneNumber> <oneNumber name="DEC">10:00:00</oneNumber> </newNumberVector>
Sometimes it shows the following error, but sometimes it times out without the message:
<message device="Temma" timestamp="2018-11-21T17:08:19" message="[ERROR] SendCommand: Timeout error"/>
while the same commands work for the "Telescope Simulator".

We can not really see what is wrong but we suspect it is related to the geographical location and LST time not set. Are they related? Right now we are trying to go through the c++ code from indi github for Temma driver to get some clues, but it is not going well.
LAT and LONG in geographical location can be set easily; however, the TIME_UTC is in format of "text" and we cannot successfully set it. Is this time the one we need to change or not?
properties for TIME_UTC:
<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>

please help.

Read More...

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:



Read More...

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:

  • turn the telescope using switch "MOTION_NORTH"(or south) in "TELESCOPE_MOTION_NS"(or we)
  • stop the turning by switching from "On" to "Off"
  • read the coordinates by getProperties of "EQUATORIAL_EOD_COORD"
To actually use the telescope practically though, we almost always tell it a new coordinate to point at, and expect it to turn to that coordinate and stop. However, we can't manage to do that.

From the description on the Standard Properties page, the correct order to do that seems like to be:
  1. switch "TRACK" in "ON_COORD_SET" to "On"
  2. change "RA" and "DE" in "EQUATORIAL_EOD_COORD"
then it is done. However, here is what happens:
  • I checked the "ON_COORD_SET":
  • input:
<getProperties device="Telescope Simulator" version="1.7" name="ON_COORD_SET"/>
it returns:
<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>
So it's "TRACK" mode by default.
  • I checked the "TELESCOPE_TRACK_RATE":
  • input:
    <getProperties device="Telescope Simulator" version="1.7" name="TELESCOPE_TRACK_RATE"/>
    it returns:
    <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>
    seems like its tracking as a equatorial mount (since 360°/24hours=15arcsecound/secound).
  • checked the "EQUATORIAL_EOD_COORD" right now
  • input:
    <getProperties device="Telescope Simulator" version="1.7" name="EQUATORIAL_EOD_COORD"/>
    output:
    <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>
    and it keeps changing, which is consistent with the "TELESCOPE_TRACK_RATE". (I actually don't know how to stop it in telnet. have to reopen telnet and reopen)
  • now try to give it a new coordinate:
  • input:
    <newNumberVector device="Telescope Simulator" name="EQUATORIAL_EOD_COORD"> <oneNumber name="RA">10:20:00</oneNumber> <oneNumber name="Dec">45:10:00</oneNumber> </newNumberVector>
    it returns:
    <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>
    and the "RA" keeps changing like before and "DEC" does not.
    I believe the "RA" changes because of the 15arcsecond/s track rate and "DEC" is not changing at all.
  • now if we change the track rate for "DE":
  • input:
    <newNumberVector device="Telescope Simulator" name="TELESCOPE_TRACK_RATE"> <oneNumber name="TRACK_RATE_DE">16384.0</oneNumber> </newNumberVector>
    (16384.0 is the maximum rate you can give)
    it returns:
    <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>
  • now try again:[li/]
    input:
    <newNumberVector device="Telescope Simulator" name="EQUATORIAL_EOD_COORD"> <oneNumber name="RA">10:20:00</oneNumber> <oneNumber name="Dec">45:10:00</oneNumber> </newNumberVector>
    it returns:
    <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>
    so it didnt work at all.
    [/ul]

    we also tried "SYNC" and "SLEW" mode and nothing works. I must be doing something really wrong, and if someone please point it out for me I'd really appreciate it!!


  • Read More...

    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"
    :side:

    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"/>
    it returns:
    <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>
    Now if I wanna change, for example, the state from "Idle" to "OK", do I do:
    <newSwitchVector device="Temma" name="CONNECTION"> <oneSwitch name="state">OK</oneSwitch> </newSwitchVector>
    ?
    But the state properties does not change.

    Read More...

    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...