semi合集-English.pdf - 第724页

SEMI E99-1104 E © SEMI 2000, 2004 14 11.4.12 Service Operability 11.4.13 Some services are perform ed by the CIDRW and ot hers are logically performe d by the individ ual heads. It is expected that th e CIDRW will suppor…

100%1 / 7923
SEMI E99-1104
E
© SEMI 2000, 2004 13
11.4.10 Write Data
11.4.10.1 Write Data is used to request a generic block of data to an ID Reader/Writer Head. This service is
required for the Carrier ID Reader/Writer type and is optional otherwise. The Carrier ID Reader/Writer is not
required to understand the content of the data.
Table 17 Write Data Service Definition
Parameter Req/Ind Rsp/Conf Description
Head ID M M Specifies Head.
DataSeg C - Indicates specific section of data.
DataSize C - Indicates number of bytes to read.
Data M - Write Data (from Host).
Result Status - M Result information on the status of the request.
Status - M Status information
11.4.11 Write ID
11.4.11.1 Write ID is used to set the field for Carrier ID to an ID Reader/Writer Head. This service is optional.
This shall be a protected operation that can be performed only in the MAINTENANCE state to prevent accidental
overwriting of the ID field.
Table 18 Write ID Service Definition
Parameter Req/Ind Rsp/Conf Description
Head ID M M Specifies Head.
Data (ID) M - Write ID Data.
Result Status - M Result information on the status of the request
Status - M Status information
11.4.11.2 The field for the Carrier ID shall be located from the first byte to the maximum byte of Carrier ID in the
memory for electric tag.
SEMI E99-1104
E
© SEMI 2000, 2004 14
11.4.12 Service Operability
11.4.13 Some services are performed by the CIDRW and others are logically performed by the individual heads. It
is expected that the CIDRW will support multiple interleaved transactions to the various independent logical units.
Table 19 shows which of the various services can be performed by the CIDRW when the CIDRW and its heads are
in various individual states. Note that when in the initializing state after powerup or the reset service, the CIDRW
may not be able to communicate.
Table 19 Valid Services per State
Service
Write ID
Write Data
Set Attributes
Reset
Read ID
Read Data
Perform
Diagnostics
Get Status
Get Attributes
ChangeState
CIDRW State
INITIALIZING
OPERATING X X
X X X X X X X
MAINTENANCE X X
X X
(See NOTE 1.)
X X X X
Head State
NOT OPERATING
X
IDLE
X
BUSY
X
NOTE 1: May not be supported by all Readers.
12 Event Notifications
12.1 Event Notification is an optional capability where the CIDRW is able to detect events and report state and
status changes independently of a service request from the upstream controller.
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-1104
E
© SEMI 2000, 2004 15
RELATED INFORMATION 1
SCENARIOS
NOTICE: This related information is not an official part of SEMI E99. This related information was approved for
publication by full letter ballot procedures on September 3, 1999.
R1-1 This section provides examples of typical scenarios for a CIDRW with two read heads.
Table R1-1 Reset Scenario
Controller CIDRW Head 1 Head 2
Msg. Msg. Action State Action State Action State
Reset Perform
Reset
Init
State
NORMAL NORMAL
Reset Reply Operating
or Maintenance
Idle or
NORMAL
Idle or
NORMAL
Table R1-2 Get Status Scenario
Controller CIDRW Head 1 Head 2
Msg. Msg. Action State Action State Action State
Get Status 0 Determine
Status
Operating
or Maintenance
Any Any
Status Reply Same Any Any
Table R1-3 Scenario for Interleaved Read ID from Both Heads
Controller CIDRW Head 1 Head 2
Msg. Msg. Action State Action State Action State
Read ID 01 Operating Start
Read
Busy Idle
Read ID 02 Operating Busy Start
Read
Busy
Read ID
Reply 01
Operating Idle Busy
Read ID
Reply 02
Operating Idle Idle
Table R1-4 Read Data from Both Heads
Controller CIDRW Head 1 Head 2
Msg. Msg. Action State Action State Action State
Read Data 01 Operating Start
Read
Busy Idle
Read Data 02 Operating Busy Start
Read
Busy
Read Data
Reply 01
Operating Idle Busy
Read Data
Reply 02
Operating Idle Idle