800xa - device management profibus - abb ltd · 800xa - device management profibus device type abb...

Industrial IT Extended Automation System 800xA

2PAA104102M02 1

800xA - Device ManagementPROFIBUS

Device Type ABB PDP22-FBPVersion 5.1

Release Notes

Introduction

This document represents the release notes for the device type ABB PDP22-FBP .

This document provides a brief overview on functionality. It also enumerates known problems encountered in the final interoperability testing with the related device hardware. and identifies workarounds that help overcome the problem. The document contains additional notes that may be valuable to customers and service personnel working with this device type.

Release Notes Device Type ABB PDP22-FBP

2 2PAA104102M02

Device Type Details

Table 1. Device Type Details

Vendor ABB

Device Type PDP22-FBP

Category Gateway

Protocol PROFIBUS DP

PNO ID 0x082D

GSD File Version / Date 1.92 / 2006-07-05

Hardware/Software Revision V1.0 / V1.0(1)

(1) For the interoperability test with the physical device the listed hardware and software revision has been used. The user has to verify that the connected device meets above version requirements or is compatible with above versions.

Please make sure that the PDP22 model available supports DPV1 diagnostics. This can be verified by it’s order number 1SAJ240100R1xxx.

PDP22 model with order number 1SAJ240100R0xxx can not be used with this Object Type.

Device Type ABB PDP22-FBP Release Notes

2PAA104102M02 3

New in this Version

Table 2. Revision History

Library Wizard Name Changes

ABB PDP22-FBP V3.3-DP First Release.

Available with 2PAA100378_A_en_DeviceObjectType_ABB_PDP22_FBP_V3_3_DP.zip

ABB PDP22-FBP V4.0-DP • Support for UMC22 firmware version 3.3 and 3.4 with DTM and Asset Monitor.

• Support for DPV1 diagnostic format.

• Extra Diagnostics support for MFI21 Device.

Available with 2PAA101563_A_en_DeviceObjectType_ABB_PDP22_FBP_V4_0_DP.exe

ABB PDP22-FBP V4.1-DP • Support for PR122_123_332_333 device with Specific Asset Monitor.

• Support for SV5.0 and Higher included.

Available with 2PAA101563_B_en_DeviceObjectType_ABB_PDP22_FBP_V4_1_DP.exe

ABB PDP22-FBP V4.2-DP • Support for PR222 DS/PD device with Specific Asset Monitor.

Available with

2PAA101563S01_x_en_DeviceObjectType_ABB_PDP22_FBP_V4_2_DP.exe

ABB PDP22-FBP V4.3-DP Release with UMC22 FW 3.4 Asset Monitor bug fix.

Available with



4 2PAA104102M02

If installed in SV5.0 SP1 or higher it will result in Hardware Library ABB_FBP_Products_DP Version 5.1-0.

The Gateway and all related device types are covered by this Hardware Library and user need not install module device type seperately.

Supported System

ABB PDP22-FBP V5.0-DP • Support for UMC22 firmware version 4.0.

• DTMs for PR222 DS/PD and PR122_123_332_333.

Available with


ABB PDP22-FBP V5.1-DP • Change in the diagnostics bit for PR123.

Available with


Table 3. System 800xA (SV5.0 onwards)

System Requirements 800xA SV5.0 SP1 or higher system versions(1)

(1) Check ABB SolutionsBank for Field Notification, to find out if this device type has any further limitations.

Hardware Library ABB_FBP_Products_DP Version 5.1-0

Supported Controller / PROFIBUS Master

Controller AC 800M / CI 854(A)

Supported Linking Devices Not Applicable

Table 2. Revision History

Library Wizard Name Changes


2PAA104102M02 5

Restrictions

PROFIBUS device types are created by ABB and tested for use in the 800xA system in connection with Device Management PROFIBUS & HART. ABB creates these device types based on data provided by individual device vendors (e.g. EDDs, GSDs, device-specific Device Type Managers (DTMs) and Asset Monitor behavior specifications), which ABB relies on as accurately reflecting the actual device specification and behavior. Therefore, ABB cannot assume liability for events that are caused by devices that are not functioning according to fieldbus standards, or device specifications, or for events that are caused by mismatches between the device behavior and the input data provided by the device vendor.

Device types installed via Device Library Wizard cannot be used or instantiated if the associated DTM is not installed.

Device-specific DTMs need to be installed on every 800xA system node on which the Device Management PROFIBUS & HART is executed. The DTM-specific licensing arrangements need to be taken into account.

DTMs installed on an 800xA system node must not be removed manually by the user unless explicitly described.

Operating Instructions

PDP-FBP:

Do not change parameter “Diagnostic Format”from it’s default value “DPV1 Diagnostic Format” in Control Builder settings tab.

UMC (Firmware Version 3.2):

Parameters “Set Current 1” and “Set Current 2” in the control builder requires special handling. The current settings are distributed as High Word and Low Word because of the limitation of control builder not able to handle more than 2 bytes as configuration parameter.

For the current settings in the range of 0.24 A to 655.35 A, High Word is 0 and Low Word will be 24 to 65535.

For the current settings above 655.35 A, High Word and Low Word will be set as per the examples shown below:


6 2PAA104102M02

Example 1:Current setting required in UMC is 1000 A, Then High Word is set to 1 and Low Word is set to 34464.


For maximum current setting of 3200 A High Word is set to 4 and Low Word is set to 57856.












