semi合集-English.pdf - 第2021页

SEMI E54.8-0305 © SEMI 1999, 2005 3 5.1.6 DP — Decentralized Periphery 5.1.7 DPM1 — DP-Master Class 1 5.1.8 DPM2 — DP-Master Class 2 5.1.9 DPV1 — DP E xtensions Versi on 1 5.1.10 DSAP — Destination SAP 5.1.11 FDL — Field…

100%1 / 7923
SEMI E54.8-0305 © SEMI 1999, 2005 2
4 Referenced Standards
4.1 SEMI Standards
SEMI E39 — Object Services Standard: Concepts, Behavior, and Services
SEMI E54.1 — Standard for Sensor/Actuator Network Common Device Model
SEMI E54.3 — Specification for Sensor/Actuator Network Specific Device Model for Mass Flow Device
SEMI E54.10 — Specification for Sensor/Actuator Network Specific Device Model for an In-Situ Particle Monitor
Device
SEMI E54.11 — Specific Device Model for Endpoint Devices
4.2 ISO Standard
1
ISO 7498 OSI — Basic Reference Model for Open Systems Interconnection
4.3 IEC Standards
2
IEC 61158-2 — Digital data communication for measurement and control – Fieldbus for use in industrial control
systems – Physical Layer specification
IEC 61158-3 — Digital data communication for measurement and control – Fieldbus for use in industrial control
systems – Data Link Layer service definition
IEC 61158-4 — Digital data communication for measurement and control – Fieldbus for use in industrial control
systems – Data Link Layer protocol specification
IEC 61158-5 — Digital data communication for measurement and control – Fieldbus for use in industrial control
systems –Application Layer service definition
IEC 61158-6 — Digital data communication for measurement and control – Fieldbus for use in industrial control
systems – Application Layer protocol specification
IEC 61784-1 — Digital data communication for measurement and control – Profile sets for continuous and discrete
manufacturing relative to fieldbus use in industrial control systems
4.4 PROFIBUS Standards
3
PROFIBUS Profile Guidelines — Part 1: Identification & Maintenance Functions
GSD Specification for PROFIBUS
NOTICE: Unless otherwise indicated, all documents cited shall be the latest published versions.
5 Terminology
5.1 Abbreviations and Acronyms
5.1.1 APDU — Application Protocol Data Unit
5.1.2 AREP — Application Reference Endpoint
5.1.3 ASE — Application Service Element
5.1.4 CDM — Common Device Model
5.1.5 DMPM — Data Link Mapping Protocol Machine
1 International Organization for Standardization, 1 rue de Varembe, Case postale 56, CH-1211, Geneva 20, Switzerland
2 International Electrotechnical Commission, 3 rue de Varembé, Case Postale 131, CH-1211 Geneva 20, Switzerland. Telephone:
41.22.919.02.11; Fax: 41.22.919.03.00, Website: www.iec.ch
3 Profibus International, Haid-und-Neu-Str. 7,76131 Karlsruhe, Germany, Telephone: 49 721 9658 590; Fax: 49 721 9658 589, Website:
www.profibus.com
SEMI E54.8-0305 © SEMI 1999, 2005 3
5.1.6 DP — Decentralized Periphery
5.1.7 DPM1 — DP-Master Class 1
5.1.8 DPM2 — DP-Master Class 2
5.1.9 DPV1 — DP Extensions Version 1
5.1.10 DSAP — Destination SAP
5.1.11 FDL — Fieldbus Data Link
5.1.12 FSPM — Fieldbus Service Protocol Machine
5.1.13 GSD — Generic Data Description
5.1.14 IM — Identification and Maintenance
5.1.15 NCS — Network Communication Standard
5.1.16 OSI — Basic Reference Model for Open Systems Interconnection (ISO 7498)
5.1.17 PDU — Protocol Data Unit
5.1.18 PHY — Physical Layer
5.1.19 SAN — Sensor/Actuator Network
5.1.20 SAP — Service Access Point
5.1.21 SDA — Send Data with Acknowledge
5.1.22 SDM — Specific Device Model
5.1.23 SDN — Send Data with No acknowledge
5.1.24 SRD — Send and Request Data with reply
5.1.25 SSAP — Source SAP
5.2 Terminology Defined in 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
SEMI E54.8-0305 © SEMI 1999, 2005 4
5.3 Terminology Mapping
5.3.1 As this standard defines the mapping of CDM data structure and behavior over a network, it makes use of
many of the terms in SEMI E54.1. Table 1 provides a mapping of fundamental terminology of the CDM document
into this document which uses the terminology of PROFIBUS.
Table 1 Mapping of CDM to NCS Terminology
CDM Term NCS Equivalent
Device DP Slave
Object = (with ASE as class specification)
Instance =
Attribute =
Behavior =
Service =
State Diagram Protocol Machine, State Machine
Byte =, Unsigned8
Nibble Specific field coding
Character String Visible String
5.4 Terminology Defined in PROFIBUS
5.4.1 Device Data Base — an electronic file that provides a clear and comprehensive description of the
characteristics of a device type in a precisely defined format. Also called a GSD File.
5.4.2 Device Profile — a Device Data Base Sheet, which specifies the characteristic features of a device, and a
GSD File.
5.4.3 Data Link Mapping Protocol Machine — a protocol layer that provides an interface to the Application Layer
Protocol Machines by translating service requests and responses between the Application Layer and the Fieldbus
Data Link.
5.4.4 DP-Master Class 1 (DPM1) — a device that polls its assigned DP-Slave devices and handles user data
exchange.
5.4.5 DP-Master Class 2 (DPM2) — a device that interacts as a configuration or diagnostic tool; usually a
programming device.
5.4.6 DP-Slave — a device that is configured, managed, and polled by Master devices; a DP-Slave initiates no
unsolicited communications.
5.4.7 Fieldbus Data Link — the PROFIBUS-DP model for the OSI Layer 2 definition.
5.4.8 GSD File — see Device Data Base.
5.4.9 Service Access Point — an addressable location in a device for the directing of service requests.
5.4.10 Send Data with No acknowledge — a service request that sends data with no reply.
5.4.11 Send and Request Data with reply — a service request that sends data followed by a reply by the receiving
device.
5.4.12 Slave Diagnostics — a method of retrieving a specifically formatted Data Structure that represents the
diagnostic status of a DP-Slave.
6 Communication Protocol High Level Structure
6.1 In a typical remote I/O configuration, single master architectures are used to optimize response times. In lower
speed applications, multi-master architectures are also possible. PROFIBUS-DP uses the polling principle for
communication (Master-Slave method).