I have a Celestron Nexstar 102SLT and I'm having an issue with skysafari 6 Plus in OSX. No matter what I try, the telescope control panel doesn't show properly. It is there, but the options (connect, goto, align...) stay inactive. It's weird because the telescope connects and I can even slew it via hotkeys. Also, the reticle of the scope doesn't show in the main panel so, I really don't know where it's pointing at.
I have tried uninstalling the app and tried to delete every single file related to the app (prefs and stuff like that) but nothing seems to work. I'm convinced it is something about the settings because it worked like a charm a few days ago until I changed something that broke it, but I don't know what.
Help would be very much appreciated.
Thanks.
Date
Votes
10 comments
-
Bill Tschumy If you choose the Demo scope as the scope type, are the buttons enabled correctly for that?
-
Bill Tschumy I also assume you have chosen "Celestron Nexstar GPS/SLT/SE" as the scope type?
-
Argimiro Viloria Yes, I chose the correct scope type.
I also tried choosing Celestron wifi to try with my SkyQ Link.
And yes, I have tried the demo scope as well, always with the same result. The panel says "connecting..." and stays like that forever, with the rest of the options unavailable (goto, align...) And as I said, the connection seems to be done because I can slew the scope via the menu or hotkeys, but the pointer indicating the position of the scope is not visible
-
Bill Tschumy I'm really surprised that restarting the app doesn't fix this. It looks like the code thinks it is still connecting to a mount. It is possible a previous attempt to connect never got cleared correctly. Restarting the app should clear that state but if you have reinstalled that app, then obviously it didn't.
After restarting, the very first time you show the panel, is it correct? It could also be some problem that after a successful connect the "connecting" state isn't cleared. That said, I've done lots of connect/disconnect from a mount like yours and have never seen this.
-
Argimiro Viloria I tried to find some info regarding this issue in this and other forums, but didn't find anything so I suppose it's a really weird problem.
I'm quite convinced it's, as you said, that some trace of a previous connection didn't get cleared correctly. That's why I'm trying to do a clean install of the software but don't get it. Even deleting every file I could find related to the app, when I download it from the app store and install it again, as soon as I open it, the app remembers my location and other preferences so, it's obvious I need to delete some other files which I can't find.
-
Bill Tschumy The state of the connection is never stored. Deleting files or reinstalling won't change that.
Please confirm, do you see the the very first time you bring up the Scope panel after restarting the app? Bring the panel up via the Telescope > Scope Control Panel. This shows it without trying to connect. If you are showing the panel automatically by trying to connect (Telescope > Connect) then I would expect you to see this, but it should change to "Disconnect" after the connection has been made.
-
Argimiro Viloria If I start the program and go to Telescope>Scope Control Panel, I see the panel as it should, with "connect" in blue and waiting. Once I click on connect, it goes to the state I sent in the previous message and stays like that.
-
Bill Tschumy I'm going to convert this into a support ticket because this is probably not of general interest.
Please respond to the following questions using the support ticket email you should get.
And you say this happens even with the Demo scope? The button is blue and says "Connect", but after connecting it never changes to "Disconnect"? Do you hear the ding sound after it connects?
What macOS version are you on?
-
Argimiro Viloria Thanks Bill.
I'll follow via support.It is as you said...it happens even with the demo. First it is blue "Connect" and once I click on it, it never changes to disconnect.
I hear the ding when the connection is made and even the sound effect when I slew it using cmd+4
I'm on a macbook pro with OSX High Sierra
-
Bill Tschumy This problem has been fixed in SS 6.1. It happened if you had less than 3 FOV indicators.
Please sign in to leave a comment.