Technical Description

FBP FieldBusPlug
MTQ22-FBP
Modbus TCP Interface

Description
The MTQ22-FBP Ethernet adapter module allows the connection
of UMC or FBP devices to Ethernet.
MTQ22-FBP Modbus TCP Interface

Technical Description

Please note the following

Target group
This description is intended for the use of trained specialists in electrical installation and control and automation engi-
neering, who are familiar with the applicable national standards.
Safety requirements
The responsible staff must ensure that the application or use of the products described satisfy all the requirements for
safety, including all the relevant laws, regulations, guidelines and standards.

Using this Handbook

Symbols
This technical document contains sentinels to point the reader to important information, potential risks and precaution
information. The following symbols are used:

Sign to indicate a potential dangerous situation that can cause damage of the
connected devices or the environment.

Sign to indicate important information and conditions.

Sign that indicates a potential dangerous situation that can cause human injuries.

Terms and Abbreviations

MRP Media redundancy protocol

MRC Media redundancy client
MRM Media redundancy manager
TCP/IP Transmission Control Protocol / Internet Protocol
UDP User Datagram Protocol
Client / Server The Modbus TCP messaging service provides a Client/Server communication between devices
connected on an Ethernet TCP/IP network. The device initiating the communication (e.g. a PLC)
is called the client.
The device answering the request is called the server (the MTQ22-FBP in this case).
Master / Slave Master/slave is a model of communication where one device e.g. a PLC has control over one or
more other devices (here MTQ22-FBP and UMC). In the Modbus TCP context the master is the
client and the slave is the server.
MAC Medium Access Control
MAC Address Unique address of every Ethernet device. The MAC address of the MTQ22-FBP is printed on
the nameplate.
PLC Programmable Logic Controller

Related Documents

Technical Documentation Document No.

MTQ22-FBP -2- FieldBusPlug / Issue: 07.2015

MTQ22-FBP Modbus TCP Interface

Technical Description

Content

Overview....................................................................................................................................................5
Ethernet...............................................................................................................................................6
Modbus TCP........................................................................................................................................6
MTQ22-FBP.........................................................................................................................................7
Supported FBP devices.......................................................................................................................7
Installation.................................................................................................................................................8
Mounting and Dismounting.................................................................................................................8
Electrical Installation............................................................................................................................8
Ethernet Commuication............................................................................................................................8
Configuration...........................................................................................................................................16
Online Mode......................................................................................................................................16
Modbus TCP Register Map.....................................................................................................................19
Supported Function Codes...............................................................................................................19
Modbus Address Table......................................................................................................................19
MTQ22 Status Data...........................................................................................................................19
Reading and Writing FBP Device Data..............................................................................................20
Example Addressmap with UMC100.................................................................................................22
Data Access in one block ordered by device....................................................................................26
Data access in one block ordered by data type................................................................................28
Diagnosis / Behaviour in Case of an Error..............................................................................................30
LED status indications.......................................................................................................................30
Reading the FBP device communication status...............................................................................31
Technical Data.........................................................................................................................................32
General..............................................................................................................................................32
EMC...................................................................................................................................................32
Ethernet and Modbus TCP Performance Data..................................................................................33
Ordering Data....................................................................................................................................33
Dimensions........................................................................................................................................34

FieldBusPlug / Issue: 07.2015 -3- MTQ22-FBP

MTQ22-FBP Modbus TCP Interface

Technical Description

Document History
D0202 page 29, 33 Supplementation of table values and supported bitrate
D0202 Rev B various Update of images, LLDP information added

MTQ22-FBP -4- FieldBusPlug / Issue: 07.2015

MTQ22-FBP Modbus TCP Interface

Technical Description

Overview
The MTQ22-FBP Ethernet adapter module supports the Modbus TCP network protocol.
This chapter contains a short description of Modbus TCP and the MTQ22-FBP Ethernet adapter module.

Highlighted Features
 The MTQ22-FBP Ethernet adapter module provides Ethernet connectivity for FieldbusPlug (FBP)
devices such as UMC100 or PST.
 Up to four FBP devices can be connected to one MTQ22-FBP. This allows a very cost efficient
connection of FBP devices to Ethernet.
 Through the MTQ22-FBP Ethernet Adapter module it is possible to:
- give control commands to the device (Start, Stop, Auto, etc.). The meaning of the commands depends
on the connected device
- read status information and actual values from the device
- change parameter values
- read maintenance counters
- reset a trip
 A built in two-port switch allows the flexible usage in bus, star or ring network topologies.
 Up to four masters can concurrently access the connected devices. The master connections can be supervised.
 Access via Modbus TCP can be restricted to a limited set of IP addresses.
 The Media Redundancy Protocol (MRP) is implemented (client). MRP is standardized in
IEC/EN 62439-2 and offers cable redundancy in case of a single failure.
 The Modbus address map offers flexible data access to best suit the needs of MobbusTCP client (e.g. PLC).
 Location supervision for detecting of interchanged drawers in withdrawable systems.

FieldBusPlug / Issue: 07.2015 -5- MTQ22-FBP

MTQ22-FBP Modbus TCP Interface

Technical Description

Ethernet
Ethernet standards support a variety of physical media (coaxial cable, twisted pair, fiber optics) and topologies (bus, ring and star).
The MTQ22-FBP Ethernet Adapter supports twisted pair as the physical media in a bus, ring and star topology.
Possible topologies are shown in Figure 1.
The MTQ22-FBP is compatible with Ethernet standards IEEE 802.3 and IEEE 802.3u.

Star Bus Ring

Switch Switch Switch

FBP FBP FBP

Device Device Device
FBP FBP FBP
Device Device Device
MTQ22 MTQ22 MTQ22
FBP FBP FBP
Device Device Device
FBP FBP FBP
Device Device Device

FBP FBP FBP

Device Device Device
FBP FBP FBP
Device Device Device
MTQ22 MTQ22 MTQ22
FBP FBP FBP
Device Device Device
FBP FBP FBP
Device Device Device

FBP Interface
Twisted Pair Ethenet

Figure 1:
Different topologies that can be realized with the MTQ22-FBP Ethernet Adapeter.
For the ring structure a special switch must be used.
See chapter Communication for more information.

Modbus TCP
Modbus TCP is a variant of the Modbus family of simple, vendor neutral communication protocols intended for supervision
and control of automation equipment. Specifically, it covers the use of Modbus messaging over TCP connection on an
IP network.
The implementation of the Modbus TCP server in the MTQ22-FBP module is done according to
- Modbus Application Protocol Specification v1.1b
- Modbus Messaging on TCP/IP Implementation Guide v1.0b
The supported Modbus commands are listed in chapter Communication. Four simultaneous Modbus TCP connections
are supported.
Further information on the Modbus TCP protocol is available on the world wide web from
www.modbus.org.

MTQ22-FBP -6- FieldBusPlug / Issue: 07.2015

MTQ22-FBP Modbus TCP Interface

Technical Description

MTQ22-FBP
Connectors X1 ... X4 are used to connect up to four FBP devices to the MTQ22-FBP. Ready made cables are available
for the connection in withdrawable systems or non-withdrawable systems. The order codes are available in chapter
Ordering Data. On the left side of the port connectors LEDs show the current communication status. See chapter Diag-
nosis / Behavior in Case of an Error for details. The Micro USB connector X5 allows device configuration using a PC. A
standard USB cable can be used. Two RJ45 sockets E1 and E2 offer Ethernet connectivity. The communication status
of each interface is shown by two LEDs. The MTQ22-FBP must be supplied with 24VDC via X6.

 MTQ22

X1
Port 1

Port 2 X2
FBP Device
Status LEDs
RDY Interface
FBP Device
Ports
Interface TCP
Ports
Port 3 X3

Port 4 X4

X5

