My setup:
Ubuntu 20.04 x86_64-little_endian-lp64
KStars: 3.4.1
INDI Library: 1.9.9
Astro-Electronic FS-2: 1.26 (1.21 same Problem)
indi_lx200fs2 Vers. 2.2

I have been using a FS-2 controlled German Equatorial Mount for about 2 years without any problems. INDIlib was 1.8.5.

After updating INDI to 1.9.8 or 1.9.9 (fresh from Jasems ppa) I am not able to do a SYNC to a specific position picked out from the KStars Star map with the right button of the mouse.
The desired position is displaced for a (very) brief moment and after the next poll the telescope again seems to point to somewhere on the sky.
At this point it looks like a mount with wrong geographic coordinates and/or wrong time.
But the FS-2 doesn't know anything from time and coordinates. It took coordinates from a SYNC and then only counts pulses for the stepper drives.

SYNCing with the telescopes hand box works. Coordinates in the hand box are the same as displayed on the star map.
But slewing from this initial position to another object fails with moving in a totally wrong direction. I had to stop the mount with the button in the INDI Tab.
From INDI Tab I can also slew the mount in an arbitrary direction.
Again, SYNCing via mouse from the star map fails in the way described.
All other components (DSLR, ZWOASI GuidingCam, Focuser and Dome) work flawlessly.

I can rule out the following things:
- connection from computer to mount (I can access the serial interface for reading and writing, also with external tools like PuTTY)
- the FS-2 itself (from a Win10 Notebook with GUIDE 9.1 I can operate without any problems while SYNC and SLEW)


I have been searching around for a many hours, but I am no closer to a solution. Any advice is welcome.

Below there are some lines out of the INDI log for clarification:
0 - prerequisites (Data are OK)
...
DEBUG 15.862916 sec : Configuration successfully saved for GEOGRAPHIC_COORD.
INFO 15.863006 sec : Observer location updated: Latitude 51:06:09.0 (51.10) Longitude 12:57:38.9 (12.96)
...

1 - impossible SYNCING
...
SCOPE 377.706308 sec : CMD <:GR#> arbitrary wrong coordinates
SCOPE 377.761091 sec : RES <15:47:14>
SCOPE 377.761185 sec : VAL [15.7872]
SCOPE 377.761205 sec : CMD <:GD#>
SCOPE 377.873140 sec : RES <-30�22:09>
SCOPE 377.873225 sec : VAL [-30.3692]
SCOPE 378.210166 sec : <setObjectRA> set coordinates to SYNC from KStars map (values are exactly those which I intend to)
SCOPE 378.210294 sec : CMD <:Sr15:05:22#>
SCOPE 378.305511 sec : CMD <:Sr15:05:22#> successful.
SCOPE 378.305869 sec : <setObjectDEC>
SCOPE 378.305900 sec : CMD <:Sd-33*09:22#>
SCOPE 378.417098 sec : CMD <:Sd-33*09:22#> successful.
SCOPE 378.417195 sec : <Sync> do the SYNC
SCOPE 378.417212 sec : CMD <:CM#>
SCOPE 378.561058 sec : RES <>
INFO 378.571360 sec : Synchronization successful. --> unfortunately not :-(
SCOPE 378.873650 sec : CMD <:GR#> again seemingly arbitrary values, but others!
SCOPE 378.993138 sec : RES <05:05:04>
SCOPE 378.993241 sec : VAL [5.08444]
SCOPE 378.993265 sec : CMD <:GD#>
SCOPE 379.105091 sec : RES <+03�09:31>
SCOPE 379.105236 sec : VAL [3.15861]
...


2 - behavior after an external hand box SYNC
...
SCOPE 60.517823 sec : CMD <:GR#> the initial position after a SYNC with the hand box
SCOPE 60.573409 sec : RES <14:52:44>
SCOPE 60.573581 sec : VAL [14.8789]
SCOPE 60.573623 sec : CMD <:GD#>
SCOPE 60.686063 sec : RES <-16�02:09>
SCOPE 60.686162 sec : VAL [-16.0358]
SCOPE 60.686254 sec : <setObjectRA> set coordinates to slew to a desired object east of the actual position
SCOPE 60.686276 sec : CMD <:Sr15:36:48#>
SCOPE 60.796586 sec : CMD <:Sr15:36:48#> successful.
SCOPE 60.796852 sec : <setObjectDEC>
SCOPE 60.796879 sec : CMD <:Sd-14*51:55#>
SCOPE 60.925680 sec : CMD <:Sd-14*51:55#> successful.
SCOPE 60.925748 sec : <Slew> start slewing to target object
SCOPE 60.925760 sec : CMD <:MS#>
SCOPE 61.036416 sec : RES <0> <0>...slew is possible
INFO 61.036555 sec : Slewing to RA: 15:36:48 - DEC: -14:51:55
SCOPE 61.686960 sec : CMD <:GR#>
SCOPE 61.772489 sec : RES <14:52:28>
SCOPE 61.772702 sec : VAL [14.8744]
SCOPE 61.772749 sec : CMD <:GD#>
SCOPE 61.884466 sec : RES <-15�49:39>
SCOPE 61.884584 sec : VAL [-15.8275]
SCOPE 62.885124 sec : CMD <:GR#>
SCOPE 62.924471 sec : RES <14:49:50>
SCOPE 62.924582 sec : VAL [14.8306]
SCOPE 62.924600 sec : CMD <:GD#>
SCOPE 63.037705 sec : RES <-14�54:54>
SCOPE 63.037807 sec : VAL [-14.915]
... incorrect slewing to northwest
SCOPE 69.876160 sec : CMD <:GR#>
SCOPE 69.931263 sec : RES <14:27:34>
SCOPE 69.931350 sec : VAL [14.4594]
SCOPE 69.931373 sec : CMD <:GD#>
SCOPE 70.043369 sec : RES <-09�20:54>
SCOPE 70.043538 sec : VAL [-9.34833]
SCOPE 70.143147 sec : <abortSlew> stop slewing manually
SCOPE 70.143221 sec : CMD <:Q#>
INFO 70.143295 sec : Slew/Track aborted.
SCOPE 71.044634 sec : CMD <:GR#>
SCOPE 71.099285 sec : RES <14:24:22>
SCOPE 71.099463 sec : VAL [14.4061]
SCOPE 71.099505 sec : CMD <:GD#>
SCOPE 71.211268 sec : RES <-08�45:17>
SCOPE 71.211371 sec : VAL [-8.75472]
...

Read More...

Thomas Berthold created a new topic ' ALccd-QHY 5III 178 color' in the forum. 7 years ago

Hi,
is the ALccd-QHY 5III series supported by INDI?
There's no hint in the "Devices" list for this series from QHY.

Read More...