Telescope Control works only if I run Stellarium 0.21.1

[ArnoldBrody]

I have three versions of Stellarium (0.21.1, 0.21.2 and 0.22.0) installed on my ASUS VivoBook 17 running Windows 11 Processor Intel(R) Pentium(R) Silver N5000 CPU @ 1.10GHz 1.10 GHz Installed RAM 8.00 GB (7.83 GB usable) System type 64-bit operating system, x64-based processor

I tried controlling the AVX with Stel 0.22.0. I had to change COM3 to COM4 and then it was able to connect. Or so it said. But I never saw my telescope's indicator in Stellarium when viewing the same area my scope was pointing to. If I did a search for the name of my telescope connection (Arnies AVX) or asked to slew to a star, the program crashed.

I launched Stel 0.21.2. It connected to my AVX on start-up. But still no indicator on the screen. If I try to slew the scope to a target, Stel crashes.

I launched Stel 0.21.1. It connected to my AVX on start-up and worked perfectly. The indicator appears, I can search for my telescope connection, and I can slew to targets (quite accurately).

Please let me know if more information is needed. Thank you.

[github-actions[bot]]

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

[gzotti]

Not that I could fix this, but it could help if you can disclose the protocol "Arnies AVX" is using. Is that a LX200 compatible?

[ArnoldBrody]

Here are the configuration settings for my telescope connection (in case this answers your question).

For Stellarium Versions 0.21.1, 0.21.2, 0.22.0 (all the same)

Telescopes Controlled

1, Type = Local, Stellarium, Name = Arnies AXV

Configuration of Arnies AVX

Telescope controlled by: Stellarium, directly through a serial port

Telescope Properties Name: Arnies AVX Connection delay: 0.50s Coordinate system: Equinox of the date (JNow) (checked) Start/connect at startup

Device settings Serial port: COM4 Device model: Celestron NexStar (compatible)

User interface settings (not checked) Use field of view indicators

Options tab GUI (checked all three) Show Telescope labels, Show telescope reticles, Show field of view indicators

About tab *Telescope Control plug-in *Version 0.4.2

On Thu, 5 May 2022 at 11:32, Georg Zotti @.***> wrote:

Not that I could fix this, but it could help if you can disclose the protocol "Arnies AVX" is using. Is that a LX200 compatible?

— Reply to this email directly, view it on GitHub https://github.com/Stellarium/stellarium/issues/2434#issuecomment-1118705081, or unsubscribe https://github.com/notifications/unsubscribe-auth/ASIOJ52AKNSXMVBXYZRYVN3VIPSZ3ANCNFSM5VFNDXCQ . You are receiving this because you authored the thread.Message ID: @.***>

[alex-w]

Could you try windowed mode?

[aargeebee]

I just purchased a Avus laptop (same one as ArnoldBrody) just to control a telescope in the field, and have spent 2 days tearing hair out trying to get Stellarium to recognise my Dob8 Goto. I have had Stellarium 0.21.2 on an Avus Desktop PC for a few months and it works perfectly. Same hardware connected to new Avus laptop simply wont work on latest Stellarium. I installed Stellarium 0.21.1. into laptop and scope was connected on first try.. Very happy I saw this report by Arnold.. Why this bug should exist is beyond me !!

[gzotti]

Have you seen the other issue reports about the TelescopeControl plugin? Have you tried the Qt5-based build of V1.2 already? If not, or if this still does not work, please attach the Logfile which we are always requesting. Somebody out there with a GOTO telescope and the same problem may hopefully eventually look into it.

[github-actions[bot]]

This is a good task for the community to participate in the contribution into Stellarium. Who wants to help us?

[aargeebee]

I just found the qt5 v1.2 and the scope was recognised by it and works fine... so I guess that would indicate something to do with qt6..
Q.. why are previous versions not available on the Stellarium website? Had to go looking for it on the web.

[aargeebee]

.... downloaded from SourceForge

[gzotti]

[gzotti]

Several Qt6/TelescopeControl issues have been solved before 23.3. We tentatively close this as member of a large group of related issue reports for now. In case of re-occurrence of this issue in V23.3, please create a new report with very clear description of circumstances.