Data
Micro USB
Configuration
E1
Port (Type B)

Link Ethernet
Interfaces
Data

E2
Power X6
Supply
Link
Terminals
24V
0V
DC

Figure 2:
Top view of the MTQ22-FBP. Four FBP devices can be connected to the MTQ22 via the ports X1 to X4.
The standard Micro USB connector X5 allows to configure the device.
The two Ethernet interfaces E1, E2 allows the flexible integration into different network structures.

Supported FBP devices

The following FBP devices can be connected to the MTQ22-FBP.

• UMC22 (all revisions)
• UMC100 (all revisions)
• Other FBP devices as listed in the configuration tool

FieldBusPlug / Issue: 07.2015 -7- MTQ22-FBP

MTQ22-FBP Modbus TCP Interface

Technical Description

Installation
Mounting and Dismounting
You can mount and unmount the MTQ22-FBP onto a 35 mm standard mounting rail, without tools.

Mounting

Dismounting

Figure: 3
Mounting and dismounting the MTQ22-FBP on a 35 mm standard mounting rail.

Electrical Installation

General
Arrange the communication cables as far away from the motor cables as possible. Avoid parallel runs. Use bushings at
cable entries.

Ethernet Connection
The network cable is connected to the RJ45 connectors on the MTQ22-FBP module. Standard CAT5 UTP, FTP or STP
cables can be used. The shield of the RJ45 cable is connected to the shield of connector X6.

Power Supply Connection

The MTQ22-FBP has to be supplied with 24 VDC on the terminals X6. Using the shield connection is optional.

MTQ22-FBP -8- FieldBusPlug / Issue: 07.2015

MTQ22-FBP Modbus TCP Interface

Technical Description
FBP Device Connection
FBP devices (e. g. UMC100) can be connected point to point using the ready made cable CDP17.
This option is recommended in non withdrawable installations (e.g. using a mounting plate for the installation).
In case the FBP device is mounted within a withdrawable unit (drawer) all the needed cables and auxiliaries are
available as well as shown in detail in the figure below.

The distance between the MTQ22-FBP and the FBP device shall not exceed 3 meter.
The communication cables between MTQ22-FBP and UMC100 shall not run in parallel
to the motor cables.

X6 X7 X8
 MTQ22
DO Relay T1 T2 Ca Cb
C C 0 1 2

CPD18 CPD18 to X1
X1
X9
Port 1

Port 2 X2
Trip/Rdy Run
to X2
RDY
Power DO DI 24V
0V 24V 3 0 ... 5
X5 TCP
to X3
Port 3 X3

Port 4 X4

X5

Data

E1
X6 X7 X8
DO Relay
C C 0 1 2
T1 T2 Ca Cb
Link
CPD18 CPD18 to X4 Data
X9 E2
X6
Link
Trip/Rdy Run

24V
Power DO DI 24V 0V
0V 24V 3 0 ... 5 DC
X5

Figure 4:
Solution for motor Control Centers in drawout technology.
Connecting the MTQ22-FBP ports 1 to 4 - connectors X1 to X4 - to the UMC mounted inside a drawer.

FieldBusPlug / Issue: 07.2015 -9- MTQ22-FBP

MTQ22-FBP Modbus TCP Interface

Technical Description

X6 X7 X8
 MTQ22
DO Relay T1 T2 Ca Cb

CPD23
C C 0 1 2

to X1
X1
X9
Port 1

Port 2 X2
Trip/Rdy Run
to X2
RDY
Power DO DI 24V
0V 24V 3 0 ... 5
X5 TCP
to X3
Port 3 X3

Port 4 X4

X5

Data

E1
X6 X7 X8
DO Relay T1 T2 Ca Cb
Link
CPD23
C C 0 1 2

to X4 Data
X9 E2
X6
Link
Trip/Rdy Run

24V
Power DO DI 24V 0V
0V 24V 3 0 ... 5 DC
X5

Figure 5:
Connecting the MTQ22-FBP ports 1 to 4 - connectors X1 to X4 - to the UMC.

MTQ22-FBP - 10 - FieldBusPlug / Issue: 07.2015

MTQ22-FBP Modbus TCP Interface

Technical Description

Ethernet Commuication
Star topology
In star topology only one RJ45 cable must be connected between the MTQ22-FBP and a switch. An unmanaged stan-
dard switch can be used in this operation mode.

Bus topology
In bus topology the internal two-port-switch of the MTQ22-FBP is used to connect MTQ22-FBP to MTQ22-FBP. Only
the first MTQ22-FBP in the chain needs to be connected to a switch. The second Ethernet port of the last MTQ22-FBP
can be left unconnected. An unmanaged standard switch can be used in this operation mode.

Ring topology with network redundancy

The ring topology offers cable redundancy on Ethernet side. The topology is similar to the bus topology but the last
MTQ22-FBP in the chain must be connected to the switch again to close the ring. A managed switch supporting MRP
and acting as MRP manager must be used in this case. The redundancy protocol implemented in the MTQ22-FBP is
according to EN/IEC 62439-2.
The MRP standard defines two principal device roles in a MRP network. The MRP manager which is typically a
managed network switch, and MRP clients which are typically automation devices like the MTQ22-FBP.
The MRP master sends out test telegrams cyclically to check the health status of the network. If everything is ok it
blocks telegrams on one side of its internal switch to avoid loops (left side of the next figure). If somewhere in the net-
work a fault is detected the MRP master reorganizes the network and closes its internal switch. So all network nodes
are still accessible (right side of next figure).

PLC / DCS PLC / DCS

Network Switch / Network Switch /

MRP Manager MRP Manger

UMC UMC

UMC UMC
MTQ22 MTQ22
UMC UMC

UMC UMC

UMC UMC

UMC UMC
MTQ22 MTQ22
UMC UMC

UMC UMC

FBP Interface
Twisted Pair Ethenet

Figure 6:
This figure shows how a single network failure is corrected in a MRP network. The left side shows the intact network.
The MRP manager has opened its internal switch, so all nodes can be reached using the green dotted route.
On the right side the MRP master has detected a network problem and has closed its internal switch to ensure
connectivity to all network nodes. The blue dotted path shows how all network nodes are reached now.

FieldBusPlug / Issue: 07.2015 - 11 - MTQ22-FBP

MTQ22-FBP Modbus TCP Interface

Technical Description

Ring topology with network redundancy in drawout systems

Drawout systems are used where highest availability and shortest downtimes should be achieved. In such systems all
the devices required for a single motor feeder are installed into a drawer to ensure fast and easy exchange in the event
of a failure. Here the MTQ22-FBP offers the following benefits:
- No need to bring high speed Ethernet into the withdrawable unit
- Stable communication even if two or more drawers are withdrawn.
The right figure below shows the situation where devices have integrated Ethernet and two drawers are withdrawn.
Devices between these two drawers cannot be reached anymore. Also the MRP redundancy function cannot solve
this situation.
On the left side the solution with MTQ22-FBP is shown. The MTQ22-FBP is not mounted inside the drawer but is in-
stalled in the cable compartment where the switch and other central equipment are installed. The Ethernet cable is not
connected to the UMC mounted inside the drawer. But the robust and well known FBP interface goes to the UMC in
the drawer. Therefore no special measures are required in the case that one or more drawers are withdrawn.
A removed drawer cannot disturb the Ethernet communication in any way.

PLC / DCS PLC / DCS

Network Switch /
Network Switch /
MRP Manager MRP Manager
Drawer UMC
Device with
integrated
Drawer
Ethernet

MTQ22
Withdrawn
Drawer

All devices
reachable

Devices not
reachable

MTQ22 Withdrawn
Withdrawn Drawer
Drawer

Cable compartment Drawers

Third party device with Ethernet inside the drawer

Problems arise with multiple drawers withdrawn!

