WAGO Configuring Modbus Networks (TCP/UDP) in e!COCKPIT User manual

Brand: WAGO

Model: Configuring Modbus Networks (TCP/UDP) in e!COCKPIT

Type: User manual

Product manual | Version 1.0.1

e!COCKPIT

Configuring Modbus Networks (TCP/UDP) in e!COCKPIT

2759-0101

2759-0101Legal Information

WAGO Kontakttechnik GmbH & Co. KG

Hansastraße 27

D - 32423 Minden

Phone: +49 571/887 – 0

Fax: +49 571/887 – 844169

E-Mail: * [email protected]

Internet: ü www.wago.com

Technical Support

Phone: +49 571/887 – 44555

Fax: +49 571/887 – 844555

E-Mail: * [email protected]

Every conceivable measure has been taken to ensure the accuracy and completeness of

this documentation. However, as errors can never be fully excluded, we always appreci-

ate any information or suggestions for improving the documentation.

E-Mail: * [email protected]

We wish to point out that the software and hardware terms as well as the trademarks of

companies used and/or mentioned in the present manual are generally protected by

trademark or patent.

WAGO is a registered trademark of WAGO Verwaltungsgesellschaft mbH.

Product manual | Version: 1.0.1

Configuring Modbus Networks (TCP/UDP) in e!COCKPIT

2759-0101 Table of Contents

Product manual | Version: 1.0.1 iii

Configuring Modbus Networks (TCP/UDP) in e!COCKPIT

Table of Contents

1 Terms ................................................................................................................................4

1.1 Intended Use........................................................................................................... 4

1.2 Typographical Conventions..................................................................................... 5

1.3 Legal Information .................................................................................................... 7

2 Security.............................................................................................................................8

2.1 General Safety Regulations .................................................................................... 8

2.2 Indirect Safety ......................................................................................................... 8

3 Overview ...........................................................................................................................9

4 Modbus Settings in e!COCKPIT....................................................................................10

4.1 General Settings for Devices and Fieldbus Interface............................................ 12

4.1.1 “Modbus Slave” Tab .....................................................................................12

4.2 Slave Settings in the Data Point Configurator....................................................... 15

4.3 Master and Connection Settings in the Fieldbus Configurator.............................. 19

4.3.1 “Modbus Master Variables” Tab ...................................................................20

4.3.1.1 Available Slave Data Points ................................................................20

4.3.1.2 Master Variables (Slave Data Points on the Master)...........................21

4.3.2 “Connection Settings” Tab............................................................................ 22

4.3.3 “Modbus Communication Channels” Tab.....................................................23

4.4 Overview of the Modbus Data Points.................................................................... 26

4.5 Access to Simple and Complex Data Types ......................................................... 28

4.6 Import/Export Functions for Modbus Data Points ................................................. 30

4.6.1 Export Slave Data Points in the Data Point Configurator .............................30

4.6.2 Import/Export the Communication Connection in the Fieldbus Configurator

.....................................................................................................................31

4.7 Diagnostic Options for Modbus Communication ................................................... 32

5 Setting Up Modbus Network (Scenarios).....................................................................34

5.1 Connecting Controller (Master) to Fieldbus Coupler (Slave) ................................ 36

5.2 Connecting Controller (Master) to Third-Party Device (Slave).............................. 42

5.3 Connecting Controller (Master) to Controller (Slave) ............................................ 49

5.4 Connecting Controller (Master) to Controller (CODESYS V2) (Slave).................. 58

5.5 Connecting Third-Party Device (Master) to Controller (Slave).............................. 64

6 Appendix.........................................................................................................................71

6.1 Protected Rights.................................................................................................... 71

2759-0101Terms

4 Product manual | Version: 1.0.1

Configuring Modbus Networks (TCP/UDP) in e!COCKPIT

1Terms

This documentation applies to the e!COCKPIT (2759-0101) software, version 1.8.0.

Note

Observe the product documentation!

The software must only be installed and operated according to the instructions of the

complete Instructions for use. Knowledge of the complete Instructions for use is required

for proper use.

1. Carefully read the Product Manual.

2. Follow the steps in the installation wizard.

Table 1: Scope of Applicability – Versions

e!COCKPIT Version Documentation Version

