semi合集-English.pdf - 第2167页

SEMI E54.16-0705 © SEMI 2005 12 Sensor/Actuat or/Controller Object (SAC) Profile ID = 00 , Instance ID = 01 Service Request Code Service Name CDM Tag Reque st Parameters Result Parame ters 6 Operate SacS6 Node Object RQ_…

100%1 / 7923
SEMI E54.16-0705 © SEMI 2005 11
may be addressed to an input network variable as a LonTalk NV update message, using the NV selection
mechanism. The confirmation of a SetAttribute (network variable update) is provided by the acknowledged service
of the LonTalk protocol transport layer.
7.1.7 Sequence Numbers — Each network variable in a functional block is identified by means of a self-
documentation string stored in the device’s memory. This string contains the functional block index of the functional
block to which this variable belongs, and the Sequence Number of the network variable within its functional block.
For the LONWORKS NCS, this sequence number is identical to the numerical sequence number specified by the
CDM tag. As an example, using the Device Manager object instance declared as the second object instance in the
device it has an Instance Id of 1. The Device Manager attribute Standard Revision Level has the tag DmA2. The
self-documentation string for this network variable is, therefore, specified as “@1|2.”
7.1.8 Publish Service — The Publish notification service is implicit when an output network variable is updated.
The device propagates the value of the output network variable (equivalent to a read-only attribute) to any input
network variable(s) to which it may be bound. The ANSI/EIA/CEA-709.1 (LONWORKS) protocol only supports
propagation of output network variables. In CDM terminology, this means that only read-only attributes may be
published. If a specific device model requires publication of a read/write attribute, an output network variable whose
value mirrors the value of the input (read/write) network variable may be introduced to the object definition.
7.2 Sensor/Actuator/Controller Object (*) — The SEMI CDM SAC object coordinates the functionality of Sensor,
Actuator, and Controller objects in the device. The SAC object is mapped to the LONMARK Node object functional
block. Each device must support one (and only one) Node object functional block. The SAC functional block as
well as its common required and optional attributes, services and behavior are described in document SEMI E54.1
the CDM standard specification. Extensions to the current SNVT list and LONMARK Interoperability Guidelines are
marked with an asterisk (*).
7.2.1 Extensions to the Node Object functional profile are defined in the LONMARK Interoperability Guidelines,
which form part of the LONMARK Functional Profiles for SEMI SAN-compliant devices based on LONWORKS
technology. Table 4 summarizes the network variables that implement the attributes of the SAC object. Table 5
summarizes the services implemented by the SAC object.
Table 4 Sensor/Actuator/Controller (SAC) Object Network Variables
Sensor/Actuator/Controller Object (SAC)
Profile ID = 00, Instance ID = 01
Sequence
Number
Name Storage Class CDM Tag Standard NV or CP Data Type
1 Last Calibration Date CP SacA1 SCPTlastCalibrationDate (*)
#2
2 Next Calibration Date CP SacA2 SCPTnextCalibrationDate (*)
#2
3 Expiration Timer NVO SacA3 SNVT_time_hour
4 Expiration Warning Enable CP SacA4 SCPTexpirationWarningEnable (*)
#2
5 Run Hours NVO SacA5 SNVT_time_hour
128 Attribute ID
#1
(*)
#2
NVI SacA65 SNVT_member (*)
#2
#1
This input is used to specify an attribute for the Restore Default and Publish Attribute services.
#2
(*) LonMark interoperability extension. Refer to §6.8.3 for further definition.
Table 5 Sensor/Actuator/Controller (SAC) Object Services
Sensor/Actuator/Controller Object (SAC)
Profile ID = 00, Instance ID = 01
Service
Request
Code
Service Name CDM Tag Request Parameters Result Parameters
1 Reset SacS1 Node Object RQ_RESET
2 Abort SacS2 Node Object RQ_ABORT (*)
#2
3 Recover SacS3 Node Object RQ_RECOVER (*)
#2
4 GetAttribute SacS4 Read NV or CP NV or CP Value
5 SetAttribute SacS5 Write NV or CP
SEMI E54.16-0705 © SEMI 2005 12
Sensor/Actuator/Controller Object (SAC)
Profile ID = 00, Instance ID = 01
Service
Request
Code
Service Name CDM Tag Request Parameters Result Parameters
6 Operate SacS6 Node Object RQ_NORMAL
7 Restore Default
#1
SacS7 Node Object RQ_RESTORE (*)
#2
NVO Value
8 Publish Attribute
#1
SacS8 Node Object RQ_PROPAGATE
(*)
#2
NVO Value
#1
These services may use the new Attribute ID input to the Node Object functional block.
#2
(*) LonMark interoperability extension. Refer to §6.8.3 for further definition.
7.3 Device Manager Object (*) — The Device Manager object is the device component responsible for managing
and consolidating the device operation. The Device Manager object is mapped to the LONMARK Node object
functional block. Each device must support one (and only one) Node Object functional block. The DM functional
block as well as its common required and optional attributes, services and behavior are described in SEMI E54.1 the
CDM standard specification. Extensions to the current SNVT list and LONMARK Interoperability Guidelines are
marked with an asterisk (*).
7.3.1 The SEMI CDM Device Manager functional block, which is mapped to the LONMARK Node object, combines
attributes of device self-documentation with an exception reporting mechanism. A new functional profile is,
therefore, defined with the following mandatory configuration parameters, network variables and behaviors. This
functional profile forms part of the LONMARK Functional Profiles for SEMI SAN-compliant devices based on
LONWORKS. Table 6 summarizes the network variables that implement the attributes of the Device Manager
functional block.
Table 6 Device Manager (DM) Object Network Variables
Device Manager Object (DM)
Profile ID = 00, Instance ID = 01
Sequence
Number
Name Storage Class CDM Tag Standard NV or CP Data Type
11 Device Type CP DmA1 SCPTdeviceType (*)
#5
12 Standard Revision Level CP DmA2 SCPTdeviceRevLevel (*)
#5
13 Device Manufacture Identifier CP DmA3 SCPTdeviceManufacturer (*)
#5
14 Manufacturer Model Number CP DmA4 SCPTdeviceModelNumber (*)
#5
15 S/W or F/W Revision Level CP DmA5 SCPTappRevLevel (*)
#5
16 Hardware Revision Level CP DmA6 SCPThardwareRevLevel (*)
#5
17 Serial Number CP DmA7 SCPTserialNumber
18 Device Configuration CP DmA8 SCPTdeviceConfiguration (*)
#5
19 Device Status NVO DmA9 SNVT_dev_status (*)
#5
20 Reporting Mode CP DmA10 SCPT_rept_mode (*)
#5
21 Exception Status Report Interval CP DmA11 SCPT_exc_sts (*)
#5
22 Exception Status NVO DmA12 SNVT_alarm_2
23 Exception Detail Alarm NVO DmA13 SNVT_exc_detail (*)
#5
24 Exception Detail Warning NVO DmA14 SNVT_exc_detail (*)
#5
25 Visual Indicator CP DmA15 SCPTvisualIndicator (*)
#5
26 Alarm Enable NVI DmA16 SNVT_obj_request
27 Warning Enable NVI DmA17 SNVT_obj_request (*-add
RQ_WARNING_NOTIFY_ENABLE
D and
RQ_WARNING_NOTIFY_DISABLE
D)
#5
SEMI E54.16-0705 © SEMI 2005 13
Device Manager Object (DM)
Profile ID = 00, Instance ID = 01
Sequence
Number
Name Storage Class CDM Tag Standard NV or CP Data Type
28 Exception Detail Type CP DmA18 SCPTexceptionDetailType (*)
#5
29 Exception Detail Alarm Queue NVO DmA19 SNVT_exc_detail (*)
#5
30 Exception Detail Warning Queue NVO DmA20 SNVT_exc_detail (*)
#5
31 Date and Time NVO DmA21 SNVT_time_p (*)
#5
32 Date and Time Type CP DmA22 SCPTdateTimeType (*)
#5
66 Test ID
#2
(*)
#5
NVI DmA34 SNVT_test_id (*)
#5
67 Password
#3
(*)
#5
NVI DmA35 SNVT_password (*)
#5
68 Exception Queue
#4
(*)
#5
NVI DmA36 SNVT_exc_que (*)
#5
128 Attribute ID
#1
(*)
#5
NVI DmA33 SNVT_member (*)
#5
#1
This input is used to specify an attribute for the Restore Default and Publish Attribute services.
#2
This input is used to specify a test ID for the Perform Diagnostics service.
#3
This input is used to specify a password for the Unlock service.
#4
This input is used to specify a password for the Get and Clear Exception Queue services.
#5
(*) LonMark interoperability extension. Refer to §6.8.3 for further definition.
7.3.2 Device Manager Functional Block Services — Table 7 summarizes the services implemented by the Device
Manager functional block.
Table 7 Device Manager (DM) Object Services
Device Manager Object (DM)
Profile ID = 00, Instance ID = 01
Service Request
Code
Service Name CDM Tag Request Parameters Result Parameters
1 Reset DmS1 Node Object RQ_RESET
2 Abort DmS2 Node Object RQ_ABORT (*)
#1
3 Recover DmS3 Node Object RQ_RECOVER
(*)
#1
4 GetAttribute DmS4 Read NV or CP NV or CP Value
5 SetAttribute DmS5 Write NV or CP
13 Execute DmS6 Node Object RQ_ENABLE
14 Perform Diagnostics DmS7 Node Object RQ_SELF_TEST
8 Publish Attribute DmS8 Node Object
RQ_PROPAGATE (*)
#1
NVO Value
9 Lock DmS9 Node Object RQ_LOCK (*)
#1
10 Unlock DmS10 Node Object RQ_UNLOCK
(*)
#1
11 Get Exception Queue DmS11 Node Object
RQ_GET_EXC_QUEUE (*)
#1
12 Clear Exception Queue DmS12 Node Object
RQ_CLEAR_EXC_QUEUE
(*)
#1
#1
(*) LonMark interoperability extension. Refer to §6.8.3 for further definition.
7.3.3 The Publish (DmS8) notification service for the Device Manager exception status is implemented when an
RQ_PROPAGATE request is received on the nviRequest input to the Node Object functional block. A specific
network variable may be specified on the SNVT_member input. This causes the value of this network variable to be
propagated across the network to other network variable(s) to which it may be bound. The implementation of the
Device Manager functional block updates the specified output network variable according to the conditions