semi合集-English.pdf - 第2097页
SEMI E54.12-0701 E © SEMI 2001 3 Manage me nt, C yclic T ra nsmis sion a nd No n-Cyc lic Tra nsmission (or T ransient Tra nsmission). Al so, Application Obj ect Models are specified as “Profiles”. See the CC-Link standar…
SEMI E54.12-0701
E
© SEMI 2001 2
4.2 ISO
1
Standards
7498 OSI — Basic Reference Model for Open Systems
Interconnection
4.3 CC-Link Partner Association
2
CC-Link Specification, Version 1.11 (or later)
5 Terminology
5.1 Abbreviations and Acronyms
5.1.1 CDM — Common Device Model
5.1.2 NCS — Network Communication Standard
5.1.3 OSI — Basic Reference Model for Open Systems
Interconnection (ISO 7498)
5.1.4 SAN — Sensor/Actuator Network
5.1.5 SDM — Specific Device Model
5.2 Definitions from Sensor/Actuator Network
Common Device Model (SEMI E54.1)
5.2.1 Attribute
5.2.2 Behavior
5.2.3 Byte
5.2.4 Common Device Model
5.2.5 Device
5.2.6 Device Manager (DM) Object
5.2.7 Device Model
5.2.8 Instance
5.2.9 Network Communication Standard
5.2.10 Object
5.2.11 Sensor, Actuator and Controller (SAC) Object
5.2.12 Service
5.2.13 Specific Device Model
5.2.14 State Diagram
5.3 Definitions
5.3.1 broadcast polling method — polling to each
station and the data communication are executed by the
same packet, and the data is transmitted to all of the
stations in this method.
5.3.2 cyclic transmission — function to transmit the
data from master station to all stations periodically,
1 ISO - International Organization for Standardization, 1 rue de
Varembe, Case postale 56, CH-1211, Geneva 20, Switzerland
2 CC-Link Partner Association - <www.cc-link.org>
then for each station to transmit the response data to
master station.
5.3.3 intelligent device station — station which can
send cyclic transmission and transient transmission to
master station.
5.3.4 local station — station which can send cyclic
transmission and transient transmission to master
station and other local stations.
5.3.5 master station — station that controls all stations
on CC-Link. One (and only one) master station per
system is required.
5.3.6 profiles — Application Object Model
specifications.
5.3.7 remote device station — station that handles bit
data and word data.
5.3.8 remote I/O station — station that handles only bit
data.
5.3.9 remote station — generic name of remote I/O
station and remote device station.
5.3.10 slave station — generic name of station other
than master station.
5.3.11 station — equipment which can be connected
with CC-Link and is assigned a station number of 0–64.
5.3.12 transient transmission — function to transmit
the non-periodic data generated in master station, local
station, and intelligent device station.
6 Communication Protocol High Level
Structure
6.1 Message transfer is organized in cycles. A message
cycle mainly consists of a request-frame followed by a
corresponding acknowledge/response-frame of the
addressed station.
6.2 A brief description of the CC-Link protocol as it
relates to the ISO 7498 OSI model follows in the
sections below. For protocol efficiency, CC-Link does
not define layers 3 to 6.
NOTE 2: The information contained in this section is for
reference only. It in no way represents specifications for CC-
Link. See related documentation for these specifications.
6.3 Physical Layer - Layer 1 — the Physical Layer
conforms to the EIA RS-485 standard. See the CC-
Link standard for more information.
6.4 Data Link Layer - Layer 2 — the Data Link Layer
conforms to the HDLC standard. See the CC-Link
standard for more information.
6.5 Application Layer - Layer 7 — the Application
Layer defines services and protocols for Network
SEMI E54.12-0701
E
© SEMI 20013
Management, Cyclic Transmission and Non-Cyclic
Transmission (or Transient Transmission). Also,
Application Object Models are specified as “Profiles”.
See the CC-Link standard for more information.
6.6 Version 1.11 of the CC-Link Standard introduces
two methods for request/response messaging.
6.7 Devices that support the CC-Link Transient
Transmission capability, use this method, together with
a messaging protocol to transmit Service Requests and
Responses.
6.8 Devices that do not support the Transient
Transmission capability, use the Cyclic Transmission
method. A protocol is defined for changing the context
of the cyclic data from I/O to a messaging protocol for
Service Requests and Responses.
6.9 See the CC-Link standard for more information.
7 Required Object Types
7.1 This section describes a general mapping of the
SEMI SAN Object Model to the CC-Link environment.
Component definitions are clarified and the mapping of
Attributes, Services and Behaviors are specified.
7.2 Object Model
The Object Model defined in the
CDM is represented in the CC-Link NCS. Specifically,
the DM and SAC objects are mapped.
7.2.1 Section 9 specifies the mapping of SDM Objects
in CC-Link.
7.3 Objects
The required objects of the CDM are
identified here. Additional objects that are contained in
the SDM are given identifiers in the Device Profile.
Section 9 specifies additional mapping information.
7.3.1 Table 1 lists the Object Identifiers specified for
use in protocol messages.
Table 1 Object Identifiers
Object ID Object
0 Invalid
1 DM Object
2 SAC Object
3–n Application Objects as specified in Section 9
7.4 Attributes All attributes are accessible via
Get_Attribute and Set_Attribute services defined in the
sections below.
7.4.1 Attribute Identifiers Every object specified in
the CDM and SDMs uses tags to identify its attributes.
These tags are formatted with letters (identifying the
object) followed by an upper case “A”, followed by a
numerical identifier. The Attribute ID used in the CC-
Link NCS is simply the numerical portion of these tags.
7.5 See Table 2 for a list of DM attributes.
Table 2 DM Object Attribute Identifiers
SEMI CDM
Attribute
ID
CC-Link
Attribute
ID
Attribute
DmA1 1 Device Type
DmA2 2 Standard Revision Level
DmA3 3 Device Manufacturer Identifier
DmA4 4 Manufacturer Model Number
DmA5 5 Software or Firmware Revision
Level
DmA6 6 Hardware Revision Level
DmA7 7 Serial Number
DmA8 8 Device Configuration
DmA9 9 Device Status
DmA12 12 Exception Status
DmA13 13 Exception Detail Alarm
DmA14 14 Exception Detail Warning
DmA15 15 Visual Indicator
DmA16 16 Alarm Enable
DmA17 17 Warning Enable
7.6 Services
7.6.1 Service Identifiers The required services of the
CDM are identified here. Additional services that are
contained in the SDM are given identifiers in the
Device Profile. Table 3 specifies the required services
and ID numbers.
Table 3 Service Identifiers
Service ID Service
0 Invalid
1 Reset
2 Abort
3 Recover
4 Get Attribute
5 Set Attribute
6 Execute
7 Perform Diagnostics
7.6.2 Specified Services
The following sections
define the details associated with each of the services
required by the CDM.
7.6.2.1 Reset
The Reset Request specifies no
parameters. In addition to an explicit Reset Service
Request, CC-Link specifies others methods whereby a
Slave device can be reset.
SEMI E54.12-0701
E
© SEMI 2001 4
7.6.2.2 Abort
The Abort Service Request specifies
no parameters.
7.6.2.3 Recover
The Recover Service Request
specifies no parameters.
7.6.2.4 Get Attribute
The Get Attribute Request
specifies two parameters: the Object ID and the
Attribute ID. Each are currently defined in the range
1–255. Both are expandable to 65,535.
7.6.2.5 Set Attribute
The Set Attribute Request
specifies three parameters: the Object ID, the Attribute
ID and the Attribute Value to set. The Object ID and
the Attribute ID are defined the same as for the Set
Attribute Service. The length of the Attribute Value is
based on the specification of the attribute.
7.6.2.6 Execute
The Execute Service Request
specifies no parameters.
7.6.2.7 Perform Diagnostics
The Perform
Diagnostic Request specifies one parameter: Test ID.
The Test ID parameter is one byte in length.
8 Protocol Compliance
8.1 The CC-Link Partner Association has established a
qualified certification system, with test laboratories in
Japan that include conformance testing and
interoperability testing.
9 Specific Device Model Mappings
9.1 The following sections specify mappings for
Sensor Actuator Network Specific Device Models.
9.2 Mass Flow Device
Reference SEMI E54.3 for a
complete specification of the SDM for Mass Flow
Devices. Accordingly, the following mapping rules
apply to the identification tags for the Objects,
Attributes and Services of this model.
9.2.1 Objects
Consistent with SEMI E54.3 and
Section 7.3 above, the DM and SAC objects are
identified as Object 1 and Object 2, respectively.
9.2.1.1 Table 4 shows the mapping of the SDM Object
Instances specified in SEMI E54.3 (Instance numbers
are listed under heading Inst. in the table) and the CC-
Link Object ID (listed under ID in the table).
Table 4 MFD Object Identifiers
SDM Object
Name
SDM Object ID Inst. ID
Sensor-AI-MF MFD3 1 3
Actuator-AO-MF MFD7 1 4
Controller MFD8 1 5
SISO-Setpoint MFD11 1 6
Sensor-AI-AT MFD4 1 7
9.2.1.2 Additional objects may be defined by the
manufacturer in the Device Profile for a given device.
9.2.2 Attributes
The mapping of Attribute Tags and
Identifiers is defined in Section 7.4.1 for the CDM.
The same method applies here for the SDM.
9.2.3 Services
The mapping of Service Tags and
Identifiers is defined in Section 7.6.1 for the CDM.
The same method applies here for the SDM.
9.3 In-Situ Particle Monitor
Reference SEMI
E54.10 for a complete specification of the SDM for In-
Situ Particle Monitor Devices. Accordingly, the
following mapping rules apply to the identification tags
for the Objects, Attributes and Services of this model.
9.3.1 Objects
Consistent with SEMI E54.10 and
Section 7.3 above, the DM and SAC objects are
identified as Object 1 and Object 2, respectively.
9.3.1.1 Table 5 shows the mapping of the SDM Object
Instances specified in SEMI E54.3 (Instance numbers
are listed under heading Inst. in the table) and the CC-
Link Object ID (listed under ID in the table).
Table 5 ISPM Object Identifiers
SDM Object Name SDM Object ID Inst. ID
Sensor-AI-LCS ISPMD3 1 3
Sensor-AI-SLS ISPMD4 1 4
Sensor-AI-MNS ISPMD5 1 5
Assembly-ISPM#1 ISPMD17 1 6
Assembly-ISPM#2 ISPMD18 1 7
Assembly-ISPM#3 ISPMD19 1 8
Assembly-ISPM#4 ISPMD20 1 9
Assembly-ISPM#5 ISPMD21 1 10
Assembly-ISPM#6 ISPMD22 1 11
Assembly-ISPM#7 ISPMD23 1 12
Assembly-ISPM#8 ISPMD24 1 13
Assembly-ISPM#9 ISPMD25 1 14
Assembly-ISPM#40 ISPMD64 1 15
Sensor-AI-Counter ISPMD16 1 16
Sensor-AI-Counter ISPMD16 n 15 + n
Sensor-AI-Counter ISPMD16 1024 1039