semi合集-English.pdf - 第2011页

SEMI E54.7-0999 © SEMI 1999 5 Table 2 Required an d Optional Object Ty pes Object Name S eriplex Class ID/Instance ID (See Note 1) CDM Tag (See Note 2) Required by Serip lex (See Note 1) Required by CDM (See Note 2) Requ…

100%1 / 7923
SEMI E54.7-0999 © SEMI 1999 4
services, and creating, defining and communicating
object attributes in an application dependent format.
The device shall comply with the object messaging and
object model specifications included in the Seriplex
standard specification documentation. In addition the
device shall comply with the object specifications
defined in Section 7 of this document.
6.8.2 Alternate Method for the Communication
Transmission of Attributes — In order to take
advantage of the Seriplex network’s speed and
deterministic characteristics, the Seriplex Standard
Specification details a mechanism of transmitting data
over the network by assigning, in advance, a sequence
of serial frames to be used collectively to deliver
specific sensor and/or actuator attribute data. This
mechanism can be utilized as an alternative to the
object messaging specification of the Seriplex Standard
Specification to implement the behavior associated with
the GetAttribute and SetAttribute services detailed in
Section 7. This mechanism may be used to provide an
efficient and optimum implementation of data
transmission over the network.
6.9 Network Management — The device shall comply
with the Seriplex network management specifications
detailed in the Seriplex Standard Specification (e.g.,
physical layer bit rate, master/slave and peer-to-peer
network management, etc.). No (additional) network
management functions are specified in this document.
7 Required Object Types
7.1 At this time, the Seriplex Standard Specification
does not require any specific objects to exist in a
Seriplex device in order to be a compliant Seriplex
device. The Seriplex Standard Specification will be
extended to identify and describe objects (i.e. classes)
that must exist in devices that are to be interoperable
and interchangeable on a Seriplex SEMI compliant
SAN network.
7.1.1 The Common Device Model specification
identifies two objects (namely the Device Manager
(DM) and Sensor Actuator Controller (SAC) objects)
that must exist in all SEMI compliant SAN devices.
The required object types for a SEMI compliant SAN
device utilizing the network communication
specification described herein, necessarily comprises
the union of the above two requirements.
7.1.2 A list of required and optional object types is
given in Table 2. Additional objects that are specified
in a particular SDM are given identifiers in that SDM
specification; Seriplex specific presentation information
for these identifiers is given in Section 9 of this
document.
7.1.3 An embodiment of a specific device type,
represented as an aggregation of the object types listed
in Table 2, that is compliant with both the CDM
specification and the Seriplex specification, is a
candidate for a SEMI SDM as well as a Seriplex device
definition. Conversely, all SEMI SDM’s and Seriplex
device definitions specified for operation over a SEMI
compliant Seriplex network must be an aggregation of
the object types listed in Table 2, and be compliant with
both the CDM specification and the Seriplex standard
specification.
7.1.4 In the following sections the presentation to the
network of object addressing, object attributes, and
object services for each of the object types listed in
Table 2 is described in detail. Refer to the CDM
standard to determine if the object instance attribute and
service is specified as required or optional. Unless
otherwise noted, all attributes and services described
are instance level attributes (as opposed to class level
attributes). A class level attribute and service is
accessed as instance number zero.
7.1.5 Note that the formats of object attributes and
services are detailed in the CDM document; the
presentation of object attributes and services to the
Seriplex network is detailed in the tables contained in
the following sub-sections and in the Seriplex standard
specification.
7.2 Device Manager (DM) Object –– The DM object
is the device component responsible for managing and
consolidating the device operation. Each device must
support one (and only one) DM object. The DM object
as well as its common required and optional attributes,
services and behavior are described in the CDM
standard. The presentation of object instance attributes
and services to the Seriplex network shall be as
indicated in Table 3.
7.2.1 Note that the formats of DM object attributes are
detailed in the CDM document; the presentation of DM
object attributes to the Seriplex network is detailed in
Table 3 and the Seriplex standard specification; the
format of DM object services is detailed in the CDM
document and the Seriplex standard specification; and
the presentation of the DM object services is detailed in
Table 3 and the Seriplex standard specification.
SEMI E54.7-0999 © SEMI 19995
Table 2 Required and Optional Object Types
Object Name Seriplex Class
ID/Instance ID
(See Note 1)
CDM Tag
(See Note 2)
Required by Seriplex
(See Note 1)
Required by CDM
(See Note 2)
Required by NCS
Device
Manager
1/1 DmI0 No Yes Yes
Sensor/
Actuator/
Controller
2/1 SacI0 No Yes Yes
Assembly 3/1 through i Asm No No No
Local Link 4/1 through j Lnk No No No
Sensor – AI 33/1 through k Sai No No No
Sensor – EI 34/1 through l Sei No No No
Sensor – BI 35/1 through m Sbi No No No
Actuator – AO 36/1 through n Aao No No No
Actuator – EO 37/1 through o Aeo No No No
Actuator – BO 38/1 through p Abo No No No
Controller 39/1 through q Ca No No No
Application
Objects
129 through x/
1 through r
(See Note 3) No No No
NOTE 1: See Seriplex specification for further information; values are decimal; ‘i’, ‘j’, ‘k’, ‘l’, ‘m’, ‘n’, ‘o’, ‘p’, ‘q’ and ‘r’
represent arbitrary numbers (greater than or equal to 1) indicating that more than one instance may be supported. ‘x’ is a number
greater than or equal to 129 indicating that one or more application object classes may be supported.
NOTE 2: See CDM specification for further information.
NOTE 3: Application Dependent objects as specified in SDM.
SEMI E54.7-0999 © SEMI 1999 6
Table 3 DM Object Instance Attributes and
Services
Device Manager Object (DM)
Class ID = 01, Instance ID = 01
Attributes
ID Attribute Name CDM Tag
01 Device Type DmA1
02 Standard Revision Level DmA2
03 Device Manufacturer Identifier DmA3
04 Manufacturer Model Number DmA4
05 Software or Firmware Revision Level DmA5
06 Hardware Revision Level DmA6
07 Serial Number DmA7
08 Device Configuration DmA8
09 Device Status DmA9
12 Exception Status DmA12
13 Exception Detail Alarm DmA13
14 Exception Detail Warning DmA14
15 Visual Indicator DmA15
16 Alarm Enable DmA16
17 Warning Enable DmA17
18 Exception Detail Type DmA18
19 Exception Detail Alarm Queue DmA19
20 Exception Detail Warning Queue DmA20
Services
ID Service Name CDM Tag
01 Reset DmS1
03 Abort DmS2
05 Recover DmS3
07 Get Attribute DmS4
09 Set Attribute DmS5
11 Execute DmS6
13 Perform Diagnostics DmS7
15 Publish Attribute DmS8
17 Lock DmS9
19 Unlock DmS10
21 Get Exception Queue DmS11
23 Clear Exception Queue DmS12
7.3 Sensor, Actuator, Controller (SAC) Object –– The
SAC object is the device component responsible for
coordinating the interaction of the device with the
sensory/actuation/control environment. Each device
must support one (and only one) SAC object. The SAC
object as well as its common required and optional
attributes, services and behavior are described in the
CDM standard. The presentation of object instance
attributes and services to the Seriplex network shall be
as indicated in Table 4.
Table 4 SAC Object Instance Attributes and
Services
Sensor, Actuator, Controller Object (SAC)
Class ID = 02, Instance ID = 01
Attributes
ID Attribute Name CDM Tag
01 Last Calibration Date SacA1
02 Next Calibration Date SacA2
03 Expiration Timer SacA3
04 Expiration Warning Enable SacA4
05 Run Hours SacA5
Services
ID Service Name CDM Tag
01 Reset SacS1
03 Abort SacS2
05 Recover SacS3
07 Get Attribute SacA4
09 Set Attribute SacA5
25 Operate SacA6
27 Restore Default SacA7
29 Publish Attribute SacA8
7.3.1 Note that the format of SAC object attributes is
detailed in the CDM document; the presentation of
SAC object attributes to the Seriplex network is
detailed in Table 3 and the Seriplex standard
specification; the format of SAC object services is
detailed in the CDM document and the Seriplex
standard specification; and the presentation of the SAC
object services is detailed in Table 3 and the Seriplex
standard specification.
7.4 Assembly Object (Asm) –– The Assembly (Asm)
object instances may be used to provide for grouping
more than one attribute from one or more object
instances is a device into a single data structure for
communication over the Seriplex network. The
presentation of object instance attributes and services
shall be as indicated in Table 5.