Applications and tools pdf

Trang 1

Configurations for Communication

Communication with Automation Systems

Planning - Configuring - Referencing

Trang 2

Communication with Automation Systems

in the heterogeneous system world (i.e SIMATIC systems communicate with “third party” automation systems) this topic is extremely complex Basic knowledge of the principles behind protocol mechanisms, protocols utilizable with the bus systems, as well as their properties, are just as im-portant as the concrete implementation of a solution approach on the basis

of proven application samples

Specific problems with the communication tasks

From the user’s or planner’s viewpoint, the following questions may often arise when planning the communication solutions:

1 Which Bus System is available as platform for the planned automation

solutions?

2 Which Protocol can be efficiently employed for the planned task on this

bus system and will be supported by the systems to be connected?

3 How will these Protocols be used to achieve effectively the desired automation solution?

4 Which further mechanisms are required to solve the given task

effi-ciently?

Objective of this document

The reader is enabled to face the concrete problems within the planning

and configuration phase in two steps:

1 The main document which prepares and clearly displays the basic information about possible bus systems and protocols being essential for the user

2 A collection of the applications, which are complete within themselves, which takes up typical communication problems and offers praxis-oriented solutions by using chosen protocols and further communication mechanisms

The applications are prepared in a way that, on the one hand, the oriented utilization and the embedding of the used protocols in the own

Trang 3

problem-Communication with Automation Systems

Addressed group of persons

This document and the attached applications as a whole provides both sic knowledge as well as example solutions This teaching material is cre-ated e.g for users …

ba-• Who want to familiarize themselves with the complex topic

“Communication for Automation Systems“ more intensely

• Who need a bus- and protocol oriented overview of all possible constellations within the SIMATIC

• Who need a glossary for the topic “Communication with SIMATIC“ User with these demands may be, e.g.:

• Starters of the SIMATIC communication

• Technically oriented marketing advisors who want to use this teaching material for their presale or planning phase

• Project planners / developers, who are looking for testes modules as basis for their own advancement

Structure of this document

This document is divided into the 4 following parts:

Table 1-1

1 Communication structures in the SIMATIC S7

This chapter gives you an overview of the structural design and the mechanisms of the communication within the SIMATIC

2 Bus-orientated selection aid of applicable protocols

This chapter is intended as selection aid and jump distributor in the protocol summary

3 Description of the available protocols

This chapter comprises a collection of summaries trying to explain in a short and parable form the individual protocols

com-4 A glossary on term explanation

As a conclusion, the terms used in the main document are explained more detailed

Using the hyperlinks

This document has been structured by means of hyperlinks to keep the structure of the main document as linear as possible Each subchapter includes a return jump point to return the next higher level of the hierarchy

The highest level will be reached as soon as chapter 2 Bus-oriented

Se-lection Aid of Usable Protocols has been reached A hyperlink is marked

by means of a blue written and underlined text:

Back to the bus-oriented selection aid of usable protocols

Trang 4

Working with this Document

There are two ways to use this document

• The pragmatic start

The user can read the document as of the first chapter and obtain

an overview of the available interfaces and the applicable protocols

• The problem-oriented start

By means of a concrete problem, a solution for a communication task is sought here

The following steps are performed:

Table 1-2

1 The start into the document is the “Bus-oriented Selection Aid

of Usable Protocols” Here you can find an overview of the

viewed bus systems and their case constellations which can be opened via hyperlinks

2 On the side opened via the selected hyperlink branch, the

available detail constellation is to be carried out or the detail

constellation has already been reached

3 Each detail constellation is represented by an overview of

approx 4 pages It contains:

○ An overview of the connection case on hand

○ An overview of the possible hardware constellations and the protocol used therein

○ An overview of the properties of the usable protocols as well as

○ An estimate of the performance of the used protocol, if available, as well as an overview of the application samples available for this bus or for the protocol

4 In the protocol overview, each of the stated protocols can be branched via hyperlinks This opens a protocol summary outlin-ing the protocol on a further approx 4 pages

Trang 5

Warranty, Liability and Support

We do not accept any liability for the information contained in this ment

docu-Any claims against us - based on whatever legal reason - resulting from the use of the examples, information, programs, engineering and perform-ance data etc., described in this document shall be excluded Such an ex-clusion shall not apply in the case of mandatory liability, e.g under the German Product Liability Act (“Produkthaftungsgesetz”), in case of intent, gross negligence, or injury of life, body or health, guarantee for the quality which goes to the root of the contract (“wesentliche Vertragspflichten”) of a product, fraudulent concealment of a deficiency or breach of a condition However, claims arising from a breach of a condition which goes to the root