1.0.0 ... 1.6.1 –

1.7.0 1.0.0

1.8.0 1.0.1

* This manual is available for e!COCKPIT version 1.7.0 and higher. For earlier e!COCKPIT versions, fieldbus-

specific content is integrated into the associated e!COCKPIT manuals.

Besides this documentation/online help, the following supplementary documents are

available:

• Quick start guide

• Library descriptions

• Manuals for integrated configurators (e.g., telecontrol configurators)

• Manuals for products used (e.g., PFC200)

• Release notes

• News

You can find the documents in PDF format in the Windows Start menu under WAGO

Software > e!COCKPIT.

You can open the context-sensitive online help within e!COCKPIT by pressing [F1] on

your keyboard.

1.1 Intended Use

Improper Use

Improper use of the products is not permitted. Specifically, improper use occurs in the fol-

lowing cases:

• Non-observance of the intended use.

• Use of the products in areas with special risk that require flawless continuous operation

and in which failure or operation of the software can result in an imminent risk to life,

limb or health or cause serious damage to property or the environment (such as the

operation of nuclear power plants, weapon systems , aircraft and motor vehicles).

2759-0101 Terms

Product manual | Version: 1.0.1 5

Configuring Modbus Networks (TCP/UDP) in e!COCKPIT

Warranty and Liability

The terms set forth in the General Business & Contract Conditions for Delivery and Ser-

vice of WAGO Kontakttechnik GmbH & Co. KG and the terms for software products and

products with integrated software stated in the WAGO Software License Contract – both

available at üwww.wago.com – shall apply. In particular, the warranty is void if:

• The products are used improperly.

• The deficiency (hardware and software configurations) is due to special instructions.

• The hardware or software has been modified by the user or a third party.

Individual agreements always have priority.

Obligations of Installers/Operators

The Installer/operator bear responsibility for the safety of an installation or a system as-

sembled with the products. The Installer/operator is responsible for proper installation and

security of the system. All laws, standards, guidelines, local regulations and accepted

technology standards and practices applicable at the time of installation and the instruc-

tions in the products’ Instructions for use must be complied with.

e!COCKPIT is an integrated development environment with seamless data retention for

all automation tasks:

• Hardware configuration and parameterization

• Programming with integrated e!RUNTIME

• Visualization (operation and monitoring)

• Diagnostics for targeted development and commissioning

Software operation is only permitted if the system requirements and license conditions

are met.

1.2 Typographical Conventions

Number Notation

100 Decimals: Normal notation

0x64 Hexadecimals: C-notation

‘100’

‘0110.0100’

Binary: In single quotation marks

Nibbles separated by a period

Text Formatting

italic Names of paths or files

bold Menu items, entry or selection fields, emphasis

Code Sections of program code

> Selection of a menu point from a menu

“Value” Value entries

[F5] Identification of buttons or keys

Cross References / Links

Cross reference / link to a section in a document

Cross reference / link to a separate document

Cross reference / link to a website

2759-0101Terms

6 Product manual | Version: 1.0.1

Configuring Modbus Networks (TCP/UDP) in e!COCKPIT

Cross reference / link to an email address

Action Instructions

ü This symbol identifies a precondition.

1. Action step

2. Action step

ð This symbol identifies an intermediate result.

ð This symbol identifies the result of an action.

Lists

• Lists, first level

– Lists, second level

Notes

DANGER

Type and source of hazard

Possible consequences of hazard that also include death or irreversible injury

• Action step to reduce risk

WARNING

Type and source of hazard

Possible consequences of hazard that also include severe injury

• Action step to reduce risk

CAUTION

Type and source of hazard

Possible consequences of hazard that include at least slight injury

• Action step to reduce risk

NOTICE

Type and source of malfunction (property damage only)

Possible malfunctions that may restrict the product’s scope of functions or ergonomics,

but do not lead to foreseeable risks to persons

• Action step to reduce risk

2759-0101 Terms

Product manual | Version: 1.0.1 7

Configuring Modbus Networks (TCP/UDP) in e!COCKPIT

Note

Notes and information

Indicates information, clarifications, recommendations, referrals, etc.

1.3 Legal Information

Intellectual Property

