point ra=00:57:45 dec=35:12:55 nodome
Each message consists of one or more fields delimited by spaces.
The terminator is a NULL (0) character.
The first field contains the command.
The other fields can contain keywords or keyword=value pairs.
The replies are limited to the two forms:
The ordinary case reponds with the word,
done point dist=.03
ERROR point power not on
done followed by the
name of the command followed by any optional keyword, keyword value
ERROR form lists the command name and
any error message. This message results from problems
in either interpreting or executing the command.
Each command must have a help feature so that if the
first keyword is
help the command will report
back immediately with a string showing the allowable options.
(With optional keywords in  brackets.)
point help done point ra= dec= [epoch=] [nodome] [noapp] [nocorr]
Every server must have a help command which lists the commands that are available. This command is used by tserver to link up servers under one roof. For example one telescope server may have the following conversation.
help done help beep dome mirror move_sec offset point power slit temps track
- Floating point:
Commands sent to different servers may, however, be executed simultaneously. For example, if the filter wheel, telescope and CCD camera are all controlled by different servers, they may be operated simultaneously. To allow this the tx command allows multiple connections.
There is currently no way to stop a task once started, although ways to get around this limitation are being explored.
where xxx is a number, the next transmission will consist of the specified number of bytes. This transmission will then be followed by the usual
nbytes=are never transmitted without a request and usually they usually asked for with a
nbytes=in part of the command.
The received bytes can be stored as uninterpreted bytes but the other following keywords can be used to help interpret the incoming bytes: