semi合集-English.pdf - 第1346页
SEMI E30-1103 © SEMI 1992, 2003 20 4.1.5.3 Simultaneous Atte mpts to Establi sh Communications — For equipm ent that supports interleaving, it i s possible that either the host or equipment could send an Establish Comm u…
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
SEMI E30-1103 © SEMI 1992, 2003
21
related to the equipment state models allows the host to
track the equipment state. An equipment’s behavior is
related to its current state. Thus, this capability helps
the host understand how an equipment will behave and
how it will react to host behavior.
4.2.1.1.2 Definitions
Collection Event — An event (or grouping of related
events) on the equipment that is considered significant
to the host.
Collection Event ID (CEID) — A unique identifier of a
collection event. See the SEMI E5 Standard for a full
definition of this data item.
Event — A detectable occurrence significant to the
equipment.
Report — A set of variables predefined by the
equipment or defined by the host via S2,F33/F34.
4.2.1.1.3 Detailed Description — The equipment
supplier must provide a set of predefined collection
events. Specific collection events are required by
individual capabilities and state models. Examples of
collection events include:
— The completion of each action initiated by a host
requested command,
— Selected processing and material handling activities,
— Operator action detected by the equipment,
— A state transition,
— The setting or clearing of an alarm condition on the
equipment, and
— Exception conditions not considered alarms.
See Section 6 for a list of required collection events.
The reporting of a collection event may be disabled per
event by the user to eliminate unwanted messages. An
event report message shall be sent to the host upon the
occurrence of a particular collection event if the
collection event (CEID) has been enabled. Attached to
each event message is one or more event reports which
contain variable data. Section 4.2.1.2 describes the
capability which allows for the dynamic customization
of event reports. The values of any data contained in an
event report message must be current upon the
occurrence of the event. This implies that event reports
be built at the time of the event occurrence.
The equipment shall also provide the S6,F15/F16
transaction to allow the host to request the data from a
specific event report.
4.2.1.1.4 Requirements
— The equipment supplier shall provide
documentation of all collection events defined on
the equipment and the conditions for each event to
occur.
— The equipment supplier shall provide unique CEIDs
for each of the various collection events that are
available for reporting.
— The equipment supplier shall provide a method for
enabling and disabling the reporting of each event.
This method shall either be available via the host
interface (see Section 4.2.1.2) or the equipment’s
operator console.
— For each event, the equipment supplier shall provide
either
• a default set of report(s) linked to the event
which contain data pertinent to that event, or
• the ability for the user to configure the data
linked to that event via the equipment’s
operator console or host interface (see Section
4.2.1.2).
4.2.1.1.5 Scenarios
Collection Event Occurs on the Equipment:
COMMENT HOST EQUIPMENT COMMENT
[IF] Event Report is Multi-block
<--S6,F5 [THEN] send Multi-block inquire
Multi-block grant S6,F6-->
[ENDIF]
<--S6,F11 Equipment sends Event Report
Host acknowledges Event Report S6,F12-->