semi合集-English.pdf - 第2170页

SEMI E54.16-0705 © SEMI 2005 15 DS_ABORT_1 = 5, DS_ABORT_2 = 6, } dev_status_t; 7.3.4.4. 1 The value DS_ABORT_1 corres ponds to the Abort from Idle or Executing state, and the value DS_ABORT_2 co rresponds to the Abort f…

100%1 / 7923
SEMI E54.16-0705 © SEMI 2005 14
specified by the Reporting Mode and Exception Status Reporting Interval configuration properties of the functional
block.
7.3.4 Device Manager Object Configuration Properties — The DM object has configuration properties to control
exception reporting as shown in Table 8. These parameters are Standard Configuration Property Types (SCPTs).
7.3.4.1 The type SCPT_rept_mode(*) contains two four-bit fields specifying the reporting method for alarms and
warning conditions. For example, in Neuron C, the application programming language used on the Neuron Chip, the
declaration of SCPT_rept_mode is as follows:
typedef enum {
REP_REQUEST = 0,
REP_REQ_LATCHED = 1,
REP_EVT_TRIGD_ON = 2,
REP_EVT_TRIGD_ONOFF = 3,
REP_TIME_TRIGD = 4,
REP_EVT_ON_TIME_TRIGD = 5,
REP_EVT_ONOFF_TIME_TRIGD = 6,
} rept_mode_t;
typedef struct {
rept_mode_t alarm_rept_mode :4;
rept_mode_t warn_rept_mode :4;
} SCPT_rept_mode;
7.3.4.2 The type SCPT_exc_sts(*) is a 16-bit value representing times from 0.00 to 655.35 seconds, with a
resolution of 0.01 seconds. This parameter is optional. The default reporting mode is REP_REQUEST.
7.3.4.3 Device Manager Functional Block Output Network Variables — The Device Manager functional block of
the CDM defines the attribute variable Device Status. The data type SNVT_dev_status is an enumeration. One field
of the union is an enumeration, corresponding to the device status attribute defined by the table Device Status
Attribute Values of the CDM. The values of this type are defined in Table 8.
Table 8 Device Status Attribute Variable Enumeration Values
Value Enumeration Tag
0 DS_UNKNOWN
1 DS_INIT_SELFTEST
2 DS_IDLE
3 DS_SELFTEST_EXCPT
4 DS_EXECUTING
5 DS_ABORT_1
6 DS_ABORT_2
7.3.4.4 The application programming language used to declare SNVT_dev_status is as follows:
typedef enum {
DS_UNKNOWN = 0,
DS_INIT_SELFTEST = 1,
DS_IDLE = 2,
DS_SELFTEST_EXCPT = 3,
DS_EXECUTING = 4,
SEMI E54.16-0705 © SEMI 2005 15
DS_ABORT_1 = 5,
DS_ABORT_2 = 6,
} dev_status_t;
7.3.4.4.1 The value DS_ABORT_1 corresponds to the Abort from Idle or Executing state, and the value
DS_ABORT_2 corresponds to the Abort from Initialized/Self Testing or Self Test Exception state of the DM object.
7.3.4.5 The type SNVT_exc_que(*) contains four fields specifying the exception queue and exception elements to
retrieve. For example, in Neuron C, the application programming language used on the Neuron Chip, the declaration
of SNVT_exc_que_mode is as follows:
typedef enum {
REP_ALARM = 0,
REP_WARNING = 1,
} que_t;
typedef struct {
que_t exception_type :1;
int element_number :1;
SNVT_state exception_list[13];
int exception_clear :1;
} SNVT_exc_que;
7.3.4.6 The type SNVT_exc_detail(*) is a sequence of three structures containing arrays. The ANSI/EIA/CEA-
709.1 protocol limits the size of each of these arrays to 9 bytes, so that the type fits within the network variable size
limit of 31 bytes. For example, in Neuron C, the declaration of SNVT_exc_detail is as follows:
typedef struct {
u_char comn_exc_size;
int calibration : 1;
int real_time : 1;
int communic : 1;
int RAM : 1;
int EEPROM : 1;
int EPROM : 1;
int microproc : 1;
int diagnostic : 1;
/*--------------------------*/
int resvd1 : 1;
int reset : 1;
int notify_mfr : 1;
int maintenance : 1;
int power_inputV : 1;
int power_outptV : 1;
int power_resvd : 1;
int power_overC : 1;
u_char comn_exc_dtl[7];
SEMI E54.16-0705 © SEMI 2005 16
/*--------------------------*/
u_char dev_exc_size;
u_char dev_exc_dtl[9];
/*--------------------------*/
u_char mfr_exc_size;
u_char mfr_exc_dtl[9];
} SNVT_exc_detail;
7.4 Sensor, Actuator, and Controller Functional Blocks — These functional blocks are necessarily specific to the
Specific Device Models. The L
ONMARK Application Layer Interoperability Guidelines provide a framework for
defining functional profiles. Specific Device Models may employ these functional profiles, and/or may define their
own functional profiles and Standard Network Variable Types for device-specific requirements. As long as the
functional profile definition guidelines are followed, these profiles may be proposed to the LONMARK
Interoperability Association as new standard profiles.
7.5 Assembly Object (Asm) – The Assembly (Asm) object instances may be used to provide for grouping more
than one attribute from one or more functional blocks in a device into a single data structure for communication over
the LonWorks network. The presentation of Assembly object instance attributes are indicated in Table 9. The
presentation of Assembly object services are indicated in Table 10.
Table 9 Assembly Object Network Variables
Assembly Object (Asm)
Profile ID = 180.81, Instance ID = 01 through i
Sequence
Number
Name Storage Class CDM Tag Standard NV or CP Data Type
1 Data File AsmA1 LONMARK file transfer NVs and
messaging interface.
Table 10 Assembly Object Network Services
Assembly Object (Asm)
Profile ID = 180.81, Instance ID = 01 through i
Service
Request Code
Service Name CDM Tag Request Parameters Result Parameters
4 GetAttribute AsmS4 File transfer read File transfer – Context Specific.
5 SetAttribute AsmS5 File transfer write –
Context Specific
7.6 Local Link Object (Lnk) — The Local Link (Lnk) object instances may be used to “link” an attribute of one
object instance to an attribute of another object instance. Refer to SEMI E54.1 – CDM standard for further
explanation and use of this object. The presentation of Local Link object instance attributes are indicated in Table
11. The presentation of Local Link object services are indicated in Table 12.