semi合集-English.pdf - 第729页

SEMI E99-1104 E © SEMI 2000, 2004 19 RELATED INFORMATION 3 APPLICATION NOTES NOTICE : This related information is not an official pa rt of SEMI E99. This relat ed inform ation was approved for publication by full l etter…

SEMI E99-1104

R2-5 Full Capabilities

R2-5.1 Figure R2-2 shows the object model for a CIDRW with full capabilities, so that all optional attributes and

services are supported.

CIDRW

- AlarmStatus

- Configuration

- DateInstalled

- DeviceType

- HardwareRevisionLevel

- MaintenanceData

- Manufacturer

- ModelNumber

- OperationalStatus

- SerialNumber

- SoftwareRevisionLevel

ChangeState

GetAttributes

GetStatus

PerformDiagnostics

Reset

SetAttributes

Head

- Cycles

- HeadCondition

- HeadDateInstalled

- HeadID

- HeadStatus

- HeadMaintenanceData

Upstream

Controller

requests

services from

is made up of

GetAttributes

GetStatus

ReadData

ReadID

WriteData

WriteID

Figure R2-2

Object Model for Full Capabilities

R2-6 Integrated Model

R2-6.1 Figure R2-3 shows the object model for a CIDRW with full capabilities and a single integrated head. The

head is not shown as a separate component in this case, and the head attributes and services have become part of the

CIDRW subsystem itself.

CIDRW

- AlarmStatus

- Configuration

- Cycles

- DateInstalled

- DeviceType

- HardwareRevisionLevel

- HeadCondition

- HeadStatus

- MaintenanceData

- Manufacturer

- ModelNumber

- OperationalStatus

- SerialNumber

- SoftwareRevisionLevel

ChangeState

GetAttributes

GetStatus

PerformDiagnostics

ReadData

ReadID

Reset

SetAttributes

WriteData

WriteID

Upstream

Controller

requests

services from

Figure R2-3

Integrated Model with Full Capabilities

SEMI E99-1104

RELATED INFORMATION 3

APPLICATION NOTES

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.

R3-1 Combined State Model

R3-1.1 The following figure, R3-1 shows the combined state model for the CIDRW unit with nn heads, from

HEAD01 TO HEADnn. The CIDRW is considered as IDLE when and only when it is in OPERATING and all of

its heads are IDLE.

CIDRW

HEAD01

OPERATING

BUSY

IDLE

NOT OPERATING

HEADnn

INITIALIZING

ALARMS

MAINTENANCE

910

ALARM STATUSOPERATIONAL

RUNNING

IDLE

BUSY

OPERATING

BUSY

IDLE

NOT OPERATING

.....

Figure R3-1

Combined State Model

SEMI E99-1104

RELATED INFORMATION 4

NOTICE: This related information is not an official part of SEMI E99 and was derived from the Japanese

Information and Control Committee. This related information was approved for publication by full letter ballot on

January 10, 2003.

R4-1 Application of RF Tag as Carrier ID Tag

R4-1.1 In case that RF Tag is utilized as Carrier Tag for SEMI E99 application, to secure the interoperability among

the CIDRW units for writing / reading the Carrier ID into / out of the RF Tag, some basic consideration should be

taken as follows:

R4-1.1.1 Coincidence of Carrier ID Written and Read in Tag Memory — Fundamentally Carrier ID, which is read

out, should be quite same as written, with no addition.

R4-1.1.2 Caution for Carrier ID Contents Applied to Object ID — Carrier ID as Material ID can be used as Object

ID. But the Space Character (20

) should not be used as the first or the last character of Carrier ID. SEMI E39

restricts these.

R4-1.1.3 Non-Visible Character in Carrier ID — If non-visible ASCII character is found within the specified tag

area, CIDRW shall send out an error (i.e. Execution error) to the upstream controller when “Read ID” service was

executed. The contents of Carrier ID issued by host/upstream controller should be compliant with visible Character.

R4-1.1.4 Location of Carrier ID Field (CID Field) — Carrier ID field shall be located from the first byte to the

maximum byte of Carrier ID in the memory of the Electric Tag. The relation of Carrier ID Offset and Carrier ID

length are shown bellow:

CID Field

First Byte

Maximum Byte of CID

Total Tag Length

141312111009

03 07

NUL

00 1508

ASCII

Address 141312111009

03 07

NUL

00 1508

ASCII

Address

Offset

Length

Do Not Care

CID

Figure R4-1

Example of Carrier ID in Tag (“CID = ABCDE”)

R4-1.1.5 Condition of CarrierIDOffset and CarrierIDLength —

By setting the condition of CarrierIDOffset and

CarrierIDLength, CIDRW can correspond to CarrierID Tag characteristic to device makers already existing, if they

are compliant with the reinforced specification for RF Tag in SEMI E99.

R4-1.1.5.1 The information of the Offset value and Length of Carrier ID should be stored as the CIDRW Attribute.

R4-1.1.5.2 When a CIDRW is installed in the equipment, it needs to set up a condition of CarrirIDOffset and

CarrierIDLength as per user requirement once at least.