Output queue
Response messages, such as those generated from print commands, are placed in the output queue.
All remote command interfaces share the same output queue.
The output queue sets the message available (MAV) bit in the status model.
The data in the output queue is cleared by the *CLS command.
Error queue
The error queue holds error and status messages. As programming errors and status messages
occur, a message that defines the error or status is placed in the error queue.
An error or status message is cleared from the error queue when it is read. You can also clear the
error queue by sending the command errorqueue.clear(). An empty error queue clears the error
available (EAV) bit in the Status Byte Register.
Messages in the error queue include a code number, message text, severity, and TSP-Link
®
node
number. See Error summary list (on page 6-2) for a list of the messages.
When you read a single message from the error queue, the oldest message is read. If you attempt to
read the error queue when it is empty, the error number 0 and “No Error” is returned.
The commands used to control the error queue are listed in the following table.
Request error code, text message, severity, and TSP-Link node
number.
Status function summary
The following functions and attributes control and read the various registers. Additional information for
the various register sets is included later in this section. Also, refer to the specific command as listed
in TSP commands (on page 9-7).
To Next Page
Loading...
Need help?
General
