Mon Oct 26 18:19:03 PST 1998 Sun Dec 12 16:07:02 PST 1999 1. AO Message Header All messages in the AO-PHARO interface (and future external interfaces) will have a message header as defined below, followed by a message body to be defined for each message type: typedef struct msg_hdr { U32 msg_id; U32 src_id; /* sender application id (see net_ao.h) */ } MSG_HDR; For consistency (and to achieve true distribution), all internal messages in the AO system (real-time embedded system and GUI-based control) will also follow the message structure described herein. 2. AO-PHARO Interface 2.1 From AO to PHARO 2.1.1 AO Status, Configuration and Performance Message The AO status, configuration and performance (SCP) data message (as defined in ao_if.h) is sent periodically to PHARO at the rate of once per second upon PHARO's network connection. It also is sent to PHARO upon detection of a loss of network connection with the AO real-time system (AOCP). 2.1.2 TCS Status Message The TCS status message (as defined in ao_tcs_if.h) is sent periodically to PHARO at the rate of once per second upon PHARO's network connection. It also is sent to PHARO upon detection of a loss of network connection with TCS. 2.1.3 Command and Response Messages All command messages to (and from) PHARO consist of a standard message header followed by an ASCII command text string. The command syntax and semantics, and their respective responses, are defined in 2.1.4. typedef struct cmd_msg { MSG_HDR hdr; char cmd[MAX_CMD_LEN]; } CMD_MSG; A command response message, when required, will have the following structure: typedef struct rsp_msg { MSG_HDR hdr; char rsp[MAX_RSP_LEN]; } RSP_MSG; 2.1.4 Commands and Responses The following PHARO commands and their responses are currently defined: 1. Request PHARO's images command: get_image {background | source} ncols=512 nrows=512 ncycles=1 nendptframes=1 response: get_image: completed. 2. Select PHARO's filters command: set_wheel where :: {slit | lyot | filter | grism | carousel | shutter} :: {1 .. 10} 1 .. 3 for carousel 1 .. 2 for shutter 1 .. 10 for others response: set_wheel: completed. = 2.2 From PHARO to AO 2.2.1 PHARO Status Message The PHARO status message (as defined in ao_if.h) is sent to AO upon change in the status of any of PHARO's wheels. 2.2.2 Command and Response Messages The structure of AO command messages and their respective response messages are as defined above. In addition to commands to control the AO equipment, commands are also provided to control the TCS and operate similarly to the corresponding remote telescope commands. 2.2.3 Commands and Responses The following AO commands and their responses are currently defined: 1. Set DM Mode command: set dm {on | off} response: set: completed. dm = on set: completed. dm = off set: rejected. Invalid command. 2. Set Tip/Tilt Mode command: set tip-tilt {on | off} response: set: completed. tip-tilt = on set: completed. tip-tilt = off set: rejected. Invalid command. 3. Move Telescope in RA/Dec (arcseconds) command: move_tel [+|-]xxxx.xxx [+|-]xxxx.xxx response: move_tel: completed. move_tel: rejected. Invalid command. 4. Other TCS Control . Source position coords ... (five or six arguments) . Define Current Position of Telescope tx . Move Telescope ret . Zero DRA and DDEC Display Offsets z The response can be one of the following: : completed. : rejected. Unrecognized command. : rejected. Invalid parameter(s). : rejected. Unable to execute at this time. : processing.