MTQ22
Withdrawn
Drawer
FBP Connection cable
Cable compartment Drawers Twisted Pair Ethenet
ABB solution with MTQ22-FBP
No problems with drawers missing.

Figure 7:
The left side shows the benefits not having Ethernet connected inside a drawer.

MTQ22-FBP - 12 - FieldBusPlug / Issue: 07.2015

MTQ22-FBP Modbus TCP Interface

Technical Description

Switch Configuration for Ring Topology

Managed switches of various vendors offer the possibility to configure ring topologies with MRP redundancy.
In the following exampe a network switch from Belden/Hirschmann is used as example.
The screenshots are taken from the RS20 configuration tool.
• Follow the setup instructions of the switch manual
• Open the "Redundancy" page and select the marked options shown in the figure below.
To get help press the Help button.

Figure 8:
The page 'Ring Redundancy' allows to enable the MRP redundancy protocol and to define the ports
that are the start and end of the ring.

FieldBusPlug / Issue: 07.2015 - 13 - MTQ22-FBP

MTQ22-FBP Modbus TCP Interface

Technical Description

Usage with multiple Modbus TCP Clients

The MTQ22-FBP allows the concurrent communication with up to four Modbus TCP clients (e.g. PLCs). The MTQ22-
FBP optionally can supervise the clients and signal a bus fault to the connected FBP devices in case of a fault. Note the
following points:
• specify the number of clients that should be supervised and the number of clients that have to be present at least.
See section Configuration for more info.
• Only one of the concurrent PCLs should send command data to a FBP device (e.g. UMC100). Otherwise there might
arise conflicts (e.g. if two different command words are sent at the same time).
• Different Modbus TCP clients can control FBP devices connected to the same MTQ22-FBP.
E. g. Modbus TCP client 'A' controls the UMC100 connected to port 1 and client 'B' controls the FBP devices
connected to port 2 - 4
• Monitoring of all FBP devices from the clients is always possible

ModbusTCP
PLC Client controlling
the UMCs

Switch

UMC UMC
Panel PC
I=23.5 A UMC UMC
Motor On
Fault: -
MTQ22 MTQ22
UMC UMC

ModbusTCP Client
reading diagnosis UMC UMC
and status data
from the UMCs
Twisted Pair Ethenet MCC

Figure 9:
The MTQ22-FBP allows up to four concurrent Modbus TCP clients.
This can be used to monitor the FBP devices (e. g. UMCs as shown here) in the MCC with the help of a
panel PC for example. At the same time the PLC controls the UMCs.

MTQ22-FBP - 14 - FieldBusPlug / Issue: 07.2015

MTQ22-FBP Modbus TCP Interface

Technical Description

Usage in Remote Access Applications

In some applications it is essential to do monitoring or even control remotely, e. g. in case of regional distributed pump
stations. In these case the use of standard Ethernet is of great benefits because standard routers, gateways etc. can be
used.

Take measures where only authorized users have access to the remote installation
and can read or write data.

The following figure shows a system with a central SCADA (supervision control and data acquisition) station and
several remote locations.
The SCADA system is connected to the remote locations via a model or other wireless or wired network.

Radio or other
Firewall communication Central SCADA System
Gateway link
etc.

UMC
MTQ22

Remote station

Switch Firewall
Gateway
etc.

Local Panel PC
I=23.5 A UMC
Motor On
Fault: -
MTQ22
UMC
ModbusTCP Client
for on site control
Remote station

Figure 10:
TCP-IP based communication makes the integration of distributed stations much simpler.

FieldBusPlug / Issue: 07.2015 - 15 - MTQ22-FBP

MTQ22-FBP Modbus TCP Interface

Technical Description

Configuration
An easy to use PC configuration tool is provided to adjust the parameters of the MTQ22-FBP. The PC can be connected
to the MTQ22-FBP with a standard Micro USB-cable. Together with the software the file "readme.txt file is provided
which contains the latest installation and setup instructions.

 MTQ22

X1
Port 1

Port 2 X2
RDY

TCP
 Port 3 X3

Micro USB Port 4 X4

X5

Data

 E1

Link
Data
:8 http://www.abb.com
> Control Products and Systems E2
> Control Products, Low Voltage X6
> Fieldbus Devices Link
> Ethernet Interfaces
O Software
....
 0V
24V
DC

Figure 11:
Connecting the MTQ22-FBP to a service Laptop.
The MTQ22-FBP must be supplied with 24V DC before the configuration can take place .
For the connection a Micro USB cable ) is used.
On the PC the MTQ22 configuration software must be installed .

First Steps
If the MTQ22-FBP is connected for the first time the required USB driver has to be installed. The Microsoft USB driver is
not part of the software package because of license reasons. It is pre-installed on Windows 7, for XP it must be down-
loaded separately from Microsoft. Follow the setup instructions of Windows to install the new hardware. The required
driver inf-file is part of the software package.
After startup of the application the screen is split into three areas - left, middle and right.
In the left area you can add as many MTQs as you have in your project. In the middle area the configuration parameters
per MTQ22-FBP are displayed. You can change them offline or online. The right area shows a short help text.
See figure 12.

Online Mode
In online mode it is possible to read the configuration data stored in a MTQ22-FBP back into the configuration tool or
to write the data from the configuration tool down into the MTQ22. The online connection is realized via USB.
On USB side the serial profile is used. Therefore Windows detects the MTQ22-FBP interface as a serial link and creates
a COM port for it. Before going online, lookup the COM port assigned by Windows and set it in the configuration tool.
Now press the connect button on the toolbar. A closed connector indicates online mode.

To up- or download parameters to the MTQ22-FBP the device must be supplied with 24 V DC.
The USB port is galvanically isolated to protect the PC in case potential differences exist between
the MTQ22 ground and the PC ground.

MTQ22-FBP - 16 - FieldBusPlug / Issue: 07.2015

MTQ22-FBP Modbus TCP Interface

Technical Description

Figure 12:
The configuration tool allows to set the parameters in an easy way.
Several MTQ22-FBP devices can be created in the device tree (left).
The final configuration can be saved to disk and downloaded into the devices using a standard USB cable.

Parameters
Master Configuration and Supervision
The MTQ22-FBP supports up to four parallel connections to Modbus TCP clients (i.e. PLCs). It is possible to monitor these
clients for activity and signal a communication fault to the connected FBP devices after an adjustable timeout time.
For security reasons the access to the MTQ22-FBP can be limited to clients having IP addresses within a user defined
range. Single addresses or address ranges can be defined.

Network Settings
Before any Ethernet communication takes place the MTQ22-FBP must have an IP address. It is possible to provide a
static address or obtain the address via DHCP or the BootP protocol.
In case of a static IP address also the netmask and the gateway address must be set manually.

FBP Device Settings

Up to four FBP devices can be connected to the MTQ22-FBP. For each port the connected device type (or NONE) must
be specified. The MTQ22-FBP then monitors the presence of the configured FBP device.

Position Supervision
The MTQ22-FBP detects accidental permutation of devices connected to it. Therefore a specific address (1...254) has
to be set per port which must match the address (1...254) set in the connected device. The MTQ22-FBP offers status
registers to read the actual FBP device supervision status via Modbus TCP.
See chapter Address Map for details.

FieldBusPlug / Issue: 07.2015 - 17 - MTQ22-FBP

MTQ22-FBP Modbus TCP Interface

Technical Description

Parameter Overview
Before using the MTQ22-FBP device the following parameters must be set

Parameter name Default settings