Unless barred by applicable legal provisions, unauthorized copying and distribution of this

document, as well as the use and communication of its content are strictly prohibited un-

less expressly authorized by prior agreement. Third-party products are always mentioned

without any reference to patent rights. WAGO Kontakttechnik GmbH & Co. KG, or for

third-party products, their manufacturer, retain all rights regarding patent, utility model or

design registration.

Third-party trademarks are referred to in the product documentation. The “

” and “

”

symbols are omitted hereinafter. The trademarks are listed in the Appendix (8Protected

Rights [}71]).

Subject to Change

The instructions, guidelines, standards, etc., in this manual correspond to state of the art

at the time the documentation was created and are not subject to updating service. The

installer and operator bear sole responsibility to ensure they are complied with in their

currently applicable form. WAGO Kontakttechnik GmbH & Co. KG retains the right to

carry out technical changes and improvements of the products and the data, specifica-

tions and illustrations of this manual. All claims for change or improvement of products

that have already been delivered – excepting change or improvement performed under

guarantee agreement – are excluded.

Licenses

The e!COCKPIT software and related components are protected by license mechanisms.

For more information, see the e!COCKPIT manual at “Licenses”.

2759-0101Security

8 Product manual | Version: 1.0.1

Configuring Modbus Networks (TCP/UDP) in e!COCKPIT

2Security

2.1 General Safety Regulations

• This documentation is part of the product. Therefore, retain the documentation during

the entire service life of the product. Pass on the documentation to any subsequent

user of the product. In addition, ensure that any supplement to this documentation is

included, if necessary.

• Any actions related to the use of WAGO software may only be performed by qualified

staff with sufficient knowledge to use the respective PC system.

Steps in which files are created or changed on a PC system may only be performed by

qualified employees with sufficient knowledge in the administration of the PC system

used in addition to file creation or modification.

Steps that change the PC system’s behavior within a network may only be performed

by qualified employees with sufficient knowledge of administration of the responsible

network.

• Comply with the laws, standards, guidelines, local regulations and accepted technol-

ogy standards and practices applicable at the time of installation.

2.2 Indirect Safety

• If automation solutions are implemented that can cause personal injury or major prop-

erty damage in the event of failure, you must take appropriate measures to ensure that

the system remains in a safe operating state even in the event of failure.

• Give all products in a network different IP addresses.

• Operate ETHERNET and PROFINET interfaces in separate networks.

• Never connect a PC on which a DHCP server is installed to a global network. In larger

networks, there is usually already a DHCP server that can cause collisions and subse-

quent network failure.

• Use only the latest security software.

• If there are access problems, check on connected devices that the e!RUNTIME run-

time system is activated. Use a software tool (depending on the hardware) to perform

the check or use the Web-Based Management System.

2759-0101 Overview

Product manual | Version: 1.0.1 9

Configuring Modbus Networks (TCP/UDP) in e!COCKPIT

3Overview

This documentation describes the configuration and parameterization of Modbus devices,

as well as examples of designing Modbus networks with the e!COCKPIT software. Vari-

ous scenarios with different devices and device roles (master/slave) are considered.

e!COCKPIT is an integrated development environment with seamless data retention for

all automation tasks, such as configuration and parameterization of hardware, CODESYS

V3-based programming, visualization for operation and monitoring and diagnostics to find

and correct errors.

Devices from the product catalog can be arranged in the project by means of the network

scan function or by dragging and dropping them. Fieldbus-specific device description files

(e.g., EDS), device drivers and libraries allow systems from other suppliers to be inte-

grated into the topology along with WAGO devices.

The network is designed by connecting devices to each other. Device parameters can be

set on panels. Integrated configurators also support fieldbus-specific configuration of de-

vices and the network.

Note

Observe other applicable documentation!

First read the e!COCKPIT manual to familiarize yourself with the software. Safe operation

of e!COCKPIT is a prerequisite for understanding the following sections. Also read the

product manuals for the products you use (e.g., fieldbus couplers, controllers and pan-

els).

2759-0101Modbus Settings in e!COCKPIT

10 Product manual | Version: 1.0.1

Configuring Modbus Networks (TCP/UDP) in e!COCKPIT

4Modbus Settings in e!COCKPIT

