Siemens NCM S7 User manual

SIMATIC NET

NCM for Industrial Ethernet

Manual

for NCM S7 V5.2 and higher

Preface, Contents

Communication via Ethernet CPs in S7 Stations

Installing and Starting the

Ethernet CP with STEP 7

SEND/RECEIVE interface

Configuring Communication

Connections

Programmed Communication

Connections

Programming FCs (Functions) and FBs for S7 Ethernet CPs

NCM S7 Diagnostics

Firmware loader

Appendix

References

Glossary

Linking to Other Systems with

FETCH/WRITE

Document History

Index

C

D

A

B

3

4

1

2

5

6

7

8

Release 6/2003

C79000–G8976–C129–07

2

Classification of Safety-Related Notices

This manual contains notices which you should observe to ensure your own personal safety, as well as to protect the product and connected equipment. These notices are highlighted in the manual by a warning triangle and are marked as follows according to the level 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 can result if proper precautions are not taken.

Caution

with warning triangle indicates that minor personal injury can result if proper precautions are not taken.

Caution

without warning triangle indicates that damage to property can result if proper precautions are not taken.

Notice

indicates that an undesirable result or status can occur if the relevant notice is ignored.

Note

highlights important information on the product, using the product, or part of the documentation that is of particular importance and that will be of benefit to the user.

SIMATIC NET NCM S7 for Industrial Ethernet

Release 6/2003

C79000–G8976–C129–07

Trademarks

SIMATIC

R

, SIMATIC HMI

R

and SIMATIC NET

R

are registered trademarks of

SIEMENS AG.

Third parties using for their own purposes any other names in this document which refer to trademarks might infringe upon the rights of the trademark owners.

Safety Instructions Regarding your Product:

Before you use the product described here, read the safety instructions below thoroughly.

Qualified Personnel

Only qualified personnel should be allowed to install and work on this equipment.

Qualified persons are defined as persons who are authorized to commission, to ground, and to tag circuits, equipment, and systems in accordance with established safety practices and standards.

Correct Usage of Hardware Products

Note the following

!

Warning

This device and its components may only be used for the applications described in the catalog or the technical description, and only in connection with devices or components from other manufacturers which have been approved or recommended by Siemens.

This product can only function correctly and safely if it is transported, stored, set up, and installed correctly, and operated and maintained as recommended.

Before you use the supplied sample programs or programs you have written yourself, make certain that no injury to persons nor damage to equipment can result in your plant or process.

EU Directive: Do not start up until you have established that the machine on which you intend to run this component complies with the directive 89/392/EEC.

Correct Usage of Software Products

Note the following

!

Warning

This software may only be used for the applications described in the catalog or the technical description, and only in connection with software products, devices, or components from other manufacturers which have been approved or recommended by Siemens.

Before you use the supplied sample programs or programs you have written yourself, make certain that no injury to persons nor damage to equipment can result in your plant or process.


Release 6/2003

C79000–G8976–C129–07

3

Prior to Startup

Before putting the product into operation, note the following warning:

Caution

Prior to startup you must observe the instructions in the relevant documentation.

For ordering data of the documentation please refer to the catalogs or contact your local SIEMENS representative.

Copyright

E

Siemens AG 2001–2003 All rights reserved

The reproduction, transmission or use of this document or its contents is not permitted without express written authority. Offenders will be liable for damages. All rights, including rights created by patent grant or registration of a utility model or design, are reserved.

Disclaimer of Liability

We have checked the contents of this manual for agreement with the hardware and software described. Since deviations cannot be precluded entirely, we cannot guarantee full agreement. However, the data in this manual are reviewed regularly and any necessary corrections included in subsequent editions. Suggestions for improvement are welcomed.

Siemens AG

Automation and Drives

Industrial Communication

Postfach 4848, D-90327 Nürnberg

4

Siemens Aktiengesellschaft


Subject to technical change.

Release 6/2003

G79000-G8976-C129-07

C79000–G8976–C129–07

This Manual on SIMATIC NET NCM S7 for

Industrial Ethernet

...supports you when using the communication services provided by the SIMATIC

NET communications processors (Industrial Ethernet CPs) for communication on

SIMATIC NET with Industrial Ethernet in the management and cell areas.

The documentation on your S7 CPs and NCM S7 is in several parts that fit together as shown below:

S

S7-CP

– selecting

– installing

– commissioning

– performance data

Manual

S

S7-CP and STEP 7 / NCM S7

– familiarization

– testing interfaces

– commissioning

Primer

S7-CP

for

S7-300 /

S7-400

STEP 7

NCM S7

S

Communication services with STEP 7 / NCM S7

– programming

– configuring

– downloading / commissioning

– diagnostics

NCM S7

Manual


Release 6/2003

C79000–G8976–C129–07

5

This Manual on SIMATIC NET NCM S7 for Industrial Ethernet

Audience

This manual is intended for personnel responsible for installing and programming

STEP 7 programs and for service personnel.

Scope of this Manual

This manual applies to version 5.2 and higher of the NCM S7 configuration software for Industrial Ethernet and to version 5.2 and higher of the STEP 7 software.

This manual also includes specially marked passages that apply specifically to and require version 5.2 SP1 of the NCM S7 for Industrial Ethernet configuration software and version 5.2 SP1 of the STEP 7 software.

These include new functions for IP configuration:

S

IP access protection

Using IP access protection gives you the opportunity of restricting access to the local S7 station to partners with specific IP addresses.

S

Configuring connections from the user program

In some situations, it is an advantage to set up communication connections not over the configuration interface of STEP 7 but program-controlled by specific applications.

As of STEP 7 V5.2 SP1, a function block is available for these applications that allows flexible transfer of data blocks with configuration data to an Ethernet CP.

The description of the configuration for FETCH / WRITE services has been extended.

Notice

Please note that the availability of new functions depends on the type of CP you are using. You can check which functions your module supports in the description in the Properties dialog in STEP 7 and in the catalog in HW Config.

The manual contains more detailed information /1/.

6


Release 6/2003

C79000–G8976–C129–07


Symbols Used in this Manual

Unless indicated otherwise, the functions described in this manual assume the use of STEP 7. This symbol is used to indicate functions that require a specific version of STEP 7 or higher, for example Version V5.2.

This symbol appears in the margin to draw your attention to useful tips.

This symbol indicates recommended documentation.

Where you see this symbol, you should also refer to additional information in the basic help system of STEP 7.

F1

This symbol indicates where detailed context-sensitive help is available. You can display these help texts with the F1 key or by clicking on the “Help” button in the relevant dialog.

Conventions

References to other manuals and documentation are indicated by numbers in slashes /.../. These numbers refer to the titles of manuals listed in the References section of the Appendix.


Release 6/2003

C79000–G8976–C129–07

7


You will find additional information in the following sources:

This manual is also part of the NCM S7 for Industrial Ethernet documentation package. These documents are also on the Manual Collection CD supplied with every S7 CP and they are also available on the Internet. The following table provides you with an overview.

Title Content

S7-CPs for Industrial

Ethernet

Manual

The manual S7 CPs for Industrial Ethernet contains information on the characteristics of the CPs and instructions on installation and connections.

This is available on the Internet at:

S

General Section: http://www4.ad.siemens.de/view/cs/de/8777865

S

CP 343-1: http://www4.ad.siemens.de/view/cs/de/8777308

S

CP 343-1 PN: http://www4.ad.siemens.de/view/cs/de/8776538

S

CP 343-1 IT: http://www4.ad.siemens.de/view/cs/de/8776544

S

CP 443-1:

S

CP 443-1 IT: http://www4.ad.siemens.de/view/cs/de/8776219 http://www4.ad.siemens.de/view/cs/de/8776322

NCM S7 for Industrial

Ethernet

Primer

Based on simple examples, the primer introduces you to the methods of connecting and networking SIMATIC S7 stations with CPs on Industrial

Ethernet. It shows you how the communications calls are entered in the user program to allow you to use the services via the SEND/RECEIVE interface.

You will learn how simple it is to create a configuration for standard applications using STEP 7 and the NCM S7 optional package.

The examples described here can also be found in the project folder for sample programs after you have installed STEP 7 and the NCM S7 for

Industrial Ethernet option!

NCM S7 for Industrial

Ethernet

Manual

This is available on the Internet at: http://www4.ad.siemens.de/view/cs/de/1172503

The manual is intended as a guide and reference work for configuring and programming an Industrial Ethernet CP.

IT-CP

Manual

Advanced PC

Configuration

Commissioning PC

Stations

Manual


The manual is intended as a guide and source of reference when working with the IT-CP. In addition to the functions provided by an Ethernet CP, the IT-CP also provides functions for Internet technology.


Advanced PC Configuration is the new tool with which you can commission a

PC station as part of an industrial communication network.

The manual supports you and helps you to make efficient use of communications with your PC applications in conjunction with the SIMATIC

NET modules. It explains the steps involved in configuration with NCM S7.

This is available on the Internet at: http://www4.ad.siemens.de/view/cs/13542666

8


Release 6/2003

C79000–G8976–C129–07


Quick Start CD: Samples covering all aspects of communication

The Quick Start CD that can be ordered separately is a treasure-trove of sample programs and configurations.

You can order this directly over the Internet at: http://www4.ad.siemens.de/view/cs/de/574211

Additional Information on SIMATIC S7 and STEP 7

The following documentation contains additional information about the STEP 7 standard software of the SIMATIC programmable controllers and can be obtained from your local Siemens office.

Topic

Basic information for technical personnel using the STEP 7 standard software for control tasks with S7-300/400 programmable controllers.

The reference works describing the programming languages

LAD/FBD and STL as well as the standard and system functions in addition to the STEP 7 basic knowledge.

Document

STEP 7 basics with

S

Configuring hardware with STEP 7

S

Programming with STEP 7

S

Manual for converting from S5 to S7

S

Primer for a fast start

STEP 7 reference manuals with

S

Manuals for LAD/FBD/STL

S

Standard and system functions for S7-300/400

You will also find information on SIMATIC programmable controllers on the Quick

Start CD and from the Customer Support Online services at: or


Release 6/2003

C79000–G8976–C129–07

9


Access to Online Help of STEP 7 and NCM S7

With the online help, you can obtain the following information:

S

You can display the contents of the STEP 7 basic help system with the menu command Help –> Contents.

F1

S

Context-sensitive help on the selected object using the Help –> Context-Sensitive

Help menu command, the F1 function key or the question mark in the toolbar.

You can then access further information relating to the current topic.

S

Glossary for all STEP 7 applications by clicking the “Glossary” button.

Please note that each STEP 7 application has its own contents and context-sensitive help.

-

10


Release 6/2003

C79000–G8976–C129–07

2

3

1

Contents

Communication via Ethernet CPs in S7 Stations . . . . . . . . . . . . . . . . . . . . . . . . . .

1.1

1.2

Industrial Ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SIMATIC S7 Communication with S7 Ethernet CPs . . . . . . . . . . . . . . . . . .

1.3

1.3.1

1.3.2

PG/OP Communication via Industrial Ethernet . . . . . . . . . . . . . . . . . . . . . .

PG Communication with STEP 7 over Industrial Ethernet . . . . . . . . . . . . .

OP Operation: Connecting Operator Interface Devices via


S7 Communication on Industrial Ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.4

1.5

1.6

1.7

1.7.1

1.7.2

1.7.3

1.7.4

1.7.5

1.7.6

S5-compatible Communication (SEND/RECEIVE Interface) ) . . . . . . . . . .

FETCH/WRITE Services (Server) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Networking Stations with STEP 7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Network/Project Variant: One Subnet – One Project . . . . . . . . . . . . . . . . . .

Network/Project Variant: SIMATIC S5 and Non-SIMATIC

Devices on the Subnet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Network/Project Variant: Two or More Subnets – One Project . . . . . . . . .

Network/Project Variant: One Subnet – More Than One (Sub)Project

Network/Project Variant: Several Subnets in Several (Sub) Projects

Network/Project Variant: Connections between Subnets (TCP/IP)

. . .

. . . .

. . . . . .

Installing and Starting the Ethernet CP with STEP 7 . . . . . . . . . . . . . . . . . . . . . . .

2.1

General Information About the NCM S7 for Industrial Ethernet Option . .

3.1

3.2

3.3

3.4

3.4.1

3.4.2

2.2

2.2.1

2.2.2

2.2.3

2.2.4

2.2.5

2.2.6

2.3

2.3.1

2.3.2

2.4

Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Creating an Industrial Ethernet Subnet . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Entering an Ethernet CP in the Hardware Configuration . . . . . . . . . . . . . .

Displaying the Network Attachments of a Station

Setting Further CP Properties

. . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

“Substitute Objects” in the STEP 7 Project

Configuring Communication Services

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Assigning Addresses for the First Time (Applies to Latest CPs)

Addressing by Selecting the Target System in the SIMATIC Manager

Addressing using the Properties Dialog in HW Config or NetPro

. . . . . . . .

. . .

. . . . . . .

Downloading the Configuration Data to the Target System . . . . . . . . . . . .

SEND/RECEIVE Interface in the User Program . . . . . . . . . . . . . . . . . . . . . . . . . . . .

How the SEND/RECEIVE Interface Works on the CPU

Programming the SEND/RECEIVE Interface

Data Exchange S7 CPU <–> Ethernet CP

Additional Information

. . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Programming Data Transfer on TCP Connections . . . . . . . . . . . . . . . . . . .

Recommendations for Use with a High Communications Load . . . . . . . . .

36

37

38

41

43

45

46

47

48

51

55

57

65

68

69

70

73

74

77

78

79

82

84

84

85

24

25

29

32

33

35

15

16

17

21

23


Release 6/2003

C79000–G8976–C129–07

11

Contents

4

5

5.5

5.5.1

5.5.2

5.5.3

5.5.4

5.5.5

5.6

5.1

5.2

5.3

5.4

Configuring Communication Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.1

Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.2

4.3

4.3.1

4.3.2

4.3.3

4.3.4

Possible Connection Configurations

Connections

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

New Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Connections to Partners in Other Projects

Further Functions

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Connections Without Assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.4

4.4.1

4.4.2

4.4.3

4.4.4

4.5

4.5.1

4.5.2

4.5.3

Configuring ISO Transport Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Specifying the Local Connection Endpoint . . . . . . . . . . . . . . . . . . . . . . . . . .

Specifying ISO Transport Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Specifying ISO Transport Dynamic Properties . . . . . . . . . . . . . . . . . . . . . . .

Checking ISO Transport Connection Properties . . . . . . . . . . . . . . . . . . . . .

Configuring ISO-on-TCP Connections Properties . . . . . . . . . . . . . . . . . . . .

Specifying the Local Connection Endpoint

Specifying ISO-on-TCP Addresses

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Checking ISO-on-TCP Connection Properties . . . . . . . . . . . . . . . . . . . . . . .

4.6

4.6.1

4.6.2

4.6.3

4.7

4.7.1

4.7.2

4.7.3

4.7.4

4.7.5

4.8

Configuring TCP Connection Properties

Specifying the Local Connection Endpoint

Specifying TCP Addresses

. . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Checking TCP Connection Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Configuring UDP Connection Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Specifying the Local Connection Endpoint . . . . . . . . . . . . . . . . . . . . . . . . . .

Specifying UDP Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

UDP with Broadcast and Multicast . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Checking the Properties of a UDP Connection . . . . . . . . . . . . . . . . . . . . . . .

Free UDP Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

FETCH/WRITE Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.9

Routing to Distribute Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Programmed Communication Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Configuration Data Block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Parameter Field for System Data

(CP Networking) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Parameter Fields for Connection Types

Parameter Field for TCP Connection

. . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Parameter Field for a UDP Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Parameter Field for an ISO-on-TCP Connection . . . . . . . . . . . . . . . . . . . . .

Parameter Field for an E-Mail Connection

Parameter field for FTP connection

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Subfield types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

150

152

153

154

155

156

158

159

119

120

123

126

127

128

130

133

137

138

139

103

104

106

109

111

112

113

115

118

143

145

146

148

149

87

88

89

91

94

96

99

100

12


Release 6/2003

C79000–G8976–C129–07

Contents

6

7

8

Programming FCs (Functions) and FBs for S7 Ethernet CPs . . . . . . . . . . . . . . .

6.1

General Notes on FCs / FBs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.2

6.2.1

6.2.2

6.2.3

6.3

6.3.1

6.3.2

Setting Parameters for FC Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Parameters for CP and Connection Assignment (input parameters)

Parameters for Specifying a CPU Data Area (input parameters)

Status Information (output parameters)

FCs for the SEND/RECEIVE Interface

FC5 AG_SEND / FC50 AG_LSEND

FC6 AG_RECV / FC60 AG_LRECV

. . . .

. . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.4

6.4.1

6.4.2

6.5

FCs for Access Coordination with FETCH/WRITE

FC7 AG_LOCK

. . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

FC8 AG_UNLOCK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

FB55 IP_CONFIG for Programmed Communication Connections . . . . . .

7.3

7.3.1

7.3.2

7.3.3

7.3.4

7.3.5

7.3.6

7.4

7.5

6.6

Numeric Data / Resource Requirements of the FCs . . . . . . . . . . . . . . . . . .

NCM S7 Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.1

7.2

7.2.1

7.2.2

Functions of NCM S7 Diagnostics

Installing and Starting NCM S7 Diagnostics

General Menu Commands

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Starting Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Establishing a Connection to the Ethernet CP . . . . . . . . . . . . . . . . . . . . . . .

Starting Diagnostics from the CP Properties Dialog

Starting Diagnostics from the Windows Start Menu

. . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . .

Using a Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Using the PC Station – Setting a Gateway with “PC internal” . . . . . . . . . .

Other Ways of Starting Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

How to Use Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Starting Diagnostic Functions Explicitly . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7.6

7.6.1

7.6.2

Checklist for “Typical Problems” in a System

Checklist for General CP Functions

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Communication Connections Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Firmware Loader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

8.1

8.2

Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Loading Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

206

207

208

210

212

212

212

213

215

217

218

219

220

222

223

224

225

226

227

191

193

195

197

203

205

163

164

167

167

169

169

170

174

184


Release 6/2003

C79000–G8976–C129–07

13

Contents

A

B

C

D

References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B.1

B.2

General Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


B.3

PROFInet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Linking to Other Systems with FETCH/WRITE . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Document History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

240

243

249

251

229

233

234

238

14


Release 6/2003

C79000–G8976–C129–07

Communication via Ethernet CPs in S7

Stations

1

The Ethernet CP for SIMATIC S7 provides a series of communications services for different tasks.

This chapter explains the following:

S

The types of communication possible with the Ethernet CP on Industrial

Ethernet

S

The tasks handled by the Ethernet CP for the various services

S

How to create the conditions for your communications requirements

You will find further information in the following sources:

S

When installing the Ethernet CP, please refer to the instructions in the manual

/1/ supplied with the Ethernet CP. This also contains further information about the performance of the Ethernet CP .

S

For the functions and use of the STEP 7 configuration software, some of which is used to configure the CP (such as hardware configuration), please refer to /6/ and /8/.

S

For using, structuring and handling Industrial Ethernet, you will find detailed information in /11/.

S

For a general introduction to local area networks with TCP/IP refer to /16/ and

/17/.


Release 6/2003

C79000–G8976–C129–07

15

Communication via Ethernet CPs in S7 Stations

1.1


Definition

Within the open, heterogeneous SIMATIC NET communication system, Industrial

Ethernet is the network for the management and cell level. Physically, Industrial

Ethernet is an electrical network that uses a shielded coaxial cable or twisted pair, or an optical network with fiber-optic cables.

Industrial Ethernet is defined by the international standard IEEE 802.3 (see /11/).

All-Round Communication in the Industrial Sector

Industrial Ethernet is integrated in the SIMATIC NET concept that allows comprehensive networking of the management, cell and field levels in conjunction with PROFIBUS and the AS-interface (AS-i).

Industrial

Ethernet

(IEEE 802.3)

PROFIBUS

(EN 50170 Vol. 2 PROFIBUS)

AS-Interface

(AS-i, Actuator-Sensor Interface)

Figure 1-1 Industrial Ethernet in the SIMATIC NET Concept

Network Access

Industrial Ethernet is accessed using the CSMA/CD (Carrier Sense Multiple

Access with Collision Detection) network access technique specified in

IEEE 802.3.

16


Release 6/2003

C79000–G8976–C129–07


1.2

SIMATIC S7 Communication with S7 Ethernet CPs

Types of Communication

The Ethernet CP for SIMATIC S7 supports the following types of communication depending on the CP type:

S7/M7-400

Ethernet CP

Ethernet CP

S7-300

Possible types of communication

S

PG/OP communication

S

S7 communication

S

S5-compatible communication

S

PROFInet communication

S

HTML process control with web browser

S

File management and file access with FTP

Interfaces / Services /

Protocols with the protocols

– ISO

– TCP/IP (RFC 1006) with the SEND / RECEIVE interface and the protocols

– ISO Transport

– ISO-on-TCP (TCP/IP with RFC 1006)

– TCP

– UDP

– E-mail with FETCH / WRITE services and the protocols

– ISO Transport

– ISO-on-TCP

– TCP with the protocols

– TCP with the protocols

– HTTP / IP protocol with the protocols

– FTP / IP protocol

S

PG/OP communication

PG/OP communication is used to download programs and configuration data, to run tests and diagnostic functions, and to control and monitor a plant from

OPs.


Release 6/2003

C79000–G8976–C129–07

17


18

S

S7 communication

S7 communication forms a simple and efficient interface between SIMATIC S7 stations and PGs/PCs using communication function blocks.

S

S5-compatible communication with SEND/RECEIVE interface

Depending on the CP type, the SEND/RECEIVE interface allows program-controlled communication on a configured connection from a SIMATIC

S7 PLC to another SIMATIC S7 PLC, to a SIMATIC S5 PLC, to PCs/PGs, and to any other station.

Depending on the CP type, the following communications services are available on the SEND/RECEIVE interface:

– ISO Transport optimized for top performance at the self-contained manufacturing level

– TCP/IP for internetwork communication with

ISO-on-TCP connections (RFC 1006), TCP connections and

UDP datagram service (including broadcast / multicast).

– Sending E-mail

The controller is capable of sending messages triggered by process events

(refer to the IT-CP manual for details /5/).

S

S5-compatible communication with FETCH/WRITE services (server)

The FETCH/WRITE services (server) allow direct access to the system memory areas on the SIMATIC S7 CPU from SIMATIC S5, SIMATIC PC stations, or from devices of other ranges.

Depending on the CP type, the following communications services are available for FETCH/WRITE access:

– ISO Transport optimized for top performance at the self-contained manufacturing level

– TCP/IP for internetwork communication with

ISO-on-TCP connections (RFC 1006), TCP connections.

S

PROFInet communication

PROFInet is a standard of the PROFIBUS Users organization defining a heterogeneous communications and engineering model.

An S7-300 station equipped with a CP capable of PROFInet can be interconnected as a PROFInet component in SIMATIC iMap.

TCP connections are used for the PROFInet communication.

For more detailed information on PROFInet, refer to /23/.

S

HTML process control

With an IT-CP, use the supplied functions and HTML pages to query important system data using a Web browser (you should also refer to the instructions on the IT-CP /5/).


Release 6/2003

C79000–G8976–C129–07


S

File management and file access with FTP

The IT-CP (S7-400 / S7-300) provides additional functions for FTP services.

You can use your S7 station both as an FTP client and as an FTP server (refer to the manual of the IT-CP /5/).

– S7 Station as FTP Client

You can transfer data blocks from or to a file server.

– S7 Station as FTP Server

Another station, for example, a PC transfers data blocks to or from the S7 station the file system on the IT-CP.

Possibilities for Communication between Device Types

The possible communication available with the types of communication listed above is shown in the following table:

PC station

S7-400 S5-115 to -155U/H

S7-300

S7-300

S7 communication

SEND/RECEIVE

PROFInet

S7 communication

SEND/RECEIVE

SEND/RECEIVE

FETCH/WRITE

S7/M7-400

S7 communication

SEND/RECEIVE

S7 communication

SEND/RECEIVE

FTP services

SEND/RECEIVE

FETCH/WRITE

PG/OP communication

1)

S7 communication

1)

SEND/RECEIVE

FETCH/WRITE

HTML process control

PROFInet

FTP services

PG/OP communication

1)

S7 communication

1)

SEND/RECEIVE

FETCH/WRITE

HTML process control

FTP services

1) PC only as client


Release 6/2003

C79000–G8976–C129–07

19


Configuration and Diagnostics

To connect and configure the Ethernet CP, you require the STEP 7 configuration software and the SIMATIC NET NCM S7 for Industrial Ethernet option.

NCM S7 for Industrial Ethernet is installed as a STEP 7 option and is therefore integrated in STEP 7.

NCM S7 for Industrial Ethernet also provides a wide range of diagnostic functions for the various types of communication.

When configuring PROFInet communication, you also use the engineering tool

SIMATIC iMap; for detailed information on SIMATIC iMap, refer to the manual

Component based Automation – Configuring Plants with SIMATIC iMap /23/.

Programmed Connections

In some situations, it is an advantage to set up communication connections not

V 5.2.1

over the configuration interface of STEP 7 but program-controlled by specific applications.


20


Release 6/2003

C79000–G8976–C129–07


1.3

PG/OP Communication via Industrial Ethernet

Application

PG/OP communication provides functions that are already integrated in every

SIMATIC S7/M7/C7 device.

A distinction must be made between the following two types of function:

S

PG communication

PG communication with STEP 7 PLCs on Industrial Ethernet means the following:

– You can use the complete range of functions of STEP 7 on Industrial

Ethernet.

– You can use programming, diagnostic, operating and monitoring functions on all modules in the SIMATIC S7 PLC via Industrial Ethernet.

S

OP Operation

PG/OP communication on Industrial Ethernet allows the operation and monitoring of all modules in a SIMATIC S7 PLC using operator interface systems (TD/OP).

The Ethernet CP acts as a “communications relay” that relays the PG/OP communication via Industrial Ethernet.


Release 6/2003

C79000–G8976–C129–07

21


Operator interface functions

Ethernet attachment

OP

STEP 7

NCM S7

PC with Ethernet CP

Modem /

ISDN

S7 – 400

Ethernet CP

Create configuration data for every CP and download to the

Ethernet CPs

Ethernet

S7 – 300

Ethernet CP

S7 – 400

WAN *

* only TCP/IP

Ethernet CP

Figure 1-2 Configuration for PG/OP Operation

22


Release 6/2003

C79000–G8976–C129–07


1.3.1

PG Communication with STEP 7 over Industrial Ethernet

Requirements for PG Communication

PG communication is possible when the following requirements are met:

S

An Ethernet CP is installed in the PG or engineering station or there is a modem/ISDN interface for remote access.

S

The Ethernet CP must have an address (default MAC address or set the IP address).

Networking the PG / Engineering Station

Depending on the configuration of the PG or Engineering Station, the following two situations are possible when using PG communication:

S

PG / Engineering Station in the Configured Mode

If you select this configuration when you commission the PG / engineering station, the interfaces of the communication modules you are using are already known. The option in “Set PG/PC Interface” is automatically set to

“PC-internal”.

Once you have downloaded this configuration to your PG / engineering station, you can exchange PG functions with the accessible nodes in the network with

STEP 7 without requiring any further settings.

S

PG / Engineering Station in PG Operation

If your PG or engineering station is configured for this mode, you must specify the interface on the PG or engineering station explicitly with “Set PG/PC Interface”.

Follow the steps outlined below:

1. Open the “Set PG/PC Interface” dialog box in the Windows Control Panel.

2. Set the PG/PC interface according to the CPs available on your PG and according to the bus attachment (interface parameter assignment used).

For more detailed information on the topic of PG operation and engineering station, refer to /4/.


Release 6/2003

C79000–G8976–C129–07

23


1.3.2

OP Operation: Connecting Operator Interface Devices via


Requirements

Operation allowing operator interface functions is possible when the following conditions are met:

S

The operator interface device has:

– an Ethernet CP installed

– SOFTNET S7 for Ind. Ethernet or S7-1613/ WIN 95, WIN NT, MS-DOS,

Windows installed.

S

The CPs in the S7 stations are supplied with a MAC/IP address (use the default

MAC address or set an IP address).

Procedure

To be able to use S7 communication, address the required module in the SIMATIC

S7 PLC on your operator interface system.

For more detailed information, refer to the description of your operator interface system.

24


Release 6/2003

C79000–G8976–C129–07


1.4

S7 Communication on Industrial Ethernet

Application

S7 communication via Industrial Ethernet allows program-controlled communication using communication SFBs/FBs via configured S7 connections.

Per job, up to 64 Kbytes of user data can be transmitted.

The Ethernet CP acts as an “S7 communication relay” by passing on the S7 functions via Industrial Ethernet (see /8/). Depending on the configuration of the

Ethernet CP, data transfer is on the basis of the ISO transport or the ISO-on-TCP protocol (TCP/IP with RFC 1006).

From the perspective of the user, S7 communication is identical over PROFIBUS and Industrial Ethernet.

Nodes

Two situations can occur depending on device type and plant configuration:

S

Client and server functionality at both ends

S7 connections can be operated between the following nodes with the entire functionality of S7 communication:

– between S7 stations S7-300 and S7-400;

– between S7 stations and PC/PG stations with an Ethernet CP.

S7 – 400

Ethernet CP

S7 – 300

Ethernet CP

M7

Ethernet

WAN *

* only TCP/IP

PC/PG with Ethernet CP

S7 – 300 / 400

Figure 1-3 Nodes Communicating on S7 Connections over Industrial Ethernet


Release 6/2003

C79000–G8976–C129–07

PUT / GET

BSEND / BRECV

USEND / URECV

25


S

Client and server functionality at one end only (S7 connections configured at one end)

In the following situations, write and read functions can be implemented with

PUT / GET:

– S7 communication over router

PG/PC stations can access S7 stations if the PG/PC stations are connected to a different subnet or subnet type (PROFIBUS / Ethernet) via routers (for example, an IE/PB Link); in this case, S7 stations are servers.

S7 communication is possible over a gateway.

Ethernet CP

S7 – 300

S7 – 400

Ethernet CP

PUT / GET

Ethernet

PC/PG Station

Ethernet

IE/PB Link

PROFIBUS

PC/PG Station

PUT / GET

Figure 1-4 PC/PG station communicates over a gateway with S7 stations on an underlying PROFIBUS or Ethernet

For more detailed information on the features supported by your Ethernet CP, refer to the manual /1/.

26


Release 6/2003

C79000–G8976–C129–07


