semi合集-English.pdf - 第726页
SEMI E99-1104 E © SEMI 2000, 2004 16 Table R1-5 Scenario to Write Data to Bo th Heads Controller CIDRW Head 1 Head 2 Msg. Msg. Action State Action State Action State Write Data 01 Operating Start Write Busy Idle Write …
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
SEMI E99-1104
E
© SEMI 2000, 2004 16
Table R1-5 Scenario to Write Data to Both Heads
Controller CIDRW Head 1 Head 2
Msg. Msg. Action State Action State Action State
Write Data 01 Operating Start
Write
Busy Idle
Write Data 02 Operating Busy Start
Write
Busy
Write Data
Reply 01
Operating Idle Busy
Write Data
Reply 02
Operating Idle Idle
SEMI E99-1104
E
© SEMI 2000, 2004 17
RELATED INFORMATION 2
OBJECT MODEL
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 August 28, 2000.
R2-1 Object models provide a graphic representation of entities. The models in this section use the Object
Modeling Technique (OMT) described in Object-Oriented Modeling and Design. Object types are represented by
rectangles with one, two, or three sections. The name of the object type is in the first, or only section. Attributes,
information about the object, are shown in the second section. Operations or services are shown in a third section.
Lines between objects represent relationships.
R2-2 Three models are shown for purposes of illustration. The general multi-head case is shown first with only the
required attributes and services. Next, the full model for the multi-head case is shown with all attributes and
services defined in this standard. Finally, the full model for the integrated single-head case is shown.
R2-3 Note that the Upstream Controller sends all service requests to the CIDRW controller, including services
shown for the individual heads. Services shown on these models for CIDRW are those with a Head ID service
parameter value of zero while services shown for the Head are those with a Head ID service parameter value
between one and thirty-one.
R2-4 Fundamental Requirements Example Object Models
R2-4.1 The object model in Figure R2-1 shows objects for the general (multi-head) CIDRW satisfying fundamental
requirements only. It shows the CIDRW subsystem as made up of one or more heads. It also illustrates the required
attributes and services provided by the CIDRW and its relationships with its upstream controller and with its heads.
1+
CIDRW
- Alarm Status
- Configuration
- SoftwareRevisionLevel
- Operational Status
Get Attributes
Get Status
Head
- HeadID
- HeadStatus
Get Attributes
Get Status
Read ID
Upstream
Controller
requests
services from
is made up of
Figure R2-1
Object Model for Fundamental Requirements