Helmholz Pn/modbustcp coupler User manual

Quick Start Guide PN/ModbusTCP Coupler

Version

2en

as of FW 1.00

www.helmholz.com

Quick Start Guide PN/ModbusTCP Coupler2

Contents

1. Safety instructions 3

2. Introduction 4

3. Function of the PN/ModbusTCP Coupler 4

4. Connection 5

5. Install GSDML le 5

6. Concept of data exchange 6

7. Supported ModbusTCP function codes 8

8. Conguration in the TIA portal 9

9. Parameters of the PN/ModbusTCP Coupler 10

10. Assign a PROFINET device name to the PN/ModbusTCP Coupler 11

11. Web interface of the PN/ModbusTCP Coupler 12

12. MQTT Publisher 14

13. Firmware update & reset to factory settings 16

14. PN/ModbusTCP status and control via the PLC 17

15. LED status information 18

16. Technical data 19

BT-beipack-134

Quick Start Guide PN/ModbusTCP Coupler 3

1. Safety instructions

Target audience

This description is only intended for trained personnel qualied in control and auto-

mation engineering who are familiar with the applicable national standards.

For installation, commissioning, and operation of the components, compliance with the

instructions and explanations in this operating manual is essential. The specialist person-

nel is to ensure that the application or the use of the products described fullls all safety

requirements, including all applicable laws, regulations, provisions, and standards.

Intended use

The device has a protection rating of IP 20 (open type) and must be installed in an elec-

trical operating room or a control box/cabinet in order to protect it against environmen-

tal inuences. To prevent unauthorized operation, the doors of control boxes/cabinets

must be closed and possibly locked during operation.

The consequences of improper use may include personal injury to the user or third par-

ties, as well as property damage to the control system, the product, or the environment.

Use the device only as intended!

Operation

Successful and safe operation of the device requires proper transport, storage, setup,

assembly, installation, commissioning, operation, and maintenance.

Operate the device only in awless condition. The permissible operating conditions and

performance limits (technical data) must be adhered to.

Retrots, changes, or modications to the device are strictly forbidden.

Quick Start Guide PN/ModbusTCP Coupler4

Application example: 1

Machine 1 Machine 2

TCP

Server

2. Introduction

This document explains the initial commissioning of the PN/ModbusTCP Coupler.

You can nd the most current version of the documentation under www.helmholz.

de or scan the QR code directly.

3. Function of the PN/ModbusTCP Coupler

Simple and uncomplicated connection of a PROFINET network with a ModbusTCP

network is possible with the PN/ModbusTCP Coupler.

The PN/ModbusTCP Coupler enables data transmission between a

PROFINET controller and ModbusTCP participants.

Received input data on one of the network sides is made available as output data to

the other network side. The IO data transfer takes place live and as quickly as pos-

sible without additional handling blocks.

The maximum size of the transmitted data is 1024bytes of input/output data. Up to

300slots for IO modules are available.

The integration into the PLC engineering tool is made possible by a GSDML le;

special conguration software isn’t necessary.

In addition to the PROFINET / ModbusTCP communication, the PN/ModbusTCP

Coupler also makes an MQTT Publisher available on both network sides.

In this way, the values exchanged via the gateway can also be distributed via MQTT

to visualization or operating data recording systems.

SCAN

QR CODE

TO GET

MANUAL

PN/ModbusTCP Coupler

documentation

Quick Start Guide PN/ModbusTCP Coupler 5

4. Connection

The left RJ45 sockets “X1 P1” and “X1 P2” are for the connection of the PROFINET

network; the right RJ45 sockets “X2 P1” and “X2 P2” are for the connection of the

ModbusTCP network.

The PN/ModbusTCP Coupler must be supplied with 24 V DC at the wide range input

18 ... 30 V via the provided connector. The power supply is designed redundantly. At

least a supply path PS 1 or PS 2 must be connected.

5. Install GSDML le

Please download t

he GSDML le

(“GSDML-V2.34-Helmholz-PN-ModbusTCP-cou-

pler-______.xml”) under www.helmholz.de or scan the QR code.

Install the le in the engineering tool so that the PN/ModbusTCP Coupler is available

for conguration.

Note: The housing of the PN/ModbusTCP Coupler is not grounded. Please connect the

functional grounding connection (FG) of the PN/ModbusTCP coupler correctly with the

reference potential.

Port 1, port 2

PROFINET connection

Operation LEDs (see page 10)

X2 P1, P2

ModbusTCP network

Redundant power supply

PS 1/PS 2

