semi合集-English.pdf - 第2005页
SEMI E54.6-0997 © SEMI 1997, 2004 11 The type SNVT _exc_detail(*) is a se quence of three structures contain ing arrays. The LonWorks Netwo rk Communi cation Standard li mits the size of each of these arrays to 9 bytes, …
SEMI E54.6-0997 © SEMI 1997, 2004 10
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;
The type SCPT_exc_sts_t(*) 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.4.4 Device Manager Object Output Network
Variables — The Device Manager object has four
output network variables as shown in Table 6. The data
type SNVT_dev_status is an enumeration,
corresponding to the device status attribute defined in
Table 6 of the CDM. The values of this type are defined
in Table 8.
Table 8 Device Status 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
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.
The type SNVT_exc_status(*) is a union of two
structures, depending on whether expanded or basic
exception reporting mode is used. For example, in
Neuron C, the declaration of SNVT_exc_status is as
follows:
typedef union {
struct {
int excpt_method : 1; //set to 0
int dev_spec : 7;
} basic_method;
struct {
int excpt_method : 1; //set to 1
int warn_mfr_spec : 1;
int warn_dev_spec : 1;
int warn_dev_comn : 1;
int resvd : 1;
int alrm_mfr_spec : 1;
int alrm_dev_spec : 1;
int alrm_dev_comn : 1;
} expanded_method;
} SNVT_exc_status;
SEMI E54.6-0997 © SEMI 1997, 2004 11
The type SNVT_exc_detail(*) is a sequence of three
structures containing arrays. The LonWorks Network
Communication Standard 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 resvd1 : 1;
int real_time : 1;
int communic : 1;
int RAM : 1;
int EEPROM : 1;
int EPROM : 1;
int microproc : 1;
int diagnostic : 1;
/*--------------------------*/
int resvd2 : 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];
/*--------------------------*/
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.5 Sensor, Actuator, and Controller Objects — These
objects are necessarily specific to the Specific Device
Models. The LonMark Application Layer
Interoperability Guidelines provide a framework for
defining LonMark objects, together with specifications
of generic sensor and actuator objects. Specific Device
Models may employ these objects, and/or may define
their own objects and Standard Network Variable
Types for device-specific requirements. As long as the
LonMark object definition guidelines are followed,
these device-specific objects may be proposed to the
LonMark Interoperability Association for incorporation
within the LonMark guidelines.
8 Protocol Compliance
A method of testing protocol compliance is required to
verify implementation conformance to the standard. By
virtue of the fact that the intermediate layers of the
LonTalk protocol are implemented in commercially
available silicon, compliance verification is needed
only at the physical and application layers. The
LonMark Interoperability Association provides a
compliance verification service to its members. When
the SEMI Sensor/Actuator Network standard is
incorporated into the LonMark guidelines, this service
may be used to verify compliance with the SEMI
guidelines.
8.1 Interoperability Guidelines Checklist
Applicant Name
Product Name
Standard Program ID
Manufacturer ID
Device Class
Device Subclass
Model Number
Comm. Transceiver
Standard Xcvr Type
Network Connector
Neuron Chip Clock Rate
Oscillator Accuracy
Network Buffer Size
Receive Transactions
SAC Object
Mandatory NVs
Optional NVs
Configuration Properties
Device Manager Object
Mandatory NVs
Optional NVs
Configuration Properties
Functional Profiles
Mandatory NVs
Optional NVs
Configuration Properties
SEMI E54.6-0997 © SEMI 1997, 2004 12
9 Specific Device Type Information
9.1 This section provides for the mapping of network-
visible specific device structure and behavior, specified
in a SEMI standard SDM specification, to the
LonWorks network. Each subsection is devoted to a
single SDM specification (e.g., Section 9.1: Mass Flow
Controller). Additional SDM mappings are added as
subsections to this NCS specification according to
SEMI guidelines and the guidelines of the SEMI SAN
Interoperability standard. Device-type-specific items,
such as overrides to the standard connector, may also be
noted in these subsections.
NOTICE: These standards do not purport to address
safety issues, if any, associated with their use. It is the
responsibility of the user of these standards to establish
appropriate safety and health practices and determine
the applicability of regulatory limitations prior to use.
SEMI makes no warranties or representations as to the
suitability of the standards set forth herein for any
particular application. The determination of the
suitability of the standard is solely the responsibility of
the user. Users are cautioned to refer to manufacturer’s
instructions, product labels, product data sheets, and
other relevant literature respecting any materials
mentioned herein. These standards are subject to
change without notice.
The user’s attention is called to the possibility that
compliance with this standard may require use of
copyrighted material or of an invention covered by
patent rights. By publication of this standard, SEMI
takes no position respecting the validity of any patent
rights or copyrights asserted in connection with any
item mentioned in this standard. Users of this standard
are expressly advised that determination of any such
patent rights or copyrights, and the risk of infringement
of such rights, are entirely their own responsibility.
Copyright by SEMI® (Semiconductor Equipment and Materials
International), 3081 Zanker Road, San Jose, CA 95134. Reproduction o
f
the contents in whole or in part is forbidden without express written
consent of SEMI.