Stellarium won't work with INDIGO mount if another client is connected to the mount

[toriqo]

Expected Behaviour

Use the mount (slew) in Stellarium.

Actual Behaviour

Running an INDIGO server on a computer attached to the telescope. After starting the INDIGO server, Stellarium connects to the mount just fine, allowing me to control it. But if I launch another client (KStars or AstroTelescope) Stellarium will stop working with my mount (also the mounts reticle/indicator disappears) switching to a status of Connecting...

The same goes if after starting the INDIGO server I connect to it with a different client first (KStars or AstroTelescope); Stellarium won't connect anymore (or just for a brief moment - and if I press CMD+1 fast enough it also issues a slew command which the mount executes - then reverts to Connecting...) and just displays Connecting...

Steps to reproduce

Connect Stellarium to a mount on an INDIGO server, then launch another client (KStars or AstroTelescope), connecting it to the same mount. OR Connect to a mount on an INDIGO server with a different client (KStars or AstroTelescope) then try connecting Stellarium to the same mount on the same server.

System

• Stellarium version: 0.20.2
• Operating system: macOS Catalina 10.15.5
• Graphics Card: Radeon Pro 560X and Intel UHD Graphics 630 1536 MB
• Screen type (if applicable): 1920x1200 HighDPI scaled

Logfile

log.txt

[github-actions[bot]]

Thanks for adding your first issue to Stellarium. If you have questions, please do not hesitate to contact us.

[gzotti]

Related to #825 or #1085?

[toriqo]

One of them is using an older build, the other doesn't state the build version. And they both say it's not connecting. For me it works perfectly until I connect a second client. So it might be related, not sure.

If they have the same issue as me, then I did a better job at describing the issue and how to reproduce it :)

[rumengb]

Guys, I investigated the issue a bit deeper and it looks to me that Stellarium does not filter connection requests by device. I am using Stellarium and indigo_control_panel, and stellarium goes in to this connecting state when I connect any other device like ccd camera from the control panel. No problem if no any other device is connected. So my assumption is that Connection and disconnection requests are not filtered by device and all reach Stellarium state machine regardless of the target device: I guess both:

22:12:04.844114 indigo_server: 20 ← <setSwitchVector device='Mount Simulator' name='CONNECTION' state='Busy'>
22:12:04.844128 indigo_server: 20 ← <oneSwitch name='CONNECTED'>On</oneSwitch>
22:12:04.844138 indigo_server: 20 ← <oneSwitch name='DISCONNECTED'>Off</oneSwitch>
22:12:04.844149 indigo_server: 20 ← </setSwitchVector>

and

22:18:04.836264 indigo_server: 20 ← <setSwitchVector device='ZWO ASI071MC-Cool #0' name='CONNECTION' state='Busy'>
22:18:04.836276 indigo_server: 20 ← <oneSwitch name='CONNECTED'>On</oneSwitch>
22:18:04.836286 indigo_server: 20 ← <oneSwitch name='DISCONNECTED'>Off</oneSwitch>
22:18:04.836297 indigo_server: 20 ← </setSwitchVector>

are treated the same way regardless of the fact that the first one targets mount "Mount Simulator" and the second ccd "ZWO ASI071MC-Cool #0"... I guess that is why stellarium looses state when another client is connected...

Rumen

[alex-w]

Please check the fresh version (development snapshot) of Stellarium: https://github.com/Stellarium/stellarium-data/releases/tag/weekly-snapshot