EQASCOM_Run is a very basic ASCOM client intended to provide a permanent client for EQASCOM thereby ensuring the EQASCOM continues to run even it other more complex client apps such as guiding/planetarium are closed (or crash). Those with dedicated mount control PCs may wish to add EQASCOM_Run to the startup menu and leave it to windows to terminate on close down. Those without dedicated PCs may also opt to use EQASCOM_Run but may want to initiate it manually.
It can be all too easy to accidentally shut down the EQASCOM interface by closing the last connected client application. The mount itself is unaffected by EQASCOM closure and will continue tracking allowing you to re-start a client app. EQASCOM will then pick up where you left off. However during the “down period” any active limit protection will have been compromised. You also lose unsaved alignment data etc.
If you set it to run automatically on windows start-up, it will then keep looking for the mount. Once it finds the mount, it will connect automatically and the EQASCOM UI will appear. It is not necessary to close EQASCOM run explicitly. Just let windows do that when it shuts down. In this way, you can open and close other clients without any concerns about accidentally shutting down EQASCOM.
An alternative way to get EQASCOM to run permanently is to use the “start EQASCOM” script that ships with EQASCOM. This efficiently tricks EQASCOM by changing its client count to think there is already a client present. If started this way the only way to stop EQASCOM is via the “Kill” script let windows do it on shutdown (or via the task manager).
Strictly speaking the script approach is a violation of ASCOM compliance which requires that drivers should not run standalone. EQASCOM_Run on the other hand is a legitimate ASCOM implementation.
The latest versions can be found in the files folder at