×

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

Bi-monthly release with minor bug fixes and improvements

IOptron Driver NOT WORKING with 8401 Hand Controller

  • Posts: 155
  • Thank you received: 10
Hello Jasem,

While I can confirm slewing movement by the mount, the Ekos Mount Control and INDI control of mount speed or manual movement in any given direction is still NOT working. I am just guessing this is an error in the command or sequence timing.

Dan
Last edit: 6 years 8 months ago by Dan Holler.
6 years 8 months ago #17606
Attachments:

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

  • Posts: 322
  • Thank you received: 31
Yesterday, I had the scope out, I was using the context menu from Kstars, and that worked.

But, I confirm what Dan found: that the arrow keys from Ekos "Mount Control" do not work.

And perhaps directly related, when doing a 'Capture and Solve' from Ekos Align, it keeps trying iteration after iteration because 'accuracy not met', with no improvement in the accuracy.

Looking through the code, and in page 42 of the 8401 hand controller manual, perhaps the following patch would fix the problem. I can't test it until late at night.
diff --git a/libindi/drivers/telescope/lx200gotonova.cpp b/libindi/drivers/telescope/lx200gotonova.cpp
index 29fda90..eecf7d8 100644
--- a/libindi/drivers/telescope/lx200gotonova.cpp
+++ b/libindi/drivers/telescope/lx200gotonova.cpp
@@ -593,20 +593,20 @@ int LX200GotoNova::moveGotoNovaTo(int direction)
     switch (direction)
     {
     case LX200_NORTH:
-        DEBUGF(DBG_SCOPE, "CMD <%s>", ":mn#");
-        tty_write_string(PortFD, ":mn#", &nbytes_write);
+        DEBUGF(DBG_SCOPE, "CMD <%s>", ":Mn#");
+        tty_write_string(PortFD, ":Mn#", &nbytes_write);
         break;
     case LX200_WEST:
-        DEBUGF(DBG_SCOPE, "CMD <%s>", ":mw#");
-        tty_write_string(PortFD, ":mw#", &nbytes_write);
+        DEBUGF(DBG_SCOPE, "CMD <%s>", ":Mw#");
+        tty_write_string(PortFD, ":Mw#", &nbytes_write);
         break;
     case LX200_EAST:
-        DEBUGF(DBG_SCOPE, "CMD <%s>", ":me#");
-        tty_write_string(PortFD, ":me#", &nbytes_write);
+        DEBUGF(DBG_SCOPE, "CMD <%s>", ":Me#");
+        tty_write_string(PortFD, ":Me#", &nbytes_write);
         break;
     case LX200_SOUTH:
-        DEBUGF(DBG_SCOPE, "CMD <%s>", ":ms#");
-        tty_write_string(PortFD, ":ms#", &nbytes_write);
+        DEBUGF(DBG_SCOPE, "CMD <%s>", ":Ms#");
+        tty_write_string(PortFD, ":Ms#", &nbytes_write);
         break;
     default:
         break;
@@ -622,7 +622,7 @@ int LX200GotoNova::haltGotoNovaMovement()
     int error_type;
     int nbytes_write = 0;
 
-    if ((error_type = tty_write_string(PortFD, ":q#", &nbytes_write)) != TTY_OK)
+    if ((error_type = tty_write_string(PortFD, ":Q#", &nbytes_write)) != TTY_OK)
         return error_type;
 
     tcflush(PortFD, TCIFLUSH);
Last edit: 6 years 8 months ago by Khalid. Reason: Corrected command for halting movement
6 years 8 months ago #17612

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

yeah I just saw that, I actually removed those functions completely since they are identical to LX200Generic. Please git pull and try again. Regarding accuracy, there is :CM vs :CMR just like LX200-Astrophysics driver. I guess that needs to be implemented as well.

EDIT: Ok, added support for :CMR now
Last edit: 6 years 8 months ago by Jasem Mutlaq.
6 years 8 months ago #17613

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

  • Posts: 322
  • Thank you received: 31
Regarding: "... there is :CM vs :CMR just like LX200-Astrophysics driver. I guess that needs to be implemented as well".

So, the code from lx200ap can be just lifted into the GotoNova driver? What about the user interface part how would :CM and :CMR be used?
6 years 8 months ago #17615

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

It's already implemented in Gotonova now, it's set to :CM by default and you can switch it to :CMR in INDI Control Panel.
The following user(s) said Thank You: Khalid
6 years 8 months ago #17618

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

  • Posts: 155
  • Thank you received: 10
Thanks Jasem, this seems you have the driver working just fine when tested inside. I'll put it out under the stars for the next test. Both you guys have done IOptron a real service.

Dan
6 years 8 months ago #17632

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

  • Posts: 322
  • Thank you received: 31
Astrodan,

When you are testing, connect to INDI, then check if your initial slew to an object is off. If so, then check the hand controller under Setup Controller -> Setup Observation Site. You may find that the offset from UTC is wrong. For example, I am on Eastern Daylight Time now, and KStars is set to -5 with US DST. In the hand controller I see the offset changing from 300 to 240 minutes. This only happens when the hand controller is connected to KStars. Even if I disable syncing in INDI Device Updates and set it to Device. The only way I found it to not cause that offset is to power on the mount, wait for the GotoNova GPS to say 'GPS OK', then connect KStars, then go back to the handset and change 240 to 300. Let me know if you face this and find another way to fix it.

Another thing that will save you time: when doing Polar Align Assist, it says to engage tracking. The way to do it is to press the 0 button on the handset. It is buried in the manual and hard to find, so that is how.

Jasem,

I tested the mount for two consecutive nights, including the latest Mount Control and CM/CMR changes. Thanks for all the effort.

The change for :Mn/s/w/e made a difference in Capture and Solve when selecting Slew To Target. I hear the mount moving.

I can confirm that Mount Control now works and moves the mount.

The only issue is that the slowest speed is 16X. The hand controller has 2X and 8X. These are crucial for positioning objects. I realize that there is no such speeds for :RCx# commands, so not sure how it can be done, or how the hand controller does it.

I encountered two issues though:

1. When clicking CMR in INDI, KStars froze, and I had to kill and restart it.

2. On the previous night, I was able to complete a polar align using Ekos without issues. However I tried 3 times last night and in all three attempts KStars aborts around the 3rd image capture and solve. Two times before the positioning magenta line, and one after. In all cases, I could not complete a polar align. It could be due to something in the Canon/Gphoto driver. I don't know. I sent a bug report when Kstars prompted me to do so. The log is attached for the third attempt, but I doubt it will benefit anything if the issue is in the camera driver/interface.

I attached the debug log for the mount.

Unrelated to the mount is Live View works the first time it is invoked, then the next time it freezes and kills the INDI driver for Canon (I use a 650D). This may relate to 2 above. Don't know?
6 years 8 months ago #17637
Attachments:

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

  • Posts: 322
  • Thank you received: 31
I found a few bugs and fixed them.

According to the hand controller manual page 41 there are differences from what is in the code, and what is in the manual.

Here they are:

1. :SC command

SCOPE 5.429171 sec : CMD <:SC 07/19/17#>
SCOPE 5.450280 sec : RES < >

Response should 32 spaces then #, then 32 spaces and another #

2. :Sg command

SCOPE 5.481597 sec : CMD <:Sg -080:48:11#>
SCOPE 5.501859 sec : RES < >

The format in the manual is:

:Sg sDDD*MM:SS#

So, a * instead of the : after the degrees

Response should be 1

3. :SG command:

SCOPE 5.460447 sec : CMD <:SG -04:00#>
SCOPE 5.481436 sec : RES < >

The format in the manual is:

:SG sHH#
So, no muinutes, just hours.

Response should be 1

A patch for all the above is attached. I tested it and it is working.
6 years 8 months ago #18036
Attachments:

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

Thanks, can you please submit the above as Pull-Request on Github?
6 years 8 months ago #18047

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

  • Posts: 322
  • Thank you received: 31
I know git fairly well, but I am new to github.

Do you have any guidance on what I need to do to reach the stage where I can create a pull request?

Do I just fork the project on github, then pull from there, and push my changes to it?

Do you have a link for a "how to contribute" thing?
Last edit: 6 years 8 months ago by Khalid.
6 years 8 months ago #18062

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

  • Posts: 90
  • Thank you received: 37
Here it is a short description how to create Github PR for INDI:
github.com/indilib/indi/#how-to-create-github-pull-request-pr
The following user(s) said Thank You: Khalid
6 years 8 months ago #18078

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

  • Posts: 322
  • Thank you received: 31
Thanks!

Done, and committed.
6 years 8 months ago #18116

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

Time to create page: 0.324 seconds