semi合集-English.pdf - 第1882页
SEMI E53.1-0704 © SEMI 1996, 2004 1 SEMI E53.1-0704 SECS-II SUPPORT FOR EV ENT REPORTING STANDARD This standard was technically approved by the Globa l Informat ion & Control Committee and is the direct responsibilit…
SEMI E53-0704 © SEMI 1996, 2004 21
NOTICE: SEMI makes no warranties or representations as to the suitability of the standards set forth herein for
any particular application. The determination of the suitability of the standard is solely the responsibility of the user.
Users are cautioned to refer to manufacturer’s instructions, product labels, product data sheets, and other relevant
literature respecting any materials mentioned herein. These standards are subject to change without notice.
The user’s attention is called to the possibility that compliance with this standard may require use of copyrighted
material or of an invention covered by patent rights. By publication of this standard, SEMI takes no position
respecting the validity of any patent rights or copyrights asserted in connection with any item mentioned in this
standard. Users of this standard are expressly advised that determination of any such patent rights or copyrights, and
the risk of infringement of such rights, are entirely their own responsibility.
Copyright by SEMI® (Semiconductor Equipment and Materials
International), 3081 Zanker Road, San Jose, CA 95134. Reproduction o
f
the contents in whole or in part is forbidden without express written
consent of SEMI.
SEMI E53.1-0704 © SEMI 1996, 2004 1
SEMI E53.1-0704
SECS-II SUPPORT FOR EVENT REPORTING STANDARD
This standard was technically approved by the Global Information & Control Committee and is the direct
responsibility of the Japanese Information & Control Committee. Current edition approved by the Japanese
Regional Standards Committee on April 30, 2004. Initially available at www.semi.org June 2004; to be
published July 2004. Originally published December 1996.
1 Purpose
1.1 This document maps the services and data of its
prime document, SEMI E53, to SECS-II streams and
functions and data definitions.
2 Scope
2.1 This is the standard way to implement the Event
Reporting, which provides event-based reporting using
the SECS-II message format.
NOTICE: This standard does not purport to address
safety issues, if any, associated with its use. It is the
responsibility of the users of this standard to establish
appropriate safety and health practices and determine
the applicability of regulatory or other limitations prior
to use.
3 Referenced Standards
3.1 SEMI Standards
SEMI E5 — SEMI Equipment Communications
Standard 2 Message Content (SECS-II)
SEMI E39 — Object Services Standard: Concepts,
Behavior, and Services
SEMI E39.1 — SECS-II Protocol for Object Services
Standard (OSS)
SEMI E53 — Event Reporting
NOTICE: Unless otherwise indicated, all documents
cited shall be the latest published versions.
4 Terminology
None.
5 Mapping of Event Reporting Messages
Table 1 Event Messages Mapping
Service Message Name Stream, Function SECS-II Name
Event Report Send S6F11,F12,F13,F14 Event Report Send/Acknowledge
Annotated Event Report Send/ Acknowledge
Event Report Request S6F15,F16 Event Report Request/Data
Data Report Request S6F19,F20 Individual Report Request/Data
Collection Event Link Request S17F9,F10 Collection Event Link Request/Acknowledge
Collection Event Unlink Request S17F11,F12 Collection Event Unlink Request/Acknowledge
Data Report Create S17F1,F2 Data Report Create Request/Acknowledge
Data Report Delete Request S17F3,F4 Data Report Delete Request/Acknowledge
Trace Create Request S17F5,F6 Trace Create Request/Acknowledge
Trace Delete Request S17F7,F8 Trace Delete Request/Acknowledge
Trace Report Send S6F27,F28 Trace Report Send/ Acknowledge
Trace Reset Request S17F13,F14 Trace Report Reset Request/Acknowledge
Trace Report Request S6F29,F30 Trace Report Request/Data
Create Object S14F9,F10 Create Object Request/Acknowledge (SEMI E39.1)
Delete Object S14F11,F12 Delete Object Request/Acknowledge (SEMI E39.1)
SEMI E53.1-0704 © SEMI 1996, 2004 2
6 Event Parameters Mapping
Table 2 Event Service Parameter Mapping
Parameter SECS-II Data Item or Object Attribute
ErrorCode ERRORCODE
ErrorText ERRTEXT
ReportID RPTID
DataSrcSpec DATASRC
CollEventID CEID
EvtSrcSpec EVNTSRC
Enabled CEED
(list of) AttrName (list of) VID
ReportChangeOnly RPTOC
TraceID TRID
SamplePeriod TRSPER
TotalSamples TOTSMP
GroupSize REPGSZ
StartEventID CEID
StopEventID CEID
AutoDelete TRAUTOD
7 Implementation Details
7.1 Many of the messages of the Event Reporting
Standard are implemented with currently defined
SECS-II messages. Certain restrictions must be applied
to their usage. These restrictions are specified in this
section.
7.2 To be OSS-compliant, the following data items
must use the format 20 specification:
• RPTID
• CEID
• TRID
• VID
7.2.1 The format of the ASCII strings shall conform to
the Object identifier specifications in the Object
Services Standards, document SEMI E39 and SEMI
E39.1.
7.3 Each Data Report sample, whether stand alone or
as part of an Event or Trace report, will report
TIMESTAMP as the first item in its list of report
variables and/or object attributes. This means for
reports defined by the service user, the user should
define TIMESTAMP as the first VID in the report
definition. Further, all of the service provider’s
predefined reports shall deliver the value of
TIMESTAMP in the first V.
7.4 Serveral capabilities of the Event Reporting
Standard are accessed through the Object Services
Standard. When an instance of a report (Report, Event,
or Trace) object has been created, then its attributes can
be read and written using the Object Service’s GetAttr
and SetAttr messages.
7.4.1 Object Services shall be used to set RPTOC and
to get CHGND.
7.4.2 Object Services shall be used to set or clear
CEED.
7.4.3 EVNTSRC shall be provided in supplier
documentation or as a list of Event Sources obtained by
using Object Services to interrogate the Collection
Event Object, COLLEVENT, with the GetAttrName
request message.
7.5 Event Reporting Services is protocol independent
and therefore, makes no mention of SECS-II multi-
block access and grant messages. When the Event
Reporting Services use the SECS-II protocol, then
S6F11,F13 shall be preceded by S6F5 if a report will be
multi-block. Trace Report Send, S6F27 shall also use
the multi-block access/grant transaction if the report
will be multi-block.