You are on page 1of 64

SIMATIC

S7 - OPEN MODBUS / TCP Communication
via the integrated PN interface of the PLC
Manual

Preface, Table of Contents
Product Description

1

Getting Started

2

Commissioning

3

Parameterization

4

Licensing

5

FB MODBUSPN

6

Diagnosis

7

Sample Application

8

SIMATIC S7
S7 OPEN MODBUS / TCP
Communication via the
integrated PN interface of the PLC
Manual

Appendices
Literature
Glossary

Edition 2.4

Safety Precautions and
Warnings

This manual contains warnings, which you should note for your own safety as well as for
the prevention of damage to property. These warnings are indicated by means of a warning
triangle and are displayed as follows in accordance with the level of danger:
__________________________________________________________________
Danger
indicates that loss of life, severe personal injury or substantial damage
will result if proper precautions are not taken.

__________________________________________________________________
__________________________________________________________________
Warning
indicates that loss of life, severe personal injury or substantial damage can result if proper
precautions are not taken.

__________________________________________________________________
__________________________________________________________________
Caution
indicates that minor personal injury or property damage can result if proper precautions are
not taken.

__________________________________________________________________
__________________________________________________________________
Note
represents an important information especially significant to the product, handling of the
product or a specific part of this documentation.

__________________________________________________________________
Qualified
Personnel

The start-up and the operation of the device may only be carried out by qualified
personnel. Qualified personnel in the sense of the security advices of this manual are any
persons authorized to commission, ground and label devices, systems and electric circuits.

Use as prescribed

Please note:
_________________________________________________________________________
Warning
This device may only be used for applications as prescribed in the catalogue and the
technical description. Furthermore, they may only be used in conjunction with third-party
devices and components recommended and authorized by Siemens.
A successful and safe operation of this product is depends on proper transport, and correct
storage, installation and assembly as well as careful operation and maintenance.

®

®

SIMATIC and SIMATIC NET are registered trademarks of SIEMENS AG.
Trademarks

Since any other brand names in this manual may refer to trademarks, the use of these
names by third parties for their own purposes may infringe the rights of the owner.

Copyright © Siemens AG 2008 All Rights Reserved

Exclusion of Liability

Passing on and reproducing this document as well as using and
disclosing its contents is prohibited unless an explicit permission is
given. Offenders will be liable for damages. All rights reserved,
especially in the case of patent grant or registration of a utility model
or design.

We have checked the contents of this document with regard to its
conformity with the described hardware and software. Deviations,
however, cannot be excluded. Therefore, we cannot guarantee its
complete conformity. The information in this document is checked
regularly and necessary corrections are contained in subsequent
versions. We will be grateful for any suggestions for improvement.

Siemens AG
Industry Sector
Engineering and Construction
I IS IN E&C
P.O. Box 3240, D- 91050 Erlangen
IT4.Industry@siemens.com

Technical data subject to change.

