semi合集-English.pdf - 第733页

SEMI E99.1-1104 © SEMI 2000, 2004 2 7 Service Parameter to Data Item Mapping 7.1 Table 2 shows the m apping between message param eters defined by CIDR W and data i tems define d by SECS- II. For parameters specified in …

100%1 / 7923
SEMI E99.1-1104 © SEMI 2000, 2004 1
SEMI E99.1-1104
SPECIFICATION FOR SECS-I AND SECS-II PROTOCOL FOR CARRIER
ID READER/WRITER FUNCTIONAL STANDARD
This specification was technically approved by the Global Information and Control Committee and is the
direct responsibility of the Japanese Information and Control Committee. Current edition approved by the
Japanese Regional Standards Committee on July 23, 2004. Initially available at www.semi.org September
2004; to be published November 2004. Originally published June 2000; previously published November
2003.
1 Purpose
1.1 This document maps the services and data of the
Carrier ID Reader/Writer (CIDRW) standard to SECS-
II streams and functions and data definitions.
2 Scope
2.1 This document applies to all implementations of
CIDRW that use the SECS-II message protocol (SEMI
E5).
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 E4 SEMI Equipment Communications
Standard 1 Message Transfer (SECS-I)
SEMI E5 SEMI Equipment Communications
Standard 2 Message Content (SECS-II)
NOTICE: As listed or revised, all documents cited
shall be the latest publications of adopted standards.
4 Terminology
4.1 Abbreviations and Acronyms
4.1.1 CIDRW — Carrier ID Reader/Writer; represents
both the Reader and the Read/Writer.
4.1.2 SECS — SEMI Equipment Communications
Standard
5 Physical Requirements
5.1 The CIDRW using the SECS-I protocol shall use a
9-pin female connector.
6 Service Message Mapping
6.1 Table 1 shows the specific SECS-II streams and
functions that shall be used for SECS-II
implementations of the service messages defined in
SEMI E99.
6.2 Request and notification messages are mapped to
primary (odd-numbered) SECS-II functions and
response messages are mapped to secondary (even-
numbered) SECS-II functions.
6.3 In some cases, a common set of parameters allows
more than one service to be mapped to the same stream
and function, with an additional SECS-II data item used
to differentiate between the two services.
Table 1 Services Mapped to SECS-II Messages
Message Name Stream,Function SECS-II Name
ChangeState S18,F13/F14 Subsystem Command Request/Acknowlege
Get Attributes S18,F1/F2 Read Attribute Request/Data
Get Status S18,F13/F14 Subsystem Command Request/Acknowledge
Perform Diagnostics S18,F13/F14 Subsystem Command Request/Acknowledge
Read Data S18,F5/F6 Read Request/Data
Read ID S18,F9/F10 Read ID Request/Data
Reset S18,F13/F14 Subsystem Command Request/Acknowledge
Set Attributes S18,F3/F4 Write Attribute Request/Acknowledge
Write Data S18,F7/F8 Write Request/Acknowledge
Write ID S18,F11/F12 Write ID Request/Acknowledge
SEMI E99.1-1104 © SEMI 2000, 2004 2
7 Service Parameter to Data Item Mapping
7.1 Table 2 shows the mapping between message parameters defined by CIDRW and data items defined by SECS-
II. For parameters specified in the definitions of a CIDRW service, either the parameters themselves, or individual
elements of complex parameters, map to a specific data item.
Table 2 Service Parameters to Data Item Mapping
Parameter Name SECS-II Data Item Format Values
Attribute ID ATTRID 20 Name of attribute
Attribute Value ATTRVAL 20
Carrier ID MID 20 20
16
- 7E
16
(Visible ASCII)
Data DATA 20 All characters 00H-0FFH
DataSize DATALENGTH 52
DataSeg DATASEG 20
HeadID TARGETID 20 “00”-“31”
Identifies either an individual head (“01”-
“31”) or the CIDRW subsystem itself (“00").
PM Information STATUS 20 “NE” = Normal execution, “MR” =
Maintenance required
Result Status SSACK 20 “NO” = Normal operation;
“EE” = Execution error;
“CE” = Communication error;
“HE” = Hardware error; “TE” = Tag error
Status List of
STATUS
L,4
1. <PMInformation>
2. <AlarmStatus>
3. <OperationalStatus>
4. <HeadStatus>
Current values of PM Information with the
corresponding attributes for CIDRW and
Head (if applicable). See Tables 4 and 5.
StateRequest CPVAL 20 “OP”,“MT”
NOTE 1: There are also data items used in SECS-II messages that do not map to specific services parameters. Services with the same set of
parameters are mapped to the same SECS-II message by adding an additional data item to differentiate between the services. Table 3 contains the
SECS-II data items that have not a corresponding CIDRW service parameter:
Table 3 Additional Data Requirements Table
SECS-II Data Item Function Value
SSCMD Used to differentiate between different subsystem commands
indicated.
“ChangeState”
“GetStatus”
“Perform Diagnostics”
“Reset”
8 Data
8.1 CIDRW Attributes
8.1.1 Table 4 specifies the values for the CIDRW attribute identifiers and limitations on values.
Table 4 CIDRW Attribute Definitions
Attribute Name Description Access Format Value
Fundamental
“Configuration” Number of heads. RO 20
“01”“31”
SEMI E99.1-1104 © SEMI 2000, 2004 3
Attribute Name Description Access Format Value
“AlarmStatus” Current CIDRW substate of ALARM STATUS RO 20 “0” = NO
ALARMS
“1” = ALARMS
“OperationalStatus” Current CIDRW substate of OPERATIONAL RO 20 “IDLE”, “BUSY”,
“MANT”
“SoftwareRevisionLevel” Revision (version) of software RO 20 8 byte maximum
Optional
CarrierIDLength Length byte of the Carrier ID.
If non-visible ASCII character exists in this
string, CIDRW shall send out an error to the
upstream controller.
RW 52 01–16
CarrierIDOffset Offset position of the first byte for Carrier ID in
the Electric Tag.
RW 52 00–15
“DateInstalled” Date the subsystem was installed RO 20 “YYYYMMDD” format
“DeviceType” Identifies subsystem as either a Carrier ID
Reader or a Carrier ID Reader/Writer.
RO 20 “CIDR_” or “CIDRW”
“HardwareRevisionLevel” Revision number of the hardware RO 20 8 byte maximum
“MaintenanceData” Supplier dependent RO 20 80 byte maximum
“Manufacturer” The name or identifier of the manufacturer RO 20 20 byte maximum
“ModelNumber” The manufacturers model designation RO 20 20 byte maximum
“SerialNumber” Subsystem serial number assigned by
manufacturer.
RO 20 20 byte maximum
8.2 Read (Write) Head Attributes
8.2.1 Table 5 shows the format and values for the Read (Write) Head.
Table 5 Read (Write) Head Attribute Definitions
Attribute Name Description Access Format Value
Fundamental
“HeadStatus” The current state. RO 20 “IDLE”,
“BUSY”,
“NOOP”
“HeadID” Head number 0–31 RO 20 2 digits, “00” through “31”.
Optional
“Cycles” Number of read and write
operations performed.
RO 54
“HeadCondition” The current Maintenance status RO 20 “NO” = No alarms
“NM” = Needs Maintenance
“NP” = No power
“RT” = Read/Write rate fault
“RW” = Read/Write fault.
“HeadDateInstalled” Date this head was installed RO 20 “YYYYMMDD” format
“HeadMaintenanceData” Supplier dependent RO 20 Text