MAC address of the

PROFINET connection

MAC address

ModbusTCP network

PN/ModbusTCP Coupler

GSDML le

SCAN

QR CODE

TO GET

GSDML

Quick Start Guide PN/ModbusTCP Coupler6

TCP

ModbusTCP

Clients

Discrete Inputs: 65536 Bits

(8 Kbyte)

Discrete Input 0 – 65535

Coils: 65536 Bits

(8 Kbyte)

Coils 0 – 65535

Input Register:

65535 Words

(128 Kbyte)

Holding Register:

65535 Words

(128 Kbyte)

In the PN/ModbusTCP Coupler, all coils, inputs and registers are always present from

the perspective of the ModbusTCP communication. It is thus always possible to ac-

cess all data types from address 0-65535.

With the PROFINET conguration, that data can be assigned in the slots of the PN/

ModbusTCP Coupler to the PLC-IO image that is to be accessed in the PLC program.

Up to 300 slots are available for such assignments in the PN/ModbusTCP Coupler

ModbusTCP differentiates between 4 different data types:

1. Discrete Inputs: Input bits; written by the PROFINET PLC

2. Coils: Output bits or internal data bits; read by the PROFINET PLC,

but can also be written

3. Input Register: Input word; written by the PROFINET PLC

4. Holding Register: Output word or internal data word; read by the PROFINET PLC,

but can also be written

6. Concept of data exchange

The PN/ModbusTCP Coupler is a ModbusTCP server. It receives data via ModbusTCP, which is then transmitted to the IO image of the PROFINET PLC

(inputs in the PLC) and makes data available as transmission data, which it receives from the PROFINET PLC (outputs in the PLC).

All data types are enumerated from 0-65535. All data types have their own storage area in the PN/ModbusTCP Coupler.

Quick Start Guide PN/ModbusTCP Coupler 7

TCP

ModbusTCP

Clients

Discrete inputs: 65536 Bits

(8 Kbyte)

Discrete Input 0 – 65535

Coils: 65536 Bits

(8 Kbyte)

Coils 0 – 65535

Input Register:

65536 Words

(128 Kbyte)

Holding Register:

65536 Words

(128 Kbyte)

Slot 1

Slot 2

Slot 3

Slot 4

Slot 5

Slot 6

...

• Discrete Input 1 Byte

• Address 10...17 (8 Bits)

• PLC: 1 Output Byte (QB 100)

• Read Coils, 2 Bytes

• Address 100..115

• PLC: 2 Input Bytes (ID 110)

• Write Coils, 4 Bytes

• Address 20..51

• PLC: 4 Output Bytes (QD 110)

• Write Input register (16 Bit)

• Address 10

• PLC: 1 Output word (1 QW)

• Read Holding register (16 Bit)

• Address 80

• PLC: 1 Input word (1 IW)

• Write Holding register (16 Bit)

• Address 60

• PLC: 1 Output word (1 QW)

The following modules are available for access to the ModbusTCP storage:

Discrete Inputs (only writing):

• Write Discrete Inputs 1 Byte (8 bits)

• Write Discrete Inputs 2 Byte (16 bits)

• Write Discrete Inputs 4 Byte (32 bits)

• Write Discrete Inputs 8 Byte (64 bits)

• Write Discrete Inputs 16 Byte (128 bits)

• Write Discrete Inputs 32 Byte (256 bits)

Coils (read/write):

• Write Coils 1 Byte (8 bits)

• Write Coils 2 Byte (16 bits)

• Write Coils 4 Byte (32 bits)

• Write Coils 8 Byte (64 bits)

• Write Coils 16 Byte (128 bits)

• Read Coils 1 Byte (8 bits)

• Read Coils 2 Byte (16 bits)

• Read Coils 4 Byte (32 bits)

• Read Coils 8 Byte (64 bits)

• Read Coils 16 Byte (128 bits)

Input Register (only writing):

• Write Input Register (16 bits)

Holding Registers (read/write):

• Write Holding Register (16 bits)

• Read Input Register (16 bits)

All modules have the register numbers (Input Register, Holding Register)

or the rst bit address (Discrete Inputs, Coils) as parameter.

Example of a conguration:

Quick Start Guide PN/ModbusTCP Coupler8

7. Supported ModbusTCP function codes

The PN/ModbusTCP Coupler supports the following function codes:

Data size Data range Function Function code

decimal

Function code

hex

Bit access

Input bits Read discrete inputs 2 0x02

Output bits or

internal bits

Read coils 1 0x01

Write single coil 5 0x05