e!COCKPIT integrates various configurators and settings options to configure device pa-

rameters, as well as fieldbus-specific device interfaces and connections between devices.

Settings related to communication are made in e!COCKPIT at the following places:

• “Settings” panel

→ see 8General Settings for Devices and Fieldbus Interface [}12]

Figure1: “Settings” Panel

• Data point configurator in the Device Detail view

→ Configuration of the data points that the slave makes available to other devices (see

8Slave Settings in the Data Point Configurator [}15])

Figure2: Data Point Configurator

2759-0101 Modbus Settings in e!COCKPIT

Product manual | Version: 1.0.1 11

Configuring Modbus Networks (TCP/UDP) in e!COCKPIT

• Fieldbus configurator

→ Configuration of connections between the master and slave on the data point level

(see 8Master and Connection Settings in the Fieldbus Configurator [}19])

Figure3: Fieldbus Configurator

2759-0101Modbus Settings in e!COCKPIT

12 Product manual | Version: 1.0.1

Configuring Modbus Networks (TCP/UDP) in e!COCKPIT

4.1 General Settings for Devices and Fieldbus Interface

The basic parameters for devices, PLC, local bus and the fieldbus interfaces are set on

the “Settings” panel.

The “Settings” panel is open by default. If it is closed, it can be reopened through the

“VIEW” tab in the menu ribbon.

Icons that vary according to the device selected appear to open a corresponding tab for

parameterization. The available icons (tabs) are context-sensitive and depend on the se-

lected device and supported protocols.

Modbus settings are made on the “Modbus Slave” tab of the “Settings” panel.

Figure4: “Settings” Panel – “Modbus Slave” Tab

4.1.1 “Modbus Slave” Tab

Table 2: “Settings” Panel – “Modbus Slave” Tab

Parameter Value Description

General Settings

Unit ID 1 … 247 Specifies the Modbus unit ID (slave ID)

Behavior on PLC

Stop

Behavior of the Modbus slave when the control system has halted (control system in

“STOP” state):

Keep last value Data exchange possible

For Modbus read requests, the last frozen values are returned.

For write requests, the values are carried over unchanged to the

Modbus process image without passing them to the controller.

No data exchange No data exchange possible

Modbus requests will always be answered by the exception re-

sponse “ILLEGAL FUNCTION” (0x81).

Use substitute value Data exchange possible

For Modbus read requests, substitute values (0) are returned. For

write requests, the values are carried over unchanged to the local

Modbus process image without passing them to the controller.

Behavior on fieldbus

error

Response of the Modbus slave in the event of detected fieldbus errors (interruption of

communication).

Keep last value Data exchange possible

For PLC read functions, the last frozen values from the Modbus

process image are returned. For write accesses, the values are

carried over unchanged to the Modbus process image without

passing them to the Modbus master.

No data exchange No data exchange possible

Use substitute value Data exchange possible

For PLC read functions, the substitute values (0) from the Modbus

process image are returned. For write accesses, the values are

carried over unchanged to the Modbus process image without

passing them to the Modbus master.

2759-0101 Modbus Settings in e!COCKPIT

Product manual | Version: 1.0.1 13

Configuring Modbus Networks (TCP/UDP) in e!COCKPIT

Table 2: “Settings” Panel – “Modbus Slave” Tab

Parameter Value Description

Response Delay [ms] 0 … 32 Transmission of the response to a Modbus request is delayed

from the time of processing (read and/or write register values) by

the time according to the setting.

32ms = maximum delay

0ms = no delay

The actual duration is always longer due to parallel requests/sys-

tem utilization. Changes take effect immediately for each subse-

quent request.

Update Variables Always update Variables are always updated, even if they do not appear in the

program, but only used in the Visu Task.

Only when used in

the PLC task

Variables are only updated when the appear in the program.

Watchdog Settings

Function Mode Advanced Mode The watchdog must be controlled explicitly via commands (see

registry 0xFA00 [Watchdog Command]).

Simple Mode The watchdog is activated directly with a timeout > 0s in registry

0xFA01 (Watchdog Timeout). Each trigger restarts both the run-

ning watchdog as well as the expired one.

Reset Timeout [ms] 0 … 65535 Specifies the watchdog reset timeout.