2PAA104102M02 7





MFI21:

Parameter “Star Delta Time” in the control builder requires special handling. The time setting is distributed as High Word and Low Word because of the limitation of control builder not able to handle more than 2 bytes as configuration parameter.

For the time setting in the range of 50 mS to 65535 mS, High Word is 0 and Low Word will be 50 to 65535.

For the current settings above 65535 mS, High Word and Low Word will be set as per the examples shown below:

Example 1:Time setting required in MFI is 100 S, Then High Word is set to 1 and Low Word is set to 34464.

Example 2:Time setting required in MFI is 150 S, Then High Word is set to 2 and Low Word is set to 18928.

PR122/PR123/PR332/PR333:

Active Power and Reactive Power channel values require special handling.

Device sends these values in the form of signed double word . But GSD import tool is not able to handle such data format hence these values are divided in two words: Low word and High word.

User has to get these 2 words in application program and combine them to make signed double word.

For Example if Channels shows following values :


8 2PAA104102M02

Example (1)

Total Active Power - Low Word = 64626

Total Active Power - High Word = 65535

Then the Total power is calculated as : Decimal (65535)(64626) = Hex (FFFF)(FC72)

Since the MSB is 1, it is a negative value. User has to take 2’s compliment to find correct value.

2’s compliment of (FFFFFC72) = -(0000038E) =( -910) decimal.

So the combined channel value will be read as -910.

Example (2)

Total Active Power - Low Word = 525

Total Active Power - High Word = 0

Here since MSB is 0, it is a positive value and final channel value will be 525.

Installation

Installation of this device type also installs a DTM. To install a DTM, please follow the on-screen instructions of that installer. For some DTMs, manual selection of the device type is required. For more details, refer to Device Type Manager (DTM) on page 35 in this document.

This object type can be installed with the Device Library Wizard tool only. For more details, please refer to ABB Device Library Wizard, User Instructions (3BDD011857R0101) in SV4.1 and ABB Device Library Wizard, User Instructions (2PAA102573R5011) in SV5.0 SP1.


2PAA104102M02 9

Device Type, Modules and ChannelsSince System 800xA version 5.0 onwards the implementation and usage of PROFIBUS device types is different to previous 800xA system versions. Main difference between pre SV5.0 and SV5.0 is not to have object types for device types and corresponding modules, but to have a hardware library.

For detailed information, please refer to the specific system documentation for configuration and operation of PROFIBUS device types.

Table 4 lists the device type and corresponding module types.

Since SV5.0 onwards all released Device Type and Module Types are included in the Hardware Library of the Device Type. Therefore a separate installation of Module Types is not required as it was described and mandatory for pre-SV5.0 800xA systems.

In pre-SV5.0 system version these installation steps are still valid for those Device Types delivered as single Device and Module Type files.

Please read the Release Notes for the used Module Type, whether it is used in pre-SV5 or SV5.0 onwards.

Table 4. Module/Device Types according to GSD

Object Type Description

SV5.0 onwards:

ABB_PDP22_FBP_DP_V5_0

Device Type (Slave), must be configured first with associated PROFIBUS address.

SV5.0 onwards:

UMC22_Fw3_20_v1

Module contains the following 6 bytes data structure with 4 bytes input and 2 bytes output.

Inputs:

UMC_Input : 2 Bytes --> DINT

UMC_MotorCurrent : 2 Bytes --> DINT

Output:

UMC_Output : 2 Bytes --> DINT


10 2PAA104102M02

SV5.0 onwards:

UMC22_Fw3_30_v1


Inputs:



Output:


SV5.0 onwards:

UMC22_Fw3_40_v1


Inputs:



Output:


SV5.0 onwards:

UMC22_Fw4_00_v1


Inputs:



Output:


SV5.0 onwards:

MSD11_v3_0

Module contains the following 2 bytes data structure with 1 byte input and 1 byte output.

Input:

Input : 1 Bytes --> DINT

Output:

Output : 1 Bytes --> DINT




2PAA104102M02 11

SV5.0 onwards:

MFI21_v3_0


In Area:

1 Byte -> 8 Bool - DI 0 to DI 2, and Motor Protecting Switch

Out Area:

1 Byte -> 8 Bool - DO 0 to DO 2

SV5.0 onwards:

MSR22_v2_0


Input:

1 Bytes -->8 Bool - Input_TRIP_CONTACT ON, Input_RUN1_FORWARD, and Input_RUN2_FORWARD

Output:

1 Bytes -->8 Bool - Output_RUN1_FORWARD and Output_RUN2_FORWARD.




12 2PAA104102M02

SV5.0 onwards:

PR122_123_332_333_v2_0


Inputs:

1 Byte -> DInt - Digital Input Byte 0















2 Byte -> DInt Unsigned - Maximum Current

2 Byte -> DInt Unsigned - L1 Run Time Current



2 Byte -> DInt Unsigned - Neutral Run Time Current

2 Byte -> DInt Unsigned - Internal Rog Ground Run Time Current

2 Byte -> DInt Unsigned - V12 Line to Line Voltage





2PAA104102M02 13


2 Byte -> DInt Unsigned - Total Active Power - Low Word

2 Byte -> DInt Unsigned - Total Active Power - High Word

2 Byte -> DInt Unsigned - Total Reactive Power - Low Word

2 Byte -> DInt Unsigned - Total Reactive Power - High Word