DHCP / BOOTP Manual
IP Address 192.168.171.254
Subnet Mask 255.255.255.0
Standard Gateway 192.168.171.1
Number of Modbus TCP masters under supervision 1
Allowed number of supervised connections missing 0
Allowed Modbus TCP IP Address for master 1 ... 4 0.0.0.0 ... 255.255.255.255 for master 1
0.0.0.0 ... 0.0.0.0 for master 2-4
Timeout for master 1 ... 4 10s
Device port 1 ... 4 used UMC100
Device address for device 1 ... 4 1,2,3,4

MTQ22-FBP - 18 - FieldBusPlug / Issue: 07.2015

MTQ22-FBP Modbus TCP Interface

Technical Description

Modbus TCP Register Map

Supported Function Codes
The following Modbus Function Codes are supported:

Function Code Explanation

FC1 Read coils
FC2 Read input discretes
FC3 Read multiple registers
FC4 Read input registers
FC5 Write single coil
FC6 Write single register
FC7 Read exception status
FC15 Force multiple coils
FC16 Write multiple registers
FC23 Read/Write multiple registers

Modbus Address Table

The I/O-data as well as parameter, diagnosis and configuration data of the connected FBP devices can be accessed
applying the supported function codes on the addresses described in the following table 2.

Modbus TCP counts registers beginning with one. But on the bus registers start counting from zero.
The addresses in this manual describe the addresses that are transmitted on the network.
Depending on your client application it might be necessary to increment all addresses by one.

Device I/O data and diagnosis can be accessed by three different ways:
• separate access to each data type (boolean values or analog values) of each module.
This requires sending several Modbus telegrams to the dedicated addresses
• access to the data of all connected devices with one MODBUS telegram ordered by module connected to port 1..4
• access to the data of all connected devices with one MODBUS telegram ordered by data type DI, AI, Diagnosis or DO, AO.

MTQ22 Status Data

Adress Data Size Access

0x0000 - 0x007F (HEX) General Parameter for 128 Words Read, Write
0 - 127 (DEC) MTQ22-FBP (reserved for
further use)
0x0080 - 0x0083 (HEX) Diagnostics (one block) 4 Words Read
128 - 131 (DEC)
0x0080 - 0x0083 (HEX) FBP Port 1 ... Port 4 com- 1 Word Read
128 - 131 (DEC) munication status
0x0090 - 0x0093 (HEX) Number of connection 1 Word Read / Write
144 - 147 (DEC) losses between FBP device
(e.g. UMC100) and MTQ22-
FBP

See section Diagnosis / Behaviour in Case of an Error for an explanation of the communication status codes.

FieldBusPlug / Issue: 07.2015 - 19 - MTQ22-FBP

MTQ22-FBP Modbus TCP Interface

Technical Description

Reading and Writing FBP Device Data

The following tables show how to generally access data of the FBP-devices connected to port one to port four of the
MTQ22-FBP. The manuals of the connected FBP devices are needed in addition to understand what data is provided
and thereof derive the length of the input and output data telegrams.

Individual data access by device

This method allows to individually access data of a connected device via single registers or groups of registers
organized in words.

Adress for data access to device

connected to port Data Length Access
1 2 3 4
0x0C00 0x0C20 0x0C40 0x0C60 Diagnosis data 0 ... 16 registers* Read
dec 3072 dec 3104 dec 3136 dec 3168 of connected
device
0x1000 0x1010 0x1020 0x1030 Digital Inputs (DI) 0 ... 16 registers* Read
dec 4096 dec 4112 dec 4128 4144 (0 - 32 bytes)
0x1800 0x1810 0x1820 0x1830 Digital Outputs 0 ... 16 registers* Write,
dec 6144 dec 6160 dec 6176 dec 6192 (DO) (0 - 32 bytes) Read
0x2000 0x2100 0x2200 0x2300 Analog Inputs 0 ... 256 registers Read
dec 8192 dec 8448 dec 8704 dec 8960 (AI)
0x2800 0x2900 0x2A00 0x2B00 Analog Outputs 0..256 registers Write,
dec 10240 dec 10496 dec 10752 dec 11008 (AO) Read
*) Concrete number of registers (length) depends on the connected device.

The following table shows the data which can be accessed using bit access requests.
Adress for data access to device
connected to port Data Length Access
1 2 3 4
0x1000 0x1100 0x1200 0x1300 Digital Inputs (DI) 0 ... 256 Bit* Read Coils,
dec 4096 dec 4352 dec 4608 dec 4864 bitwise access Read Multiple Coils
0x1800 0x1900 0x1A00 0x1B00 Digital Outputs 0 ... 256 Bit* Write Coils,
dec 6144 dec 6400 dec 6656 dec 6912 (DO) bitwise Write Multiple Coils
access Read Coils,
Read Multiple Coils
*) Concrete number of bits depends on the connected device.

MTQ22-FBP - 20 - FieldBusPlug / Issue: 07.2015

MTQ22-FBP Modbus TCP Interface

Technical Description

Access to all data ordered by device

For performance reasons some applications might require access to the entire I/O data with one Modbus TCP telegram.
This access method allows to read or write data of all the connected devices with one request.

Adress Data Length Access

0x3000 Input Data Block 0...1216 Read
dec 12288 DI1 AI1 Diag1 DI2 AI2 Diag2 ... DI4 AI4 Diag4 registers

0x4000 Output Data Block 0...1216 Write, Read

dec 16384 DO1 AO1 DO2 AO2 DO3 AO3 DO4 AO4 registers

The total input data block length depends of the length of the AI, DI, Diagnosis data of each configured
device.
The total output data length depends of the length of the AO, DO data of each configured device.
In case only three ports are used (e.g. port four used as spare) the data length for device four must be
set to zero in the input and output data block.
If a device does not provide a certain data type (e. g. AO) the length of this field has to be set to zero.
Only word access is supported in this address range.

Access to all data ordered by data type

For performance reasons some applications might require access to the entire I/O data with one Modbus TCP telegram.
This access method allows to read or write data of all devices ordered by data type

Adress Data Length Access

0x5000 Input Data Block 0...1216 Read
dec 20480 DI1 DI2 DI3 DI4 AI1 ... AI4 Diag1 ... Diag4 registers

0x6000 Output Data Block 0...1216 Write, Read

dec 24576 DO1 ... DO4 AO1 ... AO4 registers

The total input data block length depends of the length of the AI, DI, Diagnosis data of each configured
device.
The total output data length depends of the length of the AO, DO data of each configured device.
In case only three ports are used (e. g. port four used as spare) the data length for device four must
be set to zero in the input and output data block.
If a device does not provide a certain data type (e. g. AO) the length of this field has to be set to zero.
Only word access is supported in this address range

FieldBusPlug / Issue: 07.2015 - 21 - MTQ22-FBP

MTQ22-FBP Modbus TCP Interface

Technical Description

Example Addressmap with UMC100

The previous section described the Modbus address map in a device independant manner.
In this section the address map is presented for the case that four UMC100 devices are connected.

Note that the UMC100 allows to remap the content of the IO data bytes.
In case you changed the IO data content in an own function block application the content of
the data bytes might be different compared to the data shown in the following tables.

UMC100-I/O data referrred to in section A1 Parameters and Data Structures on a Fieldbus: in the UMC100 manual

Diag: 8 Bytes (4 Words)

Monitoring Data:
DI: 2 Bytes (1 Word) DI + AI + Diag = 24 Bytes = 12 Words
DO: 4 Bytes (2 Words)
Command Data:
AI: 14 Bytes (7 Words) DO + AO = 12 Bytes = 6 Words
AO: 8 Bytes (4 Words)

UMC100
Device
Port 1
UMC100
Device
MTQ22
UMC100
Device
Port 4
UMC100
Device

Individual data access by device

This method allows to individually access data of a connected device via single registers or groups of registers.

Adress for data access to device