Explicit Trigger On Only writing the value 0x5555 (WATCHDOG_START) to registry

0xFA00 (Watchdog Command) is considered a watchdog trigger

(exception: registry 0xFA02 [Watchdog Status]).

Off All valid Modbus requests are considered watchdog triggers (ex-

ception: registry 0xFA02 [Watchdog Status]).

Trigger on Status On Reading the watchdog status triggers the watchdog.

Off The watchdog trigger is disabled. Watchdog status read-out is not

considered a watchdog trigger.

Resetting of the TCP

Connections

On All Modbus TCP connections are disconnected when the watch-

dog expires.

Off Existing Modbus TCP connections remain open.

TCP Settings

TCP Port 1 … 65535 Port number for the TCP link

1 = minimum port number

502 = Modbus default port

65535 = maximum port number

Timeout [10ms] 1 … 65535 Timeout for a TCP link

The connection is closed when no more packets are received

within the timeout period.

Example:

Entering “1” yields10 ms.

Entering “600” yields 6s.

Entering “65535” yields 10min 55s 350ms.

Type of Service (IP)

Low Delay On Sets the “Low Delay” attribute in the IP header

Off The “Low Delay” attribute is not set.

High Throughput On Sets the “High Throughput” attribute in the IP header

Off The “High Throughput” attribute is not set.

High Reliability On Sets the “High Reliability” attribute in the IP header

Off The “High Reliability” attribute is not set.

2759-0101Modbus Settings in e!COCKPIT

14 Product manual | Version: 1.0.1

Configuring Modbus Networks (TCP/UDP) in e!COCKPIT

Table 2: “Settings” Panel – “Modbus Slave” Tab

Parameter Value Description

Keepalive (TCP)

Enabled On Enables “KeepAlive” for TCP connections

Off Disables “KeepAlive” for TCP connections

KeepAliveTime [s] 0 … 65535 The time span in seconds between the last data packet and the

first “KeepAlive” packet (probe)

KeepAliveInterval [s] 0 … 65535 Time between two successive connection attempts if “KeepAlive”

packet fails

KeepAliveProbes

[Number]

0 … 65535 Number of unanswered attempts until a connection is considered

lost

UDP Settings

UDP Port 1 … 65535 Port number for the UDP link

1 = minimum port number

502 = Modbus default port

65535 = maximum port number

Type of Service (IP)

Low Delay On Sets the “Low Delay” attribute in the IP header

Off The “Low Delay” attribute is not set.

High Throughput On Sets the “High Throughput” attribute in the IP header

Off The “High Throughput” attribute is not set.

High Reliability On Sets the “High Reliability” attribute in the IP header

Off The “High Reliability” attribute is not set.

Multicast Settings

Multicast Group 1 …

xxx.xxx.xxx. xxx Specifies the IP address of multicast groups 1 to 5

2759-0101 Modbus Settings in e!COCKPIT

Product manual | Version: 1.0.1 15

Configuring Modbus Networks (TCP/UDP) in e!COCKPIT

4.2 Slave Settings in the Data Point Configurator

The data point configurator is used to configure the fieldbus interface of a slave device.

The slave data points accessible via Modbus are created and configured here. The data

points that the slave makes available to all masters are specified.

If the slave is a fieldbus coupler or a third-party device, a data point overview resulting

from the node structure is displayed in the data point configurator. From the available

data points, you can select the ones that should be accessible to Modbus master de-

vices.

If a controller is used as a Modbus slave, data preprocessing can also be performed in

the controller if necessary. In this process, application variables are mapped to data

points. However, this is not usually necessary. The data points are also available to Mod-

bus master devices.

You can open data point configurators by double-clicking on the device tile (Network

view) below the Device Detail view. They are also accessible from the fieldbus configura-

tor.

Data point configurators are displayed in individual tabs according to the specific protocol.

If devices are selected in the Network view that communicate via multiple protocols, tabs

are displayed for all applicable protocols.

The Modbus data point configurator is shown on the “Modbus Slave” tab:

Figure5: Modbus Data Point Configurator – “Modbus Slave” Tab

Table 3: Modbus Data Point Configurator – “Modbus Slave” Tab

Parameter Description

Name Name of the Modbus data points