2 Byte -> DInt Unsigned - CB Number of Operations

2 Byte -> DInt Unsigned - CB Number of Protection Trips

Outputs:

1 Byte -> DInt - Command Info - Value High Byte

1 Byte -> DInt - Command Info - Command Info - Value Low Byte

1 Byte -> DInt - Command Info - Command Info - Parameter High Byte

1 Byte -> DInt - Command Info - Command Info - Parameter Low Byte




14 2PAA104102M02

SV5.0 onwards:

PR222_DS_PD_v2_0

Submodule contains the following 46 bytes data structure with 42 bytes input and 4 bytes output.

Inputs:











2 Byte -> Dint - L1 Run Time Current



2 Byte -> Dint - Neutral Run Time Current

2 Byte -> Dint - Ground Run Time Current

2 Byte -> Dint - L1 Trip Current



2 Byte -> Dint - Neutral Trip Current




2PAA104102M02 15

2 Byte -> Dint - Ground Trip Current

2 Byte -> Dint - CB Number of Operations

2 Byte -> Dint - CB Number of Protection Trips

2 Byte -> Dint - L number of trips

2 Byte -> Dint - S number of trips

2 Byte -> Dint - I number of trips

2 Byte -> Dint - G number of trips

Outputs:

1 Byte -> Dint - Command Info - Value High Byte

1 Byte -> Dint - Command Info - Value Low Byte

1 Byte -> Dint - Command Info - Parameter High Byte

1 Byte -> Dint - Command Info - Parameter Low Byte




16 2PAA104102M02

Device Object Type Functionality in 800xA

Documentation

Please select the following aspects in Product Documentation aspect to view documentation related to this device type.

PDP-FBP:

• Application Manual.

• UL Certificate.

• Environmental Information.

• EU directive on hazardous substances.

• Technical Description.

• Type Approval Certificate.



• Data Sheet.



• Data Sheet.



• Data Sheet.

MSD11:


For details on PROFIBUS device configuration, refer to IndustrialIT 800xA - Device Management, PROFIBUS, Configuration Device (3BDD011750R4101) in SV4.1 and Device Management, PROFIBUS & HART, Configuration (3BDD011934R5011) in SV5.0 SP1.


2PAA104102M02 17

MFI21:

• Declaration of Conformity.

• Certificate of Compliance.

• Environmental Information.

• Installation Manual.

• Technical Reference Manual.

MSR22:


PR122/PR123/PR332/PR333:

• Installation and Service Instructions

• Installation Manual of EP010

• Instruction Manual

• Operating Instructions

• SACE PR010 Test Unit Annex

• User and Operator Manual of EP010.

PR222 DS/PD:

• Declaration of Conformity.

• Installation Manual of EP010.

• Instruction Manual.

• SACE PR010 Test Unit Annex.

• User and Operator Manual.

Device Diagnostics in Control Builder M

Each unit of an device object type has a variable of type Hardware Status (HwStatus). The HwStatus type is displayed as 32 bit integer value for


18 2PAA104102M02

ErrorsAndWarnings (EW) and ExtendedStatus (ES). Table 5 shows the supported diagnostics information provided by the device.

Table 5. Device Diagnostics

Status BitHW-

StatusValue

Diagnostics Information

Warning/Error

Alarm/Event

Severity

PDP-FBP

Standard Diagnostics (Available at slave level)

ExtendedStatus1 ExtendedStatus

16#00000001 Slave does not exist

Error Alarm Medium


16#00000002 Configuration data fault

Error Alarm High


16#00000004 Parameter data fault

Error Alarm High


16#00000008 Static diagnostic

Warning Event Low


16#00000010 Redundant slave does not exist

Warning Event Medium


16#00000020 Diagnostic configuration data fault



16#00000040 Report Diagnostics fault


Manufacturer Specific Diagnostics (Available at slave level)


2PAA104102M02 19

DeviceSpecific1 ErrorsAndWarnings

16#80000000 PDP22 Diagnose Byte Bit 0

Error Alarm High

UMC22(Firmware version 3.2)



16#00000001 Fault Input Signal - Byte 0 Bit 5

Warning Alarm High


16#00000002 Self Test Failed - Byte 0 Bit 6

Warning Alarm High


16#00000004 Relay 0 Check-back Fault - Byte 1 Bit 0

Warning Alarm High



Warning Alarm High



Warning Alarm High


16#00000020 Current Check-back Fault - Byte 1 Bit 3

Warning Alarm High


Status BitHW-

StatusValue


Warning/Error

Alarm/Event

Severity


20 2PAA104102M02


16#00000040 Parameter out of range - Byte 1 Bit 4

Warning Alarm High


16#00000080 Communication Fault - Byte 1 Bit 5

Warning Alarm High


16#00000100 Motor Blocked - Byte 1 Bit 6

Warning Alarm High


16#00000200 Overload (trip) Fault - Byte 1 Bit 7

Warning Alarm High


16#00000400 Reversing Lockout Time Running - Byte 2 Bit 3

Warning Event High


16#00000800 Cooling Time Running - Byte 2 Bit 4

Warning Event High


16#00001000 Motor Current Low Threshold - Byte 2 Bit 6

Warning Event High


16#00002000 Motor Current High Threshold - Byte 2 Bit 7

Warning Event High


16#00800000 Self test Running - Byte 2 Bit 2

Warning Event High