Write multiple coils 15 0x0F

16 bit

access

Input data Read input register 4 0x04

Output data or

internal information

Read holding register 3 0x03

Write single holding register 6 0x06

Write multiple Register 16 0x10

Read/write multiple holding registers 23 0x17

Mask write holding register 22 0x16

Quick Start Guide PN/ModbusTCP Coupler 9

8. Conguration in the TIA portal

The PN/ModbusTCP Coupler can be found in the hardware catalog under “Other eld

devices / PROFINET IO / Gateway / Helmholz GmbH & Co. KG / Helmholz PN/Mod-

busTCP Coupler”.

The PN/ModbusTCP Coupler can be completely congured via the GSDML le in the

PROFINET congurator. An additional conguration software is not necessary. The

ModbusTCP network settings can also be made through the website if needed.

Provide the PN/ModbusTCP Coupler with a PROFINET name under “General”. Con-

nect the PROFINET network of the PROFINET controller with the PN/ModbusTCP

Coupler.

Now insert the desired modules for discrete inputs, coils, input registers or holding

registers into the slots.

All modules have the register number (input register, holding register) or the

rst bit address (discrete inputs, coils) as parameter. In the case of the input bits and

coils, these can be addressed together in one slot from 8 bits (1 Byte) to 256 bits (32

Bytes). Addressing of individual bits is not possible via the PROFINET PLC; the smallest

unit is one byte.

Quick Start Guide PN/ModbusTCP Coupler10

ModbusTCP Denition of the IP address for the ModbusTCP network.

IP address mode:

“DHCP”, “Static IP”, “use IP from webpage setting”

Static IP address:

The static IP address can be indicated here when the address

mode has been set to “Static IP”.

Static IP subnet mask:

The subnet mask can be indicated here when the address

mode has been set to “Static IP”.

DHCP host name mode:

Adopt from the PROFINET conguration or from the web page

DHCP host name:

DHCP name of the device

ModbusTCP port:

Port to which the ModbusTCP driver listens. Port 502

is always active, even when another port has been set here.

ModbusTCP connection Time in which a connection is closed when

monitoring (ms): communication no longer takes place via this connection.

Range: 1–65535 ms

Maximum number of

Number of participants that can establish connections

ModbusTCP connections: with the PN/ModbusTCP coupler simultaneously.

PN/ModbusTCP coupler can be read out via ModbusTCP.

Range 0-65535

Status of website: On which network interfaces should the website be

displayed.

MQTT Publisher option:

On which network interfaces should the MQTT Publisher

be activated.

9. Parameters of the PN/ModbusTCP Coupler

The conguration of the PN/ModbusTCP Coupler can take place completely through the PROFINET hardware congurator. However, several parameters can also be optionally

set via the website, e.g. the IP address of the ModbusTCP server, the DHCP host name.

Quick Start Guide PN/ModbusTCP Coupler 11

10. Assign a PROFINET device name to the PN/ModbusTCP Coupler

When the conguration of the PN/ModbusTCP Coupler has been completed in the

hardware congurator of the engineering tool, it can be loaded into the PLC.

In order that the PN/ModbusTCP Coupler can be found by the PROFINET controller,

the PROFINET device name must be assigned to the PN/ModbusTCP Coupler. To this

purpose, use the function “Assign device name”, which you can access in the Online

menu with the right mouse button when the PN/ModbusTCP Coupler is activated.

With the “Update list...” button, the network can be browsed for PROFINET par-

ticipants. The PROFINET device name can be assigned to the device with “Assign

name”.

The clear identication of the PN/ModbusTCP Coupler is ensured here by the MAC

address of the device. The MAC addresses of the device can be found on the device

front of the PN/ModbusTCP Coupler.

The Helmholz IPSet tool, which can be downloaded at no charge from the Helmholz

website, can also be used to set the PROFINET name.

If the PN/ModbusTCP Coupler has been assigned the correct PROFINET name, it is

recognized by the PLC and congured. If conguration has taken place correctly, the

PROFINET “BF” LED should be off.

Alternatively, the PROFINET name or the IP address of the device can be set with the

free Helmholz tool “IPset”.

The tool can be downloaded in the download area of the product under “Software”.

PN/ModbusTCP Coupler

IPSet

SCAN

QR CODE

TO GET

FIRMWARE

Quick Start Guide PN/ModbusTCP Coupler12

11. Web interface of the PN/ModbusTCP Coupler

The web interface of the PN/ModbusTCP coupler provides an overview of the status