Data points are displayed in group as follows:

• PLC Variables

Under “PLC Variables,” you can view data points of the application and create new ones.

• Modbus Special Registers

These special registers contain pre-defined Modbus data points of the WAGO devices for de-

vice configuration and diagnostics.

• Generic Data Points

Generic data points are used to access existing data points, which can represent any position

in the existing Modbus process image, in a certain way (using function codes).

• Local Bus Data Points

Local bus data points result from the hardware or from attached I/O modules.

Note: You can find a more detailed expansion of the Modbus data points in 8Overview of the

Modbus Data Points [}26].

2759-0101Modbus Settings in e!COCKPIT

16 Product manual | Version: 1.0.1

Configuring Modbus Networks (TCP/UDP) in e!COCKPIT

Table 3: Modbus Data Point Configurator – “Modbus Slave” Tab

Parameter Description

Direction Indicates whether the data is input data or output data

Input The value of the variable is set exclusively via the bus and is readable in the pro-

gram. Write access in the program does not make sense because the value is

constantly overwritten from the outside.

Output The value of the variable is set in the program and is only readable from the out-

side.

Variable Name of variable

The name is always identical to the name of the application variable.

Mapping Indicates which variable is new and which variable already exists:

The variable is not yet available, will be newly created and can then be used in

the entire project.

An existing variable is used for mapping.

Data Type Displays the data type of the Modbus data point, and thus of the application variable. The following

data types are supported:

• BOOL

• BYTE

• WORD

• DWORD

• LWORD

• SINT

• USINT

• INT

• LINT

• UINT

• ULINT

• DINT

• UDINT

• REAL

• LREAL

• ARRAY OF BYTE

• ARRAY OF WORD

• ARRAY OF DWORD

• ARRAY OF LWORD

• ARRAY OF SINT

• ARRAY OF USINT

• ARRAY OF INT

• ARRAY OF LINT

• ARRAY OF UINT

• ARRAY OF ULINT

• ARRAY OF DINT

• ARRAY OF UDINT

• ARRAY OF REAL

• ARRAY OF LREAL

Length of

the Array

Displays the number of elements for arrays

MODBUS

Address

Displays the Modbus address of the variable – bit-based (coil) or register-based

Individual values of a row, e.g., data point names, can be changed by double-clicking on

the respective entry. Note that no periods (“.”) can occur in the name.

If the information icon (“i” in a blue circle) is displayed, this indicates that there are ad-

dressing overlaps. In other words, multiple data points are using the same memory regis-

ter. Double-click to modify the memory register.

To create or edit a new data point, the following functions are available in the context

menu (right-click on a row):

Figure6: Data Point Configurator Context Menu

2759-0101 Modbus Settings in e!COCKPIT

Product manual | Version: 1.0.1 17

Configuring Modbus Networks (TCP/UDP) in e!COCKPIT

Table 4: Data Point Configurator Context Menu

Sym-

bol

Button Description

[Add] Adds a Modbus data point

Note: Use [Add] for access to I/O modules of controllers (CODESYS V2), for

example; see scenario 8Connecting Controller (Master) to Controller

(CODESYS V2) (Slave) [}58]. For program variables, use [Add from Pro-

gram] (see below).

[Add from Program] Adds Modbus data points that represent variables of a controller program

Note: Use of this is described by an example in scenario 8Connecting Con-

troller (Master) to Controller (Slave) [}49].

One or more existing variables can be selected from the PLC program that are

to be published via Modbus.

[OK] adds the variables in the data point configurator.

[Cancel] closes the dialog.

Note: Simple data types are transferred directly via Modbus, while complex

data types (including structures) are mapped to word arrays. These are then

transferred via Modbus instead. If the data type used is known globally in the

project, the master can directly access the individual elements of the complex

variables, although Modbus does not use such a data type itself (see also

8Access to Simple and Complex Data Types [}28]).

[Delete] Deletes the Modbus data point

[Edit] Opens a dialog with further options (see description in the table below)

[Reset] This button is available if a name has been changed. The name of the mapping

variable is reset to the default name (data point name).

[Transfer] This button is available if a value has been changed (e.g., “Input” to “Output”)

and then multiple rows have been selected.