connected to port Data Length Access
1 2 3 4
0x0C00 0x0C20 0x0C40 0x0C60 Diagnosis 4 Words ( = 8 Bytes) Read
each UMC
0x1000 0x1010 0x1020 0x1030 Digital Inputs (DI) 1 Word ( = 2 Bytes) Read
each UMC
0x1000 0x1100 0x1200 0x1300 DI bitwise 0 ... 16 Bit each UMC Read Coils,
Read Multiple Coils
0x1800 0x1900 0x1A00 0x1B00 Digital Outputs 2 Word (= 4 Byte) each Write, Read
(DO) UMC
0x1800 0x1810 0x1820 0x1830 DO bitwise 0..32 Bit each UMC Write Coils,
Write Multiple Coils
Read Coils,
Read Multiple Coils

0x2000 0x2100 0x2200 0x2300 Analog Inputs (AI) 7 Words each UMC Read
0x2800 0x2900 0x2A00 0x2B00 Analog Outputs 4 Words each UMC Write, Read
(AO)

MTQ22-FBP - 22 - FieldBusPlug / Issue: 07.2015

MTQ22-FBP Modbus TCP Interface

Technical Description

Word oriented access to the monitoring data of UMC100 acc. to the UMC100 manual section
A1 Parameters and Data Structures on a Fieldbus
UMC UMC UMC UMC Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit1 Bit 0
at port at port at port at port Bit 15 Bit 8
1 2 3 4
Address
Sum- Summa- Local Reverse Overload Run Off Run
Low-
mary ry Fault Control Lockout warning Forward / Reverse /
Byte
Warning Time3 Opening Closing
0x1000 0x1010 0x1020 0x1030
dec 4096 dec 4112 dec 4128 dec 4144 UMC100 UMC100 UMC100 UMC100 UMC100 UMC100 Run -
DI5 DI4 DI3 DI2 DI1 DI0 Fast High-
For- Byte
ward

Bit oriented access to the monitoring data of UMC100 acc. to the UMC100 manual section
A1 Parameters and Data Structures on a Fieldbus
UMC UMC UMC UMC Bit Information
at port at port at port at port
1 2 3 4
Address
0x1000 0x1100 0x1200 0x1300 Run Reverse /
Bit 0
dec 4096 dec 4352 dec 4608 dec 4864 Closing
0x1001 0x1101 0x1201 0x1301 Off
dec 4097 dec 4353 dec 4609 dec 4865
...
... ... ... ...
0x100F 0x130F 0x130F 0x130F UMC100 DI5
Bit 15
dec 4111 dec 4867 dec 4823 dec 4879

Word oriented access to the command data of UMC100 acc. to the UMC100 manual section
A1 Parameters and Data Structures on a Fieldbus
UMC UMC UMC UMC Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit1 Bit 0
at port at port at port at port Bit 15 Bit 8
1 2 3 4 Bit 23 Bit 16
Bit 31 Bit 24
Address Low
Byte

- Fault Auto Prepare - Run For- Off Run

Reset Mode Emergen- ward / Reverse /
cy Start Opening Closing High
Byte
0x1800 0x1810 0x1820 0x1830
dec 6144 dec 6160 dec 6176 dec 6192 UMC100 UMC100 UMC100 UMC100 - - Run - Low
DO2 DO1 DO0 24VDC Fast Byte
Out For-
ward High
Byte

VI15x - - - DX1xx DX1xx DX1xx DX1xx

DO0 DO3 DO2 DO1 DO0
0x1801 0x1811 0x1821 0x1831
dec 6145 dec 6161 dec 6177 dec 6193
- - - - - - - -

Bit oriented access to the command data of UMC100 acc. to the UMC100 manual section
A1 Parameters and Data Structures on a Fieldbus
UMC UMC UMC UMC Bit Information
at port at port at port at port
1 2 3 4
Address Bit 0

0x1800 0x1900 0x1A00 0x1B00 Run Reverse / Closing

dec 6144 dec 6400 dec 6656 dec 6912

0x1801 0x1901 0x1A01 0x1B01 Off

dec 6145 dec 6401 dec 6657 dec 6913

... ... ... ... ... Bit 31

0x1820 0x 191F 0x1A1F 0x1B1F -

dec 6175 dec 6431 dec 6687 dec 6943

FieldBusPlug / Issue: 07.2015 - 23 - MTQ22-FBP

MTQ22-FBP Modbus TCP Interface

Technical Description

Analog Inputs of UMC100 acc. to the UMC100 manual section

A1 Parameters and Data Structures on a Fieldbus
UMC at UMC at UMC at UMC at
port 1 port 1 port 1 port 1 Data
Address
0x2000 0x2100 0x2200 0x2300
Motor Current in % of Ie (0% - 800%
dec 8192 dec 8448 dec 8704 dec 8960
0x2001 0x2101 0x2201 0x2301
Analogue Word (Thermal Load: 0% - 100%)
dec 8193 dec 8448 dec 8704 dec 8961

0x2002 0x2102 0x2202 0x2302

Analogue Word (Time to trip in seconds)
dec 8194 dec 8450 dec 8704 dec 8962

0x2003 0x2103 0x2203 0x2303

Analogue Word (Time to restart in seconds)
dec 8195 dec 8451 dec 8704 dec 8963

0x2004 0x2104 0x2204 0x2304

Analogue Word (Active power in selected scale)
dec 8196 dec 8452 dec 8704 dec 8964

DX1xx DX1xx DX1xx DX1xx DX1xx DX1xx DX1xx DX1xx Low

DI7 DI6 DI5 DI4 DI3 DI2 DI1 DI0 Byte

0x2005 0x2105 0x2205 0x2305 - - Run Out of Torque Torque End Pos End Pos
dec 8197 dec 8453 dec 8704 dec 8965 Time Positi- Open1 Closed1 Open1 Closed1
Excee- on1
ded1 High
Byte

U Imbal. U Under- Under- Under- Under- Over- Overpo- Low

warn Imbal. voltage voltage power power power wer trip Byte
trip warn trip warn trip warn

0x2006 0x2106 0x2206 0x2306

dec 8198 dec 8454 dec 8704 dec 8966
Earth Earth Cooling - THD No start 1 start More than High
fault fault time war- possi- left 5) 1 start Byte
warning trip running ning ble5) left5)

Analog Outputs of UMC100 acc. to the UMC100 manual section

A1 Parameters and Data Structures on a Fieldbus
UMC at UMC at UMC at UMC at
port 1 port 1 port 1 port 1 Data
Address
0x2800 0x2900 0x2A00 0x2B00 Analogue Word

0x2801 0x2901 0x2A01 0x2B01 Analogue Word

0x2802 0x2902 0x2A02 0x2B02 Analogue Word

0x2803 0x2903 0x2A03 0x2B03 Analogue Word

MTQ22-FBP - 24 - FieldBusPlug / Issue: 07.2015

MTQ22-FBP Modbus TCP Interface

Technical Description

Diagnosis Data of UMC100 according to the UMC100 manual section

A1 Parameters and Data Structures on a Fieldbus

UMC UMC UMC UMC Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit1 Bit 0
at at at port at port
port 1 port 2 3 4
Adress
Check- PTC wiring PTC hot Pre-waring Locked ro- Phase im- Phase Thermal
back failure thermal tor during balance1 loss1 overload trip
missing model start-up
(stall)
0x0C00 0x0C20 0x0C40 0x0C60
Actuator UMC self- Earth fault Eart I above I above I below I below low
dec 3072 dec 3104 dec 3136 dec 3168 problem1 test error pre- fault trip high high cur- low current trip
warning (internal or current rent trip current threshold
externally warning threshold warning
triggered) threshold thresh-
old

Trip/Warn- Trip/Warn- Trip/ Trip/Warn- Trip/Warn- HW fault Custom IO module