and the conguration of the device, as well as the possibility for carrying out a rm-

ware update.

The ModbusTCP conguration can also be set in the web interface if this hasn’t been

prescribed through the PROFINET conguration.

A password must be dened for the standard user “admin” with the rst access to

the web interface. The password can be retroactively changed in the “Account”

menu.

The current settings and the status are represented in the “Overview”.

The other websites can be called up in the top line.

Note: Calling up the website can inuence the transmission capacity of the PN/

ModbusTCP Coupler.

Quick Start Guide PN/ModbusTCP Coupler 13

The “Module cong” page shows the IO modules dened by the PROFINET congu-

ration. The data type and the address are also provided on the ModbusTCP page.

The current value is displayed in brackets.

The IP address and the DNS name of the ModbusTCP network interface are set on

the “ModbusTCP server settings” website when these have not been xed through

the GSDML conguration.

Quick Start Guide PN/ModbusTCP Coupler14

12. MQTT Publisher

In addition to the PROFINET / ModbusTCP communication, the PN/ModbusTCP

Coupler also makes an MQTT Publisher available.

MQTT is broadly distributed and simple protocol for the distribution of information

in large networks.

The MQTT Publisher can be activated via the PROFINET conguration on the PROFINET

or Modbus interface.

For all IO modules dened in the PROFINET conguration, the current values of the

value change are sent via MQTT.

Since MQTT works slower than the priority PROFINET/Modbus TCP communication,

it is possible that not all value changes are transmitted via MQTT, but only the last

value state.

11.1 MQTT Publisher settings

At least one MQTT broker is always required to be able to distribute data via MQTT in

a network. The broker can run everywhere in the network.

The settings of the MQTT Publisher can be dened on the website under “MQTT”,

separate for the two network sides.

ClientID:

The name of the MQTT Publisher

User name / Password:

Optional user name and password for login with the

MQTT broker

Broker IP address:

Address of the MQTT broker

Broker TCP port:

MQTT port at the MQTT broker

Keep alive (seconds):

MQTT connection monitoring in the event of inactivity

Note: The MQTT Publisher of the PN/ModbusTCP Coupler currently does not provide

encoding!

Quick Start Guide PN/ModbusTCP Coupler 15

PROFINET network: ModbusTCP network:

Module MQTT Topic Name MQTT Topic Name

Write discrete inputs PN-ClientID/Slot X/Output, Y bytes (1 to 32 bytes) ModbusTCP-ClientID/Discrete Inputs/Address X, Y Bytes (1 to 32 bytes)

Read Coils PN-ClientID/Slot X/Input, Y bytes (1 to 16 bytes) ModbusTCP-ClientID/Coils /Address X, Y Bytes (1 to 16 bytes)

Write Coils PN-ClientID/Slot X/Input, Y bytes (1 to 16 bytes) ModbusTCP-ClientID/Coils /Address X, Y bytes (1 to 16 single bytes)

Read holding register PN-ClientID/Slot X/Output (2 byte decimal value) ModbusTCP-ClientID/Holding Register/Register X (2 byte decimal value)

Write holding register PN-ClientID/Slot X/Output (2 byte decimal value) ModbusTCP-ClientID/Holding Register/Register X (2 byte decimal value)

Write input register PN-ClientID/Slot X/Output (2 byte decimal value) ModbusTCP-ClientID/Input Register/Register X (2 byte decimal value)

Example PN_MQTT/Slot 1/Input, 3 bytes | 0x12 0x23 MODBUS_MQTT/Coils/Address 49, 2 bytes | 0x12 0x34

PN_MQTT/Slot 5/Output | 12345 MODBUS_MQTT/Holding Register/Register 10 | 12345

11.2 MQTT format of the data

The data is transmitted in plain text format via MQTT. The syntax differs depending upon the network interface used.

The following MQTT topics can also be read on both network interfaces:

ClientID/Modules List:

Contains the list of all topics made available by the PN/ModbusTCP Coupler via the addressed interface.

ClientID/Status Register:

Contains the value of both status bytes, see chapter 11.1.

Quick Start Guide PN/ModbusTCP Coupler16

13. Firmware update & reset to factory settings

A rmware update can be carried out via the web interface on the “Firmware up-

grade” page.

The rmware can be selected with the Browse button. The rmware le has the end-

ing “HUF” (Helmholz Update File).

The rmware is transferred to the PN/ModbusTCP Coupler and burned with the

“Submit” button.

The PN/ModbusTCP Coupler then performs a restart and the new rmware is active.

