semi合集-English.pdf - 第2900页

SEMI E109-0305 © SEMI 2001, 2005 10 # Previous State Trigger New State Actions Comments 6 READY TO LOAD Manual : “The equipment recognizes the logi cal ind ication of the start of a ma nual load transfer. This trigger is…

100%1 / 7923
SEMI E109-0305 © SEMI 2001, 2005 9
9.5.4 Reticle Pod Load Port Transfer State Transition Table
Table 5 Reticle Pod Load Port Transfer State Transition Definition
# Previous State Trigger New State Actions Comments
1 (no state) System reset. OUT OF
SERVICE
or
IN SERVICE
(History)
This transition is based on what the
current transfer status was prior to system
reset.
Data required to be available for this
event report:
PortID
2 OUT OF
SERVICE
The host or an operator has
invoked the ChangeServiceStatus
service for this load port with a
value of IN SERVICE.
IN SERVICE Reticle Pod Load port is now usable for
transfer.
Data required to be available for this
event report:
PortID
3 IN SERVICE The host or an operator has
invoked the ChangeServiceStatus
service for this load port with a
value of OUT OF SERVICE.
OUT OF
SERVICE
Reticle Pod Load port is now rendered
unusable for transfer. Attempted usage
of the reticle pod load port for reticle pod
transfer after the state transition results in
an alarm.
Data required to be available for this
event report:
PortID
4 IN SERVICE Service: The host or an operator
has invoked the
ChangeServiceStatus service for
this load port with a value of IN
SERVICE.
System Reset: This transition can
be activated by an equipment re-
initialization.
TRANSFER
READY
or
TRANSFER
BLOCKED
This is the default entry into IN
SERVICE. The state is TRANSFER
BLOCKED if the reticle pod, or reticle
pod load port, is not available for pod
transfer. Otherwise, the state is
TRANSFER READY.
Data required to be available for this
event report:
PortID
5 TRANSFER
READY
Service: The host or an operator
has invoked the
ChangeServiceStatus service for
this load port with a value of IN
SERVICE.
System Reset: This transition can
be activated by an equipment re-
initialization.
Failed Transfer: If a transfer fails,
this transition is activated by
transition #10.
READY TO
LOAD
or
READY TO
UNLOAD
When entering the TRANSFER READY
state, if a reticle pod is present, the sub-
state is READY TO UNLOAD, else the
sub-state is READY TO LOAD.
If the state is READY TO LOAD, data
required to be available for this event
report:
PortID
If the state is READY TO UNLOAD,
data required to be available for this
event report:
PortID
PodID
SEMI E109-0305 © SEMI 2001, 2005 10
# Previous State Trigger New State Actions Comments
6 READY TO
LOAD
Manual: “The equipment
recognizes the logical indication of
the start of a manual load transfer.
This trigger is configurable by the
user, exam
p
les are included in table
8.”
Automated: The PIO load transfer
is beginning and the PIO ready
signal is activated.
TRANSFER
BLOCKED
Data required to be available for this
event report:
PortID
7 READY TO
UNLOAD
Manual: The equipment recognizes
a logical indication of the start of
an unload transfer.
Automated: The PIO unload
transfer is beginning and the PIO
ready signal is activated.
TRANSFER
BLOCKED
Data required to be available for this
event report:
PortID
8 TRANSFER
BLOCKED
Manual: The reticle pod unload
transfer has completed, and the
reticle load port is now empty and
ready for load transfer.
Automated: The PIO unload
transfer ends with a PIO complete
signal.
READY TO
LOAD
Data required to be available for this
event report:
PortID
9 TRANSFER
BLOCKED
Manual: Activities using reticles
contained within the pod have
completed the reticle pod is ready
to be removed.
Automated: Handling for reticles
destined for the reticle pod has
completed, or a CancelPod/
CancelPodAtPort service has been
issued, and the reticle pod is ready
to be removed. This is indicated
by a PIO unload request signal.
READY TO
UNLOAD
The reticle pod on the reticle pod load
p
ort can now be unloaded from the reticle
load port to an external entity.
Data required to be available for this
event report:
PortID
PodID
10 TRANSFER
BLOCKED
The transfer was unsuccessful, and
the reticle pod was not loaded or
unloaded.
TRANSFER
READY
The sub-state of TRANSFER READY,
which is decided by transition #5.
Data required to be available for this
event report:
PortID
10 Reticle Pod Object
10.1 Information about a reticle pod is encapsulated as an object. This allows the host to exchange information
with the equipment about one or more specific reticle pods using services defined in SEMI E39, Object Services
Standard. A reticle pod has properties (attributes) that are defined in Table 6, Pod Attribute Definition.
10.2 Object Instantiation
10.2.1 The reticle pod object is a software representation of the reticle pod in the equipment. Under normal
circumstances this object is instantiated by the equipment when the host uses the Bind, ReticleTransferJob, or
PodNotification service or when the equipment successfully reads the PodID from the reticle pod. A reticle pod
object is instantiated by PodID read only if there are no currently existing objects of the same object type with the
PodID just read. A reticle pod object can also be instantiated by either the ProceedWithPod or CancelPod Services
on an UNASSOCIATED port. (This implies a failed PodID read event.) The ContentMap attribute will be an empty
list (a list of zero) when the instantiation is done by PodID read. The SlotMap attribute should be a list consisting of
all slots enumerated as “UNDEFINED” when the reticle pod object is instantiated by PodID read.
SEMI E109-0305 © SEMI 2001, 2005 11
10.2.2 From the host point of view, an object is instantiated if the host is able to query the equipment about that
object, its current state, and other attributes. Once instantiated, the object is considered destroyed (no longer
instantiated) if the response to such queries is “unknown object”.
10.2.3 Summary of reticle pod object instantiation:
1. Bind, ReticleTransferJob, or PodNotification Service;
2. PodID read with no currently existing pod objects having the PodID just read; and
3. ProceedWithPod or CancelPod Service on an UNASSOCIATED port with a pod.
10.2.4 Reticle Pod Object Identifier (ObjID)
10.2.4.1 The purpose of an Object Identifier is to allow references to an object within the system. The object
identifier is created when an object is instantiated and should be unchanged or persistent until the end of the object
lifecycle. The Object Identifier shall be unique at the equipment during lifecycle of the object. The PodID is the
Reticle Pod Object Identifier. The equipment is responsible for ensuring uniqueness of the PodID prior to
instantiation by the bind, pod notification, or ReticleTransferJob service.
10.2.5 Reticle Pod Object Destruction
10.2.5.1 Normally, the Reticle Pod Object reaches the end of its lifecycle when the reticle pod is unloaded from the
equipment. Abnormally, the Reticle Pod Object reaches the end of it’s lifecycle when a CancelBind,
CancelReticleTransferJob, or CancelPodNotification service is executed prior to the reticle pod being loaded, or
when an equipment based pod verification fails following pod instantiation by the bind service.
10.2.5.2 Summary of reticle pod object destruction:
1. A reticle pod is unloaded from the equipment;
2. A CancelBind, CancelReticleTransferJob or CancelPodNotification service is received; and
3. An equipment based verification fails (after the object has been instantiated via the bind services).
10.3 Reticle Pod Attribute Definitions
10.3.1 The following table contains the attributes that are of importance to the host and/or the equipment in order to
manage the history and the reports about the reticle pod object.
10.3.2 REQD Column
10.3.2.1 All attributes in the following table are required to be associated with the reticle pod object. However only
the attributes marked with a “Y” in the REQD column are always required to be maintained and updated by the
equipment. The attributes marked with an “N” in the REQD column are only required to be maintained if they are
provided by the host by either the Bind, PodNotification, ReticleTransferJob or ProceedWithPod Services or if the
equipment has means of determining the attribute values. (For example, if the equipment has a ReticleID reader, the
equipment can determine the ContentMap).
10.3.3 ACCESS Column
10.3.3.1
Even though a value may be marked as RO (read only), the initial value for the attribute may be provided
by the host when attached to either the Bind, PodNotification, ReticleTransferJob or ProceedWithPod services. The
only other time the PodCapacityStatus attributes are updated is at the first ProceedWithPod service.
10.3.4 Pod Attribute Definition Table
Table 6 Pod Attribute Definition
Attribute Name Definition Access Reqd Form
ObjType Object type. RO Y Text equal to “Reticle Pod”.
ObjID Object identifier. RO Y Text 1 to 80 characters equal to the PodID.
Capacity Maximum number of reticles in
pod.
RO Y Positive integer. If a pod arrives at a load port
with no warning the default value is one.