-
Notifications
You must be signed in to change notification settings - Fork 2
Asynchronous Messages
Asynchronous messages are broadcast on the asynchronous message port. See Asynchronous Message Port
Each message is preceded by one of the following tags, as in "TAG:message". This allows a listening client to look for only messages that it might be interested in, by looking for a particular tag and ignoring others.
When datacube is true (Cf. §4.3.10) this message is sent after each cube has been written to a FITS extension. The number n increments {1, 2, 3, ... } for each extension. If the write was successful then the message terminates with COMPLETE, or ERROR if an error occurred writing the frame.
When an error occurs, the lowest-possible (fundamental) error message is written to the async port. Additional information will be in the log.
Sent during exposure delay to indicate exposure progress, indicates the remaining exposure delay n, in the chosen units (Cf. longexposure §4.3.30).
Sent during exposure delay to indicate exposure progress, indicates the remaining exposure delay n, in msec for device d.
This message is sent upon successful completion of each FITS file written, indicating the fully qualified filename.
Note that in the case of data cubes, this message is in addition to DATACUBE (§5.1.1) which would generate a DATACUBE: message for each cube, plus a FILE: message when all cubes have been written and the file is closed.
Sent during detector readout to indicate read progress, indicates number of lines read, n.
This tag is used for general informational, non-error but important messages. Unlike the activity log, this tag is used sparingly. For example, if a user neglects to set something where a default must be assumed, the system may alert the user via an async message using this tag.
Sent during detector readout to indicate read progress, indicates number of pixels read, n.
All Archon native commands will produce an asynchronous status message of the following format:
CMD:BEGIN
CMD:<reply>
CMD: ...
CMD:END
where CMD is the native command and <reply> is the reply from that command, which may be carried onto multiple lines. For any reply which contains multiple responses, each will be returned on a separate line, and the :BEGIN and :END denotes the beginning and ending of the reply. Examples of these are shown in Section 7.1.