s71500 Communication v12 Function Manual en-US en-US

� �Communication

___________________

___________________

___________________

___________________

___________________

___________________

___________________

___________________

___________________

___________________

___________________

___________________

___________________

___________________

SIMATIC

S7-1500, ET 200MP, ET 200SPCommunication

Function Manual

01/2013 A5E03735815-01

Preface

Documentation guide 1

Product overview 2

Communications services 3

PG communication 4

HMI communication 5

Open communication 6

S7 communication 7

Point-to-point link 8

Routing 9

Connection resources 10

Connection diagnostics 11

Industrial Ethernet Security (CP 1543-1)

12

Service & Support A

Siemens AG Industry Sector Postfach 48 48 90026 NÜRNBERG GERMANY

A5E03735815-01 Ⓟ 01/2013 Technical data subject to change

Copyright © Siemens AG 2013. All rights reserved

Legal information Warning notice system

This manual contains notices you have to observe in order to ensure your personal safety, as well as to prevent damage to property. The notices referring to your personal safety are highlighted in the manual by a safety alert symbol, notices referring only to property damage have no safety alert symbol. These notices shown below are graded according to the degree of danger.

DANGER indicates that death or severe personal injury will result if proper precautions are not taken.

WARNING indicates that death or severe personal injury may result if proper precautions are not taken.

CAUTION indicates that minor personal injury can result if proper precautions are not taken.

NOTICE indicates that property damage can result if proper precautions are not taken.

If more than one degree of danger is present, the warning notice representing the highest degree of danger will be used. A notice warning of injury to persons with a safety alert symbol may also include a warning relating to property damage.

Qualified Personnel The product/system described in this documentation may be operated only by personnel qualified for the specific task in accordance with the relevant documentation, in particular its warning notices and safety instructions. Qualified personnel are those who, based on their training and experience, are capable of identifying risks and avoiding potential hazards when working with these products/systems.

Proper use of Siemens products Note the following:

WARNING Siemens products may only be used for the applications described in the catalog and in the relevant technical documentation. If products and components from other manufacturers are used, these must be recommended or approved by Siemens. Proper transport, storage, installation, assembly, commissioning, operation and maintenance are required to ensure that the products operate safely and without any problems. The permissible ambient conditions must be complied with. The information in the relevant documentation must be observed.

Trademarks All names identified by ® are registered trademarks of Siemens AG. The remaining trademarks in this publication may be trademarks whose use by third parties for their own purposes could violate the rights of the owner.

Disclaimer of Liability We have reviewed the contents of this publication to ensure consistency with the hardware and software described. Since variance cannot be precluded entirely, we cannot guarantee full consistency. However, the information in this publication is reviewed regularly and any necessary corrections are included in subsequent editions.

Communication Function Manual, 01/2013, A5E03735815-01 3

Preface

Purpose of the documentation This function manual provides you with an overview of the communications options, the CPUs, communications modules and processors of the S7-1500, ET 200MP and ET 200SP systems.

The documentation deals with the following topics:

● Overview of the communications services

● Properties of the communications services

● Overview of the user activities for setting up the communications services

Basic knowledge required The following knowledge is required in order to understand the Function manual:

● General knowledge of automation engineering

● Knowledge of the industrial automation system SIMATIC

● Experience of working with STEP 7 (TIA Portal)

Scope of the documentation This documentation is basic documentation for all products of the S7-1500, ET 200MP and ET 200SP systems. The product documentation is based on this documentation.

Conventions STEP 7: In this documentation "STEP 7" is used as a synonym for "STEP 7 V12 (TIA Portal)" and subsequent versions of the configuration and programming software.

This documentation contains pictures of the devices described. The pictures may differ slightly from the devices supplied.

You should also pay particular attention to notes such as the one shown below:

Note

The notes contain important information on the product, handling the product or on part of the documentation to which particular attention should be paid.

Preface

Communication 4 Function Manual, 01/2013, A5E03735815-01

Additional support You will find information about the technical support available in the appendix Service & Support (Page 79).

