semi合集-English.pdf - 第2329页

SEMI E82-0705 © SEMI 1999, 2005 25 11.3.2 Remote Commands and Associated Host Command Parameters 11.3.2.1 This table desc ribes the allowable comm and parameters (CPNAME) fo r each remote command (RC MD). Equipment shall…

100%1 / 7923
SEMI E82-0705 © SEMI 1999, 2005 24
If additional remote commands are supported then a “remote commands versus valid states” matrix must be
generated for these additional commands.
For additional commands, a table must be generated similar to the remote command descriptions summary.
11.3 Remote Commands Description
11.3.1.1 ABORT — This command terminates the activity of a specific TRANSFER command based on
CommandID while the command is in the ACTIVE state. This command may not be accepted due to mechanical
issues if the vehicle is in a specific condition (e.g., depositing a carrier). The exact conditions surrounding when the
ABORT command is not accepted by the TSC must be documented by the IBSEM equipment supplier.
11.3.1.2 CANCEL — This command terminates the activity of a specific TRANSFER command based on
CommandID while the command is in either the QUEUED or WAITING state. This command must always be
accepted by the TSC when in the QUEUED or WAITING state.
11.3.1.3 PAUSE — This command puts the TSC in the PAUSING state.
11.3.1.4 RESUME — This command puts the TSC in the AUTO state.
11.3.1.5 TRANSFER — This is a SECS-II Enhanced Remote Command instead of a SECS-II Host Command Send
(S2,F49 instead of S2,F41). See the examples in Related Information 1 for details.
11.3.1.5.1 This command is used to perform the entire transfer command for the carrier(s) to be transferred between
transfer ports. The execution of this command will include allocation of a vehicle, acquiring the carrier(s), moving
the carrier(s) to the destination port(s), depositing the carrier(s), and returning the vehicle for other use. The number
of carriers in the TRANSFER command is less than or equal to the number of carriers in the transfer unit (see ¶5.2
for definition of the transfer unit). It is recommended that the Carrier already be at the SOURCEPORT upon the
issue of the TRANSFER command, otherwise, it is possible that the TRANSFER command can fail on “empty
acquire” when no carrier is present on the SOURCEPORT when the acquire is started.
11.3.1.5.2 This command shall not be rejected or denied for the sole reason that a STAGEID in the STATEIDLIST
parameter does not reference the STAGEID of any current STAGE command. The TRANSFER command shall be
processed as if the invalid STAGEID was not present in the message.
11.3.1.6 INFOUPDATE — This is used to associate information with a carrier while in the TSC database. This
command is an optional feature and is not required for compliance. If this command is not supported, then a
HCACK of ‘1’ (Command does not exist) shall be returned. If the carrier does not exist in the TSC database, then a
HCACK of ‘3’ (At least one parameter is invalid) shall be returned.
11.3.1.7 STAGE — This is used to inform the TSC that a transport will be requested in the future. This command
allows, but does not require, the TSC to perform Transfer optimizations. This command is an optional feature and is
not required for compliance. If this command is not supported, then a HCACK of ‘1’ (Command does not exist)
shall be returned. It is also permissible for the command to be accepted and no action taken. The Host is not
required to send this command prior to a TRANSFER. Multiple valid STAGE commands for the same
SOURCEPORT can exist at the same time. A STAGE command becomes invalid once the subsequent TRANSFER
command is received, once the WAITTIMEOUT has expired, or once it has been deleted with STAGEDELETE.
The use of this command may cause premature blocking of sections of the transport system based upon the values of
the timers along with the TSC software and hardware implementations.
11.3.1.8 STAGEDELETE — This command is used to delete STAGE commands. If a STAGEID is specified, then
that STAGE command shall be deleted. If the STAGEID is not specified, (STAGEID cpname parameter is not
included in the message), then all STAGE commands shall be deleted. It can be used in anomaly situations when a
TRANSFER command will not be sent, or prior to sending an updated STAGE command, or during recover
scenarios.
SEMI E82-0705 © SEMI 1999, 2005 25
11.3.2 Remote Commands and Associated Host Command Parameters
11.3.2.1 This table describes the allowable command parameters (CPNAME) for each remote command (RCMD).
Equipment shall support all parameters. The column marked Req/Opt, specifies which parameters are required to be
sent by the host and which parameters may be optionally sent by the host.
Table 11 Allowable Command Parameters
Parameters
Remote Command
Cpname Req/opt Comment
ABORT “COMMANDID” R Must specify the commandID that was used for the TRANSFER
command that is being ABORT’ed.
CANCEL “COMMANDID” R Must specify the commandID that was used for the TRANSFER
command that is being CANCEL’ed.
INFOUPDATE “CARRIERID”
“HostDefined”
R
O
The “HostDefined” cpnames are used to indicate the name of the
data that is to be associated with a carrier. See §12 for example
scenarios. The data associated with a carrier is for display purposes
only and information such as the carrier’s current location and state
cannot be changed with this command.
PAUSE None NA Once received by the TSC, the TSC will queue any TRANSFER
commands until the TSC receives and successfully executes the
RESUME command. Once in the AUTO state the TSC will process
the TRANSFER commands in its queue.
RESUME None N/A Returns the PAUSEd TSC to the AUTO state.
STAGE “STAGEINFO”
“TRANSFERINFO”*
R
R
*STAGE commands are allowed a maximum of |transfer unit|
TRANSFERINFOs.
Any information that is unknown to the Host at the time the STAGE
is sent shall be left blank in the TransferInfo. In some scenarios,
information in the STAGE command may differ from that in the
subsequent TRANSFER command.
STAGEDELETE “STAGEID” O The STAGEID of the corresponding STAGE command to be
deleted.
TRANSFER “COMMANDINFO”
“TRANSFERINFO”*
“STAGEIDLIST”
R
R
O
* TRANSFER commands are allowed a maximum of |transfer unit|
TRANSFERINFOs.
STAGEIDLIST contains the STAGEID of each STAGE command
that this TRANSFER command fulfills.
11.3.3 Host Command Parameters Name and Values
Table 12 Host Command Parameters CPNAMES
Parameter Value
Cpname
Description Range Format
CARRIERID ID of the carrier being moved. A[1–64]
COMMANDID Unique command identifier created by the Host. A[1–64]
COMMANDINFO L,3
COMMANDID
PRIORITY
REPLACE
L,3
DESTPORT Destination port unique identifier. A[1–64]
EXPECTEDDURATI
ON
The amount of time, in seconds, the host expects between
the STAGE command and the subsequent TRANSFER
command.
0-999 U2
SEMI E82-0705 © SEMI 1999, 2005 26
Parameter Value
Cpname
Description Range Format
NOBLOCKINGTIME The amount of time, in seconds, following a STAGE
command that movement past the SOURCEPORT should
not be blocked by a transport unit. This time should not
exceed the ExpectedDuration.
0–999 U2
PRIORITY Remote command priority. 0 is not valid.
1 is the LOWEST
priority, 99 is the
highest priority.
U2
REPLACE Flag to denote a TRANSFER replace carrier. Replace a
carrier already on the port with the one on the vehicle.
Refers to the subsequent TRANSFER command when
used in a STAGE command.
0 is OFF
> 0 is ON
U2
SOURCEPORT Source port unique identifier. A[1–64]
STAGEID The unique STAGE command identifier created by the
host.
A[1–64]
STAGEIDLIST L,n
1. <STAGEID
1
>
2. <STAGEID
2
>
.
.
.
n. <STAGEID
n
>
L,n
The format shall
follow format ‘A’ as
defined for the S2F49
message in SEMI E5.
(The CPNAME
“STAGEID” is NOT
included, only values).
For Example:
L,2
1. “STAGEID
LIST”
2. L,n
1, “Stage 1
2. “Stage2”
n, “StageN”
STAGEINFO L,6
STAGEID
PRIORITY
REPLACE
EXPECTEDDURATION
NOBLOCKINGTIME
WAITTIMEOUT
L,6
TRANSFERINFO L,3
CARRIERID
SOURCEPORT
DESTPORT
L,3
WAITTIMEOUT The amount of time, in seconds, after the SOURCEPORT
is reached by a transport unit and the ExpectedDuration
has elapsed that the STAGE command should be
considered valid by the TSC. Following the WaitTimeout,
the Controller should disregard the STAGE command.
0–999 U2
11.3.4 Remote Commands versus TSC and TRANSFER Command States
11.3.4.1 The following table indicates TSC and TRANSFER Command States where the remote commands are
allowed. This is indicated with a “X” mark. Remote commands act independently of other state models (e.g.,