semi合集-English.pdf - 第2549页

SEMI E88-1104 E © SEMI 1999, 2004 46 13.2.3 Carrier ID Errors 13.2.3.1 A carrier ID er ror occurred. See table below fo r possible Carrier ID errors and resolutions. Table 14 Carrier ID Error Scenario s at Stocker Ports …

100%1 / 7923
SEMI E88-1104
E
© SEMI 1999, 2004 45
STEP COMMENTS HOST SC COMMENTS
16. If the ABORT command is issued
by the Host, an unkown carrier
is created in the SC database
at the physical location
res
p
onsible for the error. This
generates a
CarrierInstalledCom
p
leted event
for the newly created carrier.
The newly created carrier is
NOT automatically sent to the
LP of the manual output port.
The host can issue a new
TRANSFER command for the
carrier currently on the crane
as well as the recentl
y
created
unkown carrier.
17. If the operator indicates, via
the stocker console (supplier
option), that the SC should
select another shelf location,
an unknown carrier is created
in the SC database at the
physical location responsible
for the error. This
g
enerates a
CarrierInstalledCom
p
leted event
for the newly created carrier.
The newly created carrier is
NOT automatically sent to the
LP of the manual output port.
The host can issue a new
Transfer command for the
recently created unknown
carrier. The original transfer
command for the carrier on the
crane completes with success at
the other shelf location.
SEMI E88-1104
E
© SEMI 1999, 2004 46
13.2.3 Carrier ID Errors
13.2.3.1 A carrier ID error occurred. See table below for possible Carrier ID errors and resolutions.
Table 14 Carrier ID Error Scenarios at Stocker Ports
ID Error Error Description Input Port Action Intrabay Output Port Action*
Failure ID read fails
Examples of reasons for failure are:
· Bad bar code reader
· Bad bar code label
· Obstruction of bar code
read
· Other
If IDReadFailureOption is ‘Reject’
Option 1.
1. CarrierIDRead event sent.
2. Carrier automatically sent to
LP of manual output port.
3. IDReadError event sent when
carrier arrives at LP of manual
output port.
Option 2 - manual input port only.
1. CarrierIDRead event sent.
2. Stocker automatically sends
carrier back to operator accessible
location of input port(if necessary).
3. IDReadError event sent
Person picks up carrier from
input port with the PGV.
If IDReadFailureOption is
‘HostControlled’.
1. CarrierIDread event sent.
2. CarrierWaitIn event sent with
unkown carrier ID.
3. Host issues Transfer Command.
Either of the following scenarios are
acceptable based upon the supplier’s
option when moving carrier 456.
Option 1:
1. CarrierIDRead event sent.
2. Carrier continues as if there
was no reader and all events
(CarrierWaitOut,
TransferComplete, etc) will be
sent with the ID (456) of the
carrier as if there was no reader
at the port.
3. IDReadError event sent when
carrier arrives at LP of this
output port.
Option 2:
1.
CarrierWaitOut event for 456.
2. CarrierIDRead event for
Unknown carrier.
3. TransferComplete for 456 with
ID failure error.
4. SC automatically deletes carrier
456 from database and sends
CarrierRemoveCompleted event.
5. SC automatically creates
Unknown carrier at the port and
sends event according to Carrier
State Model.
6. Carrier continues to or remains at
LP of this output port with
CarrierWaitOut for created
Unknown carrier at each position.
7. IDReadError event sent when
carrier arrives at LP of this output
port.
SEMI E88-1104
E
© SEMI 1999, 2004 47
ID Error Error Description Input Port Action Intrabay Output Port Action*
Duplicate The carrier ID read results in an ID
that matches another entry already
in the SC database at a different
physical location.
Example at Input – Carrier 123
read at ID reader, but there is
already a database entry for a
carrier with CarrierID 123.
Example at Output – Carrier 456
requested to ID reader but
CarrierIDRead result is 123, but
there is already a database entry for
a carrier with CarrierID 123.
DuplicateIDs are a subset of
unkownIDs with the following
format: UNKNOWNDUP-oldid-
Seq. Where Seq is a unique
sequence identifier.
1. CarrierIDRead event sent for
123.
2. If existing carrier 123 has a
TransferCommand, send
TransferCompleted with
‘Duplicate ID’ ResultCode.
3. SC automatically Deletes carrier
123 from SC database and sends
CarrierRemovedCompleted.
4. SC automatically creates a
DuplicateID carrier at previous
location and sends event according
to Carrier State Model.
5. CarrierWaitIn event for 123 at the
port.
If IDReadDuplicateOption is ‘Reject’
EITHER Option 1:
6a. Carrier 123 automatically sent
to LP of manual output port.
7a. IDReadError event sent for
123 when carrier arrives at LP
of manual output port.
8a. Host or manual maintenance
required to disposition the carrier
that SC thought was 123 that is
now a Duplicate.
OR Option 2 – manual input port
only:
6b. Stocker automatically sends
carrier back to operator
accessible location of input
port(if necessary).
7b. IDReadError event sent.
8b. Person picks up carrier from
input port with the PGV.
9b. Host or manual maintenance
required to disposition the carrier
that SC thought was 123 that is
now a Duplicate.
If IDReadDuplicateOption is
‘HostControlled’:
6c. Host responsible for sending
appropriate Transfer Commands for
both carriers.
If IfReadDuplicateOption is
‘Reject’ or ‘HostControlled’ and
carrier’s previous location is a shelf.
1. CarrierWaitOut event for 456.
2. CarrierIDRead 123 event sent.
3. If carrier ID has a
TransferCommand, send
TransferCompleted with
‘Duplicate ID’ ResultCode.
4. SC automatically deletes
carrier 123 from SC database
and sends
CarrierRemoveCompleted
event.
5. SC automaically creates a
DuplicateID carrier at previous
location and sends event
according to Carrier State
Model.
6. SC automatically deletes
carrier 456 from SC database
and sends
CarrierRemoveCompleted
event.
7. TransferCompleted for 456
with duplicate ID
ResultCode.
8. SC automatically creates an
carrier123 at the port
location and sends
CarrierWaitOut event.
9. Carrier continues to LP of this
output port. (CarrierWaitOut
for 123 at each position.)
10. IDReadError event sent
when carrier arrives at the
LP of this output port.
11. Host or manual maintenance
required to disposition the
carrier that SC thought was
123 (now a duplicate).
Note: The TransferCompleted
events may come anywhere from
step 3 to step 8.