Transcript ACS_2007_aries21

Developing the control system for the 40m
OAN radiotelescope with ACS
Observatorio Astronómico Nacional
P. de Vicente, Rubén Bolaño, Laura Barbas
January 2007
Developing the control system for the 40m
OAN radiotelescope with ACS
The OAN has four sites in Spain
40m RT. Project status
Time delays due to problems with contractors:
Structure
Servos
Surface
Mirrors
40m RT. Current status
Main milestones already achieved
Backend equipment has been moved to the new
antenna building.
Antenna moves with handheld pannel
Surface has been adjusted with a teodolite and
measured
RMS:~ 200 µm
Measuring the surface
2007 expectations
New servosystem for the subreflector
Servosystem
Aerospace)
tests
by
the
contractor
(MT
Nasmyth mirrors installation
Cabling between receiver cabin and backends
room.
Holography receiver in the primary
Receivers in the secondary
Commissioning by OAN
The Antenna Control Unit
2 CPU's: 2 Windows XP PCs.
Windows XP + TwinCAT (real time extension)
Remotely commanded using TCP sockets.
Interface Control Document is almost finished.
ACS in the OAN
Before:
Debian Sarge
ACS 5.0.2
Compiled ACS ourselves
Now:
Debian Sarge
ACS 6.0
ACS binary distribution
ACS 6.0 on Debian
Sarge: current stable
Etch: next stable
ACS 6.0 does not compile on Etch
ACS 6.0 binary does not work on Etch.
components do not work.
Python
ACS 6.0 compiles on Sarge but requires Python
2.4. Too much effort to twikle the OS.
New Pcs require a new kernel => Debian Etch.
Modus operandi (devices)
Serial
ACS
Client
ACS
Component
Library
(Not ACS)
Ethernet
GPIB
Java Client examples
Python Qt example
Micro IOC
Used to monitor and control analog signals from
receivers
Microprocessor running Debian Sarge
Delivered with ACS 4.1 but we installed ACS 5.0
Created drivers ourselves
Component runs inside the Micro IOC
Modus operandi
(abstract components)
ACS
Client
ACS
Component
Library
(Not ACS)
Antenna control schematics
Astronomer
Client
CORBA
CORBA
Antenna
Component
Engineer
Client
CORBA
ACU
Component
Sockets
Antenna control simulator
RT components overview
Based on APEX design
Very difficult to adapt it to our needs.
Some components:
Implemented
(ScanObs)
in
a
totally
different
way:
Reused part of the code (FitsWriter, Interactive
client), and complete libraries (MBFITS)
Components relationship
Uses
Uses
Ephemeris
Activates/Starts/Stops
Commands
Client
Commands
Observing
engine
Antenna
Archiving
channel
Uses
Scan
Stops
/Starts
Creates
FITS data
writer
Sends data
Instruments
Uses
Code contribution
Code contribution would be a benefit for everybody
but ...
Reuse is not easy and can be a nightmare
Code reusage works if:
generalization
documentation
time
centralized server