Clicking [Transfer] applies the value to all selected rows.

[Rename] This button is available if the data point configurator has been opened for the

slave device and there is a connection to another device. Clicking [Rename]

opens a dialog to rename the variable.

The [Edit] button opens a dialog with further setting options. The settings options differ

according to the group (“PLC Variables,” “Modbus Special Registers” or “Generic Data

Points”).

2759-0101Modbus Settings in e!COCKPIT

18 Product manual | Version: 1.0.1

Configuring Modbus Networks (TCP/UDP) in e!COCKPIT

Table 5: Editing Data Points

Parameter Description

Explicit Access Excludes the variables from any optimizations of the Modbus master

Function Code (Read) Function codes for reading the variables

Address (Read) Address for reading the data point in the Modbus process image

Function Code (Write) Function codes for writing the variables

Address (Write) Address for writing the data point in the Modbus process image

MODBUS Address If available: setting for bit-based (coil) or register-based access of the master

Specific function codes are used according to the setting.

2759-0101 Modbus Settings in e!COCKPIT

Product manual | Version: 1.0.1 19

Configuring Modbus Networks (TCP/UDP) in e!COCKPIT

4.3 Master and Connection Settings in the Fieldbus Configurator

Fieldbus configurators are primarily used to configure connections between two devices

on the data point level. The fieldbus configurator specifies the data points through which

communication occurs, the data that is exchanged on a specific master–slave connection

and the transmission quality used for communication (e.g., update rate, access time/

type).

The [Configurator] button opens the Fieldbus configurators in the Network view in the

context menu of the respective connector or fieldbus connection line.

Figure7: Open Fieldbus Configurator

The selected connection between the master and slave device is displayed at the top of

the fieldbus configurator.

Figure8: Selected Connection in the Modbus Fieldbus Configurator

The slave device on the right (blue) serves as a link to jump to the Device Detail view to

configure slave data points directly.

The “Selected Connection” drop-down list shows all connections to and from selected de-

vices of the graphical or tabular Network view:

• If a master is selected in the Network view, all existing connections to slaves are

shown in the drop-down list.

• If a slave is selected in the Network view, all connections that relate to the network are

shown in the drop-down list.

• If multiple devices are selected in the Network view, then the connections in the drop-

down list are limited to those that relate to these selected devices. Thus the selection

made in the Network view already pre-selects connection.

Changing the selection in the drop-down list of the fieldbus configurator does not affect

the selected devices in the Network view.

Modbus settings are entered on the following three tabs:

• 8“Modbus Master Variables” Tab [}20]

• 8“Connection Settings” Tab [}22]

• 8“Modbus Communication Channels” Tab [}23]

2759-0101Modbus Settings in e!COCKPIT

20 Product manual | Version: 1.0.1

Configuring Modbus Networks (TCP/UDP) in e!COCKPIT

Figure9: Tabs in the Modbus Fieldbus Configurator

Tip: The settings on the first tab suffice for most standard applications. In most cases,

you can keep the connection and channel settings the same.

4.3.1 “Modbus Master Variables” Tab

On the “Modbus Master Variables” tab, you can configure the data exchange between the

master and slave. The fieldbus configurator displays a split window:

• Right side of window: available slave data points

• Left side of window: master variables

(i.e., slave data points that are made available to the master)

Figure10: Modbus Fieldbus Configurator – “Modbus Master Variables” Tab

4.3.1.1 Available Slave Data Points

Available slave data points are displayed in a table on the right side of the fieldbus config-

urator as follows:

Table 6: Modbus Master Variables – Available Slave Data Points (Right Side)

Parameter Description

Data Points Tree with available data points, sorted into Modbus special registers, generic data points

and PLC variables

Data Type Variable data type

MODBUS Address Register/coil address of the data point

Right-clicking on the data point opens a context menu with the [Map] button. Use this

button to publish the slave data point via Modbus and to make it available to the master.

Page is loading ...

WAGO Configuring Modbus Networks (TCP/UDP) in e!COCKPIT User manual

WAGO Configuring Modbus Networks (TCP/UDP) in e!COCKPIT User manual

WAGO Configuring Modbus Networks (TCP/UDP) in e!COCKPIT User manual

Related papers

Other documents