ing from ing from Warn- ing from ing from on IO applica- missing
AuxFault AuxFault ing from AuxFault AuxFault module tion
function function AuxFault function function error
block input block input function block input block input
52) 42) block 22) 12)
0x0C01 0xC021 0x0C41 0x0C61 input 32)

dec 3073 dec 3105 dec 3137 dec 3167 - - - - Trip trig- Trip trig- Trip trig- Trip / Warn-
gered from gered from gered ing from
Multifunc- Multifunc- from AuxFault
tion input tion input Multi- function
DI2 DI1 function block input
input 62)
DI0

- - THD Voltage out Overload Underload - -

Warning of spec1 power power1
0x0C02 0x0C22 0x0C42 0x0C62
- - Cooling Just one Num Starts - - -
dec 3074 dec 3106 dec 3138 dec 3168 Time start left Overrun
Running

Extended Param- - - - - - -
diagnosis eter out of
is avail- range
0x0C03 0x0C23 0x0C43 0x0C63 able1).

dec 3075 dec 3107 dec 3139 dec 3169 Fault code. See section "Error Handling, Maintenance and Service-> Fault Messages" for a description of the
code.

FieldBusPlug / Issue: 07.2015 - 25 - MTQ22-FBP

 MTQ22-FBP Modbus TCP Interface

Technical Description

Data Access in one block ordered by device

This section explains how to access the data of the connected devices in one block.
Only one Modbus TCP read request is required to read all monitoring data and only one request is necessary to write all command
data.

Monitoring Data
This address map shows how the complete monitoring data from up to four UMCs can be read in one block.
The data is ordered without any gaps after each other in the followng way.
DI AI Diag DI AI Diag ... DI AI Diag
UMC1 UMC1 UMC1 UMC2 UMC2 UMC2 UMC4 UMC4 UMC4

The following table shows in detail how the data is organized

UMC at UMC at UMC at UMC at Data

port 1 port 2 port 3 port 4
0x3000 0x300C 0x3018 0x3024
dec 12288 dec 12300 dec 12312 dec 12324 Summary Summa- Local Rev Lockout Overload Run Fwd / Off Run Rev/
Warning ry Fault Control Time warning Opening Closing
UMC100 UMC100 UMC100 UMC100 DI2 UMC100 UMC100 DI0 Run Fast -
DI5 DI4 DI3 DI1 Fwd