16#00400000 Parameter Unknown - Byte 2 Bit 5

Warning Event High


Status BitHW-

StatusValue


Warning/Error

Alarm/Event

Severity


2PAA104102M02 21





Warning Alarm High



Warning Alarm High


16#00000004 Relay 0 Check-back Fault / Clos TS->0 but not closed LS(intermed.) - Byte 1 Bit 0

Warning Alarm High


16#00000008 Relay 1 Check-back Fault / Closed LS appears without close cmd. - Byte 1 Bit 1

Warning Alarm High


Status BitHW-

StatusValue


Warning/Error

Alarm/Event

Severity


22 2PAA104102M02


16#00000010 Relay 2 Check-back Fault / Open LS appears without Open cmd. - Byte 1 Bit 2

Warning Alarm High



Warning Alarm High



Warning Alarm High



Warning Alarm High



Warning Alarm High



Warning Alarm High



Warning Event High



Warning Event High


Status BitHW-

StatusValue


Warning/Error

Alarm/Event

Severity


2PAA104102M02 23



Warning Event High



Warning Event High



Warning Event High



Warning Event High


16#00004000 Sametime Open LS and Closed LS - Byte 0 Bit 7

Warning Alarm High


16#00008000 Run-time exceeded - Byte 2 Bit 0

Warning Alarm Medium


16#00010000 Open TS->0 but not Open LS (intermed.) - Byte 0 Bit 0

Warning Alarm High


16#00020000 Clos LS->0 not within 3 s after Open cmd. - Byte 0 Bit 1

Warning Alarm High


Status BitHW-

StatusValue


Warning/Error

Alarm/Event

Severity


24 2PAA104102M02


16#00040000 Open LS->0 not within 3 s after Close cmd. - Byte 0 Bit 2

Warning Alarm High


16#00080000 Closed LS disappears without Open cmd. - Byte 0 Bit 3

Warning Alarm High


16#00100000 Open LS disappears without Close cmd. - Byte 0 Bit 4

Warning Alarm High


16#01000000 Emergency start prepared - Byte 2 Bit 1

Warning Event High





Warning Alarm High


Status BitHW-

StatusValue


Warning/Error

Alarm/Event

Severity


2PAA104102M02 25



Warning Alarm High


16#00000004 Relay 0 Check-back Fault / Clos TS->0 but not closed LS(intermed.) - Byte 1 Bit 0

Warning Alarm High


16#00000008 Relay 1 Check-back Fault / Closed LS appears without close cmd. - Byte 1 Bit 1

Warning Alarm High


16#00000010 Relay 2 Check-back Fault / Open LS appears without Open cmd. - Byte 1 Bit 2

Warning Alarm High



Warning Alarm High



Warning Alarm High



Warning Alarm High


Status BitHW-

StatusValue


Warning/Error

Alarm/Event

Severity


26 2PAA104102M02



Warning Alarm High



Warning Alarm High



Warning Event High



Warning Event High



Warning Event High



Warning Event High



Warning Event High



Warning Event High


16#00004000 Sametime Open LS and Closed LS - Byte 0 Bit 7

Warning Alarm High


Status BitHW-

StatusValue


Warning/Error

Alarm/Event

Severity


2PAA104102M02 27


16#00008000 Run-time exceeded - Byte 2 Bit 0

Warning Alarm Medium


16#00010000 Open TS->0 but not Open LS (intermed.) - Byte 0 Bit 0

Warning Alarm High


16#00020000 Clos LS->0 not within 3 s after Open cmd. - Byte 0 Bit 1

Warning Alarm High


16#00040000 Open LS->0 not within 3 s after Close cmd. - Byte 0 Bit 2

Warning Alarm High


16#00080000 Closed LS disappears without Open cmd. - Byte 0 Bit 3

Warning Alarm High


16#00100000 Open LS disappears without Close cmd. - Byte 0 Bit 4

Warning Alarm High


16#01000000 Emergency start prepared - Byte 2 Bit 1

Warning Event High


Status BitHW-

StatusValue


Warning/Error

Alarm/Event

Severity


28 2PAA104102M02


16#00020000 PTC temperature - Byte 3 Bit 0

Warning Alarm High


16#80000000 PTC wire break - Byte 3 Bit 1

Warning Alarm High


16#40000000 PTC Short-circuit - Byte 3 Bit 2

Warning Alarm High


16#20000000 Earth Fault - Byte 3 Bit 3

Warning Alarm High


16#08000000 Fault on DI0 - Byte 3 Bit 4

Warning Alarm High



Warning Alarm High



Warning Alarm High

MSD11

-/- Diagnostic bits NOT AVAILABLE

-/- -/-

MFI21



16#00000001 Common Fault Warning Alarm High


Status BitHW-

StatusValue


Warning/Error

Alarm/Event

Severity


2PAA104102M02 29


16#00000002 Faulty Channel 0

Warning Alarm High



Warning Alarm High



Warning Alarm High


16#00000010 Common Fault: Communication off

Warning Alarm High


16#00000020 Common Fault: both Input Commands on the same time

Warning Alarm High


16#00000040 Common Fault: Value of Delay Time out of range

Warning Alarm High


16#00000080 Common Fault: Parameter unknown

Warning Alarm High


16#00000100 IO Fault: Command signal for Output 0 appears without Input 0

Warning Alarm High


Status BitHW-

StatusValue


Warning/Error

Alarm/Event