Configuring S7 Connections

Create S7 connections to use S7 communication for data exchange between two

SIMATIC S7 stations.

For more detailed information, refer to the STEP 7 Description /6/ /8/.

Notice

S7 connections via routers are supported only within a STEP 7 project but not between partners in different STEP 7 projects of a multiproject!

Interface in the User Program of the S7 Station

You use SFBs (for S7-400) and FBs (for S7-300) in the user program.

SFB / FB12

SFB / FB13

SFB / FB15

SFB / FB14

SFB / FB8

SFB / FB9

SFC / FC62

Block Type

BSEND

BRCV

PUT

GET

USEND

URCV

CONTROL (S7-400) /

C_CNTRL (S7-300)

Client

x x x x

– x

1) you do not need to configure a connection on the server

2) for S7-300

Server

– x

–

1)

–

1)

– x x

2)

Described in

STEP 7 t ti /9/

Notice

Please remember the following points regarding data consistency in your user program:

In the CPU of the S7 station, the read or written information is taken from the S7 user program into the operating system or copied from the operating system to the

S7 user program in blocks of 8 or 32 bytes (depending on the firmware version).

If information in the word or double-word format is located across such boundaries, data inconsistency may arise during transmission using S7 communication!

For more detailed information, refer to the STEP 7 documentation /9/.


Release 6/2003

C79000–G8976–C129–07

27


Notes on S7 Communication between PC/PG Station and S7 Station

Applications in a PC/PG station communicate with the S7 station over an OPC interface or SAPI-S7 interface for operator intervention, monitoring and control.

The S7 stations use the integrated communication SFBs/FBs (client and server functionality at both ends).

The following general requirements must be met by a PC/PG station for S7 communication:

S

On the PC/PG:

– an Ethernet CP installed

– there is an interface for S7 communication installed: SOFTNET S7 for Ind.

Ethernet or S7-1613/ WIN 95, WIN NT, MS-DOS, Windows.

S

The CPs in the S7 stations are supplied with a MAC/IP address (use the default

MAC address or set an IP address).

To use S7 communication with the SIMATIC S7 PLC from a PC, address the

required CPU module in the SIMATIC S7 PLC that you want to communicate

with in your PC application.

S7 Communication via Routers (one-sided Client and Server Functionality)

It is possible to reach the S7 station from an application (OPC server) of the

PC/PG station that is attached to another subnet. The subnets must be connected over a router such as the IE/PB Link. An S7 station or a PC connected to both subnets can also serve as a router.

In this configuration, the S7 station can only be addressed by the PC/PG station as a communications server on S7 connections configured at one end.

The requirements for the configuration of the PC/PG station are identical to those for operation in the same subnet (see above); the CP in the PC/PG station must also have routing capability.

In this situation, configure a one-ended S7 connection to the PC/PG station in the other subnet for the PC/PG station in STEP 7 NetPro. You can then access data in the S7 station in your user program using the functions PUT (writing) and GET

(reading).

28


Release 6/2003

C79000–G8976–C129–07


1.5

S5-compatible Communication (SEND/RECEIVE

Interface)

1

)

Application

Using the SEND/RECEIVE interface, your S7 user program has access to

S5-compatible communication with configured transport connections.

Data transmission on a configured transport connection is suitable for

S the reliable transmission of related blocks of data between two Ethernet nodes using

– TCP (see /17//19//20/) with ISO-on-TCP connection (see /18/) or TCP connection;

– ISO transport connection

S simple (unacknowldeged) transfer of related blocks of data (datagram service) between two Ethernet nodes with UDP (User Datagram Protocol) on IP.

The SEND/RECEIVE interface is also suitable for sending E-mail (refer to the manual for the IT-CP /5/).

For TCP applications, there is an active network with IP protocol (see /20/).

ISO Transport Connection

ISO transport provides services for the reliable transfer of data on configured connections. Due to the segmentation of the data, large amounts of data can be transmitted.

Transmission reliability is extremely high due to automatic repetition and additional field check mechanisms. The communications partner confirms reception of data and the sender receives a return value on the SEND/RECEIVE interface.

ISO transport is operated only on Industrial Ethernet and is optimized for high-performance operation at the self-contained manufacturing level.

1 The previous name of the SEND/RECEIVE interface was S5S5 connections


Release 6/2003

C79000–G8976–C129–07

29


IP (Internet Protocol)

For internetwork data transmission, the following services are available with suitable CPs such as the CP 443-1:

S

ISO-on-TCP connection

ISO-on-TCP is intended for reliable, internetwork data transmission.

The ISO-on-TCP service corresponds to the TCP/IP standard (Transmission

Control Protocol/Internet Protocol) with the RFC 1006 extension according to layer 4 of the ISO reference model (see /18/).

RFC 1006 extends the TCP protocol by allowing the transmission of blocks of data (“messages”) assuming that both partners support RFC 1006.

Transmission reliability is extremely high due to automatic repetition and additional field check mechanisms. The communications partner confirms reception of data and the sender receives a return value on the

SEND/RECEIVE interface.

S

TCP connection

When using the SEND/RECEIVE interface on TCP connections, the Ethernet

CP supports the socket interface (for example, Winsock.dll) to TCP/IP found on almost every system (PC or other system).

TCP is intended for reliable internetwork data transmission.

The TCP service complies with the TCP/IP standard (Transmission Control

Protocol/Internet Protocol; see /18/).

S

UDP connection

UDP is intended for simple internetwork data transmission without confirmation.

If the connection is suitably configured, broadcast and multicast frames can also be sent on UDP connections.

To avoid overload due to high broadcast load, the CP does not allow reception of UDP broadcasts. As an alternative, use the multicast function over a UDP connection. This allows you to register the CP as a node in a multicast group.

SEND/RECEIVE

Interface

Data transfer is triggered by the user program. The interface to the user program in the SIMATIC S7 is formed by special SIMATIC S7 blocks of the type FC

(functions).

30


Release 6/2003

C79000–G8976–C129–07


Stations

The SEND/RECEIVE interface allows program-controlled communication on

Industrial Ethernet between the SIMATIC S7 PLC and the following:

S

SIMATIC S7 PLC with Ethernet CP

S


S


S

Other station with Industrial Ethernet attachment

S7 – 400

Ethernet CP

S7 – 300

Ethernet CP

Ethernet

D D D

D D D

D D D

D D D

SIMATIC S5 with Ethernet CP

Other station with

Ethernet attachment PG/PC with Ethernet attachment

WAN

Internet

Router only TCP/IP

Figure 1-5 SIMATIC S7 PLC with Possible Communications Partners on the SEND/RECEIVE Interface


Release 6/2003

C79000–G8976–C129–07

31


1.6

FETCH/WRITE Services (Server)

Application

In addition to the SEND/RECEIVE interface, the FETCH/WRITE functionality provides further services for S5-compatible communication on configured transport connections.

The FETCH/WRITE interface is used primarily to attach SIMATIC S7 to SIMATIC

S5 and to other non-S7 stations (for example PCs).

S

FETCH

The partner on the connection (SIMATIC S5 or non-S7 station) can read system data on the SIMATIC S7 PLC.

S

WRITE

The partner on the connection (SIMATIC S5 or non-S7 station) can write system data on the SIMATIC S7 PLC.

From the point of view of the SIMATIC S7 PLC, this is a passive communication function; the communications partner initiates the connection establishment.

For further information, refer to the system documentation of the SIMATIC S5 PLC or the non-S7 station you are using.

Connection Types

To access a station with FETCH or WRITE functions, a FETCH passive or WRITE passive connection must be configured. The following types are possible:

S

ISO Transport

S

ISO-on-TCP

S

TCP

Coordinating Access Using the User Program

To coordinate access, you can use the FCs AG_LOCK and AG_UNLOCK.

With these FCs, you can coordinate access to system memory areas so that no inconsistent data are created and transferred.

SIMATIC S5

On the SIMATIC S5 station, the FETCH/WRITE services are configured and started by READ ACTIVE/PASSIVE and WRITE ACTIVE/PASSIVE.

32


Release 6/2003

C79000–G8976–C129–07


1.7

Networking Stations with STEP 7

Configuring

To allow stations to communicate with each other the networks must be configured in the STEP 7 projects.

Configuring a network or subnet involves the following:

1. You create one or more subnets of the required subnet type in the project.

2. You select the properties of the subnet. Normally the default settings are adequate.

3. You connect the station “logically” to the subnet.

4. You set up connections for communication.

Networking in a Multiproject

STEP 7 as of Version V5.2 supports configuration in a multiproject.

Using a multiproject, for example, you can create a project for distributed editing by various editors and distribute the stations to the projects according to their editors.

To allow this, functions are available for branching and merging (sub) projects.

Interproject subnets and connections can be created.

Tools

The SIMATIC Manager provides convenient tools for configuring and documenting networks (also graphically with NetPro).

The chapter describing network configuration in /6/ and the online help system also contain information about configuring SIMATIC S7 networks.


Release 6/2003

C79000–G8976–C129–07

33


Variants

Before configuring networks with STEP 7, you should be aware of the various configurations possible in the STEP 7 project. The following configurations are typical for stations networked with CPs:

Variant (examples)

1

2

3

4

5

6

Characteristics/Configuration

1 subnet – 1 project

Additional SIMATIC S5 stations and stations with equipment of other vendors

2 or more subnets – 1 project

1 subnet – more than one project

More than one subnet – more than one project

Internetwork connections (TCP)

These variants will be used as a basis to illustrate how real configurations can be created in STEP 7 projects.

34


Release 6/2003

C79000–G8976–C129–07


1.7.1

Network/Project Variant: One Subnet – One Project

Configuration of the System

In the simplest case, your system consists of SIMATIC S7 stations connected by

one subnet, for example of the type Industrial Ethernet.

System

“Production”

S7-400/1

S7-300/1

Ethernet (1)

S7-300/2

View in a STEP 7 Project

You create an Industrial Ethernet object in the STEP 7 project. Stations created in the same project refer to this object as soon as they are configured as network nodes.


Release 6/2003

C79000–G8976–C129–07

35


1.7.2

Network/Project Variant: SIMATIC S5 and Non-SIMATIC Devices on the Subnet


In addition to SIMATIC S7 stations, SIMATIC S5 stations and non-SIMATIC devices can be included in your system.

System

“Production”

Non-SIMATIC

SIMATIC S5

S7-300/2


SIMATIC S5 stations you intend to include in the communication can be selected directly. Non-SIMATIC devices must be entered in the configuration as

Other stations.

36


Release 6/2003

C79000–G8976–C129–07


1.7.3

Network/Project Variant: Two or More Subnets – One Project


Due to the different tasks of the stations or due to the extent of the system it may be necessary to operate more than one network.

S7-400/1

System

“Production and Management Level”

Ethernet (1)

S7-400/2

Ethernet CP

PROFIBUS CP

PROFIBUS (1)

S7-300/1 S7-300/2


You can create the subnets in one STEP 7 project and configure the stations for communication.

This representation illustrates the following:

S

More than one subnet can be managed in one project.

S

Each station is created once in the project.

S

Each station can be assigned to more than one subnet by assigning its CPs to different subnets.


Release 6/2003

C79000–G8976–C129–07

37


1.7.4

Network/Project Variant: One Subnet – More Than One

(Sub)Project


In complex networked systems, during configuration it is sometimes more efficient to manage plant sections in different (sub) projects.

The situation can arise that communication takes place over an interproject subnet and that interproject connections must then also be created.

Example:

System section

“Production 2” System section

“Production 1”

S7 400/1

S7 – 400/2

Ethernet (1)

S7 300/1 S7 – 300/2 S7 – 300/3

Organization in a Multiproject

User-friendly and consistent configuration of such communication is supported in

STEP 7 as of Version V5.2 with the multiproject.

The functions for multiprojects in STEP 7 allow the following:

S

Several projects can be managed in one multiproject and edited separately

S

Projects can be branched and merged

Two different strategies can be distinguished in a multiproject:

S

Several employees work at the same time on a multiproject in a networked environment. The projects of the multiproject are in different network folders. In this case, all connection partners are available for configuring connections.

S

One employee manages the multiproject centrally. This person creates the structures for projects (when necessary locally) and contracts individual projects out for external editing. The central configuration engineer then returns these projects to the multiproject and synchronizes the interproject data with system support and where necessary executes the required interproject functions.

38


Release 6/2003

C79000–G8976–C129–07


In this case, agreement is necessary, for example, regarding the assignment of connection names because it will be far easier when synchronizing the projects to bring connections with identical connection names together.

The topic of multiprojects is dealt with in detail in the STEP 7 basic help.

Here, you will find information on the following topics:

S

Requirements for interproject functions

S

How to create multiprojects

S

How to create a new project in a multiproject

S

How to separate a project from a multiproject

S

How to include projects in the multiproject

S

How to synchronize projects in a multiproject

S

Moving stations within a multiproject (when a station is moved from one project of a multiproject to another project of the same multiproject (for example using drag & drop), the interproject connections are retained)

S

Possible problems in distributed projects and tips on how to avoid them

Possibilities for stations outside the current project

The addition of the multiproject functionality means that the following situations can arise:

S

Connection to a partner in an unknown project

The new multiproject functionality allows you to create a connection to a partner in an unknown project. In this case, you can specify a connection name as a reference in the properties dialog of the connection. When the projects are merged, STEP 7 then supports you with automatic synchronization of the separately configured connections.

The connection remains unspecified until the projects have been merged and the connections synchronized. Only following this synchronization can the configuration data be downloaded to the local station without inconsistencies.

You should therefore use this variant when you know that the projects will be merged in a multiproject.

S

Specified connections with representative objects

To allow you to create specified connections to stations in a different project (for example production 2) or that are not managed with STEP 7, you can configure these stations as other stations(example in the project production 1).

This makes it possible to create consistent, fully specified configuration data and to download it to the local station.

It is also possible to create specified connections between these stations in different, independent projects. The stations can then communicate immediately over the created connections after the configuration data have been downloaded.


Release 6/2003

C79000–G8976–C129–07

39


Use this variant when you want to operate projects separately due to the complexity.

Stations of the type SIMATIC S5 function in just the same way as representative objects.

Merging Projects in the Multiproject:

If you have used the multiproject functions allowing you to use connections to a partner in an unknown project, STEP 7 will automatically attempt to synchronize two separately configured connections.

If you have configured projects with representative objects and want to merge these projects into a multiproject, you have the following options:

S

You can leave the representative objects with the configured connections unchanged.

S

You can reassign the connection partner and then delete the representative objects.

40


Release 6/2003

C79000–G8976–C129–07


1.7.5

Network/Project Variant: Several Subnets in Several (Sub)

Projects


If several network types need to be used and if these need to be managed in different projects due to the different tasks of the stations or due to the large span of the plant, stations can be created as follows:

S

Using (sub) projects in the “multiproject”

S by configuring “Other stations / SIMATIC S5” in the other project.

Ethernet (1)

S7 – 400/1

Ethernet CP

PROFIBUS CP

Cell level = (sub)project 1

Cell level = (sub)project 2

PROFIBUS (1)

S7 – 300/1 S7 – 300/2


If you use a multiproject organization, follow the steps below to connect the

S7-400/1 station to the PROFIBUS (1) subnet:

Create a subnet of the type PROFIBUS in both subprojects and merge these two subnets in NetPro.


Release 6/2003

C79000–G8976–C129–07

41


Representative Objects for Stations Outside the Current Project

If you do not want to use the multiproject functions, you can fall back on the use of representative objects as used previously.

To be able to network the representative objects, you must once again create a subnet of the type PROFIBUS in both projects as shown in the example here.

42


Release 6/2003

C79000–G8976–C129–07


1.7.6

Network/Project Variant: Connections between Subnets

(TCP/IP)


If connections are required to stations on network structures connected by routers due to the differing tasks of the stations or the large span of the network, the stations in the other project can be reached by configuring “Other Stations”.

S7 – 400/1

Ethernet CP

Ethernet (1)

Router *

Ethernet (2)

WAN

Internet *

S7 – 400/2

Ethernet CP

S7 – 300/1

* only TCP/IP


If the stations in the two networks are managed in the same project, the networking appears as shown below in NetPro.


Release 6/2003

C79000–G8976–C129–07

43


44


Release 6/2003

C79000–G8976–C129–07

Installing and Starting the Ethernet CP with STEP 7

2

To attach a SIMATIC station to Industrial Ethernet via the Ethernet CP, configure the CP with the NCM S7 configuration software. The chapter explains the following:

S

How the CP is configured in the STEP 7 project

S

How the various network configurations are managed (setting up access to other systems)

S

How to control and supply the CP with data using NCM S7


S

When installing the Ethernet CP, please refer to the instructions in the manual

/1/ supplied with the Ethernet CP. This also contains further information about the performance of the Ethernet CP .

S

For more information about the functions and applications of STEP 7 in which the NCM S7 option is integrated, please read the following topics:

– For using the help functions, read the section Working with STEP 7 in /6/.

– Configuring and assigning parameters to modules in /6/

– Configuring networks in /6/. You will find this information in the online help with integrated in STEP 7 by selecting Help "

Contents.

S

You will find examples of configurations in the Primer /3/.


Release 6/2003

C79000–G8976–C129–07

45

Installing and Starting the Ethernet CP with STEP 7

2.1

General Information About the NCM S7 for Industrial

Ethernet Option

Installation

Please follow the instructions in the README file when installing the NCM S7 for

Industrial Ethernet option on your PG/PC under STEP 7.

Functions

NCM S7 consists of the following:

S

CP-specific index dialogs that you call using the properties dialog box of the modules.

S

Dialogs for the connection configuration

S

Diagnostic functions that you obtain as follows:

– Using the “Diagnostics” tab in the properties dialog

– Using the standard Start menu of Windows with which you can call the

SIMATIC program group

S

Functions displayed with SIMATIC " NCM... in the Start menu of Windows:

– Diagnostics

– Help for functions (FCs)

– “Readme” file with current information about NCM

– Firmware loader

Operation

Operating and handling the software package is as explained in the STEP 7 user manual /6/.

46


Release 6/2003

C79000–G8976–C129–07


2.2

Procedure

A CP is managed in an S7 project just as the other modules. You use STEP 7 to configure the hardware and create and manage the user software (see /6/).

Configuring a CP involves the following basic steps (the broken lines indicate options):

Create the Industrial Ethernet subnet (see 2.2.1)

Check or set the network properties

Enter the Ethernet CP in the hardware configuration

(see 2.2.2)

Attach the Ethernet CP to the Ethernet subnet

(see 2.2.2)

Display the network attachments of a station (see 2.2.3)

Make further CP settings (see 2.2.4)

Configuring communication connections (Chap. 4)

– S7 connections /6/

– ISO transport connections

– ISO-on-TCP connections

– TCP connections

– UDP alternative:

Program communication connections

(see Chapter 5)

Configuration data in the STEP 7 project

Programming the

SEND/RECEIVE interface

(see Chapter 3)

User programs in the STEP

7 project

Download the configuration to the PLC (see 2.4).


Release 6/2003

C79000–G8976–C129–07

47


2.2.1

Creating an Industrial Ethernet Subnet

Aims

To be able to attach the SIMATIC stations to a subnet, you create the subnet in your project. This means that all the parameters for the entire subnet are managed centrally.

Procedure

It is advisable to create the subnet before you configure the stations since the assignment of the SIMATIC stations is then performed largely automatically.

It is also possible to create the subnet at a later point in time when configuring a

CP. This is explained in more detail later in the chapter.

Follow the steps outlined below:

1. Select the project in the SIMATIC Manager.

2. Select Insert

"

Subnet

"

Industrial Ethernet.

Result: An object of the type network is created in the project. This allows all the SIMATIC stations created in the project to be attached to this subnet.

Figure 2-1 Project with Assigned Ethernet Network

48


Release 6/2003

C79000–G8976–C129–07


3. If you prefer a NetPro graphic network display, select the network object

“Ethernet” and confirm with Edit " Open Object.

Figure 2-2 Graphic Network Representation (here showing stations not yet networked)

From this graphic representation, you can also activate all the functions for networking and configuring connections with the Ethernet CPs.

You can also create the subnets in NetPro! Open the catalog using the menu command Insert "

Network Objects.


If you use the multiproject form of organization, this has the following effects when creating subnets.

You create subnets initially in the subprojects as described above. To be able to network S7 stations, you will, for example, need to create a suitable subnet of the type Industrial Ethernet in each subproject.

If this is physically a subnet that extends beyond the boundaries of the subproject, you should first merge the subnets before configuring the communication connections between the S7 stations.

If you do not merge the subnets, NetPro assumes that you are connecting the subnets via routers and displays warning messages to this effect.

Properties of Merged Subnets (Multiproject)

When you merge subnets, transferable subnet properties such as the subnet ID of the master subnet will be transferred to the other subnets of the group.

Some parameters relate specifically to a subproject and remain unchanged; these include, for example, descriptive parameters such as the name, author, and any comments.


Release 6/2003

C79000–G8976–C129–07

49


Notice

Preserving Consistency in Merged Subnets

After merging the subnets, you should check the consistency throughout the multiproject using the menu command Network > Check Interproject Consistency in

NetPro to make sure that there is consistency throughout the multiproject. This check detects, for example, S7 subnet IDs that are not unique within the multiproject.

50


Release 6/2003

C79000–G8976–C129–07


2.2.2

Entering an Ethernet CP in the Hardware Configuration

Procedure

By installing and assigning the Ethernet CP in the rack of a SIMATIC station, you establish the logical attachment between the Internet CP and the subnet.

1. Select the station in your project that you want to attach to Industrial Ethernet using an Ethernet CP.

2. Select the CP in the hardware configuration just like any other module by selecting it in the hardware catalog and then selecting the slot in the rack.

You select CPs in the hardware catalog using a short text and the order number. Once you have installed NCM S7, the CPs are available in the catalog.

Result: The CP is assigned to the SIMATIC station.

For information about the permitted slots, refer to /1/.

How to configure a module with STEP is described in detail in /6/.


Release 6/2003

C79000–G8976–C129–07

51


Subnet Attachment

To allow you to activate the network attachment of the Ethernet CP, the SIMATIC

Manager displays the following dialog:

52


Release 6/2003

C79000–G8976–C129–07


Note

You can open the dialog for setting the interface at any time from the Properties dialog of the CP in the “General” tab.

1. If you have not yet created a subnet in the project or have not yet created the selected subnet, you can now create a subnet. To do this, select the “New” button.

Result: An object of the type network is created in the project.

2. Check the addresses and if necessary change them. The system enters the next free address automatically.

You will find detailed information on the address ranges in the online help.

Please note the following additional information:

– MAC address

The latest Ethernet CPs are supplied with a default MAC address (address printed on the module). To be sure that you have a unique address assignment, do not enter a MAC address in the configuration (the option is deactivated). This means that the module automatically uses the factory-set address. If you want to use ISO services, we recommend that you enter the address printed on the module in the configuration.

Note

The “IP address” and “Subnet mask” input fields have no significance for ISO transport (option “IP protocol being used”).

3. Select the required subnet type in the “Subnet” list box.

4. You can display the properties dialog box for the selected subnet by clicking the

Properties button.

5. Enter information specific to the subnet node in the “General” tab.

6. You must finally confirm your input with OK, otherwise the networking is not entered (refer to Point 3.).

Result: The CP is now configured as a network node for the corresponding S7 station.


Release 6/2003

C79000–G8976–C129–07

53


Setting Addresses in the Configuration and Addressing for the First Time

The address settings described here are made on the CP only after you download the configuration data.

With the latest Ethernet CPs, the situation is as follows:

To be able to reach the CP using these addresses before you download the configuration data, you can address the CP using its default MAC address and then supply it with project-specific address information.

How to do this is described in Section 2.3.

54


Release 6/2003

C79000–G8976–C129–07


2.2.3

Displaying the Network Attachments of a Station

Procedure

You can easily get an overview of the network attachment configurations of a

SIMATIC station in one of the following ways:

S

A graphic overview in NetPro;

S

An overview in table form in the Properties dialog of the station

Graphic Overview in NetPro

The NetPro view provides you with a good overview of the networked stations:

Follow the steps below:

1. Double-click one of the network objects, for example Ethernet in your project in the SIMATIC Manager.

Figure 2-3 NetPro View of a Subnet of the Type Industrial Ethernet


Release 6/2003

C79000–G8976–C129–07

55


Overview in Table Form

The table view in the Properties dialog of the station provides a detailed overview of the components used for network attachment.

Follow the steps below:

1. Using the SIMATIC Manager, select the station in your project that you want to check.

2. Select the Object Properties using the menu option Edit "

Object Properties

or by double-clicking the station symbol.

3. Select the “Interfaces” tab.

Result:

Figure 2-4 “Interface” Tab in the “SIMATIC 300/400” Properties Dialog Box

In the displayed dialog, you can see the subnet attachments that were configured for the SIMATIC station.

56


Release 6/2003

C79000–G8976–C129–07


2.2.4

Setting Further CP Properties

Overview

In addition to the network attachment, you can also make further settings for the specific module or you can call functions.

1. Select the Ethernet CP in the hardware configuration.

2. Select Edit " Object Properties. Depending on your type of CP, the dialog includes other tabs in addition to the “General” tab described in Section 2.2.2:

F1

Tabs

General

Addresses

Options

Time-of-Day Synchronization

User

Symbols

DNS parameters

Diagnostics

Addressing

IP Access Protection

IP Configuration

Settings for

Interface

Interface parameters for the user program

Time-of-day synchronization

Data transfer

Replace module without PG

Ethernet profile for fault-tolerant connections

Individual network settings

Send keepalives for connections

Multiplex OP connections / reserve internal CPU connection resources

SIMATIC mode

NTP mode (NTP: Network Time Protocol)

Specify user permissions for IT functions

Symbolic access to variables using IT functions

Specify the address for the domain name server for E-mail services

Call NCM diagnostics (special diagnostics / module diagnostics)

Select the station to initialize

Assign configured IP parameters

Edit the IP access list

Set the IP address

Please read the description of the Properties dialog of the CP in the integrated help. The functions are explained in detail there.


Release 6/2003

C79000–G8976–C129–07

57


Addresses Tab

The Addresses tab displays the address at which the module can be addressed by the user program. You require this address when calling the FCs for transport connections –> see Chapter 6.

Notice

Please note the following notes on S7-300 stations:

If you selected the “Update OB1 process image cyclically” option in the CPU configuration (default), you must set the module base address of the Ethernet CP outside the process image (base addresses in the “Addresses” tab).

Example: If the size of the process image selected for the CPU is 1024 (0...1023), the address for the Ethernet CP must be set equal to or higher than 1024.

Options Tab

Depending on the CP type, you can make the following settings:

Table 2-1 Settings in the “Options” Tab

Option Meaning / Effect

S

Time-of-Day Synchronization Here, you decide whether the CP passes on time-of-day frames or not. You require this function if you have several CPs in a station since only one CP (on the same network) is permitted to forward the time synchronization messages.

Note

The time-of-day synchronization function does not exist for all module types.

S

Data transfer > 240 bytes With this option, you specify whether or not the CP will support jobs with a data length of more than 240 bytes (for S7-300 stations).

Notes

S

The transfer of more than 240 bytes of data is supported by newer version CPs. Please note the information in the product information bulletin / manual of the Ethernet CP.

Please note the information in Section 6.1 on the newer CP types.

S

Remember that with this configuration on an S7-300, one connection resource (free connection for S7 functions) of the

S7-300 CPU is used. CPU connection resources are also used, for example, by S7-300 CPs, in the FMS mode or by Pg. and Pos.

For more detailed information about the maximum connection resources, refer to /13/ and /7/.

58


Release 6/2003

C79000–G8976–C129–07


Table 2-1 Settings in the “Options” Tab , continued

Option Meaning / Effect

S

Replace Module without PG With this option, you can have the configuration data of the CP stored on the CPU. If you then replace CP, the configuration data for the new CP are downloaded automatically from the CPU when the CP is started up.

If you select this option, the configuration data are stored long-term on the CPU instead of in the EPROM of the CP. Remember, however, that long-term storage on the CPU is only safe from power outages if the CPU is protected by battery backup or by using an S7 Memory

Card.

S

Ethernet Profile for

Fault-Tolerant Connections

Note

If you store the configuration data on the CPU, please read the note below.

The following functions do not modify the configuration data on the

CPU:

S

Reset module memory

S

Resetting to factory settings

S

Assigning an IP address

1)

(using the target system selection in the SIMATIC Manager or the properties dialog in HW Config or

NetPro)

If you subsequently upload the configuration data from the CPU to a

PG you will always object the configuration data that were previously on the CP (with parameters, connections, IP address).

1) Note: You should only use the assign IP address function during commissioning; in other words, before downloading the configuration data.

Select this profile if you use fault-tolerant communication in your system. Fault-tolerant communication means that Industrial Ethernet is designed with redundancy and that you have configured fault-tolerant S7 connections.

If you select the Ethernet profile for fault-tolerant connections here, the time response of the S7 connections is adapted. As a result, breakdowns of a connection are detected more quickly and the failover to redundant connections is faster.

Note

Select the Ethernet profile for fault-tolerant connections only when you actually use fault-tolerant S7 connections. Otherwise you must expect your system to be more susceptible to problems since, for example, the number of transfer or connection establishment attempts is reduced compared with non-redundant systems.

S

Individual Network Settings Here, you can make fixed network settings, when necessary. As default, “Automatic Setting” is selected and this setting generally guarantees problem-free communication in most situations.

If problems occur in communication (for example, when connections are not established or when there are often disturbances on the network), the reason may be that the selected or automatic network settings are not suitable. You can then select a network setting to suit your network configuration.


Release 6/2003

C79000–G8976–C129–07

59


Table 2-1 Settings in the “Options” Tab , continued

Option

S

Send Keepalives for

Connections

Meaning / Effect

Here, you can set the interval at which keepalives are sent to the partner of a communications connection. This setting decides the latest time after which the failure of a communications partner is detected.

For all connection-oriented services, the Ethernet CP is configured so that keepalives are sent. This guarantees that connections are closed if a communications partner fails and that the connection resources are released. The setting made here applies to all TCP and ISO-on-TCP connections operated via the CP; a connection-oriented setting is not possible.

Possible values:

S

Multiplex OP Connections /

Reserve Internal CPU

Connection Resources

Turn keepalives off

Maximum value:

0 seconds

65535 seconds

Notes / Recommendations:

Remember that the keepalive mechanism can keep underlying connections established (for example, an ISDN telephone connection) although no user data are actually being transmitted. If this is not required, set the interval so high that the underlying connection is closed down when no further user data are sent before a keepalive is sent.

To attach TD/OPs or HMI devices, you can optimize the connection resources on the S7-300 CPU by having up to 16 of these devices communication on a single CPU connection resource (multiplex mode).

If you do not use this option, the number of operable TD/OPs or HMI devices depends on the number of available connection resources of the CPU you are using.

As default, this option is deactivated. This means that a CPU connection resource is used for multiplex only when necessary.

Configured S7 connections over the CP use the same multiplex channel as you use for multiplexing the HMI connections. If you configure S7 connections, this means that one CPU connection resource is already used.

Please note: PG connections do not use the multiplexer; if you use a

PG, one connection resource is always occupied.

Note on Programming:

When you use the multiplex mode, you must specify the rack/slot assignment of the CP for addressing on TD/OP/HMI connections instead of the rack/slot assignment of the CPU!

Applications (for example ProAgent) that require block-related messages (Alarm_S: SFC17-19) are not supported in the multiplex mode.

60


Release 6/2003

C79000–G8976–C129–07


Time-of-Day Synchronization Tab

In this tab, you can make the settings for one of the two synchronization modes explained below:

S

SIMATIC mode

If the CP receives MMS time-of-day frames, its local time is synchronized providing the NTP mode was not configured (MMS = Manufacturing Message

Specification).

The advantage of this mode is the accuracy that is generally higher than achieved with the NTP mode.

S

NTP mode (NTP: Network Time Protocol)

In the NTP mode, the CP sends time queries (in the client mode) at regular intervals to the NTP server in the subnet (LAN). Based on the replies from the server, the most reliable and most accurate time is calculated and the time of day on the station is synchronized.

The advantage of this mode is that the time of day can be synchronized beyond the boundaries of the subnet.

Diagnostics Tab

In the “Diagnostics” tab, you can startNCM S7 Diagnostics.

See Chapter 7 Diagnostics for a description of the diagnostic functions themselves.

Addressing Tab

In the “Addressing” tab, you can assign the previously configured IP address and

IP parameters to the CP.

This is necessary before the configuration data can be downloaded to the CP over

Ethernet.

For a detailed description, refer to Section 2.3.


Release 6/2003

C79000–G8976–C129–07

61


IP Access Protection Tab

Using IP access protection gives you the opportunity of restricting communication

V 5.2.1

over the CP of the local S7 station to partners with specific IP addresses. Partners you have not authorized cannot access data of the S7 station over the CP using the IP protocol.

In this tab, you can activate or deactivate IP access protection and can enter IP addresses in an IP access control list (IP-ACL).

As default, IP access protection is deactivated.

S

IP access protection for configured connections with specified partners

If you want to restrict access to the precise set of partners you specify during connection configuration, you simply need to activate access protection. In this case, you do not need to enter IP addresses in list.

Remember, however, on unspecified connections, all other IP addresses are unauthorized and are rejected.

IP access protection relates to all connection types handled using the IP protocol (TCP, ISO-on-TCP, UDP)

S

IP access protection for partners with specific IP addresses

To allow IP access for specific IP addresses, enter these IP addresses in the IP access control list.

The IP addresses you specify when you configure the connection always belong to the permitted IP addresses and do not, therefore, need to be entered explicitly in the IP-ACL.

62


Release 6/2003

C79000–G8976–C129–07


IP Configuration Tab

In this tab, you can decide the route and the method with which the IP address of the local S7 station is obtained and assigned.

V 5.2.1

With the options available here, it is also possible to assign IP addresses dynamically outside the STEP 7 configuration.

Table 2-2 Options in the “IP Configuration” Tab

Option

S

Set IP address in the

“Properties – Ethernet

Interface” dialog

S

Obtain an IP address from a

DHCP server


This option is the default.

It means that the IP address is set during the networking of the

Ethernet CP. The IP address of the CP is therefore fixed in the configuration.

You must select this option if you want to configure specified connections.

If you select this option, the IP address is obtained from a DHCP server when the S7 station starts up.

The DHCP server is informed of the MAC address of the CP or the client ID that you can enter here.

Requirement / Restriction:

If you select this option, it is initially not possible to create a fully specified connection in the STEP 7 project because the local IP address is not known.

You must therefore select “unspecified” with passive connection establishment as the connection type.

Please not the following:

If the connections are configured over the interface in the user program, you must use the option “Set IP address in the user program” as described below. This also applied if the IP address is obtained from a DHCP server.


Release 6/2003

C79000–G8976–C129–07

63


Table 2-2 Options in the “IP Configuration” Tab, continued

Option

S

Set IP address in the user program

S

Set IP address using a different method


With this option, you specify that the IP address is set over a user program interface (function block IP_CONFIG). This allows the IP address to be supplied dynamically during operation.

In this situation, communication connections are created only over the user program interface; configuring connections using STEP 7 is not possible (relates to connections over IP: TCP, ISO-on-TCP, UDP).

This setting does not preclude the IP address being obtained from a

DHCP server. It is possible for the user program to instruct the module to obtain an IP address in this way.

Further information:

Read the section “Programmed Communication Connections” and refer to the example in the appendix of the manual.

With this option, you specify that the IP address is set by other services outside STEP 7.

In this situation, configuring connections using STEP 7 is not possible

(relates to connections over IP: TCP, ISO-on-TCP, UDP).

Note

You can query the IP address actually being used with NCM S7 Diagnostics.

64


Release 6/2003

C79000–G8976–C129–07


2.2.5

“Substitute Objects” in the STEP 7 Project

Overview

Communication connections can be configured fully when the communications partners are available in the current project. For the stations on the Ethernet subnet, whose configuration data were not created in STEP 7 or whose configuration data are not managed in the currently active project, the following substitute objects can be created in the project:

S

SIMATIC S5 stations

S

PG/PC

S

Other stations

– for devices of other manufacturers

– for SIMATIC S7 stations in another project (not necessary in a multiproject)

Note

Instead of creating substitute objects, you can also configure unspecified connections for connections to the stations listed above.

In the Properties dialog of these connections, you must then specify the full partner address. These partners do not appear in the NetPro plant view.

Plant

“Production 1”

S7-400/1 S7-400/2

PC/PG

Plant

“Production 2”

S7-400/4

Non-Siemens device

Ethernet subnet (1)

S7-400/3

SIMATIC S5

S7-400/5


Release 6/2003

C79000–G8976–C129–07

65


Procedure

To enter a substitute object in the project, following the steps below:

1. Select the project in the SIMATIC Manager.

2. Select the menu command Insert " Station " and then as necessary

Other Station, PG/PC or SIMATIC S5.

Possible result: the selected object is created in the project.

Figure 2-5 Project With Substitute Objects Configured

Attaching Non-S7 Stations to the Subnet

The next step is to assign the substitute objects to the subnet, as follows:

1. Select the required object in the project and select Edit "

Object Properties.

