SEMI E99-1000
E
© SEMI 2000, 2001 2
5.2.5 carrier ID reader/writer — a u nit (subsystem)
with the functionality of both a carrier ID reader and a
carrier ID writer.
5.2.6 carrier ID tag (tag, ID tag) — a physical device
for storing Carrier ID and other information. There are
two basic types of tags, read-only tags and read/write
tags.
5.2.7 carrier ID writer — a unit wh ich encodes data
for and writes it to the carrier ID tag.
5.2.8 cassette — an open structure that holds one or
more substrates (SEMI E44).
5.2.9 controller — a system that pro vides control
(performs required operations when certain conditions
occur or when interpreting and acting upon
instructions) and communicates with a higher level
manager. Controllers exist at all levels within a factory.
Examples of controllers include the Multiple ID
Reader/Writer Controller, the Equipment Controller,
and the Load Port Controller.
5.2.10 front-opening unified pod (FO UP) — a box
(that complies with SEMI E47.1) with a non-removable
cassette (so that its interior complies with SEMI E1.9)
and with a front-opening interface (that mates with a
FIMS port that complies with SEMI E62).
5.2.11 fundamental requirements — the requirements
for information and behavior that must be satisfied for
compliance to a standard. Fundamental requirements
apply to specific areas of application, objects, or
services.
NOTE 2: All portions of the carrier ID reader/writer
specification are considered to be fundamental requirements
unless explicitly described as optional. See also optional
requirement.
5.2.12 load port — the interface location on a tool
where wafer carriers are delivered. It is possible that
wafers are not removed from, or inserted into, the
carrier at this location.
5.2.13 message interleaving — the pr actice of sending
a new message request before receiving the reply to an
earlier request.
5.2.14 multiple ID reader/writer controller — a unit
controlling the Reader/Writer function of one or
multiple ID Reader/Writer Heads, communicates the
command/data with the equipment controller or the
equivalent controller such as Load port Controller in the
equipment configuration.
5.2.15 optional capability — a specif ication that is not
required for an implementation to be compliant to a
standard. The supplier developing the CIDWR has the
option to provide these additional capabilities or not
depending on supplier’s product configuration. See also
fundamental requirement.
5.2.16 reader/writer head — a structu red portion
which functions to detect the ID code and/or to write
the ID code. The ID reader/writer unifying a head
function inside its body can be placed as a head. The ID
reader/writer not unifying a head function will be
located separately from the head.
5.2.17 tag fault — any condition that causes errors
when reading or writing to the tag, including power
faults and tag damage.
5.2.18 upstream controller — a contr oller that directs
the Carrier ID Reader/Writer through the communi-
cation interface.
5.3 Data Types
5.3.1 enumerated — may take on on e of a limited set
of possible values. These values may be given logical
names, but they may be represented by any single-item
data type.
5.3.2 form — type of data: positive i nteger, unsigned
integer, integer, floating point (float), enumerated,
boolean, text, formatted text, structure, list, ordered list.
5.3.3 integer — may take on the valu e of any negative
or unsigned integer. Messaging protocol may impose a
limit on the range of possible values.
5.3.4 structure — a specific set of ite ms, of possibly
mixed data types, in a specified arrangement.
5.3.5 text — a character string. Messaging protocol
may impose restrictions, such as length or ASCII
representation.
5.3.6 unsigned integer — may take on the value of any
positive integer or zero. Messaging protocol may
impose a limit on the range of possible values.
6 Conventions
6.1 State Model Methodology
6.1.1 This document uses the Harel state chart
convention for describing dynamic operation of defined
objects. The outline of this convention is described in
an attachment of SEMI E30. The official definition of
this convention is described in “State Charts: A Visual
Formalism for Complex Systems” written by D. Harel
in Science of Computer Programming 8, 1987
1
.
1 Elsevier Science, P.O. Box 945, New York, NY 10159-0945,
http://www.elsevier.nl/homepage/browse.htt
评论0
最新资源