Please download the current rmware under www.helmholz.de or scan the QR

code.

Note: It is also possible to carry out the reset to factory settings at the website.

PN/ModbusTCP Coupler

rmware

SCAN

QR CODE

TO GET

FIRMWARE

Quick Start Guide PN/ModbusTCP Coupler 17

14. PN/ModbusTCP status and control via the PLC

13.1 Status

The PN/ModbusTCP Coupler provides a status via the PROFINET input image:

Byte 1: Status bits

Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0

PROFINET congu-

ration completed.

Device is ready to

operate.

- Power supply

detected on PS 1

(left)

Power supply

detected on PS 2

(right)

MQTT connection

active on network

MQTT connection

active on network

ModbusTCP net-

work has an active

IP address

(static or acquired

via DHCP)

Network cable

detected

11.2 Control bits

The PN/ModbusTCP Coupler can be controlled via the following control bits in the PROFINET output image:

Byte 1 “Control bits”

Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0

- - - - - - Reset the ModbusTCP

memory (coils, inputs and

registers)

Interrupt all ModbusTCP connec-

tions and prevent the establishing

of connections

Byte 2: Number of active connections

Quick Start Guide PN/ModbusTCP Coupler18

15. LED status information

X1 PROFINET (left side) X2 ModbusTCP (right side)

SF (rot)

Off Conguration correct Conguration correct

On There is no conguration, the conguration does not agree with

the conguration on the right side (X2), or a diagnosis exists.

PROFINET side not congured or has failed

Flashing PROFINET function “LED ashing” for nding the device is being

carried out

BF (red)

Off The device is congured The device is congured

On The device has no conguration, the PROFINET device name is

incorrect, or there is no connection with the PROFINET controller.

No Ethernet cable plugged in or no Ethernet connection

Flashing PROFINET function “LED ashing” for nding the device is being

carried out

MT (yellow)

Flashing A rmware update is being carried out A rmware update is being carried out.

Blinking together

with SF and BF.

PROFINET function “LED ashing” for nding the device is being

carried out.

PWR (green)

On PS1 Power supply present PS2 Power supply present

RUN (green)

Off Firmware or device defective. Please contact Support

On The device is ready to operate

RJ45 LEDs X1 P1/P2 and X2 P1/P2

Green (Link) Connected

Orange (Act) Data transfer at the port running

Quick Start Guide PN/ModbusTCP Coupler 19

16. Technical data

Order no. 700-159-3MB01

Article designation PN/ModbusTCP Coupler

Scope of delivery PN/ModbusTCP Coupler incl. Quick Start Guide

PROFINET interface

-Number 1 with 2 ports

-Protocol PROFINET IO as dened in IEC 61158-6-10

-Transmission rate 100 Mbps full duplex

-I/O image size max. 1024 bytes of input and output data

-Number of congurable slots 300

-Connection 2x RJ45, integrated switch

-Features Media redundancy (MRP), automatic addressing, topology detection (LLDP, DCP), diagnosis alarms

ModbusTCP interface

-Number 1 with 2 ports

-Protocol ModbusTCP server

-Transmission rate 10/100 Mbps full duplex

-Storage size 65536 coil bits, 65536 discrete input bits, 65536 input register, 65536 holding register

-Supported function codes 1, 2, 3, 4, 5, 6, 15, 16, 22, 23

-Connection 2x RJ45, integrated switch

Status indicator 9 LEDs function status, 8 LEDs Ethernet status

Voltage supply 24 V DC (18 - 28 V DC)

Current draw Max. 210 mA

Power dissipation Max. 5 W

Dimensions (D x W x H) 35 mm x 58 mm x 72 mm

Weight Approx. 135 g

Ambient temperature 0 °C to 60 °C

Transport and storage temperature -20 °C to 80 °C

Protection rating IP 20

Certications CE

Note:

The contents of this Quick Start Guide have been checked by us so as to ensure that they match the hardware and software described.

However, we assume no liability for any existing differences, as these cannot be fully ruled out.

The information in this Quick Start Guide is, however, updated on a regular basis. When using your purchased products, please make sure to use the latest version of this

Quick Start Guide, which can be viewed and downloaded in the Internet at www.helmholz.de.

Our products contain open source software, among others. This software is subject to the respectively relevant license conditions. We will send you the corresponding license

conditions, including a copy of the complete license text together with the product. They are also provided in our download area of the respective products under www.helmholz.de.

We also offer to send you or any third party the complete corresponding source text of the respective open source software for an at-cost fee of 10.00 EUR as a DVD upon request.