Hello Mat,

Sorry for the late answer. You give me hope and I will do more experiments with my Star Discovery mount.

Last week I could prove that the issue is not caused by my guiding camera, PHD2 installation or mechanical setup. I used my optics with an equatorial mount and could successfully guide. Before that I was not fully sure if the camera is good enough for guiding (a Raspberry Pi HQ camera with my self made driver github.com/scriptorron/indi_pylibcamera). Attached is a picture of my equipment after a frosty observation night. The guiding scope is a Svbony with 190mm focal length, the main OTA is a Newtonian with 750mm focal length. Both have their own Pi with HQ camera. The Pi on the guiding scope operates the guiding camera, runs PHD2 and sends the guiding commands over WIFI to the Pi on the main OTA. The Pi on the main OTA runs KStars, operates the main camera and drives the mount. That setup sounds strange but it was the only which avoids sending camera pictures from one Pi to the other (that would be too slow). Controlled is everything using remote desktop (xrdp) from a Linux laptop in the same WIFI. I can do this from the couch and do not stay connected all the time.

As mentioned guiding works with the same optics, same cameras and same Pis on my equatorial mount but not on the StarDiscovery mount (www.astroshop.de/azimutal-mit-goto/skywa...an-wifi-goto/p,57362). The only differences on the StarDiscovery setup are:

• different mount (of corse),
• different mount driver (indi_synscan_telescope and SynScan app on Android, connect in same WIFI).