PHOENIX SOFTWARE

Go to the Table of Contents .

INTRODUCTION

 This note describes the software provided at Parkes and Mopra in support of the Phoenix program.

The software complies with the design document External Interface Design Document (May 18, 1994), and its revisions (June 20, July 29, October 29 and November 23).

REQUIREMENTS

 CSIRO will provide two serial lines - one expecting action commands, the other producing a stream of monitor data. The two lines connect to the CSIRO system at a terminal server; the line characteristics are currently set to 9600 baud.

The command line connects to a CSIRO task, SETIOBS. The monitor line connects to a CSIRO task, SETIMON.

To the outside world (SETI) the Parkes version of these tasks is the same as the MOPRA version.

The root directory is OBS$1:[SETI] at Parkes, and OBS$0:[SETI] at Mopra. These will be referred to generically as OBS$x: in the text.

USER GUIDE

 Both tasks will maintain logs of all the messages received from or sent to the SETI system.
These files are kept in the area user1:[observer.seti.log] at Parkes, and OBS$0:[SETI.LOG] at Mopra. The files are called setimon.log and setiobs.log; a new file is opened each time the task is started.

The local implementation of the environment is given in the files SETIMON.DEF and SETIOBS.DEF in the OBS$x:[SETI.WORK] area. (These are listed in appendix A).

In addition, a log is maintained in the file at$log:sngl_command.log of all the messages sent to the control system.

Setiobs

To start the task interactively:
$ set default obs$x:[seti.work]
$ run/nodebug obs$x:[seti.work]setiobs 




Setiobs running on MOPRA:: should not need to be 
restarted, as this will be done automatically by BIGBROTHER, should the 
process stop at any time.


There may be instances when SETIOBS needs to be stopped for a period of time
and hence it is desirable to disable the automatic restart function supplied
by the BIGBROTHER program.


This is done with the command

 $ stop_setiobs 

from the OBSERVER account.


To restart SETIOBS and reenable the BIGBROTHER facility after a
stop_setiobs command use

 $ start_setiobs 

from the OBSERVER account.









Once started the task will receive commands from the SETI system and pass 
them to the relevant CSIRO subsystem.


All incoming messages will be displayed on the task's screen;  they will
also be logged;  they will be put into global common so that SETIOBS
can be checked out remotely.


Every message from SETI will elicit a response.  The responses are logged
and displayed.


A `QUIT' message from SETI will kill setiobs.


A `MON_QUIT' message will kill setimon 
(see below).


Local specific information is stored in the file SETIOBS.DEF in
OBS$x:[SETI.WORK]


Initialisation - MOPRA
 
When SETIOBS starts it puts the receiver and synthesiser in a standard setting:








Safety

An activity monitor has been placed on the Mopra version.  A warning is
sent back to Parkes if there is no activity in a five minute interval.
The antenna will be stowed if there is no activity in a ten minute
interval.


Setimon will show the warning/stow condition in the second record.
(Data2 - the status word will switch to 000000000001 on warning,
and 000000000999 on stow).




Debug Mode

If the terminal name (in setiobs.def) is set to TEST then the
SETI link is cut and the terminal keyboard becomes the input source.


Finer control of the debug modes is available in the file
obs$x:[seti.work]setiobs.def - one can disable entirely the
antenna drive (ie, one can test SETIOBS without requiring the antenna),
or one can choose to drive just the ME (Parkes only).


Setimon

To start the task interactively: 

 $ run/nodebug obs$x:[seti.work]setimon 




Setimon running on MOPRA:: should not need to be 
restarted, as this will be done automatically by BIGBROTHER, should the 
process stop at any time.



This task will send two monitor records back to SETI at regular intervals.
The period is currently set to 10 secs.  It can be changed.


Every record is logged, as is the rare message from setiobs.




Data format


c        We send two strings every ten seconds, containing:
c
c  "data1" .. ID of first message
c   time      F8.1      UTC in hhmmss.s notation
c   pwr       I1        UPS/MAINS flag [1 .. mains;  0 .. UPS]
c   alloc     I1        1 .. allocated;  0 .. not alloc
c   wrap      I1        1 .. NORTH;  2 .. SOUTH
c   mode      I1        0/2/4/6/8 .. azel/hadec/ra-dec, apparent,
c                       J, B
c   ra        F9.2      ra/dec as specified by mode, except that
c                       mode 0 wants ha/dec;
c   dec       F9.1      hhmmss and ddmmss format
c   az        F8.4      az, decimal degrees
c   za        F7.4      za, decimal degrees
c   trkerr    F8.4      great-circle tracking err; decimal
c                       degrees
c   drives    I1        0/1/2/3/4/5/6 : stowed/parked/idle/
c                                       slewing/tracking/
c                                       stowing/focussing