2. In the Properties dialog box that is displayed select the “Interfaces” tab and click the “New” button (for example “Other Station”.

Result: The New Interface – Type Selection dialog box is displayed.

66


Release 6/2003

C79000–G8976–C129–07


Figure 2-6 Selecting the Subnet Type for “Other Station” (Example)

3. Select a subnet.

Result: The “Properties – Ethernet Interface” dialog is displayed. Here, you can select the subnet, connect the station to the network and set the address (MAC,

IP). All the SIMATIC stations in the project can establish communication relationships to this substitute object.

The addresses (MAP/IP) configured for the substitute object here must also be set on the station using the appropriate tool, for example COM 1430.


Release 6/2003

C79000–G8976–C129–07

67


2.2.6

Configuring Communication Services

Setting Up Connections

You must set up connections for the connection-oriented services supported by the

Industrial Ethernet CP, see also the Table in Section 1.2.

S

S7 connections see the STEP 7 user manual /6/

S

ISO transport connections see Section 4.4

S

ISO-on-TCP connections see Chapter 4.5.

S

TCP connections see Section 4.6

S

Connections for UDP see Section 4.7.

S

Interconnections for PROFInet communication see manual Component based Automation – configuring plants with SIMATIC iMap /23/

The information in the STEP 7 user manual /6/ in the chapter “Creating

Communication Connections Between Two Programmable Modules” also applies to the additional types of connection possible with the CPs.

You will find this information in the online help with integrated in STEP 7 by selecting Help " Contents. Select the topic “Configuring Connections and Data

Exchange.

68


Release 6/2003

C79000–G8976–C129–07


2.3

Assigning Addresses for the First Time (Applies to

Latest CPs)

Meaning of the Address Assignment – MAC Address and IP Address

The CP ships with a factory-set MAC address. Without further configuration, the device can only be accessed over the Ethernet port using this MAC address.

In its original state, you can already use the following functions via the CP using the ISO protocol and the factory-set MAC address:

S

Download the defined configuration to the CP or CPU

S

Run diagnostics on the CP or CPU

Before you can download defined configuration data to the device using an IP address, you must first assign an IP address to the CP.

Assigning the Address – Options and Recommendations

There are three ways of assigning this address in STEP 7:

S

Addressing by selecting the target system in the SIMATIC Manager

This option allows you to assign the address without having to set up a STEP 7 project. This is useful, for example, if you want to download defined configuration data you created offline to the S7 station.

This is described in Section 2.3.1.

S

Addressing using the properties dialog in HW Config or NetPro

This option assumes that the CP was networked in STEP 7. The advantage of this method is that the IP parameters set during configuration in STEP 7 /

NetPro can be used.

In the “Addressing” tab, you assign the previously configured IP address and IP parameters to the CP.

This is necessary before the configuration data can be downloaded to the CP over Ethernet.

This is described in Section 2.3.2.

S

Downloading configuration data using the ISO protocol

Another option is to download configuration data with a defined IP address using the ISO protocol (see above).


Release 6/2003

C79000–G8976–C129–07

69


Requirements

Before you can use the addressing described here, the CP must be obtainable online, which means:

S

An attachment to the Ethernet LAN must already exist; there must be no routers between subnets in the path.

S

The Ethernet port of your PG/PC must be accessible to STEP 7.

Notice

The options for assigning an address as described here are available only if you have a module that can be reached using the default MAC address; such modules must support the PST (Primary Setup Tool) function. Please refer to the information in the relevant manual /1/.

2.3.1

Addressing by Selecting the Target System in the SIMATIC

Manager

Follow the steps below to assign the IP address the first time:

1. Open the SIMATIC Manager

2. Select the menu command PLC " Assign Ethernet Address.

70


Release 6/2003

C79000–G8976–C129–07


3. Start a network search for available modules by selecting the “Browse...” button.

4. Select the CP with the matching MAC address from the components listed.

5. Enter the required IP parameters and assign them to the CP.

Result:

The CP is now accessible on Industrial Ethernet using the IP address.

Note

You will find further detailed information on this procedure in the STEP 7 online help.


Release 6/2003

C79000–G8976–C129–07

71


Alternative Procedure

You can also follow the steps outlined below in the SIMATIC Manager:

1. Use the menu command PLC " Display Accessible Nodes to display the nodes that you can access over Industrial Ethernet.

2. Select the required node in the list displayed.

3. Then select the menu command PLC " Ethernet Address.

Result: The previously selected node is entered directly into the “Addressing” dialog. You cannot modify the MAC address of the node.

4. Enter the required IP parameters and assign them to the CP (see above under

STEP 5.).

Result:


72


Release 6/2003

C79000–G8976–C129–07


2.3.2

Addressing using the Properties Dialog in HW Config or NetPro

Follow the steps below to assign the IP address the first time:

1. Open the SIMATIC Manager.

2. Define the configuration of your S7 station with the appropriate components in

HW Config in an existing or newly created project.

3. When you create the CP, network it with an Industrial Ethernet subnet.

When you create the CP in HW Config, the necessary dialog is displayed in which you can network the device and assign the IP address.

4. Select the “Addressing” tab in the properties dialog of the CP you want to address.

The tab displayed is identical to the dialogs illustrated in Section 2.3.1.

5. Start a network search for available modules by selecting the “Browse...” button.

6. Select the CP with the matching MAC address from the components listed.

7. Assign the IP parameters taken from the networking to the CP by clicking the relevant button.

Result:


Note

You will find further detailed information on this procedure in the STEP 7 online help.


Release 6/2003

C79000–G8976–C129–07

73


2.4

Downloading the Configuration Data to the Target

System

Principle

The configuration data of the Ethernet CP are downloaded from the hardware configuration. All the configuration data of the S7 station are downloaded including the central configuration, all relevant DP master systems and all parameter settings.

The data of the configured connections must also be downloaded, see below.

Type of Interface

You can download the configuration data to the S7 station on the following paths

(interfaces):

S

MPI interface

You can use this interface to download configuration data or when assigning a

MAC/IP address for the first time (node initialization – for details, refer to the manual /1/ “Assigning Addresses for the First Time”).

S

Industrial Ethernet

Here, you use the PG mode of the Ethernet CP in the S7 station (see also

Section 1.3).

Depending on the PG/PC interface used by the station on which you create your configuration, you can download the defined configuration data to the S7 station over the TCP/IP interface or over the ISO interface of STEP 7.

– When you download over the IP interface, the CP must already have been assigned an IP address; refer to Chapter 2.3.

– When you download over the ISO interface, you can use the preset MAC address. However, please note the following:

Note

If you want to download the configuration data over the ISO interface to a CP with an unchanged, factory-set MAC address and you have configured a different MAC address in your STEP 7 project, you must start the download in NetPro or HW

Config; this is the only way you will be prompted to enter the current MAC address. The SIMATIC Manager, on the other hand, aborts the download if the target station cannot be reached.

74


Release 6/2003

C79000–G8976–C129–07


Procedure

F1

To download the configuration data to the S7 station, follow the steps outlined below:

1. Open the “Set PG/PC Interface” dialog box in the Windows Control Panel.

2. Set the PG/PC interface according to the CPs available on your PG and according to the bus attachment (interface parameter assignment used).

For more detailed information, refer to the integrated help system.

3. Change the CPU to the STOP mode (regardless of the type of interface – see above).

4. Select the menu command PLC "

Download to Module.

STEP 7 then guides you through dialog boxes. Note the additional information in the “STEP 7 User Manual”, Chapter “Configuring and Assigning Parameters to

Modules” /6/.

Deactivating the MAC Address in the Configuration

If you deactivate the use of the MAC address when you are configuring the CP, the

CP can be reached via the preset MAC address, however you cannot define any

ISO transport connections or S7 connections over ISO connections in your configuration.

Saving the Configuration Data in Non-Volatile Memory

You can download the configuration data step-by-step or all at once. If you download step-by-step, you will be prompted to start the download function separately for each module. You must select this method if you want to save the configuration data in non-volatile memory on the Ethernet CP. In this case, select the “Copy to ROM” button in the “Download” dialog for the CP.

Downloading the Configured Connections

To download configured connections, you use a corresponding download function in the connection configuration (NetPro).

Notice

If you have assigned a new address to the Ethernet CP or have configured connections, you must always download the connection configuration again.

Remember that you also make suitable address adaptations for the other stations or “substitute objects”.


Release 6/2003

C79000–G8976–C129–07

75


Relocating the CP in the Hardware Configuration

If you are using communication services with configured connections, the connection IDs also identify the slot of the CP. If you “drag” a CP you have already configured to a different slot, note the following:

Notice

If you drag the CP to a different slot, the data of the connection configuration are automatically updated. The data of the connection configuration must, however, be downloaded again!

-

76


Release 6/2003

C79000–G8976–C129–07

SEND/RECEIVE Interface in the User

Program

3


S

How to send and receive data.

S

Which data areas can be used on the S7 CPU.

S

How to program the SEND/RECEIVE interface in the user program.


S

For programming and configuring nodes for connections (for example a

SIMATIC S5 PLC with the CP 1430 TCP, PC with CP 1613), please refer to the appropriate manuals.

S

The FCs for programming connections are described in Section 6.3.

S

Configuring the Ethernet CP with NCM S7 is described in Chapter 4.

S

Programming communication connections over the interface in the user program is described in Chapter 5.

Sample programs:

Sample configurations and programs are available for the SEND/RECEIVE interface described here:

S

In the sample project PROJECT_ETHERNET that you can start immediately after installing NCM S7; for a description, refer to the Primer /2/.

S

On the Internet as downloadable sample projects; refer to the information in

Appendix C “Support and Training”.


You can order this directly over the Internet at: http://www4.ad.siemens.de/view/cs/de/574211


Release 6/2003

C79000–G8976–C129–07

77

SEND/RECEIVE Interface in the User Program

3.1

How the SEND/RECEIVE Interface Works on the CPU

Functions (FCs)

The following functions (FCs) are available for handling communication on connections:

S

AG_SEND/AG_LSEND

This block takes the user data from the specified user data area and transfers it to the Ethernet CP.

S

AG_RECV/AG_LRECV

This block transfers received user data to the user data area specified in the call.

The diagram below illustrates the situation. Using the FCs AG_SEND/AG_LSEND and AG_RECV/AG_LRECV, the user program instructs the Ethernet CP to send or receive data on the configured connection.

CPU

Ethernet station SIMATIC S7

Ethernet CP

STEP 7 user program

CP database

User data buffer

User data areas

AG_SEND

AG_RECV send receive

Communication connection

Figure 3-1 Interaction of the CPU and Ethernet CP on Connections

Amounts of Data

The Ethernet CP can transfer the amounts of data shown in the table below per job on one connection:

Table 3-1

Sending

Receiving

ISO Transport

8192 bytes

8192 bytes

ISO-on-TCP

8192 bytes

8192 bytes

TCP

8192 bytes

8192 bytes

UDP

2048 bytes

2048 bytes

78


Release 6/2003

C79000–G8976–C129–07


3.2

Programming the SEND/RECEIVE Interface

Principle of Job and Data Transfer

The user program triggers the transfer of the user data areas with FC calls and monitors the transfer by evaluating the return codes of the FCs.

The following parameters are transferred when the FCs are called:

S

The number of the connection (ID)

S

The location of the user data area in the CPU

For detailed information about the call interface see Chapter 6.

Purpose of the FCs

Calling the function blocks has the following effects:

S

The user data area is transferred to the Ethernet CP or received from the

Ethernet CP.

S

The execution of the job is confirmed positively or negatively in a status message.

Procedure

Program the SEND/RECEIVE interface in the user program as follows:

1. Use the following functions (FCs) for data transmission on connections:

– AG_SEND / AG_LSEND for transferring the user data area to the Ethernet

CP

– AG_RECV / AG_LRECV for entering data received from the Ethernet CP in the user data area

2. Evaluate the following bits in the FCs:

– for AG_SEND / AG_LSEND the parameters DONE, ERROR, STATUS

– for AG_RECV / AG_LRECV the parameters NDR, ERROR, STATUS

Notice

Connection numbers (IDs) must be taken from the configuration when programming.

To ensure correct parameter settings for the block calls, The LAD/STL/FBD editor in STEP 7 provides you with the option of accepting all the relevant parameters from the hardware configuration (HW Config) and from the connection configuration. For more information, refer to Section 6.2


Release 6/2003

C79000–G8976–C129–07

79


Calling FCs in the CPU Program

One possible sequence for FCs in conjunction with the organization and program blocks in the CPU cycle is illustrated in the following diagram.

Read PII

OB

Read in the received data of the connection

User program

AG_RECV


ÇÇÇÇÇÇÇÇ

AG_RECV

ÇÇÇÇÇÇÇÇ

AG_SEND

ÇÇÇÇÇÇÇ

Communication

ÇÇÇÇÇÇÇ connection

ÇÇÇÇÇÇÇ

ÇÇÇÇÇÇÇ

ÍÍÍÍÍÍÍÍ

AG_RECV

ÍÍÍÍÍÍÍÍ

ÍÍÍÍÍÍÍÍÍ

ÍÍÍÍÍÍÍ connection

ÍÍÍÍÍÍÍ

ÍÍÍÍÍÍÍ

ÍÍÍÍÍÍÍ

Transfer send data for the connection

ÇÇÇÇÇÇÇÇÇ

AG_SEND

ÇÇÇÇÇÇÇÇÇ

ÇÇÇÇÇÇÇÇÇ

Write PIQ

Legend:

Sequence of the CPU cycle

ÍÍ ÇÇ

ÍÍ ÇÇ

The different shading shows which connections and FC blocks belong together.

Figure 3-2 Typical Sequence of Function Calls in the CPU Cycle

The following points are illustrated by the diagram:

S

The user program consisting of any number of blocks (OBs, FBs or FCs –> see also /6/ accesses several connections (Figure 3-2 illustrates three connections).

S

At various points (event and program-controlled) the user program sends data

80


Release 6/2003

C79000–G8976–C129–07


on a connection using the AG_SEND call.

S

At various points in the CPU cycle, the user program accepts the data received on the connection using an AG_RECV call.

Note

The blocks can also be called more than once in a cycle for the same communication connection.


Release 6/2003

C79000–G8976–C129–07

81


3.3

Data Exchange S7 CPU <–> Ethernet CP

The Ethernet CP processes the send and receive jobs independent of the CPU cycle and requires one transmission time. The interface to the user program with the FCs is synchronized by an acknowledgment. Two situations must be distinguished:

S

The CPU cycle is faster than the transmission time.

S

The CPU cycle is slower than the transmission time.

Note

Please refer to the sequence charts for the FCs in Chapter 6. These charts show how to handle the SEND/RECEIVE interface in the user program for problem-free data exchange.

Remember the points below about the CPU cycle and transmission time.

FC Calls Faster than the Transmission Time

If a block is called again in the user program before data were transferred or received, the procedure is as follows on the interface of the FCs:

S

AG_SEND/AG_LSEND:

No further job is accepted until the transmission of the data on the connection has been acknowledged by the Ethernet station. During this time, the user program receives the message “job active” until the Ethernet CP can accept the next job on the same connection.

S

AG_RECV/AG_LRECV:

The job is acknowledged with the message “no data available yet” if there are no received data on the Ethernet CP. The user program receives this message in the CPU cycle until the Ethernet CP has received data again on the connection.

82


Release 6/2003

C79000–G8976–C129–07


FC Calls Slower than the Transmission Time

If a block is called again before the data were completely transferred or received, the procedure is as follows on the interface of the FC blocks:

S

AG_SEND/AG_LSEND:

The job is positively acknowledged. The Ethernet CP is ready to receive a new send job (at the earliest however with the next call).

S

AG_RECV/AG_LRECV:

The job is acknowledged with “New Data Received” when the data have been transferred to the user program. Following this, the FC call can be repeated.

Notice

Remember that resource shortages can occur if the processing speeds on the sender and receiver are not the same (sender faster than receiver).

The sender receives a message from the FCs if problems occur (“No resources on the destination station”).


Release 6/2003

C79000–G8976–C129–07

83


3.4

Additional Information

3.4.1

Programming Data Transfer on TCP Connections

Purpose of TCP Connections

TCP connections should be used above all for connections to systems of a different type if they do not support RFC1006.

For communication between devices of the SIMATIC family, you should use the more convenient ISO-on-TCP connections! The following sections explain certain special points to note.

Special Features

S

Block types (FC calls)

Use only the following functions (FCs) for data transmission:

– With the S7-CPs for S7-400, you must use FCs AG_LSEND (FC 50) and

AG_LRECV (FC 60) on TCP connections!

– With the latest S7-CPs for S7-300, you also use FCs AG_SEND (FC 5) and

AG_RECV (FC 6) for TCP connections.

S

Frame length

On the TCP connections, the protocol contains no information about the end of a message and start of a new message.

The receiving station must therefore know how many bytes belong to a message and transfer an ANY pointer corresponding exactly to this length when

FC AG_LRECV is called. (Example: if 100 bytes of data are always transferred, the ANY pointer could appear as: P#DB100.DBX 0.0 Byte 100)

If you want to receive data with a variable length, follow the steps below:

Include information on the length of the user data in the frame before the actual user data. Initially, you should only evaluate the length information on the receiving station. Fetch the appropriate length of user data in another receive job by specifying an ANY pointer of the required length on the FC interface for fetching the actual user data.

84


Release 6/2003

C79000–G8976–C129–07


3.4.2

Recommendations for Use with a High Communications Load

Overview

The points below will help you to avoid overload situations on your CPU when using the Ethernet CPs.

In particular when you replace an older CP with a newer CP and are then confronted with overload problems, you should check your application for the pitfalls outlined below.

Known Problems

S

The functions for sending and receiving (FC5/FC6 or FC50/60) are often called cyclically in OB1. This leads to constant communication between the CPU and

CP. As a result, other types of communication such as PG functions cannot be executed or only very slowly.

S

HMI systems access data of the CPU too often using S7 functions. This slows down communication generally and there may be a lack of resources when

SEND/RECEIVE FCs are called cyclically in OB1.

Remedy

The recommendations below will help to avoid these situations:

S

Do not call communication blocks cyclically in OB1!

Communication should be called time-controlled in a suitable cyclic-interrupt

OB. The call interval of this OB should be significantly higher than the average cycle time of your program.

S

You should set a minimum cycle time that is higher than the average runtime of

OB1. This frees resources for communication on the CPU. This is, for example, a remedy for existing applications when communication already takes place cyclically in OB1.

S

If necessary, reduce the time taken for communication processing on the CPU by changing the parameters set for “cyclic load due to communication” in the properties dialog of the CPU.


Release 6/2003

C79000–G8976–C129–07

85


-

86


Release 6/2003

C79000–G8976–C129–07

Configuring Communication Connections

4


S

The general aspects of configuring communication connections

S

How to configure ISO transport connections, ISO-on-TCP and TCP connections

S

How to use the connection configuration functions to specify communication partners that exchange data via UDP

You will find a description of the connection-specific properties dialogs in the following sections:

S

ISO transport connections see Section 4.4

S

ISO-on-TCP connections see Section 4.5

S

TCP connections see Section 4.6

S

UDP see Section 4.7


S

For the properties of the configurable connection types, refer to Section 1.5

S

There are situations in which communication connections are not set up over the configuration interface of STEP 7 but program-controlled by certain applications; see also Chapter 5.

S

For the properties of the configurable connection type E-mail, refer to /5/.

S

You will find information on the numbers of connections and amounts of data in

Section 3.1.

S

For information on configuring connections, refer to the online help of STEP 7 by selecting Help "

Contents.


Release 6/2003

C79000–G8976–C129–07

87

Configuring Communication Connections

4.1

Procedure

Initial Situation

The steps described here assume the following:

1. You have created the local S7 station and the required partner stations in your

STEP 7 projects (refer to the description in Chapter 2).

2. You have clarified the other station types with which connections must be established. You create substitute objects for these station types in your

STEP 7 projects.

Setting up Connections and Using Them in the User Program

The following steps are necessary to operate connections on the SIMATIC S7 PLC with the Ethernet CP:

Configuring

Create new connections.

(see Section 4.3.1)

Programming

Program the SEND/RECEIVE interface in the user program.

(Refer to Section 3.2 and the detailed

FC description in Chapter 6).

Configure connection properties.

(see Sections 4.4 to 4.4)

Download connection configurations and user programs to the S7 station.

Legend: necessary steps optional steps

88


Release 6/2003

C79000–G8976–C129–07


4.2

Possible Connection Configurations

Communication connections are possible between the communication partners shown in the diagram below.

The communication partners can be in the same project or distributed in the subprojects of a multiproject.

Connections to communication partners outside a project are configured using the

STEP 7 object “Partner other project” or using substitute objects such as ”Other stations” or SIMATIC S5.

S7 – 400

Ethernet CP

Ethernet CP

S7 – 300

Ethernet CP

S7 – 400

Ethernet /IT-CP

Subnet 1

PG/PC with Ethernet CP

Subnet 2

S7 – 400

Ethernet CP

SIMATIC S5

Ethernet CP

WAN*

LAN * only TCP/IP

Other station with

Ethernet attachment

Figure 4-1 Possible Connections


Release 6/2003

C79000–G8976–C129–07

89



If interproject subnets are configured, you can also configure connections over such subnets using STEP 7 V5.2. The endpoints of these connections can be located in different projects.

STEP 7 supports you both when creating interproject connections within a multiproject as well as when synchronizing connections that were configured without a multiproject context.

90


Release 6/2003

C79000–G8976–C129–07


4.3

Connections

Characteristics of a Connection

A communication connection allows program-controlled communication between two nodes on Industrial Ethernet with the following characteristics:

S

The data transfer is bi-directional, in other words, it is possible to transmit and receive on the connection simultaneously.

S

Both stations have the same rights, in other words, each station can trigger the send and receive procedures in response to events.

S

The address of the communication partner is specified in the configuration.

Exceptions to this are:

– free UDP connections

Here, the address is specified at the FC interface in the user program.

– programmed communication connections (see Chapter 5)

SIMATIC S7 station Ethernet node send receive

Communication connection receive send send receive


Ethernet node receive send

Figure 4-2 Sending and Receiving via one Communication Connection

Note

The term “connection” is also used here for UDP. Reason: During configuration

(just as in TCP) the communication partners are assigned to each other and therefore logically “connected”. In actual fact, with UDP there is no explicit connection establishment between communication partners.


Release 6/2003

C79000–G8976–C129–07

91


Amounts of Data

Refer to the manual /1/ supplied with the Ethernet CP for the number of communication connections supported by the Ethernet CP. The number of connections per station can be increased by adding more CPs.

The Ethernet CP can transfer the amounts of data shown in the table below per job on one connection:

Table 4-1

Sending

Receiving

ISO Transport

8192 bytes

8192 bytes

ISO-on-TCP

8192 bytes

8192 bytes

TCP

8192 bytes

8192 bytes

UDP

2048 bytes

2048 bytes

Notice

The transfer of more than 240 bytes of data is supported by newer version CPs.

Please note the information in Section 6 and in the manual of the Ethernet CP.

Tasks of the Ethernet CP

When handling the data transfer on a connection, the Ethernet CP has the following tasks:

S

When receiving

Receiving data from Ethernet and transferring it to the user data area on the

CPU.

S

When sending

Taking data from the user data area on the CPU and sending the data via

Ethernet.

The connection is established automatically as soon as the partner is obtainable.

For a free UDP connection, the following functions are also necessary in addition to those above:

S

When receiving

Entry of the sender of the message in the job header.

S

When sending

Evaluation of the job header and addressing the partner

92


Release 6/2003

C79000–G8976–C129–07


Requirements for Configuring Connections

The Ethernet CP was entered in the hardware configuration and connected to the subnet.

As a bus node, the Ethernet CP has an address.

Notice

All stations not in the STEP 7 project must be configured with substitute objects

(for example as “SIMATIC S5” or “Other stations”).

or

Use the “unspecified” partner type when you create the connection.


Release 6/2003

C79000–G8976–C129–07

93


4.3.1

New Connection

Principle

When you create new connections, you start from entered and networked stations.

A connection is then configured starting from a station or CPU in the current S7 project and then selecting a destination station.

Due to the networking, the node addresses (MAC or IP addresses) of the two stations are already decided. The local/remote TSAPs (Transport Service Access

Point) or ports at both ends of the connection are automatically assigned default values.

If the partner station is a station outside the current project or a non-S7 station, the remote TSAPs (Transport Service Access Point) or ports must be specified in the

Properties dialog of the connection.

The endpoint of the connection to a SIMATIC S7 station is always a CPU. A separate connection table is created for each CPU and displays the connection partner and types of connections.

Creating a New Connection

To configure a new connection, the stations and their CPs must be configured and networked in the S7 project. To create a new connection, follow the steps below:

In NetPro, follow the steps below:

1. In NetPro, select the station or the CPU in the station from which you want to establish the connection.

2. Select the menu command Insert " New Connections (also available with the right mouse button!)

Result: The following dialog appears on the screen.

94


Release 6/2003

C79000–G8976–C129–07


Figure 4-3 Layout of the “New Connection” Dialog (Example of an ISO Transport Connection)

3. Select the partner station to which you want to establish a connection (if several

CPUs exist, please select the required CPU).

4. Select the connection type you want to use (for example ISO transport connection) in the “Type” box

When you confirm your input with Apply, the new connection is created and the

”New Connection” dialog box remains open. This allows you to create further connections without needing to reopen the dialog box. The connection table is updated at the same time.

When you click OK, the connection is entered in the list, the dialog is terminated and the display in the main dialog is updated.

If you click Cancel, the dialog is terminated and the connection is not entered in the list.


Release 6/2003

C79000–G8976–C129–07

95


Handling Connections in a Multiproject

Interproject connections to a specified partner (for example, a CPU) are created in the same way as connections within a project (identical procedure). The dialog for selecting the connection partner has been extended and allows you not only to select the endpoint (module) but also the project within a multiproject to which the endpoint belongs.

The consistency of interproject connections is retained when you work with the projects of the multiproject:

S

Interproject connections within a multiproject are implicitly broken when a project is taken out of the multiproject for distributed editing and the connection partner is located in the removed project.

S

When the removed project is returned to the multiproject, STEP 7 automatically merges the broken connections consistently.

Connections to Non-S7 Stations using Substitute Objects

If you want to configure connections to devices or stations that are not S7 stations, select a station of the type “SIMATIC S5”, “PC/PG” or “Other Station” as the destination station.

By creating these stations in NetPro and networking them, you have already specified the node addresses (MAC or IP addresses) of the two stations. You must specify the TSAP (Transport Service Access Point) for the destination station.

Notice

Connections to non-S7 stations (for example SIMATIC S5) are generated as incompletely specified connections; in other words, the remote TSAP or port is empty. These connections must be specified in the Properties dialog.

4.3.2

Connections to Partners in Other Projects

There are various ways of creating connections to partners configured in other

STEP 7 projects or with other tools outside the current STEP 7 project:

S

Connections using substitute objects such as “SIMATIC S5”, “PC/PG” ,

“SIMATIC PC Station” or “Other Station”.

This method is described in the section above.

S

Unspecified connections

S

STEP 7 object ”Partner in other project” (multiproject)

With this method, a connection is reserved in both subprojects that can be synchronized later by the system when the partner project is included in the multiproject.

96


Release 6/2003

C79000–G8976–C129–07


In both projects, the same connection name must be configured in the properties of the connection. The connection name is used as a textual reference when the projects are merged. Based on the connection name it is possible to assign the connection partner and synchronize the connection properties.

Before the projects are merged, such connections are ”unspecified connections” in terms of addressing; in other words, the partner addresses remain empty.

Unspecified Connections

Connections to an as yet unknown device (for example a diagnostic unit) are configured as “unspecified” connections. They can be specified later in the

Properties dialog.

You can create an unspecified connection simply by selecting station “unspecified” for the connection partner when you create the connection. The unspecified connection can be used in three ways (explained below based on the example of an ISO-on-TCP connection (ISO transport and TCP connections are analogous):

S

Declare readiness for communication – passive connection establishment

The connection establishment is then set to passive (see settings in the

General tab).

The address setting for the ISO-on-TCP connection is then as follows:

The remote IP address and the remote TSAP are empty, in other words, they are not relevant for the CP. When the connection is established, any partner is accepted (partner = connection name that addresses the CP with the correct IP address and TSAP).

It is also possible to use a partial specification; in other words, communication is permitted with any partner that matches the specified TSAP.

S

Connection to a specific station in any project

The address setting for the ISO-on-TCP connection is then as follows:

You can specify the remote IP address and the port of any destination station.

The destination station can be in the current STEP 7 project or in another project.

V 5.2.1

Use this method if you have not created a substitute object for the partner station, for example SIMATIC S5, in the current project.

S

IP Address Assignment over DHCP

If you select the option to obtain the IP address from a DHCP server, it is initially not possible to create a fully specified connection in the STEP 7 project because the local IP address is not known. You must therefore select

”unspecified” with passive connection establishment as the connection type.


Release 6/2003

C79000–G8976–C129–07

97


The following table lists the possible options.

Table 4-2

Meaning for Connection

Establishment

by any partner by any partner via specific TSAP to or by a specific partner

IP Address /

MAC Address

empty empty specified

TSAP / Port

empty specified specified

Possible Connection

Establishment

passive passive active / passive

The free UDP connection is another variant. With this type of connection, the address of the connection partner is left open during configuration. The communication nodes are identified by address information in the communication job in the user program.

For further information, refer to the sections dealing with specific connections.

Notice

The number of connections possible per Ethernet CP can be found in the manual

/1/supplied with the CP. If several CPs are installed in one station, the next CP is automatically selected if the limit is exceeded. The connections can be routed in the Properties dialog of the connection.

98


Release 6/2003

C79000–G8976–C129–07


4.3.3

Further Functions

Toolbar

In the toolbar of the connection configuration dialog the following functions are available:

Save

To save the configured connection, select the Save function or click the save button.

Print

Change Connection

Partners

Insert Connection

You can print the entire connection table or individual sections of it by selecting the Print function or clicking the print button.

The following print options are available:

S

Overview of all connections (complete connection table)

S

Overview of the selected connections (selected area)

S

Detailed printout of all connections (details of all connections)

S

Detailed printout of the selected connections (details of the selected area)

You assign a new partner station to the selected connection.

Important!

Remember that this also changes the partner ID on connections of the

SEND/RECEIVE interface. You may need to adapt your user program.

You create a new entry in the connection table.

Download

Help

You download the connection table to the PLC. For more detailed information call up the integrated help function.

If you require help or more information, select the Help function or click the help button.

The help button provides you with context-related help. Using the help function you call a help dialog familiar from other Windows applications.

Print Function in the “Overview” Tab

An additional function for printing the configured connections and configuration status is available in the “Overview” tab of the properties dialog of the connection.


Release 6/2003

C79000–G8976–C129–07

99


4.3.4

Connections Without Assignment

Overview

This section explains the actions that can lead to a configured connection losing its assignment to the CP or being deleted.

Caution

Remember that in contrast to the S7 connections, the connections of the

SEND/RECEIVE interface are assigned a CP-dependent ID. The actions below may require the ID to be modified so that the interface information in the user program must also be adapted.

Notice

If you replace one CP with another, this must provide at least the same services and have at least the same version. This is the only way to ensure that the connections configured over the CP remain consistent and can be used.

Table 4-3 Actions That Can Cause Changes to Configured Connections

Action

The CP (module) is moved to a different location in the hardware configuration (drag and drop)

The CP (module) is deleted in the hardware configuration.

You receive the message

“CP has n connections; the assignment will be lost in the connection table”.

Consequences for the

Connections

The connections are retained.

The connection IDs are automatically updated.

The connections remain without

assignment to a CP in the connection table. In the

“Overview” tab of the Properties dialog, the connections are identified with “!”.

Deleting the SIMATIC S7 station.

How to Establish the Connection

Again

1. Adapt the module start address

LADDR in the user program.

2. Download the connection configuration to the CP again.

Once you have placed a CP in the hardware configuration and networked it:

1. Assign the CP in the connection properties dialog in the “Addresses” tab.

or

Reassign the connection using the menu option Edit

"

Connection

Partner....

2. Adapt the connection ID in the user program.

3. Download the connection configuration to the CP again.

Reconfigure the station and connections.

All the connections to this station are deleted within the project.

Note:

The does not apply to connections to a partner that uses a router.

100


Release 6/2003

C79000–G8976–C129–07


Table 4-3 Actions That Can Cause Changes to Configured Connections, continued

Action Consequences for the

Connections

Deleting a remote station.

The connections of the stations in the project to remote stations remain without assignment in the connection table. In the


Changing the subnet assignment of the CP.

The connections that were assigned via the CP remain without an assignment in the connection table. In the


Note:

The does not apply to connections if a router is used.

How to Establish the Connection

Again

Reassign a remote station (or even a local station) using the menu option Edit

"

Connection Partner....

Reassign the connections using the menu option Edit

"

Connection

Partner... or in the “Addresses” tab of the properties dialog for the connection.


Release 6/2003

C79000–G8976–C129–07

101


Display (Example)

The status of connections is displayed in the “Properties ISO Transport

Connection” dialog in the “Overview” tab.

Figure 4-4 Status of the Connections in the “Overview” Tab (Example of ISO Transport Connections)

102


Release 6/2003

C79000–G8976–C129–07


4.4

Configuring ISO Transport Connections

Introduction

When you create a connection in the New dialog, you specify the connection type and, as far as possible, the connection partner.

When necessary, you can adapt other connection partners that are set as default when you create a new connection as described below.

Opening the Dialog

To call the dialog for special connection properties, follow the steps outlined below:

1. Select the required connection in the connection table.

2. Select the menu option Edit " Object Properties

Result: The “Properties ISO Transport Connection” dialog appears.

Tabs

The following tabs are available for ISO transport connections:

S

General

Displays parameters that identify the connection.

S

Addresses

Displays the local and remote address information.

S

Dynamics

Displays the relevant timers and counters.

S

Options

Here, you can decide whether or not you want to use the connection for one of the access types FETCH or WRITE.

S

Overview

This is an overview of all the configured ISO transport connections of the selected station with their parameters and the status of the connection.

S

Status Information

This tab displays the current status information for the connection (valid at the time the dialog is opened). This information corresponds to the NCM

Diagnostics display and is only available when the station can be reached online.


Release 6/2003

C79000–G8976–C129–07

103


4.4.1

Specifying the Local Connection Endpoint

General Tab

This tab of the Properties dialog displays general connection parameters that identify the local connection endpoint.

Figure 4-5 Layout of the Properties Dialog for the “General” Tab (ISO Transport Connections)

104


Release 6/2003

C79000–G8976–C129–07


Attributes

Local Endpoint

ID

Description Access

Name

Via CP

Active Connection

Establishment

The entry is identical to the Local ID parameter in the connection table.

When you create the connection, a name is proposed here for the connection endpoint along with a connection number as suffix.

With unspecified connections, use this box to identify the partner.

If the station contains more than one CP of the same type connected to the same subnet, you can select the connection route. –> “Route” button see Section 4.9.

If no CP is assigned (for example because the CP was previously deleted) “none” is displayed here.

Selectable

Modifiable

Display only

With this option, you specify whether the connection is established by this S7 station. This is the default setting when the address of the partner is specified.

ON: the connection is established actively.

OFF: the connection is established by the partner.

If you selected partner “unspecified” when you created the connection, the option is deselected as default. If you activate the option, you must also specify the address of the partner in the

“Addresses” tab.

Note:

Please note the effects on the mode. If you want to use the FETCH or WRITE mode (refer to the ”Options” tab), the mode must be set to

”Passive” for the S7 station.

Modifiable

Block Parameters

ID

LADDR

This value must be entered as a block call parameter ID for calling the FC in the user program to identify the connection. The ID changes if the local ID is changed.

This value must be entered as a block call parameter ID for calling the FC in the user program to identify the connection.

Display only

Display only

Connection Name (Reference) – Only in Multiproject

If you create a connection to a partner in another project that has not yet been merged with the current multiproject, you must specify a connection name as a reference (not to be confused with the name of the connection endpoint described above). Interproject connections can then be joined up based on this reference. As soon as the connections have been joined, the connection name (reference) is no longer relevant and is no longer displayed.


Release 6/2003

C79000–G8976–C129–07

105


4.4.2

Specifying ISO Transport Addresses

Address Parameters

An ISO transport connection is specified by the local and remote connection endpoint.

S

Local addresses:

Local MAC address and local TSAP

(Transport Service Access Point)

S

Remote addresses:

Remote MAC address and remote TSAP

Ethernet station A Ethernet station B

Remote

TSAP

Local

TSAP

MAC address A

ISO transport connection

Figure 4-6 Sending and Receiving on One ISO Transport Connection

Local

TSAP

Remote

TSAP

MAC address B

Notice

The TSAPs of an ISO transport connection must match as follows:

Remote TSAP (on Ethernet CP) = local TSAP (in destination station);

Local TSAP (on Ethernet CP) = remote TSAP (in destination station);

106


Release 6/2003

C79000–G8976–C129–07


Addresses Tab

The addresses tab displays proposed values for the relevant local and remote address information. When connecting to non-S7 stations, you can set the TSAP addresses individually.

Figure 4-7 Layout of the “Addresses” Tab of the Properties Dialog with Default TSAPs

TSAP Format

ISO transport connections have a TSAP length of 1 to 16 bytes. When you are entering values, the current length is displayed automatically (visible display: 16

ASCII characters). Local and remote TSAPs can be input as hexadecimal values or as ASCII strings. If you make your entries in ASCII, the characters you enter are also displayed in hexadecimal format. If you make your entries in hexadecimal, printable characters are displayed in ASCII (8 hexadecimal values are visible). If you enter nonprintable characters, the ASCII display is gray (no further ASCII entries possible) and the nonprintable characters are displayed as periods.

Local and Remote TSAPs

Remote and local TSAPs can be identical since the connection is uniquely identified by the different MAC addresses. If you require more than one connection between two stations, the TSAPs must also be different.


Release 6/2003

C79000–G8976–C129–07

107


Default TSAPs

When configuring the local and remote TSAPs, there is a default value “ISO-1” for the first connection between the two partners (can be changed). For a new connection between the two partners, the default value “ISO-2” is proposed. With a new connection to a new partner, the value ISO-1 is used again.

Addresses Tab – Unspecified ISO transport connection

If you select the partner type as “unspecified”, depending on your task, you can enter address information about the communication partner here. The options available to you are explained in detail in Section 4.3.1.

The Addresses tab shown here illustrates the situation in which the MAC address and the remote TSAP were not specified. If you do not make any further settings, this means that you are willing to accept a connection establishment request from any communication partner.

Figure 4-8 Layout of the “Addresses” Tab of the Properties Dialog for an Unspecified Connection

108


Release 6/2003

C79000–G8976–C129–07


4.4.3

Specifying ISO Transport Dynamic Properties

Dynamics Tab

The Dynamics tab displays the relevant timers and counters of this connection.

You can normally accept these default values.

If necessary, for example with connections to non-Simatic systems, you can set the timers and counters individually and influence the dynamic response of the connection.

Figure 4-9 Layout of the “Dynamics” Tab of the Properties Dialog

Attributes

Connection Establishment

Retransmission Time


The retransmission time specifies the interval after which an unsuccessful connection establishment attempt can be triggered again (1–60 s, default 5 s)

– if connection establishment is active

– if connection establishment is passive (–> irrelevant)

Modifiable

–––––

Data Transfer

Retransmission time Modifiable This parameter specifies the interval after which an unsuccessful transmission attempt can be triggered again (100–30000 ms, default 1000 ms).


Release 6/2003

C79000–G8976–C129–07

109


Attributes

Max. CMax. Count is the number of attempted transmissions including the first (1–100, default 5).ount

Inactivity Time

Window Time


Modifiable

The inactivity time specifies the interval after which the connection is terminated if no sign of life is received from the partner (6–180 s, default 30 s).

The window time specifies the interval at which sign of life frames are sent. For SIMATIC NET CPs, the window time is set to 1/3 of the inactivity time (2–60 s, default 10 s). Sign of life frames are sent to check the connection when there is no data traffic.

Modifiable

Display only

Notice

Window Time and Inactivity Time

The partner responds to a sign of life frame with a frame. They are therefore sent to the partner at the intervals of the window time. To avoid unwanted connection termination, the inactivity time should be at least three times as long as the window time.

110


Release 6/2003

C79000–G8976–C129–07


4.4.4

Checking ISO Transport Connection Properties

Overview Tab

The Overview tab displays all previously configured ISO transport connections and their parameters for this station (information only).

For an example of this display, refer to Section 4.3.4.

Parameter

Local ID

Name

CPU / Applications

R/S or via CP

Remote address

Local TSAP

Partner TSAP

Mode

Status

Description

S7 Station: This is the connection ID of the ISO transport connection;

PC Station: Identification number for the connection.

Name entered for the connection endpoint.

If you display all the ISO transport connections being operated in this station in the multiprocessor mode (with PC stations: multiple applications), the

CPU/application that is the endpoint of the particular connection is specified here.

With S7-CPs: Rack/slot of the local CP via which the connection is established.

With PC stations: Display of the CP over which the connection is maintained.

Specifies the remote MAC address of the connection on the Ethernet subnet.

Transport Service Access Point for the local connection endpoint.

Transport Service Access Point for the remote connection endpoint.

Displays the mode configured in the ”Options” tab.

Indicates the current configuration of the connection.

“Connections without assignment” are indicated by “No local CP/No remote

CP” in the status column and a “!” character at the end of the“Local ID” (for example: 0002 A000!).

Connections you are currently editing are also indicated by “!” at the end of the local ID.

You can set the column widths in the “Overview” tab individually.

Connection Overview with Multiple CPUs in an S7 Station

If you operate more than one CPU in your S7 station, you can click the button to extend the overview to the connections on all CPUs.


Release 6/2003

C79000–G8976–C129–07

111


4.5

Configuring ISO-on-TCP Connections Properties

Introduction







Result: The “Properties ISO-on-TCP Connection” dialog appears.

Tabs

The following tabs are available for ISO-on-TCP connections:

S

General


S

Addresses


S

Options


S

Overview

This is an overview of all the configured ISO-on-TCP connections of the selected S7 station with their parameters and the status of the connection.

S


This tab displays the current status information for the connection (valid at the time the dialog is opened). This information corresponds to that displayed by

NCM diagnostics.

112


Release 6/2003

C79000–G8976–C129–07


4.5.1


General Tab


Figure 4-10 Layout of the “General” Tab in the Properties Dialog for ISO-on-TCP Connections


Release 6/2003

C79000–G8976–C129–07

113


Parameter

Local Endpoint

ID

Name

Via CP

Active Connection

Establishment


ID

LADDR



When you create the connection, a name is proposed here along with a connection number as suffix.


If the station contains more than one CP of the same type connected to the same subnet, you can select the connection route. –> “Route” button see Section 4.9.

If no CP is assigned (for example because the CP has been deleted) “none” is displayed here.




If you selected partner “unspecified” when you created the connection, the option is deselected as default. If you activate the option, you must also specify the address of the partner in the “Addresses” tab.

Note:

Please note the effects on the mode. If you want to use the

FETCH or WRITE mode (refer to the ”Options” tab), the mode must be set to ”Passive” for the S7 station.

Selectable

Modifiable

Display only

Modifiable


The ID changes if the local ID is changed.


Display only

Display only


If you create a connection to a partner in another project, that has not yet been merged with the current multiproject, you must enter a connection name as reference. Interproject connections can then be joined up based on this reference.

As soon as the connections have been brought together, the connection name

(reference) can no longer be entered.

114


Release 6/2003

C79000–G8976–C129–07


4.5.2

Specifying ISO-on-TCP Addresses

Address Parameters

A connection is specified by the local and remote connection endpoint.

S

Local addresses:

Local IP address and local TSAP

(Transport Service Access Point)

S

Remote addresses:

Remote IP address and remote TSAP

Ethernet station A Ethernet station B

Remote

TSAP

Local

TSAP

MAC address A


Local

TSAP

Remote

TSAP

IP address B

Figure 4-11 Sending and Receiving on One ISO-on-TCP Connection

The address parameters are configured with NCM S7 and saved in the CP database. Modifications and extensions to the Industrial Ethernet network topology do not therefore have any effect on the CPU user program.

Notice

When you configure the Ethernet CP and the Ethernet destination station, the

TSAPs of an ISO-on-TCP connection must cross match:

Remote TSAP (in Ethernet CP) = local TSAP (in destination station)

Local TSAP (in Ethernet CP) = remote TSAP (in destination station)


Release 6/2003

C79000–G8976–C129–07

115


Addresses Tab

The addresses tab displays proposed values for the relevant local and remote address information. If necessary, you can set the TSAP addresses individually.

Figure 4-12 Layout of the “Addresses” Tab of the Properties Dialog with Default TSAPs for ISO-on-TCP

Connections

TSAP Format

ISO-on-TCP connections have a TSAP length of 1 to 16 bytes. When you are entering values, the current length is displayed automatically (visible display: 16

ASCII characters). Local and remote TSAPs can be input as hexadecimal values or as ASCII strings. If you make your entries in ASCII, the characters you enter are also displayed in hexadecimal format. If you make your entries in hexadecimal, printable characters are displayed in ASCII (8 hexadecimal values are visible). If you enter nonprintable characters, the ASCII display is gray (no further ASCII entries possible) and the nonprintable characters are displayed as periods.

Local and Remote TSAPs

Remote and local TSAPs can be identical since the connection is uniquely identified by the different MAC addresses. If you require more than one connection between two stations, the TSAPs must also be different.

116


Release 6/2003

C79000–G8976–C129–07


Default TSAPs

When configuring the local and remote TSAPs, there is a default value “TCP-1” for the first connection between the two partners (can be changed). For a new connection between the two partners, the default value “TCP-2” is proposed. With a new connection to a new partner, the value TCP-1 is used again.

Addresses Tab – Unspecified ISO-on-TCP Connection


The Addresses tab shown here illustrates the situation in which the remote IP address and the remote TSAP were not specified. If you make no further entries, you are accepting connection establishment from any communication partner.

Figure 4-13 Layout of the “Addresses” Tab of the Properties Dialog for an Unspecified Connection


Release 6/2003

C79000–G8976–C129–07

117


4.5.3

Checking ISO-on-TCP Connection Properties

Overview Tab

The overview shows all the configured ISO-on-TCP connections and their parameters (cannot be modified here).

You can adjust the width of the columns in the table.

For an example of this display, refer to Section 4.3.4 (the ISO transport connection).

Parameter

Local ID

Description

This is the connection ID of the ISO-on-TCP connection (STEP 7 connection configuration; DWORD)

Entered connection name. This identifies the ISO-on-TCP connection.

Name (loc.

endpoint)

CPU /

Applications

R/S or via CP

If you display all the ISO transport connections being operated in this station in the multiprocessor mode (with PC stations: multiple applications), the CPU/application that is the endpoint of the particular connection is specified here.



Specifies the remote IP address of the connection.

Partner address

Local TSAP Local Transport Service Access Point (8 characters default)

Remote TSAP Remote transport service access point (8 characters default).

Mode

Status



“Connections without assignment” are indicated by “No local CP/No remote CP” in the status column and a “!” character at the end of the“Local ID” (for example: 0002 A000!).




118


Release 6/2003

C79000–G8976–C129–07


4.6

Configuring TCP Connection Properties

Introduction







Result: The “Properties – TCP Connection” dialog appears.

Tabs

The following tabs are available for TCP connections:

S

General


S

Addresses


S

Options


S

Overview

This is an overview of all the configured TCP connections of the selected S7 station with their parameters and the status of the connection.

S



NCM diagnostics.


Release 6/2003

C79000–G8976–C129–07

119


4.6.1


General Tab


Figure 4-14 Layout of the “General” Tab in the Properties Dialog for TCP Connections

120


Release 6/2003

C79000–G8976–C129–07


Attributes

Local Endpoint

ID

Name

Via CP

Active Connection

Establishment

Use for FTP protocol





If the station contains more than one CP of the same type connected to the same subnet, you can select the connection route –> “Route”, see Section 4.9.



If you selected partner “unspecified” when you created the connection, the option is deselected as default. If you activate the option, you must also specify the address of the partner in the “Addresses” tab.



Selecting the option has the following effects:

S

The TCP connection is now used as an FTP connection.

S

”Addresses” tab: The addresses are specified automatically

(Port=21)

S

”Options” tab: The mode is set permanently to FTP.

S

The ”Active connection establishment” option is irrelevant and cannot be set.

Configuration limits: see /1/

Precondition: The option can only be selected for an unspecified TCP connection.

Selectable

Modifiable

Display only

Modifiable

Modifiable


ID

LADDR




Display only

Display only


Release 6/2003

C79000–G8976–C129–07

121






122


Release 6/2003

C79000–G8976–C129–07


4.6.2

Specifying TCP Addresses

Address Parameters and Connection Types

With TCP, the communication partners are addressed by the local and remote endpoints as follows:

S

Local addresses:

Local IP address and local port

S

Remote addresses:

Remote IP address and remote port

Ethernet station A Ethernet station B remote port local port

MAC address A

TCP connection local port remote port

IP address B

Figure 4-15 Sending and Receiving on One TCP Connection

Depending on the required connection type, the remote address parameters are either specified or left open during configuration.

S

Specified TCP connection

You specified a destination station when you created the connection.

S

Unspecified TCP connection

You entered “unspecified” for the connection partner when you created the connection.


Release 6/2003

C79000–G8976–C129–07

123


Addresses Tab – Specified TCP Connection

The addresses tab displays proposed values for the relevant local and remote address information. You can change the port settings individually.

Figure 4-16 Layout of the Properties Dialog in the “Addresses” tab with DEFAULT Ports for TCP

Connections

Ports

The ports or port addresses define the access point to the user program within the station / CPU. They must be unique within the station / CPU!

The following table shows the range of values:

Table 4-4

Application / Note

Fixed, must not be used!

Assigned as default, should not be used (well-known ports)

Range used by NCM in which a free port address is searched for and assigned.

You can set any port address within this range.

Port addresses higher than 5000 are used by the system!

Note:

If you want to use these port addresses, please contact your system administrator.

Port Addresses

0

1 to 1024 from 2000 to 5000 from 5000...65535

124


Release 6/2003

C79000–G8976–C129–07


Addresses Tab – Unspecified TCP Connection


The Addresses tab shown here illustrates the situation in which the remote port but not the IP address was specified. If you make no further entries, you are accepting connection establishment with any communication partner that uses the specified port.

Figure 4-17


Release 6/2003

C79000–G8976–C129–07

125


4.6.3

Checking TCP Connection Properties

Overview Tab

The overview shows all the previously configured TCP connections and their parameters (cannot be modified here).



Parameter

ID

Name (loc. endpoint)

CPU / Applications

R/S or via CP

Partner address

Local port

Remote port

Mode

Status

Description

This is the connection ID of the TCP connection (STEP 7 connection configuration; DWORD).

Entered connection name. It identifies the TCP connection (8 character double width).





Local port (8 characters default length)

Remote port (8 characters default width)



“Connections without assignment” are indicated by “No local CP/No

remote CP” in the status column and a “!” character at the end of the“Local ID” (for example: 0002 A000!).




126


Release 6/2003

C79000–G8976–C129–07


4.7

Configuring UDP Connection Properties

Introduction







Result The “Properties – UDP Connections“ dialog appears.

Tabs

The following tabs are available for UDP connections:

S

General


S

Addresses


S

Overview

Overview of all configured UDP connections of the selected S7 station with corresponding parameters and the status of the connection.

S



NCM diagnostics.


Release 6/2003

C79000–G8976–C129–07

127


4.7.1


General Tab


Figure 4-18 Layout of the “General” Tab in the Properties Dialog for UDP Connections

128


Release 6/2003

C79000–G8976–C129–07


Attributes

Local Endpoint

ID

Name

Via CP


ID

LADDR





If the station contains more than one CP of the same type connected to the same subnet, you can select the connection route –> “Route”, see Section 4.9.


Selectable

Modifiable

Display only




Display only

Display only






Release 6/2003

C79000–G8976–C129–07

129


4.7.2

Specifying UDP Addresses

Address Parameters and Connection Types

With UDP, the communication partners are addressed using the local and remote endpoint, as follows.

S

Local addresses:

Local IP address and local port

S

Remote addresses:

Remote IP address and remote port

Note

The term “connection” is also used here for UDP. Reason:

During configuration (just as in TCP) the communication partners are assigned to each other and therefore logically “connected”. In actual fact, with UDP there is no explicit connection establishment between communication partners.

Ethernet station A Ethernet station B remote port local port

MAC address A

UDP connection

IP address B local port remote port

Figure 4-19 Sending and Receiving on One UDP Connection

Depending on the required connection type, the remote address parameters are either specified or left open during configuration.

S

Specified UDP connection

You specified a destination station when you created the connection.

Configuring broadcast or multicast provides you with a further option (see

Section 4.7.3 below).

S

Unspecified UDP connection

You entered “unspecified” for the connection partner when you created the connection.

130


Release 6/2003

C79000–G8976–C129–07


Addresses Tab – Specified UDP Connections

The addresses tab displays proposed values for the relevant local and remote address information. You can make the settings for the ports individually.

Figure 4-20 Layout of the Properties Dialog in the “Addresses” tab with DEFAULT Ports for UDP

Connections

Ports

The ports or port addresses define the access point to the user program within the station / CPU. They must be unique within the station / CPU!

The following table shows the range of values:

Table 4-5

Application / Note

Fixed, must not be used!

Assigned as default, should not be used (well-known ports)

Range used by NCM in which a free port address is searched for and assigned.

Port Addresses

0

1 to 1024

2000... onwards


Release 6/2003

C79000–G8976–C129–07

131


Addresses Tab – Unspecified UDP Connection

An unspecified UDP connection can be used in two ways:

S

Free UDP Connection

To configure a free UDP connection, select the “Address assignment in block” check box. The input boxes for the remote IP address and the remote port are then deactivated since the destination addresses are now specified by the user program.

S

Connection to a remote station in a different project

You can specify the remote IP address and the port for any destination station.

The destination station can be in the current STEP 7 project or in another project.

Please note:

Since no connection is actually established with UDP (datagram service), communication on the configured UDP connection is only possible when the partner addresses (IP address and port ) are specified.

Figure 4-21 Layout of the Properties Dialog in the “Addresses” Tab for the “Free UDP Connection” Mode

132


Release 6/2003

C79000–G8976–C129–07


4.7.3

UDP with Broadcast and Multicast

Application

When you select the connection partner, you have the following two extra options on UDP connections:

S

Connection to all Broadcast Nodes

If you select the “all broadcast nodes”, you specify that UDP frames are sent to all obtainable broadcast nodes.

Notice

When using broadcast, you can only send with S7-CPs; reception is not possible

(see below)!

S

Connection to all Multicast Nodes

If you select “all multicast nodes” as the partner, you specify that UDP frames are sent to all nodes of a multicast group and that multicast frames can be received.

Multicast is a special, configurable connection option that is supported by

Industrial Ethernet CPs only on UDP connections.

The frames are sent without acknowledgment because the UDP protocol has no provision for acknowledgments. This is designed to avoid floods of data resulting from the acknowledgments. If, for example, frames are sent to 100 partners, 100 acknowledgments (1 per partner) will arrive at the same time. The sending module would not be able to evaluate such a flurry of data.

When to Use Multicast instead of Broadcast?

To allow the simultaneous transmission of a frame to a number of partners, the connection option Multicast for UDP connections was introduced.

In contrast to the broadcast connection option, it is also possible to receive frames sent to several nodes in the multicast circle on this connection type.

By specifying a particular group of recipients (multicast circle), load on recipients for which the message is not intended is prevented. Multicast therefore represents a better solution than broadcast when frames are sent to groups of partner stations.


Release 6/2003

C79000–G8976–C129–07

133


Why Does an S7-CP Prevent Reception on Broadcast Connections?

It is often necessary for one station to send frames to a number of partner stations.

It is important that the frames are sent at the same time and arrive and practically the same time. Sending and receiving broadcast frames is always required. A broadcast message is received by all nodes in the network.

A typical application is the sending of broadcast frames to find a MAC address for an IP address (ARP request).

For this reason, a communications module must accept broadcast frames and evaluate them in its software. The major disadvantage of this is that network performance sinks significantly if there are too many broadcast frames because each individual module needs to process all the broadcast frames to find out whether the frames were intended for it.

To avoid these disadvantages, S7-CPs handle broadcast as follows:

S

Following reception, the broadcast frames are filtered out with high priority by all

Ethernet CPs. This means that frames that cannot be interpreted are discarded immediately. Only frames that can be interpreted, for example an ARP request, are passed on over the LAN controller and evaluated. This prevents a negative influence on the other connections by broadcast frames.

S

For the application, this means that the S7-CP cannot receive broadcast frames intended for the transfer of user data. It is, however, possible for the module to send broadcast frames within the network.

134


Release 6/2003

C79000–G8976–C129–07


Addresses Tab – Connection to all Broadcast Nodes

If you select “all broadcast nodes” as the connection partner, you specify that UDP frames are sent to all obtainable broadcast nodes.

In the “Addresses” tab, a valid broadcast address in the network is proposed for the partner under the IP address (IP).

You must enter a PORT address suitable for all partners you want to reach under

PORT.

Figure 4-22

Layout of the Properties Dialog “Addresses” Tab for the “Broadcast” Mode


Release 6/2003

C79000–G8976–C129–07

135


Addresses Tab – Connection to all Multicast Nodes

By selecting “all multicast nodes” as the connection partner, you specify that

S sent UDP frames are delivered to all multicast nodes of the multicast group;

S the local device receives multicast frames in the specified multicast group.

In the “Addresses” tab, a valid multicast address in the network is proposed for the partner under the IP address (IP). When using multicast, the partner is always a group of receivers (multicast group).

You must enter a PORT address suitable for all partners you want to reach under

PORT.

Figure 4-23

IP addresses from 224.0.0.0 to 239.255.255.255 can be used for IP multicast.

Since the IP addresses up to 224.0.0.255 are reserved for special purposes, we recommend that you use IP addresses starting at 224.0.1.0 (default) for IP multicast.

136


Release 6/2003

C79000–G8976–C129–07


4.7.4

Checking the Properties of a UDP Connection

Overview Tab

At the overview level, all the configured UDP connections and their parameters in this station are displayed (cannot be modified).



Local ID

Parameter

Name (loc. endpoint)

CPU / Applications

R/S

Partner address

Local port

Remote port

Status

Description

This is the connection ID of the UDP connection (STEP 7 connection configuration; DWORD).

Entered connection name. This identifies the UDP connection (8 characters default length).


Rack/slot of the local CP via which the connection is established.


Local port (8 characters default length)

Remote port (8 characters default width)


“Connections without assignment” are indicated by “No local CP/No

remote CP” in the status column and a “!” character at the end of the“Local ID” (for example: 0002 A000!).





Release 6/2003

C79000–G8976–C129–07

137


4.7.5

Free UDP Connection

Program-Controlled Addressing

A free UDP connection allows program-controlled addressing of the communication partner. Communication between two nodes on Industrial Ethernet has the following properties:

S

Data transfer is bi-directional; in other words it is possible to send and receive on the UDP connection at the same time.

S

The local node is specified in the configuration. The remote node is entered in the job header of the job buffer by the user program when it calls AG_SEND.

This allows any node on Ethernet/LAN/WAN to be reached.

S

The IP address and the port of the sender can be read from the job header of

AG_RECV.

SIMATIC S7 station with Ethernet CP

User data area

Job buffer send

Job header receive unspecified

UDP connection

Ethernet node

(unspecified) receive send

User data

Figure 4-24 Sending and Receiving on an Unspecified UDP Connection with Programmed Addressing

Amounts of Data

Refer to the manual /1/ supplied with the Ethernet CP for the number of UDP connections supported by the Ethernet CP. The number of connections per station can be increased by adding more CPs.

Up to 2042 bytes of user data can be transferred per job buffer. The job header uses an additional 6 bytes.

138


Release 6/2003

C79000–G8976–C129–07


4.8

FETCH/WRITE Mode

FETCH/WRITE

The FETCH/WRITE services allow direct access to the system memory areas on the SIMATIC S7 CPU from SIMATIC S5, SIMATIC PC stations, or from devices of other ranges.

S

FETCH: Read data directly

S

WRITE: Write data directly

Connection Types

The FETCH/WRITE services can be configured and used in SIMATIC S7 on the following connection types:

S

ISO transport connections

S

ISO-on-TCP connections

S

TCP connections

Configuration

Depending on the station type, the following modes can be configured for the connection endpoint:

S

SIMATIC S7 Station: FETCH PASSIVE / WRITE PASSIVE

If you select the FETCH PASSIVE or WRITE PASSIVE mode for the ISO transport connection, you can access the system areas on a SIMATIC S7 PLC from a SIMATIC S5 station or other non-S7 station (unspecified connection).


Release 6/2003

C79000–G8976–C129–07

139


Figure 4-25 Configuring FETCH PASSIVE Based on the Example of an ISO Transport Connection

The connection can then only be used for this mode; sending or receiving with the FCs AG_SEND/AG_LSEND or AG_RECV/AG_LRECV is then no longer possible.

The connection is established passively; in other words, only the partner station

(SIMATIC S5 station, a PC station, or a non-SIMATIC station) can establish the connection. The setting is made automatically in the “General” tab and cannot be changed.

Notice

Remember that with this configuration on an S7-300, one connection resource

(free connection for S7 functions) of the S7-300 CPU is used. CPU connection resources are also used, for example, by S7-300 CPs, in the FMS mode or by

PGs and OPs. For more detailed information about the maximum connection resources, refer to /13/ and /7/.

S

SIMATIC PC Station: FETCH ACTIVE / WRITE ACTIVE

If you select the FETCH ACTIVE or WRITE ACTIVE mode for the ISO transport connection, you can access the system areas on a SIMATIC S7 PLC or a SIMATIC S5 station from the PC station.

The connection establishment is active; in other words, the partner station must wait for connection establishment (passive connection establishment on the partner).

140


Release 6/2003

C79000–G8976–C129–07


“S7 Addressing Mode” Option

When you configure the FETCH ACTIVE / WRITE ACTIVE modes, you can select the addressing mode. This specifies how the addresses will be interpreted in the

FETCH/WRITE call in the SIMATIC S7 station:

S

S7 addressing mode: byte address

S

S5 addressing mode: word address

This makes it possible for applications to access S5 or S7 stations without needing to adapt the addresses. This is particularly interesting for existing S5 applications than can be used unchanged to access S7 stations.

As default, the addressing mode for access to SIMATIC S7 is set (option selected).

System Memory

You can access the following address areas in the system memory on the

SIMATIC S7 PLC using FETCH or WRITE:

S

Data blocks (DB)

(When accessing DBs, remember that the highest DB number is 255.)

S

Bit memory (M, MB, MW, MD)

S

Process image input table (I, IB, IW, ID)

S

Process image output table (Q, QB, QW, QD)

S

I/O area inputs (PIW, PID, PIB)

S

I/O area outputs (PQW, PQD, PQB)

S

Counters (C)

S

Timers (T)

Links to Other Systems

The FETCH and WRITE modes supported on ISO transport connections and

ISO-on-TCP or TCP connections can be used with any other device to access the

S7 system memory areas.

To be able to use this type of access, for example for PC applications, you need to know the PDU structure of the jobs. The required S7 or S5 headers for request and response frames are 16 bytes long and their structure is described in the

Appendix.


Release 6/2003

C79000–G8976–C129–07

141


Messages in the Diagnostic Buffer

As a result of FETCH/WRITE access, negative acknowledgments from the S7

CPU are possible. This then leads to corresponding connection-oriented entries in the diagnostic buffer that you can read out with NCM Diagnostics (see Section

7.5).

142


Release 6/2003

C79000–G8976–C129–07


4.9

Routing to Distribute Load

Routing to Distribute Load

If more than one CP of the same type exists in a station and is connected to the same subnet, the route can be selected

.

Click the “Route” button in the “General” tab to display the route dialog:

If you have configured a load distribution on two or more Ethernet CPs at the local or remote end, you can assign the connection to the required route via the CP.


Release 6/2003

C79000–G8976–C129–07

143


Parameter Description

Via CP / Local If more than one Ethernet CP exists in the station via which connections operated you can select route here.

The CPs are only displayed for selection if they are networked.

If no CP is assigned (for example because the CP was deleted previously) “(None)” is displayed here.

If there is only one CP plugged into the station, no selection is possible.

Via CP /

Partner

(remote)

Depending on the local selection, the possible remote CPs are displayed. All the CPs connected to the same subnet (networked) and the local CP can be selected.

Alternatives are only available when a connection is established to a remote station configured in the same project and the remote station has two or more CPs.

If there is no CP assigned on the partner (for example because the CP was deleted previously) “None” is displayed here.

If there is only one CP in the remote station, no selection is possible.

If the partner is an “other station” or SIMATIC S5 PLC, one or more attachments are displayed for selection depending on the configuration and networking of the station.

-

144


Release 6/2003

C79000–G8976–C129–07

Programmed Communication Connections

Programmed Communication Connections

5

V 5.2.1

In some situations, it is an advantage to set up communication connections not over the configuration interface of STEP 7 but program-controlled by a specific application.

Typical users who will find this useful are, for example, mass producers of machines who want to offer their customers a simple user interface but need to adapt the communication services to the operator input. The end user should not need knowledge of STEP 7.



S

For the properties of the configurable connection types, refer to Section 4.

S

For the properties of the configurable connection types E-mail connection and

FTP connection, refer to /5/.

S

After installing STEP 7 and the NCM S7 for Industrial Ethernet option, you will find a programmed example in the ”Sample projects” tab of the

SIMATIC Manager. This example is described in the appendix.

S

You will find information on the numbers of connections and amounts of data in

Section 3.1.

Notice

Please remember that the functions described here depend on the characteristics of the CP type you are using /1/ .


Release 6/2003

C79000–G8976–C129–07

145


5.1

Overview

Area of Application

Communication connections can be freely configured controlled by the program.

Interplay between Programming and Configuration

Connections are either configured using STEP 7 or configured by the user program while the S7 station is running. Mixing these variants on a CP is not possible!

Principle

Configuration data for communication connections can be transferred to the CPU using the function block called in the user program.

Configuration data block

FB55 CP_CONFIG

System data for CP

Connection 1

Connection 2

Configuration data transferred to the CP

Connection n *)

*) n max

= 64

The configuration DB can be loaded on the CP at any time. The previously valid connections are then overwritten.

Based on the configuration data, the Ethernet CP recognizes that the communication connections must be set up by the user program.

As soon as the user program transfers the connection data via FB55 IP_CONFIG, the CPU switches the CP briefly to STOP. The CP receives the system data

(including the IP address) and the new connection data and processes them during startup (RUN).

Configuration Limits

A maximum of 64 connections can be specified in FB55 CP_CONFIG. The most important factor, however, is the maximum number of connections supported by the CP type you are using (see /1/).

146


Release 6/2003

C79000–G8976–C129–07


Special Features / Restrictions

S

Consistency check only with STEP 7

The connection configuration in STEP 7 involves consistency checks that are not possible or only possible with restrictions when using the programmed configuration!

S

Connection configuration required on the partner

When configuring specified connections in STEP 7, you implicitly create the connection for the partner; with a programmed configuration, this is not possible! In this case, you must configure suitable connections for the partner.

S

DHCP / DNS is supported

IP address assignment is also possible using DHCP/DNS even if you choose programmed configuration.

S

No ISO transport connections

The configuration of ISO transport connections over the program interface is not supported.

S

No connection information when uploading

When you upload the S7 station data in STEP 7, this does not contain the data of the programmed configuration.


Release 6/2003

C79000–G8976–C129–07

147


5.2

Procedure


The steps described here assume the following:

1. You have created the local S7 station and the required partner stations in your

STEP 7 projects (refer to the description in Chapter 2).

2. You have clarified the other station types with which connections must be established. You create substitute objects for these station types in your

STEP 7 projects.

Setting up Connections and Using Them in the User Program

Follow the steps outlined below to set up connections on the SIMATIC S7 PLC using the user program:

Configuring

Set the CP Properties in the “IP Configuration” tab:

Select the “Set IP address in user program” option.

Programming

Create system data and connections in the configuration

DB

Specify the connection characteristics in the

Configuration DB.

Program the

SEND/RECEIVE interface in the user program.

(Refer to Section 3.2 and the detailed FC description in

Chapter 6).

Program FB interface in the user program.

148

Download configurations and user programs to the S7 station.

Legend: necessary steps optional steps


Release 6/2003

C79000–G8976–C129–07


5.3

Configuration Data Block

Meaning

The configuration data block (CONF_DB) contains all the connection data for an

Ethernet CP. The configuration data block is transferred to the CP with function block FB55.

Block and Data Structure

The graphic below shows the following:

S

Structure resulting from parameter fields and subfields

– The connections and specific system data are is described by an identically structured parameter field.

– Individual parameters are characterized by subfields.

S

Offset range

The CONF_DB can start at any point within a data block as specified by an offset range.

Configuration data block

Offset range 0..n

CONF_DB

DB identifier

System data for CP

Connection 1

Connection 2

Connection n *)

Parameter field for system data (CP networking) and connections

Type

ID (for system data = 0)

Number of subfields

Subfield 1

Subfield 2

Subfield

Individual parameters

Subfield n

Subfield types are described below in

Section 5.6

Parameter fields are described below in

Sections 5.4 and 5.5


Release 6/2003

C79000–G8976–C129–07

149


5.4

Parameter Field for System Data

(CP Networking)

Meaning

Below, you can see the subfields that are relevant for networking the CP. These must be specified in the parameter field for system data.

Some applications do not require all the subfield types – refer to the table for details.

Structure

Type = 0

ID = 0

Number of subfields = n

Subfield 1

Subfield 2

Subfield n

Usable Subfields

Table 5-1

ID

Subfield

Type

SUB_IP_V4

SUB_NETMASK

*)

