Software Startup Order for Remote Observatory

[deepskyman]

Hi there, I have until now manually started up each app, however I ultimately want to operate as a remote observatory so I’m looking for confirmation and advice on this topic.

What is the correct startup order for Windows?  I run all Accessories via ASCOM Device Hub:

Pulsar 2.7m Dome (this is via an alpaca dynamic driver to ASCOM remote server running on the machine controlling the dome).

Primaluce ESATTO focuser

 

So logically startup order would appear to be:

ASCOM Device Hub - How do I get ADH to connect automatically to all devices?

Planetarium Software (Stellarium with DDM85 set to auto-connect)

Sequence - How do I get Sequence to auto connect to all devices?

 

Kind Regards

Paul

Edited December 10, 2023 by deepskyman

[MichiP]

Hi Paul,

I also operate my observatory remotely and perform the startup routine manually. I have not encountered any issues with the sequence of tasks, as long as all programs are started in an order where a certain program requires another program to be already running.

For instance, if Stellarium needs to connect to the mount, the mount should already be running to prevent an error.

My startup routine is as follows:

1. Dome
2. Autoslew
3. CCD & Filter Wheels
4. Focuser
5. Autoguider
6. FlipFlap (Cover opener)
7. Cloudwatcher
8. The Sky X
9. N.I.N.A.

You can keep everything connected. If you plan a fully automated setup, ensure that everything is connected and move the Mount and Dome to a park position.

Regards,
Michael