All commands are executed immediately. There is no notion of an active or passive field which is then activated by the operator as in the case of OBS. Commands are executed synchronously and the calling program waits for a return from the control system before continuing.
Refers to commands used for low-level actions at a system level. These commands should normally only be used by system administrators.
input device-name command-specific-input-parameters
output command-specific-output-parameters
input node-name whole/byte/nybble/bit [byte] [nybble/bit]
output value
input node-name whole/byte/nybble/bit [byte] [nybble/bit] data
output none
Refers to general commands which are useful for more than one type of observation.
input project-id
output none
input observer's-name
input type duration mode
output scan-id
input catalog-name
output none
input source-name
output none
input none
output none
input none
output subreflector-position
input none
output temperature pressure humidity
Refers to commands sent to the telescope drive program - STEER.
input topo/hori/appa/mean/b1950/j2000/gala/ecli
output none
input feed-name
output none
input latitude scan-rate
output none
input longitude scan-rate
input psi phi theta
output none
input angle
output none
input hour-angle declination
output none
input angle
output none
input angle
output none
input on/off
output none
Commands which are used for doing continuum observations (ask Jonathan and George for input on this section).
Commands used for doing spectral line measurements (ask Mike for input on this section).
Commands used for doing pulsar observations (ask Claire for input on this section).
Commands used for mapping (ask Justin for input on this section).