Observatory automation
The Observatory
automation is based on ASCOM architecture. Three programs
compliant to ASCOM directives have been written:
- A
Dome driver, derived from the ASCOM Dome Simulator. A first version was
using the PC Parallel Port the second version is based on a USB to IO
module.
The first version is
no more supported. The second one is described here, the description
comprise software and hardware implementation
- 'Ascom
Host Server' allowing the remote control of the observatory from home
through an Ethernet link.
The freeware
programs are available at the following link: Download
page
Miscellaneous
programs can be run on the Home computer to control the Dome, Telescope
including the Focuser and the Camera, the Ascom Client acts as a hub for
these programs. The number of programs connected to the Ascom Client is
not limited.
The software
architecture is given here.
All the
communications for the remote control and Internet access share the
Ethernet Link between home and observatory, so this Ethernet cable with the
electric main supply cable are the unique cables between home and
observatory.
All the Home computer
programs call the Ascom Client to transmit orders and receive status
to/from the Ascom Host Server running on the
Observatory
computer. The Ascom Host Server dispatches the commands to the relevant
drivers: telescope, focuser, dome.
In this way the
programs run at home as they were running on the observatory computer.
You do not need specific programs like NetOp,
PCAnywhere or
the 'Remote Control' feature provided by Windows XP pro.
SBIG provides, in the
CCDOPS5 package, a camera server named ESrvWin.exe running on the
Observatory computer. This server is called remotely with Maxim DL
software via Ethernet. All commands and status related to the camera
are sent/received through this server independently of the Ascom Client and
Ascom Host Server.
This server is
limited to camera command and status, Maxim DL will use the Ascom
Client to communicate with the Telescope, Focuser and Dome.
At the
observatory, the Ascom Host Server acts also as hub for different
programs, the Host Server is also able to communicate to different Ascom Clients running
on different computers connected to the same Ethernet link.
It's useful to
run also an ASCOM POTH at the observatory, indeed this POTH will act as
a hub for the observatory programs.
The Ascom Client and
Host Server have been written to cope my hardware configuration
comprising and could be extended to other configurations:
- Dome
with Azimuth Motors and Sensor (Technical Innovations - Home Dome
HD-6S), manual shutter.
The Dome is
controlled with the Parallel Port of a PC by an homemade interface and
the Dome Driver
derived
from the ASCOM DomeSimulator.
The Dome
system supports the following functions:
Goto and Sync to
azimuth
Park and
Find Home
- Telescope
LX200GPS with electric focuser (relative), other focusers are not
implemented.
- Camera
SBIG ST7 controlled with Maxim DL
The
development of Ascom Client and Ascom Host Server has been done on the
assumption that the observatory will be setup before launching the Ascom Client.
The setup
consists in:
- Openning
the dome shutter (I have no motor for this operation).
- Turn
on dome control hardware.
- Turning
on telescope and camera.
- Lauching
observatory computer programs
camera server
ESrvWin.exe
ASCOM
POTH program and relevant drivers (telescope, dome, focuser)
Ascom
Host Server
Planetarium
program
- 'Sync-ing'
telescope on the sky, (should be quick if scope well parked at
preceding session)
- Maxim
DL at observatory has to be shut down before launching it at home.
ESrvWin.exe does not support concurrent clients.
Planetarium program
at observatory will call ASCOM Poth and can run in parallel with a
planetarium program at home.
Software configuration drawing