of the contract shall be limited to the foreseeable damage which is intrinsic

to the contract, unless caused by intent or gross negligence or based on mandatory liability for injury of life, body or health The above provisions do not imply a change in the burden of proof to your detriment

The Configurations are not binding and do not claim to be complete ing the circuits shown, equipping and any eventuality They do not repre-sent customer-specific solutions They are only intended to provide support for typical applications You are responsible in ensuring that the described products are correctly used

regard-These Configurations do not relieve you of the responsibility in safely and professionally using, installing, operating and servicing equipment When using these Configurations you recognize that Siemens cannot be made li-able for any damage/claims beyond the liability clause described above

We reserve the right to make changes to these Configurations at any time without prior notice If there are any deviations between the recommenda-tions provided in these Configurations and other Siemens publications - e.g Catalogs - then the contents of the other documents has priority

For questions about this document please use the following e-mail-address:

csweb@ad.siemens.de

Trang 6

Table of Contents

1 Communication Structures in the SIMATIC 8

1.1 Internal communication structures (paths) 8

1.2 External communication structures (paths) 9

1.3 Bus systems 10

1.3.1 Two-point connection 11

1.3.2 Multipoint connection 11

1.3.3 Overview of the bus systems available in SIMATIC 12

1.4 Communication display in the SIMATIC family 13

1.4.1 The S7-200 family 13

1.4.2 The S7-300/400 family 15

1.4.3 WinAC-Basis/RTX 17

1.4.4 WinAC-Slot 18

2 Bus-oriented Selection Aid of Usable Protocols 20

2.1 MPI bus 21

2.1.1 CPU connection external 22

2.1.2 CPU connection internal 26

2.2 PROFIBUS 29

2.2.1 PB CPU – CP connection 30

2.2.2 PB CP-CP connection 36

2.2.3 PB CPU – CPU connection 42

2.2.4 PC Broadcast / Multicast 47

2.3 Industrial Ethernet 51

2.3.1 IE CPU – CP connection 52

2.3.2 IE CP – CP connection 56

2.3.3 IE CPU – CPU connection 61

2.3.4 IE Broadcast / Multicast 64

2.4 Serial Interface 67

2.4.1 PtP- connection 69

2.4.2 PtP Multicast / Broadcast 73

2.5 SIMATIC backplane bus 76

2.5.1 Backplane connection 77

3 Protocol Description 81

3.1 Protocols within SIMATIC S7 82

3.1.1 Global data 84

3.1.2 S7 basic communication (MPI, PB_DP) 88

3.1.3 S7 communication (IE, PB, MPI) 98

3.2 Industrial Ethernet 110

3.2.1 ISO Transport protocol 112

3.2.2 TCP protocol 116

3.2.3 ISO on TCP protocol 120

Trang 7

3.3.1 FDL protocol 132

3.3.2 DP protocol 140

3.3.3 FMS protocol 148

3.4 Serial Protocols 153

3.4.1 Protocol RK512 155

3.4.2 Procedure 3964(R) 158

3.4.3 Free ASCII protocol 160

3.4.4 Modbus protocol 162

3.4.5 Data highway protocol 172

4 Compendium / Glossary 178

Trang 8

1.1 Internal communication structures (paths)

Within the SIMATIC, this task is realized by means of a backplane bus

General display of the backplane bus systems

Figure 1-1 The backplane bus system is structured as follows:

Trang 9

P-bus (I/O bus) The P-bus (I/O-bus) is responsible for the data exchange between CPU

and the centralized I/O

Here, it is possible to access data or to transfer data which are stored in the I/O area of the CPs or IP / FMs

1.2 External communication structures (paths)

Introduction

One of the core functionalities in today’s automation world is to coordinate different automation systems with each other This coordination is made via an up-to-date exchange of data between the individual systems

To connect the systems with each other, communication paths are required enabling even the overcoming of larger distances These communication paths present themselves in the form of standardized interfaces offering services for data transfer

General presentation of the external communication structure

Figure 1-2 The external communication structure can be divided as follows:

Trang 10

CPU-internal interfaces are directly at the CPU There they are either directly connected to the associated internal bus (e.g MPI) or directly connected to a proc-essor of the CPU

A direct connection has the advantage that:

• Restrictions by the backplane bus will be avoided

• thus providing a certain performance advance External

interfaces

