×

INDI Library v2.0.6 is Released (02 Feb 2024)

Bi-monthly release with minor bug fixes and improvements

having trouble moving the telescope as a client

  • Posts: 11
  • Thank you received: 0
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.


    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!!
  • 5 years 5 months ago #30574

    Please Log in or Create an account to join the conversation.

    Maybe the mount is parked? Did you check that?
    5 years 5 months ago #30676

    Please Log in or Create an account to join the conversation.

    • Posts: 11
    • Thank you received: 0
    No, "PARK" in "TELESCOPE_PARK" is Off.
    5 years 5 months ago #30686

    Please Log in or Create an account to join the conversation.

    If you checked the INDI server output, you would have seen that it said this:
    2018-10-21T08:59:56: Driver indi_simulator_telescope: No INumber 'Dec' in Telescope Simulator.EQUATORIAL_EOD_COORD

    So it's DEC, not Dec
    The following user(s) said Thank You: chang
    5 years 5 months ago #30713

    Please Log in or Create an account to join the conversation.

    • Posts: 11
    • Thank you received: 0
    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:
    5 years 5 months ago #30763
    Attachments:

    Please Log in or Create an account to join the conversation.

    It's not a typo. In principle, anyone can define any property as they wish. However, in INDI Library (this site), the standard properties are defined here: indilib.org/develop/developer-manual/101...dard-properties.html

    So these is what must be followed.
    5 years 5 months ago #30765

    Please Log in or Create an account to join the conversation.

    Time to create page: 0.647 seconds