semi合集-English.pdf - 第2344页
SEMI E82-0705 © SEMI 1999, 2005 40 STEP COMMENTS HOST TSC COMMENTS 10. The host may now initiate another TRANSFER command for the carrier(s) from the TRANSFER command that was canceled or allow a PGV to deliver the carri…

SEMI E82-0705 © SEMI 1999, 2005 39
12.3.1.1 The Host wishes to terminate a previously issued TRANSFER command. This could be done so that the
Host could issue another TRANSFER command with new command parameter values or so that a PGV could
transfer the carriers. A Host initiated ABORT scenario would be similar to this scenario except that the remote
command would be ABORT instead of CANCEL and the states when it is accepted by the TSC are different.
STEP COMMENTS HOST TSC COMMENTS
1. The Host desires to CANCEL
a particular TRANSFER
command that it had
previously issued to the
TSC. Outstanding TRANSFER
command has CommandId =
“111111”
2. Host Command Send (HCS)
CANCEL
. COMMANDID = “111111”
The COMMANDID must match
that of the TRANSFER
command that is being
CANCEL’ed
S2,F41->
3. <-S2,F42 Host Command Acknowledge
(HCA)
This is the point where
the TSC would reject the
CANCEL command if not in
the QUEUED or WAITING
state.
4. <-S6,F11 Event Report Send (ERS)
TransferCancelInitiated
. CommandID = “111111”
5. Event Report Acknowledge
(ERA)
S6,F12->
6. <-S6,F11 Event Report Send (ERS)
TransferCancelCompleted
. CommandID = “111111”
7. Event Report Acknowledge
(ERA)
S6,F12->
8. <-S6,F11 Event Report Send (ERS)
VehicleUnassigned
. VehicleID = “CARXX”
. CommandID = “111111”
9. Event Report Acknowledge
(ERA)
S6,F12->

SEMI E82-0705 © SEMI 1999, 2005 40
STEP COMMENTS HOST TSC COMMENTS
10. The host may now initiate
another TRANSFER command
for the carrier(s) from
the TRANSFER command that
was canceled or allow a
PGV to deliver the
carriers.
If there were multiple
carriers in the CANCEL’ed
TRANSFER then the Host may
elect to issue one
TRANSFER command for all
carriers or individual
TRANSFER commands for each
carrier.
The SOURCEPORT in the
resulting TRANSFER
command(s) will be the
same as when the original
TRANSFER was issued since
the carriers have not
moved.
12.3.2 Host-Initiated Override of a TRANSFER Command
12.3.2.1 The Host wishes to override the destination of a previously issued TRANSFER command after the
command has entered the ACTIVE state. This could be done so that the Host could issue another TRANSFER
command with a new destination.
STEP COMMENTS HOST TSC COMMENTS
1. The Host desires to ABORT
a particular TRANSFER
command that it had
previously issued to the
TSC. The outstanding
TRANSFER command has
CommandID = “111111”
2. Host Command Send(HCS)
ABORT
. COMMANDID = “111111”
The COMMANDID must match
that of the TRANSFER
command that is being
ABORT’ed
S2,F41->
3. <-S2,F42 Host Command Acknowledge
(HCA)
This is the point where
the TSC would reject the
ABORT command if it is
not possible for the
transport system to
abort the ACTIVE
TRANSFER command.
4. <-S6,F11 Event Report Send (ERS)
TransferAbortInitiated
. CommandID = “111111”
5. Event Report Acknowledge
(ERA)
S6,F12->

SEMI E82-0705 © SEMI 1999, 2005 41
STEP COMMENTS HOST TSC COMMENTS
6. <-S6,F11 Event Report Send (ERS)
TransferAbort-Completed
. CommandID = “111111”
. CarrierLoc = “LOC1”
. TransferInfo
7. Event Report Acknowledge
(ERA)
S6,F12->
8. <-S6,F11 Event Report Send (ERS)
VehicleUnassigned
. VehicleID = “CARXX”
. CommandID = “111111”
9. Event Report Acknowledge
(ERA)
S6,F12->
10. The host will now initiate
another TRANSFER command
for the carrier(s) from
the TRANSFER command that
was aborted.
11. Enhanced Remote
Command(ERC)
TRANSFER
. COMMANDID = “111112”
. PRIORITY = 5
. REPLACE = 0
. TRANSFERINFO
1
- L,3
1. CARRIERID = “123456”
2. SOURCEPORT =
The current location of
the carrier as sent from
the TSC to the Host in the
TransferCompleted for the
failed TRANSFER command(an
example is a port on a
vehicle). The Host does
not have to know the
difference of whether the
carrier is still on the
car or not to send another
TRANSFER command.
3. DESTPORT = “PORTYY”
S2,F49->
12. <-S2,F50 Enhanced Remote Command
Acknowledge (ERCA)
13. Scenario will now follow
12.1.1
12.3.3 Unsuccessful Completion of a TRANSFER Command
12.3.3.1 The TSC must unsuccessfully complete a previously issued TRANSFER command due to an
unrecoverable transport system error. Although this scenario follows the GEM defined scenario for Alarm handling,
it was included to define the specifics of an IBSEM alarm and subsequent unsuccessful TRANSFER command
completion. The abort of TRANSFER command should be performed by host as described in ¶12.2.2.
STEP COMMENTS HOST TSC COMMENTS
1. <-S5,F1 Alarm Report Send (ARS)
Alarm Set
Unrecoverable Transport
System Error
. ALID
. ALTX