semi合集-English.pdf - 第1537页

SEMI E32-0997 © SEMI 1994 , 1997 32 HOReady An equipment indicates to its trans fer partner a readin ess to begin a s pecific atomic transfer. Parameter REQ/IND Description Form EQNam e M Identifier (N ame attribute) of …

100%1 / 7923
SEMI E32-0997 © SEMI 1994, 199731
between the transfer partners as a result of exceptional
conditions.
HOCancelReady — Once a transfer partner has sent a
HOReady message, it is committed to participate in a
transfer. Under some circumstances, an equipment
needs to withdraw from that commitment. The
HOCancelReady message is used for this purpose.
The HOCancelReady shall be accepted by the transfer
partner unless it has already sent the corresponding
HOReady. In cases where both transfer partners have
sent the HOReady message, the atomic transfer is
considered to have begun and cannot be canceled. If the
transfer partner receives an HOCancelReady, but has no
record of receiving the original HOReady, it should
accept the HOCancelReady.
HOHalt — The HOHalt message is used by a transfer
partner in situations when the equipment or transfer
object are endangered. The receiver of the HOHalt
message shall cease all movement related to the atomic
transfer immediately. Manual intervention is required
before the halted partner may resume movement.
5.4 Micro Level Services — This s ection expands
upon the messages defined in Section 5.2.1. It defines
the parameters of the messages and discusses the
possible values.
5.4.1 Service List — The following messages are
exchanged between transfer partners during an atomic
transfer.
Service Name Description Confirmed
HOReady Each partner sends this message
when it is ready to begin the
transfer process.
No
HOCommand Message sent by the primary
transfer partner to cause the
secondary partner to perform an
activity in the transfer envelope.
The response to this message
indicates completion of the
activity or error.
Yes
HOVerify Message sent by the primary
transfer partner informing the
secondary partner that all
activities should be complete
and asking for confirmation.
Yes
HOCancelReady Message sent to rescind a
previous HOReady message.
Yes
HOHalt Message sent to stop all action
by the transfer partner. This
message ends the transfer and
requires manual intervention at
the halted equipment.
Yes
5.4.2 Service Detail — The tables below define the
parameters for each service. In some cases, parameters
have additional detail which is defined in a following
section. These parameters are marked with the “*”
character.
The following codes are used in the definition of the
parameters (e.g., how each parameter is used in each
direction):
“M” — Mandatory Parameter—must be given a valid
value.
“C” — Conditional Parameter—may be defined in
some circumstances and undefined in others. Whether a
value is given may be completely optional or may
depend on the value of other parameter.
“U” — User-Defined Parameter.
“–” — Not Used.
“=” — (for Response only) Indicates that the value of
this parameter in the response must match that in the
primary (if defined).
The column labelled “Form” is used to indicate the type
of data contained in a parameter. The forms used in this
document are defined below.
Unsigned Integer — May take the value of any non–
negative integer. Messaging protocol may impose a
limit on the range of possible values.
Enumerated — The parameter may take on one of a
limited set of possible values. These values are
generally given textual names, but may have simpler
representations in protocol (e.g., numeric values).
Boolean — The parameter may take on one of two
possible values, equating to “True” and “False.”
Text — A text string.
Structure — A complex structure which consists of a
collection of values of one of the possible forms. The
breakdown of all “Structure” parameters is provided
within this document.
SEMI E32-0997 © SEMI 1994, 1997 32
HOReady
An equipment indicates to its transfer partner a readiness to begin a specific atomic transfer.
Parameter REQ/IND Description Form
EQName M Identifier (Name attribute) of the equipment sending this message. Text
TRLink M Used by the transfer partners to assure that their communications relate to the
same atomic transfer.
Unsigned integer
TRPort M Identifier of the port (on the equipment sending this message) to be used for the
transfer.
Unsigned integer
TRObjName C Identifier of the object to be transferred. Text
TRObjType C Type of transfer object, required if transfer might involve multiple types. Enumerated
TRRole M Is the sender of this message the primary or secondary transfer partner. Enumerated
TRPartner C Identifier (Name attribute) of the equipment expected to receive this message. Text
TRPartnerPort C Material I/O port on the equipment which receives this message to be used for
this atomic transfer.
Unsigned integer
TRDirection M Does the sender of this message expect to send or receive the transfer object. Enumerated
TRType M Is the transfer to be passive or interactive? Enumerated
TRLocation C Identifier of the material location (on the sender of this message) which will be
the source (or destination) of the transfer object.
Unsigned integer
HOCommand
The primary transfer partner directs the secondary transfer partner to perform an action related to a specific atomic
transfer.
Parameter REQ/IND RSP/CONF Description Form
TRLink M M(=) Identifier of the atomic transfer which related to this HOCommand. Unsigned
integer
HOCmdName* M - Specific command to be executed. Text
(List of)
CmdParameter
C - Parameter(s) related to the specified HOCommand. (May be a list of
0.) See Section 4.4.2 for definition of CmdParameter.
Structure
HOStatus - M Reports success or failure of the command and, if failure, supplies error
detail.
Structure
HOStatus Detail
Parameter RSP/CONF Description Form
HOAck M Did the activity succeed or fail, was the inquiry accepted or rejected. True is a positive
result, False is negative.
Boolean
(List of) Status C Reports any errors found. (May be list of 0) See Section 4.4.2 for details of this structure. Structure
HOVerify
The primary transfer partner indicates completion of the atomic transfer to the secondary partner and requests
confirmation of a successful transfer.
Parameter REQ/IND RSP/CONF Description Form
TRLink M M(=) Identifier of the atomic transfer. Unsigned integer
HOStatus M M Reports the completion status of the atomic transfer from the standpoint of the
sending transfer partner.
Structure
SEMI E32-0997 © SEMI 1994, 199733
HOCancelReady
Having previously sent an HOReady message, a transfer partner determines that it is no longer ready to begin the
transfer and sends the HOCancelReady message.
Parameter REQ/IND RSP/CONF Description Form
TRLink M M(=) Identifier of the atomic transfer. Unsigned integer
HOCancelAck* - M Acknowledge code for HOCancelReady. Enumerated
HOHalt
This message may be sent by either transfer partner when the equipment or transfer object is endangered. It requires
the receiver to cease all transfer-related movement immediately. Manual intervention is required before the halted
partner may again be available for transfer.
Parameter REQ/IND RSP/CONF Description Form
TRLink M M(=) Indentifier of the atomic transfer. Unsigned integer
HOHaltAccept - M True if the request is accepted. Request may be denied only if
referenced atomic transfer does not exist.
Boolean
5.4.3 Parameter Definitions — This section gives further detail on certain parameters defined above. Parameters
which are defined in Section 4.4 are not repeated here.
ErrorCode
HOCommand:
• Rejected/Unrecognized Command.
• Rejected/Parameter Error.
• Failed (Completed Unsuccessfully) — indicates that the activity was attemped, but failed; the mechanisms
continue to be operational.
• Failed (Unsafe) — indicates that the equipment was left in an unrecoverable state at the end of the activity due
to the failure of a mechanism or due to the risk of damage to the equipment or material. Manual intervention is
required.
HOVerify:
• Sensor-Detected Obstable.
• Material Not Sent.
• Material Not Received.
• Material Lost.
• Hardware Failure.
• Handoff Canceled Externally (by host or operator).
HOCmdName — The set of micro commands is provided below as an example. The commands used are not
limited to this set. However, adherence to a common set of commands will speed implementation of material
transfer.
This particular example applies to a situation where the secondary partner is active and the primary partner is
passive.