The range of technical documentation for the individual SIMATIC products and systems can be found on the Internet (http://www.siemens.com/simatic-tech-doku-portal).

The online catalog and the ordering system are available on the Internet (http://mall.automation.siemens.com).

http://www.siemens.com/simatic-tech-doku-portal�

http://mall.automation.siemens.com/�


Table of contents

Preface ...................................................................................................................................................... 3

1 Documentation guide................................................................................................................................. 7

2 Product overview ....................................................................................................................................... 9

3 Communications services........................................................................................................................ 15

3.1 Overview of communications services.........................................................................................15

3.2 Overview of connection resources...............................................................................................17

3.3 Setting up a connection ...............................................................................................................18

3.4 Data consistency..........................................................................................................................20

4 PG communication .................................................................................................................................. 23

5 HMI communication ................................................................................................................................. 25

6 Open communication............................................................................................................................... 27

6.1 Overview of open communication................................................................................................27

6.2 Protocols for open communication...............................................................................................27

6.3 Instructions for open communication ...........................................................................................29

6.4 Setting up open communication with TCP, ISO-on-TCP, UDP, ISO and FDL ............................32

6.5 Setting up e-mail and FTP ...........................................................................................................37

6.6 Establishment and termination of open communications relations..............................................40

7 S7 communication ................................................................................................................................... 41

8 Point-to-point link ..................................................................................................................................... 51

9 Routing .................................................................................................................................................... 57

9.1 S7 routing.....................................................................................................................................57

9.2 Data record routing ......................................................................................................................61

10 Connection resources.............................................................................................................................. 63

10.1 Occupation of connection resources ...........................................................................................63

11 Connection diagnostics............................................................................................................................ 71

11.1 Connection diagnostics................................................................................................................71

12 Industrial Ethernet Security (CP 1543-1) ................................................................................................. 75

12.1 Firewall.........................................................................................................................................76

12.2 Logging ........................................................................................................................................76

12.3 NTP client.....................................................................................................................................77

12.4 SNMP...........................................................................................................................................77

Table of contents


A Service & Support.................................................................................................................................... 79

Glossary .................................................................................................................................................. 83

Index........................................................................................................................................................ 93


Documentation guide 1

Introduction The documentation of the SIMATIC products has a modular structure and covers all aspects of your automation system.

The complete documentation for the S7-1500, ET 200SP and ET 200MP systems consists of the system manuals, function manuals and manuals of the products.

The STEP 7 information system (online help) also supports you when configuring and programming your automation system.

Overview of the documentation on communication The following table shows an overview of other recommended documentation on the topic of communication.

In the sections of this function manual, you will also find references to specific documentation relating to the topics covered.

Table 1- 1 Documentation on communication

Topic Documentation Most important contents General information on industrial communication

Brochure (http://www.automation.siemens.com/mcms/infocenter/content/en/Pages/order_form.aspx?nodeKey=key_8097497&InfoType=brochures) Industrial Communication

• Bus systems for industry • Devices and supported

communications services

General information on PROFINET

Brochure (http://www.automation.siemens.com/mcms/infocenter/content/en/Pages/order_form.aspx?nodeKey=key_8097497&InfoType=brochures) PROFINET

• Overview • Application examples • Hardware • Software

General information on PROFIBUS

Brochure (http://www.automation.siemens.com/mcms/infocenter/content/en/Pages/order_form.aspx?nodeKey=key_8097497&InfoType=brochures) PROFIBUS

• Overview • Application examples • Hardware • Software

STEP 7 (TIA Portal) STEP 7 Professional V12 online help

• Configuring and programming with the engineering software

http://www.automation.siemens.com/mcms/infocenter/content/en/Pages/order_form.aspx?nodeKey=key_8097497&InfoType=brochures�















Documentation guide


Topic Documentation Most important contents Networks Manual SIMATIC NET: Twisted-

Pair and Fiber-Optic networks (http://support.automation.siemens.com/WW/view/en/8763736)

• Ethernet networks • Network configuration • Network components

Security Industrial Ethernet Security (http://support.automation.siemens.com/WW/view/en/56577508) manual

• Overview and description of the security functions in Industrial Ethernet

PROFINET PROFINET with STEP 7 V12 (http://support.automation.siemens.com/WW/view/en/49948856) function manual

• PROFINET basics • PROFINET functions • PROFINET diagnostics

System description S7-1500 automation system (http://support.automation.siemens.com/WW/view/en/59191792) system manual

• Application planning • Installation • Connecting • Commissioning

Modules of the S7-1500 automation system

Manuals for the S7-1500 (http://support.automation.siemens.com/WW/view/en/56926743) product family

• Interrupt, error and system alarms

• Technical specifications (including communications services)

SIMATIC manuals All current manuals for the SIMATIC products are available for download free of charge from the Internet (http://www.siemens.com/simatic-tech-doku-portal).

http://support.automation.siemens.com/WW/view/en/8763736�










http://www.siemens.com/simatic-tech-doku-portal�


Product overview 2

CPUs, communications modules and processors of the S7-1500, ET 200MP and ET 200SP systems provide you with interfaces for communication via PROFINET, PROFIBUS and a point-to-point link.

CPUs, communications modules and communications processors in S7-1500 PROFINET and PROFIBUS DP interfaces are integrated in the S7-1500 CPUs. The CPU 1516-3 PN/DP for example has two PROFINET interfaces and one PROFIBUS DP interface. Other PROFINET and PROFIBUS DP interfaces are available by using communications modules (CM) and communications processors (CP).

① PROFINET interfaces ② PROFIBUS DP interface

Figure 2-1 Interfaces of the CPU 1516-3 PN/DP

Product overview


Interfaces of communications modules Interfaces of communications modules behave in exactly the same way as integrated interfaces of S7-1500 CPUs of the same interface type (for example PROFIBUS DP). They are used to expand the CPU with suitable interfaces (for example CM 1542-5 with a PROFIBUS DP interface).

① PROFIBUS DP interface

Figure 2-2 PROFIBUS DP-Interface of the CM 1542-5

Product overview


Interfaces of communications processors Interfaces of communications processors provide different functionalities compared with the integrated interfaces of the S7-1500 CPUs. CPs allow special applications, for example the CP 1543-1 provides Industrial Ethernet security functions for protecting PROFINET networks via its PROFINET interface.

① PROFINET interface

Figure 2-3 PROFINET-Interface of the CP 1543-1

Product overview


Interfaces of communications modules for point-to-point links The communications modules for point-to-point links provide communication via their RS-232, RS-422 or RS-485 interfaces, for example Freeport or Modbus communication.

① Interface for point-to-point linking

Figure 2-4 Interface for point-to-point linking of the CM PtP RS422/485 BA

Product overview


Interfaces of interface modules PROFINET and PROFIBUS DP interfaces of interface modules (IM) in the ET 200MP and ET 200SP are used to connect the distributed I/O ET 200MP and ET 200SP to PROFINET or PROFIBUS.

① PROFINET interfaces

Figure 2-5 PROFINET interfaces IM 155-5 PN ST (ET 200MP) and IM 155-6 PN ST (ET 200SP)

Communications services The communications services described below use the interfaces and communications mechanisms provided by the system via CPUs, communications modules and processors.

Product overview



Communications services 33.1 Overview of communications services

Selecting the communication service Depending on your automation task, various communications services are available. The selection of the communications service influences the following:

● The functionality available

● The time at which the connection is established

● The activities you need to perform (for example configuring connections, programming instructions)

Overview of communication services The table below is an overview of the communications services provided.

Table 3- 1 Communications services

Via interface: Communication service Functionality

PN DP serial PG communication On commissioning, testing, diagnostics X X - HMI communication On operator control and monitoring X X - Open communication using TCP/IP Data exchange via PROFINET with the TCP/IP

protocol With connection configuration: Instructions TSEND_C/TRCV_C or TSEND/TRCV Without connection configuration: Instructions TCON, TSEND, T_RCV, T_DISCON or TSEND_C and TRCV_C

X - -

Open communication using ISO-on-TCP Data exchange via PROFINET with the ISO-on-TCP protocol With connection configuration: Instructions TSEND_C/TRCV_C or TSEND/TRCV Without connection configuration: Instructions TCON, TSEND, T_RCV, T_DISCON or TSEND_C and TRCV_C

X - -

Communications services 3.1 Overview of communications services


Via interface: Communication service Functionality

PN DP serial Open communication with UDP Data exchange via PROFINET with the UDP

protocol With connection configuration: Instructions TSEND_C/TRCV_C or TSEND/TRCV Without connection configuration: Instructions TCON, TSEND, T_RCV, T_DISCON or TSEND_C and TRCV_C

X - -

Open communication via ISO (only CPs with PROFINET interface)

Data exchange via PROFINET with the ISO protocol With connection configuration: Instructions TSEND_C/TRCV_C or TSEND/TRCV

X - -

E-mail Sending process alarms via e-mail With the user program: Instruction TMAIL_C

X - -

FTP (only CPs with PROFINET interface)

File management and file access via FTP (File Transfer Protocol); CP can be FTP client and FTP server FTP client via user program: Instruction FTP_CMD

X - -

Fetch/Write (only CPs with PROFINET interface)

Server services via TCP/IP, ISO-on-TCP and ISO Via special instructions for Fetch/Write

X - -

Open communication via FDL (only CMs with DP interface)

Data exchange via PROFIBUS with the FDL protocol With connection configuration: Instructions TSEND_C/TRCV_C or TSEND/TRCV

- X -

S7 communication Data exchange client/server or client/client With connection configuration: Instructions PUT/GET, BSEND/BRCV or USEND/URCV

X X -

Point-to-point link Data exchange via point-to-point with Freeport, 3964 (R), USS or Modbus protocol Via special instructions for PtP, USS or Modbus

- - X

Web server Data exchange via the Internet, for example for diagnostics

X - -

SNMP (Simple Network Management Protocol)

Data exchange via standard protocol SNMP, for network diagnostics and parameter assignment

X - -

Via NTP (Network Time Protocol); CPU is client X - - Time-of-day synchronization CPU is time master or time slave - X -

Communications services 3.2 Overview of connection resources


Further information ● You will find the detailed description of the communications services in this manual

starting at section PG communication (Page 23).

● You will find information about the Fetch/Write services in the STEP 7 online help.

● You will find the description of the Web server functionality in the function manual Web server (http://support.automation.siemens.com/WW/view/en/59193560).

● You will find information about the standard protocol SNMP on the Service & Support pages on the Internet (http://support.automation.siemens.com/WW/view/en/15166742).

● You will find information on time-of-day synchronization in the system manual S7-1500 (http://support.automation.siemens.com/WW/view/en/59191792).

3.2 Overview of connection resources

Connection resources Some communications services require connections. Connections occupy resources on the CPUs, CPs and CMs involved (for example memory areas in the operating system of the CPU). In most cases one resource per CPU/CP/CM is occupied for a connection. In HMI communication, up to 3 connection resources are required per HMI connection.

The connection resources available depend on the CPU being used, the CPs and CMs and must not exceed a defined upper limit for the automation system.

Connection resources available on an S7-1500 automation system The maximum configuration limits within an automation system are decided by the CPU. The available connection resources of a CPU/CP/CM are automatically distributed among the interfaces as required.

Each CPU has reserved connection resources for PG, HMI and Web server communication in its project engineering. There are also resources available that can be used for all HMI, S7 communication and open communication.

When are connection resources occupied? The occupation of connection resources depends on how the connection is set up, automatically, programmed or configured (see section Setting up a connection (Page 18)).

Further information You will find more detailed information on the occupation of connection resources and the display of connection resources in STEP 7 in the section Connection resources (Page 63).




Communications services 3.3 Setting up a connection


3.3 Setting up a connection

Automatic connection STEP 7 sets up a connection automatically (for example PG or HMI connection) if you have connected the PG/PC interface to an interface of the CPU physically and have made the interface assignment in STEP 7 in the "Go online" dialog.

Programmed setup of the connection You set up the connection in the program editor of STEP 7 in the context of a CPU by assigning instructions for communication, for example TSEND_C.

Regardless of whether the communication is via an integrated interface of the CPU, of a CP or CM you use the same instructions.

When specifying the connection parameters (in the Inspector window, in the properties of the instruction), you are supported by the convenient user interface.

Figure 3-1 Programmed setup

Communications services 3.3 Setting up a connection


Configured setup of the connection You set up the connection in the network view of the Devices & networks editor of STEP 7 in the context of a CPU.

Figure 3-2 Configured setup

Summary You can often choose between a configured or a programmed connection setup. Programmed connection setup allows connection resources to be released following data transfer. With configured connection setup, you are supported in the management of connection resources in STEP 7.

Table 3- 2 Setting up the communications service

Communication service Automatically Programmed setup Configured setup PG communication X - - HMI communication X - X Open communication using TCP/IP - X X Open communication using ISO-on-TCP

- X X

Open communication with UDP - X X Open communication with ISO - - X E-mail - X - FTP - X - Open communication with FDL - - X S7 communication - - X

Communications services 3.4 Data consistency


Further information You will find more detailed information on the occupation of connection resources and the display of connection resources in STEP 7 in the section Connection resources (Page 63).

3.4 Data consistency

Definition of data consistency The size of the data area that cannot be changed at the same time by competing processes is known as a consistent data area. A data area that is larger than the consistent data area can be corrupted as a whole. This means that a self-contained data area that is larger than the consistent data area may consist of new and old consistent data fields at any one time.

Example An inconsistency can occur when an instruction for communication is interrupted, for example by a hardware interrupt OB with higher priority. If the user program in this OB now changes the data that has already been partly processed by the instruction, the transferred data originates:

● partly from the time prior to hardware interrupt processing

● partly from the time after the hardware interrupt processing.

This means that the data is inconsistent (data that does not belong together).

Effect No inconsistency occurs if the system-specific maximum size of the consistent data is kept to. The S7-1500 CPUs allow a maximum of 462 bytes (see below).

If more data than the system-specific maximum size needs to be transferred consistently, you yourself must ensure that the data remains consistent in the application. This can, for example extend the interrupt reaction time of the CPU.



Data consistency with S7-1500 Use of instructions for access to common data:

If the user program contains instructions for communication that access common data, for example TSEND/TRCV, you can coordinate access to this data area yourself, for example using the "DONE" parameter. The data consistency of the data areas that are transferred locally with an instruction for communication can therefore be ensured in the user program.

Use of PUT/GET instructions or Write/Read via HMI communication:

In S7 communication with the PUT/GET instructions or Write/Read via HMI communication, you need to take into account the size of the consistent data areas during programming or configuration because there is no instruction in the user program of the target device (server) that can coordinate the data transfer in the user program.

System-specific maximum data consistency for S7-1500:

With an S7-1500, communication data is transferred in blocks of up to 462 bytes consistently into or out of the user memory during the program cycle. Data consistency is not ensured for larger data areas. Where defined data consistency is required, the length of communication data in the user program of the CPU must not exceed 462 bytes. You can then access these data areas consistently, for example from an HMI device using Read/Write tags.

Maximum data consistency for point-to-point CM:

With communication via a CM for a point-to-point link, the data consistency is ensured by the Send/Receive instructions in the user program. The maximum data consistency is 4 KB.

Further information ● You will find the maximum amount of consistent data in the CPU, CM or CP manuals in

the Technical specifications.

● You will find further information on data consistency in the description of the instructions in the STEP 7 online help.




PG communication 4

Properties Using PG communication, the CPU or another module capable of communication exchanges data with an engineering station (for example PG, PC). The data exchange is possible via PROFIBUS and PROFINET subnets. Changing between subnets is also supported.

PG communication provides functions needed to load programs and configuration data, run tests, and evaluate diagnostic information. These functions are integrated in the operating system of the module capable of communication.

A PG/PC can be connected to a CPU online. The PG/PC can operate a maximum of 4 online connections at one time (for example to 4 CPUs).

Procedure for setting up PG communication For PG communication, you need to set up an online connection from the PG/PC to the module capable of communication:

1. Connect the PG/PC interface to the required interface physically, for example the PROFINET interface of the CPU.

2. Select the CPU in the Project tree in STEP 7.

3. Select the "Online > Go online" menu command.

PG communication


4. In the "Go online" dialog, select the PG/PC interface (for example Ind. Ethernet adapter).

Figure 4-1 Setting up PG communication

5. In the "Compatible devices in the target subnet" table, select the relevant CPU and confirm with "Connect".

Further information You will find further information on "Go online" in the STEP 7 online help.


HMI communication 5

Properties Using HMI communication, the CPU exchanges data for operator control and monitoring with one or more HMI devices (for example HMI Basic/Comfort/Mobile Panel) via the PROFINET or PROFIBUS DP interface. The data exchange is via HMI connections.

If you want to set up connections from a CPU to several HMI devices, use, for example:

● the PROFINET and PROFIBUS DP interfaces of the CPU

● additional CPs and CMs with the relevant interfaces

● additional PROFINET switches with a suitable number of connectors for the HMI devices

Procedure for setting up HMI communication 1. Configure the HMI device in an existing configuration with a CPU in the network view

of the Devices & networks editor of STEP 7.

2. Select the "Connections" button and then "HMI connection" from the drop-down list.

3. By means of drag-and-drop, connect the interface of the HMI device with an interface of the CPU. If the required subnet does not yet exist, this is created automatically.

HMI communication


4. In the "Connections" tab, select the row of the HMI connection.

In the "General" area of the "Properties" tab, you see the properties of the HMI connection, some of which you can change.

Figure 5-1 Setting up HMI communication

5. Download the hardware configuration to the CPU.

6. Download the hardware configuration to the HMI device.

Further information You will find further information on setting up HMI connections in the STEP 7 online help.


Open communication 66.1 Overview of open communication

Features of open communication Using open communication, the CPU exchanges data with another module capable of communication within a subnet. The main features of open communication are as follows:

● Open standard (communication possible with CPUs or PCs from other manufacturers)

● Communication via various protocols (in STEP 7 known as "Connection types")

● High degree of flexibility in terms of the data structures transferred; this allows open data exchange with any communications devices as long as these support the connection types available.

● Open communication in S7-1500 possible with:

– Integrated interfaces of the CPU

– CP 1543-1 (PROFINET)

– CM 1542-5 (PROFIBUS)

6.2 Protocols for open communication

Protocols for open communication For open communication, the following protocols are available for S7-1500 automation systems:

Table 6- 1 Protocols for open communication

Protocol Via interface TCP according to RFC 793 PROFINET ISO-on-TCP according to RFC 1006 PROFINET ISO according to RFC 8073 PROFINET (only CP 1543-1) UDP according to RFC 768 PROFINET E-mail PROFINET FTP PROFINET (only CP 1543-1) FDL PROFIBUS DP (only CM 1542-5)

Open communication 6.2 Protocols for open communication


Protocols for communication via PROFINET: TCP, ISO-on-TCP, ISO, UDP Prior to data transfer, these protocols establish a (logical) connection to the communications partner. Connection-oriented protocols are used when potential loss of data needs to be avoided. Usually several logical connections can be established via a physical cable. With ISO-on-TCP, ISO and UDP, information about the length and end of a data packet is also sent, this is not the case with TCP.

The following is possible with UDP:

● Unicast to one or broadcast to all devices on PROFINET via the PROFINET interface of the CPU or the CP 1543-1

● Multicast to all recipients of a multicast group via the PROFINET interface of the CP 1543-1

Protocol for communication via PROFIBUS: FDL Data transfer via an FDL connection (Fieldbus Data Link) is suitable for the transfer of related blocks of data to a communications partner on PROFIBUS that supports the sending and reception of data according to the FDL service SDA (Send Data with Acknowledge) according to EN 50170 Vol 2. Both partners have the same rights; in other words, each partner can initiate sending and receiving event-driven.

In keeping with the FDL service SDN (Send Data with No Acknowledge) according to EN 50170, Vol 2, the following is possible with FDL:

● Broadcast to all devices on PROFIBUS

● Multicast to all recipients of a multicast group

E-mail and FTP protocols The sending of process data from data blocks is, for example, possible using e-mail.

The FTP connection (FTP = File Transfer Protocol) is used to handle FTP job sequences.

Communication is controlled solely by suitable instructions in the user program.

Open communication 6.3 Instructions for open communication


6.3 Instructions for open communication

Introduction You set up open communication via the relevant connection (for example TCP connection) as follows:

● by programming in the user programs of the communications partners or

● by configuring the connection in STEP 7 in the Devices & networks editor

Regardless of whether you set up the connection by programming or configuring, instructions are always required in the user programs of both communications partners for sending and receiving the data.

Regardless of whether the communication is via an integrated interface of the CPU, of a CP or CM you use the same instructions.

Setting up the connection using the user program If the connection is set up by programming, the connection establishment and termination is implemented using instructions in the user program.

In certain areas of application it is an advantage not to set up the communications connections statically by configuring in the hardware configuration, but to have them set up by the user program. You can set up the connections via a specific application program-controlled and therefore when necessary dynamically. Programmed connection setup also allows connection resources to be released following data transfer.

The following instructions are available:

● Instructions with automatic connection management:

– TSEND_C: establish connection and send data

– TRCV_C: establish connection and receive data

● Instructions without automatic connection management:

– TCON: establish connection

– TDISCON: terminate connection

– TSEND and TRCV: send and receive data

We recommend that you use the instructions with automatic connection management, TSEND_C and TRCV_C in the user program.

Use the TCON, TDISCON and TSEND/TRCV instructions when you want to program connection establishment and termination yourself.



Data blocks for parameter assignment of the connection data A data structure is necessary for each communications connection that contains the parameters for establishing the connection (for example system data type "TCON_IP_v4" for TCP).

The system data types (SDT) are provided by the system and have a predefined structure that cannot be changed.

The various protocols have their own data structures (see table below). The parameters are stored in a data block ("connection description DB") for example of the system data type TCON_IP_v4.

There are two ways in which you can specify the DB with the data structure:

● Have the data block created automatically in the properties in the program editor during parameter assignment of the connection (recommendation; possible for TCP, ISO-on-TCP and UDP)

● Create the data block manually, assign parameters to it and write it directly to the instruction (necessary for e-mail and FTP)

You can modify the connection parameters in the "connection description DB".

Protocols, usable instructions and system data types for programmed setup

Table 6- 2 Instructions for programmed setup of the connection

Protocol Setting up the connection using the user program

System data type

Usable instructions: TCP • TCON_IP_v4

ISO-on-TCP • TCON_IP_RFC

UDP

Establish connection and send/receive data via: • TSEND_C/TRCV_C or • TCON, TSEND/TRCV

(termination of the connection possible with TDISCON)

• TCON_IP_v4

E-mail • TMAIL_C • TMail_v4 • TMail_v6 • TMail_FQDN

FTP • FTP_CMD • FTP_CONNECT_IPV4* • FTP_CONNECT_IPV6* • FTP_CONNECT_NAME*

*User-defined data type



Setting up the connection with connection configuration When setting up by configuring the connection, the address parameters of the connection are specified in the Devices & networks editor of STEP 7.

To send and receive the data, use the same instructions as when the connections are set up by programming:

Table 6- 3 Instructions for sending/receiving with configured connections

Protocol Send/receive with configured connections Usable instructions: TCP ISO-on-TCP UDP ISO FDL

Send/receive data via: • TSEND_C/TRCV_C or • TSEND/TRCV

E-mail Not supported FTP Not supported

Further information You will find the following described in the STEP 7 online help:

● the user and system data types

● the instructions for open communication

● the connection parameters

You will find information about the occupation and release of connection resources in the section Occupation of connection resources (Page 63).

Open communication 6.4 Setting up open communication with TCP, ISO-on-TCP, UDP, ISO and FDL


6.4 Setting up open communication with TCP, ISO-on-TCP, UDP, ISO and FDL

Introduction The procedure for setting up open communication via TCP, ISO-on-TCP, UDP, ISO and FDL is essentially the same.

Below you will find the description of programmed setup and setting up using a connection configuration based on the example of TCP.

Procedure for setting up a connection with the user program (possible for TCP, ISO-on-TCP and UDP)

1. Configure the communications partners in the network view of the Devices & networks editor of STEP 7.

2. In the Project tree, select the "Program blocks" folder for one of the CPUs and open OB1 in the folder by double-clicking on it. The program editor opens.

3. Select the required instruction from the "Instructions" task card, "Communication" area, "Open user communication", for example TSEND_C and drag it to a network of OB1.

4. Set the connection parameters in the Inspector window of the program editor in the properties of the instruction:

– Select the partner for the communications connection (e.g. CPU in the same project or "Unspecified" for example for a PC).

– Specify the data block for storing the connection data.

– Select the connection type for the open communication, in the example "TCP".

– Specify which of the communications partners establishes the connection actively.



5. Interconnect the "DATA" parameter of the TSEND_C instruction with the user data, for example in a data block.

Figure 6-1 Programming open communication

6. Download the hardware configuration and user program to the CPU.

Based on the procedure described above, set up the connection on the partner CPU with the instruction for receiving, TRCV_C, and download it to the CPU.



Procedure for setting up a connection by configuring the connection 1. Configure the communications partners in the network view of the Devices & networks

editor of STEP 7.

2. Select the "Connections" button and then select the required connection type for the open communication from the drop-down list, for example the entry "TCP connection".

3. Connect the relevant interfaces of the communications partners using drag-and-drop. If the required subnet does not yet exist, this is created automatically.

As an alternative or for connections to unspecified partners:

– Select "Add new connection" in the shortcut menu of the CPU.

– In the next dialog "Create new connection", select the required local interface of the CPU and "Unspecified" as the connection partner.

Figure 6-2 Setting up a connection to an unspecified partner

4. In the "Connections" tab, select the row of the connection.



5. Set the properties of the connection in the "Properties" tab in the "General" area, for example the name of the connection and the interfaces of the communications partner that will be used.

For connections to an unspecified partner, set the address of the partner.

Figure 6-3 Setting up open communication with connection configuration


7. Select the required instruction from the "Instructions" task card, "Communication" area, "Open user communication", for example TSEND_C and drag it to a network of OB1.

8. In the Inspector window of the program editor, select the configuration type "Use configured connection" in the properties of the instruction.



9. Interconnect the "DATA" parameter of the TSEND_C instruction with the user data, for example in a data block.


Based on the procedure described above, set up the connection on the partner CPU with the instruction for receiving, TRCV_C, and download it to the CPU.

Point to note with ISO connections with CP 1543-1 If you use the "ISO connection" connection type, you will need to enable the "Use ISO protocol" check box in the properties of the CP so that addressing using MAC addresses will work.

Figure 6-4 Select CP 1543-1 ISO protocol




Open communication 6.5 Setting up e-mail and FTP


6.5 Setting up e-mail and FTP

Setting up a connection for e-mail or FTP using the user program When you set up the connections described up to now, you are supported by STEP 7 when entering the connection parameters. The entries are made in the Inspector window of the program editor in the context of the relevant instruction.

For communication using e-mail and FTP, you need to create the data block of the relevant system data type yourself, assign parameters and call the instruction directly. This procedure is introduced below.

Procedure for setting up communication using e-mail A CPU can send e-mails. To send e-mails from the user program of the CPU, use the TMAIL_C instruction.

Requirement: The SMTP server can be reached via the PROFINET subnet.

1. Configure an S7-1500 automation system with CPU in the network view of the Devices & networks editor of STEP 7.

2. Set the address parameters for the SMTP server in the TMAIL_C instruction.

3. Specify a DB with the TMAIL_v4, TMail_v6 or TMail_FQDM data structure (contains the parameters required to establish the connection):

– Create the data block, assign the parameters and write it directly to the instruction.

You can modify the connection parameters in the DB.


FTP client and server functionality Data can be sent by a CPU to an FTP server and can be received from the FTP server. Communication with FTP is only possible for the S7-1500 using the CP 1543-1. The CP can be an FTP server, FTP client or both. FTP clients can also be third-party systems/PCs.

For the FTP server functionality, configure the CP accordingly in STEP 7.

With the FTP client functionality, you implement, for example the establishment and termination of an FTP connection, the transfer and deletion of data on the server. For the FTP client functionality, use the FTP_CMD instruction.



Procedure for setting up FTP server functionality Requirement: The FTP server can be reached via the PROFINET subnet.

1. Configure an S7-1500 automation system with CPU and CP 1543-1 in the device view of the Devices & networks editor of STEP 7.

2. Make the following settings in the properties of the CP under "FTP configuration":

– Select the "Use FTP server for S7 CPU data" check box.

– Assign the CPU, a data block and a file name under which the DB for FTP will be stored.

Figure 6-5 Setting up the FTP configuration

3. Download the hardware configuration to the CPU.



Procedure for setting up FTP client functionality Requirement: The FTP server can be reached via the PROFINET subnet.

1. Configure an S7-1500 automation system with CPU and CP 1543-1 in the device view of the Devices & networks editor of STEP 7.

2. Call the FTP_CMD instruction in the user program of the CPU.

3. Set the connection parameters for the FTP server in the FTP_CMD instruction.

4. Specify a DB with the FTP_CONNECT_IPV4, FTP_CONNECT_IPV6 or FTP_CONNECT_NAME data structure:

– Create the data block and write it directly to the instruction.

5. For the connection to the FTP server, specify the following in the DB:

– the user name, the password and the IP address for the FTP access in the relevant data type (FTP_CONNECT_IPV4, FTP_CONNECT_IPV6 or FTP_CONNECT_NAME)



● the system data types



Open communication 6.6 Establishment and termination of open communications relations


6.6 Establishment and termination of open communications relations

Establishment and termination of open communications relations

Table 6- 4 Establishment and termination of open communications relations

Setting up the connection Establishing the communications relation Terminating the communications relation

With the user program After downloading the user program to the CPUs: The passive communications partner sets up the local connection access by calling TSEND_C/TRCV_C or TCON. Calling TSEND_C/TRCV_C or TCON on the active partner starts connection establishment. If the connection could be established, there is positive feedback to the instructions in the user program. If the connection aborts, the active partner attempts to re-establish the connection.

• Using the TSEND_C/TRCV_C or TDISCON instructions

• When the CPU changes from RUN to STOP mode

• When power is cycled on a CPU

By configuring a connection After downloading the connection configuration and the user program to the CPUs: The passive communications partner sets up the local connection access by calling TSEND_C/TRCV_C. Calling TSEND_C/TRCV_C on the active partner starts connection establishment. If the connection could be established, there is positive feedback to the instructions in the user program.

By deleting the connection configuration in STEP 7 and downloading the changed configuration to the CPU. Otherwise the connection is not terminated following data transfer; in other words, the connection remains established. Advantage: The execution time of the instructions is shorter the next time data is transferred because the connection does not need to be established again.


S7 communication 7

Characteristics of S7 communication S7 communication as homogeneous SIMATIC communication is characterized by vendor-specific communication between SIMATIC CPUs (not an open standard). S7 communication is used for migration and for connecting to existing systems (S7-300, S7-400).

For S7-1500 automation systems, we recommend that you use open communication (see section Open communication (Page 27)).

Properties of S7 communication With S7 communication, the CPU exchanges data with another CPU via its integrated PROFINET or PROFIBUS DP interface or via a CP/CM with a suitable interface. The remote application acknowledges; in other words, as soon as the receiving CPU has received the data, it acknowledges this to the sending CPU.

The data is exchanged via configured S7 connections. S7 connections can be configured at one end or at both ends.

S7 connections configured at one end With an S7 connection configured at one end, the connection partner is the server for this connection (client/server communication). The S7 connection is configured on the client, suitable instructions are called in the user program and the configuration and user program are downloaded. On the server, the data is made available by the system without instructions in the user program.

One special case with S7 connections configured at one end is S7 communication with an unspecified partner (unspecified S7 connection). This makes it possible to use S7 connections beyond the boundaries of a project. The connection partner is unknown to the local project (unspecified) and is configured in another STEP 7 or third-party project.

S7 connections configured at both ends With S7 connections configured at both ends, both partners can send and receive data. The configuration and the instruction calls in the user program are downloaded to the CPUs of both connection partners (client/client communication).

A connection configured at both ends can also be an unspecified S7 connection (see above). Configuration etc is necessary on both connection partners.

S7 communication


Instructions for S7 communication For S7 communication with S7-1500, the following instructions can be used:

● PUT/GET for connections configured at one or both ends

● BSEND/BRCV for connections configured at both ends

– for reliable data transfer

● USEND/URCV for connections configured at both ends

– for fast unreliable transfer of data regardless of the timing of the processing by the communications partner; for example for operating and maintenance messages

Note Data blocks for PUT/GET instructions

When using the PUT/GET instructions, you can only use data blocks with absolute addressing. Symbolic addressing of data blocks is not possible.

Summary

Table 7- 1 Summary of S7 communication

Communication service Model Via interface Configure S7 connections

Call instruction in the user program

Client/client PROFINET PROFIBUS DP*

configured at both ends: in each client

In client 1: BSEND, USEND or PUT In client 2 accordingly: BRCV, URCV or GET

S7 communication

Client/server PROFINET PROFIBUS DP

configured at one end: in client

In client: PUT and GET

*when DP slave is active

S7 communication


PROFIBUS DP interface of the CM 1542-5 in slave mode You will find the "Test, commissioning, routing" check box in the properties of the PROFIBUS DP interface in STEP 7. Using this check box, you decide whether the PROFIBUS DP interface of the DP slave is an active or passive device on PROFIBUS.

● Check box enabled: The slave is an active device on PROFIBUS. S7 connections configured at both ends can be set up for this DP slave.

● Check box disabled: The DP slave is a passive device on PROFIBUS. Only S7 connections configured at one end can be set up for this DP slave.

Figure 7-1 "Test, commissioning, routing" check box

S7 communication


Procedure for setting up S7 communication 1. Configure the communications partners in the network view of the Devices & networks

editor of STEP 7.

2. Select the "Connections" button and the "S7 connection" entry from the drop-down list.

3. Connect the relevant interfaces of the communications partners using drag-and-drop. If the required subnet does not yet exist, this is created automatically.

As an alternative or for S7 connections to unspecified partners:

– Select "Add new connection" in the shortcut menu of the CPU.

– In the next dialog "Create new connection", select the required local interface of the CPU and "Unspecified" as the connection partner.

Figure 7-2 S7 connection to an unspecified partner

4. In the "Connections" tab, select the row of the S7 connection.

S7 communication


5. Set the properties of the S7 connection in the "Properties" tab in the "General" area, for example the name of the connection and the interfaces of the communications partner that will be used.

For S7 connections to an unspecified partner, set the address of the partner.

Figure 7-3 Setting up S7 communication


S7 communication


7. In the program editor, call the relevant instructions for S7 communication in the user program of the client (configured at one end) or in the user programs of the clients (configured at both ends). Select, for example, the PUT and GET instructions from the "Communication" area of the "Instructions" task card and drag them to a network of OB1.

Figure 7-4 PUT/GET instructions

8. Assign the parameters for the instructions indicating which data will be written to where and which data will be read from where.

9. Download the hardware configuration and user program to the CPU(s).

S7 communication


S7 communication via CP 1543-1 If you set up S7 communication via the PROFINET interface of the CP 1543-1, you can select the transport protocol for data transfer in the properties of the S7 connection under "General":

● "TCP/IP" check box enabled (default): ISO-on-TCP protocol (RFC1006): for S7 communication between S7-1500 CPUs

● "TCP/IP" check box disabled: ISO protocol (RFC8073): Addressing using MAC addresses

Figure 7-5 Selecting the CP 1543-1 transport protocol

S7 communication


Procedure for setting up an S7 connection via different subnets You have the option of using an S7 connection via PROFIBUS and PROFINET subnets (routing via S7 connections).

1. Configure the communications partners in the network view of the Devices & networks editor of STEP 7.

2. Select the "Network" button.

3. Connect the relevant interfaces with the PROFIBUS and PROFINET subnet using drag-and-drop.

4. Select the "Connections" button and the "S7 connection" entry from the drop-down list.

S7 communication


5. In our example, connect a PROFINET interface of CPU 1 with a PROFINET interface of CPU 3 using drag-and-drop.

The S7 connection between CPU 1 and CPU 3 is set up.

Figure 7-6 S7 connections via different subnets

Further information You will find detailed information on configuring S7 connections and how to use the instructions for S7 communication in the user program in the STEP 7 online help.

S7 communication



Point-to-point link 8

Functionality A point-to-point link for S7-1500, ET 200MP and ET 200SP is established via communications modules (CMs) with serial interfaces (RS 232, RS 422 or RS 485):

● S7-1500/ET 200MP:

– CM PtP RS232 BA

– CM PtP RS422/485 BA

– CM PtP RS232 HF

– CM PtP RS422/485 HF

● ET 200SP:

– CM PtP

The bidirectional data exchange via a point-to-point link works between communications modules or third-party systems or devices capable of communication. In general there are only 2 communications partners involved in communication ("point-to-point"). With RS 422/485, more than two communications partners are possible.

Protocols for communication via a point-to-point link ● Freeport protocol

● Procedure 3964(R)

● Modbus protocol in RTU format (RTU: Remote Terminal Unit)

● USS protocol (universal serial interface protocol)

The protocols use different layers according to the ISO/OSI reference model:

● Freeport: uses layer 1 (physical layer)

● 3964 (R), USS and Modbus: use layer 1 and 2 (physical layer and data link layer; therefore greater transmission reliability than with Freeport)

Properties of the Freeport protocol ● The recipient recognizes the end of the data transfer by means of a selectable end

criterion (e.g. character delay time elapsed, receipt of end character, receipt of a fixed amount of data).

● It is not possible to recognize whether the sent data arrived free of errors at the recipient.

Point-to-point link


Properties of procedure 3964 (R) ● When the data is sent, control characters are added

(start, end and block check character).

● Connection establishment and termination makes use of control characters.

● If errors occur, data transfer is repeated.

Data exchange using Freeport or 3964 (R) communication The data to be sent is stored in the user program of the corresponding CPU in data blocks (send buffer). A receive buffer is available on the communications module for the received data. A suitable data block is set up on the CPU.

In the user program of the CPU, the "Send_P2P" and "Receive_P2P" instructions handle the data transfer between the CPU and CM.

Point-to-point link


Procedure for setting up Freeport or 3964 (R) communication 1. Configure an S7-1500 structure with CPU and CM in the device view of the hardware

and network editor of STEP 7.

2. Assign the parameters for the interface of the CP (protocol, protocol parameters, addresses) in the "General" area in the "Properties" tab.

Figure 8-1 Setting up PtP communication

3. In the Project tree, select the "Program blocks" folder and open OB1 in the folder by double-clicking on it. The program editor opens.

4. Select the "Send_P2P" and "Receive_P2P" instructions from the "Communication" area of the "Instructions" task card and drag them to a network of OB1.

5. Assign the parameters for the instructions according to your configuration.


Point-to-point link


Otherwise: Dynamic configuration via the user program In certain types of application it is an advantage to set up communication dynamically; in other words, program-controlled by a specific application.

Typical applications for this, could be, for example manufacturers of serial machines. To make the user interfaces as convenient as possible for their customers, these manufacturers adapt the communications services to the particular operator entries.

Instructions for Freeport communication There are 3 instructions available for the dynamic configuration in the user program for Freeport communication. The following applies to all 3 instructions: the previously valid configuration data is overwritten but not stored permanently in the target system.

● The "Port_Config" instruction is used for the program-controlled configuration of the relevant port of the communications module.

● The "Send_Config" instruction is used for the dynamic configuration, for example of time intervals and breaks in transmission (serial transmission parameters) for the relevant port.

● The "Receive_Config" instruction is used for dynamic configuration, for example of conditions for the start and end of a message to be transferred (serial receive parameters) for the relevant port.

Instructions for 3964 (R) communication There are 2 instructions available for dynamic configuration in the user program for 3964 (R) communication. The following applies to the instructions: the previously valid configuration data is overwritten but not stored permanently in the target system.

● The "Port_Config" instruction is used for the program-controlled configuration of the relevant port of the communications module.

● The "P3964_Config" instruction is used for the dynamic configuration of protocol parameters.

Properties of the USS protocol ● Simple, serial data transfer protocol with cyclic message frame traffic in half duplex

mode that is tailored to the requirements of drive technology.

● Data transfer works according to the master-slave principle.

– The master has access to the functions of the drive and can read and write the drive parameters.

● Broadcast to all slaves is possible.

Point-to-point link


Data exchange using USS communication The communications module is the master. The master continuously sends frames (job frames) to the up to 16 drives and expects a response frame from each addressed drive.

A drive must send a response frame if:

● it has a received a frame without errors and

● it was addressed in this frame.

A drive must not send if these conditions are not met or the drive was addressed in the broadcast.

The connection to the relevant drive exists for the master once it receives a response frame from the drive after a specified processing time (response delay time).

Procedure for setting up USS communication 1. Configure an S7-1500 structure with CPU and CM in the device view of the hardware



3. Select the instructions for USS communication according to your task in the "Communication" area of the "Instructions" task card and drag them to a network of OB1:

– The "USS_Port_Scan" instruction allows you to communicate via the USS network.

– The "USS_Drive_Control" instruction is used to exchange data with the drive.

– The "USS_Read_Param" instruction is used to read out parameters from the drive.

– The "USS_Write_Param" instruction is used to change parameters on the drive.



Properties of the Modbus protocol (RTU) ● Communication takes the form of serial, asynchronous transfer with a transmission

speed of up to 115.2 kbps, half duplex.

● Data transfer works according to the master-slave principle.

● The Modbus master can send jobs for reading and writing operands to the Modbus slave:

– Reading inputs, timers, counters, outputs, memory bits, data blocks

– Writing outputs, memory bits, data blocks

● Broadcast to all slaves is possible.

Point-to-point link


Data exchange using Modbus communication (RTU) The communications module can be a Modbus master or Modbus slave. A Modbus master can communicate with one or more Modbus slaves (the number depends on the physical interface). Only the Modbus slave explicitly addressed by the Modbus master is permitted to return data to the Modbus master. The slave detects the end of the data transfer and acknowledges it. If an error occurs, it provides an error code to the master.

Procedure for setting up Modbus communication (RTU) 1. Configure an S7-1500 structure with CPU and CM in the device view of the hardware



3. Select the instructions for Modbus communication according to your task in the "Communication" area of the "Instructions" task card and drag them to a network of OB1:

– The "Modbus_Comm_Load" instruction configures the port of the CM for Modbus communication.

– The "Modbus_Master" instruction is used for Modbus master functionality.

– The "Modbus_Slave" instruction is used for Modbus slave functionality.



Further information ● You will find more detailed information on communication via point-to-point connections

and basics of serial data transmission in the function manual CM PtP communication module - Configurations for point-to-point connections (http://support.automation.siemens.com/WW/view/en/59057093).

● You will find a description of how to use the instructions for point-to-point links in the user program in the STEP 7 online help.

● You will find information about the communications modules with a serial interface in the manual of the particular communications module.



Routing 99.1 S7 routing

Definition of S7 routing S7 routing is the transfer of data beyond network boundaries. You can send information from a transmitter to a receiver across several networks.

Application S7 routing is possible via PROFINET and PROFIBUS subnets. With the PG/PC, you can reach devices beyond subnet boundaries, for example to do the following:

● download user programs

● download a hardware configuration or

● run test and diagnostics functions

An S7 connection between two CPUs via different subnets You have the option of setting up an S7 connection from a CPU to another CPU via different subnets (PROFIBUS and PROFINET). The procedure is described based on an example in the section S7 communication (Page 41).

CPUs, CMs and CPs in S7-1500 CPUs, CMs and CPs in S7-1500 can be routers for:

● CPUs, CMs and CPs S7-1500

● S7-300, S7-400 CPUs

● HMI devices

● PGs/PCs



S7 routing gateways: PROFINET - PROFINET The gateway from one subnet to one or more other subnets is on the device that has the interfaces to the relevant subnets. In the following figure, CPU 1 is the router between subnet 1 and subnet 2.

Figure 9-1 S7 routing: PROFINET - PROFINET

S7 routing gateways: PROFINET - PROFIBUS The following figure shows the access from a PG via PROFINET to PROFIBUS. CPU 1 is the router between subnet 1 and subnet 2; CPU 2 is the router between subnet 2 and subnet 3.

Figure 9-2 S7 routing: PROFINET - PROFIBUS



Requirements for S7 routing ● The CPUs, CMs or CPs are "capable of routing".

● All devices that can be reached in a network have been configured in a project in STEP 7 and downloaded.

● All devices using the gateway must receive the routing information about the paths to other subnets. The devices obtain the routing information by downloading the hardware configuration to the CPUs.

In a topology with several subnets, the following order must be kept to when downloading: First download the hardware configuration to the CPU(s) directly connected to the same subnet as the PG/PC, then download the CPUs of the other subnets starting with the nearest subnet through to the subnet furthest away.

● The PG/PC you want to use to establish a connection via a gateway must be assigned to the subnet it is physically connected to.

● For PROFIBUS subnets: Either the CPU must be configured as DP master or, if it is configured as a DP slave, the "Test, commissioning, routing" check box must be selected in the properties of the DP interface of the DP slave.

Using S7 routing For the CPU, select the PG/PC interface and the subnet in the "Go online" dialog of STEP 7. S7 routing is performed automatically.

Number of connections for S7 routing The number of connections available for S7 routing on the CPUs, CMs or CPs can be found in the technical specifications in the manuals of the relevant CPU/CM/CP.



S7 routing: Example of an application The figure below shows the example of an application for remote maintenance of a station using a PG. The connection to other subnets is here established via modem connection.

You configure a remote connection via TeleService in STEP 7 using "Online access" or "Go online".

Figure 9-3 Remote maintenance of a plant using TeleService

Further information ● The occupation of connection resources with S7 routing is described in the section

Occupation of connection resources (Page 63).

● You will find detailed information on setting up TeleService in the STEP 7 online help.

● You will find further information on S7 routing and TeleService adapters on the Internet.

Routing 9.2 Data record routing


9.2 Data record routing

Definition of data record routing Data can be sent from an engineering station connected to PROFINET via PROFIBUS to field devices. The field devices themselves do not have to support data record routing, since they do not forward the information received.

The data sent using data record routing include the parameter assignments for the participating field devices (slaves) and device-specific information (e.g. setpoint values, limit values). The structure of the target address for data record routing depends on the data contents, i.e. the DP slave to which the data is sent.

With the PG/PC, data record routing can also be used to read a parameter record that exists on the field device, edit it and return it to the field device if the PG/PC is assigned to a different subnet than that of the target slave.

Use case for data record routing Data record routing is used, for example, when field devices of different manufacturers are being used in a network. The field devices are addressed using standardized data records (PROFIBUS standard) for parameter assignment and diagnostics. An engineering station with SIMATIC PDM can reach field devices via several subnets using a data record gateway.

Support of data record routing Data record routing is supported by SIMATIC PDM that needs to be installed on the engineering station.

There are other use cases in which STEP 7 automatically executes data record routing. Example: An engineering system is connected to the PROFINET subnet and requests special PROFIBUS data records from a PROFIBUS DP slave. The PROFINET/PROFIBUS gateways are set automatically in the "Go online" dialog of STEP 7.

Routing 9.2 Data record routing


Example of data record routing

Figure 9-4 Example of data record routing

Further information ● Whether or not the CPU, CP or CM you are using supports data record routing can be

found in the relevant manuals.

● The occupation of connection resources with data record routing is described in the section Occupation of connection resources (Page 63).

● You will find information on SIMATIC PDM and data record routing in the manual Process Control System PCS 7 SIMATIC PDM 8.0 (http://support.automation.siemens.com/WW/view/en/57355963).

● You will find further information on configuration with STEP 7 in the STEP 7 online help.



Connection resources 1010.1 Occupation of connection resources

Occupation of connection resources with automatic connection As soon as you have connected the PG or HMI device to a CPU physically and have gone online in STEP 7, connection resources are occupied.

Occupation of connection resources with programmed connection setup With programmed connections, a connection resource is used when the instruction for establishing the connection (TSEND_C or T_CON) is called.

With suitable parameter assignment of the instructions TSEND_C/TRCV_C or by calling the TDISCON instruction, the connection can be terminated following data transfer. If the connection is terminated, the connection resources on the CPU/CP/CM are available again. If the connection remains, the execution time of the instructions during the next data transfer is shorter because the connection does not need to be established again.

Occupation of connection resources with configured connection setup With configured connections, the connection resource is occupied as soon as the hardware configuration is downloaded to the CPU.

Following transfer of data, the connection is not terminated. The connection resource is permanently occupied. To release the connection resource again, you need to delete the configured connection in STEP 7 and download the modified configuration to the CPU.

Monitoring the maximum possible number of connection resources With automatic connections, the CPU monitors the status of the connection resources on the CPU. Once the reserved connection resources have been used up, further resources can be used (as long as connection resources are available for the automation system).

If the establishment and termination of the connections is programmed in the user program, you yourself will need to make sure that the limits are kept to on the automation system.

If you have configured connections in STEP 7, STEP 7 monitors the connection resources to ensure that the maximum possible number on an automation system is not exceeded. STEP 7 signals a violation of this with a suitable warning.



Configured connections: Display of the connection resources in STEP 7 (offline view) You can display the reserved and available connection resources of an S7-1500 automation system in the hardware configuration. You will find the connection resources in the Inspector window in the properties of the CPU.

Figure 10-1 Reserved and available connection resources (offline view)

Module-specific connection resources (offline view) The columns of the module-specific connection resources contain the following for the CPU, CPs and CMs of an S7-1500 automation system:

● how many connection resources are available as maximum for CPU/CP/CM

● how many of these were configured for which communications connections

● how many connection resources were configured in total and therefore used up

● how many connection resources are still available

The display is per module and not per interface.

In the example, the CPU provides a maximum of 128 connection resources. For the CPU, 6 HMI, 2 S7 and 39 open communication connections were configured occupying a total of 47 resources on the CPU. 81 resources of the CPU remain available. For the CP 1543-1, 56 of the 118 available resources are occupied, 62 resources remain available. All 48 available resources are used for the CM 1542-5.



Station-specific connection resources (offline view) The maximum number of available connection resources on the automation system (in the station) depends on the CPU being used. If the CPU-dependent limit is reached, it does not matter whether the CPU, CPs and CMs have further module-specific connection resources. For this station, the connection resources are used up.

In the example there are 246 + 10 reserved connection resources available for the automation system.

The 10 connection resources are reserved:

● 4 for PG communication required by STEP 7 for example for test and diagnostics functions or downloading to the CPU

● 4 for HMI communication, that are occupied by the first HMI connections configured in STEP 7

● 2 for communication with the Web server that are occupied after connecting a Web browser if the Web server of the CPU is activated

A maximum of 246 connection resources are dynamic; in other words, available for various communications services on the automation system. In this example, 147 of these connection resources are already configured for various communications services and modules. This leaves 99 connection resources available for the automation system.

The warning triangle in the column of the dynamic station resources is therefore displayed because the sum of the maximum available connection resources of CPU, CP and CM (= 294 connection resources) exceeds the station limit of 256.

Note Available connection resources exceeded

STEP 7 signals a warning when the station-specific connection resources are exceeded. In this case, either use a CPU with a higher maximum number of available station-specific connection resources or reduce the number of communications connections.



Display of the connection resources in STEP 7 (online view) If you have selected a CPU in the network view of the Devices & networks editor of STEP 7 that is connected online, you can display the current status of the occupied and unoccupied connection resources for this automation system in the "Connection information" tab in the "Diagnostics" area.

Figure 10-2 Connection resources - online

The online view of the "Connection resources" table also contains the reserved and configured connection resources of the offline view columns with the connection resources currently occupied on the CPU. In the online view, all occupied connection resources on the automation system are displayed regardless of whether they were set up automatically, programmed or configured. In the "Other communication" row, occupied connection resources for communication with third-party devices and communication via data record routing are displayed. The table is updated automatically.



Connection resources for HMI communication You will find information about the availability and occupation of connection resources for HMI connections in the offline view in the context of the HMI device (in the Inspector window in the properties in the "Connection resources" area).

The following is displayed under "Offline used":

● the number of configured HMI connections

If the maximum number of available connection resources for an HMI device is exceeded, a corresponding message is output by STEP 7.

● the maximum number of connection resources occupied by the configured HMI connections

With HMI communication, the occupation of connection resources on the CPU depends on the HMI device you are using and the applications in which the HMI device is used; for example a Basic Panel requires up to 2 connection resources for an HMI connection whereas a Comfort Panel requires up to 3 connection resources on the CPU.



Figure 10-3 Connection resources - HMI communication

S7 connections beyond network boundaries (S7 routing) To transfer data beyond network boundaries ("S7 routing"), an S7 connection is established between two CPUs over several subnets. The subnets are connected via gateways known as routers. The router is the crossing point of an S7 connection and can establish S7 connections. CPUs, CMs and CPs in S7-1500 can be routers.

In the endpoints of the communication (CPUs), the connection resources for S7 routing are taken into account and displayed in the "Connection resources" table for S7 communication in STEP 7. For S7 routing, 2 connection resources are also occupied on each router.



Data record routing Data record routing also allows the transfer of data beyond network boundaries by an engineering station connected to PROFINET via PROFIBUS to various field devices.

2 connection resources are occupied for data record routing on each router. In the end point of the communication (CPU), connection resources for data record routing are displayed in the online view of the "Connection resources" table in the "Other communication" row.

Note Connection resources for S7 routing and data record routing

With S7 routing or data record routing, corresponding connection resources are occupied on the routers. Configuration and monitoring of these connection resources is not possible in STEP 7. The routers need to monitor that the limits are kept to themselves.

Further information ● S7 routing is described in the section S7 routing (Page 57).

● Data record routing is described in the section Data record routing (Page 61).

● You will find the number of connection resources that an HMI device requires on the CPU in the documentation of the HMI device.




Connection diagnostics 1111.1 Connection diagnostics

Connections table in the online view After selecting a CPU in the Devices & networks editor of STEP 7, you will see the status of your connections displayed in the online view of the connections table.

Figure 11-1 Online view of the connections table

After selecting the connection in the connections table, you obtain detailed diagnostics information in the "Connection information" tab.



"Connection information" tab: Connection details

Figure 11-2 Diagnostics of connections - connection details



"Connection information" tab: Address details

Figure 11-3 Diagnostics of connections - address details

Diagnostics via Web server Via the integrated Web server of the S7-1500 CPUs, you can evaluate diagnostics information from the CPU using a Web browser.

On the "Communication" Web page, you will find the following information about communication via PROFINET in various tabs:

● Information on the PROFINET interfaces of the CPU (for example addresses, subnets, physical properties)

● Information on the quality of the data transfer (for example number of data packets sent/received error-free)

● Information about the occupation/availability of connection resources



Further information You will find the description of the Web server functionality in the function manual Web server (http://support.automation.siemens.com/WW/view/en/59193560).



Industrial Ethernet Security (CP 1543-1) 12

All-round protection - the task of Industrial Ethernet Security With Industrial Ethernet Security, individual devices, automation cells or network segments of an Ethernet network can be protected. Data transfer can also be protected by a combination of different security measures:

● Data espionage

● Data manipulation

● Unauthorized access

Security measures ● Firewall

– IP firewall with stateful packet inspection (layer 3 and 4)

– Firewall also for Ethernet "non-IP" frames according to IEEE 802.3 (layer 2)

– Bandwidth limitation

– Global firewall rules

All network nodes located in the internal network segment of a CP 1543-1 are protected by its firewall.

● Logging

To allow monitoring, events can be stored in log files that can be read out using the configuration tool or can be sent automatically to a Syslog server.

● HTTPS

For encrypted transfer of Web pages, for example during process monitoring.

● FTPS (explicit mode)

For encrypted transfer of files.

● Secure NTP

For secure time-of-day synchronization and transmission.

● SNMPv3

For secure transmission of network analysis information safe from eavesdropping.

● Protection for devices and network segments

The firewall protective function can be applied to the operation of single devices, several devices, or entire network segments.

Industrial Ethernet Security (CP 1543-1) 12.1 Firewall


12.1 Firewall

Tasks of the firewall The purpose of the firewall functionality is to protect networks and stations from outside influences and disturbances. This means that only certain previously specified communications relations are permitted.

To filter the data traffic, IP addresses, IP subnets, port numbers or MAC addresses among other things can be used.

The firewall functionality can be configured for the following protocol levels:

● IP firewall with stateful packet inspection (layer 3 and 4)

● Firewall also for Ethernet "non-IP" frames according to IEEE 802.3 (layer 2)

Firewall rules Firewall rules describe which packets are permitted or forbidden in which direction.

12.2 Logging

Functionality For test and monitoring purposes, the security module has diagnostics and logging functions.

● Diagnostics functions

These include various system and status functions that you can use in online mode.

● Logging functions

This involves the recording of system and security events. Depending on the event type, the recording is made in volatile or non-volatile local buffer areas of the CP 1543-1. As an alternative, it is also possible to record on a network server.

The parameter assignment and evaluation of these functions is only possible with a network connection.

Recording events with logging functions You specify which events should be recorded with the log settings. Here you can configure the following recording variants:

● Local logging

With this variant, you record the events in local buffers of the CP 1543-1. In the online dialog of the Security Configuration Tool, you can then access these recordings, visualize them and archive them on the service station.

● Network Syslog

With the network Syslog, you use a Syslog server in the network. This records the events according to the configuration in the log settings.

Industrial Ethernet Security (CP 1543-1) 12.3 NTP client


12.3 NTP client

Functionality To check whether the time for a certificate and for the time stamp and log entries is valid, the date and time are maintained on the CP 1543-1.

The CP 1543-1 as NTP client receives time-of-day frames from a Network Time Protocol server (NTP server). The automatic setting and periodic synchronization of the time is either via a secure or non-secure NTP server. A maximum of 4 NTP servers can be assigned to the CP 1543-1. A mixed configuration of non-secure and secure NTP servers is not possible.

12.4 SNMP

Functionality The CP 1543-1 supports the transfer of management information using the Simple Network Management Protocol (SNMP). To achieve this, an "SNMP agent" is installed on the CP that receives and responds to the SNMP queries. Information about the properties of devices capable of SNMP is contained in so-called MIB files (Management Information Base) for which the user needs to have the appropriate rights.

With SNMPv1, the "community string" is also sent. The community string is like a password that is sent along with the SNMP query. If the community string is correct, the security module responds with the requested information. If the string is incorrect, the security module discards the query and does not respond.

With SNMPv3, data can be transferred encrypted. To do this, select either an authentication method or an authentication and encryption method.

Possible selection:

● Authentication algorithm: none, MD5, SHA-1

● Encryption algorithm: none, AES-128, DES

Industrial Ethernet Security (CP 1543-1) 12.4 SNMP



Service & Support A

The unmatched complete service for the entire life cycle For machine constructors, solution providers and plant operators: The service offering from Siemens Industry Automation and Drive Technologies includes comprehensive services for a wide range of different users in all sectors of the manufacturing and process industry.

To accompany our products and systems, we offer integrated and structured services that provide valuable support in every phase of the life cycle of your machine or plant – from planning and implementation through commissioning as far as maintenance and modernization.

Our Service & Support accompanies you worldwide in all matters concerning automation and drive technology from Siemens. We provide direct on-site support in more than 100 countries through all phases of the life cycle of your machines and plants.

You have an experienced team of specialists at your side to provide active support and bundled know-how. Regular training courses and intensive contact among our employees – even across continents – ensure reliable service in the most diverse areas

Service & Support


Online Support The comprehensive online information platform supports you in all aspects of our Service & Support at any time and from any location in the world.

You can find Online Support on the Internet at the following address: Internet (http://www.siemens.com/automation/service&support).

Technical Consulting Support in planning and designing your project: From detailed actual-state analysis, definition of the goal and consultation on product and system questions right through to the creation of the automation solution.

Technical Support Expert advice on technical questions with a wide range of demand-optimized services for all our products and systems.

You can find Technical Support on the Internet at the following address: Internet (http://www.siemens.com/automation/support-request).

Training Extend your competitive edge – through practical know-how directly from the manufacturer.

You can find the training courses we offer on the Internet at the following address: Internet (http://www.siemens.com/sitrain).

Engineering Support Support during project engineering and development with services fine-tuned to your requirements, from configuration through to implementation of an automation project.

Field Service Our Field Service offers you services for commissioning and maintenance – to ensure that your machines and plants are always available.

Spare parts In every sector worldwide, plants and systems are required to operate with constantly increasing reliability. We will provide you with the support you need to prevent a standstill from occurring in the first place: with a worldwide network and optimum logistics chains.

Repairs Downtimes cause problems in the plant as well as unnecessary costs. We can help you to reduce both to a minimum – with our worldwide repair facilities.

http://www.siemens.com/automation/service&support�

http://www.siemens.com/automation/support-request�

http://www.siemens.com/sitrain�

Service & Support


Optimization During the service life of machines and plants, there is often a great potential for increasing productivity or reducing costs.

To help you achieve this potential, we are offering a complete range of optimization services.

Modernization You can also rely on our support when it comes to modernization – with comprehensive services from the planning phase all the way to commissioning.

Service programs Our service programs are selected service packages for an automation and drives system or product group. The individual services are coordinated with each other to ensure smooth coverage of the entire life cycle and support optimum use of your products and systems.

The services of a Service Program can be flexibly adapted at any time and used separately.

Examples of service programs:

● Service contracts

● Plant IT Security Services

● Life Cycle Services for Drive Engineering

● SIMATIC PCS 7 Life Cycle Services

● SINUMERIK Manufacturing Excellence

● SIMATIC Remote Support Services

Advantages at a glance:

● Reduced downtimes for increased productivity

● Optimized maintenance costs due to a tailored scope of services

● Costs that can be calculated and therefore planned

● Service reliability due to guaranteed response times and spare part delivery times

● Customer service personnel will be supported and relieved of additional tasks

● Comprehensive service from a single source, fewer interfaces and greater expertise

Contact At your service locally, around the globe: your partner for consultation, sales, training, service, support, spare parts... for the entire range of products supplied by Industry Automation and Drive Technologies.

You will find your personal contact in our contacts database at: Internet (http://www.siemens.com/automation/partner).

http://www.siemens.com/automation/partner�

Service & Support



Glossary

Automation system Programmable logic controller for the open-loop and closed-loop control of process chains of the process engineering industry and manufacturing technology. The automation system consists of different components and integrated system functions according to the automation task.

Bus Transmission medium that connects several devices together. Data transmission can be performed electrically or via optical fibers, either in series or in parallel.

Client Device in a network that requests a service from another device in the network (server).

CM -> Communications module

Communications module Module for communications tasks used in an automation system as an interface expansion of the CPU (for example PROFIBUS) and providing additional communications options (PtP).

Communications processor Module for expanded communications tasks covering special applications, for example in the area of security.

Consistent data Data that belongs together in terms of content and must not be separated when transferred.

CP -> Communications processor

CPU Central Processing Unit - Central module of the S7 automation system with a control and arithmetic unit, memory, operating system and interface for programming device.

Glossary


Device Generic term for:

● Automation systems (PLC, PC, for example)

● Distributed I/O systems

● Field devices (for example, PLC, PC, hydraulic devices, pneumatic devices) and

● Active network components (for example, switches, routers)

● Gateways to PROFIBUS, AS interface or other fieldbus systems

DP master Within PROFIBUS DP, a master in the distributed I/O that behaves according to the EN 50170 standard, Part 3.

See also Master

DP slave Slave in the distributed I/O that is operated on PROFIBUS with the PROFIBUS DP protocol and behaves according to the EN 50170 standard, Part 3.

See also Slave

Duplex Data transmission system; a distinction is made between full and half duplex.

Half duplex: One channel is available for alternate data exchange (sending or receiving alternately but not at the same time).

Full duplex: Two channels are available for simultaneous data exchange in both directions (simultaneous sending and reception in both directions).

Ethernet International standard technology for local area networks (LAN) based on frames. It defines types of cables and signaling for the physical layer and packet formats and protocols for media access control.

Ethernet network adapter Electronic circuitry for connecting a computer to an Ethernet network. It allows the exchange of data / communication within the network.

FDL Fieldbus Data Link; communications protocol for data transfer via PROFIBUS DP.

Glossary


FETCH/WRITE Server services using TCP/IP, ISO-on-TCP and ISO for access to system memory areas of S7 CPUs. Access (client function) is possible from a SIMATIC S5 or a third-party device/PC. FETCH: Read data directly; WRITE: Write data directly

Field device -> Device

Freeport Freely programmable ASCII protocol; here for data transfer via a point-to-point link.

FTP File Transfer Protocol; a network protocol for transferring files via IP networks. It is used to download files from the server to the client or to upload files from the client to the server. FTP directories can also be created and read out and directories and files can be renamed or deleted.

HMI Human Machine Interface, device for visualization and control of automation processes.

IM -> Interface module

Industrial Ethernet Guideline for setting up an Ethernet network in an industrial environment. The essential difference compared with standard Ethernet is the mechanical ruggedness and immunity to noise of the individual components.

Instruction The smallest self-contained unit of a user program characterized by its structure, function or purpose as a separate part of the user program. An instruction represents an operation procedure for the processor.

Interface module Module in the distributed I/O system. The interface module connects the distributed I/O system via a fieldbus to the CPU (IO controller/DP master) and prepares the data for the I/O modules.

Glossary


IO controller, PROFINET IO controller Central device in a PROFINET system, usually a classic programmable logic controller or PC. The IO controller sets up connections to the IO devices, exchanges data with them, thus controls and monitors the system.

IO device, PROFINET IO device Device in the distributed I/O of a PROFINET system that is monitored and controlled by an IO controller (for example distributed inputs/outputs, valve islands, frequency converters, switches).

IP address Unique address in computer networks based on the Internet protocol (IP). It is assigned to devices connected to the network and makes these devices uniquely addressable and reachable. It is made up of the following: Address of the network and address of the device (generally called the host or network node). The IP address is made up, for example, of 4 decimal numbers with a range of values from 0 to 255. The decimal numbers are separated by dots.

ISO Communications protocol for message or packet-oriented transfer of data in an Ethernet network. This protocol is hardware-oriented, very fast and allows dynamic data lengths. It is suitable for medium to large amounts of data.

ISO-on-TCP Communications protocol capable of S7 routing for packet-oriented transfer of data in an Ethernet network; provides network addressing. It is suitable for medium and large amounts of data and allows dynamic data lengths.

Linear bus topology Network topology characterized by the arrangement of the devices in a line (bus).

MAC address Worldwide unique device identification for all Ethernet devices. It is assigned by the manufacturer and has a 3-byte vendor ID and 3-byte device ID as a consecutive number.

Master Higher-level, active participant in the communication/on a PROFIBUS subnet. It has rights to access the bus (token), sends data and requests it.

Glossary


Modbus Open communications protocol for serial interfaces based on a master/slave architecture.

Network A network consists of one or more interconnected subnets with any number of devices. Several networks can exist alongside each other.

NTP The Network Time Protocol (NTP) is a standard for synchronizing clocks in automation systems via Industrial Ethernet. NTP uses the UDP wireless network protocol.

Operating system Software that allows the use and operation of a computer. The operating system manages resources such as memory, input and output devices and controls the execution of programs.

PNO -> PROFIBUS Users Organization

Point-to-point link Bidirectional data exchange via communications modules with a serial interface between two communications partners (and two only).

PORT Physical connector to connect devices to PROFINET. PROFINET interfaces have one or more ports.

Process image Address area of a programmable logic controller (PLC), in which the signal states of the inputs and the logical states of the outputs from the connected modules are stored digitally.

PROFIBUS Process Field Bus - European Fieldbus standard.

PROFIBUS address Unique identifier of a device connected to PROFIBUS. The PROFIBUS address is sent in the frame to address a device.

Glossary


PROFIBUS device Device with at least one PROFIBUS interface either electrical (for example RS-485) or optical (for example Polymer Optical Fiber).

PROFIBUS DP A PROFIBUS with DP protocol that complies with EN 50170. DP stands for distributed I/O = fast, real-time capable, cyclic data exchange. From the perspective of the user program, the distributed IO is addressed in exactly the same way as the centralized IO.

PROFIBUS users organization Technical committee dedicated to the definition and development of the PROFIBUS and PROFINETstandard.

PROFINET Open component-based industrial communications system based on Ethernet for distributed automation systems. Communications technology promoted by the PROFIBUS users organization.

PROFINET device Device that always has a PROFINET interface (electrical, optical, wireless).

PROFINET interface Interface of a module capable of communication (for example CPU, CP) with one or more ports. A MAC address is assigned to the interface in the factory. Along with the IP address and the device name (from the individual configuration), this interface address ensures that the PROFINET device is identified uniquely in the network. The interface can be electrical, optical or wireless.

PROFINET IO IO stands for input/output (fast, cyclic data exchange with real-time capability). From the perspective of the user program, the distributed IO is addressed in exactly the same way as the centralized IO.

PROFINET IO as the Ethernet-based automation standard of PROFIBUS and PROFINET International defines a cross-vendor communication, automation, and engineering model.

With PROFINET IO, a switching technology is used that allows all devices to access the network at any time. In this way, the network can be used much more efficiently through the simultaneous data transfer of several devices. Simultaneous sending and receiving is enabled via the full-duplex operation of Switched Ethernet.

PROFINET IO is based on switched Ethernet with full-duplex operation and a bandwidth of 100 Mbps.

Glossary


Programming device Programming devices are essentially compact and portable PCs which are suitable for industrial applications. They are identified by a special hardware and software configuration for programmable logic controllers.

Programming device Programming devices are essentially compact and portable PCs which are suitable for industrial applications. They are identified by a special hardware and software configuration for programmable logic controllers.

PtP Point-to-Point, interface and/or transmission protocol for bidirectional data exchange between two (and only two) communications partners.

Ring topology All devices of a network are connected together in a ring. With the aid of media redundancy methods, the fault tolerance and availability in this network is increased.

Router Network node with a unique identifier (name and address) that connects subnets together and allows transportation of data to uniquely identified communications nodes in the network.

RS-232, RS-422 and RS-485 Standardized data transmission method for serial data transmission.

RTU Modbus RTU (RTU: Remote Terminal Unit, transfers the data in binary form; allows a good data throughput. The data must be converted to a readable format before it can be evaluated.

S7 routing Communication between S7 automation systems, S7 applications or PC stations in different S7 subnets via one or more network nodes functioning as S7 routers.

SDA service Send Data with Acknowledge. SDA is an elementary service with which an initiator (for example DP master) can send a message to other devices and then receives acknowledgment of receipt immediately afterwards.

Glossary


SDN service Send Data with No Acknowledge. This service is used primarily to send data to multiple stations and therefore remains unacknowledged. Suitable for synchronization tasks and status messages.

Security Generic term for all the measures taken to protect against

● Loss of confidentiality due to unauthorized access to data

● Loss of integrity due to manipulation of data

● Loss of availability due to the destruction of data

Server A device or more generally an object that can provide certain services; the service is performed at the request of a client.

Slave Distributed device in a fieldbus system that can only exchange data with a master after the master has requested this.

SNMP Simple Network Management Protocol, uses the wireless UDP transport protocol. This works in much the same way as the client/server model. The SNMP manager monitors the network nodes and the SNMP agents collect the various network-specific information in the individual network nodes and stores it in a structured form in the MIB (Management Information Base). This information allows a network management system to run detailed network diagnostics.

Subnet Part of a network whose parameters must be matched up on the devices (for example in PROFINET). It includes the bus components and all connected stations. Subnets can be linked together, for example using gateways or routers to form one network.

Switch Network components used to connect several terminal devices or network segments in a local network (LAN).

TCP/IP Transmission Control Protocol / Internet Protocol, connection-oriented network protocol, generally recognized standard for data exchange in heterogeneous networks.

Glossary


Time-of-day synchronization Capability of transferring a standard system time from a single source to all devices in the system so that their clocks can be set according to the standard time.

Tree topology Network topology characterized by a branched structure: Two or more bus nodes are connected to each bus node.

Twisted-pair Fast Ethernet via twisted-pair cables is based on the IEEE 802.3u standard (100 Base-TX). The transmission medium is a shielded 2x2 twisted-pair cable with an impedance of 100 Ohms (22 AWG). The transmission characteristics of this cable must meet the requirements of category 5.

The maximum length of the connection between the terminal and the network component must not exceed 100 m. The connectors are designed according to the 100Base-TX standard with the RJ-45 connector system.

UDP User Datagram Protocol; communications protocol for fast and uncomplicated data transfer, without acknowledgement. There are no error checking mechanisms as found in TCP/IP.

User program In SIMATIC, a distinction is made between the operating system of the CPU and user programs. The user program contains all instructions, declarations and data by which a system or process can be controlled. It is assigned to a programmable module (for example, CPU, FM) and can be structured in smaller units.

USS Universal Serial Interface protocol (Universelles Serielles Schnittstellen-Protokoll); defines an access method according to the master-slave principle for communication via a serial bus.

Web server Software/communications service for data exchange via the Internet. The Web server transfers the documents using standardized transmission protocols (HTTP, HTTPS) to a Web browser. Documents can be static or put together dynamically from different sources by the Web server on request from the Web browser.

Glossary



Index

B BRCV, 42 BSEND, 42

C CM, 9 Communication

Communication protocols, 27 Data record routing, 61 Establishment and termination, 40 HMI communication, 25 Open communication, 27 Overview of the services, 15 PG communication, 23 Point-to-point link, 51 S7 communication, 41 S7 routing, 57

Communications module, 9 Communications processor, 9 Communications services, 15

Connection resources, 17 Overview, 15

Connection Diagnostics, 71 Instructions for open communication, 29

Connection diagnostics, 71 Connection resources

Data record routing, 69 Display in STEP 7, 64 HMI communication, 67 Module specific, 64 Overview, 17 Pin assignments, 63 S7 routing, 68 Station specific, 65

Consistency of data, 20 CP, 9

D Data consistency, 20 Data record routing, 61

Connection resources, 69 Documentation, 7

E E-mail, 15, 28, 37 Establishment and termination of open communication, 40

F FDL, 15, 28, 32 Fetch, 15 Firewall, 76 Freeport protocol, 51 FTP, 15, 28, 37

G GET, 42

H HMI communication, 15, 25

I IM, 13 Industrial Ethernet Security, 75 Instructions for open communication, 29 Interface module, 13 Interfaces for communication, 10 ISO, 15, 28 ISO-on-TCP, 28, 32

L Logging, 76

M Modbus protocol (RTU), 51

Index


N NTP, 15, 77

O Occupation of connection resources, 63 Open communication

Instructions, 29 Properties, 27 Protocols, 27 Setting up e-mail, FTP, 37 TCP, ISO-on-TCP, UDP, FDL, setting up, 32

P PDM, 61 PG communication, 15, 23 Point-to-point link, 15, 51 Procedure 3964(R), 51 Protocols of open communication, 27 PUT, 42

S S7 communication, 15, 41, 68 S7 routing, 57

Connection resources, 68 Security, 75 Security measures, 75

Firewall, 76 Logging, 76 NTP, 77 SNMP, 77

Setting up a connection, 18 By configuring, 34 ISO connection with CP 1543-1, 36 With the user program, 32

SIMATIC PDM, 61 SNMP, 15, 77 Syslog, 76 System data type, 30

T TCON, 29 TCP, 15, 28, 32 TDISCON, 29 Time-of-day synchronization, 15 TRCV, 29 TRCV_C, 29

TSEND, 29 TSEND_C, 29

U UDP, 15, 28, 32 URCV, 42 USEND, 42 USS protocol, 51

W Web server, 15 Write, 15