c  "data2"    ID of second string
c   focus     F6.1      focus setting, mm
c   fdang     F5.1      position angle, feed E-vector. degrees
c   windsp    I3        wind speed, km/hr
c   windir    I3        wind dir,   degrees
c   tamb      F5.1      ambient temp, degrees C
c   tcryo     F5.1      20 K stage;  degrees, K
c   noise     I1        Noise diode; 0..OFF; 1..ON
c   rfifok    I1        RF LOs OK ? 0..OK; 1..NO
c   lsband    I1        1..Lband; 2..Sband
c   cstat     I12       coord+ME+feed+servo status word
c   rffreq    F12.7     topocentric; MHz
c   secure    I4        0.. OK; 1..Alarm
c






Communication with SETIMON

Information and commands can be sent to SETIMON through the shared common; 
we can use the SETIOBS communication channel to get information to SETIMON
by prefixing `MON_' to the message.


The only commands recognised at this stage:



 mon_interval secs

 This will change the reporting interval to secs
     (secs must be an integer in the range 3 < sec
< 60)

 mon_quit

 This will cause SETIMON to exit gracefully

 mon_timeout 

 Setimon will issue an INACTIVITY warning

 mon_stow

 The inactivity-induced STOW message

 mon_clear

Clears the inactivity warning message




Debug Mode

If the terminal name (in setimon.def) is set to TEST then the SETI
link is cut and the output is directed to the local screen.

 
Setiview
 
This is a utility that allows remote access to the global common so that
a check can be made on the operation of SETIOBS and SETIMON:  all the
traffic from the SETI system and the SETIMON reports will be displayed.


To start the task at Mopra:

 $ setiview 



Elsewhere:

 $ run/nodebug obs$x:[seti.work]setiview 




 
Read_log
 
This allows any of the setimon or setiobs files to be read.


To run:

 $ run obs$:[seti.work]read_log 


The program will prompt for the following information:





  > Setiobs [obs] or Setimon [mon] ? : 

 (answer obs or mon)

  > Enter the RELATIVE file version number [0,-1,...] :

 (0 is the current (open) file, -1 is the most recent previous version, 
     etc., following the standard VAX practice.)





The task will display 20 lines of the log at a time. 

 <cr>  will advance one screenful. 



To advance in larger blocks, enter 

 > j n  

where  n  is the number of lines to skip. 

eg.  > j 200  will skip the next 200 lines.



 
Scan_log
 
This task scans the specified file, extracting the highlights - errors and 
changes in drive status.


File selection is just as for  read_log.


To run:

 $ run obs$:[seti.work]scan_log 







CODE MANAGEMENT

The code is maintained using the DEC Code Management System (CMS).
The library is in OBS$x:[seti.code.cms], with a plain text copy
of the current version in [seti.code.ref]


The executables are in [seti.work]





 
APPENDIX A- The Environment Files
 


Parkes


 setiobs.def 


TEST:
PARKES
obs$1:[seti.work]marconi.def
user1:[observer.seti.log]setiobs.log
ENABLE
ME






 line 1 : Terminal line from vax (terminal server) to the seti HP

 line 2 : Observatory identifier

 line 3 : File with marconi information

 line 4 : Log file

 line 5 : Antenna Drive ENABLE/DISABLE

 line 6 : Parkes specific : config .. ME;  64M;  ALL




Mopra


 setiobs.def 


mopra_setiA_port:
MOPRA
obs$0:[marconi.work]marconi.def
obs$0:[seti.log]setiobs.log
ENABLE
ALL






 line 1 : Terminal line from vax (terminal server) to the seti HP.

 If set to TEST, the SETI HP port is redirected to the 
     keyboard for debugging purposes.

 line 2 : Observatory identifier

 line 3 : File with marconi information

 line 4 : Log file

 line 5 : Drive ENABLE or DISABLE

 line 6 : PKS specific - ME/64M/ALL






 setimon.def 


MOPRA_setib_port:
obs$0:[seti.log]setimon.log






 line 1 : terminal line name;  if set to TEST, setimon will take

 its input from stdin.







 Return to SETI home page



 Return to the Australia Telescope Mopra Observatory home page





M Kesteven & E Troup (AT reference : AT/39.1/008)


Modified: nmckay (9-OCT-1995)