4 1 .0 FB 104 “MOD_CLI“ 1.4 FB 103 “TCP_COMM” 3.5 FB 105 “MOD_SERV“ 1. Contents of the Manual This manual describes the function of the Modbus function block and its parameterization.4 FB 102 “MODBUSPN” 3. The manual contains the following topics: • Production description • Getting Started • Commissioning • Parameterization • Licensing • Function block MODBUSPN • Diagnosis • Sample application Scope of this Manual This manual is valid for the following software: Product Identification number From version OPEN MODBUS/TCP 2XV9 450-1MB02 2. Manual edition 2.) can be found in the manuals SIEMENS SIMATIC S7-300 CPU 31xC and CPU 31x: Installation Operating Instructions A5E00105491-07 MODBUS / TCP communication via the integrated PN interface of the CPU 2XV9450-1MB02.3 Note This manual contains the FB description valid at the time of publication. Additional Sources of Information All additional information concerning PN PLCs and IM 151-8 PN/DP CPU (Startup. commissioning etc.Preface Preface Purpose of the Manual The information in this manual allows you to set up and put in operation the connection between a PLC with integrated PN interface and a device that supports the Open MODBUS/TCP protocol.

6ES7315-2EH13-0AB0 CPU315F-2 PN/DP. 6ES7318-3FL00-0AB0 A5E01103134-03 Additional information concerning STEP7 can be found in the following manuals: SIEMENS SIMATIC Software Base software for S7 and M7 STEP7 user manual C79000-G7000-C502-..4 2 . SIEMENS SIMATIC Software System software for S7-300/400 System and standard functions Reference manual C79000-G7000-C503-02 MODBUS / TCP communication via the integrated PN interface of the CPU 2XV9450-1MB02.Preface SIEMENS SIMATIC S7-300 CPU 31xC and CPU 31x. CPU Specifications Manual A5E00850746-06 SIEMENS SIMATIC Distributed I/Os ET 200S Interface Module IM151-8 PN/DP CPU Manual A5E02049033-01 SIEMENS Product Information on CPU315-2 PN/DP. 6ES7315-2FH13-0AB0 CPU317-2 PN/DP. 6ES7317-6FF03-0AB0 CPU319-3 PN/DP. 6ES7318-3EL00-0AB0 CPU319F-3 PN/DP. Technical Specifications Manual A5E00105474-07 SIEMENS SIMATIC S7-400 Automation System S7-400 Hardware and Installation Operating Instructions A5E00850740-01 SIEMENS SIMATIC S7-400 S7-400 Automation System. 6ES7317-2EK13-0AB0 CPU317F-2 PN/DP. 6ES7317-2FK13-0AB0 CPU317-2 DP. 6ES7317-2AJ10-0AB0 CPU317F-2 DP. Manual edition 2.

MODBUS / TCP communication via the integrated PN interface of the CPU 2XV9450-1MB02. Manual edition 2. 317.4 3 . Terminology This document uses the term PN PLC.Preface Additional Questions For further questions regarding the use of the FBs described in this manual. please contact your Siemens partner who provided you with this function block. 414 and 416 as well as IM 151-8 PN/DP CPU. The descriptions apply to PN PLCs of series 315. 319. Scope of Application The function block described in this manual establishes a connection between a PN PLC and third-party MODBUS devices.

....................3 Insertion of the Function Blocks into the Program...........5 Diagnosis Messages of SFC24 ................................1 Field of Applications................................................................ Manual edition 2..........................................2 Editing the Parameterization ......... 4-1 4..... 1-1 1....... 3-1 4 3........................ 3-4 Parameterization of the Modbus Communication ............ 6-5 6................................................. 4-2 4...... 6-15 6........................................................... 3-2 3......2 Hardware and Software Prerequisites...................3 Example of Address Mapping................................................ 7-1 7.......................................1 Diagnosis via the Display Elements of the PLC ......................................................................................................................... 6-12 6........................................5 Renaming Standard Functions .......2 Parameters of the Function Block MODBUSPN ............. 8-1 A Literature................................................................................................................................ 1 MODBUS / TCP communication via the integrated PN interface of the CPU 2XV9450-1MB02.......... 2-1 3 Commissioning ............Table of contents Table of Contents 1 Product Description....2 Verification by the FB MODBUSPN......................... 1-1 1............................................................................................... 6-1 7 6.. 7-2 7..............................4 Diagnosis Messages of Called Blocks ........................................................................................3 Diagnosis Messages of the FB MODBUSPN................................... 7-3 7................................................... 6-16 Diagnosis ......................................................................................................................................... 1-1 2 Getting Started .............................................................................. 6-1 6.....................................................................................................1 Parameterization with the Wizard.............4 Data and Standard Functions used by the FB ................................................................................................... 5-1 6 Function Block MODBUSPN ............................................2 PLC – Assigning the IP Address .............. 7-12 8 Sample Application......................................................... 4-3 5 Licensing ........................................................................................................1 Functionality of the FB . 7-6 7......................................................................................1 Installing the Library on the STEP7 PG/-PC ............ 7-12 7....................... 3-1 3.....................4 i ...................................................................................................................................

Product description

1

Product Description

1.1

Field of Applications

Placement in the
System Environment

The function block described here is a software product for PLCs with
integrated PN interface of Simatic S7-300, S7-400 and IM 151-8 PN/DP CPU.

Function of the
FBs

With these function blocks, communication link is established between a
Simatic PLC with integrated PN interface and a device that supports the Open
MODBUS/TCP protocol.
Data transmission is carried out in accordance with the client-server principle.
The SIMATIC S7 can act as both, a client and a server, during the data
transmission.

Use of Port
Number 502

In general, the protocol uses the port 502. This port number has not been
released for all PN PLCs yet and is only possible when using a 319 CPU, an
IM 151-8 PN/DP CPU, a 414 CPU or a 416 CPU with the corresponding
firmware version. You can find the information about the released port
numbers on the internet:
http://support.automation.siemens.com/WW/view/en/34010717.
The PLC only allows a one-time use of a specific port number. Therefore
the PLC/FB cannot be addressed simultaneous from different devices on the
same port number.

1.2

Hardware and Software Prerequisites

Usable Modules

The function blocks have been tested on the PLCs with the product
identifications
CPU315-2 PN/DP
CPU317-2 PN/DP
CPU319-3 PN/DP
CPU414-3 PN/DP
CPU416-3 PN/DP
IM151-8 PN/DP

6ES7315-2EG10-0AB0
6ES7317-2EK13-0AB0
6ES7318-3EL00-0AB0
6ES7414-3EM05-0AB0
6ES7416-3FR05-0AB0
6ES7151-8AB00-0AB0

You can find the latest hardware prerequisites on the internet:
www.siemens.com/s7modbus.
Software Versions

The usage of the FB MODBUSPN is possible with STEP7 Version 5.4 SP4 or
higher.

MODBUS / TCP communication via the integrated PN interface of the CPU
2XV9450-1MB02; Manual edition 2.4

1-1

Product description

Memory
requirements

The FB MODBUSPN requires ca. 6 kbyte work memory and ca. 7 kbyte load
memory.
The FB MOD_CLI requires ca. 11 kbyte work memory and ca. 12 kbyte load
memory.
The FB MOD_SERV requires ca. 10 kbyte work memory and ca. 11 kbyte
load memory.
The FB TCP_COMM requires ca. 2 kbyte work memory and ca. 2 kbyte load
memory.

MODBUS / TCP communication via the integrated PN interface of the CPU
2XV9450-1MB02; Manual edition 2.4

1-2

Getting started

2

Getting Started

Procedure

1. Install “OpenModbusTCP PN CPU“ and insert the Modbus function blocks
into your SIMATIC project.
=> Section 3.1 to 3.3
2. Parameterize the connection parameters regarding your requirements
(IP-address, port number, etc.).
=> Section 4.1 and 4.2
3. Parameterize the Parameter-DBs MODBUS_PARAM regarding your
requirements (client/server, connect at start-up, register numbers,
DB numbers, etc.).
=> Section 4.1 and 4.2
4. Call the Modbus block FB102 in the required OBs.
=> Section 6.1
5. Parameterize the Modbus block for initialization and runtime.
=> Section 6.2
6. Load the user program into the PLC and license the Modbus block for this
CPU.
=> Section 5
.

MODBUS / TCP communication via the integrated PN interface of the CPU
2XV9450-1MB02; Manual edition 2.4

2-1

use the browse function of the “Open” dialog for libraries. Requirements Knowledge of AWL and basic knowledge of STEP7 and PLC is required. To initially access the Modbus library. Manual edition 2. • the sample project in \Program Files\Siemens\Step7\Examples. please proceed as follows: 1. Installation Insert your Modbus CD into the CD ROM drive and follow step-by-step the instructions which are displayed automatically by the installation program. 2. MODBUS / TCP communication via the integrated PN interface of the CPU 2XV9450-1MB02. Now you can find • the library in \Program Files\Siemens\Step7\S7libs. the sample projects and the manuals in English and German in the corresponding STEP7 directories. Requirements STEP7 has to be installed. 3. In the Windows Explorer. • the software registration form in \Program Files\Siemens\Step7\S7libs\Modbus_PN_CPU.1 Installing the Library on the STEP7 PG/-PC What We Provide The attached CD contains a setup which installs the library “Modbus_PN_CPU”. The manuals are also available as PDF files on CD.EXE to start the installation. The manual can be accessed via short cut under \Program Files \Siemens\ Documentation as well. Double-click on the setup directory and then on Setup.4 3-1 . • the manual in \Program Files\Siemens\Step7\S7manual\S7Comm. the sequences. If the installation program does not start automatically. In later versions. navigate to the CD ROM drive.4 SP4. Follow the step-by-step the instructions which are displayed by the installation program.Commissioning 3 Commissioning General Information The information below on STEP7 refers to Version 5. names and directories might be different.

Manual edition 2. In this example. This so-called MAC address is preset by the manufacturer and cannot be changed. MODBUS / TCP communication via the integrated PN interface of the CPU 2XV9450-1MB02. A double click on line X2 opens the object properties dialog of Ind. you can assign an IP address in the Ethernet to this physical address.4 3-2 . Ethernet. a PLC 317-2 PN/DP is inserted. 2. Procedure Before the configuration. it is necessary to create a new S7 project with STEP7. 1. Following the steps below.2 PLC – Assigning the IP Address Introduction Each node on the Ethernet network is identified by an internationally unique address. Open HWConfig The PLC 317-2 PN/DP is inserted in slot 2 and the properties dialog box of the PN-IO interface X2 is mapped.Commissioning 3.

Confirm your entries with "OK". To establish a connection via a router. Click on the "OK" button. Enter the IP address and the subnet mask. Result: You created a new Industrial Ethernet subnet.4 3-3 . Click on "New" to assign a name for a new Industrial Ethernet subnet. 4.Commissioning 3. MODBUS / TCP communication via the integrated PN interface of the CPU 2XV9450-1MB02. 5. enter the address of the router as well. Result: The properties window of Ethernet interface X2 for PLC 317-2 PN/DP closes. Manual edition 2.

Commissioning 3.2 or higher V2.4 3-4 . MODBUS / TCP communication via the integrated PN interface of the CPU 2XV9450-1MB02. Manual edition 2. Blocks of the Standard Library The following blocks are required for the Modbus communication: • TSEND (FB63) • TRCV (FB64) • TCON (FB65) • TDISCON (FB66). They can be inserted into your project for assistance purposes.3 or higher V2.1 or higher V2.3 Insertion of the Function Blocks into the Program Content of the MODBUS library The following blocks are required for the Modbus communication: • MODBUSPN • MOD_CLI • MOD_SERV • TCP_COMM The blocks have to be copied from the library into your project. the library contains the parameter data block MODBUS_PARAM as a draft. Please note that the following versions of the FBs are a prerequisite for the faultless function of the FB MODBUSPN: TSEND TRCV TCON TDISCON V2. You can find this function in „Standard Library Æ IEC Function Blocks“.1 or higher Furthermore the block FC10 EQ_STRNG is necessary. Additionally. You can find these blocks in Standard Library Æ Communication Blocks. They have to be inserted into your project.

a separate structure is required.. Manual edition 2. At first the connection parameters are defined. The connections are established and terminated by means of the function blocks TCON (FB65) und TDISCON (FB66).0 Connection 2: Modbus parameters END_STRUCT . the Modbus parameters are defined.. A prepared structure is part of the library “MODBUS_PN_CPU” and can be used as a sample. . It is also possible to use a separate parameter data block for each connection. The parameter data block can contain parameter information of all defined connections. the parameter data block must be expanded by or a new data block created with the structure for connection parameters and the Modbus parameters. STRUCT 650*i 650*i+64 Connection i+1: Connection parameters (65+i) Connection i+1: Modbus parameters END_STRUCT MODBUS / TCP communication via the integrated PN interface of the CPU 2XV9450-1MB02. For each logical connection. The maximal number of coexistent connections depends on the PLC..0 +64. This structure contains the connection parameters of both communication partners and the Modbus parameters. Several connections to different communication partners can be parameterized and established at the same time. For each additional connection. Structure of DB MODBUS_PARAM: Address Name STRUCT +0. a network configuration in NetPro is not necessary.4 4-1 .. Connection Description DB MODBUS_PARAM The parameters to establish a connection and to execute the Modbus communication are defined as a structure in a parameter DB called MODBUS_PARAM.0 Connection 1: Connection parameters Connection 1: Modbus parameters END_STRUCT STRUCT +650. subsequently.Parameterisation of the Modbus Communication 4 Parameterization of the Modbus Communication General Information For the communication via the integrated PN interface of the PLC.0 Connection 2: Connection parameters +714.

e.g. The functions TCON and TDISCON can establish and terminate a connection by means of these parameters. The second possibility is to edit the parameters in the structure in the data block with the editor of STEP7. You can find the wizard at http://support. A detailed structure can be found in section 4. 4. Manual edition 2.2. The structure of the connection parameter block is obligatory und may not be changed.Parameterisation of the Modbus Communication Connection Parameters The parameters of the connection are defined in the first block. Otherwise it becomes impossible to set up a connection. Modbus Parameters The Modbus parameters define the mode of communication and the address reference. Alternatives for Parameterization There are two alternatives for a parameterization of the connection and Modbus parameters. It is recommended to use the wizard for the parameterization of the block MODBUS_PARAM. The first one is to use a Wizard. .com/WW/view/en/31535566.siemens. The complete structure (connection parameters and Modbus parameters) is created.1 Parameterization with the Wizard General Information With the wizard Modbus TCP Wizard you can easily parameterize the connection parameters as well as the Modbus parameters in the parameter data block MODBUS_PARAM.1 and 4. the used local interface and the IP address of the communication partner. how many register or bit areas are mapped to which DB or the differentiation between the S7 acting as server or as client. MODBUS / TCP communication via the integrated PN interface of the CPU 2XV9450-1MB02.g. The structure of the parameter DB has to remain unchanged to ensure proper communication.2. The two opportunities are described in detail in the following sections 4. which offers an easy way to setup the connection parameters. e.4 4-2 .automation.

The parameter of data block MODBUS_PARAM must not be changed during runtime. TSEND.4 4-3 . This ID must be unique within the complete parameter data block and has to be parameterized during the call of FB MODBUSPN.Parameterisation of the Modbus Communication 4. Structure of and Adaption of Connection Parameters For each logical connection one structure is required. It is used for the internal calls of the T blocks (TCON. TRCV and TDISCON). If the number is already used. rename the DB. Fixed value: id W#16#40 A connection ID is assigned to each logical connection. Value range: W#16#1 to W#16#FFF MODBUS / TCP communication via the integrated PN interface of the CPU 2XV9450-1MB02.2 Editing the Parameterization Procedure Copy DB2 of the library Modbus_PN_CPU and insert them in your project. Manual edition 2. block_length This parameter describes the length of the connection parameters and must not be changed. It is necessary to restart the PLC after the modification of MODBUS_PARAM.

no IP address is required for the partner. CPU 319. IM 151-8 PN/DP CPU CPU315 or 317 CPU319 CPU414 or CPU416 local_tsap_id_len TRUE FALSE B#16#1 B#16#2 B#16#3 B#16#5 The length of the parameter local_tsap_id (= local port number) is defined here.siemens. the IP address of the communication partner. It is recommended that the Modbus client performs an active connection establishment while the Modbus server establishes passive connections. is defined here. PN interface of the PLC: B#16#0 MODBUS / TCP communication via the integrated PN interface of the CPU 2XV9450-1MB02. Active connection establishment: Passive connection establishment: 0 2 rem_subnet_id_ len This parameter is currently not used. i. rem_staddr_len The length of rem-staddr. Active connection establishment: Passive connection establishment: next_staddr_len 2 0 This parameter defines the length of next_staddr as the distinction between the communication running via an external CP or via the integrated PN interface of the PLC.com/WW/view/en/24294554 active_est This parameter defines the way the connection is established (active or passive). The value depends on the PLC.4. Active connection establishment: Passive connection establishment: local_device_id The local_device_id defines the IE interface of the used PN PLC. The following values are necessary with the different PLC types.e.3 B#16#11 with CPU315 and 317 >= FW V2.4 4-4 . IM 151-8 PN/DP CPU. Manual edition 2. TCP (compatibility mode): TCP: B#16#01 with CPU315 and 317 <= FW V2. You can find further information on the internet: http://support. Please assign the value B#16#0. Unspecified connection: Specified connection: rem_tsap_id_len B#16#0 B#16#4 This parameter defines the length of rem_tsap_id. It is used by the function TCON when establishing the connection. the port number of the remote communication partner. CPU 414 and CPU416 The values vary depending on the used firmware.Parameterisation of the Modbus Communication connection_type The structure of the connection is defined here.automation. If an unspecified connection is to be used.

rem_staddr In this array of bytes. Example: IP address 192. assign 0 to this parameter.168. rem_staddr[4] = B#16#01 (1). MODBUS / TCP communication via the integrated PN interface of the CPU 2XV9450-1MB02. rem_staddr[5-6]= B#16#00 (reserved) With connection_type B#16#11 rem_staddr[1] = B#16#C0 (192). With connection_type B#16#01 local_tsap_id[1] low byte of the local port number in hexadecimal local_tsap_id[2] high byte of the local port number in hexadecimal local_tsap_id[3-16] B#16#00 With connection_type B#16#11 local_tsap_id[1] high byte of the local port number in hexadecimal local_tsap_id[2] low byte of the local port number in hexadecimal local_tsap_id[3-16] B#16#00 rem_subnet_id This parameter is currently not used. rem_staddr[2] = B#16#A8 (168). The value range depends on the PLC. The representation depends on the parameter connection_type.4 4-5 . rem_staddr[4] = B#16#C0 (192). Manual edition 2. rem_staddr[3] = B#16#00 (0). With connection_type B#16#01 local_tsap_id[1] low byte of the remote port number in hexadecimal local_tsap_id[2] high byte of the remote port number in hexadecimal local_tsap_id[3-16] B#16#00 With connection_type B#16#11 local_tsap_id[1] high byte of the remote port number in hexadecimal local_tsap_id[2] low byte of the remote port number in hexadecimal local_tsap_id[3-16] B#16#00 next_staddr This parameter defines rack and slot of the corresponding CP. When using the integrated PN interface of the PLC. rem_staddr[2] = B#16#00 (0). The representation depends on the parameter connection_type. the IP address of the remote communication partner is defined.1: With connection_type B#16#01 rem_staddr[1] = B#16#01 (1). rem_staddr[3] = B#16#A8 (168). Please assign the value B#16#0. The representation depends on the parameter connection_type. When an unspecified connection is used. The value range depends on the PLC.0. The port number has to be unique within the PLC. no IP address has to be entered. next_staddr[1-6] spare B#16#00 Reserved.Parameterisation of the Modbus Communication local_tsap_id This parameter defines the local port number. assign 0 to this parameter. rem_staddr[5-6]= B#16#00 (reserved) rem_tsap_id This parameter defines the remote port number.

server_client TRUE: S7 is server FALSE: S7 is client single_write In operating mode “S7 is client” and single_write = TRUE write requests with length 1 are carried out with the function codes 5 and 6. Manual edition 2.4 4-6 . With single_write = FALSE all write requests use the function codes 15 and 16. MODBUS / TCP communication via the integrated PN interface of the CPU 2XV9450-1MB02.Parameterisation of the Modbus Communication Adaption of the Modbus Parameters The Modbus parameters in the block MODBUS_PARAM define the mode of operation of the Modbus communication and the address reference of Modbus addresses and SIMATIC addresses.

this data area is not used Identifier Data type Size 0 Area not used 1 Coils Bit 2 Inputs Bit 3 Holding Register Word 4 Input Register Word The parameter db_x defines the number of the data block in which the consecutively defined MODBUS registers or bits are mapped. This has to be taken into account during the parameterization. Manual edition 2. 0 cannot be used as DB number since it is reserved for system functions. FALSE: establish connection when ENQ_ENR=TRUE TRUE: establish connection immediate after PLC start-up When connect_at_startup = TRUE. Even if consecutive register numbers or coils are located in two different DBs.65535 (W#16#0001 to W#16#FFFF) MODBUS / TCP communication via the integrated PN interface of the CPU 2XV9450-1MB02.Parameterisation of the Modbus Communication connect_at_ startup This parameter defines the point in time at which the connection is being established. At least the first data area has to be defined. Depending on the type of request. two requests are necessary to access them both. With one request. these memory areas are read or written. db_x DB-Number 1 . If data_type_x set to 0. data_type_x db_x The parameter data_type_x defines the MODBUS data type which is to be mapped with this definition. the first request should be started after the connection was established (CONN_ESTABLISHED = TRUE) or an error has been reported respectively (ERROR =TRUE). The other 7 data areas are optional. 8 Data Areas 8 data areas are available to map the Modbus addresses in the S7 storage.4 4-7 . It is possible to map more Modbus values (registers or coils) in one data block than could be processed with one telegram. only one DB can be accessed.

MODBUS / TCP communication via the integrated PN interface of the CPU 2XV9450-1MB02. start_x.4 4-8 . the number of the data element of the S7 DB in which the last bit is mapped. can be calculated with the following formula: DBW number = (end_x – start_x) ∗ 2 When accessing coils or inputs. In case of an error occurring. In section 6. internal_recv_ buffer This array is used internally for the received data within the FB. End_x defines the of the last MODBUS address.Parameterisation of the Modbus Communication start_x end_x Start_x specifies the first register or bit address. Manual edition 2. The parameter end_x must not be smaller than start_x. one Modbus address (1 register or 1 bit) is allocated.3 you can find an example of the mapping of the MODBUS addresses to S7 memory areas. which is stored in the data element 0 of the DB. When start_x is equal to end_x. Accessing or changing the array is inadmissible. the initialization of the FB is stopped with an error. can be calculated with the following formula: DBB number = (end_x – start_x +7) / 8 The defined memory areas must not overlap. When accessing registers. Accessing or changing the array is inadmissible. the number of the data element of the S7 DB in which the last register is mapped. end_x MODBUS address 0 to 65535 (W#16#0000 to W#16#FFFF) internal_send_ buffer This array is used internally for message data within the FB.

The licensing takes place in two steps: reading the IDENT_CODE and declaring the registration key REG_KEY.4 5-1 . Transfer the program to the PLC and turn it to RUN mode. Monitoring the block via the button is insufficient. 2. „Data block“ -> „Open Online“ to open the DB.Licensing 5 Licensing General The block MODBUSPN must be licensed for each CPU individually. MODBUS / TCP communication via the integrated PN interface of the CPU 2XV9450-1MB02. Open the instance DB of the block MODBUSPN. Manual edition 2. Parameterize the block in the cyclic OB (OB1 or cyclic interrupt OB) and in OB100 according to your requirements. The OB121 must be available in the CPU. Read the IDENT_CODE To read the IDENT_CODE please proceed as follows: 1.

The output IDENT_CODE shows an 18 character string. 4.4 5-2 . Copy this string per copy/paste from the DB und and insert it in the form IT4Industry SOFTWARE REGISTRATION FORM. of the product package into the form.com. Please send the form per e-mail to IT4Industry it4. MODBUS / TCP communication via the integrated PN interface of the CPU 2XV9450-1MB02. Insert the License-No.. Hereupon you will receive the registration key for your PLC. Manual edition 2. This form is stored in the library path .Licensing 3.\Program Files\Siemens\Step7\S7LIBS\Modbus_PN_CPU during installation and is also available on the installation CD.industry@siemens.

Via this global DB all MODBUSPN blocks can receive the registration key (See also the following example). Transfer the changed blocks to the PLC. Manual edition 2. 2. The block is now licensed for this CPU. rename the license DB. Declare the registration key in the data block as “initial value” to avoid a repeated insertion after reloading the PLC. Choose in the menu “Edit > Initialize Data Block” – all values of the column “initial value” are copied to “actual values”. 3. 5. Copy the prepared license block DB3 of the library “Modbus_PN_CPU“ into your project. The registration key REG_KEY should be stored in a global DB. Assign the value “DB3. MODBUS / TCP communication via the integrated PN interface of the CPU 2XV9450-1MB02. Change over to the data view via the menu “View” -> “Data View”. Please proceed as follows to declare the registration key REG_KEY: 1. A STOP -> RUN transition is not necessary. Open the data block in the SIMATIC manager with the editor in the declaration view. If the DB number is already used in your project. 4.Licensing Declaration of the Registration Key REG_KEY The registration key REG_KEY must be declared for each call of the block MODBUSPN.4 5-3 .REG_KEY” to the parameter REG_KEY of the block MODBUSPN. The registration key can be set at run time. Open the license DB and copy the 17 digit registration key you received from IT4industry to the column “Initial value”.

If this error code is shown although the registration key has been inserted. the SF LED (S7-300 and IM151-8) or the INTF LED (S7-400) of the CPU is flashing. Manual edition 2. _____________________________________________________________ Modbus communication is carried out even with a missing or wrong registration key. but the output STATUS_MODBUS is set to W#16#A090 “no valid license”. A cyclic error message regarding the missing license is displayed in the diagnostic buffer too. The error number of the missing license is W#16#A090. please check if the FC “EQ_STRING” is copied into the project.4 5-4 .Licensing Missing or Wrong Licensing When the registration key is missing or a wrong one is detected. if the OB121 is not available. _____________________________________________________________ Warning ! The CPU will turn to STOP mode. MODBUS / TCP communication via the integrated PN interface of the CPU 2XV9450-1MB02.

MODBUS / TCP communication via the integrated PN interface of the CPU 2XV9450-1MB02. the block MOD_SERV executes the function of Modbus server and the block TCP_COMM handles the connection management. The block MOD_CLI comprises the function of Modbus client. 5. The blocks provide the following functions: Online-Help • Connection and data handling by means of T blocks of the standard library • Generation of MODBUS-specific telegram header before sending • Verification of the MODBUS-specific telegram header when receiving • Verification whether the memory areas requested by the client exist • Generation of exception telegrams when errors occur (only when S7 is in server mode) • Data transfer to and from the parameterized DB • Time monitoring of the data reception as well as connection establishment and termination • Verification of the registration key The SIMATIC Manager provides an online help for the function block MODBUSPN. 4. Manual edition 2. Mark the FB and press “F1” so that he online help is displayed. It contains the main information on the FB.4 6-1 . 2.Function Block MODBUSPN 6 Function Block MODBUSPN 6. 15 and 16 are supported. the FB can be operated either in client or in server mode. Depending on the parameterization.1 Functionality of the FB General Information The function block MODBUSPN enables a communication between a PLC with integrated PN interface and a partner which supports Open MODBUS/TCP. 3. 6. The block MODBUSPN calls the blocks MOD_CLI (FB104) and MOD_SERV (FB105) internally. In the server operating mode. The function codes 1. the functionality multitasking in the sense of the MODBUS specification is not implemented.

A coexistent call of FB MODBUSPN in OB1 and a cyclic interrupt OB. The OB121 must be available in the CPU. MOD_SERV and TCP_COMM must not be called additionally in an organization block. ____________________________________________________________ Warning ! The CPU will turn to STOP mode. changes to the runtime parameters are ignored. You will find more information regarding this matter in section 5 “Licensing“. Start-up of the FB Cyclical Operation of the FB OB121 “Programming Error” The function block MODBUSPN is unconditionally called once in OB100.g. e. the OB121 is called. • The runtime parameters are not evaluated during the start-up. • The initialization parameters are copied into the instance DB. if the OB121 is not available. • While a request is being processed. • The values of the parameter data block MODBUS_PARAM are evaluated. OB35 is not permissible. _____________________________________________________________ MODBUS / TCP communication via the integrated PN interface of the CPU 2XV9450-1MB02.Function Block MODBUSPN Call of the FB For a correct program sequence the function block MODBUSPN has to be called in 2 organization blocks: • OB100 Start-Up and Cyclic OB (OB1 or cyclic interrupt OB. the FB MODBUSPN is called in OB1 or in a cyclic interrupt OB.4 6-2 . the functions of the function block are activated. e. • In the cyclical operation mode. Manual edition 2. initialization parameters are ignored. • The initialization parameters must be set according to the station configuration.g. OB35) The subordinate blocks of the Modbus library MOD_CLI. If the block has not been licensed yet. • Corresponding to the runtime parameters. In case of cyclical operation.

it is possible to define whether the PLC performs active or passive connection establishment. Multiple Communication Partners A PN PLC can establish multiple connections to various communication partners. Correspondingly. active and passive. MODBUS / TCP communication via the integrated PN interface of the CPU 2XV9450-1MB02.4 6-3 . It is recommended explicitly that the Modbus client executes the active establishment. To ensure a proper operation and data transfer. the calls of the FB MODBUSPN in the OB100 and in the OB1 receive the same instance DB for one connection. there are the following requirements for each connection: • • • one connection parameter block and the related Modbus parameter in DB MODBUS_PARAM call of FB MODBUSPN in OB100 call of FB MODBUSPN in OB1 or cyclic interrupt OB In this case. The relevant information is read from the connection parameters of DB MODBUS_PARAM. The point in time at which the connection is established is defined in DB MODBUS_PARAM (parameter connect_at_startup).Function Block MODBUSPN Connection Handling Active connection establishment can be carried out by the Modbus client as well as the Modbus server. With a parameter of the connection parameter block (active_est). During runtime the function TCON establishes the connection to the communication partner for both types of connections. The termination of the connection is defined with the parameter DISCONNECT of FB MODBUSPN. a strict division of the different connections to the corresponding communication partners is inevitable. Manual edition 2. A different instance DB is required for each additional connection.

When an error is recognized during verification. MODBUS / TCP communication via the integrated PN interface of the CPU 2XV9450-1MB02. the ERROR bit is set and an error number is returned at the output STATUS. a MODBUS request telegram is generated and sent to the partner station via the TCP/IP connection. a validity check is carried out. LENGTH. the activated request is terminated with an error. DATA_TYPE. TI and WRITE_READ. The error number is returned in STATUS_MODBUS. Manual edition 2. Activation of the Function Block S7 is Server With the signal TRUE at the trigger input ENQ_ENR. the response telegram is sent. LENGTH. The output DONE_NDR is set. The completed transmission is reported to the user by setting the DONE_NDR bit. the request is terminated with an error. Depending on the input parameters UNIT. DATA_TYPE. The received telegram is verified. TI and WRITE_READ. After the receipt of the response telegram. START_ADDRESS. If the result is positive.Function Block MODBUSPN Initiate Request S7 is Client A rising edge at the trigger input ENQ_ENR initiates a request. the FB is ready to receive a request telegram from the client. An erroneous request telegram causes an error message and the ERROR bit is set. The client waits for the parameterized monitoring time RECV_TIME for a response from the server. the completed function is indicated at the outputs UNIT. At this point. the necessary actions are taken and the request is terminated without error.4 6-4 . The server remains passive and waits for a telegram from the client. The request of the client is not answered. A new request can be initiated. When the monitoring time elapses (no response from the server). If the verification result is positive. START_ADDRESS.

TSEND or TRCV) no Job processing TRUE No job processing active FALSE CONN_ ESTABLISHED OUT BOOL Connection established Connection terminated TRUE FALSE no DONE_NDR OUT BOOL S7 is Client: TRUE: Active request finished without errors TRUE FALSE no S7 is Server: TRUE: Request from the client was executed and answered MODBUS / TCP communication via the integrated PN interface of the CPU 2XV9450-1MB02. Type Description ID IN Connection ID.Function Block MODBUSPN 6. must be identical to the associated parameter in the local connection description WORD Value range Init 1 to 4095 yes W#16#1 to W#16#FFF DB_PARAM IN BLOCK_ Number of the parameter DB DB depending on PLC yes RECV_TIME IN TIME T#20ms to T#+24d20h31 m23s647ms no T#20ms to T#+24d20h31 m23s647ms no TRUE FALSE no TRUE FALSE no Character no Monitoring Time: wait for data from communication partner Shortest adjustable time: 20 ms. Manual edition 2.4 6-5 . CONN_TIME IN TIME Monitoring Time: wait for establishing or termination of the connection Shortest adjustable time: 100 ms. TDISCON.2 Parameters of the Function Block MODBUSPN Parameter Decl. KEEP_ALIVE IN TIME Not used ENQ_ENR IN BOOL S7 is Client: Initiate request at positive edge S7 is Server: Ready to receive at TRUE signal DISCONNECT IN BOOL S7 is Client: TRUE: connection is terminated after reception of response S7 is Server: TRUE: connection is terminated when ENQ_ENR = FALSE REG_KEY IN LICENSED OUT BOOL BUSY STRING [17] OUT BOOL Registration key to activate the license License state of the function block: Block is licensed Block is not licensed no TRUE FALSE Operating state of the T functions (TCON.

OUTPUT if in SERVER mode) TRUE FALSE MODBUS / TCP communication via the integrated PN interface of the CPU 2XV9450-1MB02. which causes the error at STATUS_MODBUS or STATUS_CONN Character no IDENT_CODE OUT STRING [18] Identification for licensing Please order your license with this identification string. Character no UNIT IN/ BYTE OUT Unit identification (INPUT if in CLIENT mode. OUTPUT if in SERVER mode) TI WRITE_ READ B#16#0 to B#16#FF no 1 2 3 4 0 to 65535 no Coils Reading function Writing function 1 to 2000 1 to 1968 Inputs Reading function 1 to 2000 Holding Register Reading function Writing function 1 to 125 1 to 123 Input Register Reading function 1 to 125 IN/ WORD OUT Transaction Identifier (INPUT if in CLIENT mode.Function Block MODBUSPN Parameter Decl. OUTPUT if in SERVER mode) DATA_TYPE Coils Inputs Holding registers Input registers START_ ADDRESS IN/ WORD OUT MODBUS start address (INPUT if in CLIENT mode. OUTPUT if in SERVER mode) 0 to 65535 IN/ BOOL OUT Write access or Read access (INPUT if in CLIENT mode. OUTPUT if in SERVER mode) LENGTH IN/ WORD OUT Number of values to be processed (INPUT if in CLIENT mode. OUTPUT if in SERVER mode) 0 to 255 no IN/ BYTE OUT Data type to be accessed: (INPUT if in CLIENT mode. Manual edition 2. Type Description Value range Init ERROR OUT BOOL An error has occurred TRUE no No error has occurred FALSE STATUS_ MODBUS OUT WORD Error number for protocol errors when evaluating a Modbus telegram 0 to FFFF no STATUS_ CONN OUT WORD Error number for connection errors during execution of the T blocks (TCON.4 no W#16#0000 to W#16#FFFF no W#16#0 to W#16#FFFF no 6-6 . TDISON) 0 to FFFF no STATUS_FUNC OUT STRING [8] Name of the function. TRCV. TSEND.

4 6-7 . it is not advisable to modify the input parameters while a request is active. A modification of the initialization parameters during run mode has no impact. Wait with the next request and the change of the parameters until the previous request ends with DONE_NDR or ERROR. MODBUS / TCP communication via the integrated PN interface of the CPU 2XV9450-1MB02. the output parameters may only be evaluated when DONE_NDR is TRUE. i. during the test phase). The output parameters are displayed dynamically.Function Block MODBUSPN General Information The parameters of the FB MODBUSPN can be divided into two groups: • Initialization parameters • Runtime parameters Initialization parameters are evaluated only during the call of OB100 and are adopted into the instance DB. PLC-specific restrictions must be taken into consideration.g. In the operation mode S7 is server. In the mode S7 is client.e. they are only available for one PLC cycle. They are marked with “yes“ in the column “INIT“ in the table displayed above. Manual edition 2. Runtime parameters can by modified during the cyclical operation. the instance DB must be initialized again via a STOP Æ RUN transition of the PLC. After a modification of these parameters (e. They have to be copied to an additional memory area if you need to process them or to display the values in a VAT (STEP7 variable table). Range of Values For the range of values of the different parameters.

which are necessary for the communication between the PN PLC and the Modbus device. This connection ID is defined in the connection parameter block. an indication RECV_TIME < 20 ms causes an error message and the request is rejected. In the operating mode S7 is server. MODBUS / TCP communication via the integrated PN interface of the CPU 2XV9450-1MB02. This parameter is declared in plain text: “DBxy“. 0 cannot be used as a DB number since it is reserved for system functions. This parameter data block includes the connection parameters and the Modbus-specific parameters. It is also possible to use different parameter data blocks for multiple connections. The connection ID defined in the connection parameter block has to be entered here and must be unique within the PLC. the corresponding error code is displayed at the output STATUS_CONN. an error is reported. CONN_TIME < 100ms causes an error message and the request is rejected. RECV_TIME The monitoring time RECV_TIME observes the data input from the communication partner.2s. an indication RECV_TIME < 20 ms causes the use of the default time of 1. Manual edition 2.Function Block MODBUSPN ID To each connection between the PN PLC and a communication partner a connection ID is assigned. The connection ID unambiguously specifies the connection between the PLC and the communication partner. In order to receive a Modbus telegram. The range of values for this parameter depends on the PLC. In the operating mode S7 is server. the RECV_TIME is triggered. The ID can be set to values between 1and 4095. During cyclic operation in the operating mode S7 is client. When the time RECV_TIME elapses. the active request is cancelled with an error. an indication CONN_TIME < 100 ms causes the use of the default time 5s. The RECV_TIME monitors the duration of the TCP stream. When operating various connections an individual ID is required for each logical connection. The shortest adjustable time is 20 ms. TRCV has to be called twice.4 6-8 . When CONN_TIME elapses. which is part of the parameter data block MODBUS_PARAM. With each call of TRCV. CONN_TIME The monitoring time CONN_TIME observes the connection establishment and the connection termination. If the monitoring time elapses. The monitoring time is started with the call of TRCV and stopped after the receipt of the telegram segment. DB_PARAM The parameter DB_PARAM assigns the number of the data block MODBUS_PARAM. The shortest adjustable time is 100 ms. The parameter data block can contain a sequence of parameters for several connections. This is also true for the operating mode S7 is client with connect_at_startup = TRUE. In the operating mode S7 is client. The interval between two requests is not taken into consideration.

then the Modbus block is licensed on this CPU. CONN_ ESTABLISHED CONN_ESTABLISHED indicates that a connection to the communication partner is established and data can be transferred. the connection establishment is activated. MODBUS / TCP communication via the integrated PN interface of the CPU 2XV9450-1MB02. TI and WRITE_READ. Manual edition 2. BUSY If this output is TRUE. With a FALSE signal at the input and an established connection.Function Block MODBUSPN ENQ_ENR Operating mode S7 is Client: The data transfer is initiated with a TRUE edge at the input. one of the T functions TCON. the connection to the communication partner is not established. Telegrams from the client can be received. REG_KEY The block MODBUSPN must be licensed for each CPU individually to permit a correct program sequence. none or a faulty license string was entered. You can find further information in section 5 “Licensing”. If the connection is not established (CONN_ESTABLISHED = FALSE). DATA_TYPE. This parameter is a runtime parameter and can be set optionally according to your requirements. LICENSED If this output is TRUE. The request telegram is generated with the values of the input parameters UNIT. With the registration key REG_KEY the block MODBUSPN is licensed and the Modbus communication runs without any restraint. When the parameter ENQ_ENR turns from TRUE to FALSE. In the operating mode S7 is server. START_ADDRESS. the parameter DISCONNECT = TRUE indicates that the connection is terminated when the parameter ENQ_ENR is set to FALSE. data is received from the client and discarded. Operating mode S7 is Server: The FB is activated with a TRUE signal at the input. If CONN_ESTABLISHED is set to FALSE. the connection may be terminated depending on the parameter DISCONNECT. the connection establishment is carried out first and then the data transfer takes places. LENGTH. If the output is FALSE. DISCONNECT In the operating mode S7 is client. TSEND or TRCV is running. the parameter DISCONNECT = TRUE indicates that the connection is terminated after the completed data transfer. A new request may only be initiated when the previous one is ended with DONE_NDR or ERROR.4 6-9 . If the connection is not established (CONN_ESTABLISHED = FALSE). TDISCON.

the STATUS_MODBUS output displays the error number regarding the processing of Modbus telegrams. STATUS_MODBUS When ERROR is TRUE. the response data from the server has already been entered into the DB. which caused the error occurred. DATA_TYPE. The FB copies this value to the request telegram and verifies when receiving the respond telegram. which can be read by means of a variable table? You can find further information in section 5 “Licensing”. STATUS_CONN When ERROR is TRUE. In the parameters UNIT. The output is set with the received value when the job is finished without an error. TSEND and TRCV. ERROR When this output is set. STATUS_FUNC This parameter shows the name of the function. the parameter UNIT is an output parameter. In the operating mode S7 is Server. LENGTH. TDISCON. The error number is displayed in the STATUS_MODBUS or STATUS_CONN output. UNIT In mode S7 is Client. The error numbers are described in section 7 and in the STEP7 online help of the functions TCON. the response to the request telegram has been received from the server. The FB copies this value from the request telegram to the respond telegram. the activated request was executed without an error. These outputs are only available and valid as long as DONE_NDR is TRUE. With a writing function. an error was detected at a request telegram of the client or when sending a response telegram. MODBUS / TCP communication via the integrated PN interface of the CPU 2XV9450-1MB02. In the operating mode S7 is Client. In the operating mode S7 is Client. With a reading function. the STATUS_CONN output displays the error number regarding the processing of the T functions. This input has to be set according to your requirements. The error number is displayed in the STATUS_MODBUS or STATUS_CONN output. In mode S7 is Server. this output indicates a telegram exchange without errors. After start-up of the PLC an 18 character string is displayed. IDENT_CODE With the identification string IDENT_CODE you can order the registration key at IT4industry. START_ADDRESS. the activated request was ended with an error. In this case. the ERROR bit is set to FALSE. an error was recognized. Status information like “job processing active” is provided by STATUS_CONN as well. In the operating mode S7 is Server. the parameter UNIT is an input parameter.Function Block MODBUSPN DONE_NDR The parameter DONE_NDR indicates an error-free execution of the request.4 6-10 . The error numbers are described in section 7. TI and WRITE_READ the request parameters of the client are displayed. Manual edition 2.

4 6-11 . In the operating mode S7 is Server. this is an output parameter. In the operating mode S7 is Client. this is an input parameter. For each telegram. Data type START_ADDRESS DATA_ TYPE Function Length single_ write Function code Coils 1 read any irrelevant 1 Coils 1 write 1 TRUE 5 Coils 1 write 1 FALSE 15 Coils 1 write >1 irrelevant 15 Inputs 2 read any irrelevant 2 Holding Register 3 read any irrelevant 3 Holding Register 3 write 1 TRUE 6 Holding Register 3 write 1 FALSE 16 Holding Register 3 write >1 irrelevant 16 Input Register 4 read any irrelevant 4 The parameter START_ADDRESS specifies the first MODBUS address that is read or written. With a reading function. MODBUS / TCP communication via the integrated PN interface of the CPU 2XV9450-1MB02. this is an input parameter. LENGTH The parameter LENGTH specifies the number of MODBUS values that are read or written. all registers or bits have to be in the same DB. Manual edition 2. this is an output parameter. DATA_TYPE is an output parameter. In the operating mode S7 is Server. In the operating mode S7 is Server.Function Block MODBUSPN DATA_TYPE The parameter DATA_TYPE defines which Modbus data type is to be accessed with the current job. a maximum of 123 registers or 1968 bits is possible. a maximum of 125 registers or 2000 bits is possible per telegram. The different data types are related directly to the used function codes. DATA_TYPE is an input parameter. With a writing function. In the operating mode S7 is Client. The following data types are available: Coils Inputs Holding Register Input Register B#16#1 B#16#2 B#16#3 B#16#4 In the operating mode S7 is Client.

The value TRUE specifies the writing mode. 6. The Holding Register with offset 0.g.3 Example of Address Mapping Interpretation of MODBUS Register Addresses The MODBUS data model is based on a series of storage areas with distinct properties. The FB MODBUSPN can only perform this function properly if the TI is changed with each transaction. Manual edition 2. WRITE_READ This parameter defines whether a reading or writing function is to be carried out. In the operating mode S7 is Server.4 6-12 . Therefore. is called 40001 (memory type 4xxxx. the reading mode is specified. Only a change of the TI ensures a reliable operation of the FB. it is possible to use register or bit addresses from von 0000H to FFFFH for each function code. The FB copies this value from the request telegram into the respond telegram. this is an output parameter. this is an input parameter. MODBUS / TCP communication via the integrated PN interface of the CPU 2XV9450-1MB02. A potential source of confusion is the varying interpretation of the register address in different manuals. distinguish these areas by the register or bit addresses. Some systems. Sometimes the register or bit address is defined as the address of the application layer and in other manuals it is the actually transferred address. for example. If the value of the input/output is FALSE. reference 0001). MODICON PLCs. e. In the operating mode S7 is Server. this is an input parameter. The FB copies this value to the request telegram and verifies it when receiving the respond telegram. The Transaction Identifier is used for the identification of telegrams and the unambiguous allocation of the requests to the corresponding responds. this is an output parameter.Function Block MODBUSPN The parameter TI (Transaction Identifier) is copied by the server from the request telegram to the respond telegram according to the MODBUS specification. The FB MODBUSPN uses the register or bit address transferred for its parameters start_x. TI In the operating mode S7 is Client. end_x und START_ADDRESS. Therefore. we recommend increment the TI by 1 with any request. In the operating mode S7 is Client.

The SIMATIC addresses printed in black are the offset in the DB.4 6-13 . The diagram is based on the parameterization in the table above.Function Block MODBUSPN Example: Parameterization of the Memory Areas Address Mapping data_type_1 db_1 start_1 end_1 data_type_2 db _2 start _2 end _2 data_type_3 db _3 start _3 end _3 data_type_4 db _4 start _4 end _4 data_type_5 db _5 start _5 end _5 data_type_6 db _6 start _6 end _6 data_type_7 db _7 start _7 end _7 data_type_8 db _8 start _8 end _8 B#16#3 W#16#B W#16#1 W#16#1F4 B#16#3 W#16#C W#16#2D0 W#16#384 B#16#4 W#16#D W#16#2D0 W#16#3E8 B#16#0 0 0 0 B#16#1 W#16#E W#16#280 W#16#4E2 B#16#2 W#16#F W#16#6A4 W#16#8FC B#16#1 W#16#10 W#16#6A4 W#16#8FC B#16#0 0 0 0 Holding Register DB 11 Start address: 1 End address: 500 Holding Register DB 12 Start address: 720 End address: 900 Input Register DB 13 Start address: 720 End address: 900 Not used 0 0 0 Coils DB 14 Start address: 640 End address: 1250 Inputs DB 15 Start address:1700 End address: 2300 Coils DB 16 Start address: 1700 End address: 2300 Not used 0 0 0 The following diagram shows a comparison of the SIMATIC memory area and the Modbus-typical register oriented storage arrangement. The Modbus addresses printed in black refer to the Data Link Layer and the ones printed in grey refer to the Application Layer. MODBUS / TCP communication via the integrated PN interface of the CPU 2XV9450-1MB02. Manual edition 2. you can find the Modbus register numbers printed in grey. Additionally.

1700 +74..0 499 +998.0 720 + 2..7 2299 +75.. +74..0 2300 10001 .0 721 0 1700 11701 1701 11702 ...7 2299 +75.0 2300 DB 15 + 0.Function Block MODBUSPN SIMATIC Modbus device DB 14 Coils (from 00001) + 0.0 2300 DB 13 + 0.0 2 .0 899 900 40901 +360....1 1701 1250 . 499 40500 500 40501 501 40502 ...4 6-14 ... 720 30721 721 30722 . Holding Register (from 40001) 1 02301 .0 640 + 0... 1000 + 0.0 720 + 2... . +358....0 01251 0 40001 1 40002 1000 31001 1001 31002 . +996... 40721 .....0 1700 + 0..1 641 0 . Inputs (from 10001) +560. + 0. ... Manual edition 2...0 900 901 40902 MODBUS / TCP communication via the integrated PN interface of the CPU 2XV9450-1MB02. 720 .. DB 11 01701 ..0 1700 + 0.2 00001 1250 640 00641 641 00642 DB 16 .0 500 DB 12 + 0.0 721 2301 02302 Input Register (from 30001) 0 30001 1 30002 ..1 1701 . +76. 2300 12301 2301 12302 + 2.

The instance data block contains parameters of the types input.4 Data and Standard Functions used by the FB Instance DB The function block MODBUS stores its data in an instance DB. This instance DB is created by STEP7 when initially calling the FB. Parameter DB The connection. Standard FBs for Data Transfer The function block TCP_COMM. MODBUSPN: SFCs for Miscellaneous Functions The FB MODBUSPN uses the following SFCs from the standard library: • FC10 • SFC6 “RD_SINFO“ • SFC20 “BLKMOV” • SFC24 “TEST_DB” • SFC51 “RDSYST” • SFC52 “WR_USMSG” “EQ_STRING” MODBUS / TCP communication via the integrated PN interface of the CPU 2XV9450-1MB02. Timers The FB does not use any timers. Flags The function block does not use any flags. Additionally. output and input/output as well as static variables required for its execution. TDISCON. Standard FBs for Connection Handling The function block TCP_COMM. The variables control the internal process flow of the FB. That is a total of max. Required memory of the instance-DBs: Instance-DB work memory load memory MODBUSPN ca.4 6-15 . called by MODBUSPN.Function Block MODBUSPN 6. 2 kByte Local Variables The FB requires 78 bytes of local variables. TSEND or TRCV use up to 28 bytes depending on the used function block. 160 bytes of local data for one FB MODBUSPN call. uses the blocks TCON and TDISCON of the standard library to establish and terminate the connection between the PLC and the communication partner.and Modbus-specific parameters are stored in the parameter data block MODBUS_PARAM. called by MODBUSPN. uses the blocks TSEND and TRCV of the standard library for the data transfer between the PLC and the communication partner. 1 kByte ca. These variables are remanent and keep their validity between FB calls. Manual edition 2. MOD_CLI (52 Byte) or MOD_SERV (28 Byte) and TCP_COMM require 2 bytes local variables and TCON.

Manual edition 2. which then calls FB65. MODBUS / TCP communication via the integrated PN interface of the CPU 2XV9450-1MB02.5 • SFC20 „BLKMOV“ • SFC24 “TEST_DB” • SFB4 „TON“ Renaming Standard Functions Inducement If the numbers of the standard functions are already assigned within your project or if the number interval is reserved for a different application. Exemplification: The call hierarchy in MODBUSPN: FB63 TSEND FB104 MOD_CLI FB102 MODBUSP FB64 TRCV FB103 TCP_COMM FB65 TCON FB105 MOD_SERV FB66 TDISCON Rewiring FB65 is possible: FB104 MOD_CLI FB103 TCP_COMM FB65 TCON Internally. function block FB104 calls function block FB103. FB64. It is not possible to rename the system functions SFC6. SFC24. SFC51.4 6-16 . In this line-up it is possible to rewire FB65 since it is called by TCP_COMM (FB103) which has a smaller function block number than MOD_CLI (FB104). MOD_SERV und TCP_COMM.Function Block MODBUSPN MOD_CLI and MOD_SERV: SFCs for Miscellaneous Functions The FBs MOD_CLI and MOD_SERV use the following SFCs from the standard library: TCP_COMM: SFCs for Miscellaneous Functions The FB TCP_COMM uses the following SFB from the standard library in addition to the T-blocks: 6. SFC52 and SFB4. Behavior A set of rules concerning the function block numbering have to be considered when rewiring function blocks in SIMATIC STEP 7 Manager: When rewiring a function block make sure that the previous function blocks in the call hierarchy have descending numbers. it is possible to rename the internally called function blocks FB63. FB65 and FB66 of FB TCP_COMM or the function blocks MODBUSPN. MOD_CLI. SFC20.

in order to re-wire the operands into free areas. Set the operand priority in the object properties of the block folder to "Absolute value". Manual edition 2. 3. Call the function "Extras > Re-wire" in the SIMATIC Manager. In this line-up it is not possible to rewire FB103. After this step rewiring TCP_COMM (FB103) will be possible. Solution: If FB103 is to be rewired. This is not necessary. it is necessary to temporarily assign a higher function block number to MODBUSPN (FB102) than MOD_CLI (FB104) has. since the function block MOD_CLI (FB104) has a higher function block number than MODBUSPN (FB102). Get the information about the used operand by clicking "Extras > Reference data > Display". Renaming To rename the blocks proceed as described subsequently: 1. To be able to keep on using the symbolism diagnostics tools. MODBUS / TCP communication via the integrated PN interface of the CPU 2XV9450-1MB02. which then calls FB103.Function Block MODBUSPN Rewiring FB103 is not possible: FB102 MODBUSPN FB104 MOD_CLI FB103 TCP_COMM Internally. add the modifications in the symbolism table supplementary. The modifications can be verified by clicking "Extras > Reference data > Display". function block FB102 calls function block FB104.4 6-17 . 4. 2. Afterwards MODBUSPN can have its original name reassigned. though.

The STATUS parameters can be evaluated in the user program. The STATUS_CONN output displays status information and error codes with regard to the processing of the T functions.4 7-1 . When reading the STATUS_MODBUS output. STATUS Outputs of the FB MODBUSPN For an error diagnosis. The display elements provide an overview of internal errors. The output STATUS_FUNC shows the name of the function. When reading the STATUS outputs. MODBUS / TCP communication via the integrated PN interface of the CPU 2XV9450-1MB02. Display Elements (LED) The display elements inform you about the operating mode or about the error conditions of the PLC. external errors and interface-specific errors. you are provided with a general indication of errors that occurred during the telegram processing and connection handling. which caused the error at STATUS_MODBUS or STATUS_CONN. The following diagnostic features are available: • Diagnosis via the display elements of the PLC • Diagnosis via the STATUS_MODBUS and STATUS_CONN output of the MODBUSPN function block. you are provided with a general indication of errors that occurred during the Modbus-specific telegram processing. Manual edition 2. the MODBUSPN function block has 3 STATUS outputs.Diagnosis 7 Diagnosis Diagnostic Function The diagnostic functions of the PN PLC enable a fast localization of errors.

1 Diagnosis via the Display Elements of the PLC Display Functions The display elements of the PLC provide information on the status of the component. • Special Displays PN CPU 300.Diagnosis 7. Manual edition 2.INTF Internal error When this LED is flashing. the Modbus block has not been licensed yet. PN-CPU 400 . the Modbus block has not been licensed yet.SF Group error When this LED is flashing.RX/TX a telegram is transferred via the integrated interface A detailed description of the display elements can be found in the device manual of the PLC. You can find further information in section 5 “Licensing”. MODBUS / TCP communication via the integrated PN interface of the CPU 2XV9450-1MB02. There are two types of display functions: • Group Error Displays PN CPU 300 .4 7-2 . PN CPU 400 and IM 151-8 PN/DP CPU: . You can find further information in section 5 “Licensing”.

Diagnosis 7. MODBUS / TCP communication via the integrated PN interface of the CPU 2XV9450-1MB02. start_x. With data_type_x = 0 the Modbus area is disabled and not further verified. there also is a check whether the data block specified by the register or bit address is available and has the necessary length. Modbus addresses for the same data type defined in two db_x lead to an error message (address overlap). end_x. Test end_x >= start_x 5. In the cyclical operation no requests are executed. Manual edition 2. Validity check of data_type_x 3. The DB number must not be 0 and/or identical to the number of MODBUS_PARAM or the instance DB.2 Verification by the FB MODBUSPN During Start-up • Unambiguousness of the id parameter in the connection parameters of DB MODBUS_PARAM • Parameter group data_type_x. db_x <> 0 4. • Receipt of the response telegram within the monitoring time The monitoring time can also elapse if less data than specified in the MODBUS telegram header is received. A correction of the parameterization and a STOP Æ RUN transition of the PLC are necessary. At least the first area (_1) has to be parameterized. Cyclical Operation S7 is Client Verification when the FB is called: • Valid registration key • DB MODBUS_PARAM is available with the necessary length • Range of values monitoring time RECV_TIME and CONN_TIME • Range of values START_ADRESS • Range of values LENGTH • When executing a request. (x = 1 to 8) 1. Subsequent errors with loss of telegrams can occur. db_x. Errors during start-up provoke the ERROR bit to remain set. 2.4 7-3 .

an exception telegram is sent.4 7-4 . • Protocol Identifier = 0 • Length between 6 and 207 • Received function code is verified. If the number is too large. • For write requests. • The number of registers or bits is verified. 15 or 16 an exception telegram is sent. 4. If the function code is not equal to 1. the start address and number of registers/bits have to match with the request telegram. there is also a check whether the data block specified by the register or bit address is available and has the necessary length. • FC 5 or FC6: Echo in the respond is equal to the request • Valid registration key • Receipt of the second part of the request telegram within the monitoring time The monitoring time can also elapse if less data than specified in the MODBUS telegram header is received. MODBUS / TCP communication via the integrated PN interface of the CPU 2XV9450-1MB02. • Sent UNIT is equal to the received one • Sent FC is equal to the received one • Response is an exception code telegram • For write requests. the number of registers or bits and the byte count in the telegram must match.Diagnosis Verification in the response telegram: Cyclical Operation S7 is Server • Received transaction identifier is equal to the sent one. In case of an error. the length in the header of the response telegram is checked for plausibility regarding the request. an exception telegram is sent. 3. Subsequent errors with loss of telegrams can occur. 5. • Protocol identifier = 0 • Length is between 3 and 253 Additionally. Manual edition 2. • During the execution of a request. 2. 6. The DB number must not be 0 or identical to the number of MODBUS_PARAM or the instance DB. the length in the header.

the FB terminates the connection: • Monitoring time for connection establishment exceeded • Monitoring time for receive exceeded • PI <> 0 • received TI different to sent TI • Length in the header does not match the length information in the telegram MODBUS / TCP communication via the integrated PN interface of the CPU 2XV9450-1MB02. Manual edition 2.4 7-5 .Diagnosis Termination of the Connection in Case of Error In special error situations.

bit values (end_x .start_x + 1) * 2 .start_x ) / 8 + 1 Extend the DB. Correct the length of MODBUS_PARAM A002 The parameter end_x is less than start_x. Only data type 1 or 3 can be written. called by MOD_CLI or MOD_SERV. STATUS_CONN and STATUS_FUNC. Error messages of FB MODBUSPN at the output STATUS_MODBUS STATUS Event text Remedy (Hex) A001 The parameter data block MODBUS_PARAM is too short. For further details on the error messages. The S7 sends an exception telegram. FB65 and FB66. STATUS_MODBUS displays the error numbers regarding the processing of Modbus telegrams. S7 is Client: Correct the parameters START_ADDRESS or LENGTH Other possible reasons: A004 • S7 is client: Wrong initialization parameter • S7 is server: Wrong address area in the request telegram of the client. Manual edition 2. FB64. SFC51 und SFC52. Correct the parameters. The error messages of these blocks are passed on to STATUS_CONN without any changes.register values (end_x . STATUS_FUNC shows the name of the function.4 7-6 . whereas STATUS_CONN displays the error numbers regarding the connection handling.3 Diagnosis Messages of the FB MODBUSPN Messages at the STATUS Outputs of the FB The block MOBUSPN has 3 status outputs: STATUS_MODBUS. Below you can find a list of FB-specific error messages. MOD_CLI and MOD_SERV use the standard functions SFC6. Minimum length: . The block TCP_COMM. which caused the error. SFC20. S7 is Server: Modify the request of the client. MODBUS / TCP communication via the integrated PN interface of the CPU 2XV9450-1MB02. FB63. The error messages of these blocks are passed on to STATUS_MODBUS without any changes. Applies only if S7 is client: An invalid combination of DATA_TYPE and WRITE_READ is given.Diagnosis 7. uses the standard blocks SFB4. Correct the parameterization in DB MODBUS_PARAM A003 The DB to which MODBUS addresses shall be mapped is too short. please consult the diagnosis buffer or the online help of the SIMATIC Manager. SFC24. STATUS is valid when ERROR is TRUE. Error Messages of the called SFCs and FBs The FBs MODBUSPN.

4 7-7 . CONN_TIME 100ms Correct the parameterization. The RECV_TIME has to be at least 20 ms. A007 Only if S7 is client: An invalid monitoring time RECV_TIME or CONN_TIME is parameterized. Verify the data of the communication partner with the help of a telegram trace. A00A Only if S7 is client: The received UNIT is not equal to the sent one. S7 is Server: The number of registers/bits in the request telegram is invalid. S7 is Server: Modify the number in the request telegram. A00D Only if S7 is client: The register or bit address respectively the number of registers or bits in the response telegram is not equal to the one in the request telegram. 4. S7 is Client: Correct the parameter LENGTH. S7 is Client: Correct the parameter combination DATA_TYPE. The S7 sends an exception telegram. The connection is terminated. A00C The received byte count does not match the number of registers. A00B S7 is client: Received function code is not equal to the sent one. LENGTH. The FB ignores all data. Range of values: Read coils/inputs: 1 to 2000 Write coils: 1 to 1968 Read registers: 1 to 125 Write holding registers: 1 to 123 A006 The given range of registers defined with DATA_TYPE. 15 and 16. START_ADDRESS. The S7 sends an exception telegram. S7 is client: Verify the data of the communication partner with the help of a telegram trace. Verify the data of the communication partner with the help of a telegram trace. S7 is server: The S7 sends an exception telegram. A009 Only if S7 is client: The received transaction identifier TI is not equal to the sent one. 5. S7 is server: An invalid function code was received. MODBUS / TCP communication via the integrated PN interface of the CPU 2XV9450-1MB02. START_ADDRESS and LENGTH does not exist in data_type_1 to data_type_8. 6. The connection is terminated. Manual edition 2. 2. S7 is Server: Modify the request of the client or correct the parameterization of data_type_x. A00E The length indicated in the MODBUS-specific telegram header does not match the number of registers/bits or the byte count in the telegram. The connection is terminated. 3.Diagnosis Error messages of FB MODBUS MODBUSPN at the output STATUS_MODBUS STATUS Event text Remedy (Hex) A005 S7 is client: An invalid value for the parameter LENGTH is given. S7 is server: The FB MODBUS only supports the function codes 1.

Correct the parameterization in DB MODBUS_PARAM. A028 The parameterized areas data_type_2 and data_type_5 overlap. Correct the parameterization in DB MODBUS_PARAM A024 The parameterized areas data_type_2 and data_type_4 overlap. DB 0 can’t be used. The data areas must not contain any overlapping register areas. The connection is terminated. A027 The parameterized areas data_type_2 and data_type_5 overlap. A011 An invalid value for DATA_TYPE is given (Value range: 1 Correct the parameters. Verify the data of the communication partner with the help of a telegram trace. A018 The parameterized areas data_type_1 and data_type_8 overlap.Diagnosis Error messages of FB MODBUSPN at the output STATUS_MODBUS STATUS Event text Remedy (Hex) A00F A protocol identifier <> 0 was received. Please contact the product support. The connection is terminated. A025 The parameterized areas data_type_2 and data_type_5 overlap. A01F The FB MODBUSPN has turned to an invalid state. MODBUS / TCP communication via the integrated PN interface of the CPU 2XV9450-1MB02. to 4). Correct the parameterization in DB MODBUS_PARAM. Correct the parameterization in DB MODBUS_PARAM. A010 In the parameters db_1 to db_8 a DB number is used twice. A034 The parameterized areas data_type_3 and data_type_4 overlap.4 7-8 . A016 The parameterized areas data_type_1 and data_type_6 overlap. A012 The parameterized areas data_type_1 and data_type_2 overlap. A023 The parameterized areas data_type_2 and data_type_3 overlap. A026 The parameterized areas data_type_2 and data_type_5 overlap. The data areas must not contain any overlapping register areas. A017 The parameterized areas data_type_1 and data_type_7 overlap. A019 0 is assigned to one of the parameters db_x while the according data_type_x is <> 0. A014 The parameterized areas data_type_1 and data_type_4 overlap. Manual edition 2. Verify the data of the communication partner with the help of a telegram trace. A015 The parameterized areas data_type_1 and data_type_5 overlap. A013 The parameterized areas data_type_1 and data_type_3 overlap. it is reserved for system functions. A01A Wrong length in the Modbus header (1 to 253 byte are valid).

A07E The DB number of db_x is identical to the number of the parameter DB MODBUS_PARAM or to the instance DB. A056 The parameterized areas data_type_5 and data_type_6 overlap. A037 The parameterized areas data_type_3 and data_type_7overlap. A045 The parameterized areas data_type_4 and data_type_5 overlap. Correct the parameterization in DB MODBUS_PARAM. A07D Parameter data_type_1 is not defined. A057 The parameterized areas data_type_5 and data_type_7 overlap. MODBUS / TCP communication via the integrated PN interface of the CPU 2XV9450-1MB02. A078 The parameterized areas data_type_7 and data_type_8 overlap. A07A An invalid value ID is parameterized. A079 The connection ID of parameter ID is not defined in DB MODBUS_PARAM. Correct the parameterization in DB MODBUS_PARAM A036 The parameterized areas data_type_3 and data_type_6 overlap. A07B The parameter ID exists twice in the parameter DB. Manual edition 2. A067 The parameterized areas data_type_6 and data_type_7 overlap. A048 The parameterized areas data_type_4 and data_type_8 overlap. A058 The parameterized areas data_type_5 and data_type_8 overlap. A07F The data block defined at DB_PARAM is no parameter DB for Modbus communication. A047 The parameterized areas data_type_4 and data_type_7 overlap. The length information in DBW0 was changed or a wrong DB was defined. Correct the parameterization at the input ID. A068 The parameterized areas data_type_6 and data_type_8 overlap. Range of values is 1 to 4095. The data areas must not contain any overlapping register areas. A038 The parameterized areas data_type_3 and data_type_8overlap.Diagnosis Error messages of FB MODBUSPN at the output STATUS_MODBUS STATUS Event text Remedy (Hex) A035 The parameterized areas data_type_3 and data_type_5 overlap.4 7-9 . A07C An invalid value data_type_x was given. A046 The parameterized areas data_type_4 and data_type_6 overlap. The value range is 0 to 4. The parameter area _1 is the default area and must be defined.

Restart the CPU after changing this parameter. Verify the project if there is any invalid write access to the license DB. A095 An exception telegram with an unknown exception code was received (only if S7 is client). doesn’t support the requested length). Verify the data of the communication partner with the help of a telegram trace. Manual edition 2. Wait with the initiation of a new request until the previous one was finished either with DONE/NDR = TRUE or ERROR = TRUE. A083 Only if S7 is client: A request was initiated prior to the completion of the previous one. A085 An error occurred during the license handling.g. A091 An exception telegram with exception code 1 was received (only if S7 is client) The communication partner does not support the requested function.4 7-10 . Please contact the Product Support. This is a status information. DB_PARAM is an initialization parameter. Verify the data of the communication partner with the help of a telegram trace. A090 The block MODBUSPN is not licensed for this CPU. Read the identification string IDENT_CODE for this CPU and order the registration key at IT4industry. A092 An exception telegram with exception code 2 was received (only if S7 is client) Correct LENGTH or START_ADDRESS at the call of the FB. in which the received request can’t be processed.Diagnosis Error messages of FB MODBUSPN at the output STATUS_MODBUS STATUS Event text Remedy (Hex) A080 The parameter DB_PARAM was changed without a restart of the CPU. A081 Only if S7 is client and function code 5: The received coil status is not equal to the sent one. A093 An exception telegram with exception code 3 was received (only if S7 is client) The communication partner can’t process the received request (e. The Modbus communication runs without a license as well. Check the error message of the communication partner and verify the data with a telegram trace if needed. A082 Only if S7 is client and function code 6: The received register value is not equal to the sent one. The bit ERROR is not set. Please contact the Product Support. See also section 5 “Licensing”. A084 The character string for identification “IDENT_CODE” could not be determined. A094 An exception telegram with exception code 4 was received (only if S7 is client) The communication partner is in a state. An attempt to an invalid or non existing address at the communication partner was made. MODBUS / TCP communication via the integrated PN interface of the CPU 2XV9450-1MB02.

When RECV_TIME is exceeded. Please contact the product support.4 7-11 . the connection is terminated.Diagnosis Error messages of FB MODBUSPN at the output STATUS_CONN STATUS Event text Remedy (Hex) A100 The monitoring time CONN_TIME or RECV_TIME was exceeded when executing a job. A101 The monitoring time of the TDISCON is exceeded. Check the parameterization of the connection. Manual edition 2. MODBUS / TCP communication via the integrated PN interface of the CPU 2XV9450-1MB02.

Diagnosis 7. 80B2 DB UNLINKED DB must not be created as UNLINKED. All data blocks that are specified in DB_x must be created and copied into the PLC.5 Diagnosis Messages of SFC24 Error messages of SFC24 at the output STATUS_MODBUS STATUS Event text Remedy (Hex) 80A1 DB Number = 0 or too large for the PLC Choose a valid DB number. Use the same IDB for the call of MODBUSPN in OB1 or cyclic interrupt OB and OB100.4 7-12 .4 Diagnosis Messages of Called Blocks Error messages of SFC 6 and SFC 20 at the output STATUS_MODBUS STATUS Event text Remedy (Hex) 7xxx For detailed information please refer to the online help of SIMATIC Manager. Manual edition 2. See online help (SIMATIC manager -> mark block -> key F1) 8xxx For detailed information please refer to the online help of SIMATIC Manager. when FB MODBUSPN is called with different instance DBs in OB1 or cyclic interrupt OB and OB100. See online help (SIMATIC manager -> mark block -> key F1) 8xxx For detailed information please refer to the online help of SIMATIC Manager. FB 65 and FB 66 at the output STATUS_CONN STATUS Event text Remedy (Hex) 7xxx For detailed information please refer to the online help of SIMATIC Manager. FB 64. This error code is also reported. 80B1 The DB does not exist in the PLC. See online help (SIMATIC manager -> mark block -> key F1) 7. See online help (SIMATIC manager -> mark block -> key F1) Error messages of FB 63. MODBUS / TCP communication via the integrated PN interface of the CPU 2XV9450-1MB02.

Example Project on the CD On the CD you can find an extensive example project which offers all varieties of parameterization possibilities for the Simatic stations.Application Sample 8 Sample Application General Information The following simple programming example illustrates the use of FB MODBUSPN.4 8-1 . Please note. Manual edition 2. • Simatic Station is S7-300. S7-400 or IM 151-8 PN/DP CPU • Simatic Station is client or server MODBUS / TCP communication via the integrated PN interface of the CPU 2XV9450-1MB02. the provided example project is meant for information purposes only. It displays the handling of the Modbus blocks and is not to be understood as a solution for a customer-specific installation configuration.

Block Symbol Comment OB 1 CYCL_EXC cyclic program processing OB 100 COMPLETE RESTART start-up OB for restart OB 121 PROG_ERR programming error OB FB 102 MODBUSPN FB MODBUSPN FB 103 TCP_COMM FB TCP_COMM FB 104 MOD_CLI FB MOD_CLI FB 105 MOD_SERV FB MOD_SERV DB 1 CONTROL_DAT work DB CONTROL DAT for FB MODBUSPN DB 2 MODBUS_PARAM parameter DB PARAM_DB for FB MODBUSPN DB 3 LICENSE_DB license data block for FB MODBUSPN DB 102 IDB_MODBUS instance DB for FB MODBUSPN DB 11 DATA_AREA_1 value DB for area 1 DB 12 DATA_AREA_2 value DB for area 2 DB 13 DATA_AREA_3 value DB for area 3 DB 14 DATA_AREA_4 value DB for area 4 DB 15 DATA_AREA_5 value DB for area 5 MODBUS / TCP communication via the integrated PN interface of the CPU 2XV9450-1MB02.Application Sample Sample Program The programming example consists of the blocks: • Start-Up OB100 with call of FB102 • Programming error OB121 • Cyclic program processing OB1 with call of FB102 • Global DBs for job trigger (e. with variable table) and for licensing • Data blocks for register and bit values Used Blocks The following blocks are used in the provided sample project for S7 stations with FB MODBUSPN.g. Manual edition 2.4 8-2 .

December 28.org MODBUS / TCP communication via the integrated PN interface of the CPU 2XV9450-1MB02.4 Appendix . Manual edition 2. 2006 http://www.modbus-IDA.A Literature MODBUS IDA MODBUS APPLICATION PROTOCOL SPECIFICATION V1.1b.1 .

4 Glossary . C Client A client is a device or. MODBUS / TCP communication via the integrated PN interface of the CPU 2XV9450-1MB02.> transmission rate Block Call A block call occurs when program processing branches to the called block Block Parameter Block parameters are variables within multiple-use blocks. With the help of a connection ID the system function blocks can communicate between two communication points.Glossary A Address The address identifies a physical storage location. Blocks Blocks are elements of the user program which are defined by their function. B Baud Rate . Configuration The configuration is the set up of individual modules of the PLC in the configuration table. SDB) • User-defined data types (UDT) Part of a -> subnet. SFC) • Data blocks (DB. which are replaced with actual values when the relevant block is called. OB. an object that requests a service from a -> server. FC. Automation System An automation system is a programmable logic controller that contains at least a PLC. Module for communications tasks. If the address is known. in general terms. the operand stored there can be directly accessed. CP Communications Processor. SFB. Subnets can consist of bus segments and connectivity devices such as repeaters and bridges.1 . With STEP7 there are Bus Segment • Code blocks (FB. Communications Processor Communications processors are modules for point-to-point connections and bus connections. different input and output devices as well as HMI devices. Manual edition 2. structure. Segments are transparent for addressing. Connection Parameterization The specification of a connection ID in the system function block. or purpose.

and interfaces to I/O modules. Manual edition 2. the user program is executed in a constantly repeating program loop. which are caused by. a program error or by operating mode transitions.4 Glossary . errors on a module or system errors in the PLC. operating system. They are subdivided into global data blocks and instance data blocks. D Data Block (DB) These are blocks containing data and parameters with which the user program works. F Function Block (FB) Function blocks are components of the user program and. Unlike all other blocks. in which detailed information on diagnostic events are stored in the order in which they occur. Default Setting The default setting is a basic setting which is always used if no other value is specified. memory. Function blocks can be parameterized but can also be used without parameters. called a cycle. Diagnostic Event Diagnostic events are. Download Downloading means loading objects (e. code blocks) from the programming device into the load memory of the PLC. Cycle Time The cycle time is the time the PLC needs to execute the user program once. Diagnostic Functions The diagnostics functions cover the entire system diagnosis and include detection. CRC Cyclic Redundancy-Check = Checksum which guarantees a high probability of error recognition. say. Cyclic Program Processing In cyclic program processing. a so called ”instance data block”. The data held in the data blocks can be accessed absolutely or symbolically. MODBUS / TCP communication via the integrated PN interface of the CPU 2XV9450-1MB02. for example. Diagnostic Buffer Every PLC has a diagnostic buffer. Data Type Data types allow users to define how the value of a variable or constant is to be used in the user program. are ”blocks with memory”. They are classified into elementary and structured data types. Complex data can be stored in structured form. data blocks do not contain instructions. The memory for the function block is an assigned data block.g. analysis and reporting of errors within the automation system.2 . in accordance with the IEC standard. H Hardware Hardware is the term given to all the physical and technical equipment of a PLC.CPU Central processing unit of the S7 programmable logic controller with control and arithmetic unit.

3 .4 Glossary . Operand An operand is part of a STEP7 instruction and states with what the processor is to do something.3 (ISO 8802-2) Instance Data Block An instance data block is a block assigned to a function block and contains data for this special function block.I Industrial Ethernet A LAN system complying with IEEE 802. MODBUS / TCP communication via the integrated PN interface of the CPU 2XV9450-1MB02. The functionality of the PLCs varies in the individual operating modes. O Online / Offline Online means that a data connection exists between PLC and programming device. M MAC-Address Address to distinguish between different stations connected to a common transmission medium (Industrial Ethernet). START UP and RUN. N NCM S7 for Industrial Ethernet Configuration software for configuration and diagnostic functions on an Ethernet CP. Offline means that no such data connection exists. Operating Mode The SIMATIC S7 programmable controllers have three different operating modes: STOP. Operating System of the PLC The operating system of the PLC organizes all functions and operations of the PLC which are not connected to a specific control task. Interface Module On the interface module the physical conversion of signals takes place. Media Access Control (MAC) Mechanisms for controlling access by a station to a common transmission medium shared with other stations. It can be both absolutely and symbolically addressed. Online Help STEP7 allows you to display contextual help texts on the screen while working with the programming software. By exchanging the pluggable interface module you can adapt the communications processor to the physical interface of the communications partner. Interrupt Interrupt is a name for a break of the program processing in the processor of an automation system by an external alarm. Module Modules are pluggable printed circuit boards for programmable logic controllers Module Parameters Module parameters are used to set the module behaviors. A distinction is made between static and dynamic module parameters. Manual edition 2.

A subnet consists of several stations with unique -> MAC addresses. A distinction is made between block parameters and module parameters.4 Glossary . START UP The operating mode START UP is active when the PLC transits from operating mode STOP to operating mode RUN. Subnet A subnet is part of a -> network whose parameters must be matched. and system function blocks. the signal states of the input modules are transferred to the process image input table. R Rack A rack is a rail containing slots for mounting modules. STEP7 STEP7 is the programming software of SIMATIC S7. Subnets can. MODBUS / TCP communication via the integrated PN interface of the CPU 2XV9450-1MB02. System Function (SFC) System functions are software modules without memory which are already integrated into the operating system of the S7-PLC and can be called by the user as required. At the end of the cyclic program. system functions. They are classified into system data blocks. A service is started at the instigation of a -> client. These rules are called protocols. Procedure The execution of a data interchange operation according to a specific protocol is called a procedure. be connected together by -> gateways to form a network. At the beginning of the cyclic program. the process image of the outputs is transferred to the output modules as output signals. System Block System blocks differ from the other blocks in that they are already integrated into the S7-400 system and are available for already defined system functions.4 . These include the operating system and the user programs. or in general terms. for example. The subnet includes bus components and all the attached stations. Parameterization Parameterization means setting the behavior of a module. an object that provides certain services. S Server A server is a device. System Function Block (SFB) System function blocks are software modules with memory which are already integrated into the operating system of the S7-PLC and can be called up by the user as required.P Parameter Parameters are values that can be assigned. Manual edition 2. A system consists of several subnets with unique subnet numbers. Process image This is a special memory area in the PLC. Software Software is the term given to all programs used on a computer system. Protocol The communications partners involved in a data interchange must abide by fixed rules for handling and implementing the data traffic.

Transmission Rate According to DIN 44302.T Tool A tool is a piece of software that is capable of accessing operating system functions in a programming device. Manual edition 2. The user program for SIMATIC S7 is structured and is divided into smaller units called blocks.g. E 1. V Variable A variable is an operand (e. User Program The user program contains all instructions and declarations for signal processing.g. by means of which a system or a process can be controlled. W Work Memory The work memory is a RAM on the PLC which the processor accesses while processing the user program.0) which can have a symbolic name and can therefore also be addressed symbolically. he set or selected transmission rate depends on various conditions. code blocks) from the load memory of the PLC into the programming device.4 Glossary . MODBUS / TCP communication via the integrated PN interface of the CPU 2XV9450-1MB02.5 . this is the number of binary decisions transmitted per time unit. The unit is bps. for example the distance across U Upload Uploading means loading objects (e.

60 91052 Erlangen Tel: ++49 9131 7-46111 Fax: ++49 9131 7-44757 Mail: it4.4 Stand: 02/2010 . Manual edition 2.siemens.industry@siemens.com/s7modbus Siemens Aktiengesellschaft Subject to change without prior notice.Customer Support Siemens AG Industry Sector I IS IN E&C Werner-von-Siemens-Str.com http://www. MODBUS / TCP communication via the integrated PN interface of the CPU 2XV9450-1MB02.