Severity


30 2PAA104102M02


16#00000200 IO Fault: No Command signal for Output 0, even with Input 0

Warning Alarm High

MSR22



16#00000001 Contactor 1 Stick RUN 1 - Byte 0 Bit 0

Warning Alarm High

ExtendedStatus 2 ExtendedStatus

16#00000002 Contactor 1 OFF RUN 1 - Byte 0 Bit 1

Warning Alarm High


16#00000004 Contactor 2 Stick RUN 2 - Byte 0 Bit 2

Warning Alarm High


16#00000008 Contactor 2 OFF RUN 2 - Byte 0 Bit 3

Warning Alarm High


16#00000010 Communication Fault - Byte 0 Bit 4 and 5

Warning Alarm High


16#00000020 Both Output Relays Set - Byte 0 Bit 4 and 5

Warning Alarm High


Status BitHW-

StatusValue


Warning/Error

Alarm/Event

Severity


2PAA104102M02 31

PR122/PR123/PR332/PR333



16#00000001 No Device Communication - Byte 0 Bit 0

Error Alarm High


16#00000002 Wrong Device Connected - Byte 0 Bit 1

Error Alarm High


16#00000004 Device Not Initialized - Byte 0 Bit 2

Error Alarm High


16#00000008 Internal Configuration Map Error - Byte 0 Bit 3

Error Alarm High


16#00000010 Wrong Parameter Number - Byte 0 Bit 4

Warning Alarm High


16#00000020 Wrong Parameter Value - Byte 0 Bit 5

Warning Alarm High


Status BitHW-

StatusValue


Warning/Error

Alarm/Event

Severity


32 2PAA104102M02


16#00000040 Command Not Executed - Byte 0 Bit 6

Warning Alarm High


16#00000080 Diagnostics Present - Byte 0 Bit 7

Warning Alarm High


16#00000100 Watchdog Fault - Byte 1 Bit 0

Error Alarm High


16#00000200 Modbus UART Fault - Byte 1 Bit 1

Error Alarm High


16#00000400 RS485 Driver Fault - Byte 1 Bit 2

Error Alarm High


Status BitHW-

StatusValue


Warning/Error

Alarm/Event

Severity


2PAA104102M02 33

PR222 DS/PD



16#00000001 No Device Communication - Byte 0 Bit 0

Error Alarm High


16#00000002 Wrong Device Connected - Byte 0 Bit 1

Error Alarm High


16#00000004 Device Not Initialized - Byte 0 Bit 2

Error Alarm High


16#00000008 Internal Configuration Map Error - Byte 0 Bit 3

Error Alarm High


16#00000010 Wrong Parameter Number - Byte 0 Bit 4

Warning Alarm High


16#00000020 Wrong Parameter Value - Byte 0 Bit 5

Warning Alarm High


16#00000040 Command Not Executed - Byte 0 Bit 6

Warning Alarm High


Status BitHW-

StatusValue


Warning/Error

Alarm/Event

Severity


34 2PAA104102M02


16#00000080 Diagnostics Present - Byte 0 Bit 7

Warning Alarm High


16#00000100 Watchdog Fault - Byte 1 Bit 0

Error Alarm High


16#00000200 Modbus UART Fault - Byte 1 Bit 1

Error Alarm High


16#00000400 RS485 Driver Fault - Byte 1 Bit 2

Error Alarm High


16#00000800 Cyclic Command Wrong Value - Byte 1 Bit 3

Warning Alarm High


16#00001000 Cyclic Command Not Executed - Byte 1 Bit 4

Warning Alarm High


Status BitHW-

StatusValue


Warning/Error

Alarm/Event

Severity


2PAA104102M02 35

Device Type Manager (DTM)

The DTM will be installed during setup of the device type via Device Library Wizard. User interactions may be required during installation or post installation. Please refer to section Device Type, Modules and Channels on page 9 in this document for more details.

Table 6. Device Type Manager

DTM Type Generic PROFIBUS DTM with UMC22, PR222 DS/PD and PR122_123_332_333 application (This DTM is valid for UMC22, PR222 DS/PD and PR122_123_332_333 modules).

Version / Date See Used Version of Device Management PROFIBUS.

FDT Version 1.2

Vendor ABB

DTM License Not required

DTMs are available for devices UMC22_FW3_20_v1 (Firmware 3.2), UMC22_FW3_30_v1 (Firmware 3.3) and UMC22_FW3_40_v1 (Firmware 3.4), UMC22_FW4_00_v1 (Firmware 4.0), PR222 DS/PD and PR122_123_332_333.These DTMs are available at the Gateway (PDP22) module.

User needs to select the appropriate UMC version in the Module tab of DTM configuration window.


36 2PAA104102M02

Asset OptimizationThis functionality requires installation of 800xA Asset Optimization software and can be used if the corresponding system extensions have been loaded.Asset

Optimization functionality for this device is available in aspect,

• PROFIBUS ABB UMC22 Asset Monitor for UMC22(Firmware version 3.2).

• Profibus ABB UMC22-FBP_DPV_0_1_V3.3 for UMC22(Firmware version 3.3).



• Asset Monitor not available for MSD11.

• Asset Monitor not available for MFI21.

• Asset Monitor not available for MSR22.

• Profibus ABB PR122 - PR123 - PR332 - PR333 - for PR122/PR123/PR332/PR333.

• Profibus ABB PR222.