0x3001 0x300D 0x3019 0x3025 Motor Current in % of Ie (0% - 800%

dec 12289 dec 12301 dec 12313 dec 12325

0x3002 0x300E 0x300A 0x3026 Analogue Word (Thermal Load: 0% - 100%)

dec 12290 dec 12302 dec 12314 dec 12326

0x3003 0x300F 0x301B 0x3027 Analogue Word (Time to trip in seconds)

dec 12291 dec 12303 dec 12315 dec 12327

0x3004 0x3010 0x301C 0x3028 Analogue Word (Time to restart in seconds)

dec 12292 dec 12304 dec 12316 dec 12328

0x3005 0x3011 0x301D 0x3029 Analogue Word (Active power in selected scale)
dec 12293 dec 12305 dec 12317 dec 12329

0x3006 0x3012 0x301E 0x302A

dec 12294 dec 12306 dec 12318 dec 12330 DX1xx DI7 DX1xx DX1xx DX1xx DX1xx DX1xx DX1xx DX1xx
DI6 DI5 DI4 DI3 DI2 DI1 DI0

- - Run Time Out of Position Torque Torque End Pos End Pos
Exceeded1 Open Closed Open Closed

0x3007 0x3013 0x301F 0x302B

dec 12295 dec 12307 dec 12319 dec 12331 U Imbal. U Imbal. Undervoltage Undervol- Underpo- Underpo- Overpo- Overpower
warn trip warn tage trip wer warn wer trip wer warn trip

Earth fault Earth Cooling time - THD No start One start More than
warning fault trip running warning possible left one start left

0x3008 0x3014 0x3020 0x302C

7 6 5 4 3 2 1 0
dec 12296 dec 12308 dec 12320 dec 12332 CB miss- PTC wiring PTC hot Pre-warn Locked Phase Phase loss Thermal
ing failure therm. model rotor imbalance OL trip

Actuator UMC self- Earth fault Eart fault trip I > warning I > trip I < warning I < trip
Diagnostics Word #1 problem test error pre-warning threshold threshold threshold threshold

0x3009 0x3015 0x3021 0x302D

15 14 13 12 11 10 9 8
dec 12297 dec 12308 dec 12321 dec 12333 Trip/Warn- Trip/Warn- Trip/ Trip/Warn- Trip/Warn- HW fault Custom IO module
ing from ing from Warn- ing from ing from on IO application missing
AuxFault AuxFault fb ing from AuxFault fb AuxFault fb module error
fb input 5 input 4 AuxFault input 2 input 1
fb input 3
Diagnostics Word #2 - - - - Trip trig- Trip trig- Trip trig- Trip / Warn-
gered from gered from gered from ing from
Multifunc. Multifunc. Multifunc. AuxFault fb
input DI2 input DI1 input DI0 input 6

0x300A 0x3016 0x3022 0x302E

dec 12298 dec 12310 dec 12322 dec 12334 - - THD Voltage out Overload Underload - -
Warning of spec1 power power1

Diagnostics Word #3 - - Cooling Just one Num Starts - - -

Time start left Overrun
Running

0x300B 0x3017 0x3023 0x302F

dec 12299 dec 12311 dec 12323 dec 12335 Ext. diagnosis is Parameter - - - - - -
available out of range

Diagnostics Word #4 Fault code.

128 64 32 16 8 4 2 1
MTQ22-FBP - 26 - FieldBusPlug / Issue: 07.2015
32768 16384 8192 4096 2048 1024 512 256
MTQ22-FBP Modbus TCP Interface

Technical Description

Command Data
This address map shows how the complete command data from up to four UMCs can be written in one block.
The data is ordered without any gaps after each other in the followng way.

DO AO DO AO DO AO DO AO
UMC1 UMC1 UMC2 UMC2 UMC3 UMC3 UMC4 UMC4

The next table shows in detail how the data is organized

UMC at UMC at UMC at UMC at Data

port 1 port 2 port 3 port 4
0x4000 0x4006 0x400C 0x4012
dec 16384 dec 16390 dec 16396 dec 16402 - Fault Auto Prepare - Run For- Off Run
Reset Mode Emergency ward / Reverse /
Start Opening Closing

UMC100 UMC100 UMC100 UMC100 - - Run Fast -

DO2 DO1 DO0 24VDC Out Forward

0x4001 0x4007 0x400D 0x4013

dec 16385 dec 16391 dec 16397 dec 16403 VI15x - - - DX1xx DX1xx DX1xx DX1xx
DO0 DO3 DO2 DO1 DO0

- - - - - - - -

0x4002 0x4008 0x400E 0x4014 Analogue Word

dec 16386 dec 16392 dec 16398 dec 16404

0x4003 0x4009 0x400F 0x4015 Analogue Word

dec 16387 dec 16393 dec 16399 dec 16405

0x4004 0x400A 0x4010 0x4016 Analogue Word

dec 16388 dec 16394 dec 16400 dec 16406

0x4005 0x400B 0x4011 0x4017 Analogue Word

dec 16389 dec 16395 dec 16401 dec 16407

FieldBusPlug / Issue: 07.2015 - 27 - MTQ22-FBP

MTQ22-FBP Modbus TCP Interface

Technical Description

Data access in one block ordered by data type

This section explains how to access the data of the connected devices ordered by data type. Only one Modbus TCP read request is
required to read all monitoring data and only one request is necessary to write all command data.

Monitoring Data
This address map shows how the complete monitoring data from up to four UMCs can be read in one block.
The data is ordered without any gaps after each other in the followng way.
DI DI DI3 DI4 AI1 ... AI Diag ... Diag
UMC1 UMC2 UMC3 UMC4 UMC1 UMC4 UMC1 UMC4

The following table shows in detail how the data is organized

UMC at UMC at UMC at UMC at Data

port 1 port 2 port 3 port 4
0x5000 0x5001 0x5002 0x5003
dec 20480 dec 20481 dec 20482 dec 20483 Summary Summa- Local Rev Lockout Overload Run Fwd / Off Run Rev/
Warning ry Fault Control Time warning Opening Closing
UMC100 UMC100 UMC100 UMC100 DI2 UMC100 UMC100 DI0 Run Fast -
DI5 DI4 DI3 DI1 Fwd

0x5004 0x500B 0x5012 0x5019 Motor Current in % of Ie (0% - 800%

dec 20484 dec 20491 dec 20498 dec 20505

0x5005 0x500C 0x5013 0x501A Analogue Word (Thermal Load: 0% - 100%)

dec 20485 dec 20492 dec 20499 dec 20506

0x5006 0x500D 0x5014 0x501B Analogue Word (Time to trip in seconds)

dec 20486 dec 20493 dec 20500 dec 20507

0x5007 0x500E 0x5015 0x501C Analogue Word (Time to restart in seconds)

dec 20487 dec 20494 dec 20501 dec 20508

0x5008 0x500F 0x5016 0x501D Analogue Word (Active power in selected scale)
dec 20488 dec 20495 dec 20502 dec 20509

0x5009 0x5010 0x5017 0x501E

dec 20489 dec 20496 dec 20503 dec 20510 DX1xx DI7 DX1xx DX1xx DX1xx DX1xx DX1xx DX1xx DX1xx
DI6 DI5 DI4 DI3 DI2 DI1 DI0

- - Run Time Out of Position Torque Torque End Pos End Pos
Exceeded1 Open Closed Open Closed

0x500A 0x5011 0x5018 0x501F

dec 20490 dec 20497 dec 20504 dec 20511 U Imbal. U Imbal. Undervoltage Undervol- Underpo- Underpo- Overpo- Overpower
warn trip warn tage trip wer warn wer trip wer warn trip

Earth fault Earth Cooling time - THD No start One start More than
warning fault trip running warning possible left one start left

0x5020 0x5024 0x5028 0x502C

dec 20512 dec 20516 dec 20520 dec 20524 CB miss- PTC wiring PTC hot Pre-warn Locked Phase Phase loss Thermal
ing failure therm. model rotor imbalance OL trip

Actuator UMC self- Earth fault Eart fault trip I > warning I > trip I < warning I < trip
problem test error pre-warning threshold threshold threshold threshold

0x5021 0x5025 0x5029 0x502D

dec 20513 dec 20517 dec 20521 dec 20525 Trip/Warn- Trip/Warn- Trip/Warn- Trip/Warn- Trip/Warn- HW fault Custom IO module
ing from ing from ing from ing from ing from on IO application missing
AuxFault AuxFault AuxFault AuxFault fb AuxFault fb module error
fb input 5 fb input 4 fb input 3 input 2 input 1

- - - - Trip trig- Trip Trip trig- Trip / Warn-

gered from triggered gered from ing from
Multif. input from Mul- Multif. AuxFault fb
DI2 tif.input input DI0 input 6
DI1

0x5022 0x5026 0x502A 0x502E

dec 20514 dec 20518 dec 20522 dec 20526 - - THD Warning Voltage out Overload Underload - -
of spec1 power power1

- - Cooling Time Just one Num Starts - - -

Running start left Overrun

0x5023 0x5027 0x502B 0x502F

dec 20515 dec 20519 dec 20523 dec 20527 Ext. diagnosis is Parameter - - - - - -
available. out of range

Fault code.

MTQ22-FBP - 28 - FieldBusPlug / Issue: 07.2015

MTQ22-FBP Modbus TCP Interface

Technical Description

Command Data
This address map shows how the complete command data from up to four UMCs can be written in one block.
The data is ordered without any gaps after each other.

DO ... DO AO ... AO
UMC1 UMC4 UMC1 UMC4

The following table shows in detail how the data is organized

UMC at UMC at UMC at UMC at Data

port 1 port 2 port 3 port 4
0x6000 0x6002 0x6004 0x6006
dec 24576 dec 24578 dec 24580 dec 24582 - Fault Auto Prepare - Run For- Off Run
Reset Mode Emergency ward / Reverse /
Start Opening Closing

UMC100 UMC100 UMC100 UMC100 - - Run Fast -

DO2 DO1 DO0 24VDC Out Forward

0x6001 0x6003 0x6005 0x6007

dec 24577 dec 24579 dec 24581 dec 24583 VI15x - - - DX1xx DX1xx DX1xx DX1xx
DO0 DO3 DO2 DO1 DO0

- - - - - - - -

0x6008 0x600C 0x6010 0x6014 Analogue Word

dec 24584 dec 24588 dec 24592 dec 24596

0x6009 0x600D 0x6011 0x6015 Analogue Word

dec 24585 dec 24589 dec 24593 dec 24597

0x600A 0x600E 0x6012 0x6016 Analogue Word

dec 24586 dec 24590 dec 24594 dec 24598

0x600B 0x600F 0x6013 0x6017 Analogue Word

dec 24587 dec 24591 dec 24595 dec 24599

FieldBusPlug / Issue: 07.2015 - 29 - MTQ22-FBP

MTQ22-FBP Modbus TCP Interface

Technical Description

Diagnosis / Behaviour in Case of an Error

The MTQ22-FBP provides detailed diagnosis information about the status of the connected devices, its own status
and the status of the Modbus TCP connection.
Diagnosis information is accessible
- with the locally available lamps and
- via the Modbus TCP services.
The possibilities of locally available diagnostics are described in the next section.

LED status indications

Diagnosis information is locally displayed using two Light Emitting Diodes (LEDs) per interface to an FBP device. The
meaning of the LEDs is as follows:

LED Explanation
Port 1,2,3,4 
Off Disabled (no device configured)
Green blinking Startup (waiting for device)
Green on Configured device identified and data exchange X1
running Port 1

Red blinking Communication fault Port 2 X2

Green / Red alternating • Address mismatch between expected device
RDY
address and connected device address.
E. g. caused by swapping two devices.
TCP
• Wrong device type connected.
Port 3 X3
*) Only for intelligent devices like UMC or PST. Not for passive sensors.
Port 4 X4 Data
MTQ22-FBP Status
E1
LED RDY Explanation
General Status Link
Green on Normal Data
Red blinking Minor error, e. g. wrong configuration or
E2
IP address already available in the network.
Red on Major internal fault. If the error is permanent after Link
reboot replace the device.

LED TCP Explanation

Communication Status
Green blinking Waiting for Modbus TCP connection
Green on At least one Modbus TCP connection established
Red blinking One or more (as parameterized) connections timed out
Red on Fatal error
Green / Red alternating Error in the TCP/IP configuration

Ethernet Status
The Ethernet status is shown at the two LEDs integrated in the RJ45 connectors.

Off On Flashing
Data LED Yellow No network traffic - Communication with
network active
(traffic).
Link LED Green No connection to network. E.g. Connection to network esta- -
cable not plugged in or broken blished (e.g. connection with
wire. network switch)

MTQ22-FBP - 30 - FieldBusPlug / Issue: 07.2015

MTQ22-FBP Modbus TCP Interface

Technical Description

Reading the FBP device communication status

The status of the connected FBP devices can be read via Modbus TCP on the addresses 0x80 ... 0x83 for the devices
connected to port 1 ... port 4. See chapter Modbus TCP Address Map for a detailed Modbus TCP address map.
The communication status is zero (0) in case of no error. A value different from zero indicates an error.
The value itself describes the error reason.

Error Code Description Possible Reasons, Corrective Measures

0 OK -
1 Wait For FBP Device. Communication • Check that the FBP device is powered.
not yet established • Check the wiring between the FBP device
and the MTQ22-FBP.
• Check that the drawer is inserted (in a with-
drawable system).
2 Unsupported FBP Device. An unsup- • See section "Overview -> Supported FBP
ported device was connected to the Devices" for a list
MTQ22-FBP
3 Communication Fault on Module Port. • Check the FBP device
Communication to a FBP device was • Check that the FBP device is powered.
established but was lost again • Check that the drawer is inserted (in a with-
drawable system).
4 Address Mismatch. The configured • Fix parameterization
device address and the real FBP de- • Check that the connected FBP device
vice address do not match. was not interchanged (e.g. wrong drawer
inserted). See section Configuration ->
Position supervision
5 - 10 General configuration error • Double-check the configuration
• Check that no unsupoorted device was
connected. See section "Overview -> Sup-
ported FBP Devices" for a list.
• Check configuration data sent to the
MTQ22-FBP (if own config was sent).

other reserved -
values

FieldBusPlug / Issue: 07.2015 - 31 - MTQ22-FBP

MTQ22-FBP Modbus TCP Interface

Technical Description

Technical Data
General

Supply voltage 24 V DC (+30 % ... -20 %)

(19.2 ... 31.2 V DC) including ripple
Current consumption Max. 180 mA (at 19.2 ... 31.2 V DC)
Short-circuit protection at port 1 ... 4 PTC resistor.
Reverse polarity protection of supply inputs Yes
Pollution degree terminals 3
Mounting Snap-on mounting onto 35 mm standard mounting rails
Mounting Position Any
Degree of protection IP20
Temperature range: Storage / Operation -25 ... +70 °C / 0 ... +60 °C
Dimensions (W x H x D) 45 mm x 90 mm x 96 mm
Total power dissipation max. 3,5 W
Net weight 0.172 kg
Configuration Via PC Tool
Diagnosis with LEDs See section Diagnosis
Cable length between MTQ22-FBP and devices It is strongly recommanded to limit the cable length to 3 m
Marks, Approvals CE, cUL
Further in preparation. Ask your Local Sales Unit representa-
tive for other marks/approvals.
Operation altitude above sea level max. 2000 m
For higher altitudes please contact your Local Sales Unit.

EMC

Measurement of radiated and conducted interference

Class A
according to EN61131-2 CISPR16-2-3
Electrostatic discharge 8 kV air discharge
accoring to IEC 61000-6-2 6 kV contact discharge
Radiofrequency electromagnetic field
10 V/m
according to IEC 61000-4-3
Fast transient bursts 2 kV power supply
according to EN61000-4-4 0.5 kV communication lines
High energy surges
1/0.5 kV CM/DM power supply
according to EN61000-4-5
Conducted radio frequency interference
10 V
according to EN61000-4-6
Immunity low frequency harmonics
Power supply: 50 ... 12 kHz, 3 V
according to EN61000-4-11

MTQ22-FBP - 32 - FieldBusPlug / Issue: 07.2015

MTQ22-FBP Modbus TCP Interface

Technical Description

Ethernet and Modbus TCP Performance Data

Network Redundancy Protocol MRP client acc. to EN/IEC 62439-2

Recovery time in a network with 15 MTQ22-FBP
< 200 ms typically (depends on the settings in the MRP
nodes in ring topology and interruption of the commu-
master)
nication at one place (single fault)
Response time of a ModbusTCP request
< 1 ms (typically)
to IO data
Response time of a ModbusTCP request
to parameter data and maintenance counters < 3 ms (typically)

Max. concurrent Modbus TCP connections 4

Ethernet interfaces 2 (internal two-port switch)
Supported Ethernet topologies Star, ring, bus (daisy chain)
Supported Bitrate 10MBit/s, 100MBit/s
LLDP Naming of Ethernet ports E1: Port_002
E2: Port_001

Ordering Data

Type Description Order No.

MTQ22-FBP.0 Modbus TCP Interface for 4 FBP-Devices 1SAJ260000R0100
CDP11-FBP.0 Drawer passive cable, fixing bracket 50 pcs 1SAJ929100R0001
CDP11-FBP.4 Drawer passive cable, fixing bracket 4pcs 1SAJ929100R0004
CDP17-FBP.150 Cable ETH-X1/X4-M12 female 1SAJ929170R0015
CDP18-FBP.150 Cable ETH-X1/X4-open wire 1SAJ929180R0015
CDP19-FBP.100 Passive cable drawer inside 1SAJ929190R0010
ETHTB-FBP.4 Terminalset X1…X4 for EthernetFBP 4 pcs 1SAJ929200R0001
ETHTB-FBP.50 Terminalset X1…X4 for EthernetFBP 50 pcs 1SAJ929200R0002
CPD23.150 Cable ethernet interface - UMC100.3, length 1.5 m 1SAJ929230R0015
CPD23.300 Cable ethernet interface – UMC100.3, length 3 m 1SAJ929230R0030

FieldBusPlug / Issue: 07.2015 - 33 - MTQ22-FBP

MTQ22-FBP Modbus TCP Interface

Technical Description

Dimensions

45 1.77" 96 3.8"

 MTQ22

X1
Port 1

Port 2 X2
RDY

TCP
90 3.54"

Port 3 X3

Port 4 X4

X5

Data

E1

Link
Data

E2
X6
Link

2CDC3422004F0012
24V
0V
DC

mm / inch

Figure 13: Dimensions MTQ22-FBP.0

CDP17
6 M12 A-coded
female 5 pol.
1
1.5 m 59.1“

CDP18
6

CDP19
M12 A-coded
female 5 pol.

1.0 m 39.4“

6 1

CDP23 1 6
1.5 m / 3.0 m 59.1“ / 118.1“

Pin
6 nc
5 0V blue
4 VCC brown
3 Rx black
2 Tx green/yellow
1 Diag white

Figure 14: Dimensions auxiliary cables

MTQ22-FBP - 34 - FieldBusPlug / Issue: 07.2015

MTQ22-FBP Modbus TCP Interface

Technical Description Document-No.: 2CDC194003D0202

FAX No.: +49 (0) 6221-701-1382

Detected an Error?
Your feedback helps us to constantly improve our products. We are grateful for your comments and
suggestions. Please provide us with the following information if you have noticed an issue:

Name

Company / Department

Telephone / Email

Problem Description
• Steps to reproduce the problem
• Version of UMC (Ident number on nameplate and firmware version which is displayed on the UMC100-PAN)
• Version of MTQ (Ident number on nameplate)
• Version of config tool / Windows version (Control->System)

FieldBusPlug / Issue: 07.2015 - 35 - MTQ22-FBP

MTQ22-FBP Modbus TCP Interface

Technical Description

MEMO

MTQ22-FBP - 36 - FieldBusPlug / Issue: 07.2015

Contact

ABB STOTZ-KONTAKT GmbH

2CDC 194 003 D0202 Rev B  07.2015

Note:
P. O. Box 10 16 80
We reserve the right to make technical changes or
69006 Heidelberg, Germany
modify the contents of this document without prior
notice. With regard to purchase orders, the agreed
Phone: +49 (0) 6221 7 01-0
particulars shall prevail. ABB AG does not accept
Fax: +49 (0) 6221 7 01-240
any responsibility whatsoever for potential errors or
E-Mail: [email protected]
possible lack of information in this document.
Internet http://www.abb.de/stotzkontakt
We reserve all rights in this document and in the
subject matter and illustrations contained therein.
Any reproduction, disclosure to third parties or
utilization of its contents – in whole or in parts – is
forbidden without prior written consent of ABB AG.

Copyright© 2015 ABB

All rights reserved