semi合集-English.pdf - 第2042页
SEMI E54.9-0303 © SEMI 2000, 2003 3 nection for simple f ield devices. The Modbus/TCP over TCP/IP standard specifies OSI refe rence model layers 1, 2, 3, 4 and 7 specifi cally the physi cal signaling, the media access/da…
SEMI E54.9-0303 © SEMI 2000, 2003 2
4 Referenced Standards
4.1 SEMI Standards
SEMI E39 — Object Services Standard: Concepts,
Behavior, and Services (OSS)
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
4.2 Other Standards
IEEE 802.3 –– Telecommunication and Information
Exchange between System Local and Metropolitan
Networks Specific Requirement Part 3: Carrier Sense
Multiple Access CSMA/CD Method and Physical
Layer Specification, 1998
1
IP RFC 791 — Reference for data transmission
2
ISO 7498 — Basic Reference Model for Open Systems
Interconnection
3
PI-MBUS-300 Rev. E — Modicon Modbus Protocol
Reference Guide, March 1993
4
Specification — Open Modbus/TCP Specification
Version 1.0 March 29, 1999
4
NOTICE: As listed or revised, all documents cited
shall be the latest publications of adopted standards.
5 Terminology
5.1 Terminology that is common to all of the
documents in this SAN standard may also be defined in
the Sensor/Actuator Network standard. Terminology
may be reproduced here which is defined in other SEMI
standards.
5.2 Abbreviations and Acronyms
5.2.1 CDM — Common Device Model
5.2.2 DM — Device Manager (object)
5.2.3 IP — Internet Protocol
5.2.4 NCS — Network Communication Standard
5.2.5 OSI — Open Systems Interconnect
5.2.6 OSS — Object Services Standard
5.2.7 SAC — Sensor, Actuator, Controller (Object)
1 IEEE, 3 Park Avenue, 17th Floor, New York, NY 10016 U.S.A.
tel: 212 419 7900 fax: 212 752 4929. http://www.ieee.org/
2 http://src.doc.ic.ac.uk/computing/internet/rfc/rfc791.txt
3 ISO Central Secretariat, 1, rue de Varembé, Case postale 56,
CH-1211 Genève 20, Switzerland
4 http://www.modicon.com/openmbus/standards/standards.htm
5.2.8 SAN — Sensor/Actuator Network
5.2.9 SDM — Specific Device Model
5.2.10 TCP — Transmission Control Protocol
5.3 Device Component Definitions
5.3.1 As this standard defines the presentation or
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
and the Modbus/TCP standard specifications.
NOTE 1: Column 2 contains an equal sign “=” if the
definition is used exactly as specified in the CDM
specification.
Table 1 Mapping of CDM to NCS Terminology
CDM Term NCS
Equivalent
Modbus/TCP
Equivalent
Device = =
Device Model = =
Object =, Class,
Instance
=, Class,
Instance
Instance = =
Attribute = =
Behavior = =
Service = =
State Diagram = =
Byte = =
Nibble = =
Character String = =
5.4 Modbus/TCP Specific Definitions
5.4.1 class — a set of objects that represent the same
kind of system component. A class is a generalization
of an object. All objects in a class are identical in form
and behavior, but may contain different attribute values
as well as additional attributes and services. Refer to
SEMI E39 for further definition.
5.4.2 master/slave — communication over a Modbus
network, which is referred to as “client/server”, that
provides exclusive control of data by a “master” or
“host” device acting as a “client”. All network input
data is reported exclusively to the host when requested
by the host, and the host has exclusive control over the
states of all network output signals of all nodes acting
as it’s “slaves” or “servers”. Master/Slave communica-
tion provides the typical request/response oriented
network communications.
5.4.3 modbus/TCP — an open protocol established at
The University of Michigan’s Electronics Manufact-
uring Laboratory as a standard means of intercon-
SEMI E54.9-0303 © SEMI 2000, 2003 3
nection for simple field devices. The Modbus/TCP over
TCP/IP standard specifies OSI reference model layers
1, 2, 3, 4 and 7 specifically the physical signaling, the
media access/data link protocols, internetworking
capability, the transport capability of end-to-end
transmission of data, and the application layer.
5.4.4 peer-to-peer — on Modbus/TCP over TCP/IP
networks, messages formatted according to the
Modbus/TCP protocol are embedded into the TCP
packet structure that is used on the TCP/IP network.
The Modbus protocol over TCP/IP supports the
asynchronous or unsolicited bi-directional transmission
of data between nodes. This type of communication is
referred to as peer-to-peer.
6 Communication Protocol High Level
Structure
6.1 The Modbus/TCP protocol over TCP/IP is loosely
based on a five-layer architecture. These layers
constitute a collapsed form of the OSI seven layer
architecture, mapping into the physical, data link,
network, transport, and application layers of the
Reference Model. This section has been formatted to be
aligned with the Basic Reference Model for OSI. The
high-level protocol architecture is shown in Figure 1.
Application Layer Application Layer
Presentation Layer
Session Layer
Transport Layer Transport Layer
Network Layer Network Layer
Data Link Layer Data Link Layer
Physical Layer Physical Layer
Layered View of Modbus/TCP
OSI Reference Model
Figure 1
Layered View of Modbus/TCP Over TCP/IP
NOTE 2: Figure 1 represents a conceptual view of the com-
munication device architecture. Conforming implementations
must implement the services defined in this specification at
each layer and must appear (from the network) to have
implemented this architecture, however, an internal modular
partitioning is not required. Implementations may sacrifice
modularity in order to achieve high performance.
6.1.1 The application layer is specified in the Modicon
Modbus Protocol Reference Guide and provides for the
definition of Modbus applications as a collection of
addressable objects. A subset of these objects may be
addressed over the network (as defined by the
implementation).
6.1.2 In the remainder of this section the protocol
structure is described in more detail in terms of the OSI
seven layer reference model, the object model
environment and network management specifications.
6.2 Physical Layer — The device shall comply with a
physical layer specification identified in the
Modbus/TCP specification. The recommended and
default Modbus/TCP physical layer is IEEE 802.3. If
an accepted physical layer specification other than
IEEE 802.3 is being used, this must be clearly specified
in product literature. Physical layer specification
includes physical signaling (levels and data rates),
transceivers, node isolation, media topology, cable
specifications, network connectors and taps, and power
considerations (load limits, system tolerances, and
power supply options).
6.3 Data Link Layer — The device shall comply with a
data link layer specification of the Modbus/TCP
specification. The recommended and default Modbus/
TCP data link layer is IEEE 802.3. If an accepted data
link layer specification other than IEEE 802.3 is being
used, this must be clearly specified in product literature.
Data link layer specification includes the media access
control mechanism and the logical link control
mechanism.
6.4 Network Layer — The device shall comply with a
network layer specification of the Modbus/TCP specifi-
cation. This specification is the IP or Internet Protocol
as defined in the Modbus/TCP standard specification.
The network layer specification includes network
routing and internetworking.
6.5 Transport (Messaging) Layer — The device shall
comply with the Modbus/TCP standard specification
for the Transport Layer. This specification is the
Transmission Control Protocol as defined in the
Modbus/TCP standard specification. The transport
layer provides transparent transfer of data between
objects in application-entities. Some of the functionality
of this layer is implemented in the Application Layer.
Specific functions include: object data segmentation/re-
assembly (fragmentation) for full message delivery.
6.6 Session Layer — There is no distinct session layer.
6.7 Presentation Layer — There is no distinct
presentation layer. Object addressing and data
presentation in Modbus messages are specified as part
of the Modbus object definitions and object attribute
and service communication protocol. Data byte
transmission ordering is defined in IP RFC 791,
Appendix B.
SEMI E54.9-0303 © SEMI 2000, 2003 4
6.8 Application Layer — The device shall comply with
the Modbus/TCP application layer specification for
defining and addressing objects, including their
attributes and services, and enabling specified network
behavior. The device shall comply with the object
messaging and object model specifications included in
the Modbus/TCP standard specifications. In addition,
the device shall comply with the object specifications
defined in Section 7 of this document.
6.8.1 Object Models — The Modbus/TCP protocol has
been enhanced to provide an object-oriented specifica-
tion for creating, defining, and addressing objects
explicitly, including their attributes and services, and
creating, defining, and communicating object attributes
in an application dependent format. The device shall
comply with the object messaging and object model
specifications included in the Modbus/TCP standard
specification documentation. In addition, the device
shall comply with the object specifications defined in
Section 7 of this document.
6.9 Network Management — The device shall comply
with the Modbus/TCP and TCP/IP network manage-
ment specifications detailed in the Modbus/TCP Stan-
dard Specifications (e.g., physical layer bit rate, master/
slave and peer-to-peer network management, etc.). No
(additional) network management functions are
specified in this document.
7 Required and Optional Object Types
7.1 At this time, the Modbus/TCP standard specifica-
tions do not require any specific objects to exist in a
Modbus/TCP device in order to be a compliant Mod-
bus/TCP device. The Modbus/TCP standard specifica-
tions will be extended to identify and describe objects
(i.e., classes) that must exist in devices that are to be
interoperable and interchangeable on a Modbus/TCP
SEMI compliant SAN network.
7.1.1 The Common Device Model (CDM) specifica-
tion identifies two objects (namely the Device Manager
(DM) and Sensor Actuator Controller (SAC) objects)
that must exist in all SEMI compliant SAN devices.
7.1.2 The required object types for a SEMI compliant
SAN device utilizing the network communication
specification described herein, necessarily comprises, at
minimum, the union of the Modbus/TCP object type
requirements and the CDM specification requirements.
7.1.3 A list of required and optional object types is
given in Table 2. Additional objects that are specified
in a particular SDM are given identifiers in that SDM
specification. Modbus specific presentation information
for these identifiers is given in Section 9 of this
document.
Table 2 Required and Optional Object Types
Object Name Modbus Class
ID/Instance ID
(See Note 1)
CDM Tag
(See Note 2)
Required by
Modbus
(See Note 1)
Required by
CDM
(See Note 2)
Required by
NCS
Device Manager 1/1 DmI0 No Yes Yes
Sensor/Actuator/
Controller
2/1 SacI0 No Yes Yes
Assembly 3/1 through i Asm No No No
Local Link 4/1 through j Lnk No No No
Sensor – AI 33/1 through k Sai No No No
Sensor – EI 34/1 through l Sei No No No
Sensor – BI 35/1 through m Sbi No No No
Actuator – AO 36/1 through n Aao No No No
Actuator – EO 37/1 through o Aeo No No No
Actuator – BO 38/1 through p Abo No No No
Controller 39/1 through q Ca No No No
Application Objects 129 through x/
1 through r
(See Note 3) No No No
NOTE 1: See Modbus specification for further information; values are decimal: “i”, “j”, “k”, “l”, “m”, “n”, “o”, “p”, “q” and “r” represent
arbitrary numbers (greater than or equal to 1) indicating that more than one instance may be supported. “x” is a number greater than or equal to
129 indicating that one or more application object classes may be supported.
NOTE 2: See CDM specification for further information.
NOTE 3: Application Dependent objects as specified in SDM.