SGP 16 minutes Establishing Orbit

Sequence Generator
1

I am running the latest version of SGP. My equipment is a Paramount MYT (running The Sky X), Ultimate Power Box (running Pegasus Unity software). The PC is an Intel NUC mounted on the scope.

After not running operating the scope for six months while we built a new observatory I went to start things up today. My usual routine is to boot the Unity s/w followed by The Sky X then SGP and finally PHD2.

When I opened SGP the program got to “Establishing orbit” where it hung up for 16 minutes. I tried all of the usually cures (rebooting the PC, Reinstalling SGP, etc.) and reopened the program a dozen or so times. In each case it did ultimately open but only after at least 16 minutes. I followed the suggestions in your “SGPro will not start” link: Ascom is properly installed, the default reopening of the last sequence has been disabled and i renamed the profile folder all without success.

I have two log files which I tried to upload but received a message that there are not of a type that is acceptable for upload—not sure why that would be.

Thanks for your help.

2

You’ll want to upload the SGP log file from when this happens. Start SGP, wait 16 mintues for it to start, then go to the Help menu and “Report a problem”. You can tell it to upload the current log file.
Are you saying you did that and that’s when you got the “not a type that is acceptable” message? If you, you’ll have to put them on a Google drive, on Dropbox, or somewhere else and then attach the link.

3

I’m not at the observatory so I cannot so I cannot go the “report a problem” route.

I have stored two files with the .log extension on my iPad and just uploaded them to Google drive. The links are below:

I’ve never done this before so if the process has corrupted the log files I’d appreciate if some could let me know

4

The delay is due to SGP looking for the PegasusAstro switch. Someone else had an (almost?) identical problem recently so you may want to search prior posts.
I believe the most recent beta of SGP has something that may help with this.

5

Eric thanks for the suggestion. I see the log entires re “PegasusAstro Switch 1” and “PegasusAstro Switch 2”. I am not sure whether the 1 and 2 refer to switch numbers generated in the software or physical devices. FYI my physical device is an Ultimate Power Box v3.

As suggested I have searched Pegasus Switch which produces a number of threads. None of them appear to be precisely on point. Do you recall how recent the post was?

6

Was on my phone when I responded the first time so no easy way to search.
Look at This version is really very slow at startup about 20 minutes - Premium Support - Main Sequence Software.

7

Sorry for the delay… we were out most of the last week.

As Eric mentioned, the delay is dues to a failure to instantiate and connect to the Pegasus suite (looks to be all of them). As an example:

ASCOM Switch: Error, could not instantiate switch for PegasusAstro PPB! : Retrieving the COM class factory for component with CLSID

And so on. That particular error with Retrieving the COM class factory for component with CLSID indicates that the driver install is corrupt and Windows does not know how to make those kinds of drivers. Unfortunately, there are many ways this can happen…

Can we start with your setup / intent? One of the ways this can happen is via a partial uninstall. Are you actively using this equipment? If so, is it your intent to have SGPro control it?

If you do intent to use it (i.e. it’s not old gear you’ve moved on from) the first step would a full uninstall and re-install of the latest Pegasus driver suite (not a re-install). This should effectively restore the COM link that Windows cannot find. We can go from here…