SUB_DEF_ROUTER

SUB_DNS_SERV_ADDR

–

Parameter

Special Features / Notes

(Please refer also to the general description in Table 5-7 Page 159)

Local IP address 1

2

8

4

–

This subfield can occur from 0 to 4 times.

The first entry is the primary DNS server.

14

15

SUB_DHCP_ENABLE

SUB_CLIENT_ID

0: No DHCP

1: DHCP

–

*) The general properties of the subfield types are described below in Section 5.6.

Use

( mandatory

/ optional)

m m m o o o

150


Release 6/2003

C79000–G8976–C129–07


Example

Address

+2.0

+4.0

+0.0

+1.0

+2.0

+3.0

=4.0

=8.0

+3.0

=4.0

=8.0

+22.0

+0.0

+2.0

+4.0

+0.0

+1.0

+2.0

+3.0

=4.0

=8.0

+14.0

+0.0

+2.0

+4.0

+0.0

+1.0

+2.0

0.0

+0.0

+2.0

+0.0

+2.0

+4.0

+6.0

+0.0

Name

Sub_field_len

Parameter

Value_1

Value_2

Value_3

Value_4

END_

END_

Sub_field_3

Sub_field_ID

Sub_field_len

STAT9

STAT10

STAT11

STAT12

STAT13

END_

END_

STRUCT

DB_TYP

FIELD_1

Type

ID

Subfield_Cnt

Sub_field_1

Sub_field_ID

Sub_field_len

STAT9

STAT10

STAT11

STAT12

STAT13

END_

END_

Sub_field_2

Sub_field_ID

Type

INT

STRUCT

BYTE

BYTE

BYTE

BYTE

STRUCT

STRUCT

INT

STRUCT

BYTE

BYTE

BYTE

BYTE

STRUCT

STRUCT

STRUCT

INT

INT

STRUCT

BYTE

BYTE

BYTE

BYTE

STRUCT

STRUCT

STRUCT

INT

WORD

STRUCT

INT

INT

INT

STRUCT

INT

2

8

B#16#FF

B#16#FF

B#16#FF

B#16#0

0

0

3

1

8

B#16#C0

B#16#6F

B#16#DE

B#16#6A

Initial Value

W#16#1

Comment

Identifier

// Field 1 (here system data field)

Type of data to be transferred 0 ... 5

Connection ID (with system parameters 0)

Number of subfields belonging to this field

// Subfield 1 SUB_IP_V4

// Number of the subfield

// Length of the subfield in bytes

8

8

B#16#C0

B#16#6F

B#16#DE

B#16#6A

// Subfield 2 SUBNET_MASK



SUBNET_MASK

// Subfield 3 default router




Release 6/2003

C79000–G8976–C129–07

151


5.5

Parameter Fields for Connection Types

General

Below, you will see which values need to be entered in the parameter fields and which subfields are used for the various connection types.

Some applications do not require all the subfield types – refer once again to the table for details.

Note

Please read the explanations of the configurable connection properties for the individual connection type in Chapter 4!

Connection ID

The ID parameter that precedes each connection parameter field beside the type

ID is particularly important.

On programmed connections, you can assign this ID freely within the permitted range of values. You must then use this ID on the call interface of the FCs for the

SEND/RECV interface to identify the connection.

Range of values for the connection ID:

S

S7-400: 1,2 through 64

S

S7-300: 1,2 through 16

152


Release 6/2003

C79000–G8976–C129–07


5.5.1

Parameter Field for TCP Connection

Structure

Type = 1

ID = connection ID

No_of_subfields = n

Subfield 1

Subfield 2

Subfield n

Identifier for the connection type

Freely assignable connection reference; must be specified in AG_SEND / AG_RECV.


S

S7-400: 1,2 through 64

S

S7-300: 1,2 through 16


Table 5-2

ID

Subfield

Type

SUB_IP_V4

*)

SUB_LOC_PORT

SUB_REM_PORT

SUB_CONNECT_NAME

–

Parameter



IP address of the partner 1

9

10

18

–

–

19

21

22

SUB_LOC_MODE

SUB_KBUS_ADR

SUB_CON_ESTABL

–

This value is always set to 0 for CPs for the

S7-300 and does not need to be specified.

–


Use

( mandatory

/ optional)

m m m o o m (for

S7-400) m

Note

Please read the description of the configurable connection properties for the TCP connection in Section 4.6!


Release 6/2003

C79000–G8976–C129–07

153


5.5.2

Parameter Field for a UDP Connection

Structure

Type = 2


No_of_subfields = n

Subfield 1

Subfield 2

Subfield n




S

S7-400: 1,2 through 64

S

S7-300: 1,2 through 16


Table 5-3

ID

Subfield

Type

*)

–

–

–

Parameter



IP address of the partner 1

9

10

18

SUB_IP_V4

SUB_LOC_PORT

SUB_REM_PORT

SUB_CONNECT_NAME

19

21

SUB_LOC_MODE

SUB_KBUS_ADR

–



– 22 SUB_CON_ESTABL

23 SUB_ADDR_IN_DATABLO

CK

If the “Free UDP connection” is selected for this parameter, the parameters

SUB_IP_V4, SUB_LOC_PORT,

SUB_REM_PORT are omitted.


m o o

Use

( mandatory

/ optional)

m m m (for

S7-400) m o

Note

Please read the description of the configurable connection properties for the for the UDP connection in Section 4.7!

154


Release 6/2003

C79000–G8976–C129–07


5.5.3

Parameter Field for an ISO-on-TCP Connection

Structure

Type = 3


No_of_subfields = n

Subfield 1

Subfield 2

Subfield n




S

S7-400: 1,2 through 64

S

S7-300: 1,2 through 16


Table 5-4

ID

Subfield

Type

*)

Parameter



1

11

12

18

SUB_IP_V4

SUB_LOC_TSAP

SUB_REM_TSAP

SUB_CONNECT_NAME

IP address of the partner

–

–

–

19

21

22

SUB_LOC_MODE

SUB_KBUS_ADR

SUB_CON_ESTABL

–



–


m o o m m

Use

( mandatory

/ optional)

m (for

S7-400) m


Release 6/2003

C79000–G8976–C129–07

155


5.5.4

Parameter Field for an E-Mail Connection

Meaning

To send E-mails, you must always set up one E-mail connection per IT-CP. The

E-mail connection specifies the mail server, over which all the E-mails sent by the

IT-CP are delivered.

You will find a detailed description of how to use the E-mail function with IT-CPs in

/5/.

Structure

Type = 4


No_of_subfields = n

Subfield 1

Subfield 2

Subfield n


Freely assignable connection reference; must be specified in AG_SEND.


S

S7-400: 1,2 through 64

S

S7-300: 1,2 through 16


Table 5-5

1

3

13

18

ID

Subfield

Type

SUB_IP_V4

*)

SUB_DNS_NAME

SUB_EMAIL_SENDER

SUB_CONNECT_NAME

Parameter



IP address of the mail server, over which the E-mails are sent.

The IP address can be specified in absolute or symbolic form.

The symbolic form assumes that the IT-CP knows the address of the domain name server (DNS). This must be entered during configuration of the IT-CP in HW Config, for more detailed information, refer to the online help of HW Config.

DNS name of the E-mail server

E-mail address of the sender

–

Use

( mandatory

/ optional)

m / o

**) m / o

**) m o

156


Release 6/2003

C79000–G8976–C129–07


Table 5-5 , continued

21

ID

Subfield

Type

*)

SUB_KBUS_ADR

–

Parameter





22 SUB_CON_ESTABL


Use

( mandatory

/ optional)

m (for

S7-400) m

**) The parameters SUB_IP_V4 and SUB_DNS_NAMEare mutually exclusive; one or the other must be specified.

Note

Mail server ports are well-known ports and do not need to be specified.


Release 6/2003

C79000–G8976–C129–07

157


5.5.5

Parameter field for FTP connection

Meaning

To handle an FTP job sequence between the S7 station as FTP client and an FTP server, the IT-CP must set up a connection to the S7-CPU. This connection is known in this context as an FTP connection.

FTP connections are TCP connections, with the parameter SUB_LOC_MODE set to the “FTP” mode.

You will find a detailed description of how to use the FTP function with IT-CPs in

/5/.

Structure

Type = 1


No_of_subfields = n

Subfield 1

Subfield 2

Subfield n


Freely assignable connection reference; must be specified in the FC FTP_**.


S

S7-400: 1,2 through 64

S

S7-300: 1,2 through 16


Table 5-6

18

19

ID

Subfield

Type

SUB_CONNECT_NAME

SUB_LOC_MODE

–

Parameter



here: 0x01 = FTP protocol

21 SUB_KBUS_ADR This value is always set to 0 for CPs for the



Use

( mandatory

/ optional)

o m m (for

S7-400)

158


Release 6/2003

C79000–G8976–C129–07


5.6

Subfield types

Different parameters are required depending on the parameter field. Each parameter is described by a subfield. Which subfields are required is explained in the descriptions of the system data and the connection types in the previous sections.

Each subfield consists of the specific parameter section and the header (4 Byte).

Example

The following excerpt from a CONF_DB illustrates the structure of a subfield based on the example of the SUBNET_MASK subfield type.

Header

Parameter

Address

+1.0

+2.0

+3.0

=4.0

=8.0

+14.0

+0.0

+2.0

+4.0

+0.0

Name

Sub_field_2

Sub_field_ID

Sub_field_len

Parameter

Value_1

Value_2

Value_3

Value_4

END_

END_

Type

STRUCT

INT

INT

STRUCT

BYTE

BYTE

BYTE

BYTE

STRUCT

STRUCT

2

8

Initial Value Comment

// Subfield 2 type SUBNET_MASK

// Subfield ID

// Total length of the subfield in bytes

Parameter range of SUBNET_MASK

B#16#FF

B#16#FF

B#16#FF

B#16#0

In total, the following subfield types are available:

Table 5-7

Subfield

ID

1)

1

2

3

4

8

9

10

Subfield type

SUB_IP_V4

SUB_NETMASK

SUB_DNS_NAME

SUB_DNS_SERV_ADDR

SUB_DEF_ROUTER

SUB_LOC_PORT

SUB_REM_PORT

Subfield length (in bytes)

4 + 4

4 + 4

Length of

DNS name +

4

4 + 4

4 + 4

2 + 4

2 + 4

Meaning of the Parameter

IP address according to IPv4

Subnet mask

DNS name

DNS server address

IP address of default router

Local port

Remote port, also for E-mail connections


Release 6/2003

C79000–G8976–C129–07

159



Subfield

ID

1)

Subfield type

11 SUB_LOC_TSAP

12

13

SUB_REM_TSAP

SUB_EMAIL_SENDER

14

15

18

19

20

22

SUB_DHCP_ENABLE

SUB_CLIENT_ID

SUB_CONNECT_NAME

SUB_LOC_MODE

SUB_REM_MODE

SUB_CON_ESTABL


TSAP length

+ 4

TSAP length

+ 4


Local TSAP

Remote TSAP

Length of the sender

E-mail address + 4

1 + 4

E-mail address of the sender

Obtain an IP address from a DHCP server

S

Possible values:

0 = no DHCP

1 = DHCP

(optional)

Length of the client ID + 4

(optional)

Name of the connection Length of the name + 4

1 + 4

1 + 4

1 + 4

Local mode of the connection

S

Possible values:

0x00 = SEND/RECV

0x01 = FTP protocol (TCP connection only)

0x10 = S5 addressing mode for

FETCH/WRITE *)

0x80 = FETCH *)

0X40 = WRITE *)

If you do not set the parameter, the default setting is SEND/RECV.

*) Note:

The specified codings can be can be combined by ORing them.

Setting the mode on the communication partner.

(not currently supported)

Type of connection establishment.

With this option, you specify whether the connection is established by this S7 station.

S

Possible values:

0 = passive

1 = active

Refer also to Chapter 4 under ”Specifying the local connection endpoint” for the individual connection types.

160


Release 6/2003

C79000–G8976–C129–07



Subfield

ID

1)

23

Subfield type

SUB_ADDR_IN_DATABLO

CK


1 + 4


Select free UDP connection.

The remote node is entered in the job header of the job buffer by the user program when it calls AG_SEND. This allows any node on Ethernet/LAN/WAN to be reached.

S

Possible values:

1 = free UDP connection.

0 = otherwise

The parameter is practical only for a UDP connection.

See also Section 4.7.5

1) Note: ID numbers not listed are not currently used.

-


Release 6/2003

C79000–G8976–C129–07

161


162


Release 6/2003

C79000–G8976–C129–07

Programming FCs (Functions) and FBs for

S7 Ethernet CPs

6

The interface to several communication services is implemented by ready-made program blocks (FCs and FBs). This chapter includes a detailed description of these blocks.

The description of each FC / FB includes the following sections that may be extended by specific information:

S

Meaning

S

Call Interface

S

How the Block Works

S

Explanation of the Formal Parameters

S

Condition Codes

This chapter provides you with information over and above the general information available in the online help for the FCs when programming in STEP 7.


S

The communication FBs (BSEND, BRCV, PUT, GET, USEND, URCV,

C_CNTRL) for programming S7 communication are described in the STEP 7

Documentation /9/.

Sample configurations and programs are available for the SEND/RECEIVE interface described here:

S

In the sample project PROJECT_ETHERNET that you can start immediately after installing NCM S7; for a description, refer to the Primer /3/.

S

On the Internet as downloadable sample projects; refer to the information in

Appendix C “Support and Training”.


You can order this directly on the Internet at: http://www.ad.siemens.de/csi/net


Release 6/2003

C79000–G8976–C129–07

163

Programming FCs (Functions) and FBs for S7 Ethernet CPs

6.1

General Notes on FCs / FBs

Block Library

The functions (FCs) and function blocks (FBs) described here are supplied with the

STEP 7 basic package unless indicated otherwise.

The following list shows the numbers of the FCs as they are supplied with the configuration tool. You can change these numbers.

Under SIMATIC_NET_CP, you can also see which folders contain blocks after installing the NCM S7 for Industrial Ethernet option (default setting in STEP 7

Setup). Please note that you must use different FCs for the S7-300 and S7-400

(separate libraries).

Communication

S i /

SEND/RECEIVE FC5

