semi合集-English.pdf - 第1345页
SEMI E30-1103 © SEMI 1992, 2003 19 4.1.5 Scenarios 4.1.5.1 Host Attempts to Establish Commu nications COMMENT HOST EQUIPMENT COMMENT Communications state is Enabled (any substate) Establish Communications S1,F13--> Re…
SEMI E30-1103 © SEMI 1992, 2003
18
Clock
Spooling
Control
4.1 Establish Communications — The Establish
Communications capability provides a means of
formally establishing communications following system
initialization or any loss of communications between
communicating partners, and thus of notifying the
communication partner that a period of non-
communication has occurred.
4.1.1 Purpose — Communications between host and
equipment are formally established through use of the
Establish Communications Request/Establish
Communications Acknowledge transaction.
The use of S1,F1/F2 for this purpose is ambiguous
since the transaction can be used for other purposes and
may occur at any time.
The S1,F13/F14 transaction, used in conjunction with
the Communications State Model, provides a means for
equipment to notify the host, or the host to notify the
equipment, that there has been a period of inability to
communicate. The successful completion of this
transaction also signals a possible need for
synchronization activities between host and equipment.
4.1.2 Definitions
COMMACK — Acknowledge code returned in the
Establish Communications Acknowledge message. See
the SEMI E5 Standard for a full definition of this data
item.
EstablishCommunicationsTimeout — An equipment
constant used to initialize the interval between attempts
to re-send an Establish Communications Request. This
value specifies the number of seconds for the interval.
See the SEMI E5 Standard for a full definition of this
variable data item.
4.1.3 Description — There are potential problems
when one side of the communications link fails and the
other side does not detect it. From the point of view of
the host, a loss of communications has many possible
causes. In some cases, host-controlled settings on the
equipment may need to be reset. In other cases, the
equipment may have continued an automatic processing
sequence during the period of no communication and
may have changed states. The definition of a formal
protocol for establishing communications alerts the host
to the need to synchronize itself with the equipment’s
current status.
Equipment shall consider communications as formally
established whenever either of the following conditions
have been satisfied:
14
— Communications Request has been sent to the host
and an Establish Communications Acknowledge
has been received within the transaction timeout
period and with an acknowledge code of Accept, or
— Communications Request has been received from
the host, and an Establish Communications
Acknowledge response has been successfully sent
with an acknowledge code of Accept.
When the equipment sends an Establish
Communications Request to the host, this notifies the
host of the possible need to synchronize itself with the
equipment.
When the equipment is attempting to establish
communications, an Establish Communications Request
shall be sent periodically until communications have
been formally established as described above. The
interval between attempts must be user-configurable
and begins as soon as a connection transaction failure is
detected (see Section 3.2).
Attempting to establish communications is not a low-
level connectivity issue, but rather a logical application
issue used by either party to notify its partner that the
host may need to perform synchronization activities
with the equipment.
4.1.4 Requirements
— Equipment must support the Communication State
Model (see Section 3.2).
— Equipment must provide the EstablishCommunica-
tionsTimeout equipment constant described above.
14 Satisfaction of either of these conditions will result in a transition
to the COMMUNICATING substrate. See Section 3.2 for further
detail.
SEMI E30-1103 © SEMI 1992, 2003
19
4.1.5 Scenarios
4.1.5.1 Host Attempts to Establish Communications
COMMENT HOST EQUIPMENT COMMENT
Communications state is Enabled
(any substate)
Establish Communications S1,F13-->
Request
<--S1,F14 Reply COMMACK = Accept and
Communications state =
COMMUNICATING
4.1.5.2 Equipment Attempts to Establish Communications and Host Acknowledges
COMMENT HOST EQUIPMENT COMMENT
Communications State = NOT COMMUNICATING
[LOOP]
[LOOP]--SEND
<--S1,F13 Establish Communications Request
Establish Communications S1,F14-->
Acknowledge [IF] S1,F14 rcvd w/o timeouts
[THEN] exit_loop--SEND
[ELSE] Delay for interval in
Establish Commuications-
Timeout
[ENDIF]
[END_LOOP]--SEND
[IF] COMMACK = Accept
[THEN] Communications state=
Communicating
exit_loop--
[ELSE] Reset timer for delay,
and delay for interval
specified in
EstablishCommunications—
Timeout
[ENDIF]
[END_LOOP]
SEMI E30-1103 © SEMI 1992, 2003
20
4.1.5.3 Simultaneous Attempts to Establish Communications — For equipment that supports interleaving, it is
possible that either the host or equipment could send an Establish Communications Request before receiving the
request from its partner. As communications are established by the successful acceptance of any one Establish
Communications Request, it is immaterial who sends the request first. The roles of host and equipment may be
reversed.
Equipment Receives S1,F14 From Host Before Sending S1,F14:
COMMENT HOST EQUIPMENT COMMENT
Communications State = NOT COMMUNICATING
<--S1,F13 Establish Communications Request
Establish Communications S1,F13-->
Request
Reply COMMACK = Accept S1,F14--> S1,F14 received from Host and
Communications established
15
and
Communications state =
COMMUNICATING
<--S1,F14 Reply COMMACK = Accept
16
Equipment Sends S1,F14 To Host Before Receiving S1,F14:
COMMENT HOST EQUIPMENT COMMENT
Communications State = NOT COMMUNICATING
<--S1,F13 Establish Communications Request
Establish Communications S1,F13-->
Request
<--S1,F14 Reply COMMACK = Accept
15
Communications established
15
and
Communications state =
COMMUNICATING
Reply COMMACK = Accept S1,F14--> S1,F14 received from Host
15 Communications are establisted at the successful completion of the S1,F13/14 transaction where COMMACK is set to zero.
16 Communications are established on the successful transmission of S1,F14, even if there is an open S1,F13.
4.2 Data Collection — Data collection allows the host
to monitor equipment activity via event reporting, trace
data reporting, limits monitoring, and query of selected
status or other variable data.
4.2.1 Event Data Collection — Event data collection
provides a dynamic and flexible method for the user to
tailor the equipment to meet individual needs with
respect to data representation and presentation to the
host. The event-based approach to data collection
provides automatic notification to the host of
equipment activities and is useful in monitoring the
equipment and in maintaining synchronization with the
equipment.
Event data collection may be broken into two logical
parts: host notification when an event occurs and
dynamic configuration of the data attached to the event
notification.
4.2.1.1 Event Notification — This section describes the
method of notifying the host when equipment
collection events occur.
4.2.1.1.1 Purpose — This capability provides data to
the host at specified points in equipment operation.
This asynchronous reporting eliminates the need for the
host to poll the equipment for this information. Events
on the equipment may trigger activity on the part of the
host. Also, knowledge of the occurrence of events