semi合集-English.pdf - 第735页
SEMI E99.1-1104 © SEMI 2000, 2004 4 NOTICE: SEMI makes no warranties or representations as to the su itability of the standard set fo rth herein for any particular application . The determinati on of the suitability o f …

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

SEMI E99.1-1104 © SEMI 2000, 2004 4
NOTICE: SEMI makes no warranties or representations as to the suitability of the standard 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.

SEMI E99.1-1104 © SEMI 2000, 2004 5
RELATED INFORMATION 1
SCENARIOS
NOTICE: This related information is not an official part of SEMI E99.1. This related information was approved for
publication by full letter ballot procedures on January 14, 2000.
This section provides examples of typical scenarios for a Carrier ID Reader/Writer.
R1-1 Read ID
R1-1.1 The upstream controller sends a Read ID Request message to the CIDRW for Head 1. The CIDRW Head 1
reads the ID, and the CIDRW returns the ID to the upstream controller.
CIDRW
Upstream
Controller
S18,F9 Read ID Request
Target ID = “01”
S18,F10 Read ID Data
MID = “XYZ001”
Figure R1-1
Read ID Scenario
R1-2 Read Data
R1-2.1 The upstream controller sends a Read Data Request message to the CIDRW for Head 1 and DataSeg 1. The
CIDRW Head 1 reads the data, and the CIDRW returns the data to the upstream controller.
CIDRW
Upstream
Controller
S18,F5 Read Request
Target ID = “01”
DataSeg = “0”
S18,F6 Read Data
Data = “yyyyy”
Figure R1-2
Read Data Scenario
R1-3 Write ID
R1-3.1 The CIDRW is in IDLE. The upstream controller requests the CIDRW change its operational status to
MAINTENANCE.
R1-3.2 The CIDRW changes to MAINTENANCE and replies that it has changed state.
R1-3.3 The upstream controller sends a Write ID Request message to the CIDRW for Head 1. The CIDRW Head 1
reads the ID, and the CIDRW returns the ID to the upstream controller.