(S5-compatible

FC6

FC50

FC60

FC7

FC8

FB55 Programmed

Communication

Connections

S7 i ti

FB12

FB13

FB15

FB14

FB8

FB9

FC62

Block Type

AG_SEND

AG_RECV

AG_LSEND

AG_LRECV

AG_LOCK

AG_UNLOCK

IP_CONFIG

BSEND

BRCV

PUT

GET

USEND

URCV

C_CNTRL x x x x x x x

SIMATIC Manager Library

SIMATIC_NET_CP

CP 300

x x x

2) x

2)

CP 400

x x x x x x x x x

–

Described in

Section 6.3

Section 6.3

Section 6.3

Section 6.3

Section 6.4

Section 6.4

Section 6.5

STEP 7 t ti

164


Release 6/2003

C79000–G8976–C129–07


FTP (IT-CPs) FC40

FC41

FC42

FC43

FC44

FB88

1)

FTP_CONNECT

FTP_STORE

FTP_RETRIEVE

FTP_DELETE

FTP_QUIT

PN_InOut

1)

SIMATIC Manager Library

SIMATIC_NET_CP

CP 300

x

CP 400

x x x x x x x x x x

PROFInet

1)

FB88 supplied along with the engineering tool SIMATIC iMap.

2)

Not to be used for current CPs

SIMATIC NET l /5/

Manual CP

343-1 PN /1/

Which Block Version Should I Use?

The following descriptions also include information on differences between the various block versions. Please take note of the version identifiers of the blocks you are using.

The SIMATIC Manager block libraries installed with STEP 7 / NCM S7 contain the block versions that were current at the time of the STEP 7 release.

Note

We recommend that you always use the latest block versions for all module types.

You will find information on the current block versions and the current blocks to download from the Internet in our customer support.

http://www4.ad.siemens.de/view/cs/de/8797900

Entry ID: 8797900

With the older module types, this recommendation assumes that you are using the latest firmware for the particular block type.


Release 6/2003

C79000–G8976–C129–07

165


Notice

At various points in this chapter, you will find information on the different CP versions. These passages are highlighted with the following symbol:

Newer CP types are CPs / module types with the following versions or higher:

CP 343-1 / CP 343-1 EX20

6GK 343-1EX11-0XE0 version 1 or higher / firmware version V2.0 or higher

6GK 343-1EX20-0XE0 version 1 or higher / firmware version V1.0 or higher

CP 343-1PN

6GK 343-1HX00-0XE0 version 1 or higher / firmware version V1.0 or higher

CP 343-1 IT / CP 343-1 IT GX20

6GK 343-1GX11-0XE0 version 1 or higher / firmware version V2.0 or higher

6GK 343-1GX20-0XE0 version 1 or higher / firmware version V1.0 or higher

FCs and Module Replacement (Spares)

Module replacement in this sense means the replacement of a module with another module that may be a more recent version.

Notice

Please remember that if you replace a module, you must only use the blocks permitted for the configured CP type in the user program.

This means:

S

If you replace the module without adapting the configuration data to the possibly newer module type, you do not need to make any changes to the blocks used.

S

If you replace the module and you do adapt the configuration data to the newer module type, you must use the block versions approved for this module type.

We recommend that you always use the latest block versions for all module types.

With the older module types, this recommendation assumes that you are using the latest firmware for the particular block type.

You will find more information on replacing blocks in our Customer Support on the

Internet.

The manuals /1/ contain information on the compatibility of the S7-CPs and the corresponding blocks (FCs / FBs).

166


Release 6/2003

C79000–G8976–C129–07


6.2

Setting Parameters for FC Calls

Before describing the FCs in detail, a few general comments on calling and setting parameters for FCs will be useful in this point.

It is possible to make the following general statements about the following parameter groups that occur in all FCs:

S

Parameters for CP and connection assignment (input parameters)

S

Parameters for specifying a CPU data area (input parameters)

S

Status information (output parameters)

Calling Communication Blocks for an S7-300

Caution

The communication blocks for S7-300 (SIMATIC NET block libraries for S7-300 in

STEP 7) must not be called in more than one priority class! If, for example, you call a communication block in OB1 and in OB35, block execution could be interrupted by the higher-priority OB.

If you call blocks in more than one OB, you must write your program so that a communication block that is currently executing cannot be interrupted by another communication block (for example by disabling/enabling SFC interrupts).

6.2.1

Parameters for CP and Connection Assignment (input parameters)

When you call an FC, you transfer the module start address of the Ethernet CP in the CPLADDR or LADDR parameter. The module start address of the Ethernet CP can be found in the properties dialog of the CP in the ”Address/Input” tab (can be selected in the SIMATIC Manager or in HW Config).

With connection-oriented jobs, you must also reference the connection to be used by its connection ID. You will find this in the properties dialog of the connection under “Block parameters” (refer to the information in NetPro).


Release 6/2003

C79000–G8976–C129–07

167


Setting Block Parameters Automatically

1)

To ensure correct parameter settings for the block calls, The LAD/STL/FBD editor in STEP 7 provides you with the option of accepting all the relevant parameters from the hardware configuration (HW Config) and from the connection configuration (NetPro).

When assigning the parameters for the block in the user program, follow the steps outlined below:

1. Select the block call and its block parameters;

2. Right-click and select the menu command “Connections...” .

3. Depending on the block type, you can now select the connection and/or module intended for the block from a list.

4. Confirm your selection; as far as possible, the available parameter values are entered in the block call.

Response to Incorrect Addresses

If the S7 CPU cannot communicate with the Ethernet CP using the specified module base address, the errors described below occur.

Cause

No module can be addressed or identified at the specified CP address.

The CP address points to a different module type.

Reaction / Code

The CPU remains in the stop with system error state; in this case, evaluate the diagnostic buffer of the CPU.

Possible error code in the STATUS parameter of the communication block:

8184H

80B0H

80C0H

80C3H

80D2H

System error

Module does not recognize data record.

Data record cannot be read.

Resources occupied (memory).

Logical base address wrong.

Notice

If you inadvertently address not a CP but another module type, errors occur that cannot be indicated by the error messages of the FCs themselves.

1).

This function is possible only with the block library ..V5.0 SP3 or later.

168


Release 6/2003

C79000–G8976–C129–07


6.2.2

Parameters for Specifying a CPU Data Area (input parameters)

Specifying the Data Area on the CPU

When you call an FC, you transfer the address and length of the data area on the

CPU in which the user data are available or will be stored or which can contain further parameter information.

The ANY pointer data type is used to address this area. For more detailed information on this data type, refer to the STEP 7 online help under the topic

“Format of the Parameter Type ANY”. You will also find a detailed description of the ANY point in /21/.

6.2.3

Status Information (output parameters)

For status evaluation, the following parameters must be evaluated in the user program:

S

DONE or NDR

These parameters (DONE with send jobs and NDR with receive jobs) signal

(successful) completion of the job.

S

ERROR

This indicates that the job could not be executed error-free.

S

STATUS

This parameter supplies detailed information about the execution of the job.

Status codes can be returned during execution of the job (DONE=0 and

ERROR=0).

Evaluating Status Codes

Remember that the status codes DONE, NDR, ERROR, STATUS are updated at each block call.

Status Codes during CP Startup

With a startup or restart of the Ethernet CP (after activating a switch on the module), the output parameters of the FC are reset as follows:

S

DONE = 0

S

NDR = 0

S

ERROR = 0

S

STATUS = 8180

H

for AG_RECV / AG_LRECV or 8181

H for AG_SEND

/AG_LSEND


Release 6/2003

C79000–G8976–C129–07

169


6.3

FCs for the SEND/RECEIVE Interface

Overview

The following FCs are available for transferring data on the SEND/RECEIVE interface:

FC

AG_SEND (FC5)

AG_RECV (FC6)

AG_LSEND (FC50)

AG_LRECV (FC60)

Can be used with

1)

S7 – 300 S7 – 400

x x x x x x

Meaning

for sending data for receiving data for sending data for receiving data

1)

Notes on the FCs in FCs for an S7-300 and S7-400

S

S7-300:

With older versions of the Ethernet CPs, the data length per job is restricted to

<=240 bytes (applies up to block version V3.0 of AG_SEND / AG_RECV); with later versions, longer data records (up to 8192 bytes) can be transferred with

FCs AG_LSEND or AG_LRECV.

With the latest versions of the Ethernet CPs, only FCs AG_SEND and

AG_RECV are used; due to a new and more efficient internal protocol, the data up to 8192 bytes can be transferred.

S

S7-400:

With FCs AG_SEND / AG_RECV the data length per job is restricted to <=240 bytes.

Longer data records (up to 8192 bytes) can be transferred with FCs

AG_LSEND or AG_LRECV.

Please check the manual /3/ of the S7-CP you are using for the data areas supported. You will find an overview of the versions of the FCs/FBs in the documentation and block history.

Application

The following diagram illustrates the use of the FCs described here for bi-directional data transfer on one configured connection.

170


Release 6/2003

C79000–G8976–C129–07


CPU

STEP 7 user program

User data areas

AG_SEND

AG_RECV

Ethernet CP

send receive

Ethernet CP

Connection receive send

CPU

STEP 7 user program

User data areas

AG_RECV

AG_SEND

Note

Unless specifically stated otherwise, the information on this and the following pages refers to AG_SEND / AG_LSEND or AG_RECV / AG_LRECV.

Specifying the Data Area on the CPU

When you call an FC, you transfer the address and length of the data area in the

CPU. Remember, that the maximum length of the data area depends on the block type and block version being used.

S

AG_SEND and AG_RECV

Up to version V3.0 of these blocks, a maximum of 240 bytes could be sent or received. The current block versions allow a data area of up to 8192 bytes for an S7-300. With an S7-400, the FCs AG_LSEND / AG_LRECV must still be used for larger data areas.

S

AG_LSEND / AG_LRECV

Using the CPs of the S7-400 and with earlier versions of the S7-300, larger data areas can only be transferred with the FCs AG_LSEND or AG_LRECV.

Please check the length of the data area in the product information.

The following table shows the limit values of the various connection types.


Release 6/2003

C79000–G8976–C129–07

171


Table 6-1

FC

AG_LSEND

(S7-400)

AG_SEND

(S7-300)

AG_LRECV

(S7-400)

AG_RECV

(S7-300)

ISO Transport

8192 bytes

ISO-on-TCP

8192 bytes

8192 bytes 8192 bytes

TCP

8192 bytes

8192 bytes

UDP

2048 bytes

2048 bytes

Note

For information on the length of the data area you can transfer with older versions of the Ethernet CPs, refer to the product information bulletin / manual of the

Ethernet CP you are using /1/.

Working without the Job Header

On specified connections, the address and job parameters are specified by the connection configuration. The user program only provides the user data in the UDP data area when sending with AG_SEND / AG_LSEND or receives the data with

AG_RECV / AG_LRECV.

172


Release 6/2003

C79000–G8976–C129–07


Working with the Job Header

Free UDP connections require a job header in the user data area.

The following schematic illustrates the structure of the job buffer and the meaning and location of the parameters in the job header.

User data area

Job buffer

Job header

Port

IP address

03

H

(high byte)

8E

H

28

H

Data byte 0

EB

H

(low byte)

0B

H

23

H

Data byte 1

Bytes 0,1

Bytes 2,3

Bytes 4,5

User data

Data byte 2040 Data byte 2041

Figure 6-1 Sending and Receiving on a Free UDP Connection with Programmed Addresses

Bytes 6,7

Bytes

2046,2047

S

In the picture (entries in hexadecimal) the following IP address is assumed:

142.11.40.35 (example only);

S

For the port address 1003, the following would be entered: for high byte: 03

H

; for low byte: EB

H.

S

The user data area can be up to 2048 bytes long. Up to 2042 bytes of user data can be transferred. 6 bytes are reserved for the job header.

Please note that the data length specified in the block call (LEN parameter) must include the header and the user data!


Release 6/2003

C79000–G8976–C129–07

173


6.3.1

FC5 AG_SEND / FC50 AG_LSEND

Meaning of the Block

The FCs AG_SEND / AG_LSEND pass data to the Ethernet CP for transfer over a configured connection.

The selected data area can be a process image area, a memory bit area or a data block area.

Error-free execution of the function is indicated when the entire user data area could be sent on Ethernet.

The way in which the FC functions depends on the CP type you are using. Please note the differences in the following section.

Note:

Unless otherwise stated, all the following information applies to both the FCs

AG_SEND and AG_LSEND.

Call

Call interface in LAD representation

BOOL

INT

WORD

ANY

INT

AG_SEND / AG_LSEND

ACT

ID

LADDR

SEND

LEN

DONE

ERROR

STATUS

BOOL

BOOL

WORD

Example in STL representation

STL call fc 5

ACT :=

ID :=

LADDR :=

SEND

LEN

:=

:=

DONE :=

ERROR :=

STATUS :=

M 10.0

MW 12

W#16#0100

P#db99.dbx10.0 byte 240

MW 14

M 10.1

M 10.2

MW 16

Explanation

//AG_SEND / AG_LSEND block call

//Job triggered by memory bit

//Connection ID acc. to configuration

//=LADDR 256 dec. in hw configuration

//Buffer with send data

//Length for send data

//Execution code

//Error code

//Status code

174


Release 6/2003

C79000–G8976–C129–07


Notice

Please note the following special feature on TCP connections:

With the S7-CPs for S7-400, you must use FC AG_LSEND on TCP connections!

With the latest S7-CPs for S7-300, you must also use FC AG_SEND for TCP connections.

How the Block Works

The following diagrams illustrate the normal sequence of data transmission triggered in the user program using AG_SEND.

The way in which the FC functions depends on the CP type you are using.

S

Case a: Sequence with older CP types

With older CP types, the transfer of the entire data area regardless of its length is started after the first block call by the CP.

S

Case b: Sequence with newer CP types (S7–300 only !)

With the newer CP types, data transfer has been optimized. In particular with longer data records, this allows a much higher data throughput on the interface between the CPU and CP.


Release 6/2003

C79000–G8976–C129–07

175


S


The send job is executed as soon as the parameter ACT = 1 is passed.

Following this, the parameter ACT = 0 must be passed in at least one further call.

The status code in the output parameters DONE, ERROR and STATUS is updated in each block call and can be evaluated. To update the status code without starting a new send job, start a new block call with the parameter ACT =

0.

Refer to the sample program at the end of Section 6.3.1.

User program

(CPU cycle)

Ethernet CP Communications Partner

Supply AG_SEND with data “X”

ACT = 1

AG_SEND

Job active

1)

Supply AG_SEND

ACT = 0

AG_SEND

Job active

1)

AG_SEND

Job completed without error

1)

Time Time

Transfer

“X” active on

Ethernet

Time

Legend:

1) parameter transfer DONE, ERROR, STATUS

176


Release 6/2003

C79000–G8976–C129–07


S


The send job is started as soon as the parameter ACT = 1 is passed.

In contrast to case a, the protocol used here to transfer the data segments

(each 240 bytes of user data) requires the FC to be called again for each segment.

Depending on the length of the user data, you must therefore continue to call the FC with ACT=0 until transfer of the entire data record is indicated; at least one call with ACT=0 is always necessary. The data is transferred to the communication partner in segments of 240 bytes.

The status code in the output parameters DONE, ERROR and STATUS is updated in each block call and can be evaluated.

User program

(CPU cycle)

Ethernet CP

Communications Partner

Supply AG_SEND with data “X”

ACT = 1

AG_SEND

Job active

1)

Supply AG_SEND

ACT = 0

AG_SEND

Job active

1)

Transfer of field 1 active on

Ethernet

Data record X is transferred in segments.

Transfer of field 2 active on

Ethernet

AG_SEND

Job active

1)

Transfer of field n–1 active on Ethernet

AG_SEND

Job active

1)

Transfer of field n active on

AG_SEND

Ethernet

Job completed without error

1)

Time Time

Legend:


Time


Release 6/2003

C79000–G8976–C129–07

177


Note

In principle, it is possible to call the FC more than once within the CPU cycle to speed up the handling of the job. Do not forget, however, that this increases the load during the CPU cycle (the load differs depending on the CPU type)!

Explanation of the Formal Parameters

The following table explains all the formal parameters for the AG_SEND

/AG_LSEND functions.

Parameter Declaration

ACT INPUT

Type

BOOL 0,1

Possible

Values

ID INPUT INT 1,2...64

(S7-400)

1,2...16

(S7-300)

Remarks

If an FC is called with ACT=1, LEN bytes are sent from the ISO transport data area specified with the SEND parameter.

If an FC is called with ACT = 0, the status codes DONE, ERROR and STATUS are updated.

The connection number of the connection is specified in the parameter ID. (see

Configuration Section 4.3.1

LADDR

SEND

INPUT

INPUT

WORD

ANY

Module base address

When you configure the CP with STEP 7 hardware configuration, the module base address is displayed in the configuration table.

Specify this address here.

Specifies the address and length.

The address of the data area refers to one of the following:

– Process image area

– Bit memory

– Data block area

178


Release 6/2003

C79000–G8976–C129–07


Parameter

LEN

Declaration

INPUT

Type

INT

Possible

Values

On ISO

Transport and

ISO-on-TCP /

TCP:

(or up to “length specified for

SEND parameter”)

On UDP:

Remarks

Number of bytes to be sent from the data area with this job. The possible values range from 1 to length specified for the SEND parameter.

S

Note the block type:

– S7-300

With older versions of FC AG_SEND

(up to V3.0), the data area is always restricted to a maximum of 240 bytes.

The current versions allow up to 8192 bytes (2048 bytes for UDP).

up to “length specified for

SEND parameter”)

– S7-400

With FC AG_SEND, the data area is restricted to a maximum of 240 bytes.

S

Note on the S7-400:

Data transfer may be restricted to

LEN<=240 bytes with older versions of the

CP firmware!

For further information, see /1/

S

Improved performance with shorter data records:

Transfer of data records up to 240 bytes results in better performance regardless of the block type used.

DONE

ERROR

STATUS

OUTPUT BOOL 0: Job active

1: done

OUTPUT BOOL 0: –

1: error

OUTPUT WORD see following table

This parameter indicates whether or not the job was completed without errors.

As long as DONE = 0, no further job can be triggered. DONE is set to 0 by the CP when it accepts a new job.

For the meaning of this parameter in conjunction with the ERROR and STATUS parameters, refer to the following table.

For the meaning of this parameter in conjunction with the DONE and STATUS parameters, refer to the follow table.

Status code

The following table shows the condition codes formed by the DONE and ERROR parameters.

Condition Codes

The following table shows the condition codes formed by the DONE, ERROR and

STATUS parameters that must be evaluated by the user program.


Release 6/2003

C79000–G8976–C129–07

179


Note

For entries coded with 8Fxx

H

in STATUS, refer to the information in the STEP 7

Standard and System Functions reference manual. The chapter describing error evaluation with the RET_VAL output parameter contains detailed information.

To find out which SFCs are used and are relevant for error evaluation, display the properties dialog of the FC described here in the “Calls” tab.

Table 6-2 AG_SEND / AG_LSEND Codes

0

0

1

0

DONE ERROR STATUS

0

0

0000

H

0000

H

0

1

8181

H

7000

H

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

1

1

1

1

1

1

1

1

1

1

1

1

1

1

1

1

1

8183

H

8184

H

8185

H

8186

H

8302

H

8304

H

8311

H

8312

H

8F22

H

8F24

H

8F28

H

8F32

H

8F33

H

8F3A

H

8F42

H

8F44

H

8F7F

H

Job completed without error.

No job being executed.

Meaning

Job active.

This code is possible only with the S7-300: the FC was called with ACT=0; the job has not yet been processed.

No configuration or the ISO/TCP service has not yet started on the Ethernet CP.

System error.

LEN parameter longer than SEND source area.

ID parameter invalid. ID!=1,2 to 64.

No receive resources on the destination station; the receiving station cannot process received data quickly enough or has not prepared any receive resources.

The connection is not established. The send job should only be attempted again after waiting for at least 100 ms.

The destination station cannot be obtained under the specified

Ethernet address.

Ethernet error on the CP.

Source area invalid, for example:

Area does not exist in the DB

LEN parameter < 0

Area error reading a parameter.

Alignment error reading a parameter.

Parameter contains a DB number that is too high.

DB number error.

Area not loaded (DB).

Timeout reading a parameter from the I/O area.

Address of the parameter to be read is disabled in the access track.

Internal error, e.g. illegal ANY reference.

e.g. parameter LEN=0

180


Release 6/2003

C79000–G8976–C129–07


Table 6-2 AG_SEND / AG_LSEND Codes

0

0

0

0

0

0

0

0

0

0

0

0

0

DONE

1

1

1

1

1

1

1

1

1

1

1

1

1

ERROR STATUS

8090

H

8091

H

8092

H

80A4

H

80B0

H

80B1

H

80B2

H

80C0

H

80C1

H

80C2

H

80C3

H

80C4

H

80D2

H

Meaning

No module with this address exists or the CPU is in the STOP mode.

Logical base address not at a double word boundary.

In the ANY reference, a type other than BYTE is specified.

(S7-400 only)

The communication bus connection between the CPU and CP is not established. (Only with newer CPU versions)

The module does not recognize the data record.

The specified length (in the LEN parameter) is incorrect.

The communication bus connection between the CPU and CP is not established.

The data record cannot be read.

The specified data record is currently being processed.

There are too many jobs pending.

CPU resources (memory) occupied.

Communication error (occurs temporarily and a repetition in the user program will often remedy the problem).

Module base address incorrect.


Release 6/2003

C79000–G8976–C129–07

181


Example of AG_SEND

Below you will find an executable example of an FC5 (AG_SEND) call and parameter evaluation.

The OB100 listed below belongs to the FC100 selected here in which the send call takes place; OB100 sets the ACT bit correctly when the CPU starts up.

To function correctly, a DB100 with a size of at least 240 bytes must be loaded.

The program requires a CP at address 256 and a configured connection of the type ISO Transport / ISO-on-TCP / TCP with ID=1 (please adapt your configuration where necessary !).

//––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––

FUNCTION FC 100: VOID

TITLE = SENDE_DEMO

AUTHOR : Tester

FAMILY : S7300

NAME : FC5_Demo

VERSION : 1.0

//–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––

BEGIN

CALL FC 5 (

ACT

ID

LADDR

SEND

LEN

DONE

ERROR

STATUS

:= M100.0,

:= 1,

:= W#16#100,

:= P#DB100.dbx0.0 BYTE 240,

:= 240,

:= M100.1,

:= M100.2,

:= MW102 );

//––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––

Reset parameter ACT for all further FC5 calls; R M100.0;

SET;

A M100.1;

JC done;

SET;

A M100.2;

JC err;

//

//

//

//

//

//

//

Test whether DONE = TRUE

Test whether ERROR = TRUE

//––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––

BEU; //

//

Neither DONE nor ERROR is set, the job is still running.

//–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– done S M100.0;

BEU;

//

//

Job completed without error. Set ACT = TRUE so that the next call can trigger the new job.

//–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––

182


Release 6/2003

C79000–G8976–C129–07


err: NOP 1;

NOP 1;

S M100.0;

BEU;

//

//

//

//

An error occurred. The status word can be evaluated here. Set ACT to TRUE in any case, so that a new send job can be triggered if the error disappears.

//–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––

END_FUNCTION

ORGANIZATION_BLOCK OB100

FAMILY: S7300

NAME: SENDE_DEMO_INIT

VERSION: 1.0

VAR_TEMP

OB1_System: array [1..20] of byte;

END_VAR

BEGIN

SET

S M100.0

END_ORGANIZATION_BLOCK

//

//

// Initialize ACT parameter


Release 6/2003

C79000–G8976–C129–07

183


6.3.2

FC6 AG_RECV / FC60 AG_LRECV


The AG_RECV / AG_LRECV function receives the data transferred on a configured connection from the Ethernet CP.

The data area specified for the receive data can be a process image area, a bit address area or a data block area.

Error-free execution is indicated when the data could be received from the

Ethernet CP.

Note:

Unless otherwise stated, all the following information applies to both the FCs

AG_RECV and AG_LRECV.

Call

Call interface in LAD representation

INT

WORD

ANY

AG_RECV / AG_LRECV

ID

LADDR

RECV

NDR

ERROR

STATUS

LEN

BOOL

BOOL

WORD

INT


STL call fc 6

ID :=

LADDR :=

RECV

NDR

:=

:=

ERROR :=

STATUS :=

LEN :=

MW 40

W#16#0100

P#M 0.0 BYTE 100

DB 110.DBX 0.6

DB 110.DBX 0.7

DB 110.DBW 2

DB 110.DBW 4

Explanation

//AG_RECV/AG_LRECV block call


//=LADDR 256 dec. in hardware configuration

//Buffer for received data

//Receive code

//Execution code

//Error code

//Status code

184


Release 6/2003

C79000–G8976–C129–07


Notice

Please note the following special feature on TCP connections:

With the S7-CPs for S7-400, you must use FC AG_LRECV on TCP connections!

With the latest S7-CPs for S7-300, you must also use FC AG_RECV for TCP connections.


The following diagram illustrates the normal sequence of data acceptance triggered by an AG_RECV in the user program.

Each AG_RECV job in the user program is acknowledged by the Ethernet CP with an entry in the output parameters NDR, ERROR and STATUS.

The way in which the FC functions depends on the CP type you are using.

S


With older CP types, the transfer of the entire data area regardless of its length is started after the first block call by the CP.

S


With the newer CP types, optimized data transfer on the SEND/RECEIVE interface is available. In particular with longer data records, this allows a much higher data throughput on the interface between the CPU and CP.


Release 6/2003

C79000–G8976–C129–07

185


S


When the FC is called, the user program prepares the buffer for the received data and instructs the CP to enter the received data there.

As soon as a data record has been entered fully and consistently in the receive buffer, this is indicated by the parameter NDR = 1 in one of the next FC calls.

The status code in the output parameters NDR, ERROR, and STATUS is updated in each block call and can be evaluated.

User program

(CPU cycle)


AG_RECV

There are not yet any data available

1)

AG_RECV

New data accepted

1)

Accept / evaluate received data “A”

AG_RECV


1)

AG_RECV

New data accepted

1)

Accept / evaluate received data “B”

AG_RECV

.

.

.

Transfer

“A” active on

Ethernet

Transfer

“B” active on

Ethernet

Transfer

“C” active on

Ethernet

186

Time

Legend:

1) Parameter transfer NDR, ERROR, STATUS

Time Time


Release 6/2003

C79000–G8976–C129–07


S


When the FC is called, the user program prepares the buffer for the received data and instructs the CP to enter the received data there.

In contrast to case a, the protocol used here to transfer the data to the receive buffer requires the FC to be called again for each data segment (240 bytes of user data).

Depending on the length of the user data, you must therefore continue to call the FC until transfer of the entire data record is indicated by the parameter NDR

= 1.

The status code in the output parameters NDR, ERROR, and STATUS is updated in each block call and can be evaluated.

User program (CPU cycle) Ethernet CP Communications Partner

Data record A is entered segment by segment in the buffer.

AG_RECV


1)

AG_RECV


1)

AG_RECV

New data accepted

1)

Accept / evaluate received data “A”

Data record A is entered in the buffer.

AG_RECV


1)

AG_RECV

New data accepted

1)

Accept / evaluate received data “B”

Data record C is entered segment by segment in the buffer.

AG_RECV

.

.

.

Transfer of ’A’ (e.g. 520 bytes) active on

Ethernet

Transfer of ’A’ (e.g. 240 bytes) active on

Ethernet

Transfer

“C” active on

Ethernet

Time

Legend:

1) Parameter transfer NDR, ERROR, STATUS

Time Time


Release 6/2003

C79000–G8976–C129–07

187



The following table explains all the formal parameters for the AG_RECV /

AG_LRECV function.


ID INPUT

LADDR

RECV

NDR

ERROR

STATUS

INPUT

INPUT

OUTPUT

OUTPUT

OUTPUT

Type

INT

Possible

Values

1,2...64

(S7-400)

1,2...16

(S7-300)

Remarks

The connection number of the ISO transport connection is specified in the ID parameter (see

Configuration Section 4.3.1)

WORD

ANY

BOOL

BOOL

0: –

1: new data

0: –

1: error

WORD see following table

Module base address



Specifies the address and length.

The address of the data area refers to one of the following:

– Process image area

– Bit memory

– Data block area

Note on length:

Performance is improved in transfer of data records up to 212 bytes if you also restrict the length to 212 with the RECV parameter.

This parameter indicates whether new data were received.


Error code

For the meaning of this parameter in conjunction with the DONE and STATUS parameters, refer to the following table.

Status code

For the meaning of this parameter in conjunction with the NDR and ERROR parameters, refer to the following table.

188


Release 6/2003

C79000–G8976–C129–07


Parameter

LEN

Declaration

OUTPUT

Type

INT

Possible

Values

On ISO

Transport and

ISO-on-TCP:

1,2...8192

On UDP:

1,2...2048

Remarks

Specifies the number of bytes accepted from the Ethernet CP and entered in the data area.

S

Note the block type:

– S7-300

With older versions of FC AG_RECV (up to V3.0), the data area is always restricted to a maximum of 240 bytes.

The current versions allow up to 8192 bytes (2048 bytes for UDP).

– S7-400

With FC AG_RECV, the data area is restricted to a maximum of 240 bytes.

Condition Codes

The following table shows the codes formed by the DONE, ERROR and STATUS parameters that must be evaluated by the user program.

Note

For entries coded with 8Fxx

H

in STATUS, refer to the information in the STEP 7

Standard and System Functions reference manual. The chapter describing error evaluation with the RET_VAL output parameter contains detailed information.

To find out which SFCs are used and are relevant for error evaluation, display the properties dialog of the FC described here in the “Calls” tab.

Table 6-3 AG_RECV / AG_LRECV Codes

0

0

0

0

0

1

0

NDR

1

1

1

0

1

0

0

ERROR STATUS

0000

H

8180

H

8181

H

8183

H

8184

H

8185

H

8186

H

Meaning

New data accepted.

There are not yet any data available.

Job active.

No configuration or the ISO transport service has not yet started on the Ethernet CP.

System error (the source data area is incorrect).

Destination buffer (RECV) is too short.

ID parameter invalid.

ID != 1,2....16 (S7-300).

ID != 1,2....64.(S7-400)


Release 6/2003

C79000–G8976–C129–07

189


Table 6-3 AG_RECV / AG_LRECV Codes

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

NDR

1

1

1

1

1

1

1

1

1

1

1

1

1

1

1

1

1

1

1

1

1

1

1

1

1

1

ERROR STATUS

8304

H

8F23

H

8F25

H

8F29

H

8F30

H

8F31

H

8F32

H

8F33

H

8F3A

H

