semi合集-English.pdf - 第2096页

SEMI E54.12-0701 E © SEMI 2001 2 4.2 ISO 1 Standar ds 7498 OSI — Basic R eference Model for Open Systems Interconn ection 4.3 CC- Link Pa rtner Asso ciation 2 CC-Link Specif ication, Version 1.11 (or later) 5 Terminology…

SEMI E54.12-0701

SPECIFICATION FOR SENSOR/ACTUATOR NETWORK

COMMUNICATIONS FOR CC-LINK

This specification was technically approved by the Global Information and Control Committee and is the

direct responsibility of the North American Global Information and Control Committee. Current edition

approved by the North American Information and Control Committee on April 30, 2001. Initially available

at www.semi.org May 2001; to be published July 2001.

This standard was editorially modified in September 2001 to correct a typographical error and the omission

of a required disclaimer. Section 2.3 was added and changes were made to Section 7.6.2.6.

1 Purpose

1.1 This specification is part of the SEMI

Sensor/Actuator Network (SAN) suite of standards and

defines a specific communications protocol based on

the CC-Link standard. This Network Communication

Standard (NCS) taken together with the SEMI

Sensor/Actuator Network standard suite and the CC-

Link standard completely and unambiguously defines

an open standard providing an industry specific solution

to off-the-shelf interoperability of networked devices in

semiconductor manufacturing equipment.

1.2 CC-Link is a vendor independent, open device

level network standard. Vendor independence and

openness are guaranteed by the CC-Link Partner

Association.

2 Scope

2.1 This document specifies a SAN communications

standard based on the CC-Link specification that is in

compliance with SEMI E54.1. As such, it specifies the

protocol, services and behavior that compliant

intelligent devices must support in order to interchange

information over this SAN in a method compatible with

SEMI E39.

2.2 In conjunction with a SEMI standard SAN

Common Device Model (CDM) specification and one

or more SEMI standard Specific Device Model (SDM)

specifications (e.g., for a mass flow controller), this

Network Communication Standard (NCS) with the

related CC-Link standard describe the data structures,

interactions and behavior that are characteristic of the

various devices on the network. This composite model

forms a complete interoperability standard for

communications among intelligent sensors, actuators

and controllers in semiconductor manufacturing

equipment.

2.3 This standard does not purport to address safety

issues, if any, associated with its use. It is the

responsibility of the users of this standard to establish

appropriate safety health practices and determine the

applicability or regulatory limitations prior to use.

3 Limitations

3.1 This document specifies a semiconductor

equipment SAN based solely on CC-Link; thus, a

complete specification of this standard necessarily

includes the CC-Link specifications. There are other

semiconductor equipment SAN communications

options. The specifications for these options are not

included here.

3.2 The specifications within are strictly enhancements

that provide additional capabilities over and above

those currently required by CC-Link. Included

throughout this document, primarily in Section 6, is

information paraphrased from the CC-Link

specifications — such as: protocol structure,

capabilities, options and limitations. This information is

provided here for reference only and is not intended to

provide specification definitions. In all such areas, refer

to the CC-Link specification documents for

information. This document is limited to describing

enhancements or limitations to the CC-Link

specification that are imposed by this standard.

3.3 A complete specification of the conformance

testing procedure shall include the CC-Link protocol

conformance testing specification. Conformance

testing shall also include enhancements and limitations

to the CC-Link specification required by this standard.

4 Referenced Standards

NOTE 1: Unless otherwise indicated, all documents cited

shall be the latest published versions.

4.1 SEMI Standards

SEMI E39 — Object Services Standard: Concepts,

Behavior and Services

SEMI E54.1 — Sensor/Actuator Network Common

Device Model

SEMI E54.3 — Specification for Sensor/Actuator

Network Specific Device Model for Mass Flow Device

SEMI E54.12-0701

4.2 ISO

Standards

7498 OSI — Basic Reference Model for Open Systems

Interconnection

4.3 CC-Link Partner Association

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

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

CC-Link

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.