The external communication interfaces are usually within the station racks or in an expansion rack as a communication module

Some of the communication modules can also be used in the distributed, not intelligent units

A connection of these modules to each other or to a CPU is either made:

• Via the communication bus

• or the I/O bus (Decentralized I/O is also signed to the I/O)

To provide a simple distinctive possibility the main differences of both types

of connection are shown here:

Table 1-3

Two-point connection Multipoint connection

1 connection partner for each

Small protocol effort with comparable

data transmission security

High protocol effort with comparable

data transmission security

High deterministics High deterministics only via high

protocol effort

Trang 11

In case of serial connections, standardized interfaces like RS 232, TTY (20mA) or RS 422/RS485 are usually used The protocols used here are,

for example, ASCII, RK512 or the 3964 R protocol

In case of multipoint connections, several stations are connected with each other via a joint transmission medium in order to exchange data

Figure 1-4 The multipoint connection is the classic case of a bus system Two or more stations use the same transmission medium For example twisted two-wire circuits, tri-axial cables or duplex fiber-optic cables can be used as a transmission medium

Bus systems can be set up as

• Bus / line structures

• Tree structures

• Star structures or

• Ring structures

Trang 12

Main document e-Infoshop Communication using automation systems

1.3.3 Overview of the bus systems available in SIMATIC

In the following table some of the main properties of protocols available in SIMATIC are compared with each other

No (with OLM: Yes) RS 485, optical fiber Shielded TP, optical

31 / 62 Slaves

500 m with Repeater and Extender

No ASI interface line with

247 max 32 per RS 485 segment

V 24 : 10m TTY : 1.000m

Trang 13

The following communication possibilities are available for the S7-200 ily:

fam-Figure 1-5

Trang 14

• As a PPI interface with PPI protocol fo

• As an MPI interface with MPI slave functions for CPU / CPU communication and HMI applications

• As a freely programmable, serial interface supporting the ASCII protocol

The desired operating mode can be set for the CPU Up to two interfaces can be available for each PU

Serial interface (EM 241)

The only serial expansion module of the S7-200 being available

so far is the EM241 It offers a modem interface

The application range of this module is remote diagnostics and the PC communication or the message transmission via SMS / pager The module offers the PPI protocol or a Modbus slave support

Industrial Ethernet

inter-faces (CP 243-1 /

CP 243-1 IT)

The Ethernet CPs 243-1 or 243-1 IT are designed for connecting the S7-200 to the Ethernet These allow for a direct connection of controllers of the S7-300 / S7-400 family as well as of PCs for programming or HMI functions

Moreover, the IT version is able to allow for direct access to the controller via a built-in HTTP-Server functionality or FTP func-tions In addition, a limited E-Mail client function enables sending messages

ASI master interface

(CP 243-2)

The CP 243-2 is an AS-I master of the specification 2.1 It can be used for connecting up to 62 AS-I slaves A direct processing of analog values is possible

PROFIBUS interface

(EM 277)

The expansion module EM277 is used as a valuable DP slave

interface for the PROFIBUS Programming as well as S7 Server

functions can be operated simultaneously via this module

Trang 15

• MPI interface for programming functions or for HMI functions

or for a simple connection between controllers

• PROFIBUS DP (also MPI/DP) interface for connecting

de-central field devices, HMI systems or usable as ming interface

program-• Industrial Ethernet / PROFInet interface for connecting FInet networks, suitable as programming interface or as connection of HMI systems