For more details, please refer to AO Configuration manual (3BUA000118R4101) and AO Operation manual (3BUA000150R4101).

Table 7. Asset Optimization Functionality

Asset Monitor(s) Device Specific Asset Monitor (Profibus ABB PR222)

Asset Reporter / Viewer Yes on Device Type (Slave)

CMMS Connectivity Maximo, SAP(1)

(1) SAP web view that allows direct interaction with the data is not a released functionality. Hence this access is not available.


2PAA104102M02 37

Table 8. Asset Monitor Conditions

Sl. No.

Conditions

Su

pp

ort

ed


1 External Fault Detected X

2 UMC Self Test Failed X

3 Contactor Check-back Failed on Relay 1 X



6 Contactor Check-back Failed on Relays 1 and 2 X



9 Contactor Check-back Failed on Relays 1, 2 and 3 X

10 Parameterization Invalid X

11 Communication Fault X

12 Motor Status Blocked X

13 Motor Status Overload (Trip) X

14 Motor Current Above High Threshold X

15 Motor Current Below Low Threshold X

16 Current Check-back Fault X


1 External Fault Detected X

2 UMC Self Test Failed X



38 2PAA104102M02






9 Contactor Check-back Failed on Relays 1, 2 and 3 X

10 Parameterization Invalid X

11 Communication Fault X

12 Motor Status Blocked X

13 Motor Status Overload (Trip) X

14 Motor Current Above High Threshold X

15 Motor Current Below Low Threshold X

16 Current Check-back Fault X

17 Actuator Sametime Open LS and Closed LS X

18 Actuator CloseTS->0 but not Closed LS (intermed.) X

19 Actuator Closed LS appears without Close cmd. X

20 Actuator Open LS appears without Open cmd. X

21 Actuator Run-time exeeded X

22 Actuator OpenTS->0 but not Open LS (intermed.) X

23 Actuator CloseLS->0 not within 3 s after Open cmd. X

24 Actuator OpenLS->0 not within 3 s after Close cmd. X


Sl. No.

Conditions

Su

pp

ort

ed


2PAA104102M02 39

25 Actuator Closed LS disappears without Open cmd X

26 Actuator Open LS disappears without Close cmd. X


1 Process and Installation, Motor cannot be started: Current is missing after motor was switched on.

X

2 Process and Installation, Motor cannot be started: Expected feedback from a contactor is missing.

X

3 Process and Installation, PTC protection not available: PTC wire broken or not connected with motor

X

4 Process and Installation, PTC protection not available: Short circuit between PTC wires.

X

5 Process and Installation, Ground Fault: Connection between one or more phases and ground

X

6 Process and Installation, Motor blocked: Motor current above blocking threshold..

X

7 Process and Installation, Actuator operation not possible: Problem with wiring of torque or limit switches. Limit switches not adjusted correctly.

X

8 Process and installation, Actuator operation not possible: Open/close time of actuator exeeded because of tight valve or other mechanical reasons.

X

9 Process and installation, Motor overload: Motor current above user defined threshold.

X

10 Process and installation, Motor underload: Motor current is below user defined threshold e.g. motor running idle

X


Sl. No.

Conditions

Su

pp

ort

ed


40 2PAA104102M02

11 Process and installation, Motor has tripped: Trip because of thermal overload of the motor or because of phase loss.

X

12 Process and installation, Motor has tripped: PTC element indicated that motor temperature is too high.

X

13 Process and installation, Motor has stopped: One of the inputs DI0, DI1 or DI2 triggerd a fault. The cause depends on the connected hardware. E.g. a PT100 or cos phi protection relais.

X

14 Process and Installation, Too many trips: Trip counter above configured limit

X

15 Configuration failure, UMC22 not operational X

16 Communication failure. X

17 Self test failed. X

18 Motor maintenance required (soon) X

19 Motor maintenance required (now) X

18 Contactor maintenance required (soon) X

19 Contactor maintenance required (now) X

PR122/PR123/PR332/PR333

CB Status Contacts

1 CB Status Contacts Normal X

2 Failure - CB status undefined.CB open contact gives information not compatible with CB close contact.

X

3 Failure - CB status error. CB status contacts gives erroneous information.

X


Sl. No.

Conditions

Su

pp

ort

ed


2PAA104102M02 41

Local Bus Unit

4 Local Bus Unit Normal X

5 Failure - The unit connected on Local Bus is not communicating. X

Trip Coil

6 Trip Coil Normal X

7 Failure - Trip Coil is not working properly X

8 Failure - Trip Coil is not connected. X

Contacts

9 Contacts Normal X

10 Maintenance required (soon) - Contact Wear percentage is > 80 % X

11 Maintenance required (now) - Contact Wear percentage has reached 100%

X

Temperature Sensor

12 Temperature Sensor Normal X

13 Maintenance required (soon) - Temperature is higher than 70° or lower than -20°

X

14 Maintenance required (now) - Temperature is higher than 85° or lower than -25°

X

15 Maintenance required (now) - Temperature is higher than 85° and lower than -25°. The protections would have lead to a trip but trip is blocked.

X

16 Failure - Protection against over or under temperature (T) led to a trip.

X


Sl. No.

Conditions

Su

pp

ort

ed


42 2PAA104102M02

Load side, electrical

17 Load side,electrical Normal X

18 Maintenance required (soon) - Power Factor below threshold. X

