PDP32.0 Profibus DP Communication Module: Universal Motor Controller UMC100.3
PDP32.0 Profibus DP Communication Module: Universal Motor Controller UMC100.3
M A N UA L
PDP32.0 Profibus DP
communication module
Universal Motor Controller UMC100.3
2 UNIVERSAL MOTOR CONTROLLER UMC100. 3
—
Important notice
Target group
This description is intended for the use of specialists in electrical installation and control and automation engineering 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.
—
Symbols
This technical document contains symbols to point the reader to important information, potential risks and precautionary
information. The following symbols are used:
—
Terms and abbreviations
SMK3.0 Single Mounting Kit for the fieldbus interfaces and the active termination unit PDR31
UMC100.3 Universal Motor Controller
UTP22-FBP.0 USB to PROFIBUS interface
PDR31.0 Active termination unit for PROFIBUS networks
—
Related documents
Technical documentation Document no.
Version information
This document is valid for:
Profibus DP communication module PDP32.0 Order code 1SAJ242000R0001
3
—
Table of contents
4 Overview
5 Installation
12 Diagnosis
14 Technical data
17 Ordering data
PDP32.0 MANUAL 4
—
Overview
PROFIBUS is an open serial communication standard that enables data exchange between all kinds of automation compo-
nents. The PDP32.0 communication interface is a PROFIBUS DP (Decentralized Periphery) slave on the PROFIBUS network.
PROFIBUS DP is standardized in IEC 61158 together with other fieldbus protocols.
The physical transmission medium of the bus is a twisted pair cable (according to the RS-485 standard). The maximum
length of the bus cable is 100 to 1200 meters, depending on the selected transmission rate. Up to 32 nodes can be connected
to the same PROFIBUS network segment without the use of repeaters. With repeaters, it is possible to connect 126 nodes
(including repeaters and a master station) to the network. In PROFIBUS communication, the master station – usually a
programmable logic controller (PLC) or a distributed control system (DCS) – polls nodes, which respond and take the actions
requested by the master. The PROFIBUS protocol family is specified in the IEC 61158 standard. For further information on
PROFIBUS, refer to the above-mentioned standard.
The PDP32.0 PROFIBUS DP communication module is an optional device for the ABB motor controllers UMC100.3 which
enables the connection of the UMC100.3 to a PROFIBUS network. The UMC100.3 with PDP32.0 is considered a slave on the
PROFIBUS network.
X3: D-SUB
PROFIBUS
X4: Two wire
Interface
PROFIBUS
Status connector
Indication
LEDs
X3: D-SUB
PROFIBUS
connector
—
Installation
Mechanical installation
The PROFIBUS interface module PDP32.0 can be mounted either on the UMC100.3 itself or separately from the UMC100.3
using the single mounting kit (SMK3.0).
Power
—
01 Image shows UMC100.3 DC
PDP32.0 MANUAL 6
For remote mounting of the PDP32.0, the Single Mounting Kit (SMK3.0) must be used.
When remote mounted, the PDP32.0 must be separately supplied to keep the PDP32 online, even in the case when the drawer
is removed. Ready made cables to connect the SMK3.0 with the drawer are available, but it is also possible to use own cables.
For more details, see the section „Using PDP32.0 in a drawout system“.
The single mounting kit (SMK3.0) can be either mounted on a DIN rail hat or fixed with screws on a fitting panel.
Assembly Disassembly
(2)
(1) 2CDC343004F0018
2CDC343005F0018
(2) (1)
Snap-in
Move down
Snapped
Snap-in
Step 4:
Fix cable with cable ties
—
03 Mounting the PDP32.0/PDR31.0 on the Single Mounting Kit
7 UNIVERSAL MOTOR CONTROLLER UMC100. 3
Unmounting PDP32.0/PDR31.0
Follow the procedure for demounting the PDP32.0/PDR31.0 from UMC100.3 or SMK3.0
2CDC343006F0018
—
04 Unmounting PDP32.0 and PDR31.0
Electrical Installation
PROFIBUS Connection
PROFIBUS can be connected on both X3 and X4.
X3 allows to connect a standard D-SUB connector.
X4 can be used to connect standard 2-wire PROFIBUS cable directly.
General
General cabling instructions
• Arrange the bus cables as far away from the motor cables as possible
• Avoid parallel runs
• Use bushings at cable entries
• Further instructions can be found in the PROFIBUS installation instructions provided by the PROFIBUS User Organization
(PNO)
X3 Description
1 Not used
2 Not used
3 B Data positive (Conductor 1 in twisted pair)
4 Not used
5 GND Isolated ground
6 +5V Isolated 5 V DC voltage supply (30 mA max.)
7 Not used
8 A Data negative (Conductor 2 in twisted pair)
9 Not used
+5 V and GND can be used for bus termination only.
If no D-SUB connector is used, the PROFIBUS cable can be connected to the connector X4 of PROFIBUS module.
X4 Description
1 SHLD Alternate cable shield connection. Connected to connector housing
2 B Data positive (Conductor 1 in twisted pair)
3 A Data negative (Conductor 2 in twisted pair)
Follow the PNO installation and planning guidelines for PROFIBUS DP networks.
Only use PROFIBUS bus cable “Type A" as recommended by PNO.
PDP32.0 MANUAL 8
Bus termination
Bus termination is required to prevent signal reflections from the bus cable ends. The PROFIBUS communication interface
PDP32.0 is not equipped with internal bus termination. Therefore, the PROFBUS D-SUB connectors at the first and last
PDP32.0 in a bus segment must have termination switched on.
In setups where the PDP32.0 is located in a drawer it is necessary to use an active bus termination at the end of the
PROFIBUS line. Use PDR31.0 in that case.
For the whole network, i.e. starting at the DP Master up to the last DP Slave:
• approx. 4 up to 8 DP segments by Repeater (see data sheets of the Repeater)
• the slowest DP subscriber sets the transfer rate of the DP line
• number of PROFIBUS DP subscribers ≤ 126 (Addresses 0 …125)
For a segment:
• number of DP subscriber ≤ 32 (subscriber = device with / without PROFIBUS address)
• bus termination each at the beginning and the end of every DP segment necessary!
• trunk cable length (LT) see diagram (length depending on transfer rate)
5k /s
s
t/
s
,7 Bit
s
LT/m
t/
t/
Bi
Bi
5k
Bi
2k
6k
.4
.
93
45
/s
19
9.
it
1200
kB
5
7,
18
1000
t/s
Bi
0k
50
400
s
t/
Bi
5M
s
1,
t/
12 t/s
6M s
200
t/
Bi
Bi
Bi
M
3M
100
Transmission Speed
The maximum transmission distance that can be achieved using copper cables is
directly related to the transmission speed chosen for the PROFIBUS network. As
a result, these two variables must always be considered together.
9 UNIVERSAL MOTOR CONTROLLER UMC100. 3
PROFIBUS
Master Service laptop
LT
UMC100.3 with PROFIBUS
communication interface
PDP32 mounted in drawer
Repeater
LT
PROFIBUS
Master
Service Laptop
LT
UMC100.3 with PROFIBUS communi-
cation interface PDP32 mounted in
non-withdrawable setup
Repeater
LT
Repeater
Termination active
11 UNIVERSAL MOTOR CONTROLLER UMC100. 3
• PROFIBUS address is stored in the PROFIBUS communication interface in addition to the UMC100.3.
In case of a drawer replacement the new — not addressed — UMC100.3 takes over the bus address automatically.
Fast reparameterisation without manual interaction possible.
• Swapping of drawers detected if "Address Check" in UMC100.3 enabled. In other words, it is not possible to accidentally
start the wrong motor because of a swapped drawer.
The required grounding of the PROFIBUS cable is not shown in this figure.
PROFIBUS
Service laptop
Master
Configuration adapter
UTP22
(2a) (2b)
(1)
(1) 24V DC supply for the commu-
(3) nication interface. This lets
LT 5 5 the PDP32 stay active even in
case the drawer is withdrawn.
(2a) Ready made connection cable
(4) from SMK3.0 X1 to the backside
of the drawer
max. 3m (2b) Ready made connection cable
from inside drawer to UMC100.3
(3) UMC100.3 mounted inside a
drawer
(4) PROFIBUS communication inter
Repeater face with mounting kit
LT
—
Diagnosis
PROFIBUS Diagnosis
• Standard Diagnosis: The format of the standard diagnosis data is defined within the PROFIBUS standards (IEC 61158). It
consists of 6 octets that cannot be influenced by the field device manufacturer. The diagnosis information is related to the
communication layer and covers run-up diagnosis scenarios such as the device identification, communication mode infor-
mation (FREEZE, SYNC), readiness, availabilities, watchdogs, parameterization and configuration faults.
For details, see IEC 61158-6, 6.2.3.1 to 6.2.3.5. Bit 7 in octet 3 (the “Ext_Diag_Overfl ow” flag) is used by the PROFIBUS com-
munication interface to indicate more diagnosis information then fits into the actual diagnosis message length.
• Extended Diagnosis: PROFIBUS module offers extended diagnosis to make the diagnosis data of the connected devices
available to the PROFIBUS master. Depending on the selected diagnosis format DP-V1 or DP-V0, the content of the diagno-
sis is slightly different. The extended diagnosis telegram has the following format:
Byte in the extended
Meaning DP-V0 Meaning DP-V1
diagnosis telegram
0 Block length: 10 = 10 Bytes Block length: 13 = 13 Bytes
1 Communication status communication Status type (always 0x81 = Status Mode)
interface - UMC:
Value(0) ="Communication OK"
Value(1) ="Lost Communication to UMC100"
2 Diagnosis Byte 0 UMC (see UMC manual) Slot number (always zero)
3 Diagnosis Byte 1 UMC (see UMC manual) Status specifi er (always zero)
4 Diagnosis Byte 2 UMC (see UMC manual) Communication status communication interface - UMC:
Value(0) ="Communication OK"
Value(1) ="Lost Communication to UMC100"
5 Diagnosis Byte 3 UMC (see UMC manual) Diagnosis Byte 0 UMC (see UMC manual)
6 Diagnosis Byte 4 UMC (see UMC manual) Diagnosis Byte 1 UMC (see UMC manual)
7 Diagnosis Byte 5 UMC (see UMC manual) Diagnosis Byte 2 UMC (see UMC manual)
8 Diagnosis Byte 6 UMC (see UMC manual) Diagnosis Byte 3 UMC (see UMC manual)
9 Diagnosis Byte 7 UMC (see UMC manual) Diagnosis Byte 4 UMC (see UMC manual)
10 - Diagnosis Byte 5 UMC (see UMC manual)
11 - Diagnosis Byte 6 UMC (see UMC manual)
12 - Diagnosis Byte 7 UMC (see UMC manual)
13 UNIVERSAL MOTOR CONTROLLER UMC100. 3
—
For the PROFIBUS expert
The following section provides PROFIBUS know-how useful to better understand the PROFIBUS functions.
Cold start: The CheckCfg telegram sent from the PROFIBUS master defines the reference configuration. It is accepted if it is
error free. Otherwise, a negative reply with the appropriate diagnosis information is sent to the master. The PROFBUS
module arrives in the cyclical data exchange mode only if the reference configuration sent from the master corresponds with
the configuration sent from the connected device (i.e. UMC100).
Next, the PROFIBUS module waits for a parameter telegram from the bus master. Starting the cyclic PROFIBUS communi-
cation is only possible if a correct parameter telegram was received. The parameter telegram is sent to the connected
devices if parameter "Ignore block parameters“ is not set to "Ignore“.
Online reconfiguration: PROFIBUS module does not support ‘Hot Configuration In Run’ as supported by some ABB control
systems. Whenever a configuration change is done, the module must be restarted to ensure that the configuration gets
accepted.
Reaction on wrong configuration telegrams: The wrong configuration or parameter telegrams can occur if the used GSD file
does not belong to a device or the device version. In this case, the PROFIBUS module does not accept the configuration
telegram and leaves cyclic operation mode or does not start the PROFIBUS communication.
Online re-parameterization of devices: Because parameter changes do not affect the structure of the I/O data re-compi-
lation of the user application in the master is usually not necessary. In some control systems, a restart of the master must be
performed that makes online re-parameterization impossible. Other masters are not subject of this limitation and support
online parameterization. UMC100 is able to receive parameter telegrams every time without leaving the cyclic operation
mode.
• The PROFIBUS specification allows the online re-parameterization only if the device is not operated in V1 mode.
This means that no acyclic communication is allowed from the cyclic bus master (class one master). However, systems us-
ing a so-called class 2 master for sending V1 requests and supporting sending a new parameter telegram whilst online are
capable to do online re-parameterization. If a specific control system is able to carry out online re-parameterization should
be found in the documentation of this system.
• Sending new parameters during cyclic operation can be critical. If parameters are out of range or cannot be accepted from
the device for a specific reason a device might leave the cyclical operation mode and enter an error of fail-save mode.
Please consult the manual of the connected devices for more information.
Reaction on Wrong Parameter Telegrams: The PROFIBUS module does not check the parameters itself. This can only be
done from the connected devices. If a faulty parameter telegram was received (e. g. wrong length), the PDP32 leaves the
cyclical operation mode and waits for a new parameter telegram.
V1 Requests from a Class1 Master: Different master classes are distinguished in a PROFIBUS DP-V1 network. The so-called
C1 master mainly performs the cyclical data exchange with the slaves. A typical C1 master is a control system, such as a PLC
or DCS that exchanges cyclical process data with the slave. If the DPV1 function has been activated via the GSD file, also
acyclical connections between a C1master and a slave can also be established when the cyclical connection o is being estab-
lished. If a class 1 master uses V1 services, it is physically and logically the same bus node doing V0 and V1 communication.
Before acyclic messages can be used for the C1 master a device must have entered the cyclic operation mode. This means
that the PDP32 must be first configured and parameterized before acyclic requests from a class 1 master are possible. PDP32
supports V1 requests from a class 1 master. Please see “Online re-parameterization” for further details.
V1 Requests from a Class2 Master: A C2 master cannot perform cyclical data exchange with the slaves. It is logically a
different bus node than a C1 master. Examples for a typical C2 master are visualization systems, temporary installed
programming devices (Notebook / PC) or maintenance management tools. The C2 master uses exclusively acyclic connec-
tions for the communication with the slaves. V1 connections allow for cyclical data exchange with the slaves by means of
Read or Write services. Several C2 masters can be active in a DP-V1 network. The number of C2 connections, which are estab-
lished to a slave simultaneously, are determined by the slave. PDP32 supports up to 3 concurrent class 2 connections.
PDP32.0 MANUAL 14
—
Technical data
Data at Ta = 25 °C and rated values, unless otherwise indicated
Standards / directives
Product standard IEC 61158
RoHS Directive 2011/65/EU
Environmental data
Ambient air temperature Operation 0 ... +60 °C
Storage -25 ... +70 °C
Vibration (sinusoidal) acc. to IEC/EN 60068-2-6 (Fc) 4 g / 10 .... 150 Hz (mounted on UMC100.3 / SMK3.0)
Shock (half-sine) acc. to IEC/EN 60068-2-27 (Ea) 15 g / 11 ms
General Data
Dimensions
SMK3.0
89 3.504"
Connection Cables
5 Blue VDD
4 Brown VCC
3 Black Communication
2 Grey Communication
X2 X1 1 White Diagnosis
1 2 5 4 3 2 1
Pin Function
2 24 V DC
1 0 V DC
Drawer
1
2
3
4 CDP24
5 to UMC100.3
X1
Colors must match CDP18
1
2
3
4
5
6
X3
X2
5V 24 V DC
6 2
0V 0V
5 1
A
8 1
RS485 uC +
B <-> UMC
Driver ASIC 5
3
SHLD X1
1
3
X4 PDP32
X3 X2
5V 24 V DC
6 2
R390 0V 0V
5 1
R390
A
8
B
3
R220
SHLD
1
3
X4 PDR31
17 UNIVERSAL MOTOR CONTROLLER UMC100. 3
—
Ordering data
1SAJ929240R0015 CDP24.150 Cable between single mounting kit and drawer / 1.5m
abb.com/lowvoltage
Document number 2CDC192016D0202 Rev. B (05/2019)
Additional information
We reserve the right to make technical We reserve all rights in this document and
changes or modify the contents of this in the subject matter and illustrations
document without prior notice. With contained therein. Any reproduction,
regard to purchase orders, the agreed disclosure to third parties or utilization of
particulars shall prevail. ABB AG does not its contents – in whole or in parts – is
accept any responsibility whatsoever for forbidden without prior written consent of
potential errors or possible lack of infor- ABB AG. Copyright© 2019 ABB
mation in this document. All rights reserved