Hi all,

First my equipment:

-Skywatcher Synscan ALT/AZ goto mount (not GTI) with external WIFI module
-Skywatcher Evoguide ED 50 telescope
-ZWO ASI 178MC camera

All connected to Kstars-Ekos (or CcdCiel or Stellarmate, the result is the same) via raspberry PI4 - Mount connected wireless via synscan PRO app and in Ekos configured with "Synscan" driver.
Everything works fine. I make initial alignment correctly in synscan app then goto and platesolving from Kstars (or Stellarmate) which detects the pointing difference and sends the sync command to the mount...this command is not recognized by the mount which does not update its pointing coordinates and ignores the command.
All software and drivers are updated to the latest official version released by skywatcher, the mount's debug logs show no response or error messages when the sync command is sent.
the mount seems to ignore this command...
Has anyone had the same problem?

If you're using WiFI module, then just use "AZ-GTI Alt-Az WiFi" and see if this driver works better for you. We're still working on the tracking issue.

Hi Jasem,

I also tried with the "AZ-GTI Alt-Az WiFi" driver but I often got anomalous behavior from the mount (errors for unrecognized commands, loss of movement control, ecc.) From INDI documentation the correct INDI driver for my mount seems to be "Skywatcher Synscan":

(Any SkyWatcher/Orion with Synscan Handset)

indilib.org/individuals/devices/telescopes/skywatcher.html

If you are connecting over WiFi, I think it uses different command set than the synscan driver. Using synscan driver is very limiting.

Ok, i will retry "AZ-GTI Alt-Az WiFi" driver and report here the result...in this case the driver must be connect via Synscan PRO app ip address? Or directly with the wifi module ip address?

No need to connect "via synscan PRO app".

The mount and RaspPi connect directly via WiFi.

Last night I did some tests with Kstars using the "AZ-GTI Alt-Az WiFi" driver and the "Synscan alt/az" driver. Both behaved in the same way: the sync now works, the mount accepts the sync command and updates its coordinates, but often the slewing fails to bring the subject in the FOV...the mount continues to "go around" until the plate solving fails...sometimes it gets closer, sometimes less...the tracking doesn't work, the mount doesn't follow the object, even though it is active from the indi driver.
Geographic coordinates in kstars and time are correct and result aligned in indi mount driver.
These are the setup operations I performed:
-Positioning the mount in "home position" (horizontally level and facing north)
-Powering up the mount and connecting to Kstars which displays it in the correct position.
- Unparking and goto from planetarium.
- the mount moves towards the subject but the position reached is wrong by several degrees...anyway the plate solving works and brings the mount back close to the correct coordinates. At this point the various subsequent platesolving attempts to center the subject without ever succeeding completely (the subject remains in the FOV but is never centered).

This driver has tracking turned off by default.

What & Interesting..→Turn on the info button and click the target→There is a tracking check box on the target detail screen, so please check it.

I wrote a little about it on my blog, so please translate it and read it.

tstudioastronomy.blog.fc2.com/blog-entry-17.html

Hi T-studio,
I tried your setting in Kstars, but the mount still doesn't track..also the sync works but the various slewings after plate solving never center the subject correctly...the mount keeps going around it getting closer without being able to get to the center of the FOV .... I don't understand why using the "synscan" driver connected to the synscan pro app the goto and tracking work correctly but only the sync does not work ...