19 Maintenance required (now) - Harmonic distortion too high X

20 Maintenance required (soon) - Current warning. Current is higher than user-defined Iw threshold.

X

21 Maintenance required (soon) - Load control 1 Alarm. Current is higher than user-defined LC1 threshold.

X

22 Maintenance required (soon) - Load control 1 Alarm. Current is higher than user-defined LC2 threshold.

X

23 Maintenance required (soon) - Overload protection (L) pre-alarm warning. Current higher than 90% of L threshold

X

24 Maintenance required (now) - Overload protection (L) alarm. The protection is timing to trip. Current higher than L threshold.

X

25 Maintenance required (now) - Selective protection against short-cirrcuit (S) alarm. The protecion is timing to trip. Current higher than S threshold.

X

26 Maintenance required (now) - Second selective protection against short-circuit (S2). The protecion is timing to trip. Current higher than S2 threshold.

X

27 Maintenance required (now) - Internal ground fault protection (G) alarm. The protection is timing to trip. Current higher than G threshold.

X

28 Maintenance required (now) - Protection against phase unbalance. The protection is timing to trip.

X


Sl. No.

Conditions

Su

pp

ort

ed


2PAA104102M02 43

29 Maintenance required (now) - Internal ground fault protection (G) blocked trip. Current higher than G threshold. The protection is detecting an abnormal condition but it won't lead to a trip because tripping is disabled.

X

30 Maintenance required (now) - Protection against phase unbalance. The protection is detecting an abnormal condition but it won't lead to a trip because tripping is disabled.

X

31 Failure - Protection against overload (L) led to a trip X

32 Failure - Selective protection against short-circuit (S) led to a trip X

33 Failure - Second selective protection against short-circuit (S2) led to a trip

X

34 Failure - Istantaneous protection (I) led to a trip X

35 Failure - Automatic protection (I inst) led to a trip X

36 Failure - Internal protection against earth fault (G) led to a trip X

37 Failure - Protection against phase unbalance (U) led to a trip X

Supply side, electrical

38 Supply side,electrical Normal X

39 Maintenance required (now) - Phase Cycle Error X

40 Maintenance required (now) - Protection against reverse active power. The protection is timing to trip.

X

41 Maintenance required (now) - Protection against reverse active power. The protection is detecting an abnormal condition but it won't lead to a trip because tripping is disabled.

X

42 Maintenance required (now) - Protection against reverse active power (RP) led to a trip.

X


Sl. No.

Conditions

Su

pp

ort

ed


44 2PAA104102M02

Supply / Load side, electrical

43 Supply / Load side,electrical Normal X

44 Maintenance required (now) - Net frequency is out of range(lower or higher than 10% of nominal frequency value)

X

45 Maintenance required (now) - External ground fault protection (G Ext) alarm. The protection is timing to trip. Current higher than G Ext threshold.

X

46 Maintenance required (now) - Directional protection against short-circuit (D) alarm. The protection is timing to trip. Current higher than D threshold.

X

47 Maintenance required (now) - Protection against under voltage. The protection is timing to trip. Voltage lower than UV threshold.

X

48 Maintenance required (now) - Protection against over voltage. The protection is timing to trip. Voltage higher than OV threshold

X

49 Maintenance required (now) - Protection against residual voltage. The protection is timing to trip.

X

50 Maintenance required (now) - Protection against under frequency. The protection is timing to trip.

X

51 Maintenance required (now) - Protection against over frequency. The protection is timing to trip.

X

52 Maintenance required (now) - External ground fault protection (G Ext) blocked trip. Current higher than G Ext threshold. The protection is detecting an abnormal condition but it won't lead to a trip because tripping is disabled.

X


Sl. No.

Conditions

Su

pp

ort

ed


2PAA104102M02 45

53 Maintenance required (now) - Protection against under voltage. The protection is detecting an abnormal condition but it won't lead to a trip because tripping is disabled.

X

54 Maintenance required (now) - Protection against over voltage. The protection is detecting an abnormal condition but it won't lead to a trip because tripping is disabled.

X

55 Maintenance required (now) - Protection against residual voltage. The protection is detecting an abnormal condition but it won't lead to a trip because tripping is disabled.

X

56 Maintenance required (now) - Protection against under frequency. The protection is detecting an abnormal condition but it won't lead to a trip because tripping is disabled.

X

57 Maintenance required (now) - Protection against over frequency. The protection is detecting an abnormal condition but it won't lead to a trip because tripping is disabled.

X

58 Failure - External protection against earth fault (G Ext) led to a trip X

59 Failure - Protection against directional short-cirtcuit (D) led to a trip X

60 Failure - Protection against under voltage (UV) led to a trip. X

61 Failure - Protection against over voltage (OV) led to a trip. X

62 Failure - Protection against residual voltage led to a trip. X

63 Failure - Protection against under frequency (UF) led to a trip. X

64 Failure - Protection against over frequency (OF) led to a trip. X

L1 Sensor

65 L1 Sensor Normal X

66 Failure - Phase 1 sensor error X


Sl. No.

Conditions

Su

pp

ort

ed


46 2PAA104102M02

L2 Sensor



L3 Sensor



Ne Sensor

71 Ne Sensor Normal X

72 Failure - Phase neutral sensor error X

GTe Sensor

73 GTe Sensor Normal X

74 Failure - Ground toroid external (GTe) sensor error X

Rating Plug

75 Rating Plug Normal X