8F43

H

8F45

H

8F7F

H

8090

H

8091

H

8092

H

80A0

H

80A4

H

80B0

H

80B1

H

80B2

H

80C0

H

80C1

H

80C2

H

80C3

H

80C4

H

80D2

H

Meaning

The connection is not established. The send job should only be attempted again after waiting for at least 100 ms.

Source area invalid, for example:

Area does note exist in the DB.

Area error writing a parameter.

Alignment error writing a parameter.

Parameter is in the write-protected first current data block.

Parameter is in the write-protected second current data block.

Parameter contains a DB number that is too high.

DB number error.

Destination area not loaded (DB).

Timeout writing a parameter to the I/O area.


Internal error, e.g. illegal ANY reference.

No module with this address exists or the CPU is in the STOP mode.

Logical base address not at a double word boundary.

In the ANY reference, a type other than BYTE is specified.

(S7-400 only)

Negative acknowledgment reading from the module.


The module does not recognize the data record.

Destination area invalid.


The data record cannot be read.

The specified data record is currently being processed.

There are too many jobs pending.

CPU resources (memory) occupied.

Communication error (occurs temporarily and a repetition in the user program will often remedy the problem).

Module base address incorrect.

190


Release 6/2003

C79000–G8976–C129–07


6.4

FCs for Access Coordination with FETCH/WRITE

Overview

The following FCs are available for FETCH/WRITE function to coordinate access:

FC

AG_LOCK (FC7)

AG_UNLOCK (FC8) can be used with:

S7 – 300 S7 - 400

x x x x

Meaning

Locks external data access with FETCH/WRITE.

Releases external data access with FETCH/WRITE.

Caution when Configuring

If you use FCs AG_LOCK and AG_UNLOCK, you must specify the following information for S7-400 stations in the configuration:

S in HW Config

In the “Addresses” tab, the option “Address setting for LOCK/UNLOCK” must be selected.


With these FCs, you can coordinate access to system memory areas so that no inconsistent data are created and transferred. The control is from the user program in the S7 CPU that can, if necessary disable an external FETCH/WRITE access using an AG_LOCK call. After a certain time or after the local write/read access is completed, an AG_UNLOCK job can be used to enable external access again.

Another advantages is that this access lock only applies to the FETCH/WRITE connection specified in the call. If more than one FETCH/WRITE connections are configured, these can, for example, be used for certain specific system areas and a selective access coordination can be implemented.

The following diagram illustrates the usual chronological sequence of memory access coordination controlled in the user program with AG_LOCK and

AG_UNLOCK.


Release 6/2003

C79000–G8976–C129–07

191


Cycle n

Cycle n+1

Cycle n+2

Cycle n+m

...

User program

(CPU cycle)

AG_LOCK

LOCKED = 0

AG_LOCK

LOCKED = 0


FETCH/WRITE access to DB x active

AG_LOCK

LOCKED = 1

FETCH/WRITE

FETCH/WRITE rejected

Data processing in DB x

AG_UNLOCK

STATUS = 700x

FETCH/WRITE access to DB x active

192

Time Time Time

The lock job must first be monitored in the user program using the code in the return parameter LOCKED. As long as LOCKED=0 is indicated, it must be assumed that there is still a FETCH/WRITE access active.

If LOCKED=1 is indicated, this shows that the lock is active; data can now be modified by the user program.

The status code is updated at each block call.


Release 6/2003

C79000–G8976–C129–07


6.4.1

FC7 AG_LOCK


Using the AG_LOCK block the data exchange using FETCH or WRITE on the connection selected with the parameter ID is disabled. The LOCKED output indicates whether or not the lock was successful. If the lock was not successful, the job must be triggered again in a later CPU cycle.

The STATUS output indicates the status of the CP for this connection.

Call

Representation of the AG_LOCK Function

AG_LOCK

ID

LADDR

STATUS

LOCKED


STL call fc 7

ID :=

LADDR :=

STATUS :=

LOCKED :=

DB 100.DBW 2

W#16#0100

DB 100.DBW 4

DB 100.DBX 0.6

Explanation

//Block call



//Status code

//Status code of access disable


The following table explains all the formal parameters for the AG_LOCK function:


Release 6/2003

C79000–G8976–C129–07

193



ID INPUT

LADDR

LOCKED

STATUS

INPUT

OUTPUT

OUTPUT

Type

INT

Possible

Values

1,2...16 for

S7-300

1,2...64 for

S7-400

Remarks



WORD

BOOL 0: not (yet) locked

1: locked


Module base address



Shows the status of the access lock requested on the specified FETCH/WRITE connection.

Status code

For meaning, refer to the table below.

Condition Codes

The following table shows the STATUS code that must be evaluated by the user program.

Table 6-4 AG_LOCK Condition Codes

STATUS

7000

7001

7002

8183

8186

Meaning

CP is not processing a job

FETCH active

WRITE active

FETCH/WRITE not configured for this connection

ID number not in permitted range (e.g. 1...64 with S7-400 Industrial Ethernet CPs)

194


Release 6/2003

C79000–G8976–C129–07


6.4.2

FC8 AG_UNLOCK


Using the AG_UNLOCK function, the external access to system areas on the S7

CPU with FETCH or WRITE on the connection specified by the ID parameter is released.

The next external FETCH/WRITE job to arrive for the CP can then be processed.

The AG_UNLOCK follows an access lock with AG_LOCK.

Call

Representation of the AG_UNLOCK Function

AG_UNLOCK

ID

LADDR

STATUS


STL call fc 8

ID :=

LADDR :=

STATUS :=

DB 100.DBW 2

W#16#0100

DB 100.DBW 4

Explanation

//Block call



//Status code


To release the connection again, the LOCK request bit must be reset by the FC again. The FC also shows the current status using error messages.


The following table explains all the formal parameters for the AG_UNLOCK function:


Release 6/2003

C79000–G8976–C129–07

195



ID INPUT

LADDR

STATUS

INPUT

OUTPUT

Type

INT

Possible

Values

1,2...16 for

S7-300

1,2...64 for

S7-400

Remarks



WORD


Module base address



Status code

For meaning, refer to the table below.

Condition Codes

The following table shows the STATUS code that must be evaluated by the user program.

Table 6-5 AG_UNLOCK Condition Codes

STATUS

7000

7001

7002

8183

8186

Meaning

CP is not processing a job

FETCH active

WRITE active

FETCH/WRITE not configured for this connection

ID number not in permitted range (e.g. 1...64 with S7-400 Industrial Ethernet CPs)

196


Release 6/2003

C79000–G8976–C129–07


6.5

FB55 IP_CONFIG for Programmed Communication

Connections


Connections can be specified in a DB (configuration DB) and transferred to the CP with an FB.

You can use this variant of programmed communication connections as an alternative to connection configuration with STEP 7.

Depending on the size of the configuration DB, the data may be transferred to the

CP in several segments. This means that the FB must continue to be called until the FB signals complete transfer by setting the DONE bit to 1.

Call

Representation ...

INT

WORD

ANY

INT

IP_CONFIG

ACT

LADDR

DONE

ERROR

CONF_DB

LEN

STATUS

EXT_STATUS

BOOL

BOOL

WORD

WORD


STL call fb 55

ACT :=

LADDR :=

CONF_DB :=

M 10.0

W#16#0100

P#db99.dbx10.0 byte 240

LEN

DONE

:=

:=

ERROR :=

STATUS :=

MW 14

M 10.1

M 10.2

MW 16

EXT_STATUS := MW 18

Explanation

//IP_CONFIG block call

//Job triggered by memory bit<


//Data block with connection data

//Length info for connection data

//Executed code

//Error code

//Status code

//Cause of error in connection data


Release 6/2003

C79000–G8976–C129–07

197


How It Works

The following diagram illustrates the normal sequence of connection configuration triggered by an IP_CONFIG in the user program.

The job executes as soon as the parameter ACT is transferred with value 1.

Due to the segmented transfer of the CONF_DB, you must repeat the job with

ACT = 1 until completion of the job is indicated in the parameters

DONE, ERROR, and STATUS.

If you want to transfer a connection configuration again later, the parameter ACT must first be transferred with value 0 in at least one further call.

Please refer to the sample program in the appendix.

User program

(CPU cycle)

Ethernet CP

Supply CONF_DB with data

Set ACT = 1

Call IP_CONFIG

Job active

1)

CONF_DB is transferred in segments.

Call IP_CONFIG

Job active

1)

S

CP is supplied with system data

(including the IP address);

S

Connections are configured on the

CP.

Set ACT = 0

Time

Call IP_CONFIG

Job completed without errors

1)

Time

Legend:


Notice

The data transferred with the configuration DB are stored in volatile memory on the CP and must be downloaded to the CP again following a power down!

198


Release 6/2003

C79000–G8976–C129–07



The following table explains the formal parameters for the call interface of the

IP_CONFIG function block :


ACT INPUT

Type

BOOL 0,1

Possible

Values

LADDR

CONF_DB INPUT

LEN

DONE

INPUT

OUTPUT

ERROR

STATUS

INPUT

OUTPUT

OUTPUT

EXT_Status OUTPUT

Remarks

WORD

ANY

INT

BOOL 0: –

1: new data

BOOL 0: –

1: error


WORD

When the FB is called with ACT = 1, the DBxx is sent to the CP.

If the FB is called with ACT = 0, only the status codes DONE, ERROR and STATUS are updated.

Module base address



The parameter points to the start address of the configuration data area in a data block

Length information in bytes for the configuration data area.

The parameter indicates whether the configuration data area was completely transferred.

Remember that it may be necessary to call the

FB several times depending on the size of the configuration data area (in several cycles) until the DONE parameter is set to 1 to signal completion of the transfer.


Error code

For the meaning of this parameter in conjunction with the NDR and STATUS parameters, refer to the following table.

Status code

For the meaning of this parameter in conjunction with the NDR and ERROR parameters, refer to the following table.

If an error occurs in the execution of a job, the parameter indicates which parameter was detected as the cause of the error in the configuration DB.

High byte: Index of the parameter field

Low byte: Index of the subfield within the parameter field


Release 6/2003

C79000–G8976–C129–07

199


Condition Codes

The following table shows the condition codes formed by the DONE, ERROR and

STATUS parameters that must be evaluated by the user program.

Table 6-6 Condition Codes for FB55 IP_CONFIG


General codes relating to job execution

1 0 0000

H

Job completed without errors

Meaning

0 0 8181

H

Job active

Errors detected on the interface between CPU and CP.

0

0

0

1

1

1

80B1

80C4

8187

H

H

H

The amount of data to be sent exceeds the upper limit permitted for this service. (upper limit = 16 Kbytes)

Communication error

The error can occur temporarily; it is usually best to repeat the job in the user program.

0

0

0 1 80D2

H

Configuration error

The module you are using does not support this service.

Errors detected in the evaluation of the FB in the CPU or on the interface between CPU and CP.

0

1

1

1

8183

8184

8185

H

H

H

The CP rejects the requested data record number.

System error or illegal parameter type<F 9>. (data type of the ANY pointers CONF_DB not OK)

(Currently only the byte data type is accepted)

The value of the LEN parameter is larger than the CONF_DB less the reserved header (4 bytes) or the length information is incorrect.

0 1 8186

H

Illegal parameter detected

The ANY pointer CONF_DB does not point to a data block.

Illegal status of the FB

Data in the header of CONF_DB was possibly overwritten.

or:

The instance DB does not exist.

Further errors detected on the interface between the CPU and CP.

0 1 8A01

H

The status code in the data record is invalid (value is >= 3).

0 1 8A02

H

0 1 8A03

H

There is no job running on the CP; the FB, however, expected an acknowledgment for a completed job.

There is no job running on the CP and the CP is not ready; the FB triggered the first job to read a data record.

0

0

0

1

1

1

8A04

H

8A05

8A06

H

H

There is no job running on the CP and the CP is not ready; the FB nevertheless expected an acknowledgment for a completed job.

There is a job running, but there was no acknowledgment; the FB nevertheless triggered the first job for a read data record job.

A job is complete but the FB nevertheless triggered the first job for a read data record job.

200


Release 6/2003

C79000–G8976–C129–07


Table 6-6 Condition Codes for FB55 IP_CONFIG, continued


Errors detected when evaluating the FB on the CP.

0 1 8B01

H

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

1

1

1

1

1

1

1

1

1

1

1

1

1

1

1

1

1

1

8B02

H

8B03

H

8B04

H

8B05

H

8B06

H

8B07

H

8B08

H

8B09

H

8B0A

H

8B0B

H

8B0C

H

8B0D

H

8B0E

H

8B0F

H

8B10

8B11

8B12

8B13

Meaning

Communication error

The DB could not be transferred

Parameter error

Double parameter field

Parameter error

The subfield in the parameter field is not permitted.

Parameter error

The length specified in the FB does not match the length of the parameter fields / subfields.

Parameter error

The length of the parameter field is invalid.

Parameter error

The length of the subfield is invalid.

Parameter error

The ID of the parameter field is invalid.

Parameter error

The ID of the subfield is invalid.

System error

The connection does not exist

Data error

The content of the subfield is not correct.

Structure error

A subfield exists twice.

Data error

The parameter does not contain all the necessary parameters.

Data error

The CONF_DB does not contain a parameter field for system data.

Data error / structure error

The CONF_DB type is invalid.

System error

The CP does not have enough resources to process CONF_DB completely.

Data error

Configuration by the user program is not set.

Data error

The specified type of the parameter field is invalid.

Data error

Too many connections were specified (either in total or too many for a specific type; for example, only one E-mail connection is possible).

CP-internal error

Further errors detected on the program interfaces within the CPU (SFC errors).


Release 6/2003

C79000–G8976–C129–07

201


Table 6-6 Condition Codes for FB55 IP_CONFIG, continued

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

DONE

1

1

1

1

1

1

1

1

1

1

1

1

1

1

1

1

ERROR STATUS

8F22

H

8F31

H

8F32

H

8F33

H

8F3A

H

8F42

H

8F43

H

8F44

H

8F45

H

8F7F

H

8F23

H

8F24

H

8F25

H

8F28

H

8F29

H

8F30

H

Meaning

Area length error reading a parameter (e.g. DB too short).

Area length error writing a parameter (e.g. DB too short).

Area error reading a parameter.

Area error writing a parameter.

Alignment error reading a parameter.

Alignment error writing a parameter.

The parameter is in the write-protected first current data block.

The parameter is in the write-protected second current data block.

The parameter contains a DB number that is too high.

DB number error

The target area was not loaded (DB).

Timeout reading a parameter from the I/O area.

Timeout writing a parameter to the I/O area.


Address of the parameter to be written is disabled in the access track.

Internal error

For example, an illegal ANY reference was detected.

202


Release 6/2003

C79000–G8976–C129–07


6.6

Numeric Data / Resource Requirements of the FCs

Notice

Please note the version information of the blocks. Blocks with other versions have different resource requirements.

Table 6-7 Information for FCs with an S7-400

NAME Version FC no.

AG_SEND

AG_RECV

AG_LOCK

AG_UNLOCK

AG_LSEND

AG_LRECV

1.1

1.1

1.0

1.0

3.0

3.0

5

6

7

8

50

60

Load memory bytes

732

656

272

256

1044

1190

Table 6-8 Information for FCs / FBs with an S7-300

NAME Version FC no.

AG_SEND

AG_RECV

AG_LOCK

AG_UNLOCK

IP_CONFIG

4.1

4.5

4.0

4.0

1.0

5

6

7

8

55

Load memory bytes

1916

1408

748

712

2062

Work memory bytes

1610

1174

636

604

1694

Work memory bytes

576

522

200

186

846

992

MC7

Bytes

540

486

164

150

810

956

Local data

Bytes

MC7

Bytes

1574

1138

600

568

1648

Local data

Bytes

50

40

34

32

52

20

20

6

6

52

58


Release 6/2003

C79000–G8976–C129–07

203


-

204


Release 6/2003

C79000–G8976–C129–07

NCM S7 Diagnostics

7

The NCM S7 Diagnostics described here provides dynamic information on the operating state of the communication functions of online CPs.

This chapter provides a general overview of the individual diagnostic functions.

The following checklist will help you to recognize several typical problems and their possible causes and shows how you can use the NCM S7 for PROFIBUS diagnostics tool to remedy the situation.

Further information is available from the following sources:

S

When you are working with the diagnostic tool, the integrated help system provides you with context-related support.

S

You will find detailed information on working with STEP 7 programs in the Help on STEP 7, which includes the topic “Diagnosing Hardware”

Note

NCM S7 Diagnostics supports not only diagnostics for CPs (communication modules) but also other module types such as the IE/PB Link. In this chapter, the term CP is therefore synonymous with all modules with which you can run NCM

S7 diagnostic functions.


Release 6/2003

C79000–G8976–C129–07

205

NCM S7 Diagnostics

7.1

Overview

Diagnostic Options in STEP 7

STEP 7 provides you with a graded concept allowing you to query information about the status of your SIMATIC S7 components and functions and to sort out problems in a variety of different situations. These options cover the following:

S

Hardware Diagnostics and Troubleshooting with STEP 7

Hardware diagnostics provides dynamic information on the operating mode of modules including CPs when the S7 station is online.

You can recognize the existence of diagnostic information for a module by the diagnostics icon in the project window of the SIMATIC Manager. Diagnostic icons show the status of the corresponding module and also the operating mode of CPUs.

Detailed diagnostic information is displayed in the “module information” that you can open by double-clicking a diagnostic icon in the quick view or the diagnostic view.

S

Communication Diagnostics with NCM S7 Diagnostics

The NCM S7 Diagnostics described here provides dynamic information on the operating state of the communication functions of online CPs or modules.

S

HW Config Provides Static Information

Static information means the configured communication properties of an online or offline CP and you can display this at any time using the hardware configuration shown by HW Config.

What You Should Already Know

You should be familiar with the basic information in Chapter 2 on the significance of

NCM 7 and working with it. This means that you know how to connect the Ethernet

CP to the PG and how to control the module using the PG.

Where to Find Further Information

Further information is available from the following sources:

S

Information about the communication services is available in the appropriate chapters in this manual.

S

When you are working with the diagnostic tool, the integrated help system provides you with context-related support.

S

You will find detailed information on working with STEP 7 programs in the Help on STEP 7, which includes the topic “Diagnosing Hardware”.

206


Release 6/2003

C79000–G8976–C129–07


7.2

Functions of NCM S7 Diagnostics

Functions

The diagnostic functions can be grouped as follows:

S

General diagnostic and statistical functions

S

Type and mode-dependent diagnostic functions

General diagnostic and statistical functions

Regardless of the configured mode of the Ethernet CP, the following diagnostic functions are possible:

S

Querying the operating mode on Ethernet

S

Querying the event messages recorded on the Ethernet CP (diagnostic buffer)

Mode-Dependent Functions

Depending on the configured mode of the Ethernet CP, the following diagnostic functions are possible:

S

Diagnostics of ISO transport connections

S

Diagnostics of ISO-on-TCP connections

S

Diagnostics of TCP connections

S

Diagnostics of UDP connections

S

Diagnostics of E-mail connections

S

Diagnostics of TCP connections for PROFInet


Release 6/2003

C79000–G8976–C129–07

207


7.2.1

Installing and Starting NCM S7 Diagnostics

Installation

NCM S7 Diagnostics is an integrated component of the NCM S7 for Industrial

Ethernet optional package.

NCM S7 Ethernet Diagnostics is installed along with NCM S7 for Ethernet on your

PG.

There are several ways in which you can start the diagnostic tool:

Alternative 1

S

