semi合集-English.pdf - 第1905页

SEMI E54.1-1000 © SEMI 1996, 2000 11 Figure 5 SAC Object I nstance Beh avior* NOTE: Onl y generic behavio r is indicat ed in thi s chart. A complete state ch art necessari ly r equires the incl usion o f device- spec ifi…

100%1 / 7923
SEMI E54.1-1000 © SEMI 1996, 2000 10
7.2.3 SAC Instance Behavior — SAC object instance
behavior that is common to all devices is illustrated in
Figure 5. Associated states and state transitions are
described in Tables 11 and 12. The following also
applies to SAC object behavior:
A SAC object service may be requested internally by
the SAC object.
Upon SAC object instantiation or upon receipt of a
reset request, the SAC responds by entering or staying
in its INITIALIZED state.
Upon receipt of an abort request, the SAC object
responds by entering or staying in its ABORT state.
Upon receipt of a recover request, the SAC object
responds by transitioning to its RECOVERED state if
and only if it is currently in its ABORT state.
Otherwise, it responds with an error indication.
Additional behavior may be exhibited by a SAC object
that is device-specific. A complete definition of this
additional SAC object behavior may be found in an
appropriate sensor/actuator network specific device
model specification.
All SAC services have the same behavior associated
with invalid service requests unless otherwise indicated.
Common service error responses are listed in Appendix
2.
If a Set Attribute request is received over the network
for an attribute that is not network-settable, or if the
value in the SetAttribute request is beyond the specified
range allowed for the value of the specified attribute,
the attribute value is not changed and an error service
response is generated.
When the SAC object instance is INITIALIZED, all
attributes are set to their appropriate initial values (as
indicated in their associated object instance attribute
descriptions). Initial values could correspond to those
retrieved from the device’s non-volatile memory and
reflect, in large part, the values set in a previous
NORMAL OPERATING state.
Additionally, whenever the SAC object instance enters
the INITIALIZED state, it must issue a Reset service
request to all Sensor, Actuator, and Controller object
instances. Each object instance must then respond with
a Pass or Fail response indication upon completion of
its respective INITIALIZING application process. The
SAC object instance must coordinate these responses in
order to determine whether the device is qualified to
enter the OPERATING state. If qualified, an Execute
service request is issued to the DM object instance. If
not qualified, an exception condition is reported to the
DM object instance (see Section 7.3).
When the SAC object instance is recovering from an
ABORT state, all attributes are set to their appropriate
values (as determined by the associated object instance
recovering application process defined by the
manufacturer). Additionally, the SAC object instance
must issue a Recover service request to all Sensor,
Actuator, and Controller object instances. Each object
instance must then respond with a Pass or Fail response
indication upon completion of its respective recovering
application process. The SAC object instance must
coordinate these responses in order to determine whe-
ther the device is qualified to enter the OPERATING
state. If qualified, an Execute service request is issued
to the DM object instance. If not qualified, an exception
condition is reported to the DM object instance.
The SAC object optionally includes an Expiration
Timer attribute. The value of this attribute is decremen-
ted at a rate described by the “ExpirationTimer”
attribute format definition. Whenever the “Expiration-
Timer” attribute is less than or equal to zero, a warning
exception condition exists and is reported to the DM
object instance (utilizing the PublishAttribute service)
provided the “ExpirationWarningEnable” attribute is
set to Enable. When the “ExpirationWarningEnable”
attribute is set to Disable, the “ExpirationTimer”
attribute continues to decrement; however, a warning
exception condition will not be reported to the DM
object instance.
The “ExpirationTimer” attribute will continue to be
decremented to values less than zero. Therefore, a
negative number indicates an elapsed time past
expiration. When this attribute reaches its most negative
value, it maintains this value and no longer decrements.
The “ExpirationTimer” is also maintained by the object
while in the ABORT state. In the RECOVERING state,
the current status of the device is evaluated and any
exception conditions that exist are reported to the DM
object instance.
SEMI E54.1-1000 © SEMI 1996, 200011
Figure 5
SAC Object Instance Behavior*
NOTE: Only generic behavior is indicated in this chart. A complete state chart necessarily requires the inclusion of device-
specific behavior.
* Transitions 4 through 8, 11, and 12 are recursive (i.e., the New State is the same as the Current State (including all nested sub-states)).
Table 11 SAC Object Instance Behavior State Description
State Description
NORMAL
OPERATING
Object instance exists. Object services can be processed.
RUNNING This is the entry sub-state to NORMAL OPERATING. Object instance is not in its ABORT state.
INITIALIZED This is the entry sub-state to NORMAL OPERATING and RUNNING. Object instance exists and has been
initialized. All attributes set to appropriate initial values (as indicated in an appropriate sensor/actuator network
specific device model specification).
RECOVERED Object instance is in an abort recovered state.
OPERATING This represents the entire collection of sub-states within RUNNING except INITIALIZED and RECOVERED.
The further delineation of this sub-state and transition into this sub-state is outside the scope of this document.
ABORT Object instance is in an aborted state; a detailed description of this state is outside the scope of this document.
Table 12 SAC Object Instance Behavior State Transition Matrix*, **
# Current State Trigger New State Action Comment
1 RUNNING Abort request. ABORT Abort. Abort
response.
ABORT state is device-specific.
2 ABORT Recover request. RECOVERED Recover. Recover
response.
RECOVERED state is device-specific.
3 NORMAL
OPERATING
Reset request. RUNNING Reset. Reset
response.
Valid for all sub-states of
NORMAL OPERATING. Move to
RUNNING/INITIALIZED.
4 NORMAL
OPERATING
Invalid service
request.
NORMAL
OPERATING
Error response. Valid for all substates of
NORMAL OPERATING.
SEMI E54.1-1000 © SEMI 1996, 2000 12
5 NORMAL
OPERATING
GetAttribute,
SetAttribute, or
RestoreDefault
request.
NORMAL
OPERATING
Get or Set
appropriate attribute
or restore defaults.
Valid for all substrates of NORMAL
OPERATING.
6 ABORT Abort request,
Operate request.
ABORT Error response. Invalid request in this state.
7 RUNNING Recover request. RUNNING Error response. Recover service can only be invoked while in
ABORT state.
8 RUNNING PublishAttribute. RUNNING Attribute identified
by attribute ID in
PublishAttribute
service is published.
Notification service.
9 INITIALIZED Operate request
or Device-
specific.
OPERATING Device-specific. Behavior associated with this transition may be
further specified in an appropriate sensor/actuator
network specific device model specification.
10 RECOVERED Operate request
or Device-
specific.
OPERATING Device-specific. Behavior associated with this transition may be
further specified in an appropriate sensor/actuator
network specific device model specification.
11 OPERATING Operate request. OPERATING Error response. Invalid request in OPERATING state.
12 ABORT PublishAttribute. ABORT None. Attributes cannot be published while in ABORT
state.
* Transitions 4 through 8, 11, and 12 are recursive (i.e., the New State is the same as the Current State (including all nested sub-states)).
** Note: Only generic behavior is indicated in this table.
7.2.4 Objects Embedded in SAC Object — The object types that are embedded in the SAC object are listed in Table
3. The structure and behavior of instances of these object types are detailed in the remainder of this section.
7.2.4.1 Assembly Object — Assembly object instances may be used to provide a mechanism for grouping more
than one attribute from one or more object instances in a device into a single data structure for communication over
the network.
7.2.4.1.1 Assembly Object Attributes — All required and “common optional” Assembly object attributes are listed
in Table 13.
Table 13 Assembly Object Attributes
Attribute Name Attribute Identifier Access Network Required Form
Data AsmA1 Context-Specific Yes Context-Specific
7.2.4.1.1.1 Data — An attribute which contains the assembled data. The structure of this data is context-specific.
7.2.4.1.2 Assembly Object Services — The Assembly object instance provides two services: GetAttribute and
SetAttribute.
7.2.4.1.2.1 Get Attribute — This service is used to read the value of an object instance attribute over the network.
Table 14 describes the parameters specified for this service.
Table 14 Assembly Object Get Attribute Parameter Definition
Parameter Request/
Indication
Response/
Confirmation
Form Description
Attribute ID M C Network-Specific Attribute Identifier of the attribute whose value is being
requested.
Attribute Value
—
M Context-Specific Value of the attribute requested.
7.2.4.1.2.2 Set Attribute — This service is used to modify the value of an object instance attribute over the network
which has been identified as modifiable. Table 15 describes the parameters specified for this service.