76 Failure - Rating Plug error X

Key Plug

77 Key Plug Normal X

78 Failure - Key Plug error X

Trip unit, Electronic

79 Trip unit,Electronic Normal X

80 Function check - A trip test has been performed from device HMI X


Sl. No.

Conditions

Su

pp

ort

ed


2PAA104102M02 47

81 Function check - A trip test has been performed from test unit X

82 Maintenance required (soon) - Invalid Date X

83 Maintenance required (now)- Configuration Error X

84 Failure - Fault of the CB electronic internal hardware X

85 Failure - Trip generated by external digital input unit X

86 Failure - A hardware error has led to a trip X

EP010

87 EP010 Normal X

88 Failure - EP010 can't communicate with CB Trip Unit X

89 Failure - EP010 detects a wrong CB Trip Unit type X

90 Failure - Some CB Trip Unit data are not initialized X

91 Failure - EP010 software configuration error X

92 Failure - EP010 watchdog error X

93 Failure - EP010 Modbus communication interface (UART) error X

94 Failure - EP010 Modbus communication interface (RS485) error X

PR222 DS/PD

Trip Coil

1 Normal X

2 Failure - Trip Coil is not working properly X

Load side,electrical

3 Normal X


Sl. No.

Conditions

Su

pp

ort

ed


48 2PAA104102M02

4 Maintenance required (soon) - Overload protection (L) pre-alarm warning

X

5 Maintenance required (now) - Overload protection (L) alarm X

6 Maintenance required (now) - Selective protection against short-circuit (S) alarm

X

7 Maintenance required (now) - Internal ground fault protection (G) alarm

X

8 Failure - Protection against overload (L) led to a trip X

9 Failure - Selective protection against short-circuit (S) led to a trip X

10 Failure - Instantaneous protection (I) led to a trip X

11 Failure - Internal protection against earth fault (G) led to a trip X

MOE-E

12 Normal X

13 Failure - Motor operator MOE-E is overheated X

14 Failure - Motor operator MOE-E status is unknown X

AUX-E

15 Normal X

16 Failure - Auxliliary contacts AUX-E status is unknown X

Trip Unit,dip-switches setting

17 Normal X

18 Maintenance required (now) - Trip unit manual parameters (dip-switches setting) are inconsistent

X


Sl. No.

Conditions

Su

pp

ort

ed


2PAA104102M02 49

Trip Unit,Electronic

19 Normal X

20 Maintenance required (now) - Trip unit electronic parameters are erroneous

X

21 Function check - A trip test has been performed from Test Unit X

UVR

22 Normal X

23 Failure - Trip test or UVR (Under Voltage Release) led to a trip X

EP010

24 Normal X

25 Failure - EP010 can't communicate with CB Trip Unit X

26 Failure - EP010 detects a wrong CB Trip Unit type X

27 Failure - Some CB Trip Unit data are not initialized X

28 Failure - EP010 software configuration error X

29 Failure - EP010 watchdog error X

30 Failure - EP010 Modbus communication interface (UART) error X

31 Failure - EP010 Modbus communication interface (RS485) error X


Sl. No.

Conditions

Su

pp

ort

ed


50 2PAA104102M02

For UMC22(Firmware version 3.3) note the below.

For UMC22(Firmware version 3.4) note the below.

If user has selected Control Function as “Actuator” then the Asset Parameter "Actuator Configured" should be set to TRUE. This can be set by:

1. Select Asset Monitor at instance level.

2. Select Config view.

3. Select tab ”Asset Parameters”.

4. Un-check “Inherit Configuration”.

5. Set “Actuator Configured” to true and then apply the changes.

If user has selected Control Function as “Actuator” then the Asset Parameter "Actuator Configured" should be set to TRUE. This can be set by:

1. Select Asset Monitor at instance level.

2. Select Config view.

3. Select tab ”Asset Parameters”.

4. Un-check “Inherit Configuration”.

5. Set “AP_Actuator_Operational_Mode” to true and then apply the changes.

Follow above procedure to change “Operating hours”, ”No. of Starts” and “No. of Trips”.


2PAA104102M02 51

Fixed Problems

Table 9 lists the critical or major issues that have been corrected since the previous version. A brief description of the correction is also been given.

Known Problems

Table 10 lists issues that may exist and affect the operation of the device type at time of release. Workarounds, clarifications, or helpful hints have been provided for each issue wherever possible.

Table 9. Fixed Problems

Issue Fixed Description

Fixed issue of “Internal Configuration Map Error - Byte 0 bit 3” for PR123 module.

Changed the diagnosis bit information in hardware file of PR123 module.

Table 10. Known Problems

Issue Workaround

Operator user role cannot work with UMC22 application of DTM in SV5.0.

-/-


52 2PAA104102M02

Support

Contact ABB technical support for assistance in problem reporting.


2PAA104102M02 53


2PAA104102M02. Printed in Sweden March 2009Copyright © 2009 by ABB. All Rights Reserved® Registered Trademark of ABB.™ Trademark of ABB.

http://www.abb.com

Automation Technology Products Wickliffe, Ohio, USAwww.abb.com/controlsystems

Automation Technology ProductsVästerås, Swedenwww.abb.com/controlsystems

Automation Technology ProductsMannheim, Germanywww.abb.de/controlsystems

800xa - device management profibus - abb ltd · 800xa - device management profibus device type abb...

Documents