Gemini Telescope.net caused SharpCap to quit

A place to report problems and bugs in SharpCap
Forum rules
‍

If you have a problem or question, please check the FAQ to see if it already has an answer : https://www.sharpcap.co.uk/sharpcap-faqs

Please also read about Troubleshooting USB Issues before posting.

*** Please do not post license keys - please report any problems with licensing to 'admin' by private message ***

Please include the following details in any bug report:

* Version of SharpCap
* Camera and other hardware being user
* Operating system version
* Contents of the SharpCap log after the problem has occurred.
[If SharpCap crashes, please send the bug report when prompted instead of including the log]
Post Reply
MarMax
Posts: 191
Joined: Sun Sep 19, 2021 11:43 pm

Gemini Telescope.net caused SharpCap to quit

#1

Post by MarMax »

SC Version 4.1.12551, Windows 10 Mini-PC at mount

I've never had an issue with the G11G (Gemini2) and SharpCap before but last night SharpCap quit and sent the automatic report. Hopefully you received this report and I'm curious what happened. Whatever it was the mount stopped responding to both Stellarium and SharpCap just before SC quit. Since this is a first I'd like to know if you need any additional information to troubleshoot.

I'm on L5 with the Gemini2 and plan to go to Losmandy tomorrow for the L6 upgrade so this may be moot. The current L5 configuration has been running fine for months except for this one instance. I'm using Stellarium 23.2 (Qt5 version).
User avatar
admin
Site Admin
Posts: 17534
Joined: Sat Feb 11, 2017 3:52 pm
Location: Vale of the White Horse, UK
Contact:

Re: Gemini Telescope.net caused SharpCap to quit

#2

Post by admin »

Hi,

I just found the bug report and the error message from the ASCOM driver was

'Slew to outside of safety limits'

It looks like this happened while you were trying to recenter the target using the deep sky annotation, and I guess that somehow the point that you clicked on was considered dangerous by the mount driver. I can see from the report that the co-ordinates being targeted were RA=22:31:00.6,Dec=-20:42:31, but I don't have info on what the altitude/azimuth for them were at the time of the problem.

I will add some error handling around the mount movement here to make sure you just get a nice 'Failed to move mount' message or similar rather than a crash in future.

cheers,

Robin
Post Reply