Differences

This shows you the differences between two versions of the page.

--- obs:123 [2009/03/20 19:57] – experience from compilation rtopera2 mates
+++ obs:123 [2009/03/20 20:07] – mates
@@ Line 52: / Line 52: @@
 The operation of RTS2 may, at present, appear chaotic to the responsible CAHA staff, especially in case of GRB alerts. We believe that care should be taken to inform people around about the actions the telescope is performing in a simple and accessible way.
-==== EPIX database ====
+==== EPICS database ====
 CAHA maintains a database of all available information (meteo/ccd info/telescope info/etc.) Practically anything can be taken there. Most importantly the imaging CCD properties and conditions, which cannot be taken with any //info// command on the command line.
+=== Update:  ===
+This is still a piece of magic for us. However, seemingly this may be the key to get a real grip to the telescope with RTS2. The calls provided to us for managing the CCD camera are in fact actually EPICS wrappers.
 ===== Telescope control model =====
@@ Line 64: / Line 68: @@
 ==== Telescope ====
-There is an GUI for the telescope.
+The telescope is controlled with the computer tecs12. To get the graphical interface go for
 ''ssh tecs@tecs12''
@@ Line 82: / Line 86: @@
   - Manage the dome with the pull-down ''dome'', ''auto'' means to follow the telescope.
+=== scripting commands ===
+The following scripting commands are executed at ''ultra2''.
+From what I have seen they are all scripts which can be studied (and not really used literally). The level of support of programs based on what has been found inside is, however, likely to be different than if we use them as they are. On the other hand, connecting rts2 to epics would bring a serious simplification.
-These are commands to the mount and focuser. They are generally blocking commands which end when the requested action is finished. They return a single numeric value on a line to determine the exit status. (//We are missing examples of the output of each command at this moment.//)  The dome is entirely integrated with the telescope, there is no need to take care of it.
+They are generally blocking commands which end when the requested action is finished. They return a single numeric value on a line to determine the exit status. (//We are missing examples of the output of each command at this moment.//)  The dome is entirely integrated with the telescope, there is no need to take care of it.
 As I (mates) understood, this set of commands, although old as the others, has been recently revisited by Ulli Thiele when the telescope has been repaired and could, theoretically, be retouched if there are some issues. But we should not expect Ulli or anybody else do much effort here.