semi合集-English.pdf - 第2320页

SEMI E82-0705 © SEMI 1999, 2005 16 Collection Event Name Event Description Required DVVALs UnitStatusOccurred An Informational Status occurred on a ‘transport unit’. The supplier determines when and what ‘status’ inform …

100%1 / 7923
SEMI E82-0705 © SEMI 1999, 2005 15
Collection Event Name From State To State Required DVVALs
VehicleDepositStarted PARKED
ACQUIRING
DEPOSITING
DEPOSITING
VehicleID
TransferPort
CarrierID
(If Multi-position vehicles)
TransferPortList
CarrierIDList
VehicleDepositCompleted DEPOSITING PARKED VehicleID
TransferPort
CarrierID
(If Multi-position vehicles)
TransferPortList
CarrierIDList
VehicleInstalled REMOVED INSTALLED VehicleID
VehicleRemoved INSTALLED REMOVED VehicleID
VehicleUnassigned ASSIGNED NOT ASSIGNED VehicleID
CommandID
CARRIER STATE TRANSITION EVENTS
CarrierInstalled None INSTALLED VehicleID
CarrierID
CarrierLoc
CommandID
CarrierRemoved INSTALLED None VehicleID
CarrierID
CarrierLoc
CommandID
PORT TRANSFER STATE TRANSITION EVENTS
PortInService None
OUT OF SERVICE
IN SERVICE PortID
PortOutOfService None
IN SERVICE
OUT OF SERVICE PortID
PortTransferBlocked Any TRANSFER BLOCKED PortID
PortReadyToLoad Any READY TO LOAD PortID
PortReadyToUnload Any READY TO UNLOAD PortID
8.3 Non-Transition Collection Event Table
Table 7 Non-Transition Collection Event Table
Collection Event Name Event Description Required DVVALs
OperatorInitiatedAction The operator initiated an action from the
Transport System Controller. The related
State Transition Events defined in Table 6
shall be required after this
“OperatorInitiatedAction” event.
CommandID
CommandType
CarrierID
SourcePort
DestPort
Priority
UnitStatusCleared An Informational Status has been
cleared on a ‘transport unit’. This event
is not required for compliance with the
specification but shall be generated for
every UnitStatusOccurred event that is
generated with a UnitStatusClearable
value of ‘Y’.
UnitID, UnitStatusID, UnitStatusText,
VehicleState, VehicleLocation
The Vehicle variables are only required
if a vehicle based system is being
implemented.
SEMI E82-0705 © SEMI 1999, 2005 16
Collection Event Name Event Description Required DVVALs
UnitStatusOccurred An Informational Status occurred on a
‘transport unit’. The supplier determines
when and what ‘status’ information is to
be supplied to the host. This event is not
required for compliance with the
specification.
UnitID, UnitStatusID, UnitStatusText,
UnitStatusClearable, VehicleState,
VehicleLocation
The Vehicle variables are only required
if a vehicle based system is being
implemented.
9 Variable Data Items
9.1 The purpose of this section is to define the list of variable data item requirements for IBSEM equipment. Values
of these variables will be available to the host via collection event reports and host status queries.
9.2 Requirements
All variable data items defined in GEM and data item restrictions defined in SEMI E30 are required on IBSEM
equipment (according to the GEM capabilities required per §13).
All variable data items in the IBSEM Variable Data Item Dictionary for specific equipment classifications are
required for IBSEM equipment. The data item restrictions are also required.
Some SVs in the Variable Data Item Dictionary are referenced by an “i” subscript (e.g., CarrierID
i
). The “i”
subscript denotes a specific instance of the SV. This is necessary since there is usually more than one instance
of such an SV active in the system at the same time (e.g., if there are 20 carriers active at the same time then “i”
could range from 1 to 20 for CarrierID
i
). Variable Data Items containing the “i” subscript should not have
Variable IDs assigned to them.
All variable data items with a format of ASCII (A) shall be limited to printable characters in the decimal range
of 32 to 126 with the exception of the following non-permitted characters: “*” (decimal 42), “\”(decimal 92).
9.2.1 Variable data items are documented in the IBSEM Variable Data Item Dictionary using the following format:
Variable Name Type Description Class Format Comment
Where:
Variable Name: A unique name for the variable data item.
Type: CV – meaning common variables, variables that are general to all vehicles.
CSV – meaning configuration specific variables.
Description: If class is DVVAL, then the description shall contain a statement of when data is valid in terms of
IBSEM events.
Class: The data type of the item.
Format: < SECS Message Language (SML) mnemonic > acceptable formats are SEMI E5 lists, ASCII,
floating point, unsigned integer or signed integer. A description of “ANY”, indicates that only the above formats
are acceptable and is left to the supplier to decide.
Comments: Any additional information pertinent to the variable name.
9.3 Variable Data Item Types
9.3.1 Equipment Constants (ECV) — The value can be changed by the host using S2F15. The operator may have
the ability to change some or all of the values. The value of equipment constant may be queried at any time by the
host using the S2F13/14 transaction or Stream 6 reports.
9.3.2 Status Variables (SV) — The values are valid at all times. A SV may not be changed by the host or operator,
but may be changed by the equipment. A host or operator command may change an equipment status thus changing
a SV. The value of status variables may be queried by the host at any time using the S1F3/4 or Stream 6 reports.
SEMI E82-0705 © SEMI 1999, 2005 17
9.3.3 Data Variables (DVVAL) — These are variables which are valid upon the occurrence of a specific collection
event, and may or may not be valid at other times depending upon the equipment. An attempt to read a variable data
item when it’s invalid will not result in an error, but the data reported may not have relevant meaning.
9.3.4 Variable Data (V) — This is a class of variable data which includes all the previously defined types of
variables.
9.4 Variable Data Item Dictionary
Table 8 Variable Data Item Dictionary
Variable Name Type Description Class Format Comment
ActiveCarriers CV List current status of all
INSTALLED carriers.
SV L,n
1. <CarrierInfo
1
>
.
.
n. <CarrierInfo
n
>
ActiveTransfers CV List current status of all
ACTIVE TRANSFER
commands.
SV L,n
1. <TransferCommand
1
>
.
.
n. <TransferCommand
n
>
ActiveVehicles CV List current status of all
vehicles available or being
used for TRANSFER
commands.
SV L,n
1. <VehicleInfo
1
>
.
.
n. <VehicleInfo
n
>
CarrierID CV ID of the carrier being moved.
CarrierID must be unique for
each carrier within the TSC.
DVVAL A[1–64] If an Id is created by the
equipment (not obtained via
an id reader, the host
interface, or the user
interface) it must be of the
following format:
UNKNOWNEqpNameSeq
Where:
UNKNOWN are the exact
characters “UNKNOWN”
EqpName is the value of the
EqpName ECV (truncated if
required)
Seq is a unique sequence
identifier determined by the
vendor.
CarrierID
i
CV ID of the i
th
carrier. SV A[1–64] See comment for CarrierID.
CarrierIDList CV The Ids of the Carriers being
moved.
DVVAL L,n
1.<CarrierID
1
>
.
.
n.<CarrierID
n
>
‘n’ is the number of carriers
being simultaneously
transferred.
CarrierInfo CV All database information
associated with a particular
carrier generating an event.
DVVAL L,3
1. <CarrierID>
2. <VehicleID>
3. <CarrierLoc>