PRO-Serial interface (e.g CP 440,

Trang 16

Industrial Ethernet (z.B CP 343-1/

transmis-• ISO transport (restricted)

ASI Master (z.B CP 343-2)

Via the AS-I bus it is possible to connect directly simple actuators or sensors of specification 2.1 This version can be used for connect-ing up to 62 AS-I slaves

Trang 17

MPI interfaces (e.g CP 5611)

The MPI interface represents primarily a programming interface Furthermore, it is designed as a dynamic data interface for the ex-change with S7 micro-controllers as well as for the data communica-tion to an HMI application

PROFIBUS interfaces

(e.g CP 5611,

CP 5613)

The PROFIBUS interface of the WinAC is used as PROFIBUS DP

master or as communication interface with other S7 systems via the S7 protocol HMI function is additionally possible There are no

other PROFIBUS standard protocols available in the system

Industrial Ethernet

inter-faces (e.g CP 1611,

CP 1613)

The Industrial Ethernet interface of the WinAC is suitable for changing larger data amounts with other S7 systems It can also be used to program the controller or operate via HM systems

ex-Special features of the WinAC-Basis/RTX

With its position as a mere Soft PLC, the WinAC Basis takes a special

status among the S7 controllers Via the additional software package dustrial Data Bridge” it is also able to use indirectly other communication protocols by means of the OPC server However, out of all the standard functions the WinAC-Basis/RTX is only fixed to the DP and S7 communica-tion

Trang 18

”In-Communication with Automation Systems

CPU-internal interface

The WinAC-Slot offers (CPU 412 or CPU 416) two internal faces in both versions:

inter-• An MPI / DP interface and

• A DP interface Both interfaces can be used as DP master interface The MPI / DP interface can be used either as MPI or DP interface for remote pro-gramming, or for connecting to other S7 controllers or for HMI appli-cations, without having to use another CP

MPI interfaces (e.g CP 5611)

The MPI interface represents primarily a programming interface Furthermore, it can be used as a dynamic data interface for the exchange with S7 micro-controllers as well as for the application as data interface for micro-HMI applications

PROFIBUS interfaces

(e.g CP 5611,

The PROFIBUS interface of the WinAC is used as PROFIBUS DP

master or as communication interface with other S7 systems via the

Trang 19

CP 1613)

The Industrial Ethernet interface of the WinAC is suitable for changing larger data amounts with other S7 systems It can also be used to program the controller or operate via HM systems

ex-Special features of the WinAC-Slot

The WinAC-Slot is a mixture of a mere HW controller and a Soft-PLC By using the Slot CPU as hardware plug-in card (PCI or ISA format) it works

out the PLC program independently from the PC CPU By means of the software package “T-Kit“, an additional software data interface is available enabling a direct data exchange with PC applications

Trang 20

Contents of the selection aid

Table 2-1

Bus system Constellation Description

CPU connection external

CPU connection between two stations MPI Bus

CPU connection internal

CPU connection within a rack without using the backplane bus

PB CPU – CP connection

PROFIBUS communication between the central processing unit and communication processor

PB CP – CP connection

PROFIBUS communication between communication processors

PB CPU – CPU connection

PROFIBUS communication between tral processing units

cen-PROFIBUS

PB Broadcast / cast

Multi-PROFIBUS communication with multicast / broadcast functionality

IE CPU – CP tion

connec-Industrial Ethernet communication tween the central processing unit and communication processor

be-IE CP – CP connection Industrial Ethernet communication

be-tween communication processors

IE CPU – CPU connection

Industrial Ethernet communication tween central processing units

be-Industrial Ethernet

IE Broadcast / Multicast

Industrial Ethernet communication with multicast / broadcast functionality PtP- connection PtP connection between two stations Serial

interface PtP Multicast /

Broad-cast

PtP communication with multicast / cast functionality

broad-SIMATIC backplane bus

Backplane bus nection

con-Backplane bus communication between two stations

Trang 21

constella-Detailed bus description

You will find a detailed bus description of the bus system discussed here in

the document “Selection criteria for networks and services”

http://support.automation.siemens.com/WW/view/en/21045102

Structure of the chapter

The chapter MPI bus deals with the following 2 hardware constellations: Table 2-2

CPU connection external

The CPU connection between two individual lers

control-CPU connection internal

CPU connection within a rack without using the plane bus

back-Overview of the constellations

Each constellation is described by means of the following 4 information units:

• Description of the connection case

• The matrix of the hardware constellations

• The core information of the available protocols

• An overview of the available sample applications for this constellation

Advantages of this consideration

This consideration enables the purposive selection of the hardware lation and out of this the selection of the applicable protocol

constel-All possible hardware constellations within the SIMATIC S7 family will be viewed in each constellation The following overview of protocols enables a direct selection by comparing the functionalities of the applicable protocols

Trang 22

Trang 23

Which protocols can I use with this constellation?

The following table shows all applicable protocols for the respective hardware constellations The following page provides further details of the possible protocols

S7 communication (partner 2 as server) S7 basis communication (partner 2 as server via XPUT / XGET)

S7 communication

global data

S7 basis communication S7 communication (partner 1 as client partner 2 as server) global data

S7 communication

global data

S7 basis communication S7 communication global data

S7 communication

global data

S7 basis communication S7 communication global data

Trang 24

Overview of the properties of the MPI bus protocols

With the following overview you can evaluate the properties of the applicable protocols by means of chosen core properties

Yes Throughout the whole length 8 bytes throughout

the whole length

Evaluation " In case of static connections

In case of dynamic connections

Trang 25

Evaluating the performance of the used protocols

The evaluation of the performance statement of the above table is partly made on the basis of the available measurements resulting from the com-munication examples in the Application Portal and partly on the basis of previous experiences when using protocols

Application samples

For this constellation, “CPU connection external via MPI”, there are several pre-coded examples which are available in the Application Portal

Table 2-5

Application title/ Entry-ID Description

S7 Communication via Profibus CPs with

BSEND / BRECEIVE and several Job

Refer-ences (R_IDs)

Entry-ID: 20987358

This application is an automatic test program to exchange data between two stations on up to 4 R_Ids, respectively via an S7 connection, when operated under stress i.e continuous data exchange between the stations The application can recognize occurring mistakes and can react pur- posively (predetermined)

Client server communication between WinAC

Basis and S7.200 station via S7 communication

(PUT/GET)

Entry-ID: 20987586

This Application describes the synchronization of substations via a server station When requested, the server station transfers up to 3 different data records to the substations

N to 1 synchronization of data in the MPI

net-work via S7 basic communication (X_SEND/

X_RCV)

Entry-ID: 19017849

This Application describes the synchronization of

a system of four S7 300 stations Triggered by means of a digital input, three S7 station send data via a dynamic connection to a defined master

Back to the bus-oriented selection aid

Trang 26

Note

The configuration on hand is a special case The described configuration is ally carried out via the backplane bus connection which can be used, too

Trang 27

usu-Communication with Automation Systems

Trang 28

Overview of the properties of the MPI bus protocols

Yes Throughout the whole length 8 bytes throughout

the whole length

Evaluation " In case of static connection

In case of dynamic connection

Trang 29

The evaluation of the performance statement of the above table is partly made on the basis of the available measurements resulting from the com-munication examples in the Application Portal and partly on the basis of previous experiences when using protocols

For this constellation, “CPU connection external via MPI”, there are several pre-coded examples which are available in the Application Portal

Table 2-8

N to 1 synchronization of data in the MPI

net-work via S7 basic communication (X_SEND/

X_RCV)

Entry-ID: 20989875

This Application describes the synchronization of

a system of four S7 300 stations Triggered by means of a digital input, three S7 station send data via a dynamic connection to a defined master

2.2 PROFIBUS

Introduction

The following chapter shows successively all possible hardware tions enabling a data transfer via the PROFIBUS

constella-Detailed bus description

You will find a detailed bus description of the bus system discussed here in

the document “Selection criteria for networks and services”

http://support.automation.siemens.com/WW/view/en/21045102

Structure of the chapter

The chapter PROFIBUS deals with the following 4 hardware constellations:

Trang 30

PB CPU – CP connection PROFIBUS communication between the central

processing unit and communication processor

PB CP – CP connection PROFIBUS communication between

Overview of the constellations

Each constellation is described by means of the following 4 information units:

• Description of the connection case

• The matrix of the hardware constellations

• The core information of the available protocols

• An overview of the available sample applications for this constellation

Advantages of this consideration

This consideration enables the purposive selection of the hardware lation and out of this the selection of the applicable protocol

constel-All possible hardware constellations within the SIMATIC S7 family will be viewed in each constellation The following overview of protocols enables a direct selection by comparing the functionalities of the applicable protocols

Trang 31

Trang 32

DP communication

S7 basis communication (station 1 DP master, station 2 DP slave) S7 communication

DP communication

S7 communication / DP communication

S7-300 ± DP communication S7 communication / DP

communication

S7-400 ± ± S7 communication S7 communication S7 communication

WinAC-Slot ± ± S7 communication S7 communication S7 communication

WinAC Basis/RTX

(ab V 4.0)

± ± S7 communication S7 communication S7 communication

± = nicht anwendbar

Trang 33

Overview of the properties of the PROFIBUS protocols

Operating system of the controller In the PROFIBUS ASIC implemented

mechanism + level 7 implementation via the user program

bidirectional

1 – 1 bidirectional

1 – 1 unidirectional 1-1 bidirectional

Configuration type Non-configured connection Bilaterally configured Unilaterally configured Bilaterally configured

Connection type Dyn / stat connection Client / Server Stat connection Client / Client Stat connection Client

Evaluation " In case of static connection

In case of dynamic connection

Connection of

old systems ( S5 ) /

third party systems

Trang 34

The evaluation of the performance statement of the above table is made on the basis of the available measurements resulting from the communication examples in the Application Portal and of previous experiences when using protocols Some representative comparison values as an illustration: Table 2-12

Protocol Data

S7 communication BSEND / BRECEIVE

DP communication

Approx 200

bytes

Approx 95 ms Approx 79 ms from master to slave*

Approx 39 ms from slave to master*

* The measured value for the DP protocol is based on a measurement with implemented level 7 edgement via the user program of 2 stations The typical DP cycle time is 3 ms

acknowl-These measurements are based on the following general requirements:

Table 2-13

Refer-ences (R_IDs)

Entry-ID: 20987358

Routing of data records reaching over the

sub-network via a gateway CPU with S7

communi-cation (BSEND/BRECEIVE)

Entry-ID: 20983154

By means of a fully programmed example, this application shows an implementation of a func- tioning routing of data records Via a gateway station, configurable data are sent from one station to the other predefined station which is on another network

Client / server communication with (I) Slaves via

S7 basic communication (I_PUT/ I_GET)

Entry-ID: 20987910

The Application on hand offers a simple, quick and practical learning startup into the client/server specifications of the I_PUT/ I_GET S7 basic communication service and shows how to deal with the configuration and user interfaces in the SIMATIC

Trang 35

Data connection between separate DP systems

via DP communication

This application deals with a cost-effective fer of data between two DP masters by using a

trans-DP slave CP 342-5 The trans-DP additionally receives

a data acknowledgement, which will be evaluated via the application

Trang 36

Trang 37

DP communication

S7-300 ± S7 communication

(loadable PBK functions) FMS communication FDL communication

DP communication

S7 communication (per client/server) FMS communication FDL communication

DP communication

S7-400 ± S7 communication

(loadable PBK functions) FMS communication FDL communication

DP communication

S7 communication (per client/server) FMS communication FDL communication

DP communication

Trang 38

Overview of the properties of the PROFIBUS protocols

On the following pages you will find an overview stating the properties of the applicable protocols You can evaluate these protocols by means of the selected core properties

Operating system of the controller In the PROFIBUS ASIC implemented

mechanism + level 7 implementation via the user program

bidirectional

1 – 1 unidirectional 1-1 bidirectional

Configuration type Non-configured connection Bilaterally configured Unilaterally configured Bilaterally configured

Connection type Dyn / stat connection Client / Server Stat connection Client / Client Stat connection Client

Evaluation " In case of static connections

In case of dynamic connections

Trang 39

Part 2 of the table

Table 2-16

Protocol Service

Data range 1 -240 bytes 1 – 236 bytes 1 – 237 bytes PDU

size*

1 – 233 bytes PDU size*

Consistency Throughout the whole length Throughout the whole length 8 bytes throughout the

whole length

Acknowledgement mechanism

Level 4 is implemented

1 – n unidirectional

Connection type Stat connection Client / Client Stat connection Client / Client Stat connection

Client / Client Server / Client

Data tion suitable for:

connec-Small data amounts Medium data amounts Small data amounts

Perfor- man

Connection of old systems ( S5 ) / third party systems

*= In case of FMS, it is important to consider the usable variable description rather than the one of the usable PDU size

By using structures, up to 76 structure elements can be packed up to a package and this package needs only a small amount of variable descriptions (In this connection see manual: SIMATIC NET NCM S7 for PROFIBUS / FMS)

In case of S7 and depending on the used CP, the amount of the variable description is built up as follows:

Trang 40

Variable descriptions in the S7 S7-300 S7-400

The evaluation of the performance statement of the above table is made on the basis of the available measurements resulting from the communication examples in the Application Portal and of previous experiences when using protocols Some representative comparison values as an illustration:

Table 2-18

Protocol Data

S7 communication BSEND / BRECEIVE

FDL Service SDA

• Bus profile standard

• Two stations at the bus

For this constellation, PROFIBUBS CP to CP connection, the following coded examples have been created which are available in the Application Portal

pre-Table 2-19

Refer-ences (R_IDs)

Entry-ID: 20987358

Data transfer via an FDL connection with SDA

via AG_SEND / AG_RECV

Entry-ID: 20987711

This application shows as to how a data transfer, which can transfer any data amount up to a maximum DB size, can be realized via a

Tiêu đề	Configurations for Communication
Trường học	Siemens AG
Chuyên ngành	Automation Communication Systems
Thể loại	hướng dẫn tập tin PDF
Năm xuất bản	2005

Định dạng
Số trang	185
Dung lượng	1,84 MB