semi合集-English.pdf - 第1536页

SEMI E32-0997 © SEMI 1994 , 1997 31 between the transfer partn ers as a result of exceptional conditions. HOCancelReady — Once a transfer partner has sen t a HOReady message, it is co m mitted to particip ate in a transf…

100%1 / 7923
SEMI E32-0997 © SEMI 1994, 1997 30
executed by the primary partner. Only one
HOCommand may be active at any time.
The list of commands to execute may be included in a
transfer recipe. See Section 4.2.4 above for more detail.
Figure 5.1
Micro Level Message Flow
When the secondary partner is passive, no
HOCommands need be issued. In this case, all micro
moves are conceived of and executed by the primary
partner. The HOReady and HOVerify portions are still
required in this case.
HOCommand Complete — Once the secondary partner
has completed the task defined in the HOCommand, it
uses the HOCommand Complete response message to
alert the primary partner. If an HOCommand cannot be
accepted or fails, this message shall be used to convey
that information.
HOVerify — The primary transfer partner, believing all
micro moves complete, shall check its port to ensure
that the transfer object has been sent (or received) and
that all mechanisms are in a safe position. Next, it shall
send the HOVerify message to the secondary partner,
asking that it perform the same check.
HOVerify Response — The affirmative response from
the secondary partner confirms that the transfer was a
success. This message may alternatively signify
(through a data field) that the secondary partner does
not consider the transfer to be complete. This message
coincides with the transition for both partners from the
macro level TRANSFERRING state to the ATOMIC
TRANSFER COMPLETE state.
5.2.2 Micro Level Messaging via Host — As
mentioned above, all three parts of the micro level of
communications must be carried out in some form. If a
direct link from equipment to equipment exists, they
should occur via that means, whether using SECS–I,
Parallel I/O, or another protocol. If no direct link exists,
there is a means by which the host may relay micro
level messages from one transfer partner to the other.
This is illustrated in Figure 5.2.
Figure 5.2
Micro Level Message Flow via Host
In this situation, the host may act as a surrogate of each
equipment's transfer partner. A piece of equipment
would send the same defined micro level message as
before, but would deliver it to the host via the standard
host link. The equipment would treat the host as its
transfer partner, expecting the same response as if it
were talking directly to its true transfer partner. The
host is responsible for managing the relay of messages
from one partner to the other as necessary.
The equipment shall provide the ability to pass micro
level messages through the host. If a direct peer–to–
peer link is available, the user shall be able to configure
the path for the messages (directly to partner or through
the standard host link).
5.3 Extended Behavior — This section discusses two
micro level messages which may be exchanged
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