From the standard Start menu of Windows (program group SIMA-

TIC " ...

" NCM).

Use this method if the STEP 7 project in which the CP was configured is not available on your PG (for service purposes).

Alternative 2

S

From the Properties dialog of the CP within your STEP 7 project.

208


Release 6/2003

C79000–G8976–C129–07


Structure

In the same way, for example, as the SIMATIC Manager, NCM S7 Diagnostics appears as a separate two-part application window with a menu and toolbar:

Navigation area with diagnostic objects

Content area with the diagnostic result

S

In the navigation area on the left-hand side, you will find the hierarchically arranged diagnostic objects.

You have an overview of the available diagnostic functions at all times. The object structure displayed in the navigation area is adapted to the type of CP you are currently checking and the functions and connections configured for the

CP.

S

In the content area, on the right-hand side, you will see the result of the diagnostic function you selected in the navigation area.

Operation

S

By selecting a diagnostic object in the navigation area with the mouse, you execute the diagnostic function.

S

Using the menu bar and toolbar, you control the sequence of the diagnostics with context-sensitive menu commands.


Release 6/2003

C79000–G8976–C129–07

209


7.2.2

General Menu Commands

Overview

When running diagnostic functions, the following menu commands have general significance. Depending on the context, other functions may be available; for more detailed information refer to the online help for NCM Diagnostics.

Table 7-1 Meaning of the Menu Commands

Menu

Diagnostics

"

Open Online Connection...

Diagnostics

"

Close Online Connection...

Operating Mode

"

Stop a module

Start a module

Reset module memory

Resetting to factory settings

View

"

Update

View

"

Update Cyclically

Meaning

With this menu command, you can establish a connection to a different CP you want to check without having to quit and restart the diagnostic tool. The current diagnostic connection is closed.

If you want to use more than one diagnostic connection at the same time, you can start NCM S7 diagnostics more than once.

You can control the CP as follows:

Stops the CP.

Starts the CP if the RUN/STOP switch is set to RUN.

With certain CP types, for example the CP 443-1, you can reset the CP memory. This function must be confirmed before it is executed.

Following this memory reset, the CP retains the preset MAC address and the retentive parameters. The CP is therefore immediately ready for downloads.

The retentive parameters include:

S

IP address and IP parameters

S

A newly set MAC address

S

LAN settings

With some modules, it is possible to reset to the factory settings.

When you reset to the factory settings, the retentive parameters are also deleted. After this, the module retains only the factory-set MAC address (as shipped).

Each time you activate this menu command, the displayed diagnostic and status information is updated once.

Using this menu command, you activate and deactivate the automatic

(cyclic off) updating of the displayed diagnostic and status information.

You can set the interval between update points with the menu command

Options

"

Customize.

210


Release 6/2003

C79000–G8976–C129–07


Table 7-1 Meaning of the Menu Commands

Menu

Options

"

Customize

Help

"

Meaning

With this menu command, you set the general parameters for the diagnostic session.

On Ethernet:

S

Dialog update time

This sets the interval at which the diagnostic data are updated in a contents area when cyclic updating is selected.

You can obtain help about the current diagnostic function As an alternative, you can also press the F1 key.

Remember that you can also call up context-related help for some of the diagnostic functions. To obtain help, position the cursor on the output field and press the F1 key.

Note

If the connection to the CP is terminated during the diagnostic session, the following message is displayed: “The online connection was terminated”.

You can reestablish the connection to the CP with the corresponding acknowledgment in the dialog. The connection is then automatically reestablished whenever possible.


Release 6/2003

C79000–G8976–C129–07

211


7.3

Starting Diagnostics

7.3.1

Establishing a Connection to the Ethernet CP


Establish the physical connection between the PG and the SIMATIC S7 Station.

There are two ways of doing this:

S

MPI

S

Industrial Ethernet (ISO protocol)

S

Industrial Ethernet TCP/IP (IP protocol)

S

PROFIBUS

Ways of Starting Diagnostics

You can start NCM Diagnostics from the following STEP 7 functions or dialogs:

S

CP properties dialog

S

Windows Start menu

S

Connections properties dialog (NetPro)

S

Hardware configuration HW Config

These possibilities are described below.

7.3.2

Starting Diagnostics from the CP Properties Dialog

If the project data are available on your PG/PC, follow the steps outlined below:

1. Select the S7 station in the project and open the hardware configuration (HW

Config).

2. Select the CP and open the Properties dialog.

3. Select the “Diagnostics” dialog.

4. Select the “Run” button.

Result:

NCM S7 Diagnostics is opened. The path is set automatically to match the current connection in STEP 7.

212


Release 6/2003

C79000–G8976–C129–07


7.3.3

Starting Diagnostics from the Windows Start Menu

If there are no configuration data on your PG/PC, follow the steps outlined below to start diagnostics with a connected CP:

1. Open the Windows Start menu and select the command SIMATIC "

STEP 7

"

Diagnostics

NCM S7 Diagnostics is started with the message “No online connection to the

CP” in the contents area.

2. In the displayed dialog “NCM S7 Diagnostics”, select the interface to match your hardware configuration.

Depending on the type of network attachment you have, you will be prompted to specify an address:

Table 7-2 Possible Settings for the Online Paths – without Parameters for Internetworking

Attachment on

Destination Station

MPI

PROFIBUS

Industrial Ethernet

Industrial Ethernet

TCP/IP

Node Address

MPI address of the CP if this has its own MPI address.

Otherwise specify the MPI address of the CPU.

PROFIBUS address of the

PROFIBUS CP via which the S7 station is reached.

MAC address of the Ethernet CP via which the S7 station is reached.

Entered in hexadecimal.

IP address of the Industrial Ethernet

CP via which the S7 station is reached.

Entered in decimal.

Example:

IP address decimal 142.120.9.134

Location of the Module

Rack / Slot

Rack/slot no. of the CP to be checked.

If you specify the MPI address of the

CP, you can simply use the default setting “0/0”.

With this setting, the CP whose address was specified as the node address is accessed.



If you specify “0/0”, the CP specified with the node address is accessed directly.


If you specify “0/0”, the CP specified with the node address is accessed directly.


Release 6/2003

C79000–G8976–C129–07

213


Examples of an Online Path without Gateway

Rack / slot : 0/4

PG/PC

S7 – 300

CP

U

CP

Node address (MAC):

08-00-06-01-02-03

Attachment of target station: Industrial Ethernet

Figure 7-1 CP requiring diagnostics can be reached directly

Rack / slot : 0/5

PG/PC S7 – 300

CP

U

C

P

C

P

Attachment of target station: Industrial Ethernet

Node address (MAC):

08-00-06-01-02-03

Network 2

Figure 7-2 The CP requiring diagnostics is accessible indirectly over another CP

214


Release 6/2003

C79000–G8976–C129–07


7.3.4

Using a Gateway

Case a: One gateway

If the CP you want to check with diagnostic functions can only be reached via a gateway, you must select the device and specify its node address in the local network.

You must also specify the S7 subnet ID of the destination network:

The subnet ID consists of two numbers separated by a dash:

– One number for the project

– One number for the subnet

You will find the subnet ID in the object properties of the subnet in the STEP 7 project. The subnet ID is also printed out with the network configuration.

PG/PC

Node address (gateway) (MAC):

08-00-06-01-02-03

S7 – 300

CP

U

C

P

C

P

S7 – 300

CP

U

C

P

Rack / slot : 0/5

Node address: PRO-

FIBUS address 9

Attachment of gateway:


S7 subnet ID of target network:

0001 0001

Attachment of target station : MPI/PROFIBUS/AUTO

Figure 7-3 Example of the Parameter Settings for the Online Path with one Gateway


Release 6/2003

C79000–G8976–C129–07

215


Case b: Several Gateways

If the CP requiring diagnostics can only be reached over several gateways, you only specify the first gateway.

Routing over the other gateways is done automatically.

PG/PC

Node address (gateway) (MAC):

08-00-06-01-02-03

S7 – 300

CP

U

C

P

C

P

Rack / slot : 0/5

Attachment of gateway:


Routing over other gateways is done automatically !

S7 – 300

CP

U

C

P

Node address:

PROFIBUS address 9

Attachment of target station: MPI/PROFIBUS/AUTO


0001 0001

Figure 7-4 Example of the Parameter Settings for the Online Path with Several Gateways

216


Release 6/2003

C79000–G8976–C129–07


7.3.5

Using the PC Station – Setting a Gateway with “PC internal”

There is a special situation when you use your PC/PG as a PC station and have therefore set the interface to PC internal (local) in “Setting the PG/PC Interface”.

You must them set parameter values for the gateway, even when you do not need to go through any other gateway to reach the target station.

Select the following settings:

S

Gateway attachment: MPI/PROFIBUS/AUTO

S

Node address (gateway)

Enter the index of the module here.

The index is the virtual slot address of the component (can be displayed using the Station Configuration Editor). The index is identical to the slot number selected during configuration of the PC station in STEP 7 HW Config!

S

S7 subnet ID of destination network:

Follow the same steps as described for setting the gateway.

Tip:

You do not need to make these settings for the gateway if you select one of the following options:

S

Start NCM Diagnostics from the Properties dialog of the CP.

S

When setting up your module, do not select the interface as PC internal (local) in “Set PG/PC Interface”.

Node address (gateway) : 2

(here, the index of the module!)

PC station

OPC serv er

CP

S7 – 300

CP

U

CP

Rack / slot : 0/4

Node address: PROFIBUS address 12

Gateway attachment:

MPI/PROFIBUS/AUTO


0001 0001

Figure 7-5 Example of Settings with “PC internal”

Attachment of target station : MPI/PROFIBUS/AUTO


Release 6/2003

C79000–G8976–C129–07

217


7.3.6

Other Ways of Starting Diagnostics

Starting in the properties dialog of the connections:

1. Select the PLC " Activate Connection Status menu command to activate online access.

2. Select the “Special Diagnostics” button in the “Status Information” tab.

Starting in the hardware configuration tool HW Config:

1. With the S7 station online, select the PLC " Module Status menu command;

2. Select the “Special Diagnostics” button in the dialog that is opened.

Note

To operate several diagnostic connections at the same time, you can start NCM

S7 Diagnostics more than once.

You can also start NCM S7 Diagnostics twice with an online connection to the same CP; this can, for example, be useful if you want to monitor the diagnostic buffer at the same time as running diagnostic functions on a connection.

Requirement: You have an online connection available via the LAN (ISO or

TCP/IP) on the one hand and an online connection via the communication (K) bus on the other (alternatively via the CPU or via PG channel routing via a further CP).

218


Release 6/2003

C79000–G8976–C129–07


7.4

How to Use Diagnostics

Procedure

To use diagnostics efficiently, particularly when working with the diagnostic tool for the first time, the following procedure can be recommended.

1. Use the sequence shown below as a basis for using diagnostics:

Start NCM S7 Diagnostics:

– Establish the connection to the CP (Section 7.3

– Set the options (Section 7.2.2)

– Identify the Ethernet CP

Query the current status of the CP

“Operating Mode” diagnostic object

If the CP is not in the RUN mode

If the CP is in the RUN mode

TCP connections

ISO transport connections/

ISO-on-TCP connections

UDP connections

If anything unusual is displayed for

– connection status

– receive status,

– send status

View / evaluate the diagnostic buffer to obtain an overview and detailed explanation of diagnostic events.

If necessary, correct configuration or programming.

2. Clarify your problem or task using the check list in Section 7.6 and select the diagnostic function based on the recommendation there.


Release 6/2003

C79000–G8976–C129–07

219


7.5

Starting Diagnostic Functions Explicitly

The following table shows the diagnostic options that exist in the available functions.

Table 7-3 General Diagnostic and Statistical Functions

Diagnostic

Functions /

Diagnostic Object

CP information

Mode

Diagnostic Aims

The aim is to identify the CP to which

NCM S7 Diagnostics is connected and to find out the current mode.

Here, the aim is to find out the current operating mode of the Ethernet CP as a module in the S7-300/400 and as a node on Industrial Ethernet and, if necessary, to modify the mode (menu command

Operating Mode

"

Stop Module / Start

Module / Reset Memory / Reset to

Factory Settings).

Diagnostic buffer General error diagnostics using diagnostic buffers

To display and decode event messages recorded on the CP in detail. The diagnostic buffer provides you with detailed information about all the communication services of the CP.

Special Features

Event messages are recorded on the CP in a ring buffer. The ring buffer can contain up to 50 entries.

In NCM S7, on the other hand, up to 500 messages can be saved!

All the CP functions can generate event messages. When you call the diagnostic object, the messages are read out and displayed. The latest message is displayed in the top line with the highest consecutive number.

If you double-click a previously selected event message, you display a help text explaining the message in greater detail.

220


Release 6/2003

C79000–G8976–C129–07


Table 7-4 Mode-Dependent Functions

Diagnostic

Functions /

Diagnostic Object

Diagnostic Aims Special Features

To display and monitor communication connections. You obtain an overview or detailed information in the contents area depending on the diagnostic object you select.

Connections

S

Overview of All Connection Types

Used

Connections

"

Type

Connections

"

Type

"

Type-connection-n

S

Overview of all the communication connections of a particular type, for example all TCP connections;

S

Information on the connection status

S

Detailed information about the status of a communication connection.

By double-clicking the objects in the contents area, you can display detailed information.


Release 6/2003

C79000–G8976–C129–07

221


7.6

Checklist for “Typical Problems” in a System

Meaning

The following lists contain several typical problems and their possible causes and how you can use the NCM S7 Ethernet Diagnostics tool to remedy the situation.

The checklists deal with the following topics:

1. Checklist for General CP Functions

2. Communication Connections Checklist

Note

In the column “Identifying the Cause and Remedy”, you will see the diagnostic function recommended for dealing with the problem shown in bold face.

222


Release 6/2003

C79000–G8976–C129–07


7.6.1

Checklist for General CP Functions

Table 7-5 Checklist for Typical Problems When Operating a CP in a System

Problem

The Ethernet CP will not change to the RUN mode.

Possible Cause

Invalid configuration loaded on the Ethernet

CP.

Switch set to STOP on the

Ethernet CP.

Identifying the Cause and Remedy

Yellow STOP LED and red SF LED lit continuously.

Call up the diagnostic buffer in NCM S7

Ethernet Diagnostics.

Example of an entry

CP STOP due to invalid CP parameter assignment

What to do:

Correct the configuration of the Ethernet CP.

Query the operating mode in NCM S7

Diagnostics.

Operating mode: STOP, Cause: switch set to

STOP

What to do:

Change the switch to RUN on the Ethernet CP


Release 6/2003

C79000–G8976–C129–07

223


7.6.2

Communication Connections Checklist

Table 7-6 Checklist for Typical Problems with ISO Transport / ISO-on-TCP / UDP Connections

Problem

No data transfer on an

ISO transport connection

/

ISO-on-TCP connection or only in one direction.

Data transfer too slow

Possible Cause

AG-SEND and AG-RECV are not called in the user program.

or

Receive or send buffer too small or incorrect.

Identifying the Cause and Remedy

Check the user program.

Evaluate status bytes in AG-SEND and

AG-RECV.

What to do:

If necessary, configure FC blocks.

If necessary, correct ANY pointer.

The connection is not established.

Evaluate status bytes of the FC blocks or evaluate diagnostic buffer.

What to do:

Change the address parameters (MAC/IP address, TSAP).

Receiving device too slow

Evaluate diagnostic buffer.

Entry: “No receive resources on destination station XX”.

What to do:

Delay the send trigger or check the destination station and optimize reception.

LEN parameter for

AG-SEND is set to the wrong value.

What to do:

Set the LEN parameter to the required size.

The complete data field is not sent on an ISO transport /

ISO-on-TCP/UDP connection.

The complete data field is not sent on an ISO transport /

ISO-on-TCP/UDP connection.

The buffer specified with the ANY pointer is too small.

What to do:

Correct the LEN parameter and the ANY pointer.

-

224


Release 6/2003

C79000–G8976–C129–07

Firmware Loader

8

This chapter will familiarize you with the uses and handling of the Firmware

Loader.

The Firmware Loader allows you to download more recent firmware versions to the

SIMATIC NET modules.

For more detailed information on the various load options, refer to the integrated help.


Release 6/2003

C79000–G8976–C129–07

225

Firmware Loader

8.1

Application

Firmware

Here, firmware means the system programs in the SIMATIC NET modules.

Uses of the Firmware Loader

The Firmware Loader allows you to download more recent firmware versions to the

SIMATIC NET modules. It is used on the following:

S

PROFIBUS modules

S

Industrial Ethernet modules

S

Modules for Gateways (for example, IE/PB Link)

Installation

The firmware loader is available when you have installed NCM S7 on your PG/PC.

Load Files

The Firmware Loader supports the following file types:

S

<file>.FWL

A file form that contains information that can be displayed in the dialogs of the

Firmware Loader in addition to the LAD file form.

S

<file>.LAD

A file format containing only the system program that can be downloaded to the module.

For detailed information, read the documentation, for example, the README file shipped with the load file.

This information is displayed even after reading in the FWL file into the firmware loader.

Working with the Firmware Loader

Depending on the module type, the downloading is prepared and executed in three or four steps.

For more detailed information, refer to the next section and the dialog boxes themselves.

226


Release 6/2003

C79000–G8976–C129–07

Firmware Loader

8.2

Loading Firmware

Starting the Download

Open the Windows Start menu and select the menu command SIMATIC "

STEP 7

"

NCM S7 Industrial Ethernet

"

Firmware Loader.

!

Select the Next button and follow the instructions displayed in the dialog box.

Caution

Make sure that the load file you are using is intended as an update for the version of the firmware contained on your module. If you are in any doubt, contact your local Siemens advisor.

!

Caution

Remember that interrupting the download can lead to an inconsistent state on the module!

For more detailed information on the various load options, refer to the integrated help.


Release 6/2003

C79000–G8976–C129–07

227

Firmware Loader

-

228


Release 6/2003

C79000–G8976–C129–07

References

A

/1/

Product information bulletin / manual SIMATIC NET CP

Supplied with the specific CP

Siemens AG

/2/

/3/

NCM S7 for PROFIBUS Primer

Part

– of the documentation package NCM S7 for PROFIBUS

– of the online documentation in the STEP 7 optional package NCM S7 for

PROFIBUS

SIEMENS AG

NCM S7 for Industrial Ethernet Manual

Part

– of the documentation package NCM S7 for Industrial Ethernet


Industrial Ethernet

SIEMENS AG

/4/

SIMATIC NET , Manual

Commissioning PC Stations

Part



Industrial Ethernet

Siemens AG


Release 6/2003

C79000–G8976–C129–07

229

References

/5/

SIMATIC NET IT-CP, manual

Part



Industrial Ethernet

Siemens AG

/6/

SIMATIC STEP Configuring Hardware and Connections with STEP 7

Part of the standard STEP 7 Documentation Package

Part of the online documentation in STEP 7

SIEMENS AG

/7/

Communication with SIMATIC

Manual

SIEMENS AG

/8/

SIMATIC Programming with STEP 7

Part of the standard STEP 7 Documentation Package


SIEMENS AG

/9/

/10/

SIMATIC STEP 7 Reference Manuals with manuals

– LAD / FBD / STL

– System Software for S7-300/400 System and Standard Functions


Siemens AG

SIMATIC NET Industrial Twisted Pair Networks

SIEMENS AG

/11/

Ethernet, IEEE 802.3

(ISO 8802-3)

230


Release 6/2003

C79000–G8976–C129–07

References

/12/

SINEC CP 1413

Manuals for MS-DOS, Windows

SIEMENS AG

/13/

/14/

/15/

SIMATIC NET Manual for Triaxial Networks

SIEMENS AG

SIMATIC NET Ethernet Manual

SIEMENS AG

/16/

Lokale Netze –

Kommunikationsplattform der 90er Jahre

Andreas Zenk

Addison-Wesley

ISBN 3-89319-567-X

/17/

TCP/IP

Internet-Protokolle im professionellen Einsatz

Mathias Hein

International Thomson Publishing

ISBN 3-8266-400-4

ITP Online-Center: http://www.ora.de

/18/

SIMATIC S7

S7-300 Programmable Controller

Hardware and Installation

Manual

SIEMENS AG

RFC1006 (Request For Comment)


Release 6/2003

C79000–G8976–C129–07

231

References

/19/

RFC793 (TCP)

/20/

RFC791 (IP)

/21/

Berger, Hans

Automation with STEP 7

SIMATIC S7-300/400 Programmable Logic Controllers

/22/

For configuring PROFInet components and systems:

Basic help in the SIMATIC iMap engineering tool

/23/

For configuring PROFInet components and systems:

Component based Automation – Configuring Systems with SIMATIC iMap

Manual

/24/

SIMATIC S7

Programmable Controller

S7-400, M7-400

Hardware and Installation

Order Numbers

The order numbers for the SIEMENS documentation listed above can be found in the catalogs “SIMATIC NET Industrial Communication, Catalog IK PI” and

“SIMATIC Programmable Controllers SIMATIC S7 / M7 / C7”.

You can obtain these catalogs and any further information you require from your local SIEMENS office or national head office.

Some of the documents listed here are also on the Manual Collection CD supplied with every S7-CP.

232


Release 6/2003

C79000–G8976–C129–07

Glossary

B

B.1

B.2

B.3

General Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


PROFInet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

234

238

240


Release 6/2003

C79000–G8976–C129–07

233

Glossary

B.1

General Section

Baud rate

–> transmission rate

Broadcast

A broadcast is like ”calling all stations”: Using one broadcast frame, you can reach all nodes that are prepared to accept broadcast frames.

Bus segment

Part of a –> subnet. Subnets can consist of bus segments and connectivity devices such as repeaters and bridges. Segments are transparent for addressing.

Client

A client is a device or, in general terms, an object that requests a service from a

–> server.

Configuration data

Parameters that determine the modes and functions of a –> CP. They are set and downloaded using the NCM S7 configuration tool.

CP

Communications Processor. Module for communications tasks.

CSMA/CD

CSMA/CD (Carrier Sense Multiple Access with Collision Detection); a transmission technique.

Frame

A message from one PROFIBUS/Ethernet station/node to another.

Frame header

A frame header consists of an identifier for the –> frame and the source and destination address.

Frame trailer

A frame trailer consists of a checksum and the end identifier of the –> frame.

234


Release 6/2003

C79000–G8976–C129–07

Glossary

Functions (FCs)

STEP 7 code blocks of the type ”function”.

Gateway

Intelligent connectivity device that connects local area –> networks of different types at the ISO Layer 7 level.


A LAN system complying with IEEE 802.3 (ISO 8802-2)

Multicast

A multicast is like ”calling all group stations”: Using one multicast frame, you can reach all the nodes that belong to the multicast group and that are prepared to receive frames.

NCM S7 for Industrial Ethernet

Configuration software for configuration and diagnostic functions on an Ethernet

CP.

NCM S7 for PROFIBUS

Configuration software for configuration and diagnostic functions on a PROFI-

BUS CP.

Network

A network consists of one or more interconnected –> subnets with any number of –> nodes. Several networks can exist side by side.

PG operation

A mode of the PROFIBUS/Ethernet CP in which the SIMATIC S7-CPU is programmed, configured or diagnosed over PROFIBUS/Ethernet. This mode is handled by the S7 functions.

PROFInet

Standard of the PROFIBUS Users organization defining a heterogeneous communications and engineering model.

Protocol

A set of rules for transferring data. Using these rules, both the formats of the frames and the data flow are specified.


Release 6/2003

C79000–G8976–C129–07

235

Glossary

Process image

The process image is a special memory area in the programmable logic controller. At the start of the cyclic program, the signal states of the input modules are transferred to the process input image. At the end of the cyclic program, the process output image is transferred as a signal state to the output modules.

Segment

Synonym for –> Bus segment.

Services

Services provided by a communication protocol.

Server

A server is a device, or in general terms, an object that provides certain services.

A service is started at the instigation of a –> client.

SIMATIC NET

Siemens SIMATIC Network and Communication. Product name for –> networks and network components from Siemens. (previously SINEC)

SIMATIC NET Ind. Ethernet

SIMATIC NET LAN system for industrial applications based on Ethernet.

(previously SINEC H1)

SINEC

Previous product name for -> networks and network components from Siemens.

Now: SIMATIC NET

Station

A station is identified by a

S

MAC address in the Ethernet network

S

PROFIBUS address in the PROFIBUS network

236


Release 6/2003

C79000–G8976–C129–07

Glossary

Subnet

A subnet is part of a –> network whose parameters (for example –> PROFIBUS) must be matched. The subnet includes bus components and all the attached stations. Subnets can, for example, be connected together by –> gateways to form a network.

A –> system consists of several subnets with unique –> subnet numbers. A subnet consists of several –> stations with unique –> PROFIBUS or MAC addresses (Industrial Ethernet).

System

This means all the electrical equipment within a system. A system includes, among other things, programmable logic controllers, devices for operation and monitoring, bus systems, field devices, actuators, supply lines.

Transport layer

The transport layer is layer 4 of the ISO/OSI reference model for open system interconnection. The purpose of the transport layer is to transfer data reliably from device to device. Transport connections can be used for the transmission.

Transport interface

The transport interface of a SIMATIC S5 PLC is the access to the connectionoriented services of the transport layer on the CP. The transport interface presents itself to the control program in the form of handling blocks (HDBs).

TSAP

Transport Service Access Point

Transmission rate

According to DIN 44302, this is the number of binary decisions transmitted per time unit. The unit is bps. The set or selected transmission rate depends on various conditions, for example the distance across the network.

Watchdog

Mechanism for monitoring operability.


Release 6/2003

C79000–G8976–C129–07

237

Glossary

B.2


Base address

Logical address of a module in S7 systems.

S

For PROFIBUS

The PROFIBUS base address is the address starting at which all addresses that are calculated automatically in the project are assigned.

S

For Industrial Ethernet

The base MAC address is the address starting at which all addresses that are calculated automatically in the project are assigned.

Ind. Ethernet station

A station is identified by a –> MAC address in –> Industrial Ethernet.

ISO-on-TCP

Transport layer connection (layer 4 communication complying with ISO) simulated on TCP.

On an ISO-on-TCP connection, messages can be exchanged in both directions.

TCP provides the data flow communication without segmenting the data into messages. ISO, on the other hand, is message-oriented. With ISO-on-TCP, this mechanism is simulated on TCP. This is described in RFC1006 (Request For

Comment).

ISO-on-TCP connections allow program/event-controlled communication via

Ethernet from a SIMATIC S7 PLC to

S


S


S


S any system

238


Release 6/2003

C79000–G8976–C129–07

Glossary

ISO Transport Connection

Communication connection of the transport layer (with the CP/COM 143 previously S5S5 connection).

ISO transport connections allow program/event-controlled communication on

Industrial Ethernet between SIMATIC S7 PLCs and

S


S

SIMATIC S5 with an Ethernet CP (e.g. CP 143 or CP 1430)

S

PC/PG with Ethernet CP (for example CP 1613)

S

Any system using the ISO transport protocol (ISO 8073)

The transfer of blocks of data on an ISO transport connection is bi-directional.

MAC address

Address to distinguish between different stations connected to a common transmission medium (Industrial Ethernet).

Media Access Control (MAC)

Mechanisms for controlling access by a station to a common transmission medium shared with other stations.

RFC1006

see ISO-on-TCP

S5S5 connection

see ISO transport connection

Subnet mask

The subnet mask specifies which parts of an IP address are assigned to the network number. The bits in the IP address whose corresponding bits in the subnet mask have the value 1 are assigned to the network number.

Subnet number

A –> system consists of several –> subnets with unique subnet numbers.


Release 6/2003

C79000–G8976–C129–07

239

Glossary

TCP/IP

TCP = Transport Connection Protocol; IP = Internet Protocol

UDP

User Datagram Protocol. User Datagram Protocol: datagram service for simple internetwork transmission without acknowledgment.

B.3

PROFInet

Component based Automation

Concept for implementing modular, distributed automation applications on the basis of open standards and data communication.

Component based Automation is an expansion of Totally Integrated Automation

(TIA).

Device

In Component based Automation: part of the PROFInet component that contains the hardware-specific data of the PROFInet component. In SIMATIC iMap, a device is the software representation of the physical device for which the

PROFInet component was created. It is displayed in the network view of

SIMATIC iMap as an object with one or more bus attachments. The following distinction is made according to the communication functionality: –> PROFInet devices and –> PROFIBUS devices.

Interconnection

General: Logical data connection between two objects. In SIMATIC iMap:

Connection between two technological functions. An output is interconnected with an input of the same type. Interconnections are represented in SIMATIC iMap by lines.

Network view

View of the devices and the networks (Ethernet, PROFIBUS) in SIMATIC iMap.

Plant view

View of the technological functions of the automation system and its interconnections in SIMATIC iMap. One chart is displayed in the plant view.

240


Release 6/2003

C79000–G8976–C129–07

Glossary

PROFIBUS device

In Component based Automation: A PROFIBUS device has only one PROFIBUS attachment as a slave. It does not take part directly in PROFInet communication but is linked using a proxy PROFInet device.

PROFInet

Standard of the PROFIBUS Users organization defining a heterogeneous communications and engineering model.

PROFInet device

A device on Ethernet is a PROFInet device. A PROFInet device can also have a

PROFIBUS attachment as master and proxy PROFInet device for PROFIBUS devices.

PROFInet component

Software representation of a technological module with defined functionality. An automation system is made up of several PROFInet components.

A PROFInet component always includes a technological function and the corresponding device.

PROFInet device, proxy

A PROFInet device that has the role of the master for PROFIBUS devices. This allows PROFIBUS slaves to be included in PROFInet communication.

SIMATIC IMap

Engineering tool from Siemens for Component based Automation. Allows the configuration, commissioning, and monitoring of modular, distributed automation systems based on the PROFInet standard.

SIMATIC iMap – STEP 7 AddOn

Software for the SIMATIC iMap interface to STEP 7.


Release 6/2003

C79000–G8976–C129–07

241

Glossary

-

242


Release 6/2003

C79000–G8976–C129–07

Linking to Other Systems with

FETCH/WRITE

C

The FETCH and WRITE modes supported on ISO transport connections, TCP, and ISO-on-TCP connections can be used with any other device to access the S7 system memory areas.

To be able to use this type of access, for example for PC applications, you need to know the PDU structure of the jobs. The required S7 or S5 header for request and response frames are 16 bytes long and their structure is described in this chapter.


Release 6/2003

C79000–G8976–C129–07

243

Linking to Other Systems with FETCH/WRITE

a) Structure of WRITE Frames

The meaning and values of parameters shown without values in the following table can be found in the section

“Parameter Values“.

WRITE request frame

0 System ID

1

2 Length of header

3

ID OP code

4

Length OP code

5 OP code

6

ORG field

7 Length ORG field

8 ORG ID

9 DBNR

A

Start address

B

C

Length

D

E Empty field

F Length empty field

Data up to 64 K

=”S”

=”5”

=16d.

=01

=03

=03

=03

=08

High Byte

Low Byte

High Byte

Low Byte

=FFh.

=02

WRITE acknowledgment frame

0

System ID

=”S”

1

2

Length of header

=”5”

=16d.

3

ID OP code

4

Length OP code

5

OP code

6

Ack field

7

Length ack field

8

Error field

9

Empty field

=01

=03

=04

=0Fh

=03

=No

=FFh

A

Length empty field

B

C

D free

E

F

=07

244


Release 6/2003

C79000–G8976–C129–07


a) Structure of FETCH Frames

The meaning and values of parameters shown without values in the following table can be found in the section

“Parameter Values“.

FETCH request frame

0 System ID

1

2 Length of header

3

ID OP code

4

Length OP code

5 OP code

6

ORG field

7 Length ORG field

8 ORG ID

9 DBNR

A

Start address

B

C

Length

D

E Empty field

F Length empty field

=”S”

=”5”

=16d.

=01

=03

=05

=03

=08

High Byte

Low Byte

High Byte

Low Byte

=FFh.

=02

FETCH response frame

0

System ID

1

2

Length of header

3

ID OP code

4

Length OP code

5

OP code

6

Ack field

7

Length ack field

8

Error field

9

Empty field

A

Length empty field

B

C

D free

E

F

Data up to 64 K but only if Error no. =0

=”S”

=”5”

=16d.

=01

=03

=06

=0Fh

=03

=No

=FFh

=07


Release 6/2003

C79000–G8976–C129–07

245


Parameter Values

S7 Address Area

ORG ID

DBNR permitted range

Start address permitted range

Length permitted range

DB

01

H

Source/dest.

data from/to data block in main memory

M

02

H

Source/dest.

data from/to flag area

I

03

H

Source/dest.

data from/to process image of the inputs (PII) irrelevant

Q

04

H

Source/dest.

data from/to process image of the outputs (PIQ) irrelevant DB, from which the source data are taken or to which the dest data are transferred irrelevant

1...255

DW number, from which the data are taken or written to

0...2047

Length of the source/dest.

data field in words

Flag byte no., from which the data are taken or written to

Input byte no., from which the data are taken or written to

Output byte no., from which the data are taken or written to

0...255


data field in bytes

0...127


data field in bytes

0...127


data field in bytes

1...2048

1...256

1...128

1...128

246


Release 6/2003

C79000–G8976–C129–07


S7

Address Area

ORG ID

DBNR

Start address permitted range

Length permitted range

PI/PQ C

05

H

Source/dest.

data from/to in

I/O modules.

With source data input modules, with dest data output modules irrelevant

06

H

Source/dest data from/to counter cells irrelevant

T

07

H

Source/dest data from/to timer cells irrelevant

I/O byte no., from which the data are taken or written to

Number of the counter cell from which the data are taken or written to

Number of the timer cell from which the data are taken or written to

0...127

digital I/Os

128...255

analog I/Os


data field in bytes

1...256

0...255


data field in words (counter cell = 1 word)

1

0...255


data field in words (counter cell = 1 word)

1


Release 6/2003

C79000–G8976–C129–07

247


-

248


Release 6/2003

C79000–G8976–C129–07

Document History

D

This section provides an overview of the previous releases of this manual and the functional expansions in STEP 7 and NCM S7.

New in release 06 / STEP 7 V5.2

S

S7 communication over routers (single-ended client and server functionality) via an IE/PB Link or CP.

S

Multiprojects

With the new multiproject functionality, projects can be split up and distributed for engineering and then merged again.

New in Release 05 / STEP 7 V5.1 SP3

S

Configuring multicast and broadcast on UDP connections.

See Chapter LEERER MERKER.

S

The blocks AG_SEND and AG_RECV can now be used for “long data packets” with an S7–300. See Chapter 6

S

The S7 CPs for Ind. Ethernet are now supplied with a default MAC address allowing configuration data to be downloaded over Ethernet without a “node initialization”.

New in Release 04 / up to STEP 7 V5.1 SP2

S

The FETCH/WRITE mode is now supported on TCP connections. See

Chapter 4.

S

The FETCH/WRITE mode can be coordinated in the user program by the new

FCs AG_LOCK and AG_UNLOCK. See Chapter 6

S

NCM Diagnostics has a completely revised user interface. See Chapter 7.

The description of NCM S7 Diagnostics has been restructured. While this manual provides you with an overview and checklists, the online help provides you with detailed information on the diagnostic events.


Release 6/2003

C79000–G8976–C129–07

249

Document History

250


Release 6/2003

C79000–G8976–C129–07

A

Access coordination, 191

CONF_DB, 198

Address parameters

Broadcast, 136

broadcast, 135

unspecified ISO-on-TCP connection, 117

unspecified TCP connection, 125

unspecified UDP connection, 132

AS-interface, 16

B

Broadcast, with UDP, 133

C

Communication options, 17

Communication services, configuring, 68

Configuration data, download to target system,

74

Configuration data block, 146, 149

Connection, properties, 91

Connection configuration, 89

Connection ID, 152 range of values, 152

Connection types, parameter fields for, 152

CP address, 164

CP configuration data, saving, 75

Creating a subnet, 48

CSMA/CD, 16

Ethernet CP

further CP properties, 57

time, 58

installing and starting, 45

procedure, 47

F

FB, 164

CP_CONFIG, 146

IP_CONFIG, 197

FCs

block number, 164

for configured connections, 170

general notes, 164

FCs for access coordination with

FETCH/WRITE, 191

FETCH/WRITE services

configuration for ISO transport, 139

overview, 32

Firmware Loader, 225

application, 226

loading firmware, 227

FTP connection, Parameter field for, 158

Functions

AG-RECV, 78, 79

AG-SEND, 78, 79

Functions (FC), typical sequence, 80

Functions (FCs)

AG_LOCK, 193

AG_LOCK / AG_UNLOCK, 191

AG_RECV / AG_LRECV, 184

AG_SEND / AG_LSEND, 174

AG_UNLOCK, 195

Further functions, 99

D

DHCP server, 63

Displaying network attachments, 55

Downloading, 74

Dynamic properties, 109

H

Hardware configuration, Ethernet CP, 51

E

E-mail connection, Parameter field for, 156

Ethernet, overview, 16

I

Industrial Ethernet, overview, 16

Industrial Ethernet; user interface to, 25


Release 6/2003

C79000–G8976–C129–07

Index-1

IP access control list, 62

IP access protection, 62

IP address

in the ”Properties – Ethernet Interface”

dialog, 63 obtaining from a DHCP server, 63 setting in the user program, 63

IP address assignment over DHCP, 97

IP configuration, 63

ISO transport connection, 103

amount of data and number of connections,

91

checking, 111

connection without assignment, 100

dynamic properties, 109

printing configured connections, 99

properties dialog, 103

addresses, 107

dynamics, 109

general, 104

overview, 111

save connection, 99

Unspecified connection, 108


addresses, 115

checking, 118

parameter field for, 155

properties, 112

specifying the connection partner, 113

J

Job header, 172

M

MAC address, 75

Multicast, with UDP, 133, 136

Multiproject, 33, 38

configuring connections, 90, 96

NCM S7 Diagnostics online path examples of an online path with gateway,

215

Examples of an online path without

gateway, 214

NCM S7 diagnostics online path, examples of

an online path with ”PC internal”, 217

Network access, 16

New connection, 94, 95

O

Operator interface devices, 24, 25

Other station, 33, 96

configuring, 65

connecting a subnet, 66

P

PC internal, 217

PG communication

in configured mode, 23 in PG operation, 23

with STEP 7 on PROFIBUS, 23

PG operation, with STEP 7 via Ethernet, 21

PG/PC interface, 25

PROFIBUS, 16

PROFIBUS; user interface to, 25

PROFInet communication, 17, 18

Programmed Communication Connections,

145

Programmed connections, 20

Project variant

1 subnet – 1 project, 35

1 subnet – more than 1 project, 38

2 or more subnets – 1 project, 37

several subnets – several projects, 41

several subnets several projects, 43

SIMATIC S5 and non-SIMATIC devices, 36

R

Routing, 143

N

NCM S7

general information, 46 installation, 46

NCM S7 Diagnostics, 61, 205

NCM S7 diagnostics, overview, 206

S

S7 communication on Ethernet, 17, 25

Index-2


Release 6/2003

C79000–G8976–C129–07

S7 communication relay, 17, 25

S7 functions, 17

SEND/RECEIVE interface, 17

CPU cycle, 82

data exchange, 78

overview, 29

user program, 79

SIMATIC NET, 16

Subfield types, 159

System data, parameter field for , 150

System memory, access using

FETCH/WRITE, 141

T

TCP Connection, checking properties, 126

TCP connection, 119

addresses, 123



Type of communication, 17

U

UDP

addresses, 130

checking, 137

configuring, 127

UDP connection



Unspecified connection, 97


Release 6/2003

C79000–G8976–C129–07

Index-3

A&D Technical Support

Worldwide, available 24 hours a day:

Nuernberg

Johnson City

Beijing

Worldwide (Nuernberg)

Technical Support

24 hours a day, 365 days a year

Phone: +49 (0) 180 5050-222

Fax:

E-Mail:

GMT:

+49 (0) 180 5050-223 adsupport@ siemens.com

+1:00

Europe / Africa (Nuernberg)

Authorization

United States (Johnson City)

Technical Support and

Authorization

Asia / Australia (Beijing)

Technical Support and

Authorization

Local time: Mon.-Fri. 8:

00 to 17:00

Local time: Mon.-Fri. 8:00 to 17:00

Phone:

Fax:

+49 (0) 180 5050-222

+49 (0) 180 5050-223

E-Mail: adsupport@ siemens.com

Local time: Mon.-Fri. 8:00 to 17:00

Phone:

Fax:

E-Mail:

+1 (0) 423 262 2522

+1 (0) 423 262 2289 simatic.hotline@ sea.siemens.com

Phone:

Fax:

E-Mail:

+86 10 64 75 75 75

+86 10 64 74 74 74 adsupport.asia@ siemens.com

GMT: +1:00 GMT: -5:00 GMT: +8:00

The languages of the SIMATIC Hotlines and the authorization hotline are generally German and English.

A&D Technical Support

Service & Support on the Internet

In addition to our documentation, we offer our Know-how online on the internet at: http://www.siemens.com/automation/service&support where you will find the following:

• The newsletter, which constantly provides you with up-to-date information on your products.

• The right documents via our Search function in Service & Support.

• A forum, where users and experts from all over the world exchange their experiences.

• Your local representative for Automation & Drives via our representatives database.

• Information on field service, repairs, spare parts and more under "Services".

A&D Technical Support

No results