Experion PKS

Release 530

Profibus Gateway Module User's Guide

EPDOC-XX88-en-530B
June 2025
 DISCLAIMER
This document contains Honeywell proprietary information.
Information contained herein is to be used solely for the
purpose submitted, and no part of this document or its
contents shall be reproduced, published, or disclosed to a third
party without the express permission of Honeywell
International Sàrl.
While this information is presented in good faith and believed
to be accurate, Honeywell disclaims the implied warranties of
merchantability and fitness for a purpose and makes no
express warranties except as may be stated in its written
agreement with and for its customer.
In no event is Honeywell liable to anyone for any direct, special,
or consequential damages. The information and specifications
in this document are subject to change without notice.
Copyright 2025 - Honeywell International Sàrl

2
CONTENTS
Chapter 1 - About this guide 19
Revision history 19

Chapter 2 - PROFIBUS Gateway Module (PGM) Overview 20

PROFIBUS Communication Profiles 21
PROFIBUS DP Overview 22
PROFIBUS PA Overview 22
PROFIBUS network time synchronization support 22
DPV1 alarm support 22
Overview of PGM components 23
About DPV1 and HART enhancements for PGM 24
DPV1 24
HART enhancements 25
PGM topology 25
PGM data flow diagram 27
Data communication in PGM 28

Chapter 3 - PROFIBUS Gateway Module (PGM) Planning and Design 30

Review ExperionLXPlantCruiseExperion PKS system capabilities 31

Chapter 4 - PROFIBUS Gateway Module (PGM) Installation 33

Pre-installation considerations 34
PGM assembly 34
CF9 control firewall - 9-port control firewall (CF9) 35
PGM IOTA pinouts 35
PROFIBUS DP Master LED behavior 37
Installing a PGM 39

3
 Prerequisites 39
Perform the following steps to install a PGM 39
PGM power-on and startup 41
PGM Startup 41
PGM front panel and LED display 41
Profibus cabling guidelines 42
Copper cable-based media redundancy 42
Fiber-optic cabling-based media redundancy 43
Redundant PGM in a non-redundant Profibus cabling 44

Chapter 5 - PROFIBUS Gateway Module (PGM) Block 46

PGM overview 47
PGM redundancy support 47
HART device support in PGM 47
PGM block creation 48
PGM block deletion 48
Configuring a PGM 48
Perform the following steps to configure a PGM 48
Configuring a secondary PGM 49
Perform the following steps to configure a secondary PGM 49
Converting a redundant PGM to a non-redundant PGM 49
Perform the following steps to convert a redundant PGM to a
non-redundant PGM 49
Monitoring PGM block 50
PGM block state after configuration and load 50
PGM block status parameters 50
PGM block command parameters 51
PGM PDA statistics parameters 51
PGM memory statistics parameters 52

4
 PGM block icons 54
PGM block diagnostic alarms 56
PGM redundancy-specific operations 58
About switchover 58
Conditions that result in a switchover 59
Conditions that do not result in a switchover 59
Conditions that result in loss of synchronization 59
PGM Redundancy tab in Monitoring view 60
Enabling Synchronization 61
Disabling Synchronization 61
Configuring the network for switchover 62
Enabling a secondary PGM to become a primary PGM in the
absence of a partner module 65
Performing a manual switchover 66
PGM redundancy notifications 66
PGM shutdown operations 67
Initiating a PGM shutdown 67
Shutting down the secondary PGM 69
PGM block station displays 69
Detail displays and faceplate names 69
Calling up the displays 70
Detail display tabs 71
PGM group detail display, system status display, group trend
display 74
PGM faceplates 76

Chapter 6 - Protocol Block 78

Protocol Block overview 79

5
 "Profibus Network Configuration Tool " 79
Using Profibus Network Configuration Tool for configuring field
network devices 80
Configuring the Protocol Block 81
Perform the following steps to configure a Protocol Block 81
Configuring the PROFIBUS devices in PROFIBUS Network
Configuration Tool 82
Prerequisites 82
Perform the following steps to configure a PROFIBUS device 83
Drive DSB specific module configuration in Profibus Network
Configuration Tool 86
GENPADSB and GENPAGWDSB specific module configuration
in Profibus Network Configuration Tool 86
Siemens ASi Link DSB specific modules configuration in
Profibus Network Configuration Tool 87
Siemens ET 200M DSB specific module configuration in
Profibus Network Configuration Tool 87
Turck Excom DSB specific modules configuration in Profibus
Network Configuration Tool 88
Configuring the master in Profibus Network Configuration Tool 91
Perform the following steps to configure the master 91
Assigning the device to the correct hardware 92
Modifying the PROFIBUS network setup values (bus parameters)93
Configuring the field network tag names 94
Changing the field network device address 99
Changing the master settings 99
Detecting PROFIBUS devices in the network 99
Adding a new GSD-based device to PROFIBUS Network
Configuration Tool library 100
Perform the following steps to add a new GSD-based device to 101

6
 PROFIBUS Network Configuration Tool library
About grouping adjacent modules into one logical module 101
Guidelines for grouping modules 102
About the Address Management page 104
Grouping adjacent modules into one logical module 106
Ungrouping grouped modules 107
Adding reserved memory area to the devices 108
Defragmenting memory area 109
About the Signal Configuration page 109
About modifying the field network configuration during runtime 110
Guidelines for using the Configure In Runtime (CiR) / Hot
Configuration in Run (HCiR) feature 112
Support for time synchronization functionality 114
Configuring time synchronization in PGM master DTM 114
Configuring time synchronization in responder 115
Export/import of field network configuration 116
Exporting field network configuration 117
Importing field network configuration 117
Audit Trail for field network configuration 118
Operations that impact Audit Trail 119
Monitoring Protocol Block 120
Protocol Block state after configuration and load 120
Protocol Block status parameters 121
Protocol Block command parameters 122
Protocol block statistics parameters 122
Protocol Block icons 123
Protocol Block notifications 124

7
 Monitoring the field network configuration 125
Viewing the master's diagnosis and extended diagnosis 126
Viewing the status of all PROFIBUS devices from the Profibus
Network Configuration Tool Network view 128
Viewing the PROFIBUS devices from the Life List menu 129
Changing the device address from the Set Station Address
menu 129
Detecting PROFIBUS devices in the network 131
Viewing the PROFIBUS device diagnosis 132
Viewing the PROFIBUS device's extended diagnosis 133
QVCS - Diff Tool view of non-human readable data 135
Protocol Block station displays 136
Detail displays and faceplate names 136
Calling up the displays 136
Detail display tabs 137

Chapter 7 - PROFIBUS Configuration Tools 141

Accessing PROFIBUS Configuration Tools 144
Configuring responders/modules 146
Rule files 146
Creating rule file from a template 147
Guidelines for naming a rule file 148
Guidelines for configuring rule file 149
Elements configured in a rule file 150
Modifying the existing rule file 164
Selecting the default rule file in Auto-configure Slaves 164
Configuring the PROFIBUS device 165
Representation of DSB names 166
Configuring the modules 167

8
 Representation of PIOMB names 168
Representation of PBHIOMB names 169
Subsequent Update of DSB using Auto Configure Slave 169
Validating and saving configuration 171
Troubleshooting scenarios 174

Chapter 8 - Device Support Block (DSB) 180

Device Support Block (DSB) overview 181
DSB block creation 182
DSB block deletion 182
About DPV1 read/write messages configuration in DSBs 183
DPV1 records scanning 184
Configuring DPV1 read/write messages (Project view) 185
HART communication/response time impact in a DP network 186
Data processing 188
Extended range handling 189
Generic Device Support Blocks (GENDSB and GENIODSB) 190
Functions of Generic DSBs 191
Generic Device Support Blocks (GENPADSB and GENPAGWDSB)
for PA devices 192
Functions of GENPADSB and GENPAGWDSB 192
Generic Drive Device Support Block (DRIVEDSB) 193
Parameter - process data object (PPO) 194
Configurable channel types 195
Guidelines for using PKW channels 195
Supported data transfer types 197
Functions of DRIVEDSB 198
CEAG Device Support Block (CEAGDSB) 200

9
 I/O modules supported by the CEAGDSB 201
Functions of CEAGDSB 204
Siemens AS-i Link Device Support Block (Siemens DP/AS-i-Link
DSB) 209
Functions of Siemens AS-i Link 210
Siemens ET200M Device Support Block (Siemens ET200M DSB) 214
Supported gateways 215
I/O modules supported by the Siemens ET200M DSB 215
Functions of Siemens ET200M DSB 219
Turck Excom Device Support Block (Turck Excom DSB) 222
Support for processing HART data 222
Gateway redundancy 223
Guidelines for configuring DM80Ex digital module 223
Guidelines for configuring the DF20Ex F as a Frequency
Counter module 223
Guidelines for configuring the DF20Ex P as a Pulse Counter
module 224
I/O modules supported by the Turck Excom DSB 224
Functions of Turck Excom DSB 225
UDT support for DSB blocks 228
Template defining parameters for DSB block types 228
Bulk Build support for DSB block types 228
Guidelines for configuring DSBs 229
Configuring a Generic Device Support Block 230
Prerequisites 231
Perform the following steps to configure a GENDSB 231
Configuring a device-specific DSB 233
Prerequisites 233

10
 Perform the following steps to configure a device-specific DSB 233
About initialization of AO/DO channels from user-defined values 236
Background 236
Overview 237
Impact on DSB load 241
Configuring the PDC 242
Perform the following steps to configure the PDC 242
Generic DSB specific PDC configuration guidelines 245
Generic Drive DSB specific PDC configuration guidelines 247
Generic DSB for PA devices (GENPADSB and GENPAGWDSB)
specific PDC configuration guidelines 249
CEAG DSB specific PDC configuration guidelines 252
Siemens AS-I Link DSB specific PDC configuration guidelines 252
Siemens ET200M DSB specific PDC configuration guidelines 254
Turck Excom DSB specific PDC configuration guidelines 256
oHGuidelines for configuring Turck Excon DSB for reading
HART data 258
Guidelines for configuring Turck Excon DSB for gateway
redundancy 260
Alarms 261
Alarms supported by GENPADSB 262
Alarms supported by GENPAGWDSB 262
About RIO (Remote IO) profile-based alarming 262
Configuring alarms 265
Support for device-specific alarms 268
Configuring device-specific alarms 269
Monitoring DSB block 271
DSB block state after configuration and load 271

11
 DSB block status parameters 276
Monitoring the DPV1 data records 277
DSB block icons 277
DSB block diagnostic alarms 278
o Monitoring device-specific alarms 282
Setting the channel output values from Monitoring view 283
Setting the analog output values 284
Setting the digital output values 284
DSB block station displays 284
Detail displays and faceplate names 284
Calling up the displays 285
Detail display tab 285

Chapter 9 - PROFIBUS HART Input/Output Module (PBHIOM) Function

Block 289
PBHIOMB block overview 290
Bulk Build support for PBHIOMB block 292
PBHIOMB block creation 292
PBHIOMB block deletion 292
PROFIBUS HART I/O channel 293
PBHCHANNEL block creation 293
PBHCHANNEL block deletion 294
Functioning of PBHIOMB 295
Connection and status processing 295
Configuring a PBHIOMB block 296
Prerequisites 296
To configure a PBHIOMB block when PDC is not grouped 296
To configure a PBHIOMB block when PDC is grouped 298
To configure a PBHIOMB block for Universal Modules 299

12
 Configuring a PBHCHANNEL block 301
Creating a new HART channel (PBHCHANNEL) when
PBHIOMB is loaded 302
PBHIOMB operations affecting the control behavior 303
Monitoring a PBHIOMB block 304
PBHIOMB block state after configuration and load 304
PBHIOMB block status parameters 305
About auto-discovery of HART devices 306
Monitoring the PBHCHANNEL block 308
PBHCHANNEL HART Status-related parameters 309
PBHCHANNEL HART Notification-related parameters 310
PBHCHANNEL HART Variables-related parameters 310
PBHCHANNEL HART Identification-related parameters 312
HART alarms/events processing 313
HART alarms/event regeneration 315
PBHIOMB block station displays 315
Main tab - Detail Displays 316
HART channels-Detail Display 316
Config. Details tab-Detail Display 317
PBHCHANNEL station displays 318
Main tab - Detail Displays 318
Config. Details tab-Detail Display 319

Chapter 10 - PROFIBUS I/O Module (PIOMB) Function Block 320

PIOMB block overview 321
PIOMB block creation 322
PIOMB block deletion 322
PROFIBUS I/O channel blocks 322

13
 Function 323
Functioning of PIOMB 324
Connection and status processing 324
Input module processing 325
Output module processing 325
Clamping of output process values 325
Scaling of process data 325
Notifications 326
Example to illustrate operations affecting the control behavior 326
Configuring a PIOMB 340
Prerequisites 340
Perform the following steps to configure a PIOMB 340
Assigning a PROFIBUS Channel to PIOMB 342
Perform the following steps to assign a PROFIBUS channel to a
PIOMB 343
Monitoring PIOMB block 345
PIOMB block state after configuration and load 345
PIOMB block status parameters 347
PIOMB block icons 347
PIOMB notifications 348
PIOMB block station displays 348
Detail displays and faceplate names 348
Calling up the displays 348
Detail displays tabs 349

Chapter 11 - PROFIBUS Gateway Module (PGM) Configuration Example 353

Chapter 12 - Loading PROFIBUS Gateway Module (PGM) 357
Initial load order guidelines 358
Loading PGM function blocks 358

14
 Loading a PGM 361
Perform the following steps to load a PGM function block and
its associated blocks 361
Reloading the PGM function blocks 362
Reloading the PGM function block 362
Reloading the Protocol Block 362
Reloading the DSB function block 362
Reloading the PIOMB function block 363
Reloading the PBHIOMB function block 363
Reloading a CM containing PROFIBUS I/O channel blocks 363
Reloading the PROFIBUS HART I/O channel blocks 364

Chapter 13 - PROFIBUS Gateway Module (PGM) Maintenance 365

Periodic checks 366
Replacing a non-redundant PGM 366
Perform the following steps to replace a non-redundant PGM 366
Replacing a redundant or secondary PGM 367
Perform the following steps to replace a redundant or
secondary PGM 367
Replacing a non-redundant PGM IOTA board 368
Perform the following steps to replace a non-redundant PGM
IOTA board 368
Replacing a redundant or secondary PGM IOTA board 370
Perform the following steps to replace a redundant or
secondary PGM IOTA board 370

Chapter 14 - PROFIBUS Gateway Module (PGM) Troubleshooting 372

Behavior of PGM during fault scenarios 373
Loss of communication between PGM and C300/UOC/HCA 373
Loss of communication between PGM and PROFIBUS device 374

15
 Loss of communication between the PGM and control
strategies 375
CEEC300/UOC/HCA state is changed to Idle 375
Inactivation of PIOMB 375
Deletion of PIOMB 376
PGM power failure 376
Removal of PGM from IOTA 377
Mismatch of the PROFIBUS device and the master addresses 377
ExperionLXPlantCruiseExperion PKS server switchover 377
Fault Classifications 377
Initial checks 379
Checking Control Builder error code reference 379
Viewing flash log 380
Viewing release information log 380
Checking server point build log 380
Checking server point build error log 380
Checking error log 381
Using CTool to capture diagnostic data 381
Fixing common problems 381
Loss of communication with the devices when a switchover is
initiated 381
Loss of connection to some of the field network PROFIBUS
devices 382
Loss of power 383
Power-On Self Test (POST) does not complete 383
PGM display indicates -bp- or -ts- 384
One or both FTE LEDs are RED 385
FTE receive fault diagnostic 385

16
 PGM does not synchronize with backup 387
Fatal ECC error 388
Display shows FAIL 388
Isolated (lonely) Node 389
Duplicate Device Index setting 390
Device Index value is zero upon power up 390
Getting further assistance 391
Other troubleshooting sources 391
Guidelines for requesting support 394

Notices 395

17
18
CHAPTER

1 ABOUT THIS GUIDE

This guide provides information that will assist you in planning

and designing activities as well as installation, configuration,
operation and troubleshooting of the Profibus Gateway Module
(PGM).
This guide:
n Introduces the various blocks of the PGM.
n Describes how to create and configure the PGM blocks.
n Provides information on monitoring and troubleshooting the
PGM blocks.

ATTENTION: This document is structured such that

complete information related to a block is available in one
chapter. For example, the PROFIBUS I/O Module (PIOMB)
Function Block chapter contains the following information
related to PIOMB block:

Revision history
Revision Date Description

A March Initial release of the document.

2024

B June Added Note in About the Signal

2025 Configuration page

19
CHAPTER

2 PROFIBUS GATEWAY MODULE (PGM)

OVERVIEW

In this section:

PROFIBUS Communication Profiles 21

PROFIBUS DP Overview 22
PROFIBUS PA Overview 22
PROFIBUS network time synchronization support 22
DPV1 alarm support 22
Overview of PGM components 23
About DPV1 and HART enhancements for PGM 24
PGM topology 25
PGM data flow diagram 27
Data communication in PGM 28

20
Chapter 2 - PROFIBUS Gateway Module (PGM) Overview

The PROFIBUS Gateway Module is an interface module that

can be used with C300/UOC/HCA Controller to connect and
communicate with the Profibus devices. The PGM is developed
in the Series 8C form factor for use with the C300/UOC/HCA
Controller. The PGM module is an FTE resident module.
As a PROFIBUS gateway, PGM is always a master and
communicates with the PROFIBUS compatible PROFIBUS
devices.
The PGM supports the following functions.
n Redundancy
n Experion Events and alarms
n Experion Bulk Build utility
n Experion Import/export functionality
n Qualification and Version Control
n Peer-to-peer communications

ATTENTION: The PGM does not retain RAM across power

failure using a battery backed RAM. However, it does retain
its configuration in Flash and can resume normal operation
upon power up.

Table 2-1: Profibus supported Controllers

Communication Protocol Supported Controllers

Profibus communication via C300, UOC and HCA (Control

PGM. HIVE)

PROFIBUS Communication Profiles

The following information is extracted from the PROFIBUS
Technical Description describing the PROFIBUS DP
communication profile as defined by the PROFIBUS Standard
Definition (EN 50170):
PROFIBUS DP - Decentralized Periphery (DP) is the most
frequently used PROFIBUS communication profile. It is
optimized for speed, efficiency and low connection costs and is

21
 Chapter 2 - PROFIBUS Gateway Module (PGM) Overview

designed especially for communication between automation

systems and distributed peripherals.

PROFIBUS DP Overview
PROFIBUS DP is a master/responder, token passing network,
which utilizes a request/response protocol. Basic data
exchange operations ensure that on a periodic basis, the
master sends an output message to each PROFIBUS device,
which responds in turn with an input message. PROFIBUS DP
is typically used as an I/O network. As compared to a traditional
I/O network architecture that requires dedicated wiring
between each I/O module and the controller device, PROFIBUS
offers the advantage of a single network/bus on which all I/O
peripheral devices reside.

PROFIBUS PA Overview
PROFIBUS-PA is one of three PROFIBUS variants that are
compatible with each other. PROFIBUS PA is available for
applications in process automation with a demand for bus
power and intrinsically safe devices. PROFIBUS PA is linked to
the DP network with a coupler module. PROFIBUS PA supports
the tree or line structures and any combination of these two
network topologies.

PROFIBUS network time synchronization

support
Time synchronization functionality provides support for
synchronizing the time interval between the responder and the
master according to the PROFIBUS specification.

DPV1 alarm support

PGM supports device-specific alarms, status, and diagnostics
(DPV1) according to the PROFIBUS DPV1 specification. The
alarms are reported in the Experion Station.

22
Chapter 2 - PROFIBUS Gateway Module (PGM) Overview

Overview of PGM components

This section provides a brief overview of the major components
of the PGM.
n Field Network Application (FNAPP) - The PGM does not
contain a basic execution block. However, it utilizes a set of
services called the Field Network Application (FNAPP) to
support the data access to and execution of control objects.
The main control objects of the PGM are the Protocol Blocks
(PB) and the Device Support Blocks (DSB). Each PB and
DSB block is characterized by a set of parameters and an
algorithm. The execution of these blocks are based on event
sequences (faster response). The FNAPP is periodically
triggered to consume data from the C300/UOC/HCA and
provide data to the C300/UOC/HCA.
n Device Support Block (DSB): The Device Support Block
represents one of the PROFIBUS field devices (PROFIBUS
devices) in the PROFIBUS network. A single PROFIBUS
network can support up to 124 PROFIBUS devices. A single
DSB can support up to 16 PDCs.
n Protocol Block (PBLINK): The Protocol Block represents one
of the field network interfaces. The Protocol Blocks are
automatically created when a PGM block is created.
n Process Data Access (PDA) - PGM utilizes the PDA protocol
for process data transfer between the C300/UOC/HCA
Controller and the PROFIBUS devices over the PROFIBUS
network. The main purpose of using PDA is for fast I/O
protocol data transfer that provides optimized peer-to-peer
communications between the PGM and the
C300/UOC/HCA Controller over FTE. The number of
supported PDA connections is increased from 1 to 5.
n Process Data Collection (PDC) - A data structure that can
store and map several input or output process data items
(channels) from a given PROFIBUS device to one or more
PIOMB blocks in the C300/UOC/HCA Controller. The
PIOMB then presents data to control blocks in the CEE
through a set of channels." For example, in Siemens
ET200M I/O rack, one PDC holds all real-time process data
of one input or output I/O module. An I/O module that has
both inputs and outputs has two PDCs. In PGM, each PDC
represents a unique I/O module. However, if an I/O module

23
 Chapter 2 - PROFIBUS Gateway Module (PGM) Overview

is a mixed module (input and output module), then the

module is represented by more than one two PDCs.
n PROFIBUS HART I/O Module Block (PBHIOMB) – This block
is used for supporting HART over PROFIBUS profile. This
block represent a HART IOM in the Remote Input/Output
(RIO) responder and enables you to configure the HART
devices.
n PROFIBUS HART Channel Block (PBHCHANNEL) – This
channel block is used for supporting HART configuration
and monitoring. Therefore, the CMD48 data can be
monitored and used for generating alarms and events in
Experion system.
n DPV1 alarm support – Device Support Blocks (DSB) are
enhanced to configure and report DPV1 alarms in the
station.
n Time synchronization – This functionality enables to
synchronize the time interval between the responder and
the master.

About DPV1 and HART enhancements for PGM

DPV1
PROFIBUS-DPV1 supports acyclic data communication
between master and responders for the standard functions of
PROFIBUS-DP. A Class1 master (PGM) controls the cyclic
exchange of process data with the responders. Using the
acyclic communication functions, (PROFIBUS-DPV1) PGM now
supports acyclic data communication to the responders in
addition to the cyclic process data.
Acyclic data transfer exists wherever PROFIBUS devices provide
several parameterization options during operation. Typically,
the parameters of a device such as limit values, rotational
speed or torque, operation mode, generation of an error list,
and generating alarms, are parameterized during operation.

24
Chapter 2 - PROFIBUS Gateway Module (PGM) Overview

HART enhancements
PGM is enhanced to support HART over PROFIBUS profile. The
PBHIOMB represents a HART IOM in RIO responder and it is
associated to a PDC in the DSB, which is connected to the
Protocol block.

PGM topology
The following figure depicts the non-redundant PGM topology.

25
 Chapter 2 - PROFIBUS Gateway Module (PGM) Overview

The following figure depicts the non-redundant PGM-

PROFIBUS topology.
g src="../../_Images/HTS_Images/profibus_gtwy_mod_
ug/PGM_PROFIBUS_topology_non_redundant_New.png"
style="width:400px;height:228px;" />
The following figure depicts the redundant PGM topology.

26
Chapter 2 - PROFIBUS Gateway Module (PGM) Overview

The following figure depicts the redundant PGM-PROFIBUS

topology.

ATTENTION: The wiring diagrams provided in the PGM

architecture and topology section is used for illustration
purposes only and is not the recommended way of
PROFIBUS cabling.

PGM data flow diagram

The following figure depicts the data flow through the various
components and blocks in the PGM architecture.

27
 Chapter 2 - PROFIBUS Gateway Module (PGM) Overview

Data communication in PGM

The following block diagram depicts the various data
communication between the C300/UOC/HCA Controller, PGM,
PROFIBUS devices and the HART modules.
Data communication between C300/UOC/HCA Controller,
PGM, PROFIBUS devices and the HART modules

28
Chapter 2 - PROFIBUS Gateway Module (PGM) Overview

29
CHAPTER

3 PROFIBUS GATEWAY MODULE (PGM)

PLANNING AND DESIGN

In this section:

Review ExperionLXPlantCruiseExperion PKS system

capabilities 31

30
Chapter 3 - PROFIBUS Gateway Module (PGM) Planning and Design

The following sections provide information regarding the

guides that you can refer in the User Assistance library for a
brief overview of the Series 8C control hardware, PGM model
details, and PGM performance data.
For more information on the PROFIBUS technology, you must
refer to the PROFIBUS website.
For more information on the PROFIBUS devices, you must refer
to the vendor-specific manuals.

Review ExperionLXPlantCruiseExperion PKS

system capabilities
Read the Overview document to understand the basic concepts
and terminology, and appreciate the capabilities
ofExperionLXPlantCruiseExperion PKS.
Complement the information in this document with the data in
the Server and Client Planning Guide to cover all aspects of
anExperionLXPlantCruiseExperion PKS installation.
Refer to the Server and Client Planning Guide for planning and
design topics for ExperionLXPlantCruiseExperion PKS servers
and clients as well as information about adding third-party
controllers.
Refer to the Control Hardware Planning Guide for a general
discussion of planning activities for
ExperionLXPlantCruiseExperion PKS control hardware that
covers the following:
n Initial planning and design
n Control network considerations
n Control hardware configuration
n Site selection and planning
n Control processing considerations
n Application licensing considerations
Refer to the PROFIBUS Interface Implementation Guide to
understand the basic concepts and terminologies of
PROFIBUS.

31
 Chapter 3 - PROFIBUS Gateway Module (PGM) Planning and Design

Refer to the CEAG Remote I/O Modules and Easy-COM

LB8106/FB8206 Instruction Manual for more information on
the CEAG remote I/O modules.

32
CHAPTER

4 PROFIBUS GATEWAY MODULE (PGM)

INSTALLATION

In this section:

Pre-installation considerations 34
PGM assembly 34
PGM IOTA pinouts 35
Installing a PGM 39
PGM power-on and startup 41
Profibus cabling guidelines 42

33
Chapter 4 - PROFIBUS Gateway Module (PGM) Installation

Pre-installation considerations
Installation declarations

ATTENTION: This equipment shall be installed in

accordance with the requirements of the National Electrical
Code (NEC), ANSI/NFPA 70, or the Canadian Electrical
Code (CEC), C22.1. It is intended to be mounted within an
enclosure or suitable environment acceptable to the local
"authority having jurisdiction," as defined in the NEC, or
"authorized person" as defined in the CEC.

Unless the location is known to be non-hazardous, do not

connect or disconnect cables while the control system is
powered.

TIP:
Refer to the Planning Your Series 8 Control System
section in the for details.

PGM assembly
The PROFIBUS Gateway Module consists of an Input/Output
Terminal Assembly (IOTA) board and the PGM module which is
housed within a plastic cover and is mounted onto the IOTA
board. The PGM assembly is installed in a control cabinet on
vertically-mounted channels specifically for Series 8C control
hardware. The following table provides information on the PGM
IOTA board.

PGM IOTA
Description
Board

F1 Fuse (0.8A/250V Type F).

PROFIBUS 1 Connectors to the PROFIBUS network.

PROFIBUS
2

FTEA, FTEB Fault Tolerant Ethernet (FTE) network connectors.

FTE A network cable connectors are yellow. FTE B

34
 Chapter 4 - PROFIBUS Gateway Module (PGM) Installation

PGM IOTA
Description
Board

network cable connectors are green.

FTE DEVICE Three rotary decimal switches used to set the FTE
INDEX 100, network address (Device Index) of the PGM.
10, 1

PB Link A Connectors to PB Link cables for PGM power and

PB Link B grounding connection.
l PB Link A cable connectors are green.
l PB Link B cable connectors are yellow.

n CF9 control firewall - 9-port control firewall (CF9)

CF9 control firewall - 9-port control firewall (CF9)

In the control cabinet, Control Firewall assemblies (CF9)
provide connection of control hardware (PGM and C300
Controllers) to the FTE network. STP CAT5 cables connect the
FTE-capable control hardware to the Control Firewall IOTA. Two
Control Firewall assemblies are required to provide network
redundancy, (one CF9 supports the FTE "A" segment and the
second supports FTE "B" segment). Eight ports on each control
firewall provide connection for up to eight FTE nodes. A 9th
port provides an uplink to the supervisory FTE network and
level 2 control.
See the Control Firewall User's Guide for details about the
Control Firewall installation.

PGM IOTA pinouts

The following figure illustrates the pinout diagram of the
PGM/IOTA DB9-F connector.

35
Chapter 4 - PROFIBUS Gateway Module (PGM) Installation

The following table lists the PROFIBUS DB9-F Pin and signal
definitions.

Pin
Signal Description
Number

Shell Shield Shield, Protective Ground

1 Shield Shield, Protective Ground (not

recommended – see note)

2 -- Not Connected

3 RxD/TxD-P Receive/Transmit data – plus (B wire, red

color)

4 CNTR-P Repeater control signal (direction

control), RTS signal

5 DGND Data ground (reference potential for VP)

*

6 VP Voltage - plus (P5V), +5V *

7 -- Not Connected

8 RxD/TxD-N Receive/Transmit data – minus (A wire,

green color)

9 -- Not Connected

36
 Chapter 4 - PROFIBUS Gateway Module (PGM) Installation

NOTE:
Only the signals shown in the above figure and table are
available for PGM. Others are not connected.
The metallic shell shall be used as the primary shield and
protective ground connection as it provides the best EMI
mitigation.
Pin 1 is provided for compatibility with older systems that
use this pin as a shield connection point.
* VP (+5V) and DGND are primarily used for external bus
termination. Some devices such as electrical to fiber optic
repeaters might require external power from these pins (not
to exceed 35 mA). CNTR-P (repeater control) is used in
some equipment to determine the direction of
transmission/reception.

PROFIBUS DP Master LED behavior

The following tables describe the behavior of the LEDs located
adjacent to the PROFIBUS 1 and PROFIBUS 2 DB9 connectors
on the PGM IOTA (CC-TPOX01). The behavior of the LEDs
depends on whether the PGM acting as a primary or acting as a
secondary.

LED behavior for primary PGM

Table 4-1: LED Behavior for primary PGM

State Color LED Indication Description

1 Green Flashing acyclic (four 100 PGM is in NO DB.

ms flashes followed by
approximately 3 seconds
OFF, then repeat)

2 Green Flashing cyclic PGM's network

configuration
load is in
progress.

37
Chapter 4 - PROFIBUS Gateway Module (PGM) Installation

State Color LED Indication Description

3 Green Flashing cyclic Communication

with at least one
responder is lost.

4 Green ON Communication
with all
responders is
established.

5 None OFF Communication

to all responders
is lost.

ATTENTION: State 2 and State 3 result in the same LED

indication.

LED behavior for secondary PGM

Table 4-2: LED Behavior for secondary PGM

State Color LED Indication Description

1 Green Flashing acyclic (four PGM is not

100 ms flashes synchronized with its
followed by partner.
approximately 3
seconds OFF, then
repeat)

2 Green Flashing cyclic PROFIBUS network

configuration
synchronization is in
progress.

3 Green ON This is the default run

state for the PGM
acting as secondary.

4 None OFF This is the default

state at power up, and

38
 Chapter 4 - PROFIBUS Gateway Module (PGM) Installation

State Color LED Indication Description

then transitions to
State 1. Refer to
Attention

ATTENTION: Both LEDs OFF: This situation persists only

for a short time after power cycle. Thereafter, LEDs
transitions to State 1.

Installing a PGM
Prerequisites
Before you install the PGM you should have:
n A control cabinet installed with appropriate channel
hardware for mounting the Series 8C control hardware.
n A Series 8C power supply Header Board hardware installed
in the cabinet.
n Installed pair of Control Firewall (CF9) assemblies.
n The PGM assembly (PGM module with IOTA board and
mounting hardware). In addition, you need the necessary
parts for installing PGM to the control system. See Series 8C
System Cabling in the Control Hardware Planning Guide for
cable hardware details.
n Ensure the cabinet enclosure is connected to a protective
earth ground using #8 AWG solid copper wire. There should
be metal to metal contact between the grounding bus bar
and the enclosure as well as the channel.

Perform the following steps to install a PGM

1. Refer to appropriate site location drawings for the specified
installation location, PGM Device Index (FTE address), and
wiring diagrams.
2. Identify the mounting location on channel and align
mounting holes in IOTA with screw hole locations on the
channel.

39
Chapter 4 - PROFIBUS Gateway Module (PGM) Installation

3. Assemble mounting screws, washers and spacers provided.

Insert spacers and washers between backside of IOTA and
front of channel. Ensure that the component side of the
IOTA is facing up.
Do not fully tighten the IOTA mounting screws before
installing and tightening the power and ground screws (24V
and COM terminals) which can bind during installation or
removal. Follow instructions carefully.
4. Position the assembled IOTA board at the proper mounting
location.
5. Thread the four mounting screws only half-way to attach the
IOTA board to the channel.
6. Tighten the mounting screws securing the IOTA board to the
channel.
7. Connect FTE-A and FTE-B Ethernet link cables to the RJ-45
connectors on PGM IOTA board.
l The yellow Cat5 cable must connect to the FTEA
connector on the IOTA.
l The green Cat5 cable must connect to the FTEB
connector on the IOTA.
8. Route the FTE cables to the appropriate Control Firewall
module location.
l The Yellow FTE cable is routed to the Control Firewall that

supports FTE-A.
l The Green FTE cable is routed to the Control Firewall that

supports FTE-B.
9. Connect PBLink1 and PBLink2 cables to the IOTA board.
10. Set the Device Index (FTE DEVICE INDEX) of the PGM
according to the site documentation by turning the three
rotary decimal switches located on the IOTA board. Set the
switches to the three digit address ranging from 001 to 509.
The left-most switch (100) is used to set the hundreds digit.
The middle switch (10) is used to set the tens digit and the
right-most switch (1) sets the ones digit. The FTE device
index setting on the switches should match the Device Index
number entered on the PGM block's Main tab configuration
form.
11. Insert the PGM module onto IOTA board making sure that
the PGM circuit board is aligned properly with the IOTA

40
 Chapter 4 - PROFIBUS Gateway Module (PGM) Installation

board connector. Secure the PGM module to the IOTA board

with two screws located at each side of the plastic cover.
12. Using a #2 Phillips screwdriver, tighten the plastic screw on
the front of the module cover. Be careful not to strip the
plastic screw head.

PGM power-on and startup

PGM Startup
The PGM startup is identical to the C300/UOC/HCA Controller
startup.

TIP:
For detailed information on startup, refer to the
C300/UOC/HCA Controller Startup section in the .

PGM front panel and LED display

The PGM faceplate indicators/displays are identical to the
C300 controller faceplate indicators/displays. The front panel
of the PGM has four LEDs. The module also has a four-
character display that indicates the state of the module.
The following figure displays the bus powered PGM.

41
Chapter 4 - PROFIBUS Gateway Module (PGM) Installation

TIP:
For detailed information on faceplate indicators/displays,
refer to the C300 faceplate display section.

Profibus cabling guidelines

This section provides guidelines on possible ways to extend
PGM redundancy to support Profibus media redundancy. Note
that these illustrations are provided for references purposes
only. You must refer to vendor documentation for actual design
rules and placement/use of network components and
terminators.

Copper cable-based media redundancy

The following diagram illustrates the copper cable-based
PROFIBUS topology. In this topology, DP cable A and DP cable
B are the redundant backbone network. To this network, the
switch responder supporting media redundancy can be directly
connected. This network can have non-redundant segment like
the ones on the left side of the diagram or DP Net-1 and DP
Net-2 where redundant PGMs are connected through RLM
modules.

42
 Chapter 4 - PROFIBUS Gateway Module (PGM) Installation

ATTENTION: Use external active terminators in copper

segments where PGM is connected.

Fiber-optic cabling-based media redundancy

The following diagram illustrates the fiber-optic cabling-based
media redundancy. In this topology, the redundant backbone is
the optical cable based redundant ring where redundant or
non-redundant segment are connected through OLM modules.

43
Chapter 4 - PROFIBUS Gateway Module (PGM) Installation

ATTENTION: Use external active terminators in copper

segments where PGM is connected.

Redundant PGM in a non-redundant Profibus cabling

The following diagram illustrates a topology of a redundant
PGM in a non-redundant Profibus cabling scenario.

44
 Chapter 4 - PROFIBUS Gateway Module (PGM) Installation

ATTENTION: Terminators are very important for copper

segments. All copper segments may not need external
terminators. Only the segments that contain PGM need
external active termination.

Avoid using diagnostic LED PROFIBUS connector and enabling

termination in the plug connected to PGM.

45
CHAPTER

5 PROFIBUS GATEWAY MODULE (PGM)

BLOCK

In this section:

PGM overview 47
Configuring a PGM 48
Configuring a secondary PGM 49
Converting a redundant PGM to a non-redundant PGM 49
Monitoring PGM block 50
PGM redundancy-specific operations 58
PGM shutdown operations 67
PGM block station displays 69

46
Chapter 5 - PROFIBUS Gateway Module (PGM) Block

PGM overview
The PGM is an interface module that can be used with the
C300/UOC/HCA Controller to connect and communicate with
the Profibus devices. You can assign a maximum of four PGMs
to a C300/UOC/HCA Controller. The PGM has a set of function
blocks to represent the complete PROFIBUS Gateway Module.
The following are the FBs associated with the PGM.
n PGM
n Protocol Blocks
n DSB
n PIOMB
n PROFIBUS HART Input/Output Module (PBHIOM) Block
n PROFIBUS I/O channel blocks
n PROFIBUS HART I/O channel blocks
When a PGM block is created, two Protocol Blocks are
automatically created. The PGM block can be configured as
redundant/non-redundant from the Main tab of the PGM FB’s
configuration form in the Control Builder.

PGM redundancy support

When a PGM is configured as redundant, only the primary PGM
exchanges data with the PROFIBUS devices. The secondary
PGM must be in the "Synchronized State."
The secondary PGM cannot determine the health of the
PROFIBUS network. The secondary PGM considers the network
as healthy if it has established a PROFIBUS communication
with the primary PGM . The secondary PGM does not
communicate with the PROFIBUS devices at all. The secondary
PGM only checks if a device with the configured master
address participates at token exchange (active and passive
PROFIBUS master exchange token between each other).

HART device support in PGM

PGM block supports a maximum of 512 HART (PBHCHANNEL)
device configurations (that is, 256 HART devices per PBLINK).
One PBHIOMB block supports a maximum of 16 HART
channels.

47
 Chapter 5 - PROFIBUS Gateway Module (PGM) Block

PGM block creation

A PGM block is created in the Control Builder from the file
menu (File > New > Interface Modules > Profibus Gateway Module
(2 Links) ) and assigned to the root.

PGM block deletion

A PGM block cannot be deleted from the Project view in Control
Builder unless all the contained blocks are deleted first.
You must first delete all the contained blocks from the
Monitoring view before deleting them from the Project view.

Configuring a PGM
Perform the following steps to configure a PGM
1. Choose File > New > Interface Modules > Profibus Gateway
Module (2 Links). The PGM block configuration form appears.
2. In the Tag Name box, type the name of the PGM (a maximum
of 40 characters) or accept the default.
3. In the Item Name box, type the item name.
4. In the Device Index box, type a valid device index number.
Use odd numbers for non-redundant and primary PGM
blocks. If you do not enter a valid device index number, an
error message appears when you close the configuration
form.
5. Check the Module is redundant check box if you want the
module to be one of a redundant pair. If you select the
check box, the secondary tag name appears in the
Redundancy Configuration box. The secondary PGM block is
added when the primary PGM block configuration form is
closed.
6. In the CPU Free Low Alarm box, type the value at which an
alarm is to be generated when the available CPU resources
fall less than this limit. Do not set the CPU Free Low Alarm
value lower than the default value of 20%.
7. Use the online help as a guide to complete the configuration
entries on the other tabs.

48
Chapter 5 - PROFIBUS Gateway Module (PGM) Block

8. Click OK. The PGM block with two Protocol Blocks are added
to the Project tree.

Configuring a secondary PGM

When a PGM is configured as redundant, the secondary PGM
block is added to the Project view automatically.

Perform the following steps to configure a secondary

PGM
1. In the Project view, right-click the secondary PGM block icon
and select Module Properties. The secondary PGM
configuration form appears.
2. In the Tag Name box, type the name of the secondary PGM
block (a maximum of 40 characters) or accept the default.
3. In the Item Name box, type the item name.
4. Use the online help as a guide to complete the configuration
entries on all other tabs.
5. Click OK.

Converting a redundant PGM to a non-

redundant PGM
You can convert a redundant PGM to a non-redundant PGM
on-process.

ATTENTION: Ensure that the current primary PGM is

physically configured with the odd Device Index. If not,
enable synchronization, wait for initial-sync to complete,
and manually command switchover.

Perform the following steps to convert a redundant

PGM to a non-redundant PGM
1. In the Monitoring view, double-click the secondary PGM.
The secondary PGM configuration form appears.
2. Click the Redundancy tab.

49
 Chapter 5 - PROFIBUS Gateway Module (PGM) Block

3. Click Disable Synchronization. Wait for the command to

complete. The synchronization between the primary and
secondary PGM terminates. A 'Not Synchronized' diagnostic
alarm is generated by both the primary and the secondary
PGM.
4. Delete the secondary PGM function block from the
Monitoring view.
5. Disconnect the redundancy cable from the primary PGM.
6. Remove the secondary PGM hardware by removing the PGM
module and its IOTA.
7. In the Project view, right-click the primary PGM and select
Module Properties. The primary PGM configuration form
appears.
8. Clear the Module is redundant check box.
9. Click OK. The secondary PGM icon is deleted from the
Project view. The primary PGM icon changes from a
redundant to a non-redundant icon.
10. Load the non-redundant PGM. The PGM icon in the
Monitoring view indicates that the PGM is now non-
redundant.

Monitoring PGM block

TIP:
In this section, the state and command parameters of the
PGM block are listed for quick reference. For detailed
information about these parameters, you need to refer to
the PROFIBUS Gateway Module Parameter Reference
guide.

PGM block state after configuration and load

After the PGM block is loaded, the Platform State (BCMSTATE)
must be OK.

PGM block status parameters

PGM State (BCMSTATE)

The BCMSTATE parameter displays the PGM platform state.

50
Chapter 5 - PROFIBUS Gateway Module (PGM) Block

Redundant Synchronization State (RDNSYNCSTATE)

The RDNSYNCSTATE parameter displays the current
synchronization state of the PGM.

Redundancy Role (RDNROLESTATE)

The RDNROLESTATE parameter indicates whether the module
is operating as a primary, secondary, or logically non-
redundant PGM.

PGM block command parameters

PGM Command (BCMCOMMAND)

The BCMCOMMAND parameter displays the PGM platform
command. In the PGM this command can assumes one value,
“SHUTDOWN.”

Enable Shutdown (ENABLESHUTDOWN)

The ENABLESHUTDOWN command can use used to shutdown
the PGM with the configured PROFIBUS devices that are on
control.

PGM PDA statistics parameters

The PDA Statistics tab is included in the PGM block’s
configuration form that displays the following information
when the PGM is communicating with the C300/UOC/HCA.
n Packets Sent Avg
n Packets Received Avg
n PDC Messages Avg
n Connection Statistics
l IP Address
l Connection Status
The number of supported PDA connections between the PGM
and the C300 (Compatibility with CC-PCNT01 / CC-PCNT02) is
5.
The number of supported PDA connections between the PGM
and the C300/HCA (Compatibility with CC-PCNT05) is 8.

51
 Chapter 5 - PROFIBUS Gateway Module (PGM) Block

The number of supported PDA connections between the PGM

and the UOC is 5.

Packets Sent Avg (PKTSTXAVG)

The PKTSTXAVG parameter is used for displaying the average
number of packets sent to the C300/UOC/HCA.

Packets Received Avg (PKTSRXAVG)

The PKTSRXAVG parameter is used for displaying the average
number of packets received from the C300/UOC/HCA.

PDC Messages Avg (PDCMSAVG)

The PDCMSAVG parameter is used for displaying the average
PDC messages sent in a packet.

IP Address (IPADDR [0..4])

The IPADDR [0..4] parameter is used for indicating the IP
address of the C300/UOC/HCA through which the PGM
communication occurs.

Connection Status (CONNSTATUS [0..4])

The CONNSTATUS [0..4] parameter is used for indicating the
connection status between the PGM and the C300/UOC/HCA.

PGM memory statistics parameters

The Memory tab is included in the PGM block’s configuration
form that displays the memory statistics information of the
PGM block.
The memory parameters are classified into four different
groups, namely:
n Memory Usage in KBytes
n Memory Usage in Bytes
n Memory Descriptors
n Memory Blocks

52
Chapter 5 - PROFIBUS Gateway Module (PGM) Block

Memory Usage (both in Bytes and KBytes)

The following parameters are used for displaying the usage of
PGM memory.
n Total User Memory In Bytes/Kbytes (TOTALMEMINK): Used for
indicating the PGM user memory pool in bytes/kbytes.
n Currently Used Memory (USEDMEMINK): Used for indicating
the total amount of used memory in the PGM user memory
pool. The difference between the total user memory and the
free memory is equal to the used memory.
n Currently Free Memory (FREEMEMINK): Used for indicating
amount of free memory currently available in the PGM user
memory pool.
n Largest Free Memory Block (MAXFREEINK): Used for indicating
the size of the largest adjacent memory in the PGM user
memory pool. The largest memory block is always less than
or equal to the current free memory block.
Some of the blocks loaded in PGM may require the large
blocks of contiguous memory.

Memory Descriptors
Memory Descriptors is a process address space with a data
structure that contains all the information related to the
process address space.
The following parameters are used for displaying the memory
descriptors.
n Total Memory Descriptors (NTOTMEMDESC): Used for
indicating the total number of memory descriptors. This is a
static number and the units are number of descriptors.
n Free Memory Descriptors (NUMFREEDESC): Used for indicating
the number of free or available memory descriptors.
n Registered Memory Descriptors (NUMREGDESC): Used for
indicating the number of registered descriptors. Generally,
this parameter is close or equal to zero since the descriptors
are registered when the connection is lost.
n Used Memory Descriptors (NUMUSEDDESC): Used for
indicating the number of used memory descriptors. This
parameter is equal to the difference between the total
memory descriptors and the free memory descriptors.

53
 Chapter 5 - PROFIBUS Gateway Module (PGM) Block

Memory Blocks
Memory Blocks, is a fixed-size blocks allocation, is the use of
pools for memory management that allows dynamic memory
allocation.
The following parameters are used for displaying the
information about the memory blocks.
n Used Memory Blocks (NUMUSEDBLKS): Used for indicating the
number of used memory blocks. The size of the memory
block may vary.
n Free Memory Blocks (NUMFREEBLKS): Used for indicating the
number of free memory blocks. Generally, only one free
memory block is available.
The memory is not partitioned into blocks until it is used.

PGM block icons

The following table summarizes the various appearances that a
PGM block can assume based on configuration, view, and
current operating state.

And Module
If icon is... Then it represents...
State is...

Project view

gray PGM is configured for non- N/A

redundant operation

PGM primary configured for N/A

redundant operation

gray/white

PGM secondary configured for N/A

redundant operation

white/gray

54
Chapter 5 - PROFIBUS Gateway Module (PGM) Block

And Module
If icon is... Then it represents...
State is...

Monitoring view

green PGM is non-redundant Run

Primary PGM is synchronized Run

green/white

Secondary PGM is synchronized Backup

white/green

Primary PGM is not synchronized Run

and partner PGM is visible

green/yellow

yellow PGM is non-redundant No

Database

Primary PGM is synchronized No

Database

yellow/shadow

Primary PGM is not synchronized No

and partner PGM is visible Database

yellow/yellow

55
 Chapter 5 - PROFIBUS Gateway Module (PGM) Block

And Module
If icon is... Then it represents...
State is...

red PGM is non-redundant and not Offnet

communicating

Primary PGM is not Offnet

communicating

red/white

Secondary PGM is not Offnet

communicating

white/red

PGM block diagnostic alarms

When active, the PGM block reports the following diagnostic
alarms.

ATTENTION: In a redundant PGM, if a PB Link failure

occurs in the secondary PGM, the secondary PGM does not
generate an alarm or an event. However, there is a
diagnostic that detects the absence of the primary master
on the field network and prohibits the synchronization. You
can also refer to the redundancy history for more details.

Alarm Description

Communication This alarm is reported when the connection

Error between the PGM and PROFIBUS devices is
broken. The following are the probable causes
for generation of this alarm.
l Power is disrupted to the IOTA in which the
PGM resides.

56
Chapter 5 - PROFIBUS Gateway Module (PGM) Block

Alarm Description

l The PGM is removed under power.

l The FTE cables are removed from the IOTA.

Not Synchronized This alarm is reported when the primary and

secondary PGM are not synchronized or not in
standby. The "Not Synchronized" alarm returns
to normal upon configuring the primary at the
odd device Index or upon entering the
Synchronized or Standby state.

Unexpected This alarm is reported when the PGM is

Partner on explicitly configured as non-redundant and a
Redundancy Link partner is present on the redundancy private
path. The RDNSYNCSTATE parameter is set to
either PARTNERVISBL or INCOMPATIBLE. This
alarm returns to normal after the PGM is re-
configured as redundant or if the partner is
removed from the redundancy link.

Device Index This alarm is reported when the device index

Switches of the PGM is changed when it is up and
Changed running. In such a scenario, the PGM retains
the device index value assumed at start up.
The alarm returns to normal after the device
index is changed to its original number. Note:
Changing the device index number does not
affect the control strategies and there is no
loss of data. However, a soft fail is generated. If
the PGM is powered off and on, the PGM
clears it memory database and also clears the
device index value.

Duplicate Device This alarm is reported when the device index

Index alarm of the secondary PGM is identical to the device
index of another node.

FTE A/B cable This alarm is reported when one of the FTE
Fault Alarm cables (FTE-A/FTE-B) is removed or is faulty.
This alarm returns to normal when the FTE
cable is reconnected. In such a scenario, PGM
will be up and running. Also, the control

57
 Chapter 5 - PROFIBUS Gateway Module (PGM) Block

Alarm Description

strategies do not lose the data from the PGM.

Note that the PGM can operate with a single
FTE.

OFFNET This alarm is reported when both the FTE

cables are removed. In such a scenario, there
is a loss of view of the PGM block. The control
strategies lose data from the PGM. This alarm
returns to normal if one of the FTE cables is
re-connected. When re-connected, the control
strategies start receiving data from the PGM.

Temperature This alarm is reported when the temperature

High Alarm high alarm set point value reaches lower than
the specified set point.

PGM redundancy-specific operations

TIP:
For complete information on the Redundancy
functionality, refer to the following documents.

l Control Builder Components Theory -> Controller

Redundancy Functionality
l C300 Controller User's Guide -> C300 Redundancy
Operation

About switchover
A switchover is triggered immediately upon the detection of a
fault in the primary or upon the receipt of an operator
command.
Depending on the switchover trigger, the original primary PGM
attempts to reboot into the secondary role, but this PGM
cannot immediately participate in another switchover
operation. After the new secondary reboots into the secondary
role, it must first perform and complete initial-synchronization
before another switchover is allowed.

58
Chapter 5 - PROFIBUS Gateway Module (PGM) Block

During the switchover time, the PROFIBUS devices lose

connection to the master. However, the behavior of the
PROFIBUS devices during a switchover depends on their
configuration. For most of the devices, you can configure a
time during which they hold their outputs. However, there are
devices that lose their outputs immediately. Therefore, from a
PGM redundancy standpoint, selection of the I/Os plays a vital
role.

Conditions that result in a switchover

The following conditions result in a switchover.
n Issuing a Switchover command.
n Issuing a Shutdown command on the primary PGM.
n Both FTE cables removed from the primary PGM.
n The primary PGM is removed from the IOTA.
n The primary PGM is restarted.
n The primary PGM is failed.
n The PROFIBUS cable is disconnected from the primary
PGM.

Conditions that do not result in a switchover

The following conditions do not result in a switchover.
n Redundancy cable between the primary and the secondary
PGM is disconnected or broken.
n Both FTE links to the secondary PGM are lost.
n Loss of power to the secondary PGM.
n Failure of the secondary PGM.
n Removal of the secondary PGM module from its IOTA.
n Inserting a different PGM module into a powered secondary
IOTA.
n If the PGM is provided with a single FTE link and that link is
disconnected or broken.

Conditions that result in loss of synchronization

The following conditions result in loss of synchronization in a
synchronized or standby redundant PGM pair.

59
 Chapter 5 - PROFIBUS Gateway Module (PGM) Block

n Issuing the Disable Sync command (from the primary or the

secondary platform FB).
n Redundancy cable between the primary and the secondary
PGM is lost.
n Loss of input power to the secondary PGM.
n Failure of the secondary PGM.
n Removal of the powered secondary PGM from its IOTA.
n Removal of PROFIBUS network cable from the secondary
PGM.

TIP:
When the single FTE link to the primary and/or secondary
PGM is disconnected, this does not result in loss of
synchronization.

PGM Redundancy tab in Monitoring view

After the PGM configured as redundant is loaded, the
Redundancy tab must provide the following statistics.
n Auto Synchronization State (RDNAUTOSYNC)
n Redundancy Compatibility (RDNCMPT)
n Inhibit Sync Reason (RDNINHIBITSYNC)
n Initial Sync Progress (RDNSYNCPROG)
n Last Synchronization Time (SYNCTIMEBEG)
n Last Loss of Sync Time (SYNCTIMEEND)
n Redundancy Controllability (RDNCTLABILITY)
n Device Index (RDNDEVICEIDX)
n Redundancy Traffic bytes/sec (RDNXFERAVG)
n Max Redun. Traffic bytes/sec (RDNXFERMAX)
n Redundancy Delay (RDNDELAYAVG)
n Maximum Redundancy Delay (RDNDELAYMAX)
n Max Initial Sync Time (RDNISTIMEMAX)
n Max Switchover Time (RDNSOTIMEMAX)

60
Chapter 5 - PROFIBUS Gateway Module (PGM) Block

Enabling Synchronization
Use the following procedure to initiate a synchronization
command manually to a redundant PGM pair.

TIP:
You can view the active PGM pair in the Monitoring view
in the Control Builder.

Perform the following steps to enable synchronization

1. In the Monitoring view, double-click the primary PGM icon.
The PGM block configuration form appears.
2. Click the Redundancy tab.
3. Click Enable Synchronization.
4. Click Yes to confirm the action and issue the synchronize
command. Confirm that the Auto Synchronization State
becomes ENABLED.
5. Click OK.

Disabling Synchronization
Use the following procedure to disable synchronization
manually to a redundant PGM pair.

TIP:
You can view the active redundant PGM pair in the
Monitoring view in the Control Builder.

Prerequisites
The primary and secondary modules are synchronizing,
synchronized, or in standby state.

Perform the following steps to disable synchronization

1. In the Monitoring view, double-click the primary PGM icon.
The PGM block configuration form appears.
2. Click the Redundancy tab.
3. Click Disable Synchronization.

61
 Chapter 5 - PROFIBUS Gateway Module (PGM) Block

4. Click Yes to confirm the action and issue the Disable

Synchronization command. Confirm that the Auto
Synchronization State becomes DISABLED.
5. Click OK.

Configuring the network for switchover

During the PGM switchover, there is a brief absence of master.
The behavior of the PROFIBUS devices during the switchover is
up to the PROFIBUS device configuration. For most of the
PROFIBUS devices, you can configure a time during which they
keep their outputs. However, some devices lose their outputs
immediately.
Therefore, the PROFIBUS field network must be configured to
tolerate this brief absence of the master during switchover. If
this configuration is not performed, the device outputs can
drop.

ATTENTION: While configuring the network for switchover,

DPV1 must be disabled from all PROFIBUS devices.

Perform the following steps to configure the network for

switchover
1. Navigate to the Field Network Configurationtab of the Protocol
Block in which you have configured the PROFIBUS device
and the master.
2. Double-click the master. You can also right-click the master
in the Network view and select Configuration. The
configuration window appears. The Device Assignmentmenu
in the Navigation Areais selected by default.
3. Click the Bus Parameters menu in the Navigation Area. The
Bus Parameters details appear in the right pane. The Bus
Parameters details contain the main setup values of the

62
Chapter 5 - PROFIBUS Gateway Module (PGM) Block

PROFIBUS network.

4. Type the value 6000 in the Data Control Timebox.

5. Select the Override slave specific Watchdog Control Time check
box.
6. Type the value 1000 in the Watchdog Control Timebox. The
Watchdog control time and Data control time must have
proper values based on the number of PROFIBUS devices
configured in the network and the bus speed. In addition, V1
communication has a major impact on the watchdog data
control time values . If DP-V1 is enabled for a PROFIBUS
device, the Watchdog control time and Data control times
must be about three times longer than the actual time when
DP-V1 is disabled.
7. Click Apply.
8. Click OK.

63
 Chapter 5 - PROFIBUS Gateway Module (PGM) Block

9. Click Save in the Field Network Configuration tab toolbar. A

message appears after you save the configuration. When
you click Save,

10. Click OK.

11. Click OK to close the Field Network Configuration form. The
field network configuration is saved to the ERDB. If you click
Cancel and close the configuration form, the configuration
is not saved to the ERDB even if you have clicked Save on
the Field Network Configuration tab toolbar

64
Chapter 5 - PROFIBUS Gateway Module (PGM) Block

12. Reload the Protocol Block.

Enabling a secondary PGM to become a primary PGM

in the absence of a partner module
You can use the "Become Primary" command to cause an
unsynchronized secondary module to transition into the
primary role in the absence of a partner module. This command
is applicable only if the unsynchronized secondary has no view
to a partner module across the redundancy cable and the
primary IP address is not occupied.

TIP:
You can view the active redundant PGM pair in the
Monitoring view.

Perform the following steps to enable a secondary PGM to

become a primary PGM in the absence of a partner module
1. In the Monitoring view, double-click the primary PGM icon.
The PGM block configuration form appears.
2. Click the Redundancy tab.
3. Click Become Primary.
4. Click Yes to confirm the action. Confirm that the secondary
module assumes the primary role. The old primary module

65
 Chapter 5 - PROFIBUS Gateway Module (PGM) Block

should boot up in the backup role.

5. Click OK.

Performing a manual switchover

You can use the "Initiate Switchover" command to manually
initiate a switchover to a redundant PGM pair.

TIP:
You can view the active redundant PGM pair in the
Monitoring view.

Prerequisites
The primary and secondary modules are synchronized.

Perform the following steps to perform a manual switchover

1. In the Monitoring view, double-click the primary PGM icon.
The PGM block configuration form appears.
2. Click the Redundancy tab.
3. Click Initiate Switchover.
4. Click Yes to confirm the action. Confirm that the secondary
module assumes the primary role.
5. Click OK.

PGM redundancy notifications

The following table lists the redundancy-related notifications
implemented for the PGM that may occur during controller
synchronization and switchover operations.

Notification Generated when…

Backup State The secondary PGM is successfully restarted.

Redun The redundancy cable of the primary PGM is

Incompatible connected to a different PGM.
Partner

Redun No Both the primary and the secondary PGM

Partner generate this notification when the partner is not

66
Chapter 5 - PROFIBUS Gateway Module (PGM) Block

Notification Generated when…

present.

Redun Non- Both FTE cables of the PGM configured explicitly

Redundant as non-redundant are removed and re-connected
after sometime.

Redun Partner Both FTE cables of the secondary PGM are

Visible on FTE removed and re-connected after sometime.

Redun Partner Both the primary and the secondary PGM

Visible on generate this notification upon detecting a
Redun Link compatible partner visible across the redundancy
private path.

Redun Sync In Both the primary and the secondary PGM

Progress generate this notification after both FTE cables
are removed and re-connected and the initial
synchronization is started.

Redun Sync Both the primary and the secondary PGM

Maintenance generate this notification after completing the
initial synchronization.

Redundancy This notification is generated when the

Link Active redundancy link cable is connected.

Redundancy This notification is generated when the

Link Inactive redundancy link cable is disconnected.

Switchover Both the primary and the secondary PGM

generate this notification when a switchover is
initiated by entering the switchover command.

PGM shutdown operations

Initiating a PGM shutdown
Use the following procedure to initiate a shutdown command to
the PGM, which results in the PGM rebooting to its RDY state
or boot firmware.

67
 Chapter 5 - PROFIBUS Gateway Module (PGM) Block

In a redundant-pair, when you shutdown the primary PGM, the

secondary PGM automatically assumes the role of the primary,
if the pair is synchronized.

ATTENTION: Shutting down the PGM, interrupts the

transfer of data to the ExperionLXPlantCruiseExperion PKS
system. Caution MUST be exercised when performing a
PGM SHUTDOWN as it may result in a loss of control.

Perform the following steps to initiate a PGM shutdown

1. Double-click the PGM in the Monitoring view. The PGM
Block Configuration form appears.
2. In the Main tab, click Shutdown in the Controller Command list.
To shutdown the primary PGM, you must select the Enable
Shutdown check box. This parameter enables you to
shutdown the PGM along with the configured PROFIBUS
devices that are on control.

TIP: In a redundant pair, when the primary PGM FB is

shutdown, the secondary PGM assumes the role of the
primary. You can monitor this change by observing the
following parameters on the tab of the new primary
PGM.
l After the secondary assumes the role of the primary,

its IP address (IPADDRESS) changes to that of the

old primary.
l The Redundancy Role State (RDNROLESTATE) of

the new primary changes to "PRIMARY" from

"SECONDARY."
l The Redundancy Synchronization State

(RDNSYNCSTATE) of the new primary transitions to

"PARTNERVISBL."
l The CPMSTATE of the new primary transitions from

"BACKUP" to "IDLE" or "RUN" as appropriate.

3. Click Yes to confirm the action. Wait for the PGM to reboot
to its RDY state.

68
Chapter 5 - PROFIBUS Gateway Module (PGM) Block

Shutting down the secondary PGM

Perform the following steps to shutdown the secondary PGM

1. Navigate to the appropriate secondary PGM FB in the
Monitoring view.
2. Double-click the PGM FB.
3. In the Main tab, click Shutdown in the Controller Command list.
The secondary PGM FB is shutdown. This results in the
PGM to work as a non-redundant PGM.

PGM block station displays

Detail displays and faceplate names
The following table lists the names of the details display and
faceplate of the PGM (primary/non-redundant and
secondary/redundant) block.

Tab Name Detail Display Faceplate

Primary or non-
redundant

Main tab sysdtlPGM2a.htm sysdtlPGM2a_

fp.htm

Redundancy tab sysdtlPGM2b.htm

Soft Failures tab sysdtlPGM2c.htm

Configuration Details sysdtlPGM2d.htm

tab

Secondary or
redundant

Main tab sysdtlPGM2a.htm sysdtlPGM2a_

fp.htm

Redundancy tab sysdtlPGM2b.htm

Soft Failures tab sysdtlPGM2c.htm

69
 Chapter 5 - PROFIBUS Gateway Module (PGM) Block

Tab Name Detail Display Faceplate

Configuration Details sysdtlPGM2d.htm

tab

Calling up the displays

The following table lists the actions that you must perform to
call up the PGM block detail displays.

To call the
Then …
PGM block…

Main tab Type the point name (for example PGM2_325) in

display the Station command zone and press F12. You

can also click the Search icon in the

Station toolbar and type the point name and click
OK.

Redundancy Click the Redundancy tab.

tab display

Soft Failures Click the Soft Failures tab.

tab display

Config details Click the Config Details tab.

display

Secondary
PGM Main tab
displays Click the icon in the Station toolbar. You
can also type the point name (for example PGM2_
325SEC) in the Station command zone and press
F12.

Secondary Click the Redundancy tab.

PGM
Redundancy
tab display

Secondary Click the Soft Failures tab.

70
Chapter 5 - PROFIBUS Gateway Module (PGM) Block

To call the
Then …
PGM block…

PGM Soft
Failures tab
display

Secondary Click the Config Details tab.

PGM Config
details display

Detail display tabs

Main tab
From the Main tab detail display, you can navigate to the
PBLink block detail display directly by clicking the hyper-link
provided for the PBLink_<> blocks.

Figure 5-1: PGM Main tab display

You can modify the following values from the PGM Main tab
detail display.

71
 Chapter 5 - PROFIBUS Gateway Module (PGM) Block

n Alarm Enable State.

n Temperature Threshold (this is not available in the
secondary module detail display).
n Stack exceeded alarm.
n Controller Command.
n Reset Statistics (this is a push button).

ATTENTION: The Main tab detail display of the redundant

PGM is identical to the primary PGM Main tab detail
display tab.

Redundancy tab
The Redundancy tab detail display provides the redundancy
history details. You can also view the complete configuration
details of the PGM block from the Config Details link provided
in the Redundancy history section.
When you click the Config Details link, the Main tab of the PGM
block configuration form appears. You can click the
Redundancy tab in the configuration form to view the
redundancy parameters.

72
Chapter 5 - PROFIBUS Gateway Module (PGM) Block

You can perform the following functions from the PGM

Redundancy tab detail display.
n Disable Synchronization.
n Enable Synchronization.
n Become Primary.
n Initiate Switchover.

TIP:
These parameters appear as push buttons in the detail
display.

ATTENTION: For a non-redundant PGM, the text "Non

Redundant" appears in the Redundancy tab detail display.

Soft failure tab

The Soft failures tab detail display provides information on the
soft fails that have occurred in the PGM block. If there is a soft
fail, the corresponding LED in the detail display appears red.
Note that you cannot modify any values from the Soft Failures
tab detail display.

73
 Chapter 5 - PROFIBUS Gateway Module (PGM) Block

ATTENTION: In the event of a communication error, all the

LEDs in the Soft Failure tab appear gray.

Config Details tab

The Config Details detail display is identical to the Main tab of
the PGM block (from Control Builder).

You can modify the following values from the Config Details
detail display.
n Alarming Enabled.
n Controller Command.
n Temperature High Alarm.
n CPU Free Low.

PGM group detail display, system status display,

group trend display

Group detail displays

You can configure the group with PGM, PBLINK, and PIOMB
faceplates.

74
Chapter 5 - PROFIBUS Gateway Module (PGM) Block

Group Trend display

You can configure the group trend with PGM, PBLINK, and
PIOMB faceplates.

System Status display

You can view the faceplates of PGM, PBLINK, and PIOMB on
the status pane of the System Status Display.

75
 Chapter 5 - PROFIBUS Gateway Module (PGM) Block

PGM faceplates
You can acknowledge the alarms from the faceplate. In
addition, the operators can issue the "SHUTDOWN" command
from the faceplate. The following figure displays the faceplate
of a redundant and non-redundant PGM.

76
Chapter 5 - PROFIBUS Gateway Module (PGM) Block

77
CHAPTER

6 PROTOCOL BLOCK

In this section:

Protocol Block overview 79

Configuring the Protocol Block 81
Configuring the PROFIBUS devices in PROFIBUS Network
Configuration Tool 82
Configuring the master in Profibus Network Configuration
Tool 91
Adding a new GSD-based device to PROFIBUS Network
Configuration Tool library 100
About grouping adjacent modules into one logical module101
About modifying the field network configuration during
runtime 110
Support for time synchronization functionality 114
Export/import of field network configuration 116
Audit Trail for field network configuration 118
Monitoring Protocol Block 120
Monitoring the field network configuration 125
QVCS - Diff Tool view of non-human readable data 135
Protocol Block station displays 136

78
Chapter 6 - Protocol Block

Protocol Block overview

The Protocol Block represents one of the field network
interfaces. The Protocol Blocks are automatically created when
a PGM block is created. These blocks manage the
communication between the master (PGM) and the PROFIBUS
devices. These blocks are also responsible for exchanging
process, acyclic, and diagnostic data.
The Protocol Blocks are used to perform the field network
configuration. The "Profibus Network Configuration Tool "is the
tool used to perform the PROFIBUS network and
PROFIBUS device configuration. This tool is also used for
online monitoring of the field devices. The "Profibus Network
Configuration Tool " can be invoked directly from the Protocol
Block configuration tabs.
On creating a PGM block, two Protocol Blocks are automatically
created and assigned to its parent PGM block. You cannot
create a Protocol Block individually. Similarly, you cannot delete
a Protocol Block individually. You must delete the parent PGM
block to delete the Protocol Block.

"Profibus Network Configuration Tool "

The "Profibus Network Configuration Tool " is used for
configuring the field network devices on the PROFIBUS
gateway. The Protocol Block configuration form is the host tool
and the "Profibus Network Configuration Tool " is an ActiveX
component. The "Profibus Network Configuration Tool " can be
invoked directly from the Field Network Configuration tab of
the Protocol Block configuration form. The "Profibus Network
Configuration Tool " frame contains the PGM as a master in the
Network view. The Library view contains the device catalog
("Profibus Network Configuration Tool " library) that lists all the
available vendor and PROFIBUS devices.
When you select a PROFIBUS device, its associated Device Type
Manager (DTM) also appears.
The following figure displays a sample Field Network
Configuration tab of the Protocol Block that hosts the "Profibus
Network Configuration Tool ".

79
 Chapter 6 - Protocol Block

This tool is also used for online monitoring of the field devices.
In addition, you can import and export the field network
configuration using the "Profibus Network Configuration Tool ".

Using Profibus Network Configuration Tool for

configuring field network devices
The field network configuration that you perform using the
"Profibus Network Configuration Tool " must be identical to the
actual field setup.
Configuring a field network device using "Profibus Network
Configuration Tool " involves the following steps.
1. Configuring responder.
2. Configuring master.

ATTENTION: If you are migrating a PGM from R410.1 or

earlier, you must manually install SYCON.net_Honeywell_
setup.exe as per the Installation Instructions document.
This document is available in the R410.2 support media in
the following path: Packages\Hilscher\SYCON_NET.

80
Chapter 6 - Protocol Block

Configuring the Protocol Block

Perform the following steps to configure a Protocol
Block
1. Double-click the PBLink_<> icon. The Protocol Block
configuration form appears.
2. In the Tag Name box, type the name of the Protocol block (a
maximum of 40 characters) or accept the default.
3. In the Item Name box, type the item name.
4. In the Description box, type a description of the block (a
maximum of 132) characters in the Description box.
5. In the Baud Rate list, select the baud rate for the link that is
configured in "Profibus Network Configuration Tool ".

ATTENTION: You must configure this parameter only

for calculating the DPV1 bandwidth based on the
baud rate.

6. In the DPV1BANDWIDTH list, select the percentage of

PROFIBUS DP bandwidth that you want to allocate for DPV1
request and response handling.
7. Click the Field Network Configuration tab. The following figure
displays a sample Field Network Configuration tab. The
address of the master is always 1. For more information on
configuring a field device, refer to Configuring field network
device.

81
 Chapter 6 - Protocol Block

8. Use the online help as a guide to complete the configuration

entries on all other tabs.
9. Click OK.

Configuring the PROFIBUS devices in

PROFIBUS Network Configuration Tool
Prerequisites
The PROFIBUS device being configured must to be present in
the"PROFIBUS Network Configuration Tool " Library view. If a
device does not appear in the Library view, you must add the
device to the library. For more information, see Adding a new
GSD to the "PROFIBUS Network Configuration Tool " library.

ATTENTION: You can use the following procedure for

configuring the parameters that are generic to all DSBs.
However, you must refer to the sections “<DSB
name>specific module configuration in "PROFIBUS
Network Configuration Tool "” for information on
configuring parameters that are specific to each DSB. For
example, you can refer to the section “Turck Excom DSB

82
Chapter 6 - Protocol Block

specific modules configuration in "PROFIBUS Network

Configuration Tool "” for Turck Excom DSB specific
configuration.

n When performing the field network configuration, some of

the devices may not function as expected and there can be
errors when the Protocol Block is loaded when such devices
are used. This can be a result of the vendor GSDs not
supporting the functionalities provided by the PGM.
n When you use the Siemens PA coupler, you must modify the
Slot Time, Max. Station Delay Time, and the Setup Time
values to enable the coupler detect the PA devices. For more
information, see Modifying the PROFIBUS network setup
values (bus parameters).

Perform the following steps to configure a PROFIBUS

device
1. Click the Field Network Configuration tab of the Protocol Block
configuration form.When you create a PROFIBUS network
configuration, the PROFIBUS master address is set to 1 and
the secondary address is set to 0, by default. If you have
more than one PGM pair connected to the same physical
network, ensure that there are no other devices with
identical addresses in any of the PGM pairs in the same
network.
2. Drag-and-drop the device you must configure from the
Library view to the Network view. You can also copy and
paste the existing PROFIBUS devices in the Network view.
When you copy and paste an existing PROFIBUS device, the
tag names are also copied. You can modify the tag names,
as required.
3. Double-click the device in the Network view. The
configuration form of the specific device appears. You can
also right-click the PROFIBUS device in the Network view
and select Configuration The Modules menu in the Navigation
Area is selected by default. The Available Modules section lists
all the available modules that can be associated with the
selected PROFIBUS device.
4. Select the modules that you must associate with the
PROFIBUS device.

83
 Chapter 6 - Protocol Block

5. Click Insert. All the modules you selected in the Available

Modules section appear in the Configured Modules section.
When you click Append, the last module you selected is
placed at the end of the Configured Modules list.
6. Select the Parameters menu from the Navigation Area.
7. Click Common from the Module list. All the common
parameters of the selected device appears in the Module list
and you can configure the common settings, as required.
The parameters that appear in this list may vary based on
the DSB selected.
8. Select the I/O module from the Module list.
Configure the channel type and the channel's high and low
ranges. Refer to the following figure for an example of
configuring the analog module parameters. You must
perform this step if you have selected the analog I/O
modules.

9. Similarly, select the other I/O modules from the Module list
and configure the channel type and the channel's high and
low ranges.
10. Select the DPV1 menu from the Navigation Area. You can
enable DP-V1 from the DPV1 menu in the Navigation Area.
Note that PGM does not support DP-V1 in R400. However,
for the ET200M devices, DP-V1 is enabled by default.
11. Click Apply.

84
Chapter 6 - Protocol Block

12. Click OK.

13. Click Save on the Field Network Configuration tab toolbar. A

message appears after you save the configuration. When
you click Save, the configuration is saved temporarily.

14. Click OK.

15. Click OK to close the Field Network Configuration form.
The field network configuration is saved to the ERDB.

85
 Chapter 6 - Protocol Block

ATTENTION: If you click Cancel and close the

configuration form, the configuration is not saved to
the ERDB even if you have clicked Save on the Field
Network Configuration tab toolbar.

Drive DSB specific module configuration in Profibus

Network Configuration Tool
The following list illustrates the Drive device specific module
configuration guidelines that you must remember while
configuring the Drive device in "Profibus Network Configuration
Tool ".
n You can only select one PPO type for a Drive device.

GENPADSB and GENPAGWDSB specific module

configuration in Profibus Network Configuration Tool
The following list summarizes the GENPADSB and
GENPAGWDSB specific PDC configuration guidelines that you
must remember while configuring the GENPADSB and
GENPAGWDSB.
n For Siemens DP/PA Link IM-157, you must use the
customized GSD file that is generated from the GSD

86
Chapter 6 - Protocol Block

Combiner tool.
n While configuring the GENPAGWDSB for Siemens DP/PA
Link IM-157, you must refer to the Siemens DP/PA Link
document.
n While configuring the GENPAGWDSB, to support alarming
based on diagnostic data received from Siemens DP/PA
Link IM-157, you must select the option 160 byte diagnostics
data length from the Parameters page.

Siemens ASi Link DSB specific modules configuration

in Profibus Network Configuration Tool
The following list illustrates the Siemens AS-i Link device
specific module configuration guidelines that you must
remember while configuring the Siemens AS-i Link device in
"Profibus Network Configuration Tool".
n For configuring the Siemens AS-i Link/Siemens AS-i Link
Advanced device, the minimum configuration required to
support all 31 devices involves mapping every 4 bytes to a
single net tag (in the field network configuration). This
means that you can leave some bytes with the default net
tag name.
n . While configuring the Siemens AS-i Link DSB for AS-I Link
20E device, you can only select the "max. 16/16 Byte AKF"
module. Note that the "max. 32/32 Byte" module is not
supported by the Siemens AS-i Link DSB.
n While configuring the Siemens AS-i Link DSB for AS-i Link
Advanced device, you must select the Classic layout which is
the only layout supported by this DSB.
n While configuring the Siemens AS-i Link DSB for the AS-i
Link Advanced device, you can select "ASi-1: Binary Array
16-byte" and/or "ASi-2: Binary Array 16-byte."

Siemens ET 200M DSB specific module configuration

in Profibus Network Configuration Tool
The following list illustrates the Siemens ET200m device
specific module configuration guidelines that you must
remember while configuring the Siemens ET200M device in
"Profibus Network Configuration Tool".

87
 Chapter 6 - Protocol Block

n While configuring the Siemens ET200M DSB, you must

define configuration slot 1, Configuration slot 2, and
Configuration slot 3 in the slot 1,2, and 3 respectively. You
can define the I/O modules from slot 4 onwards in the same
order as they are placed in the physical rack.
n You must select the following values for the common
parameters.
l Diagnostic Interrupt - Yes

l Process Interrupt - Yes

l Analog-Value format - SIMATIC S7

l Extended diagnostics - Yes

l Start-up for setpoint/act.conf - Yes

l Remove/Insert interrupt - Enable

n While configuring the channel type, channel high and low

ranges;
l The slot number parameter can be used to set the

physical position of the module on the rack. The slot

number for I/O modules starts from 4. The first three
slots are reserved. For example if AI module takes the first
position after the station in the rack, then its slot number
is 4.
l The Diag enable channel parameters can be used to enable

extended diagnostic for the channel.

l The Meas: Type/Range parameters can be used to select

signal type for the channel.

Turck Excom DSB specific modules configuration in

Profibus Network Configuration Tool

For reading HART data

The following sections illustrate the Turck Excom device
specific module configuration guidelines that you must
remember while configuring the Truck Excom device in
"Profibus Network Configuration Tool".
n For configuring the Turck Excom DSB to read HART data,
you can configure the I/O modules AIH40Ex or AIH41Ex or
AOH40Ex as follows.

88
Chapter 6 - Protocol Block

l AIH40Ex/AIH41Ex/ AOH40Ex - Process data + 1 HART

data
l AIH40Ex/AIH41Ex/ AOH40Ex - Process data + 4 HART

data
l AIH40Ex/AIH41Ex/ AOH40Ex - Process data + 8 HART

data
If you are using the output module, AOH40Ex, you must
configure two net tag names; one for the process data and
one for the HART data. However, if you are using the input
module, AIH40Ex or AIH41Ex, you must configure only one
net tag name.
While configuring the module-specific parameters in the
Parameters page, you can note that for each channel, the
first secondary variable value is set to “on” and the
remaining three secondary variable value is set to “off.” You
can modify this as required based on from which secondary
variable you want to read the HART data.
The following figure illustrates a sample Parameters page of
a module that is capable of reading HART data.

For gateway redundancy

n For configuring the Tuck Excom DSB for gateway
redundancy, you must select the gateway module with suffix
“C” (Cyclic Data). For example, GDP1,5Ex C should be

89
 Chapter 6 - Protocol Block

selected if “Trckff9f” GSD file is used for configuration. The

gateway module contains an input status word and an
output command word. You must configure the net tag
names for both words.
n While configuring the module- specific parameters in the
Parameters page, you must configure the following
parameters for gateway redundancy.
l Redundancy mode - Redundancy mode is “off” by default.

When the redundancy mode is “off,” communication

capability of the redundant gateway is not verified on
switchover and diagnostic data for gateway is not
generated. Therefore, you cannot view the status of the
redundant gateway in the Redundant Gateway tab from the
Monitoring view. When the redundancy mode is set to
“mode 1,” the communication capability of the redundant
gateway is verified on switchover and diagnostic data for
gateway is generated. In addition, you can view the status
of the redundant gateway in the Redundant Gateway tab
from the Monitoring view. Mode 3 is not supported.
l address offset - You must select the value “enable.”

l address offset value - An address offset value for the

secondary gateway.
The following figure illustrates a sample Parameters page of the
GDP module.

90
Chapter 6 - Protocol Block

Configuring the master in Profibus Network

Configuration Tool
While configuring the master, the mandatory task that you
must perform is modifying the field network tag name.
You can also perform the following tasks while configuring the
master.
n Assign the device to the correct hardware.
n Change the PROFIBUS network setup values.
n Change the field network device address.
n Change the master settings.

ATTENTION: To perform any of the above tasks, you must

navigate to the Field Network Configuration tab of the
Protocol Block configuration form and double-click the
master in the Network view.

Perform the following steps to configure the master

1. Click the Field Network Configuration tab of the Protocol Block
configuration form.
2. Double-click the master in the Network view. You can also
right-click the master in the Network view and select
Configuration. The configuration window appears. The Device
Assignment menu in the Navigation Area is selected by
default. The device assignment details appear in the right
pane.
3. Perform the following as required.
l Assigning the device to the correct hardware

l Modifying the PROFIBUS network setup values (bus

parameters)
l Configuring the field network tag names

l Changing the field network device address

l Grouping adjacent modules into one logical module

l Changing the master settings

l About modifying the field network configuration during

runtime
4. Click OK.

91
 Chapter 6 - Protocol Block

5. Click Save in the Field Network Configuration tab

toolbar. A message appears after you save the configuration.

When you click Save , the configuration is saved

temporarily.
6. Click OK.
7. Click OK to close the Field Network Configuration form. The
field network configuration is saved to the ERDB. If you click
Cancel and close the configuration form, the configuration is

not saved to the ERDB even if you have clicked Save

on the Field Network Configuration tab toolbar.

Assigning the device to the correct hardware

You must assign the device to the correct hardware to monitor
the status of the field network and the devices online.
1. Click the Device Assignment menu in the Navigation Area.
2. Click Scan. This reads information from the hardware
through the network. Therefore, the PGM module must be
available and powered on before assigning a device. After
the scan is complete, the device information such as the
chip type, the serial number, and the access path is
displayed.
3. Select the check box against the device that you must
assign.
4. Click Apply.

92
Chapter 6 - Protocol Block

Modifying the PROFIBUS network setup values (bus

parameters)
1. Click the Bus Parameters menu in the Navigation Area. The
Bus Parameters details appear in the right pane. The Bus
Parameters details contain the main setup values of the
PROFIBUS network. For more information on each
parameters, refer to the PROFIBUS website.

If the Data Control Time and Watchdog Control Time are

not configured properly, and there is a switchover initiated,
this may result in loss of communication with the
PROFIBUS devices. In such a scenario, you must modify the
Baud Rate, the Watchdog Control Time, and the Data
Control Time. The Baud Rate is also dependent on the
number of PROFIBUS devices configured in the network. In
addition, you must select the Override slave specific Watchdog
Control Time check box.
2. Click Apply.

ATTENTION:
If repeaters like Procentec B2+R, ABB RLM etc.. is used in
Profibus network, then bus parameters like min TSDR (SDR
= Station Delay of Responder), max TSDR, TSL (SL = slot)

93
 Chapter 6 - Protocol Block

and TQUI (Quiet time) must be calculated as per the

corresponding repeater manual.

Configuring the field network tag names

The procedure of configuring field network tag names for Drive
devices and AS-I link/AS-I Link Advanced is slightly different
from this procedure. For more information, see Configuring
field network devices tag names for the Drive devices and
Configuring field network tag names for the AS-i Link/AS-i Link
Advanced devices respectively.

ATTENTION: You can also configure net tag names through

Bulk Build operation. To do so, you must configure the
NETTAGPDCNAME and the NETTAGNAME parameters. The
NETTAGPDCNAME contains the net tags for the PROFIBUS
devices configured in "Profibus Network Configuration
Tool". This parameter contains net tags starting from index
1 (NETTAGPDCNAME[1]) in the Bulk Build XLS file. If you
do not configure this parameter, NETTAGNAMEs for the
PDCs are not assigned in the DSB on creating and
assigning it to the Protocol Block through the Bulk Build
tool.

1. Click the Process Data menu in the Navigation Area. The

PROFIBUS devices that you have selected appear in the
right pane.

94
Chapter 6 - Protocol Block

2. Click to view the input and output modules associated with

the specific device. By default, the field network tags appear
as Input_* or Output_* depending on whether the device is
an input module or an output module.
3. Select the field network tag in the Tag column and modify
the tag name. If you do not modify the default network tags,
only the first default name for each input/output is used.
The following figure displays a sample Address Management
page that replaces the Process Data page and the Address
Table pagein Experion R410.2 and later.

The network tag names must be unique within a PROFIBUS

95
 Chapter 6 - Protocol Block

device. However, you can use the same tag name for
another PROFIBUS device. If there are identical tag names
within a PROFIBUS device, an error message appears when
you try to save the configuration.
4. Click Apply.
5. Click OK.

Configuring field network tag names for the Drive devices

1. Click the Process Data menu in the Navigation Area. The
Danfoss VLT2880 PPO type 1 is used for illustration
purposes. The PPO type that you have selected appears in
the right pane.

2. Click the plus sign to expand all the inputs and outputs
associated with the specific PPO type.

The PKW and cyclic data areas appear separated from each
other. Based on the number of PKW and cyclic data areas,

96
Chapter 6 - Protocol Block

you must configure the network tag names. In the example

above, there are two inputs (PKW inputs and Cyclic inputs)
and two outputs (PKW outputs and Cyclic outputs).
Therefore, you must configure four PDCs to access this
data.
3. Configure the PKW inputs as "PKWIn" and PKW outputs as
"PKWOut."
4. Configure the input PPO type PDCs as "CyclicIn" and output
PPO type PDC as "CyclicOut." If there are more than one
input PPO type PDCs, you must configure the input PPO
types as CyclicIn1, CyclicIn2, and so on.

TIP: Note that the net tag names provided in the above
example are used for illustration purposes only. You
can use different net tag names as required.

5. Click Apply.
6. Click OK.

Configuring field network tag names for the AS-i Link/AS-i Link
Advanced devices
1. Click the Process Data menu in the Navigation Area.

2. Click to view the input and output modules associated with

the AS-i Link/AS-i Link Advanced device.

97
 Chapter 6 - Protocol Block

3. Modify the net tag names for a single byte of data. This tag
name must refer to the entire 4 byte area with the tag name
referring to its own byte plus the 3 byte with the default
names.

In the above figure, net tag "Slv1_7Out" refers to its own

byte, plus the 3 bytes with the default names "Output_2,"
"Output_3," and "Output_4." Similarly, the net tag "Slv16_
23In" refers to its own byte, plus the 3 bytes with the default
names "Input_10," "Input_11," and "Input_12."

TIP: Note that the net tag names provided in the above
example are used for illustration purposes only. You
can use different net tag names as required.

4. Click Apply.
5. Click OK.

98
Chapter 6 - Protocol Block

Changing the field network device address

1. Click the Station Table menu in the Navigation Area. The
Station Table appears in the right pane. The Station Table
displays the field network device information such as device
address, device name, and vendor name.
2. Change the field network device station address, if required,
in the Station Address column. The address you set here must
be identical to the address that is set on the device using
the address switches. Normally, the address on devices is
defined by a dip switch.
3. Change the device name, if required.
4. Click Apply.

Changing the master settings

1. Click the Master Settings menu in the Navigation Area. You
can only change the watchdog time in the master settings.
The master settings appear in the right pane.
2. Change the watchdog time if required in the Watchdog time
box.
3. Click Apply.

Detecting PROFIBUS devices in the network

You can detect all the physical PROFIBUS devices in the
network from the Field Network Configuration tab of the
Protocol Block. This can be accomplished by performing a
Network Scan. This scan lists all the physical PROFIBUS
devices connected to the network. In addition, you can add a
PROFIBUS device to the network, if the device is not added to
the network.

Perform the following steps to detect all PROFIBUS devices in

the network
1. Click the Field Network Configuration tab of the Protocol Block
in which you have configured the PROFIBUS master and the
PROFIBUS device.

99
 Chapter 6 - Protocol Block

2. Right-click the master and select Network Scan. If you have

not assigned the device to the hardware, an message
appears. The netDevice window appears as displayed in the
following figure. This window lists all the physical devices
that are present in the network and also the details of the
devices.

3. If you want to add a device to the network, select Add from

the Action column.
l If the device is already added to the network, the value

Skip appears in the Action column.

l If you want to replace a device with another device, select

Replace in the Action column.

4. Click OK.

Adding a new GSD-based device to PROFIBUS

Network Configuration Tool library
A Generic Station Description (GSD) file is an electronic data
description of a PROFIBUS device. In accordance with a
standard format, the GSD file is a text file that is defined and
supplied by the device vendor.
You can add new GSD-based devices to the "PROFIBUS
Network Configuration Tool" library if they are not available in
the "PROFIBUS Network Configuration Tool"library.

100
Chapter 6 - Protocol Block

TIP:
You can obtain the GSD file from the device
manufactures. You can also check for the GSD files in the
PROFIBUS website.

Perform the following steps to add a new GSD-based

device to PROFIBUS Network Configuration Tool
library
1. Copy the GSD file of the device into the following directory.
Documents and Settings\All Users\Application
Data\SYCONnet\PROFIBUS\GSD. For Windows 7, use the
following directory.
C:\ProgramData\SYCONnet\PROFIBUS\GSD. You must copy
only one version of the device GSD to the defined directory.
If different versions (languages) are copied, you will see the
device as many times in the "PROFIBUS Network
Configuration Tool" library. If the same device exist several
times in the "PROFIBUS Network Configuration Tool" library,
the first one will be used always irrespective of which one is
dragged-and-dropped into the network view.

2. Click Reload Catalog on the Field Network Configuration tab

toolbar to rebuild the device catalog. A dialog box appears
that displays the catalog update completion status. The new
device appears in the PROFIBUS Network Configuration
Tool library after the catalog update is complete. If the
device does not appear in the "PROFIBUS Network
Configuration Tool" library, you must restart the Control
Builder.

About grouping adjacent modules into one

logical module
ATTENTION: This feature is available in Experion R410.2
and later.

Though a single PDC can support up to 32 channels (GENDSB)

or 16 channels (GENIODSB), sometimes not all channels of a

101
 Chapter 6 - Protocol Block

module are used. In such scenarios, you can pack IO channels

from several IO modules into one PDC to minimize number of
PDCs. This reduces the load on PDA and controller by
decreasing the number of PDC-PIOMB connections.
Grouping of adjacent modules into one logical module is
supported for the GENDSB and the GENIODSB. This module
grouping enables you to select multiple adjacent IO modules
and create one logical module. This logical module can have
one net tag name and this net tag name can be associated with
a single PDC.
Example: Consider a scenario where you have three IO
modules but you are using only three channels of each module.
In this case, you need three PDCs for three modules, three
PIOMBs, and three connections. However, with module
grouping you can group all the modules into one group and
configure one net tag name and associate this net tag name
with a single PDC. This ensures that the data is available in a
single PDC and this PDC can be associated with a single
PIOMB.
To enable module grouping, the Address Table page and the
Process Data page in the field network configuration tool
(Profibus Network Configuration Tool) is replaced by the
Address Management page. For more information, refer to the
section Grouping adjacent modules into one logical module.

Guidelines for grouping modules

The following list summarizes the guidelines for grouping the
modules together.
n You can group only the adjacent modules with consecutive
addresses and there must not be any empty slot in between
the grouped modules.
n You can configure the input modules as one group and the
output modules as another. However, you cannot configure
both input and output modules as one group.
n You can group bidirectional modules as groups. However,
you cannot group unidirectional and bidirectional modules
as one group.

102
Chapter 6 - Protocol Block

n When grouping bidirectional modules, you must ensure that

all the modules in the group are consistent with respect to
positioning of the input and output channels. However, you
cannot randomly configure the first channel as input and
second channel as output and then again third channel as
input and fourth channel as output and so on.
n You must start channel numbering either from 0 or 1, but
should be consistent within the group. For example if you
start numbering the channels from 1, then channel
numbers must start from 1 for all the modules in that group.
Similarly, if you start numbering the channels from 0, then
channel numbers must start from 0 for all the modules in
that group.
n For all the grouped PDCs (PDC which is configured for a
grouped module), you must correctly enter the
CHNNUMBER parameter. The channel numbers must be
entered in the same order as they are grouped.
l Example 1: Assume four input modules each having four

channels are grouped together, then the NUMCHANNEL

must be entered as 16 (4+4+4+4) and the CHNNUMBER
parameter should contain: 0, 1, 2, 3, 0, 1, 2, 3, 0, 1, 2, 3, 0,
1, 2, 3 or 1, 2, 3, 4, 1, 2, 3, 4, 1, 2, 3, 4, 1, 2, 3, 4 (if the
channel numbering is started from 1).
l Example 2: Assume three output modules on slots 5, 6, 7

are grouped together. The module on slot 5 has three

channels, the module on slot 6 has four channels and the
module on slot 7 has eight channels. Then the
NUMCHANNEL should be entered as 15 (3+4+8) and the
CHNNUMBER parameter should be entered as displayed
in the following figure.

If the channel numbering starts from 1, then the channel

numbers must be 1, 2, 3, 1, 2, 3, 4, 1, 2, 3, 4, 5, 6, 7, 8.

103
 Chapter 6 - Protocol Block

Also the physical channel numbers of each module

should be entered correctly and in the same order as they
are grouped. Here the first set 0, 1, 2 represents the
channels of the first module in the group, which is on slot
5. The second set 0, 1, 2, 3 represents the channels of the
second module in the group, which is on slot 6. The third
set 0, 1, 2, 3, 4, 5, 6, 7 represents the channels of the third
module in the group, which is on slot 7. When grouping
digital modules which have the number of channels that
are not multiples of 8 (for example 2, 4, 12, and so on),
you must use the Configurable Input/Output PDC types
for configuration. You cannot use the Digital
Input/Output PDC types for configuring such digital
modules as this configuration is not supported for
module grouping.

About the Address Management page

In Experion R410.1 or earlier, the Address Table page displays
the configured module’s offset and length wherein you can
manually adjust the offsets. The Process Data page displays the
configured signals, IOs, definition of the tag names for signals
and modules.
In Experion R410.2 and later, the contents of the Address Table
page and the Process Data page are combined into a single
page called the Address Management page. The Address
Management page enables you to perform the following:
n Group modules together into a virtual module for which you
can assign a tag name.
n Add/remove reserved memory space for each PROFIBUS
devices.
n Lock/unlock slave addresses.
n Defragment input and output memory area.
The following figure displays a sample Address
Managementpage.

104
Chapter 6 - Protocol Block

The following table summarizes the various options available in

the Address Management page.

Option name Description

Defragment Defragments the memory automatically.

Display Mode Displays the address in decimal or hexadecimal

format.

CSV Export Enables you to export the configuration into an

Excel file. Grouped modules do not appear in the
exported file.

Group Enables you to select multiple adjacent modules

selected and create a new virtual module.
modules

Ungroup Enables you to ungroup a grouped virtual module

or one of the modules in a group. Also deletes the
corresponding grouped virtual module.

Add reserved Enables you to add a contiguous memory area as

area reserved area for a PROFIBUS device. By default,
reserved memory space for each responder is 128
bytes. However, you can modify this based on your
requirement. Maximum space available is 244
bytes for each input or output.

105
 Chapter 6 - Protocol Block

Option name Description

Del reserved Enables you to free unnecessary reserved memory

area area.

Lock all Enables you to lock all PROFIBUS devices and

responders their respective modules at the current configured
Dual-Ported Memory (DPM) addresses. Data
addresses for the locked responder are retained in
any network configuration change.

Unlock all Enables you to unlock all PROFIBUS devices and

responders their respective modules which are currently
locked.

Remaining Displays the remaining reserved bytes for the

free memory responder.

Grouping adjacent modules into one logical module

Perform the following steps to group adjacent modules in to
one logical module.

ATTENTION: Refer to the Guidelines for grouping modules

section before grouping modules.

1. Click the Field Network Configuration tab of the Protocol Block

configuration form.
2. Double-click the master in the Network view.
3. Click Address Management in the Navigation area. The Address
Management page appears.

4. Click to view the input and output modules associated

with the specific device.
5. Select the adjacent modules that must be grouped into one
logical group. The following figure displays a sample Address
Management page in which two adjacent modules are
selected for –––grouping.
6. Click Group selected modules. After the modules are grouped,
a virtual tag name is automatically assigned to the grouped
logical module. You can modify the tag name as required.

106
Chapter 6 - Protocol Block

After the modules are grouped, you can click the Lock all
slaves button to lock the modules at the current configured
address. You can click the Unlock all slaves button to unlock
the locked modules. The following figure displays a sample
virtual tag name for the grouped modules.
You cannot group IO modules if one or more IO modules
have PDC references in DSB. The network configuration tool
does not display any error message if you group IO modules
that have PDC references in DSB. Also, when you group
such modules the status bar displays the status as save
operation succeeded and also the virtual group is created.
This virtual group exists even after you close and reopen the
Address Management page. However, when you close the
Protocol Block configuration form and reopen it, you can
notice that the grouping was not successful and the virtual
group is not displayed.
7. Click OK to close the Address Management page.
8. Click OK to close the Field Network Configuration tab.

Ungrouping grouped modules

Perform the following steps to ungroup the grouped modules.
1. Click the Field Network Configuration tab of the Protocol Block
configuration form.
2. Double-click the master in the Network view.
3. Click Address Management in the Navigation area. The Address
Management page appears.

4. Click to view the input and output modules associated

with the specific device.
5. Select the grouped modules that must be ungrouped.
6. Click Ungroup. After the modules are ungrouped, the virtual
name disappears and the actual names of the modules are
reverted.
7. Click OK to close the Address Management page.
8. Click OK to close the Field Network Configuration tab.

107
 Chapter 6 - Protocol Block

Adding reserved memory area to the devices

Perform the following steps to group adjacent modules in to
one logical module.
1. Click the Field Network Configuration tab of the Protocol Block
configuration form.
2. Double-click the master in the Network view.
3. Click Address Management in the Navigation area. The Address
Management page appears.

4. Click to view the input and output modules associated

with the specific device.
5. Select the module/device for which you want to add
reserved memory area.
6. Click Add reserved area.
l An empty row with the text Reserved in the Device/Module

name column appears. In addition, for each responder a

reserved memory space size of 128 bytes is added in the
Length column.
l Every time you click the Add reserved area button, the Add

reserved area button changes to Del reserved area button

and vice versa. You can click the Del reserved area button
to remove the unnecessary reserved memory area.

ATTENTION: Maximum space available for a

configured module is 244 bytes for an input or an
output. When 244 bytes are configured and if you try
to add reserved memory space, an error message
appears indicating that no reserved memory can be
added.

Modify the length of the reserved memory as required in the

Length column.
7. Click Defragment.
8. Click Apply. If you want to cancel adding reserved memory
area, you can click Cancel in the Address Management page
and click No in the Question dialog box. However, when you
open the Address Management page after canceling, the
addresses of the other devices changes to 0. You must click

108
Chapter 6 - Protocol Block

the Defragment button again to restore the addresses.

However, when you close and open Field Network
Configuration tab, the addresses are restored.
9. Click OK to close the Address Management page.
10. Click OK to close the Field Network Configuration tab.

Defragmenting memory area

Perform the following steps to defragment the memory area.
1. Click the Field Network Configuration tab of the Protocol Block
configuration form.
2. Double-click the master in the Network view.
3. Click Address Management in the Navigation area.
4. Click Defragment. Defragmentation does not change the
offsets of responders for which these offsets are locked.
5. Click Apply.
6. Click OK to close the Address Management page.
7. Click OK to close the Field Network Configuration tab.

About the Signal Configuration page

After you have configured the resoner devices in the master,
you can view the device details such as the slot number, device
type, tag name, data type, and so on from the Signal
Configuration page.
The following figure displays a sample Signal Configuration
page.

109
 Chapter 6 - Protocol Block

NOTE: When adding a new signal, ensure the Apply button

is clicked before clicking on the Add Signal button for the
next signal. Adding a new signal without pressing the Apply
button for the previously added signal may corrupt the
signal data.
Steps for Adding New Signals:
1. Click Add Signal to begin.
2. Input all necessary details and configurations for the
new signal.
3. Click Apply to save the current signal settings.
4. Once the changes are applied, click Add Signal again to
create the next signal.

About modifying the field network

configuration during runtime
Starting 410.2, Configure In Runtime (CiR) / Hot Configuration
in Run (HCiR) is supported in PGM. This feature enables you to
modify some of the PROFIBUS device configuration without
causing a break in the V0 process data delivery to other
PROFIBUS devices. When you modify the configuration during

110
Chapter 6 - Protocol Block

runtime, the corresponding device is r-econfigured, which

means that the field device is re-initialized.
CIR in PGM is supported for responders that retain their
process data in same addresses in old and new version of the
network configuration.

ATTENTION: While configuring the responders in "Profibus

Network Configuration Tool", it is recommended that you
add reserved input and/or output memory area to the
responders and lock the responders (ensure that you lock
the inputs and outputs separately). This helps you to add
modules without unlocking the responders. The length of
the reserved area gets adjusted automatically with the
memory area of the module on insertion of a module. This
way the Target Token Rotation Time (TTRT) is maintained
and as a result the change can be loaded to the PGM
without causing process data delivery interruptions to
unchanged responders in the network. As long as the
modified responder supports the Hot Configuration in Run
feature, even its own inputs and outputs are automatically
frozen during the re-configuration and a bump-less restart
after the re-configuration is executed.

Modifying PROFIBUS device configuration can be any of the

following:
n Modifying the device configuration or parameters.
n Adding or removing a module that can be added or
removed.
n Modifying any of the PGM master parameters such as baud
rate, station address, and so on. In this scenario, all field
devices are reconfigured. The following figure displays a

111
 Chapter 6 - Protocol Block

sampleBus Parameters page.

Guidelines for using the Configure In Runtime (CiR) /

Hot Configuration in Run (HCiR) feature
The following list summarizes the guidelines that you must
follow to use the CIR/HCIR feature.
n Hot Configuration in Run is possible when both the
PROFIBUS master and the PROFIBUS devices support this
feature.
n Neither Configuration in Run nor Hot Configuration in Run
supports the change of parameters or settings which are
global for all responders. This means parameters like the
bus speed, the global watchdog, target token rotation time
and so on cannot be changed using HCiR.
n If the PROFIBUS device supports HCiR, you must consult
the PROFIBUS device’s vendor documentation to know
about the setup that is required to support HCiR on the
responder.
n To use the HCiR feature, you must ensure that all
responders which support HCiR have reserved areas
configured. While configuring the responders in "Profibus
Network Configuration Tool", it is recommended that you
add reserved input and/or output memory area to the
responders and lock the responders (Ensure that you lock

112
Chapter 6 - Protocol Block

the inputs and outputs separately). This helps you to add

modules without unlocking the responders. The length of
the reserved area gets adjusted automatically with the
memory area of the module on insertion of a module.
n The Lock/Unlock features are very important for a
successful configuration of HCiR. It is recommended that
you lock all your responders before modifying the
configuration to use the HCiR feature. This prevents any re-
arrangement of the "Profibus Network Configuration Tool"
address management. Modifying the configuration includes
adding or deleting modules.
n Keep all responders in the Protocol Block locked all the time.
Unlock them when there is no reserved memory area
planned for the device and modification in the configuration
is required. After the modification, lock the responders.
n By default, the addition of a reserved memory area reserves
128 bytes into the memory map of a responder. However the
length/size of the reserved area can be changed manually
based on your requirement.
n If it is likely that complete responders needs to be added
during runtime, these responders needs to be either
planned as responders (set to inactive in "Profibus Network
Configuration Tool" in order to not be expected during
runtime until they are physically attached to the network), or
the Target Token Rotation Time (TTRT) needs to be tuned
upwards already. Both scenarios require a careful planning
by a Profibus expert.
n It is a best practice to review and clear all HCiR related
settings in "Profibus Network Configuration Tool" during a
plant maintenance shutdown to ensure that all
requirements are in place for the next production phase of
the plant and potential HCiR requirements.
n It is recommended that you do not use the Defragment
feature. Though this feature does not affect the locked
responders, it could have an impact if by chance one or
more responders are unlocked when the Defragment button
is clicked.
n It is recommended that you do not modify more than one
responder configuration during a HCiR event.

113
 Chapter 6 - Protocol Block

Support for time synchronization functionality

Time synchronization functionality enables you to synchronize
the clock between the secondary and the primary. When time
synchronization is enabled in the responders, they may use the
timestamp when internally recording the event data. This
functionality is supported on a device when "Time_Sync_supp"
is equal to 1 in the GSD file.
An additional configuration page named "TimeSync" is included
to the PGM master DTM and the responder DTM.
To overwrite the clock interval configured for each responder by
a common value that is valid for all responders, the following
parameters must be configured in the "TimeSync" page.
n Overwrite Clock Sync Interval setting for all responders with
Time Sync support
n Clock Sync Interval
To enable the time synchronization functionality in the
responders, an additional configuration page named "DPV2" is
included to the PGM responder DTM. Time synchronization
configuration for a responder is required only when it is not
configured in the master.

ATTENTION: If the Overwrite Clock Sync Interval setting for all

slave with Time Sync support check box is enabled, the Clock
Sync Interval parameter cannot be modified and a warning
message appears in the responder DTM.

The following parameters must be configured for each

responder to enable the time synchronization.
n Activate Time Sync
n Clock Sync Interval
The value of this parameter varies based on the device type.
For more information about the supported value, see the
device-specific manual.

Configuring time synchronization in PGM master DTM

To maintain a common time for all responders, configure time
synchronization in the PGM DTM.

114
Chapter 6 - Protocol Block

To configure time synchronization in PGM DTM

1. Double-click the Protocol block. The Protocol block’s
configuration form appears.
2. On the Field Network Configuration tab, double-click the PGM
master. The "Profibus Network Configuration Tool" window
appears.

3. In the Navigation Area, click Time Sync.

4. On the right pane, select the Overwrite Clock Sync Interval
setting for all slaves with Time Sync support check box. It is
recommended that the Overwrite Clock Sync Interval setting for
all slaves with Time Sync support check box is always enabled
because the time interval configured in the master always
overrides the time interval configured at responder level.
5. Enter the value in the Clock Sync Interval box. The time base
for this parameter is 10 ms.
6. Click Apply > OK.
7. Click OK.

Configuring time synchronization in responder

Prerequisites
To enable time synchronization for a PROFIBUS device, "Time_
Sync_supp" must be set as 1 in the responders GSD file.

115
 Chapter 6 - Protocol Block

To configure time synchronization in responder

1. Double-click the Protocol block. The Protocol block’s
configuration form appears.
2. On the Field Network Configuration tab, double-click the PGM
master. The "Profibus Network Configuration Tool" window
appears.

3. In the Navigation Area, click DPV2.

4. On the right pane, select the Activating Time Sync check box.
5. Enter the value in the Clock Sync Interval box. The time base
for this parameter is 10 ms.
6. Click Apply > OK.
7. Click OK.

Export/import of field network configuration

The field network configuration that is performed through the
"Profibus Network Configuration Tool" in the Field Network
Configuration tab of the Protocol Block is stored as a .dat file.
The "Profibus Network Configuration Tool" enables you to
export and import this file from/into the Field Network
Configuration tab of the Protocol Block.
The export functionality enables you to export/copy the field
network configuration through the "Profibus Network

116
Chapter 6 - Protocol Block

Configuration Tool". The exported or copied file is stored as a

.dat file. You can save this file in any location.
The import functionality enables you to import the field network
configuration through the "Profibus Network Configuration
Tool". If you already have a network configuration performed
and you import another configuration, the existing
configuration is overwritten by the imported configuration.

Exporting field network configuration

Perform the following steps to export field network configuration

1. Navigate to the Field Network Configuration tab of the
Protocol Block in which you have performed the field
network configuration.

2. Click Export on the Field Network Configuration tab toolbar.

The Save As dialog box appears.
3. Select the location where you want to store this .dat file.
4. Type a name for the configuration file.
5. Click Save.

Importing field network configuration

When you perform an import of the field network configuration,
the existing configuration that you have performed, if any, is
replaced by the imported configuration.

Perform the following steps to import field network

configuration
1. Navigate to the Field Network Configuration tab of the
Protocol Block to which you want to import the field network
configuration.

2. Click Import on the Field Network Configuration tab

toolbar. If a PDC in the existing configuration is assigned to
a PIOMB, you cannot import the field network configuration
and an error message appears. The Open dialog box
appears.
3. Select the .dat file of the field network configuration that
you want to import.

117
 Chapter 6 - Protocol Block

4. Click Open. The field network configuration is copied to the

"Profibus Network Configuration Tool" Network view.

Audit Trail for field network configuration

The Audit Trail tab is available in the Protocol Block
configuration form only if the PGM block is under QVCS. This
tab displays the Audit Trail data in a readable format and is
available both from the Project view and the Monitoring view.
This tab is also available from the Protocol Block detail display.
The following list illustrates some of the properties of the Audit
Trail tab.
n The Audit Trail information appears only if the PGM block is
under QVCS.
n The Audit Trail information does not appear for the first
checked-in version irrespective of the version number.
n Each version (other than first checked-in version) will have a
set of sessions. A session implies to the time period during
which the Field Network Configuration tab of the Protocol
Block is opened and closed. Each session is identified by a
unique session ID along with the logged in user name. If you
make any changes to the network configuration during a
session, the changes that you have made appears under the
respective session.
n The - /+ buttons in the Audit Trail tab can be used to
expand/collapse Audit Trail information of each version as
well as the session.
The following figure illustrates a sample Audit Trail tab of the
Protocol Block.

118
Chapter 6 - Protocol Block

In the above example, version V1.00 does not display any Audit
Trail information because this is the first checked-in version of
the PGM block.
The version V2.00 displays the detailed configuration changes
that are done during session 1.
The version V3.00 does not display any Audit Trail information
as no configuration changes are done in this version.
The version V4.00 displays the configuration changes done
during session 2.

Operations that impact Audit Trail

Some of the following Control Builder operations impact the
visibility of the Audit Trail tab.

QVCS Revert to Version

During QVCS Revert to Version operation, one version of
AUDITTRAIL parameter value is replaced with another version
of AUDITTRAIL parameter value.
For example, if you have made changes in the network
configuration during V4.00 and then you perform a QVCS
Revert to Version 3.00, then Audit Trail information will be

119
 Chapter 6 - Protocol Block

available only for the network configuration changes that you

made till V3.00.

QVCS Compare
When you perform a QVCS Compare operation, the Diff Tool
displays the ERDB AUDITTRAIL parameter in highlighted mode.
The status appears as “M” if the data has been modified
between the selected versions. In addition, the message "Please
refer to module properties of this block to see the parameter
value" appears in the parameter value.

ATTENTION: QVCS does not support "Profibus Network

Configuration Tool" AUDITTRAIL parameter for parameter
value comparison between versions in the Diff Tool.

Import
When you perform an Import of a PGM block, the Audit Trail tab
is visible only if the PGM block is under QVCS. If the PGM block
is not under QVCS, the Audit Trail tab is not visible.

Monitoring Protocol Block

TIP:
In this section, the state and command parameters of the
are listed for quick reference. For detailed information
about these parameters, you need to refer to the
PROFIBUS Gateway Module Parameter Reference guide.

Protocol Block state after configuration and load

When the PGM block is loaded, the Protocol Blocks are also
loaded along with the PGM block.

Main tab
The PB Link State (STATE) will be "ONLINE" after the successful
load of the Protocol Block. Also, the PROFIBUS Master section
will display the appropriate firmware version and date, boot
version, and CPU load.

120
Chapter 6 - Protocol Block

Field Network Status tab

n The Field Network Master State (MASTERSTATE) will be
"OPERATE."
n The Field Network State (BUSTATE) will be "RUNNING" if the
PGM is communicating with at least one PROFIBUS device.
Otherwise, the status will be "STOPPED." If the network
configuration is not created, the status will be "IDLE."
n The Slave State (SLAVESTATE) will be "OK" indicating that
the master is in cyclic data exchange with all the configured
PROFIBUS devices. If there is at least one PROFIBUS device
missing or if the PROFIBUS device has a diagnostic request
pending, the status will be "FAILED."
n Global State Field (GLOBALSTATE) - If there is a notified
error at the PROFIBUS master or the PROFIBUS devices, the
respective LED will appear in red. For example, if the
PROFIBUS network cable is disconnected from the PGM, the
NON-EXCHANGE-ERROR LED will appear red.
The Error and Responder Details section will display the
number of configured PROFIBUS devices and the number of
active PROFIBUS devices in the network. Also, it will display the
number of diagnostic issues, if any.

Slave Status tab

The Slave Status tab will display the PROFIBUS device status
with the corresponding LEDs.
n If the PROFIBUS devices are communicating with the
PROFIBUS master, the corresponding LEDs will appear
green.
n If the PROFIBUS devices are in a fault state, the
corresponding LEDs will appear red.
n If the PROFIBUS devices have diagnostics, the
corresponding LEDs will appear yellow.

Protocol Block status parameters

PBLink State (STATE)

The STATE parameter displays the state of the Protocol Block.

121
 Chapter 6 - Protocol Block

Field Network Master State (MASTERSTATE)

The MASTERSTATE parameter displays the state of the field
network master.

Slave State (SLAVESTATE)

The SLAVESTATE parameter indicates whether the master is in
cyclic data exchange to all the configured PROFIBUS devices.

Field Network State (BUSSTATE)

The BUSSTATE parameter indicates the current network status
of the communication channel.

Global State (GLOBALSTATE)

The GLOBALSTATE parameter serves as a collective display of
the global notifications. The notified errors can occur either at
the PROFIBUS master itself or at the PROFIBUS devices.

Protocol Block command parameters

Compact Non-Volatile Storage (COMPNVSCMD)

The COMPNVSCMD parameter indicates whether to compact
the non-volatile memory or not.

Protocol block statistics parameters

The DPV1 Statistics tab is added in the Protocol block’s
configuration form for monitoring the DPV1 statistics
information. The statistics information related to the DPV1
connection is monitored from the Class 2 Connection Status
table.

DPV1 Bytes per sec (DPV1BYTESPERSEC)

The DPV1 Bytes per sec (DPV1BYTESPERSEC) parameter
provides the DPV1 traffic in bytes per second per link level.

DPV1 Requests per sec (DPV1REQSPERSEC)

The DPV1 Requests per sec (DPV1REQSPERSEC) parameter
provides the DPV1 traffic in requests per second (HOP and
DPV1) per link level.

122
Chapter 6 - Protocol Block

DPV1 Connection Status (DPV1CONNSTS)

The DPV1 Connection Status (DPV1CONNSTS) parameter
provides the DPV1 connection status of the PROFIBUS devices.

DPV1 Connection Ref ID (DPV1CONNREF)

The DPV1 Connection Ref ID (DPV1CONNREF) parameter
displays the DPV1 connection ID for a responder.

ATTENTION: A valid connection ID is displayed only when

the DPV1 connection status to a responder is set as
“Connected.”

DPV1 Req last error code (LASTERRCODE)

The DPV1 Req last error code (LASTERRCODE) parameter
displays the last error code received for DPV1 connection to a
responder.
For more information about the connection status of DPV1
request, see PROFIBUS Gateway Module Parameter Reference.

Protocol Block icons

The following table summarizes the various appearances that a
Protocol Block icon can assume based on view and current
Protocol Blockstate.

If Icon is... Then it indicates...

Project view

gray Protocol Block a is associated with configured

PGM.

Monitoring
view

green Protocol Block is active.

123
 Chapter 6 - Protocol Block

If Icon is... Then it indicates...

red Protocol Block is in a failed state.

Protocol Block notifications

When the Protocol Block is active, it generates the following
notifications.

Notification Description

Field Network This notification is generated when the

Failure PROFIBUS master has lost connection to all
PROFIBUS devices.

Field Network After the Protocol Block is downloaded, the CRC

Configuration sum of the parameter NETCONFBIN is
Failure calculated. It is then compared to the
NETCONCRCSUM parameter which was
calculated by the tools. In there is a mismatch in
this comparison, this notification is generated.
You must modify and reload the field network
configuration for this notification to return to
normal.

Field Network After the Protocol Block downloaded, the CRC

Tag Table sum of the parameter NETTAGTABLEBIN is
Failure calculated. It is then compared to the value that
was loaded along the NETTAGTABLEBIN
parameter. If there is a mismatch in this
comparison, this notification is generated. You
must modify and reload the field network
configuration for this notification to return to
normal.

Input Data The input data is sampled on every Process Data

Base Cycle Access (PDA) base cycle, which is the smallest
Changed raw data cycle seen in PDA opens. The data
delivery time which is the time consumed

124
Chapter 6 - Protocol Block

Notification Description

between process data read from the PROFIBUS

network to the end of triggering PDA transport is
measured on every cycle. The new data sample
time is calculated based on the data delivery
time and the start time of the earlier sample. If
the data delivery time is longer than minimum
cycle (5 ms), the next sample will be delayed so
that there is always a minimum of 5 ms time
from the end of data delivery to the start of the
next sample. If the data delivery takes more than
the minimum cycle (5 ms) on three consecutive
cycles, this notification is generated. This
notification returns to normal when the data
delivery time has been below minimum cycle
(5ms) on three consecutive cycles. To recover
from this, you must reduce either the number of
PIOMB connections or the input data read cycle
defined in the PIOMB block.

Monitoring the field network configuration

You can monitor the PROFIBUS master and the PROFIBUS
devices online from the Project view or the Monitoring view.
You can perform the following functions while monitoring the
PROFIBUS master and/or responder devices.
n View the PROFIBUS master's diagnosis and extended
diagnosis
n View the status of all PROFIBUS devices
n View the PROFIBUS devices from the Life List menu
n Change the PROFIBUS device address
n View the PROFIBUS device's diagnosis
n View the PROFIBUS device's extended diagnosis

ATTENTION: To perform any of these actions, the devices

that must be monitored must be assigned to the hardware.
See Assigning the device to the correct hardware.

125
 Chapter 6 - Protocol Block

Viewing the master's diagnosis and extended

diagnosis

Perform the following steps to view the PROFIBUS master's

diagnosis and extended diagnosis
1. Click the Field Network Configuration tab of the Protocol Block
in which you have configured the master and the PROFIBUS
device.
2. Right-click the PROFIBUS master and select Connect. If you
have not assigned the device to the hardware, an error
message appears. The master is highlighted as displayed in
the following figure.

You must right-click the PROFIBUS master and select

Disconnect to discontinue monitoring the master online.
3. Right-click the PROFIBUS master and select Diagnostic. The
Diagnostics form appears. The General Diagnosis menu is
selected by default. You can view the general diagnostics
such as device state, network state, configuration state,
watchdog time, and error count.
4. Select the Master Diagnosis menu in the Navigation Area to
view the master diagnostics. The Master Diagnosis provides
information such as on the PROFIBUS device status,
number of active PROFIBUS devices, number of configured

126
Chapter 6 - Protocol Block

PROFIBUS devices, and number of PROFIBUS devices that

have diagnostics.
5. Similarly, you can select the appropriate diagnosis menus in
the Navigation Area to view the appropriate diagnostics.
6. Click OK.

127
 Chapter 6 - Protocol Block

Viewing the status of all PROFIBUS devices from the

Profibus Network Configuration Tool Network view

Perform the following steps to view the status of all PROFIBUS

devices from the Profibus Network Configuration Tool Network
view
1. Click the Field Network Configuration tab of the Protocol Block
in which you have configured the master and the PROFIBUS
device.
2. Right-click the master and select Start Debug Mode. The
status of each device appears in the "Profibus Network
Configuration Tool" Network view as displayed in the
following figure.

The symbol indicates that the PROFIBUS device is not

connected.

128
Chapter 6 - Protocol Block

Viewing the PROFIBUS devices from the Life List

menu
Right-click the master and select Addition Functions > Life List
The Life List window displays the PROFIBUS devices that are
connected to the network.

Changing the device address from the Set Station

Address menu
Some of the PROFIBUS devices such as the Siemens
SIMOCODE Pro C do not have the physical switch that is used
to set the address of the PROFIBUS device. In such cases, you
can change the PROFIBUS device address from the Field
Network Configuration tab of the Protocol Block.

129
 Chapter 6 - Protocol Block

Perform the following step to change the device address from

the Set Station Address menu
1. Click the Field Network Configuration tab of the Protocol Block
in which you have configured the PROFIBUS device and the
master.
2. Right-click the master and select Addition Functions > Set
Station Address. The Set Station Address dialog box appears.
The following figure displays the Life List window
when the address is 10.

3. Type the new station address in the New station address box.
4. Click Set Address. If the change is successful, you can view
the new station address in the Life List window. The
following figure displays the station address as 15 after
changing

130
Chapter 6 - Protocol Block

the address.

Detecting PROFIBUS devices in the network

You can detect all the physical PROFIBUS devices in the
network from the Field Network Configuration tab of the
Protocol Block. This can be accomplished by performing a
Network Scan. This scan lists all the physical PROFIBUS
devices connected to the network. In addition, you can add a
PROFIBUS device to the network, if the device is not added to
the network.

Perform the following steps to detect all PROFIBUS devices in

the network
1. Click the Field Network Configuration tab of the Protocol Block
in which you have configured the PROFIBUS master and the
PROFIBUS device.
2. Right-click the master and select Network Scan. If you have
not assigned the device to the hardware, an message
appears. The netDevice window appears as displayed in the
following figure. This window lists all the physical devices
that are present in the network and also the details of the

131
 Chapter 6 - Protocol Block

devices.

3. If you want to add a device to the network, select Add from

the Action column.
l If the device is already added to the network, the value

Skip appears in the Action column.

l If you want to replace a device with another device, select

Replace in the Action column.

4. Click OK.

Viewing the PROFIBUS device diagnosis

Perform the following steps to view the PROFIBUS device

diagnosis
1. Navigate to the Field Network Configuration tab of the
Protocol Block in which you have configured the PROFIBUS
device and the PROFIBUS master.
2. Right-click the PROFIBUS device and select Connect. You
must right-click the PROFIBUS device and select Disconnect
to discontinue monitoring of the PROFIBUS devices online.
The PROFIBUS device appears highlighted as displayed in

132
Chapter 6 - Protocol Block

the following figure.

3. Right-click the PROFIBUS device and select Diagnostic. The

Diagnostics configuration form appears. The Diagnosis
menu in the Navigation Area is selected by default. The
PROFIBUS Device and the Watchdog On LEDs must be
green during normal conditions.
4. Click OK.

Viewing the PROFIBUS device's extended diagnosis

Perform the following steps to view the PROFIBUS device's

extended diagnosis
1. Navigate to the Field Network Configuration tab of the
Protocol Block in which you have configured the PROFIBUS
device and the master.
2. Right-click the PROFIBUS device and select Connect. You
must right-click the PROFIBUS device and select Disconnect
to discontinue monitoring of the PROFIBUS devices online.
The PROFIBUS device appears highlighted as displayed in

133
 Chapter 6 - Protocol Block

the following figure.

3. Right-click the device and select Diagnostic. The Diagnostics

page appears. The Diagnosis menu in the Navigation Area is
selected by default.
4. Select the Extended Diagnosis menu in the Navigation Area to
view the extended
diagnostic details, if any.

The extended diagnostic message of the Siemens Simocode

Pro C device is used for illustrating the diagnostic message.
5. Click OK.

134
Chapter 6 - Protocol Block

QVCS - Diff Tool view of non-human readable

data
When you compare differences between two versions of a PGM
block, the Diff Tool does not display the value for the
parameters that have “non-human readable” binary data or
data that is not readily understandable by users. Instead, the
message “Please refer to module properties of this block to see
the parameter value” appears for these parameters in the Diff
Tool. This is applicable for the following internal parameters of
the Protocol Block.
n NETCONF
n NETCONFXML
n NETTAGTABLE
n NETTAGLIST
n SDN_AUDITTRAIL
n AUDITTRAIL
The following figure illustrates a sample Diff Tool view when
there is a difference in the parameters values between the two
versions.

135
 Chapter 6 - Protocol Block

Protocol Block station displays

Detail displays and faceplate names
The following table lists the names of the details display and
faceplate of the Protocol Block.

Tab Name Detail Display Faceplate

Main tab sysdtlPBLINKa.htm ssysdtlPBLINKa_

fp.htm

Status tab sysdtlPBLINKb.htm

Field Network Status sysdtlPBLINKc.htm

tab

Configuration sysdtlPBLINKd.htm
Details tab

Calling up the displays

The following table lists the actions that you must perform to
call up the Protocol Block detail displays.

To call the
Protocol Then …
Block…

Main tab Type the PBLINK point name (for example PBLINK_
display 132) in the Station command zone and press F12. You
can also click the Search icon in the Station

toolbar and type the point name and click OK.

Slave Click the Slave Status tab.

Status tab
display

Field Click the Field Network Status tab.

Network
Status tab
display

136
Chapter 6 - Protocol Block

To call the
Protocol Then …
Block…

Config Click the Config Details tab.

Details
tab
display

Detail display tabs

Main tab
The Main tab detail display provides information such as the
name of the point detail display, group detail display, and the
faceplate.

You can modify the following value from the Protocol Block
Main tab detail display.
n Alarm Enable State.
Slave Status tab
The number of LEDs displayed in the Slave Status tab detail
display refers to the maximum number of PROFIBUS devices
that can be connected to a single Protocol Block. You can
monitor the status of the configured devices from the Slave
Status tab detail display.

137
 Chapter 6 - Protocol Block

From the detail display, you can interpret the status of the
devices based on the following LED colors.
n Red - Configuration error/device not present.
n Yellow - Diagnostic data available.
n Green - Device is healthy and running.
n Black - Device not configured.
You cannot modify any values from the Slave Status tab detail
display.
Field Network Status tab
The Field Network Status tab detail display provides
information on the global notifications.
From the detail display, you can interpret the global state of the
devices based on the following LED colors.
n Black - No global state errors.
n Green - Global state error.
n Gray - The global state parameter value is "Bad."
Detail display of Field Network Status

138
Chapter 6 - Protocol Block

You cannot modify any values from the Field Network Status
tab detail display.
Config Details tab
The Config Details detail display is identical to the Main tab of
the Protocol Block (from Control Builder).

You can modify the following value from the Protocol Main tab
detail display.

139
 Chapter 6 - Protocol Block

n Alarming Enabled.

140
CHAPTER

7 PROFIBUS CONFIGURATION TOOLS

In this section:

Accessing PROFIBUS Configuration Tools 144

Configuring responders/modules 146
Validating and saving configuration 171
Troubleshooting scenarios 174

141
Chapter 7 - PROFIBUS Configuration Tools

PROFIBUS Configuration Tools (Auto-configure Slaves) is a

project engineering productivity tool that can be used for
automatically creating and configuring responders of a
PROFIBUS segment. The responder blocks include DSB,
PIOMB, and PBHIOMB blocks. However, HART channels
(PBHCHANNEL) must be manually configured after auto-
configuring PBHIOMBs.The Auto-configure Slaves feature
removes double-data entry during configuration and reduces
the risk of human failures. Furthermore it enables the
enforcement of a best practice configuration.
This flow chart explains the steps to be performed to
automatically create and configure responders.

142
 Chapter 7 - PROFIBUS Configuration Tools

S TA RT

C on figu re slaves in
P R O FIB U S N etw ork
C on figu ration Too l

Is
P R O FIB U S
C on figu ration
Too ls add in NO
enab led
in C on trol E nab le P R O FIB U S
Rule file repository B uilde r? C on figu ration Too ls
add in
YE S

Open Auto-Configure
Rule file Slaves and provide required
input and pe rform valida tion

C orr ect err ors or

Is the f orm w arning s listed in S tatus
da ta D esc ription colum n
valida tion
succ ess?

Verify S ta tu s colum n an d
NO S tatus D esc ription
YE S
colum n
S ave t he valida ted
con figu ration t o E RD B

S TO P

Flow chart
Note that the Auto-configure Slaves option does not permit the
following:

143
Chapter 7 - PROFIBUS Configuration Tools

n PROFIBUS Gateway Module (PGM) or Protocol block

creation.
n PBHChannel or DD assignment.

Accessing PROFIBUS Configuration Tools

The PROFIBUS Configuration Tools add-in is integrated with
Control Builder and can be invoked from the Tools menu.

ATTENTION: If PROFIBUS Configuration Tools add-in is

disabled in the Add-in Manager menu, the Auto-configure
Slaves option is disabled in all instances.

The following figures display how to enable PROFIBUS

Configuration Tools add-in and the Auto-configure Slaves
option.Enabling PROFIBUS Configuration Tools

To access the Auto-configure Slaves option, PROFIBUS

Configuration Tools add-in must be activated in the Add-in
Manager menu. The Auto-configure Slaves option can be
accessed through one of the following methods.
n Click Tools > Auto-configure Slaves
n Right-click Protocol block > Auto-configure Slaves
n From the List View, right-click Protocol block > Auto-configure
Slaves

144
 Chapter 7 - PROFIBUS Configuration Tools

Auto-configure Responders

Legend Description

1 Available from Tools menu

2 Available from the context right-click menu

3 Available from List View

The following figure displays the Auto-configure Slaves window.

Auto-configure Slave

145
Chapter 7 - PROFIBUS Configuration Tools

Configuring responders/modules
The PROFIBUS Configuration Tools add-in creates and
populates related blocks and modules for each configured
responder according to the rules defined in the selected rule
file. The Auto-configure Slaves option also creates the PDC and
assigns net tags to PDC types as defined in the rule file.
Before auto-configuring responders or modules, perform the
following tasks.
1. Verify that the GSD file is available for a specific responder
2. Configure responders in the "Profibus Network
Configuration Tool "
3. Request the rule file(s) if the default rule files are not
sufficient for your project

Rule files
The rule file is an XML file for instructing the Auto-configure
Slaves option to create the DSB, PIOMB, and PBHIOMB blocks
according to the responder configuration in the "Profibus
Network Configuration Tool "
The Auto-configure Slaves option requires a rule file to
automate the object creation for a responder. A rule file is
associated with a specific GSD version; therefore any rule file
can only be used with a responder created with the same GSD
file.
There can be one or more rule files defined for a particular GSD
file. This option helps you create different configurations for
different responders from the same GSD file. You can select the
rule file to be used for the Auto-configure Slaves operation.
In addition, a single physical rule file can be associated with a
family of similar GSD files. This must be done through virtual
file linking/shortcuts.
The rule files must be saved at the location:
C:\ProgramData\Honeywell\Experion PKS\PBRuleFiles.
By default, the rule file is selected for each responder if only
default rule file exists for the responder. In addition, different
rule files can be selected for each responder. If the rule files are
not saved at the default location, the default rule file name is
empty in the Rule File column.

146
 Chapter 7 - PROFIBUS Configuration Tools

The following figure is graphical structure of the rule file.

S lave

Co mm on M odule s

Tem plate M odu leN am e

N am e

D esc M odu leID

AssocAsset IsValid

D SBB yteO rde r PDC

D evice Type P D CType

A lm E nb S tate P DCD esc ription

C on B rS up Tim e BuildPIOMB

C on B rks up Tm NwD ow n BuildPBHIOMB

S lotO ffS etInS yC on BuildPDC

E nab leR IO P rof PDCSubscriptionRate

Igno rE xtDi ag O vrflo IsValid

E nab le PA Di ag H oldO nFail

AS IS eg m en t
S tatusA larm Lim it

P DCDi rection
ControlMode

N um C hanne l
U ser A larm s *

C hanne l *
Di ag A larm s

PBHIOMB *
DPV1Params

DPV1Param*

Rule file structure

Creating rule file from a template

The rule file template is available at the location:
C:\ProgramData\Honeywell\Experion PKS\PBRuleFiles
and can be configured to create rule files for each responder
configured in the "PROFIBUS Network Configuration Tool."

Prerequisites
Rule file template is available.

147
Chapter 7 - PROFIBUS Configuration Tools

To create the rule file from a template

1. Create a copy of the "PBRuleTemplate.xml" available at
C:\ProgramData\Honeywell\Experion
PKS\PBRuleFiles
2. Rename the file name as described in the topic Guidelines
for naming a rule file.
3. Open the existing rule file in an XML editor or in Notepad,
and update elements marked as "Mandatory." The following
elements must be configured in the rule file.
l TemplateName

l ModuleName

l IsValid

l BuildPIOMB

l BuildPBHIOMB

l PDCType

l PDCDirection

4. Save the rule file at the default location.

5. Repeat this procedure to create multiple rule files for each
responder.

Guidelines for naming a rule file

The following guidelines must be adhered to when naming a
rule file.
n The first part of the rule file name must match the GSD file
name of the associated device type (this includes the file
extension).
n Add an additional character as a suffix to the GSD file name
separated by a delimiter (_). The default rule file template
contains “Default” as the prefix.
n Store the rule file with the file extension of “.rul.xml.”
The default rule file is defined as “GSDFILENAMEWITHEXT_
Default.rul.xml.” An additional rule file can be created with a file
name of “GSDFILENAMEWITHEXT_userdefinedword.rul.xml.”
The following table lists a few examples of naming the rule file.

Table 7-1: Naming convention for rule files

148
 Chapter 7 - PROFIBUS Configuration Tools

Default rule file Additional rule file

GSD file name
name names

HIL_7404.GSD HIL_7404.GSD_ HIL_7404.GSD_

Default.rul.xml Version2.rul.xml

HIL_7404.GSD_
Version3.rul.xml

T203FF9F.gse T203FF9F.gse_ T203FF9F.gse_

Default.rul.xml rev1.rul.xml

T203FF9F.gse_
rev2.rul.xml

T203FF9F.gse_
rev3.rul.xml

Guidelines for configuring rule file

The following points must be remembered while configuring
the rule file.
n Each net tag must have a corresponding PDC defined in the
rule file. If you do not want to configure PDC for the
available net tags, the "IsValid" element must be set as
"FALSE."Scenario 1: Consider that a module has a single
input net tag configured in the Module configuration page
of the "PROFIBUS Network Configuration Tool." In this case,
the rule file must have a single PDC definition and the
"PDCDirection" must be configured as "Input." Similarly, if a
module has a single output net tag configured in the
Module configuration page of the "PROFIBUS Network
Configuration Tool." In this case, the rule file must have a
single PDC definition and the "PDCDirection" must be
configured as "Output."Scenario 2: Consider that a module
has multiple input and output net tags configured in the
Module configuration page of the "PROFIBUS Network
Configuration Tool." In this case, the rule file must have
corresponding PDC definition and the "PDCDirection" must
be configured as "Input" and "Output," respectively for each
net tag.
n Rule file validation does not verify the parameter
configuration errors. For example, if any parameter is

149
Chapter 7 - PROFIBUS Configuration Tools

configured with an invalid value, the specific parameter is

not saved into the ERDB.
n If any of the parameter is not applicable for a particular
DSB, it is recommended to delete the parameters in the rule
file. If any parameter is left blank, validation error is reported
while launching the Auto-configure Slaves.
n You can use the check box for creating PIOMB and
PBHIOMB in the Auto-configure Slaves irrespective of the
rule file configuration. However, the changes made in the
Auto-configure Slaves do not have any impact to the rule
file.

Elements configured in a rule file

In a rule file, responder is the first element and indicates that
the rule file is specific to a responder configured in Field
Network Configuration tab. This responder element includes the
following elements.
1. GSD-file
2. Common
3. Modules
Each of these elements contains a subset of elements. The
following table explains about each element up to third level.
However, you may also configure elements based on your
requirement for each module.

Table 7-2: Elements configured in a rule file

Top level Second level Third level

Descripti
elements elements elements
on
GSD-file Specifies
the GSD-
file name
of a
respond
er
configur
ed in
Field

150
 Chapter 7 - PROFIBUS Configuration Tools

Top level Second level Third level

Descripti
elements elements elements
on
Network
Configur
ation
tab.

Common Creates
a DSB
and the
paramet
ers that
must be
configur
ed based
on the
basic
informati
on
available
on the
Field
Network
Configur
ation
tab.

TemplateName Specifies
a name
for the
template
of the
DSB to
be
created
for a
particula
r
respond
er

151
Chapter 7 - PROFIBUS Configuration Tools

Top level Second level Third level

Descripti
elements elements elements
on
configur
ed at the
correspo
nding
respond
er
address.

Desc Specifies the

DSB description
that can be
viewed on the
Main tab of the
DSB
configuration
form.

AssocAsset Specifies the

associated asset
for a DSB and
can be viewed on
the Main tab of
the DSB
configuration
form.

DSBByteOrder Specifies the

DSB byte order
that can be
Little-endian or
Big-endian.
DSBByteOrder is
applicable only
for GENDSB and
GENIODSB.

DeviceType Specifies the

device type that
can be viewed on

152
 Chapter 7 - PROFIBUS Configuration Tools

Top level Second level Third level

Descripti
elements elements elements
on
the Main tab of
the DSB
configuration
form.

AlmEnbState Specifies the

Alarming
Enabled state of
DSB that can be
viewed on the
Main tab of the
DSB
configuration
form.

Specifies the
ConBrSupTim DPV0 Connection
e breakout time of
DSB that can be
viewed on the
Main tab of the
DSB
configuration
form.

Used for
ConBrksupTm specifying
NwDown whether the
connection break
timeout is
applicable for
Network down or
not. The
connection break
timeout can be
viewed on the
Main tab of the
DSB

153
Chapter 7 - PROFIBUS Configuration Tools

Top level Second level Third level

Descripti
elements elements elements
on
configuration
form.

Specifies the slot

SlotOffSetInS offset that is
yCon applicable only
for GENDSB and
GENIODSB.

Specifies if the
EnableRIOPro status of RIO
f Profile of DSB is
enabled and can
be viewed on the
Alarm tab of the
DSB
configuration
form.
EnableRIOProf is
applicable only
for GENDSB and
GENIODSB.

Specifies if the
IgnoreExtDiag extended
Overflo diagnostic
overflow is
enabled and can
be viewed on the
Alarm tab of the
DSB
configuration
form.
IgnoreExtDiagOv
erflo is applicable
only for GENDSB
and GENIODSB.

EnablePADiag Specifies if the

154
 Chapter 7 - PROFIBUS Configuration Tools

Top level Second level Third level

Descripti
elements elements elements
on
Alarm tab of the
DSB
configuration
form.
EnablePADiag is
applicable only
for GENPADSB
and
GENPAGWDSB.
tab of the DSB
configuration
form.
EnablePADiag is
applicable only
for GENPADSB
and
GENPAGWDSB.

Specifies the
StatusAlarmLi acceptable PA
mit status value.
StatusAlarmLimit
is applicable only
for GENPADSB
and
GENPAGWDSB.

UserAlarms Lists the alarm

configuration
information for
the DSB and that
can be viewed on
the Alarm tab of
the DSB
configuration
form. UserAlarms
is applicable only
for the following

155
Chapter 7 - PROFIBUS Configuration Tools

Top level Second level Third level

Descripti
elements elements elements
on
DSB.

DiagAlarms Lists the device-

specific alarms
for the DSBs and
that can be
viewed on the
DeviceAlarmConf
ig tab of the DSB
configuration
form.

1.
DiagAlarmTyp
e
2.
DiagAlarmNu
mber
3. DiagAlarmHel
pString
4.
DiagAlarmPrio
rity
5.
DiagAlarmSev
erity
6.
DiagAlarmBitI
ndex
7. DiagAlarmBitA
reaSize
8. DiagAlarmBitA
reaValue

DPV1Params Lists the the

DPV1 parameters
for the DSB and
that can be
viewed on the
DPV1Config tab

156
 Chapter 7 - PROFIBUS Configuration Tools

Top level Second level Third level

Descripti
elements elements elements
on
of the DSB
configuration
form.

1. DPV1NumPoll
(Attribute)
2. DPV1NumHig
hPriRe
3. DPV1NumHig
hPriReq
4. DPV1Param
Number
(Attribute)
5. DPV1ReqType
6. DPV1Priority
7. DPV1SlotNum
8. DPV1Index
9. DPV1Length
10. DPV1NumOfD
ataRecords
11.
DPV1DataRec
s
12.
DPV1ParamN
ame
13.
DPV1DataTyp
e
14.
DPV1ByteOffs
et
15. DPV1BitOffset

DPV1Params is
an optional
element. If this
element is not

157
Chapter 7 - PROFIBUS Configuration Tools

Top level Second level Third level

Descripti
elements elements elements
on
provided in rule
file then default
configuration by
DSB will be done.

Modules Specifies
the
module
configur
ation for
a
correspo
nding
module
type
configur
ed on
the Field
Network
Configur
ation
tab.
Multiple
module
elements
can be
present
under
each
module.

If there are no modules configured in the rule file, PDC

configuration is not performed and corresponding modules
(PIOMB or PBHIOMB) are not created.

ModuleName Specifies
the

158
 Chapter 7 - PROFIBUS Configuration Tools

Top level Second level Third level

Descripti
elements elements elements
on
name of
a module
for which
further
rules are
defined.
The
Auto-
configur
e Slaves
option
uses the
defined
rules
when it
finds a
matchin
g
module
name on
the Field
Network
Configur
ation
tab.

ModuleID Specifies the

ModuleId of a
module for which
further rules are
defined. The
Auto-configure
Slaves option
uses the defined
rules when it
finds a matching
ModuleId on the
Field Network

159
Chapter 7 - PROFIBUS Configuration Tools

Top level Second level Third level

Descripti
elements elements elements
on
Configuration
tab.

IsValid Indicates if the

module specified
in the rule file is
a valid
configuration for
a particular
responder. While
configuring the
rule file for
universal
modules, you
must configure
this element as
"FALSE" to
exclude the net
tag configuration
from the rule file.

PDC Specifies the

PDC information
to be configured
for the DSB.
Multiple PDCs
can be present in
a module.

PDCType Specifies the type

of PDC to be
configured for
corresponding
responders in
which the
module is
configured.

Provides a brief

160
 Chapter 7 - PROFIBUS Configuration Tools

Top level Second level Third level

Descripti
elements elements elements
on
PDCDescripti description of the
on corresponding
PDC.

BuildPIOMB Specifies if the

PIOMB must be
created for a
particular module.
This element is
Mandatory/Yes/N
o/Forbidden. By
default it will be
Mandatory, if not
specified in rule
file.

Specifies if the
BuildPBHIOM PBHIOMB must be
B created for a
particular module.
This element is
Mandatory/Yes/N
o/Forbidden. By
default it will be
Mandatory, if not
specified in rule
file.

BuildPDC User can specify

whether the
PIOMB and
PBHIOMB should
be created for a
particular PDC or
not. This element
is
Mandatory/Yes/N
o/Forbidden. By

161
Chapter 7 - PROFIBUS Configuration Tools

Top level Second level Third level

Descripti
elements elements elements
on
default it will be
Mandatory, if not
specified in rule
file. If BuildPDC is
set to "Forbidden",
BuildPIOMB,
BuildPBHIOMB
will be forbidden
regardless of the
specified value at
BuildPIOMB &
BuildPBHIOMB

If "Mandatory" is set in the rule file, the applicable check boxes will
be checked and disabled.

User can specify

PDCSubscript the PDCSUBRATE
ionRate value which needs
to be set for each
PIOMB. This
element is enum
type. By default it
will be set to 50_
ms, if not specified
in rule file. It will be
disabled for output
type of modules.

IsValid Indicates if the

PDC specified in
the rule file is a
valid configuration
for a particular
responder.

HoldOnFail Specifies the state

of the output
modules when

162
 Chapter 7 - PROFIBUS Configuration Tools

Top level Second level Third level

Descripti
elements elements elements
on
there is a
communication
loss with the
controller.

ASISegment Specifies the

segment in PDC
where the ASI
responders are
located.

PDCDirection Specifies the

direction of PDC;
input or output.
Based on this
direction, the net
tag to be
associated with the
particular PDC
type is selected.

NumChannel Specifies the

number of
channels available
within the PDC.

Channel Specifies the

channel
configuration on
the PDC tab of the
DSB configuration
form.

PBHIOMB Lists the the

PBHIOMB
parameters

1.
DirProcDataInd
ex

163
Chapter 7 - PROFIBUS Configuration Tools

The rule file is invalid if one of these elements is not configured

in the rule file, and the Auto-configure Slaves option updates
the Status and Status Description columns.

Modifying the existing rule file

The existing rule file can be modified to create different rule
files for each responder configured in the "PROFIBUS Network
Configuration Tool "

Prerequisites
Rule file is available.

To modify the existing rule file

1. Open the existing rule file in an XML editor or in Notepad,
and update elements marked as "Mandatory."
The following elements must be configured in the rule file.
lTemplateName
l ModuleName

l IsValid

l BuildPIOMB

l BuildPBHIOMB

l PDCType

l PDCDirection

2. Save the rule file at the default location.

Selecting the default rule file in Auto-configure Slaves

If there are multiple rule files available for each responder, the
default rule file can be modified in the Auto-configure Slaves
option if needed.

Prerequisites
Multiple rule files are available.

To select the default rule file in Auto-configure Slaves option

1. Click Tools > Auto-configure Slaves. The Auto-configure
Slaves window appears.
2. Click Browse icon in the Rule File column.

164
 Chapter 7 - PROFIBUS Configuration Tools

3. Browse to the C:\ProgramData\Honeywell\Experion

PKS\PBRuleFiles folder, and select the rule file. The
following figure is an example for selecting a rule file from
multiple files.

4. Click Open. The selected rule file is validated and their

corresponding details updated in the Auto-configure Slaves
option.

Configuring the PROFIBUS device

You can configure device and module separately or together on
the Field Network Configuration tab of the Protocol block using
the "PROFIBUS Network Configuration Tool "

ATTENTION: If you export and import the field network

configuration, you must explicitly save the imported
configuration.

Prerequisites
Ensure that the respective GSD file is available.

165
Chapter 7 - PROFIBUS Configuration Tools

To configure the slaves

1. Double-click the Protocol block.
The Module properties window appears.
2. Click the Field Network Configuration tab, and drag-and-drop
the device from the Library view to the Network view. When
you create a PROFIBUS network configuration, the
PROFIBUS master address is set to 1 and the secondary
address is set to 0, by default. If you have more than one
PGM pair connected to the same physical network, ensure
that there are no other devices with identical addresses in
any of the PGM pairs in the same network.
3. Click OK. The field network configuration is saved to ERDB.
4. Right-click the Protocol block, and click Auto-configure
Slaves. The Auto-configure Slaves window appears.
5. Observe that the Address, Type, GSD Name, and Rule File
columns are automatically updated based on the
"PROFIBUS Network Configuration Tool "
6. Type DSB name in the DSB Name column.
7. Click Validate. The Status column is updated with the
validation results.

Representation of DSB names

The DSB name is automatically generated based on the rule file
configuration, if the name is mentioned in the rule file. The
default DSB name has 16 characters. The DSB name is
represented in Auto-configure Slaves option as follows:
n Default DSB name must have 16 characters.
n First 9 characters specify the first 9 characters of the DSB
template name as specified in the rule file.
n Next 3 characters specify the PGM ID under which the
selected Protocol block appears.
n Next character specifies the Protocol block ID.
n Last 3 characters specify the corresponding device
addresses.

ATTENTION: The DSB name can only be modified before

validating the configuration. The default DSB name

166
 Chapter 7 - PROFIBUS Configuration Tools

appears only if the DSB is not available for the

corresponding device address. However, if a DSB is already
present for the corresponding device address, the DSB
name configured with the correspondingdevice address is
displayed, and it cannot be renamed.

For example, consider that the DSB type is GENIODSB, PGM ID

is 4, Protocol block ID is 1, and the device address is 3. In this
case, the DSB name is displayed as "GENIODSB0041003" in
the DSB Name column.

Configuring the modules

To configure the modules

1. Double-click the Protocol block. The Module properties
window appears.
2. Click the Field Network Configuration tab, and double-click the
responder in the Network view. The Modules menu in the
Navigation Area is selected by default. The Available Modules
section lists all the available modules that can be associated
with the selected PROFIBUS device.
3. Select the modules that you must associate with the
PROFIBUS device.
4. Click Insert. All the modules you selected in the Available
Modules section appear in the Configured Modules section.
When you click Append, the last module you selected is
placed at the end of the Configured Modules list.
5. Click OK to close the Field Network Configuration form. The
field network configuration is saved to the ERDB. If you click
Cancel and close the configuration form, the configuration

is not saved to the ERDB even if you have clicked Save

on the Field Network Configuration tab toolbar.
6. Right-click the Protocol block, and click Auto-Configure
Slaves. The Auto-Configure Slaves window appears.
7. Observe that the Slot, Module, and PDC are automatically
updated for the selected responder based on the
"PROFIBUS Network Configuration Tool."

167
Chapter 7 - PROFIBUS Configuration Tools

8. By default, PDC, PIOMB, PBHIOMB check boxes are

enabled/disabled/checked/unchecked based on the rule
file.
9. Type the PIOMB Name, CEE Name, and the PBHIOMB Name in
the corresponding columns. When the user selects the CEE
Name for the first PDC, by default the same CEE Name is
updated to rest of the PDCs for that responder. If required,
user can change the CEE Name of any PDC manually at any
point of time for that responder. If user changes the CEE
Name for the first PDC, the changes done previously will be
overwritten for that responder. This is just made for user’s
ease of selecting CEE Name for each PDC. If CEE Name is
blank, the Validation will give a warning to the user, but still
save will go ahead and the PIOMB will be created under
Unassigned.
10. Click Validate. The Status column is updated with the
validation results.

Representation of PIOMB names

The PIOMB name is automatically generated based on the rule
file configuration, if the PIOMB name is mentioned in the rule
file. The default PIOMB name has 14 characters. The PIOMB
name is represented in Auto-configure Slaves option as follows:
n First 5 characters specify the PIOMB template name.
n Next 3 characters specify the PGM ID under which the
selected Protocol block appears.
n Next character specifies selected Protocol block ID.
n Next 3 characters specify the device address under which
the corresponding module appears.
n Last 2 characters specify the corresponding PDC number.

ATTENTION: The default PIOMB name can only be

modified before validating the configuration. The default
PIMOB Name appears only when the corresponding PDC is
not already configured. If the PDC is already configured
and a PIOMB is associated with it, the PIOMB name cannot
be edited.

168
 Chapter 7 - PROFIBUS Configuration Tools

For example, consider that the PIOMB template name is

PIOMB, PGM ID is 043, Protocol block ID is 1, device address is
002, and the PDC number is 10. In this case, the PIOMB name
is displayed as "PIOMB043100210" in the PIOMB Name column.

Representation of PBHIOMB names

The PBHIOMB name is automatically generated based on the
rule file configuration, if the PBHIOMB name is mentioned in
the rule file. The default PBHIOMB name has 15 characters.
The PBHIOMB name is represented in Auto-configure Slaves
option as follows:
n First 6 characters specify the template name of PBHIOMB
n Next 3 characters specify the PGM under which the selected
Protocol block appears.
n Next character specifies the Protocol block ID.
n Next 3 characters specify the device address under which
the corresponding module appears.
n Last 2 characters specify the corresponding PDC number.

ATTENTION: The default PBHIOMB name can only be

modified before validating the configuration. The default
PBHIMOB Name appears only when the corresponding
PDC is not already configured. If the PDC is already
configured and a PBHIOMB is associated with it, the
PBHIOMB name cannot be edited.

For example, consider that the PBHIOMB template name is

PBHIOMB, PGM ID is 055, Protocol block ID is 4, device
address is 015, and the PDC number is 15. In this case, the
PBHIOMB name is displayed as "PBHIOMB055401515" in the
PBHIOMB Name column.

Subsequent Update of DSB using Auto Configure

Slave
DSBs created by this tool can be updated later by invoking
Auto-Configure Slaves . Only the below updates are possible for
DSB on subsequent update using Auto-Configure Slaves .

169
Chapter 7 - PROFIBUS Configuration Tools

ATTENTION: DSBs created manually cannot be updated

later by using Auto-Configure Slaves tool.

Adding a new module to the existing DSB

Prerequisites
n The required PDCs must be available in the existing DSB.
n The rule file must be update with the required module
configuration.
To add a new module to the existing DSB using the
Auto-configure Slaves
1. Double-click the Protocol block. The Module properties
window appears.
2. Click the Field Network Configuration tab, and double-click the
device in the Network view.
3. Select the modules that you want to add to the existing
responder.
4. Click Insert. All the modules you selected in the Available
Modules section appear in the Configured Modules section.
When you click Append, the last module you selected is
placed at the end of the Configured Modules list.
5. Click OK to close the Field Network Configuration form. The
field network configuration is saved to the ERDB. If you click
Cancel and close the configuration form, the configuration is

not saved to the ERDB even if you have clicked Save

on the Field Network Configuration tab toolbar.
6. Right-click the Protocol block, and click Auto-Configure
Slaves. The Auto-Configure Slaves window appears.
7. Observe that the Slot, Module, and PDC are automatically
updated for the existing responder based on the changes
made to the "PROFIBUS Network Configuration Tool."
8. By default, PDC, PIOMB, PBHIOMB check boxes are
enabled/disabled/checked/unchecked based on the rule
file.
9. If you are adding the PIOMB and PBHIOMB, type the
PIOMB Name, CEE Name, and the PBHIOMB Name in the

170
 Chapter 7 - PROFIBUS Configuration Tools

corresponding columns. When the user selects the CEE

Name for the first PDC, by default the same CEE Name is
updated to rest of the PDCs for that responder. If required,
user can change the CEE Name of any PDC manually at any
point of time for that responder. If user changes the CEE
Name for the first PDC, the changes done previously will be
overwritten for that responder. This is just made for user’s
ease of selecting CEE Name for each PDC. If CEE Name is
blank, the Validation will give a warning to the user, but still
save will go ahead and the PIOMB will be created under
Unassigned.
10. Click Validate. The Status column is updated with the
validation results.

Parameter update for DSB

n Parameter update is possible only for the parameters which
has external parameter support.
n List of DSB parameters that can be configured using
external parameters are "ChLowRange, ChHighRange,
InputSignalType, OutputSignalType, AISensorType and
AOSensorType".
n Parameter update for these parameters are possible only
when these parameters are already configured with the
support of external parameter. The change happened for
corresponding external parameter will be updated to DSB on
subsequent update using this tool.

Validating and saving configuration

When the validation is running in the Auto-configure slaves
option, the "Mandatory" elements and configuration of
responders and modules are validated and the results are
updated in the Status column. The Status Description column is
updated only if the status is either "Failed" or "Warning."
You can initiate automatic object creation and configuration of
the validated responders only when the responder validation is
marked as "Success" in the Status column. If the Status column
is marked as "Failed" for any selected responder configuration,

171
Chapter 7 - PROFIBUS Configuration Tools

clear the failed responder configuration check box and save the
remaining responder configuration.
For example, consider that one of the mandatory elements in
the rule file is not configured or incorrectly configured. In this
scenario, validation of the rule file for a particular responder
fails and the Status column is marked as “"Failed." Hence, you
cannot save the configuration of all the selected responders
and must clear the check box for the failed configuration.
If the Status column is marked as "Warning" for any selected
responder configuration, you can save the validated
configuration or take any further action based on the warning
message.
For example, consider that you are trying to re-configure a
loaded DSB. In this scenario, validation of the selected
responder is updated in the Status column as "Warning."
Hence, you can either save or make the required changes to the
responder configuration based on the requirement.
The following table lists the various validations performed in
the Auto-configure slave option.

Table 7-3: Type of validations

Validation Type of validation Results

Rule file Rule file validation Finds any missing

validation against rule schema mandatory elements
and mismatch in
data type of
parameters.

Availability of all Validates all configured

the configured modules in the rule file.
modules

Availability of the Validates PDCs that are

PDCs that are required for the
required for the configured net tags.
configure net
tags

PDC type Validates the PDC type

172
 Chapter 7 - PROFIBUS Configuration Tools

Validation Type of validation Results

specified in the rule file

for the specified DSB
type.

Number of PDCs Validates the number of

PDCs for each DSB
type.

User entered DSB name Validates the DSB

data validation entered in the rule
file and the number
of characters of the
entered DSB name.

PIOMB name Validates the PIOMB

entered in the rule file
and the number of
characters of the
entered PIOMB name.

PBHIOMB name Validates the PBHIOMB

entered in the rule file
and the number of
characters of the
entered PBHIOMB
name.

Rule file name Rule file path Validates if the rule

validation This file is selected from
validation is the default path.
performed while
modifying the
rule file.

Rule file naming Validates if the selected

convention rule file satisfies the
guidelines of naming
the rule file.
While saving the validated responder configuration, the DSBs
and the corresponding modules (PIOMB and PBHIOMB) are

173
Chapter 7 - PROFIBUS Configuration Tools

created and updated in the ERDB. The status of the save

operation is updated in the Status Description column.
For more information about the various Status Description, see
Troubleshooting scenarios.
In case of any configuration modification made between
validate and save operations, perform a validation of the
modification before saving the configuration.

Troubleshooting scenarios
The following table lists the validation status description,
cause, and workaround for each rule that is validated.

Table 7-4: Validation errors and workaround

Status Description Cause Workaround

Rule file not found. Selected rule file not Make sure rule file
found in the location is available in the
PBRuleFiles
directory

RuleSchema is not PBRuleSchema.xsd file Make sure Rule file

present in the is not present in schema is present
Engineering "Program in Rule file
Repository (ER) Files\Honeywell\Expe directory. If not,
directory. rion PKS\Engineering contact TAC
Tools \SYSTEM\ER" support.
directory

Error messages Not Applicable Rule file should be

mentioning about corrected.
rule file errors.

Template name Not Applicable 1. Open the

provided in the rule selected rule
file is an invalid DSB file.
template name. 2. Navigate to the
element.
3. Make sure the
TemplateName
mentioned is a
valid DSB

174
 Chapter 7 - PROFIBUS Configuration Tools

Status Description Cause Workaround

template name.

Grouping of Grouping of modules When a responder

modules is supported only for has grouped
supported for the "DSB:GENDSBDP": modules make
provided DSB type. "DSB:GENIODSBDP" sure
"DSB:GENPADSB" TemplateName
"DSB:GENPAGWDSB" provided in the
rule file is either of
the following:
"DSB:GENDSBDP":
"DSB:GENIODSBD
P"
"DSB:GENPADSB"
"DSB:GENPAGWD
SB"

DSB Name: Invalid DSB Name has invalid Correct DSB name
name syntax. syntax. This is existing
an error message.

DSB Name: Existing error message Correct DSB name

InvalidNameLengt h

DSB Name : Illegal Existing error message Correct DSB name

character(s)
encountered

The entered DSB Not Applicable Provide a new DSB

name is not allowed name
as it is a duplicate of
an existing DSB in
the Project/Library
view.

The entered DSB Not Applicable Provide a new DSB

name is not allowed name
as it is a duplicate of
an existing name

175
Chapter 7 - PROFIBUS Configuration Tools

Status Description Cause Workaround

selected for another

DSB/PIOMB/
PBHIOMB.

Number of PDCs Maximum number of l Select a

exceeded for this PDCs exceeded for the different rule
DSB type. The selected DSB type. file with
number of PDC different DSB
supported for each type, which
DSB varies based on allows available
number of
the DSB type.
PDCs, or
l Delete the
exceeded
modules.

PDC configuration Not Applicable Configure PDC for

for this module is the module to
missing in the rule include it in Auto
file. This module is configuration.
excluded from auto-
configuration.

The entered PIOMB Not Applicable Not Applicable

name is not allowed
as it is a duplicate of
an existing PIOMB
in the
Project/Library view.

The entered PIOMB Not Applicable Not Applicable

name is not allowed
because it is a
duplicate name of
an existing DSB/
PIOMB/ PBHIOMB.

The entered Not Applicable Not Applicable

PBHIOMB name is
not allowed as it is a

176
 Chapter 7 - PROFIBUS Configuration Tools

Status Description Cause Workaround

duplicate name of
an existing
PBHIOMB in the
Project/Library view.

The entered Not Applicable Not Applicable

PBHIOMB name is
not allowed as it is a
duplicate name of
an existing DSB/
PIOMB/ PBHIOMB.

PDCType specified Not Applicable Correct the

in rule file is invalid PDCType in the
for this DSB. rule file.

Module Not Applicable Configure the

configuration for module in rule file
this module is to include it in
missing in the rule Auto
file. This module is configuration.
excluded from auto-
configuration.

The module Not Applicable Configure the

configured in the module as valid
rule file has an (Isvalid= true) in
invalid value. This rule file to include
module is excluded it in Auto
from auto- configuration.
configuration.

The PDC configured Configure the PDC

in the rule file has as valid (Isvalid=
an invalid value. This true) in rule file to
module is excluded include it in Auto
from auto- configuration.
configuration.

177
Chapter 7 - PROFIBUS Configuration Tools

Status Description Cause Workaround

Module validation When module None

failed. For more validation failed, this
details, see module message is shown in
configuration status responder grid
description.

Module validation When module None

warning. For more validation gives a
details, see module warning, this message
configuration status is displayed in
description. responder grid.

CEE Name is empty. Not Applicable Select CEE Name

Failed to save Not Applicable None

PIOMB.

Saving of module Not Applicable None

completed.

Not Applicable None

ImportResponderFai
led Desc

Saving of responder Not Applicable None

completed.

NetTags are not Not Applicable None

available for re-
configuration.

Re-configuration of Not Applicable Re-configure the

this DSB is not DSB manually.
allowed as the DSB
was manually
created.

PDC is not checked; Not Applicable Check PDC if

PIOMB and PIOMB and
PBHIOMB will not PBHIOMB needs
be created to be created, in
case it is not set to

178
 Chapter 7 - PROFIBUS Configuration Tools

Status Description Cause Workaround

Forbidden.

179
CHAPTER

8 DEVICE SUPPORT BLOCK (DSB)

In this section:

Device Support Block (DSB) overview 181

About DPV1 read/write messages configuration in DSBs 183
Data processing 188
Generic Device Support Blocks (GENDSB and GENIODSB) 190
Generic Device Support Blocks (GENPADSB and
GENPAGWDSB) for PA devices 192
Generic Drive Device Support Block (DRIVEDSB) 193
CEAG Device Support Block (CEAGDSB) 200
Siemens AS-i Link Device Support Block (Siemens DP/AS-
i-Link DSB) 209
Siemens ET200M Device Support Block (Siemens
ET200M DSB) 214
Turck Excom Device Support Block (Turck Excom DSB) 222
UDT support for DSB blocks 228
Guidelines for configuring DSBs 229
Configuring a Generic Device Support Block 230
Configuring a device-specific DSB 233
About initialization of AO/DO channels from user-defined
values 236
Configuring the PDC 242
Alarms 261
Monitoring DSB block 271
Setting the channel output values from Monitoring view 283

180
Chapter 8 - Device Support Block (DSB)

DSB block station displays 284

Device Support Block (DSB) overview

The Device Support Block represents one of the PROFIBUS field
devices (PROFIBUS devices) in the PROFIBUS network. A single
PROFIBUS network can support up to 124 PROFIBUS devices.
A single DSB can support up to 16 PDCs. However, some DSBs
can support more than 16 PDCs. For example, a CEAGDSB can
support up to 24 I/O modules. DSBs perform the data
conversion to and from device-specific data format (raw data)
to formats supported in ExperionLXPlantCruiseExperion PKS
(PDC format). DSBs also decode field device specific diagnostic
data and report alarms for any notified exception.
The following DSBs are supported by PGM.
n Generic Device Support Blocks ( GENDSB and GENIODSB) -
The Generic DSBs can be configured for any PROFIBUS
devices that do not have device-specific DSBs. You can also
use the Generic DSBs to configure the PROFIBUS devices
that have device-specific DSBs.
n Generic Device Support Blocks (GENPADSB and
GENPAGWDSB) for PA devices - You can use the
GENPADSB and GENPAGWDSB for PROFIBUS PA devices
which are connected either to a PROFIBUS PA Coupler or to
Siemens DP/PA link IM-157.
n Generic Drive DSB (DRIVEDSB) - You can use the DRIVEDSB
for any drive device that supports the PROFIDrive profile.
n CEAGDSB - The CEAGDSB can be configured for the CEAG
LB/FB Remote I/O modules.
n Siemens AS-i Link DSB - The Siemens AS-i Link DSB can be
configured for the DP/AS-i Link 20E and the DP/AS-i Link
Advanced modules.
n Siemens ET200M DSB - The Siemens ET 200M DSB can be
configured for Siemens Simatic I/O modules.
n Turck Excom DSB - The Turck Excom DSB can be
configured only for Turck Excom field devices.

181
 Chapter 8 - Device Support Block (DSB)

ATTENTION: Maximum number of GENDSBs and

GENPADSBs supported for one PGM is 248. However, the
maximum number for other DSBs (GENIODSB,
GENPAGWDSB, DRIVEDSB, CEAGDSB, Siemens AS-i Link
DSB, Siemens ET200M DSB, and Turck Excom DSB) blocks
is limited based on the memory used per DSB block.

Related Concepts
CEAG Device Support Block (CEAGDSB)Generic Drive Device
Support Block (DRIVEDSB)Generic Device Support Blocks
(GENPADSB and GENPAGWDSB) for PA devicesSiemens AS-i
Link Device Support Block (Siemens DP/AS-i-Link
DSB)Siemens ET200M Device Support Block (Siemens ET200M
DSB)Turck Excom Device Support Block (Turck Excom
DSB)Generic Device Support Blocks (GENDSB and GENIODSB)

DSB block creation

A DSB block is created in the Control Builder from the File
menu
(File > New > Devices > DSB)
A DSB block is assigned to the Protocol Block by dragging a
DSB module template from the Library and assigning it one of
the Protocol Blocks in the Project view.

DSB block deletion

You cannot delete a DSB FB with at least one PDC still
associated with a PIOMB and a PBHIOMB. You must dissociate
the PIOMB from the DSB and then delete the DSB. However,
there are no restrictions on deleting a DSB that has no PDCs
associated to PIOMBs.
You must first delete the DSB from the Monitoring view before
deleting it from the Project view.

182
Chapter 8 - Device Support Block (DSB)

About DPV1 read/write messages configuration

in DSBs
DSB blocks can be configured to support the DPV1 data record
read/write between PROFIBUS master and responders. For
each PROFIBUS device, the DPV1 configuration can be done in
the respective DSB blocks. In addition, the following
parameters can be configured in the DSB blocks to control the
DPV1 requests from multiple responders.
n Number of DPV1 data records (DPV1NUMPOLL)
n Scan priority (DPV1PRIORITY)
n Scan ratio of high and low priority requests
(DPV1NUMHIGHPRIREQ)

ATTENTION: The DPV1 write is always considered as high

priority request compared to the DPV1 read.

The following DSB blocks supports a maximum number of 16

DPV1 data access requests from data records.
n GENDSB
n TURCKDSB
n CEAGDSB
n SIEMENSET200
However, the GENIODSB supports 64 data access requests
from data records.

ATTENTION: You must read the PROFIBUS responder

vendor manual before configuring the DPV1 requests in
the DSB block.

A DPV1 record can be parsed to 16 data fields

(parameters/data types). If a DPV1 data record needs to be
parsed to more than 16 fields, then the
n Same record can be configured multiple times for read or
write and parsed to more fields, or
n C300/UOC/HCA strategies can be used to parse the
complex record into simpler records.

183
 Chapter 8 - Device Support Block (DSB)

DPV1 data write occurs in three stages as follows:

1. Read the DPV1 data from the PROFIBUS-DP device
2. Append the modified DPV1 value
3. Write the modified value to the PROFIBUS-DP device

DPV1 records scanning

Generally, all the DPV1 requests (16 for all DPV1 supported
DSBs and 64 for GENIODSB) in DSB are scanned in a cyclic
manner irrespective of the DPV1 request configuration.
One DPV1 scan cycle has 16 time slots. Therefore, all the DPV1
request (even if it is not configured) is scanned once in every
cycle. For example, consider that the time slot is 1 second and
there are four DPV1 requests that are configured. In this
scenario, the first DPV1 request is scanned at n, n+16, n+32,
and so on.
The Scan Priority (DPV1PRIORITY) has the following options
that are used for scanning the DPV1 requests.
n High
n Low
n On Demand
n No Poll
When the DPV1PRIORITY parameter is set as “High,” DPV1
requests are polled for every cycle.
When the DPV1PRIORITY parameter is set as “Low,” the DPV1
requests are polled based on the DPV1NUMHIGHPRIOREQ
parameter. For example, if the DPV1NUMHIGHPRIOREQ
parameter is set as 5, then the “Low” requests are polled once
for every 5 cycles.
When the DPV1PRIORITY parameter is set as “On Demand,” the
DPV1 requests are polled only when the
DPV1ONDEMANDSCAN parameter is selected.
When the DPV1PRIORITY parameter is set as “No Poll,” the
corresponding DPV1 request is not polled.

184
Chapter 8 - Device Support Block (DSB)

Configuring DPV1 read/write messages (Project view)

Prerequisites
DSB block must be configured.

To configure DPV1 read/write messages (Project view)

1. Double-click the DSB block. The DSB block configuration
form appears.
2. Click the DPV1 tab.
3. Under Settings, select the Number of High Priority Requests
(DPV1NUMHIGHPRIREQ) as required. This parameter
indicates the number of times a high priority request is
serviced before servicing a low priority request.
4. Under Configuration, type the total number of DPV1 requests
to be configured in the Number Of Requests (DPV1NUMPOLL)
box. The rows are added in the DPV1 Requests table.
5. Under the DPV1 Requests, configure the following
parameters.
a. In the DPV1 Type (DPV1REQTYPE) list, select the DPV1 type
as “DPV1 Read” or “DPV1 Write” for each DPV1 request.
b. In the Scan Priority (DPV1PRIORITY) list, select the scan
priority as “No Poll” or “On Demand” or Low” or “High” for
each DPV1 request based on your requirement. The Scan
Priority (DPV1PRIORITY) configuration options are
applicable only for the DPV1 read records.
c. Under the Scan Options, select the Scan On-Demand
(DPV1ONDEMANDSCAN) check box only when the
DPV1PRIORITY parameter is set as “On Demand.” The
Scan On-Demand (DPV1ONDEMANDSCAN) check box is
available for configuration only in the Monitoring view.
When the DPV1ONDEMANDSCAN check box is selected,
the DPV1 requests that are configured as “Low,” “High,”
and “On Demand,” are scanned one time. The
DPV1ONDEMANDSCAN check box is cleared after scanning
all the DPV1 records.
d. In the Slot Number (DPV1SLOTNUM) column, configure slot
number based on the PROFIBUS device manual.
e. In the Index (DPV1INDEX) box, type the index value for
each DPV1 request to be read/written based on the
PROFIBUS device manual.

185
 Chapter 8 - Device Support Block (DSB)

f. In the Length (DPV1LENGTH) box, type the number of

bytes to be read/written from the configured the slot and
index.
g. In the Number Of Data Records
(DPV1NUMOFDATARECORDS) box, type the number of data
records as required.
6. Click OK. The number of data records is saved.
7. Double-click the DSB block. The DSB block configuration
form appears.
8. Click the DPV1 tab.
9. Under the DPV1 Data Records, configure the following:
a. In the Data Type (DPV1DATATYPE) list, select the data type
as required from the list of supported data types for each
Parameter Name (DPV1PARAMNAME). The Octet string data
type is not supported.
b. In the Value (DPV1PARAMVALUE) box, type the parameter
value for writing or monitoring the DPV1 parameter value.
c. In the Parameter Name (DPV1PARAMNAME) box, type the
parameter name.
d. In the Byte Offset (DPV1BYTEOFFSET) box, type the byte
offset value of the parameter, which needs to be mapped
from the DPV1 response.
e. In the Bit Offset (DPV1BITOFFSET) box, type the bit offset
value of the parameter, which needs to mapped from the
DPV1 response. This parameter is available for
configuration only when the data type is configured as
“Boolean.”
10. Click OK.

HART communication/response time impact in a DP

network
The following factors can impact the DPV1/ HOP scan time in a
DP network.

HART devices that are distributed per responder

If there are more number of HART devices configured in a
single responder, then PGM takes more time to complete HOP
scan than the responders that contains less number of HART

186
Chapter 8 - Device Support Block (DSB)

devices. This is because the DPV1 command for each HART

device needs to be sent only after the previous command
response is received.

DP Network baud rate

DP Network baud rate has direct impact on any communication
on the DP network. If the baud rate is high, then the time taken
to receive the response is less. Similarly, if the baud rate is less,
then the time taken to receive the response is more. In addition,
if the baud rate is high, then more commands can be sent in
allocated DPV1 bandwidth. If baud rate is low, then less
number of command in the allocated DPV1 bandwidth.

Allocated DPV1 Bandwidth

The DPV1 requests are sent in a single cycle based on the
configured DPV1 BANDWIDTH parameter value, and hence
DPV1BANDWIDTH value has direct impact on the scan time of
DPV1 requests.

Responders capability
Some of the responders has the capability to serve more than
one DPV1 request at a time and some of the responders
supports only one request at a time.

Field Device Manager (FDM) requests

If the FDM is connected to the DP network and communicates
to the devices that are configured, then the FDM takes priority
than the HOP and DPV1 requests. Therefore, the FDM requests
also has a direct impact on the HART communication.

Configured DPV1 Requests

The number of DPV1 requests that are configured for each
responder and the priorities also have an impact on the HART
command response time-out since both the DPV1 and HOP
requests are serviced.

DPV0 Bus Cycle time

The number of DSBs and their PDCs configured in a link decide
the DPV0 cycle time. If the DPV0 cycle time is high, then the
number of DPV1 request processed per second decreases

187
 Chapter 8 - Device Support Block (DSB)

because PGM limits the number of DPV1 requests handled at

the end of every bus cycle.

IOM's internal HART scan

If the responder have internal HART scan enabled in their HART
IOMs, then the response to HOP requests is slow. Therefore,
you must verify whether the responders have internal HART
scan is enabled while configuring the responders.

ATTENTION: IOM internal scan of the HART devices can be

disabled by following a method that is provided by the
salve. For example, the responder methods are FDT
settings, DPV1 write, through DTM form FDM, and so on.

Data processing
When a DSB is loaded, it performs the following:
n Checks for communication status with PROFIBUS device.
l If the DSB is communicating with the PROFIBUS device,

the SLAVESTATE parameter is set to "Communicating."

l If there is a communication error between the DSB and

the PROFIBUS device, the SLAVESTATE parameter is set

to "Communication error" and notifications are sent
accordingly.
n For each configured PDC, checks its communication with
PB and PIOMB and sets the PDCSTATE accordingly.
n For PDCs that are configured as AI or DI module, the DSB
performs the following:
l Receives extended diagnostic data and process data from

the PROFIBUS device.

l Updates CHDATARAW parameter for AI modules,
performs percentage range conversion, and updates
CHDATAREAL parameter.
l Updates CHDATABOOL parameter with the value of each

channel.
l Processes extended diagnostic data and sends
notification based on extended diagnostic data.
l Updates channel status based on extended diagnostics.

188
Chapter 8 - Device Support Block (DSB)

n For PDCs that are configured as AO or DO module, the DSB

performs the following.
l Processes extended diagnostic data, updates channel
status, and sends notifications based on channel status.
l Checks if the configured PDC is associated with a PIOMB.

n If a configured PDC is associated with a PIOMB, the DSB

performs the following:
l Receives recent data from the PIOMB and sends it to the

device.
l Updates the CHDATARAW and CHDATAREAL parameters

of the configured AO module with the data sent to end

device.
l Updates the CHDATABOOL parameter of the configured

DO module with the data sent to the end device.

n If a configured PDC is not associated with a PIOMB, the
DSB sets the channel values to 0.

Extended range handling

Output channels
For output channels, whenever the output value received from
the C300/UOC/HCA is greater than the maximum range, the
output value is clamped to the maximum possible value
maintaining the channel status as "GoodCascade_NonSpecific."
For example, consider the following scenario.
The high range of a channel is 20000 and the extended high
range of a channel is value 25000. In such a scenario, if the
value received from the C300/UOC/HCA is 27000, then this
value is clamped to 25000.
However, when there is no association of a PDC to a PIOMB,
and when you try to enter the output values that are out of
range, the following error message
"kVAStsLimitOrRangeExceeded" appears. In such a case, the
last good value is retained.

Input channels
For input values which are out of the maximum extended
range, the input channel status is set to "Bad_DevError."

189
 Chapter 8 - Device Support Block (DSB)

However, the same value is sent to the C300/UOC/HCA. The

DSB does not clamp the value received from the device to
extended range limits.
The extended range lower limit for all the analog input modules
is "0."

ATTENTION: To prevent the process data values from being

clamped, you can set the channel high and low range as
"NaN." When this is performed, the process value is limited
by the values supported by the data type.

Generic Device Support Blocks (GENDSB and

GENIODSB)
The Generic DSBs run on the PGM and represent one
PROFIBUS field device in the PROFIBUS network. The Generic
DSBs can be configured for PROFIBUS devices that do not
have device-specific DSBs. The Generic DSBs process the raw
data from the PROFIBUS field devices and converts it to the
PDC format supported by the ExperionPlantCruise. The Generic
DSBs communicate with the master PGM for data conversion.
The 1st Slot Offset in Sycon (SLOTOFFSETINSYCON)
parameter is used for indicating the slot number offset for the
1st IO module in "Profibus Network Configuration Tool"
configuration. For example, in the TURCK EXCOM Responder,
the slot offset is 1 because the gateway module is present in
slot number 1 and the IO modules starts from the slot number
2. Similarly, in the SiemensET200M Responder, the first 3 slots
are configured and the IO modules starts from slot number 4.
Hence, the slot offset is 3.
There are two types of Generic DSBs.
n GENDSB - A single GENDSB can support up to 16 I/O
modules and each I/O module can support up to 32
channels.
n GENIODSB -A single GENIODSB can support up to 64 I/O
modules and each I/O module can support up to 16
channels. The GENIODSB is introduced with R410. The

190
Chapter 8 - Device Support Block (DSB)

GENIODSB can be used in scenarios where the number of

modules are more and the channel density is less.

Functions of Generic DSBs

Function
n Integrates the PROFIBUS DP devices to the
ExperionPlantCruise.
n Reads data from field devices and writes output into field
devices depending on whether the I/O module is an input
module or an output module.
n Processes extended diagnostic data and updates channel
status and sends notification based on the channel status.
n Receives data from PIOMB and sends it to the device, if the
PDC is connected to a PIOMB.
n Updates the PDC states.

Data Processing
See Data processing.

Extended Diagnostics
The first 8 bytes of the extended diagnostics message contain
the alarm/status diagnostics of the device. Status diagnostics
provides information such as data validity, module error, wrong
module insertion, and modules being not inserted. The next 4
bytes of the extended diagnostics message contain the slot-
specific diagnostics.
One bit per slot (module slot) indicates whether there are
diagnostics messages present for the respective slot. If the
appropriate bit is set, a diagnostics entry is present for the
respective slot.
Channel specific diagnostics message start from byte number
13 of the extended diagnostics.

TIP:
You can view the diagnosis and extended diagnosis of the
devices online. For more information, see Viewing the

191
 Chapter 8 - Device Support Block (DSB)

PROFIBUS device diagnosis and Viewing the PROFIBUS

device's extended diagnosis respectively.

Generic Device Support Blocks (GENPADSB

and GENPAGWDSB) for PA devices
Starting from R430, the GENPADSB and GENPAGWDSB can be
configured for PROFIBUS PA devices.
If the PROFIBUS PA devices are connected to a transparent
PROFIBUS PA Coupler, you must use the GENPADSB. If the
PROFIBUS PA devices are connected to a Siemens DP/PA link
IM-157, you must use the GENPAGWDSB.
A single GENPADSB can support up to 8 PDCs and each PDC
can support up to 16 channels. In addition, GENPADSB
supports 16 user-defined alarms.
A single GENPAGWDSB can support up to 64 PDCs and each
PDC can support up to 16 channels. In addition,
GENPAGWDSB supports 132 user-defined alarms.

Functions of GENPADSB and GENPAGWDSB

GENPADSB
n Integrates PROFIBUS PA devices to ExperionPlantCruise
through transparent PA segment couplers. GENPADSB
reserves individual address for every individual responder.
n Reads data from field devices and writes output into field
devices.
n For input devices, updates channel status and sends
notification based on the PA status byte received from the
PROFIBUS device. Note that some of the PROFIBUS devices
do not provide the status information. You must refer to the
device specification provided by the vendor.
n For output devices, provides data status to the PROFIBUS
device. Note that some of the PROFIBUS devices do not
accept the PA status provided by the master. You must refer
to the device specification provided by the vendor.

192
Chapter 8 - Device Support Block (DSB)

n Processes extended diagnostic data from PA device and

allows access of diagnostic data to controller.
n Allows enabling/disabling of alarms per channel based on
PA data status.
n Receives data from PIOMB and sends it to the device, if the
PDC is connected to a PIOMB.

GENPAGWDSB
n Integrates PROFIBUS PA devices to ExperionPlantCruise
through non- transparent Profibus DP/PA link, Siemens
DP/PA link IM-157. The Siemens DP/PA link IM-157, is a
DP responder that acts as a proxy for the PA field devices.
The Siemens DP/PA link IM-157 reserves one PROFIBUS DP
responder address.
n For input devices, updates channel status and sends
notification based on the PA status byte received from the
PROFIBUS device. Note that some of the PROFIBUS devices
do not provide the status information. You must refer to the
device specification provided by the vendor.
n For output devices, provides data status to the PROFIBUS
device. Note that some of the PROFIBUS devices do not
accept the PA status provided by the master. You must refer
to the device specification provided by the vendor.
n Processes extended diagnostic data from Siemens DP/PA
link IM- 157 and allows ways to use extended diagnostic
data to set channel statuses and alarm.
n Allows enabling/disabling of alarms per channel based on
PA data status.

Generic Drive Device Support Block

(DRIVEDSB)
The DRIVEDSB runs on the PGM and represents one
PROFIdrive application in the PROFIBUS network. The
DRIVEDSB processes the raw data from the PROFIdrive
applications and converts it to the PDC format supported by
the ExperionPlantCruise.
Unlike other DSBs, the DRIVEDSB does not have slots for the
I/O modules. The DRIVEDSB has a port that can be used to
access all the parameters.

193
 Chapter 8 - Device Support Block (DSB)

The DRIVEDSB supports the following two PROFIdrive

applications.
n Standard drive (For example, speed control).
n Single axis positioning drive with local motion control.
Both drives can be implemented only using the DP-V0
communication. These drives support only a single Parameter-
process data object (PPO) module per device. The DRIVEDSB
does not support modules that require multiple PPO types.
Also, only the big-endian devices are supported by the
DRIVEDSB.

Parameter - process data object (PPO)

The PPOs are defined for cyclic data transfer and can be
divided into the following two parts.
n PZD (Process data area) - These parameters represent the
monitoring parameters such as the control words, status
information, set point, and actual values.
n PKW (Parameter area) - These parameters enable you to
read/write values to the parameters in the drive. For
example, reading parameter information such as maximum
value, minimum value, and so on.
Through the PPO, the PZD parameters and the PKW
parameters can be transferred from the PROFIBUS master to
the PROFIBUS device and vice versa.
The following 5 PPOs are defined in the PROFIdrive technology.
n PPO1 input channel - Support up to 17 channels (16 DI
channels, 1 AI channel)
n PPO1 output channel - Supports up to 17 channels (16 DO
channels, 1 AO channel)
n PPO2 input channel - Supports up to 32 channels (16 DI
channels, 1 AI channel and 15 user configurable channels)
n PPO2 output channel - Supports up to 32 channels (16 DO
channels, 1 AO channel and 15 user configurable channels)
n PPO3 input channel - Supports 17 channels (16 DI
channels, 1 AI channel)
n PPO3 output channel - Supports 17 channels (16 DO
channels, 1 AO channel)

194
Chapter 8 - Device Support Block (DSB)

n PPO4 input channel - Supports 32 channels (16 DI

channels, 1 AI channel and 15 user configurable channels)
n PPO4 output channel - Supports 32 channels (16 DO
channels, 1 AO channel and 15 user configurable channels)
n PPO5 input channel - Supports 32 channels (16 DI
channels, 1 AI channel and 15 user configurable channels)
n PPO5 output channel - Supports 32 channels (16 DO
channels, 1 AO channel and 15 user configurable channels)
In the PPO input types, the 16 DI channels map to the
individual bits of the status word of the PPO. The standard AI
channel maps to the real time actual value of the drive (speed
or torque).
In the PPO output types, the 16 DO channels map to the
individual bits of the control word of the PPO. The standard AO
channel maps to the set point of the drive (speed or torque).
Refer to the PROFIBUS Gateway Module Parameter Reference
guide for more information on the Status Word and the Control
Word descriptions.

Configurable channel types

The PROFIdrive technology defines the following two
configurable channel types.
n PKW Inputs
n PKW Outputs
These channels use the acyclic PKW data area to read
parameter information from the drive. These channels are slow.
Therefore, they can be used to read information such as
statistics, configuration information, and other miscellaneous
data from the drive.

ATTENTION: The PKW area is supported in the PPO types 1,

2, and 5.

Guidelines for using PKW channels

While using the PKW channels, you must remember the
following guidelines.

195
 Chapter 8 - Device Support Block (DSB)

n Do not use PKW channels for accessing or writing time-sensitive

data - Typically, the PKW channels send and receive data at
a rate proportional to the device subscription rate. If there is
no PDA connection, the rate is approximately 1 sec. If there
is a PDA connection, the rate depends on the PDA
subscription rate. Also, this rate is dependent on the number
of PKW channels. For example, if the subscription rate is 1
sec and you have 10 channels configured, the rate at which
each channel will be updated is 10 sec (subscription rate * n
= 1 sec * 10). However, due to the acyclic nature of the
parameter requests, there is no guarantee that the response
comes in the data cycle after the request. Therefore, you can
use the above information only for approximation purposes
and not consider as the actual rates. Because the PKW
channels update the date at a non-deterministic rate, you
should not use these channels for accessing or writing data
that is time sensitive.
n Configuring the channel high range and low range as "NaN" to
enable or prevent scaling of the parameter values - Because the
PKW channels are analog channels, you must configure the
channel high and low range. If you know the parameter
range and if it is possible to scale the parameter value
within 0% to 100%, you can enter the high and low ranges.
However, in some cases having a scaled value does not
make sense. For example, counters and for configuration
enumeration values (which may have a range of 0, 1, 2, 3,
and 4, each with a specific meaning). In such cases, you can
configure the channel high and low range as "NaN" (IEEE
754 "Not a Number"). Configuring the channel high and low
range as "NaN" prevents scaling of the parameter value.
n Do not use PKW channels with Regulatory Control blocks - You
must be careful while using the PKW channels in control
strategies because of the following reasons:
l They are slow and non-deterministic in the timing of their

updates.
l You can read and write the same parameter which can

lead to race conditions. This may result in error reading

old data or error writing new data.
l The status of the output channels does not follow the

typical channel behavior. For example, consider a

scenario where you provide a value to an output channel

196
Chapter 8 - Device Support Block (DSB)

that writes to a PKW parameter, and that value is outside

of the range of that parameter. In this scenario, the
channel status is set to "Bad" because of the PKW error
response. Also, if this channel is wired to a block that is
used in a control (for example, PID, REGCALC, RATIOCTL,
and so on) you must force all upstream blocks into the
"Initialization Manual" state. Also, you will not be able to
recover without deleting the Control Module containing
the strategy. This is one of the reasons you should not
use PKW channels with regulatory control blocks.
n Difference in PKW channel displays - You can use the displays
for the PKW channels for displaying statistics, counters, and
other information about a drive. However, the displays of the
PKW channels differ depending on whether or not that drive
is under control (PIOMB is loaded or not). For example,
consider a display displaying all 32 channels of a PKW input
PDC. If the C300/UOC/HCA is controlling the drive (there
exists a loaded PIOMB that refers to this DRIVEDSB) then
update rate for the PKW parameters in the display is faster.
As a rough estimate, assuming ideal conditions, you could
expect to have all of the PKW parameter refresh their values
in a time period of approximately 5 seconds.
However, if there are no PIOMBs loaded and connected to the
DRIVEDSB, the rate at which the PKW parameters refresh their
values become very slow. The parameter values in the display
may refresh their values in a time period of around 30 through
60 seconds for the 32 channels.

Supported data transfer types

The DRIVEDSB supports the PROFIdrive cyclic and acyclic
(through the PKW area) data transfer of the PPO types.
n PROFIdrive cyclic data transfer - The PROFIdrive
specification V2 defines the cyclic data transfer for fast data
transfer at equidistant time intervals.
n PROFIdrive acyclic data transfer - The PKW area is used to
access acyclic parameters through the cyclic process data
communication path (pseudo acyclic data transfer using
DP- V0). The output data defines parameter ID and sub-
index and value for parameter write. The input area has

197
 Chapter 8 - Device Support Block (DSB)

value for parameter that was last requested or status of the

parameter write.

TIP:
For more information on the PROFIdrive technology, refer
to the PROFIBUS website.

Functions of DRIVEDSB

Function
n Integrates the PROFIBUS DP devices to
ExperionPlantCruise.
n Reads data from field devices and writes output into field
devices depending on whether the I/O module is an input
module or an output module.
n Updates channel status and send notification based on the
channel status.
n Receives data from PIOMB and sends it to the device, if the
PDC is connected to a PIOMB.
n Updates the PDC states.

Data Processing
You can change the channel output values directly through the
PDC tab. When you change the values through the PDC tab, the
values are updated in the DSB and then periodically sent out
over the PROFIBUS. However, when using control word bits, you
cannot assume that the control word bits will be sent to the
device at once. This is because control word bits must be set in
a specific order or a group. Also, the application engineers must
ensure that any control bits which are dependent on each other
must be logically tied together by the control strategy. This
means that they must be contained in the same Control
Module.
There are two scenarios during which control word could be
sent non-atomically to the PROFIBUS.
n A PIOMB is not connected to the PPO output PDC - The
engineer or the operator may directly change the control
word bit-by-bit from the DSB display in Control Builder or

198
Chapter 8 - Device Support Block (DSB)

Station. In such a scenario, these changes are sent

individually and therefore results in incremental control
word changes being sent to the device.
n The DO channels associated with the control word are in
separate CMs, they may be on different phases and have
different cycles - This results in partial updates to the
control word (bit-by-bit change) being sent to the device.
See Data processing.

PKW Processing
The PKW processing enables you to process and monitor
parameters (write/read). The PKW processing is applicable only
to the PPO types 1, 2, and 5. The DSB uses the same data areas
for both read and write requests for these channels.
The flow of the PKW processing by the DSB is as follows:
1. Identifies the first PDC channel that is associated with a
PKW PDC.
2. Updates the PKW section of the output area with the
appropriate information.
3. Sends out the PKW data.
4. Reads the PKW input data until the response ID is not 0 (no
response).
5. Compares the request Parameter Number with the response
Parameter Number to ensure that they are identical.
6. Sets the channel status based on the response ID.
7. Copies the response value to the requested channel.
8. Identifies the next PDC channel that is associated with a
PKW PDC.
9. Repeats step 3 through step 7 for the other PDC channels
that are associated with the PKW PDCs one at a time.

ATTENTION: The channel status is set to "Bad_NonSpecific"

when the response of a PKW read or write is one of the
following; otherwise, the channel status is set to "Good."

199
 Chapter 8 - Device Support Block (DSB)

Channel status processing

A short delay of approximately 10 seconds or less is introduced
for the DRIVEDSBs while transitioning the status from "Bad" to
"Good." This is to ensure proper behavior of the DSB and also to
avoid fluctuating status.
The DRIVEDSB only supports channel-level status for PKW
channels. Also, all channels follow the status of the entire PDC.
Therefore, if one channel is bad, all channels will be bad.

TIP:
If a PKW channel is bad, it is a result of an error response
for that PKW request.

Diagnostics
The extended diagnostic data specifics are not defined for the
PROFIdrive specification. However, the DRIVEDSB actually uses
the process data area for alarming.
You can configure alarms that correspond to an input PDC and
a given byte/bit offset within that PDC. When the specific bit
becomes "On," an alarm is raised.
You can configure up to 16 alarms. However, you cannot
configure the severity or the priority for these alarms. All alarms
are reported with priority as "High" and Severity as "0."

TIP:
There are no other alarms specific to the DRIVEDSB other
than these user-configurable alarms.

CEAG Device Support Block (CEAGDSB)

The CEAGDSB runs on the PGM and represents one PROFIBUS
field device in the PROFIBUS network. The CEAGDSB processes
the raw data from the CEAG field devices and converts it to the
PDC format supported by ExperionLXPlantCruiseExperion PKS.
The CEAGDSB communicates with the master PGM for data
conversion.

200
Chapter 8 - Device Support Block (DSB)

A single CEAGDSB supports up to 46 I/O modules. The

CEAGDSB is used for configuring the CEAG LB/FB Remote I/O
family when using PROFIBUS communication unit Easy COM
LB8106/FB8206 V6.XX.
The CEAGDSB supports the I/O stations per bus line that
provide 31 stations without repeaters and up to 125 stations
with repeaters. The maximum number of modules per
responder device is 49 (46 I/O modules plus 3 slots reserved
for the communication unit) in the field network configuration.
The communication unit present in each station transfers the
data of internal system bus to the protocols of the master bus
system.
The maximum number of PDCs required per station is 48 and
this can be interpreted as follows:
n 2 PDCs for the communication unit and 46 PDCs for 46
one-channel modules. Or
n 2 PDCs for the communication unit and 46 PDCs for 23
multi-channel modules having both inputs and outputs.

ATTENTION: The maximum number of one-channel I/O

module per station is 46.

I/O modules supported by the CEAGDSB

The following tables lists the I/O modules supported by the
CEAGDSB.

CEAGDSB

Supported CEAG
PDC Type
modules

Digital Input with line fault detection - 2 l LB1101

channels l LB1001
l FB1201
l FB1301

Digital Input with line fault detection - 3 l LB1102

channels l LB1002
l FB1202

201
 Chapter 8 - Device Support Block (DSB)

Supported CEAG
PDC Type
modules

l FB1302
l 2xxx

Digital Input with line fault detection - 8 l LB1108

channels l LB1008
l FB1208
l FB1308
l LB6X08
l FB6X08 (input
= current
output value)

Digital Input without channel status (Relay l LB6005

Inputs) - 4 channels l FB6305 (input
= current
output value)
l 6x1y

Digital Input without channel status (Relay l LB6006

Inputs) - 8 channels l FB6306 (input
= current
output value)

Digital Input with only line fault detection - 4 l LB4104

channels l LB4105
l LB4005
l FB4204
l FB4205
l FB4305 (input
= LFD of
analog
outputs)

Analog Input with line fault and live zero l LB3002

detection - 1 channel l LB3101
l LB3102
l LB3103
l FB3201

202
Chapter 8 - Device Support Block (DSB)

Supported CEAG
PDC Type
modules

l FB3202
l FB3203
l FB3302

Analog Input with line fault and live zero l LB3104

detection - 4 channels l LB3005
l LB3105
l FB3204
l FB3205
l FB3305

Analog Input with line fault detection l LB5101

(Converter Inputs) - 1 channel l LB5001
l FB5201
l LB5102
l LB5002
l FB5202

Analog Input with line fault detection l LB5104

(Converter Inputs) - 4 channels l LB5004
l FB5204
l LB5105
l LB5005
l FB5205

Analog Input without channel status l LB5106

(Converter Inputs) - 1 channel l LB5006
l FB5206

Numeric Input for Communication module - 2 l LB8106

channels This is used internally by DSB and it l FB8206
cannot be connected to PIOMB.

Numeric Output for Communication module - l LB8106

2 channels This is used internally by DSB and l FB8206
it cannot be connected to PIOMB or operated
using Control Builder. This must be
configured always.

203
 Chapter 8 - Device Support Block (DSB)

Supported CEAG
PDC Type
modules

Digital Output (Relay Outputs) - 2 channels l LB6101

l FB6301
l 2xxx

Digital Output with data invalid setting (Relay l LB6005

Outputs) - 4 channels l FB6305
l 6x1y

Digital Output with data invalid setting - 8 l Digital Outputs

channels
l LB6X08
l FB6X08
l Relay Outputs
l LB6006
l FB6306

Analog Output - 1 channel l LB4101

l FB4201
l LB4102
l LB4002
l FB4202
l FB4302

Analog Output - 4 channels l LB4104

l LB4105
l LB4005
l FB4204
l FB4205
l FB4305

Functions of CEAGDSB

Function
n Integrates the PROFIBUS DP devices to
ExperionLXPlantCruiseExperion PKS.

204
Chapter 8 - Device Support Block (DSB)

n Reads data from field devices and writes output into field
devices depending on whether the I/O module is an input
module or an output module.
n Processes extended diagnostic data and updates channel
status and send notification based on the channel status.
n Receives data from PIOMB and sends it to the device, if the
PDC is connected to a PIOMB.
n Updates the PDC states.

Data Processing
See Data processing.

ATTENTION: For PDCs that are configured as NI or NO

module, CEAGDSB performs the following processing.

Channel Error Processing

The channel error status generated is delivered with the raw
data. The error status bits are picked from the raw data and
used as the information while generating the channel status
and channel alarms. The channel error is transmitted only if the
error reporting for the channel is allowed using the field
network configuration.

ATTENTION: The channel errors are transmitted for the

analog values only if the range values are set to default
(Low = 10000 and High = 50000) in the field network
configuration.

Extended Diagnostics
The extended diagnostics message contains the
communication module diagnostic data and module status,
which are used for generating the CEAGDSB alarms. The
additional module status information is used to produce the
channel status parameter of the PDC.
The following table lists the various module status values and a
brief description of the state.

205
 Chapter 8 - Device Support Block (DSB)

Module
Description
Status
Data This is the normal module status when there are no
valid errors.

Module This state indicates that one or more channel error is

error active in the module. This state is applicable only to
the channels that are configured to allow channel error
reporting in the Field Network Configuration.

Wrong This state indicates that the module type in the slot
module conflicts with the module type defined in Field Network
Configuration.

Missing This state indicates that the module is physically not

module present in the configured slot.

TIP:
You can view the diagnosis and extended diagnosis of the
devices online. For more information, see Viewing the
PROFIBUS device diagnosis and Viewing the PROFIBUS
device's extended diagnosis respectively.

Channel and module alarms based on module status

and PDC type
The following table lists the behavior of the channel and
module alarms, based on the module states and the PDC types.

Module
PDC type Channel alarms Module alarm
status

Missing IN/OUT All channel alarms of Module alarm is

module module are set to set to ACTIVE,
RETURNED to parameter =
NORMAL. missing module
(4).

Wrong IN/OUT All channel alarms of Module alarm is

module module are set set to ACTIVE,
RETURNED to parameter = wrong
NORMAL. module (3).

206
Chapter 8 - Device Support Block (DSB)

Module
PDC type Channel alarms Module alarm
status

Module IN l Alarms of channels Module alarm is

error reporting error are set to RETURNED
set to ACTIVE. to NORMAL.
l Alarms of channels
not reporting error
are set RETURNED
to NORMAL.

OUT - Module alarm is set

ACTIVE, parameter =
module error (2).

Data IN/OUT All channel alarms of Module alarm is

valid module are set set RETURNED TO
RETURNED TO NORMAL.
NORMAL.

Channel status processing

Channel specific diagnostics message starts from byte 13 of
the extended diagnostics. In addition to the channel status
processing, the CEAGDSB applies extended channel status
processing based on the module status and the channel error
bits.

Extended channel status processing

The following table lists the various channel states that a
channel can assume, based on the module status and the PDC
types.

Channel Channels
Module status PDC type
status affected

Missing IN Bad_DevError All channels

module

OUT Bad_DevError All channels

Wrong module IN Bad_ All channels

ConfigError

207
 Chapter 8 - Device Support Block (DSB)

Channel Channels
Module status PDC type
status affected

OUT Bad_ConfigError All channels

Module error IN Bad_ Channels

SensorError reporting
error

Good_ Channels not

NonCascade reporting error

OUT Bad_SensorError All channels

Data valid IN Good_ All channels

NonCascade

OUT GoodCasc_ All channels

NonSpecific

ATTENTION: In case of a channel error, the channel value

provided by the device is the last good value of the
channel.

Alarm Processing
The following alarms are generated by the CEAGDSB.
l CEAGDSB internal alarms - This alarm is reported when the
communication unit is not configured. This alarm’s severity
is "0" and the priority is "Low."
l Alarms based on the module status - This alarm reports the
slots associated with the module error. All modules can
report this alarm. This alarm’s severity is "0" and the priority
is "High."
l Alarms based on the channel errors - This alarm reports the
slots associated with channel errors. All modules can report
this alarm. This alarm’s severity is "0" and priority is "High."
The CEAGDSB cannot detect the channel error status for the

208
Chapter 8 - Device Support Block (DSB)

output modules. Therefore, it is not useful to activate

channel-related alarms for the output modules.
l Alarms based on Communication unit diagnostics.

Siemens AS-i Link Device Support Block

(Siemens DP/AS-i-Link DSB)
The Siemens DP/AS-i-Link DSB runs on the PGM and
represents one PROFIBUS field device in the PROFIBUS
network. The Siemens DP/AS-i-Link DSB represents a
PROFIBUS module and acts as a gateway to an AS Interface
bus. The Siemens AS-DP/AS-i-Link DSB processes the raw data
from the Siemens DP/AS-i-Link field devices and converts it to
the PDC format supported byExperionLXPlantCruiseExperion
PKS. The Siemens DP/AS-i-Link communicates with the master
PGM for data conversion.
The Siemens DP/AS-i-Link supports the following two modules:
n Siemens DP/AS-i Link 20E
n Siemens DP/AS-i Link Advanced
The following table lists the functionalities supported by the
Siemens DP/AS-i Link 20E and the Siemens DP/AS-i Link
Advanced modules.

Device Supported functionality

Siemens l Up to 31 PROFIBUS devices (no A/B extended

DP/AS-i Link responder addressing).
20E l Up to 4 digital inputs/outputs per PROFIBUS
device using DP-V0.

Siemens l Supports both single PROFIBUS master and

DP/AS-i Link double master AS-i (that is, up to two AS-i
Advanced segments).
l Up to 31 PROFIBUS devices (no A/B extended
responder addressing) per AS-i segment.
l Up to 4 digital inputs/outputs per PROFIBUS
device using DP-V0.

The AS-Interface bus can access up to 31 devices and access

up to 62 devices when extended addressing is used. The
Siemens DP/AS-i-Link acts as PROFIBUS device and AS-I

209
 Chapter 8 - Device Support Block (DSB)

master at the same time and allows the PROFIBUS master to

access devices on the AS-i-bus. The PROFIBUS device and AS-I
master can have up to four binary inputs and four binary
outputs.
The device input or output data and status or diagnostic
information from the Siemens DP/AS-I Link to the PGM is
communicated through DP-V0.

Functions of Siemens AS-i Link

Function
n Integrates the PROFIBUS DPdevices to
ExperionLXPlantCruiseExperion PKS.
n Reads data from field devices and writes output into field
devices depending on whether the I/O module is an input
module or an output module.
n Processes extended diagnostic data and updates channel
status and send notification based on the channel status.
n Receives data from PIOMB and sends it to the device, if the
PDC is connected to a PIOMB.
n Updates the PDC states.

Data Processing
When a Siemens AS-i-Link DSB is loaded, it performs the
following:
n Checks for communication status with responder.
l If the DSB is communicating with the responder, the
SLAVESTATE parameter is set to "Communicating."
l If there is a communication error between the DSB and

the responder, the SLAVESTATE parameter is set to

"Communication error" and notifications are sent
accordingly.
n For each configured PDC, checks its communication with
PB and PIOMB and sets the PDCSTATE accordingly.
n For PDCs that are configured as DI module, Siemens AS-i-
Link DSB performs the following:
l Receives extended diagnostic data and process data from

the PROFIBUS device.

210
Chapter 8 - Device Support Block (DSB)

l Updates CHDATABOOL parameter with the value of each

channel.
l Processes extended diagnostic data and sends
notification based on extended diagnostic data.
l Updates channel status based on extended diagnostics.

n For PDCs that are configured as DO module, it performs the

following.
l Processes extended diagnostic data, updates channel
status, and sends notifications based on channel status.
l Checks if the configured PDC is associated with a PIOMB.

n If a configured PDC is associated with a PIOMB, it performs

the following:
l Receives recent data from the PIOMB and sends it to the

device.
l Updates the CHDATABOOL parameter of the configured

DO module with the data sent to the end device.

n If a configured PDC is not associated with a PIOMB, it sets
the channel values to 0.

ATTENTION: In the event of a loss of communication with

the PGM, the Siemens DP/AS-i-Link DSB changes the
output value internally. However, when the device is
reconnected, the current internal value is written to the
device. This value is reflected by the CHDATABOOL
parameter.

Extended Diagnostics

TIP:
You can view the diagnosis and extended diagnosis of the
devices online. For more information, see Viewing the
PROFIBUS device diagnosis and Viewing the PROFIBUS
device's extended diagnosis respectively.

In the extended diagnostic processing, the diagnostic

conditions are not mutually exclusive and both the internal
error and the hardware error may be signaled.

211
 Chapter 8 - Device Support Block (DSB)

The following table lists the various channel states that a

channel can assume based on the extended diagnostics.

Extended
Affected channels Channel status
Diagnostic

Internal error All channels in all PDCs Bad_DevError

External error Does not impact the Left as-is

channel status

Unexpected Does not impact the Left as-is

responder channel status
configuration

AS-Interface Does not impact the Left as-is

voltage low channel status

Hardware error All channels in all PDCs Bad_DevError

DP/AS-I Link All channels in all PDCs Bad_

module is offline OutOfServError

EEPROM is All channels in all PDCs Bad_DevError

defective

Responder error All channels associated Bad_NonSpecific

(for responder X) with AS-i responder X

Combination of Largest scope of common Bad_NonSpecific

any of the above, diagnostics Only the
with the same Siemens DP/AS-i-Link
scope DSB has the diagnostic
tab.

ATTENTION: After the diagnostic condition returns to

normal for the channels whose status is "Bad," the
affected channels change their status to request the
PIOMB to back initialize these channels. This is
applicable only for the output channels.

In addition, the following two scenarios result in the output

value initialization in the Siemens DP/AS-i Link DSB.

212
Chapter 8 - Device Support Block (DSB)

l When the PDA connection is lost or closed, the output

channel values are held or set to 0 (Off) and these output
values are written to the appropriate AS-i PROFIBUS devices.
However, the output value written to the PROFIBUS devices
depends on the value of the HOLDONFAIL parameter.
l When the PDA connection is restored with the controller, the
output values are back-initialized to the PIOMB.

ATTENTION: The Siemens DP/AS-i Link DSB does not

support remote/local control of AS-i device input/output
values. Therefore, there are no initialization scenarios for
these. In addition, there is no read-back of output values
from the AS-i PROFIBUS devices. Therefore, the back
initialization is performed using the values which are held
internally in the DSB, typically the last written value.

Alarm Processing
The Siemens DP/AS-i-Link DSB can have one AS-i responder
error alarm for each configured responder in the system. It can
have up to 62 active responder error alarms.
The alarms conditions are processed at the same rate as the
PROFIBUS data is cyclically fetched. However, the alarms are
reported at the DSB’s cyclic execution period of one second.
The following table lists the various alarms reported by the
Siemens DP/AS-i-Link DSB. This table also provides
information on the priority and severity of each alarm.

ATTENTION: One of the diagnostic conditions listed in the

table below must exist for at least one second to ensure
that an alarm is generated.

Alarm Description Priority Severity

AS-i Alarm indicates which AS-i High (3) 0

Responder PROFIBUS device has an
Error error (1 – 31). Theoretically, if
you had 31 PROFIBUS

213
 Chapter 8 - Device Support Block (DSB)

Alarm Description Priority Severity

devices and all of them had

errors you would see 31
alarms in Station.

AS-Interface This alarm only provides High (3) 0

voltage low notification of AS-i voltage
low if either the DP/AS-i Link
is on an external 24V power
source or there is still enough
power on the AS-i cable for
the DP/AS-i Link to operate.

DP/AS-I This alarm provides the Low (2) 0

Link module communication error (when
is offline there is the failure of the
whole device).

Hardware Unspecified hardware error High (3) 0

error with the DP/AS-i Link
module.

EEPROM This alarm indicates the High (3) 0

defective failure of the nonvolatile
storage (NVS).

TIP:
For more information on the Siemens DP/AS-i Link DSB,
refer to the following:

Siemens ET200M Device Support Block

(Siemens ET200M DSB)
The Siemens ET200M DSB runs on the PGM and represents
one Siemens device in the PROFIBUS network. The Siemens
ET200M DSB processes the raw data from the Siemens devices
and converts it to the PDC format supported by the
ExperionLXPlantCruiseExperion PKS. The Siemens ET200M
DSB communicates with the master PGM for data conversion.

214
Chapter 8 - Device Support Block (DSB)

A single Siemens ET200M DSB can support up to 16

input/output modules.
The Siemens ET200M DSB has 9 card physical slots. The first
slot is for the station and the remaining eight slots are for the
I/O modules. Logically, the ET200M I/O rack is divided in to 11
logical slots. The first 3 slots are reserved and the remaining
slot 4 through slot 11 are for the I/O modules. The extended
diagnostics for the ET200M has diagnostic data for the
modules in I/O rack slots. It also contains the channel-specific
diagnostics for channels of modules in the I/O rack slots.
The following table summarizes the I/O modules supported by
the Siemens ET200M DSB and also the number of channels
supported by these I/O modules.

Number of channels
I/O module
supported

Siemens analog input module 8, 4, 2

Siemens analog output modules 8, 4, 2

Siemens digital input module 32, 16, 8, 4

Siemens digital output module 32, 16, 8, 4

Set of mixed digital input and output -

module

Supported gateways
The Siemens ET200M DSB supports following gateways.
n IM 153-1
n IM 153-2

I/O modules supported by the Siemens ET200M DSB

The following tables lists the I/O modules supported by the
Siemens ET200M DSB.

215
 Chapter 8 - Device Support Block (DSB)

Siemens ET200M DSB

Order
Digital Module
Number

Digital Input Module SM 321; DI 32_24 VDC (6ES7 321-

1BLx0-0AA0)

Digital Input Module SM 321; DI 32_120 VAC (6ES7 321-

1EL00-
0AA0)

Digital Input Module SM 321; DI 16_24 VDC (6ES7 321-

1BHx2-
0AA0)

Digital Input Module SM 321; DI 16_24 VDC High (6ES7 321-

Speed 1BH10-
0AA0)

Digital Input Module SM 321; DI 16_24 VDC; with (6ES7 321-

Hardware and Diagnostic Interrupts, Clocked 7BHx0-
0AB0)

Digital Input Module SM 321; DI 16_24 VDC; (6ES7 321-

Source Input 1BH50-
0AA0)

Digital Input Module SM 321; DI 16 UC 24/48 V (6ES7 321-

1CH00-
0AA0)

Digital Input Module SM 321; DI 16_48-125 VDC (6ES7 321-

1CH80-
0AA0)

Digital Input Module SM 321; DI 16_120/230 VAC (6ES7 321-

1FH00-
0AA0)

Digital Input Module SM 321; DI 8_120/230 VAC (6ES7 321-

1FFx1-0AA0)

216
Chapter 8 - Device Support Block (DSB)

Order
Digital Module
Number

Digital Input Module SM 321;DI 8_120/230 VAC (6ES7 321-

ISOL 1FF10-0AA0)

Digital Input Module SM 322; DO 32_24 VDC/0.5 A (6ES7 322-

1BL00-
0AA0)

Digital Output Module SM 322; DO 32_120 (6ES7 322-

VAC/1.0 A 1EL00-
0AA0)

Digital Output Module SM 322; DO 16_24 VDC/0.5 (6ES7 322-

A 1BHx1-
0AA0)

Digital Output Module SM 322; DO 16_24 VDC/0.5 (6ES7 322-

A High Speed 1BH10-
0AA0)

Digital Output Module SM 322; DO 16_24/48 VUC (6ES7 322-

5GH00-
0AB0)

Digital Output Module SM 322; DO 16 120/230 (6ES7 322-

VAC/1 A 1FH00-
0AA0)

Digital Output Module SM 322; DO 8_24 VDC/2 A (6ES7 322-

1BF01-
0AA0)

Digital Output Module SM 322; DO 8_24 VDC/0.5 (6ES7 322-

A; with Diagnostic Interrupt 8BFx0-0AB0)

Digital Output Module SM 322; DO 8_48-125 (6ES7 322-

VDC/1.5 A 1CF80-
0AA0)

Digital Output Module SM 322; DO 8_120/230 (6ES7 322-

VAC/2 A 1FFx1-0AA0)

217
 Chapter 8 - Device Support Block (DSB)

Order
Digital Module
Number

Digital Output Module SM 322; DO 8_120/230 (6ES7 322-

VAC/2 A ISOL 5FF00-0AB0)

3.27 Relay Output Module SM 322; DO 16_Rel. (6ES7 322-

120/230 VAC 1HH01-
0AA0)

Relay Output Module SM 322; DO 8_Rel. 230 VAC (6ES7 322-

1HF01-
0AA0)

Relay Output Module SM 322; DO 8_Rel. 230 (6ES7 322-

VAC/5A 5HF00-
0AB0)

Relay Output Module SM 322; DO 8_Rel. 230 (6ES7 322-

VAC/5 A 1HFx0-0AA0)

Digital Input/Output Module SM 323; DI (6ES7 323-

16/DO16_24 VDC/0.5 A 1BL00-
0AA0)

Digital Input/Output Module SM 323; DI 8/DO 8_ (6ES7 323-

24 VDC/0.5 A 1BHx1-
0AA0)

The Siemens ET200 M DSB supports the following analog I/O

modules.

Analog Module Order Number

Analog Input Module SM 331; AI 8_16 bits (6ES7 331-7NF00-

0AB0)

Analog Input Module SM 331; AI 8_16 bits (6ES7 331-7NF10-

0AB0)

218
Chapter 8 - Device Support Block (DSB)

Analog Module Order Number

Analog Input Module SM 331; AI 8_13 bits (6ES7 331-1KF00-

0AB0)

Analog Input Module SM 331; AI 8_12 bits (6ES7 331-7KF02-

0AB0)

Analog Input Module SM 331; AI 8_RTD (6ES7 331-7PF00-

0AB0)

Analog Input Module SM 331; AI 8_TC (6ES7 331-7PF10-

0AB0)

Analog Input Module SM 331; AI 2_12 bits (6ES7 331-7KBx2-

0AB0)

Analog Output Module SM 332; AO 8_12 (6ES7 332-5HF00-

bits 0AB0)

Analog Output Module SM 332; AO 4_16 (6ES7 332-7ND01-

bits 0AB0)

Analog Output Module SM 332; AO 4_12 (6ES7 332-5HD01-

bits 0AB0)

Analog Output Module SM 332; AO 2_12 (6ES7 332-5HBx1-

bits 0AB0)

Analog Input/Output Module SM334;AI (6ES7 334-0CE01-

4/AO 2_8/8 bits 0AA0)

Analog Input/Output Module SM334;AI (6ES7 334-0KE00-

4/AO 2_12 bits 0AB0)

Functions of Siemens ET200M DSB

Function
n Integrates the PROFIBUS DP devices to
ExperionLXPlantCruiseExperion PKS.
n Reads data from the field devices and writes output into the
field devices depending on whether the I/O module is an
input module or an output module.

219
 Chapter 8 - Device Support Block (DSB)

n Processes extended diagnostic data and updates channel

status and sends notification based on the channel status.
n Receives data from PIOMB and sends it to the device, if the
PDC is connected to a PIOMB.
n Updates the PDC states.

Data Processing
See Data processing.

Channel Status Processing

The Siemens ET200M DSB supports the following channel
states.
n Bad_NonSpecific
n Bad_ConfigError
n Bad_ConnError
n Bad_DevError
n GoodCasc_NonSpecific
n Good_NonCascade
n GoodCasc_InitReq

TIP:
Refer to the PROFIBUS Gateway Module Parameter
Reference guide for more information on channel status.

Diagnostics
The ET200M I/O rack provides responder diagnostics for
troubleshooting and checking the health of the rack. These
diagnostics are also used for reporting the ET200M DSB
alarms. The maximum size of the responder diagnostics of an
IM 153-1 is 64 bytes and IM 153-2 is 96 bytes.
The responder diagnostics can be classified into the following
categories.
n Standard diagnostics - Byte 0 through byte 5 represent the
standard diagnostics related to the PROFIBUS device. These
diagnostics can be viewed from the Slave Status tab of the
DSB configuration form.

220
Chapter 8 - Device Support Block (DSB)

n Module diagnostics - Byte 6 through byte 8 represent the

module-related diagnostics. These diagnostics represents
the I/O modules of the DSB that are faulty.
n Module status - Byte 9 through byte 15 represent the module
status. Module status reflects the status of the configured
module. Note that you can receive the module status only if
the extended diagnostics is enabled during configuration.
n Channel-specific diagnostics - The channel-specific
diagnostics provide information about the channel errors in
the module. However, the channel-specific diagnostics do
not impact the module status. Note that you can receive the
channel-specific diagnostics only if you have enabled the
extended diagnostics during the configuration.

TIP:
You can view the diagnosis and extended diagnosis of the
devices online. For more information, see Viewing the
PROFIBUS device diagnosis and Viewing the PROFIBUS
device's extended diagnosis respectively.

Alarm processing
The following alarms are reported by the Siemens ET200M DSB
when the PDC state is "Configured," "Opening PDC delivery," or
"Connected."
n Module fault on Slot n - This alarm is reported when the
diagnostic data indicates failure in the module in slot "n."
When this alarm is reported, the Trip Value field in the alarm
summary displays the module status reported in the
extended diagnostics. However, this alarm returns to normal
after fresh diagnostics are received for the slot and the
diagnostics does not indicate a module failure. For each
faulty slot, an alarm is reported.
n Channel errors of Module on Slot n - This alarm is reported
when the diagnostic data indicates a fault in one ore more
channels of a module configured in the slot "n." When this
alarm is reported, the Trip Value field in the alarm summary
displays the faulty channel. However, this alarm returns to
normal after fresh diagnostics are received for the slot and
the diagnostics does not indicate channel failure. For each
faulty slot, an alarm is reported.

221
 Chapter 8 - Device Support Block (DSB)

ATTENTION: In a scenario where both module failure and

channel failure conditions exist, the "Channel errors of
Module on Slot n" returns to normal and only the "Module
fault on Slot n" alarm is reported.

The following alarm is reported by the Siemens ET200M DSB

when the PDC state is other than "Configured," "Opening PDC
delivery," or "Connected."
n Rack Fault on module - This alarm is reported when the
extended diagnostics data indicates a rack failure. When
this alarm is reported, the Trip Value field in the alarm
summary displays the faulty module number. For each
faulty module, an alarm is reported. For example, if there are
three faulty modules, three alarms are reported. This alarm
returns to normal after fresh diagnostics are received for the
slot and the diagnostics does not indicate a rack failure.

Turck Excom Device Support Block (Turck

Excom DSB)
The Turck Excom DSB runs on the PGM and represents one
Turck Excom device (field device) in the PROFIBUS network.
The Turck Excom DSB processes the raw data from the Turck
Excom devices and converts it to the PDC format supported by
the ExperionLXPlantCruiseExperion PKS. The Turck Excom DSB
communicates with the master PGM for data conversion.
A single Turck Excom DSB can support 8 or 16 input/output
modules depending on the size of the backplane. Each module
can be configured as digital or analog module based on the
number of channels, sensor types, and mode parameterization.

Support for processing HART data

With R410, Turck Excom DSB supports processing of HART
data for the following modules.
n AIH40Ex
n AIH41Ex
n AOH40Ex

222
Chapter 8 - Device Support Block (DSB)

If the above I/O modules are connected to HART devices, the

Turck Excom DSB processes secondary variables (HART data).

Gateway redundancy
With R410, Turck Excom DSB provides gateway redundancy. In
addition, Turck Excom DSB can be configured to command
switchover and provide status of the redundant gateway.
Turck Excom station can accommodate 2 gateway modules in
the I/O rack which act as a redundant pair. At any point of time
only one gateway is active. PGM supports only line redundancy.

Guidelines for configuring DM80Ex digital module

You must configure the correct number of channels
(NUMCHANNEL) parameter for the DM80Ex digital module as
this value is not automatically updated for this module. The
number of channels are not updated automatically for this
module for the following reasons.
n This module can be configured either as inputs or outputs.
n This module can be configured as 8 inputs or 8 outputs.
n This module can be configured as 4 inputs and 4 outputs.
n This module can configured as 5 inputs and 3 outputs.
n Set of 2 channels can be freely configured as either inputs
or outputs.

ATTENTION: The default NUMCHANNEL value for DM80Ex

is 8.

When this module is configured as input/output module, 2

PDCs must be configured and the number of channels for each
PDC must be entered manually. For example, if the module is
configured for 6I/2O, then number of channels for input PDC is
6 and 2 for output PDC.

Guidelines for configuring the DF20Ex F as a

Frequency Counter module
While configuring the DF20Ex as a Frequency Counter module,
you must configure one input (FreqCounter_Input) and one
output (FreqCounter_Output) PDC. The input PDC has 2

223
 Chapter 8 - Device Support Block (DSB)

channels and the output PDC has 2 channels. In the output

PDC, the channels are configured as digital outputs.
This module provides one control byte per input to control its
counting direction and bit 3 of each control byte is reserved for
this purpose. Hence the 2 channels represent the control bit
information.
Channel 0 represents control bit information for the first input
and channel 1 represents control bit information for the second
input. This means that the channel 0 controls the counting
direction of first input and channel 1 controls the counting
direction of second input.

Guidelines for configuring the DF20Ex P as a Pulse

Counter module
While configuring the DF20Ex as Pulse Counter module, you
must configure one input (PulseCounter_Input) and one output
(PulseCounter_Output) PDC. The Input PDC has 2 channels
and output PDC has 8 channels. In the output PDC, the
channels are configured as digital outputs.
This module provides one control byte per input to control its
counting operations. Each control byte has 4 control bits (0, 1,
2, and 3) having specific functionality. Therefore, the output
PDC will have 8 channels. The first four channels represent 4
control bits of the first control byte and the last 4 channels
represent the 4 control bits of second control byte. Channels 0
to 3 represent bits 0 to 3 of first control byte respectively and
channels 4 to 7 represent bits 0 to 3 of second control byte
respectively.

I/O modules supported by the Turck Excom DSB

The following tables lists the I/O modules supported by the
Turck Excom DSB.

Turck Excom DSB

Supported Turck Excom Modules

PDC Type

l AnalogInput-AI40Ex l AI40Ex

224
Chapter 8 - Device Support Block (DSB)

Supported Turck Excom Modules

PDC Type

l AnalogInput-AI41Ex l AI41Ex

l AnalogInput-AIH40Ex l AIH40Ex
l AnalogInput-AIH41Ex l AIH41Ex

AnalogOutput-AO40Ex AO40Ex

AnalogOutput-AOH40Ex AOH40Ex

TemperatureInput-TI40ExR TI40ExR

TemperatureInput-TI40ExT TI40ExT

FreqCounter_Input-DF20ExF DF20ExF

FreqCounter_Output-DF20ExF DF20ExF

PulseCounter_Input-DF20ExP DF20ExP

PulseCounter_Output-DF20ExP DF20ExP

DigitalInput-DI40Ex DI40Ex

DigitalOutput-DO40Ex DO40Ex

Digital_Input-DM80Ex DM80Ex

Digital_Output-DM80Ex DM80Ex

TemperatureInput-TI41ExR TI41ExR

DigitalInput-DI40N DI40N

Digital_Output-DO60N DO60N

Functions of Turck Excom DSB

Function
n Integrates the PROFIBUS DP devices to the
ExperionLXPlantCruiseExperion PKS.

225
 Chapter 8 - Device Support Block (DSB)

n Reads data from field devices and writes output into field
devices depending on whether the I/O module is an input
module or an output module.
n Processes extended diagnostic data and updates channel
status and sends notification based on the channel status.
n Receives data from PIOMB and sends it to the device, if the
PDC is connected to a PIOMB.
n Updates the PDC states.

Data Processing
See Data processing.

Status Diagnostics
The status information for the input data is a single bit, and is
set to "Bad" when there is a loss of communication between the
PGM and the devices. By default, the status bit for analog
inputs (AI, TI, and Counter) is always the most significant bit
within the value field. Counter inputs have an additional
overflow status bit.
The digital input modules can be configured to have status for
the input channel data.
The output data has no status information.
All the channels of a PDC is set "Bad" when a module error
exists. The following are the possible module error types.
n Module not inserted
n Wrong module insertion
n Module error
For Turck Excom modules, the status bit in the data word is set
in the event of a module error and the input values are provided
with substitute values.
The following table lists the minimum and maximum values
that can be substituted for the input values in case of a module
error.

ATTENTION: The input values are substituted with the

minimum value, maximum value, or the last good value.

226
Chapter 8 - Device Support Block (DSB)

This substitution is based on the selection made for the

Fail-safe mode, while configuring the I/O module during
field network configuration.

Signal Type Minimum Value Maximum Value

4 to 20 mA 3600 22000

0 to 20 mA 0 22000

0 to 10 Volts 0 10500

2 to 10 Volts 1800 10500

The channel status of all the modules can be obtained from the
extended diagnostics information.

TIP:
You can view the diagnosis and extended diagnosis of the
devices online. For more information, see Viewing the
PROFIBUS device diagnosis and Viewing the PROFIBUS
device's extended diagnosisrespectively.

Alarm processing
The following alarms are reported by the Turck Excom DSB.
n Module fault on Slot n - This alarm is reported when the
diagnostic data indicates failure in the module in the slot
"n." This alarm returns to normal after fresh diagnostics are
received for the slot and the diagnostics does not indicate a
module failure.
n Channels errors of Module on Slot n - This alarm is reported
when the diagnostic data indicates a fault in a channel of a
module configured in the slot “n.” This alarm returns to
normal after fresh diagnostics are received for the slot and
the diagnostics does not indicate a channel failure.
n Rack fault on module - This alarm is reported when the
diagnostic data indicates a rack failure. This alarm returns
to normal after fresh diagnostics are received for the slot
and the diagnostics does not indicate a rack failure.

227
 Chapter 8 - Device Support Block (DSB)

UDT support for DSB blocks

With R410, youYou can create and configure user-defined
templates (UDT) for any of the DSB block types. From the
Library view, you can right-click any of the DSB block and
select Make Template. A new UDT for the DSB block is added to
the User library.

Template defining parameters for DSB block types

The following parameters are excluded from template defining
for all DSB block types.
n AUXDESC
n FIELDNETWORKNUMBER
n MASKINGNETTAGNAME
n NETTAGNAME
n NETTAGPDCNAME
n PARENTASSET
n PDCPIOMBNAME
n RESETCOUNTERS
n SLAVEADDRESS
n PDCHASHCODE
n PDCDATAXML
For a Drive DSB, the following parameters are excluded from
template defining.
n SECTIONTYPE
n SUBINDEX
For CEAG DSB, Siemens AS-I DSB, Siemens ET200 DSB, and
Turck DSB block types, the following parameter is excluded
from template defining.
n ALARMDESC

Bulk Build support for DSB block types

The Bulk Build function is extended to support the DSB user-
defined templates. You can create bulk copies of the DSB user-
defined template.

228
Chapter 8 - Device Support Block (DSB)

ATTENTION: The procedure for bulk building is identical to

bulk building any other component. Refer to the Control
Building User's Guide for more information about bulk
building.

Guidelines for configuring DSBs

You can use the Generic DSBs for configuring the devices that
do not have device-specific DSBs. You can use the device-
specific DSBs to configure the specific devices.
Configuring the device-specific DSBs is similar to configuring
the Generic DSB.However, you must remember the following
guidelines while configuring the DSBs.

DSB Name Guidelines for Configuration

Generic DSB l Appears as GENDSBDP/GENIODSBDP in the

DSB library.
l You must perform the field network configuration
in the PDC tab.

Generic l Appear as GENPADSB and GENPAGWDSB in the

DSBs for PA DSB library. You must perform the field network
devices configuration in the PDC tab.

DRIVEDSB l Appears as DRIVEDSBDP in the DSB library.

l You can only configure one input PPO type PDC
and one output PPO type PDC for a drive.
l If you need to configure additional PDCs, the
PDC types must be either "User Configurable" or
"PKW."
l The PKW Information tab is only applicable to the
DRIVEDSB.
l You must perform the field network configuration
in the PDC tab.

CEAGDSB l Appears as CEAGDSBDP in the DSB library.

l You must configure the Communication Module
PDC to ensure steady data delivery between the
CEAGDSB and the I/O devices.
l You must perform the field network configuration

229
 Chapter 8 - Device Support Block (DSB)

DSB Name Guidelines for Configuration

in the PDC tab.

Siemens AS- l Appears as SIEMENSASI in the DSB library.

i Link DSB l The Diagnostics tab is only applicable to the
Siemens AS-i Link DSB.
l You must perform the field network configuration
in the PDC tab.

Siemens l Appears as SIEMENSET200MSTD in the DSB

ET200M library.
DSB l You must select the AI sensor type and AO sensor
type while configuring the PDC.
l You must perform the field network configuration
in the IOM Configuration tab.

Turck l Appears as TURCKEXCOM in the DSB library.

Excom DSB l You must select the input signal type and output
signal type while configuring the PDC.
l You must perform the field network configuration
in the IOM Configuration tab.

Configuring a Generic Device Support Block

The Generic DSBs(GENDSB, GENIODSB, GENPADSB,
GENPAGWDSB) is configured for the PROFIBUS devices that
do not have device-specific DSBs. Although Generic DSBs can
be used for configuring devices with device-specific DSBs,
Honeywell does not recommend this.

ATTENTION: If the PROFIBUS PA devices are connected to

a transparent PROFIBUS PA Coupler, you must use the
GENPADSB. If the PROFIBUS PA devices are connected to
a DP/PA Link, Siemens DP/PA link IM-157, you must use
the GENPAGWDSB.

230
Chapter 8 - Device Support Block (DSB)

Prerequisites
n The PGM block and the Protocol Blockmust be defined.
n The PROFIBUS devices must be defined in the Field Network
Configuration tab of the Protocol Blocks.

Perform the following steps to configure a GENDSB

1. Drag-and-drop the Generic DSB
(GENDSBDP/GENIODSBDP) block from the DSB library to
one of the Protocol Blocks. The Load Dialog box appears. For
DSB blocks, the State to Load and Post Load State conditions
are not applicable. For more information on loading control
strategy components, refer to the Control Building User's
Guide.
2. Click OK. The DSB block icon appears under the Protocol
Block to which it is assigned.
3. Double-click the Generic DSB in the Project view.
4. In the Tag Name, box, type the name of the DSB (a maximum
of 40 characters) or accept the default.
5. In the Item Namebox, type the item name.
6. In the Description box, type a brief description (a maximum
of 132 characters) of the block.
7. In the Byte Order list, select the byte order. You can define
the byte order in the little-endian or big-endian format. If
you do not select the byte order, an error message
"DSBByteOrderNotSelected" appears when you load the DSB
block.

8. In the Associated Asset box, click the button. The Point

Selection dialog box appears.
9. Select an asset from those configured in the Enterprise
Model Database to set the Scope of Responsibility (SOR) for
the point. No validation is done at the configuration time. If
you enter an asset that does not exist in the points
database, the associated asset for the point reverts to the
server point. If the asset does exist but is not an area-
enabled asset, then the first area-enabled asset up the tree
is used for the SOR of that device. A subsequent upload of
that device point to Control Builder returns the area-enabled
asset and not the original non-assignable asset entered.

231
 Chapter 8 - Device Support Block (DSB)

10. In the Slave Address box, type the address number of the
PROFIBUS device.
l The PROFIBUS device address range is 2 through 125.

l This address must be identical to the address of the

PROFIBUS device defined during the field network
configuration.
l The DSB communicates with the PROFIBUS devices
through this address. The PROFIBUS device address
must be unique for a Protocol Block.

ATTENTION: For GENPADSB, the transparent segment

coupler displays all devices connected to the
PROFIBUS PA network as if they were PROFIBUS DP
field devices.

11. In the Device Type box, type the description of the device
type.
12. In the Connection Break TimeOut (Sec) box, type the duration
in seconds during which the network communication break
needs to be filtered off. If the communication break
condition persists even after this time, then the status of the
PROFIBUS device is set to “Communication Error.” This
parameter is applicable only when the PROFIBUS device is
disconnected from the Profibus network. If the complete
Profibus network is down, the status of all PROFIBUS
devices is set to “Communication Error” immediately.
13. Select the Connection Break Timeout applicable for Network
Down check box if you want the output channels to initialize
back from the user-defined values after the connection
break timeout timer is exceeded. If the complete Profibus
network is down and you have not selected this check box,
the status of all PROFIBUS devices is set to “Communication
Error” immediately. However, if you have selected this check
box and the complete Profibus network is down, the status
of all PROFIBUS devices are set to “Communication Error”
after the connection break timeout is exceeded.
14. Select the Reset counters check box if you want to reset all
static counters.

232
Chapter 8 - Device Support Block (DSB)

15. Click the Slave Status tab. The Slave Status tab displays the
responder communication standard status bits and
extended diagnostic information in the Monitoring view. .
16. Click the Alarms tab. The Alarms tab is only applicable to the
Generic DSBs and the DRIVEDSB as you can configure
alarms only for these DSBs.
17. Click the PDC tab. The PDC tab of the DSB block is used for
defining the PDCs. You cannot proceed with the DSB
configuration until you complete the PDC configuration. To
configure the PDCs, see section Configuring the PDC tab.
18. Use the online help as a guide to complete the configuration
entries on all other tabs.
19. Click OK.

Configuring a device-specific DSB

The PROFIBUS devices such as the Turck Excom, CEAG,
Siemens AS-i Link, and Siemens ET200M have device-specific
DSBs. You can use the device-specific DSB to configure these
devices.

TIP:
l You can use this procedure as a reference for
configuring the DRIVEDSB.
l The Siemens ET200MDSB is used for illustration
purpose.

Prerequisites
n The PGM block and the Protocol Blockmust be defined.
n The PROFIBUS devices must be defined in the Field Network
Configuration tab of the Protocol Blocks.

Perform the following steps to configure a device-

specific DSB
1. Drag-and-drop the DSB block from the DSB library to one of
the Protocol Blocks. The Load Dialog box appears. For DSB
blocks, the State to Load and Post Load State conditions are
not applicable. For more information on loading control

233
 Chapter 8 - Device Support Block (DSB)

strategy components, refer to the Control Building User's

Guide.
2. Click OK. The DSB block icon appears under the Protocol
Blockto which it is assigned.
3. Double-click the DSB block. The DSB block configuration
form appears.
4. In the Tag Name box, type the name of the DSB (a maximum
of 40 characters) or accept the default.
5. In the Item Name box, type the item name.
6. In the Descriptionbox, type a brief description (a maximum of
132 characters) of the block.
7. In the Byte Order list, select the byte order. You can define
the byte order in the little-endian or big-endian format. If
you do not select the byte order, an error message
"DSBByteOrderNotSelected" appears when you load the DSB
block.

8. In the Associated Asset box, click the button. The Point

Selection dialog box appears.
9. Select an asset from those configured in the Enterprise
Model Database to set the Scope of Responsibility (SOR) for
the point. No validation is done at the configuration time. If
you enter an asset that does not exist in the points
database, the associated asset for the point reverts to the
server point. If the asset does exist but is not an area-
enabled asset, then the first area-enabled asset up the tree
is used for the SOR of that device. A subsequent upload of
that device point to Control Builder returns the area-enabled
asset and not the original non-assignable asset entered.
10. In the Slave Address box, type the address number of the
PROFIBUS device.
l The PROFIBUS device address range is 2 through 125.

l This address must be identical to the address of the

PROFIBUS device defined during the field network
configuration.
l The DSB communicates with the PROFIBUS devices
through this address. The PROFIBUS device address
must be unique for a Protocol Block.

234
Chapter 8 - Device Support Block (DSB)

11. In the Device Type box, type the description of the device
type.
12. In the Connection Break TimeOut (Sec) box, type the duration
in seconds during which the network communication break
needs to be filtered off. If the communication break
condition persists even after this time, then the status of the
PROFIBUS device is set to “Communication Error.” This
parameter is applicable only when the PROFIBUS device is
disconnected from the Profibus network. If the complete
Profibus network is down, the status of all PROFIBUS
devices is set to “Communication Error” immediately.
13. Select the Connection Break Timeout applicable for Network
Down check box if you want the output channels to initialize
back from the user-defined values after the connection
break timeout timer is exceeded. If the complete Profibus
network is down and you have not selected this check box,
the status of all PROFIBUS devices is set to “Communication
Error” immediately. However, if you have selected this check
box and the complete Profibus network is down, the status
of all PROFIBUS devices are set to “Communication Error”
after the connection break timeout is exceeded.
14. Select the Reset counters check box if you want to reset all
static counters.

TIP: The RESETCOUNTER parameter is not applicable

to the Siemens AS-I DSB, Turck Excom DSB, and
Siemens ET200M DSB.

15. In the Vendor Name list, select the vendor name.

TIP: The box is applicable only to the DRIVEDSB.

16. In the Drive Control Mode list, select the control mode of the
drive. You can select the following control modes.
l SpeedControlMode

l PositioningMode

ATTENTION: Note that changing the control mode

from the Control Builder configuration does not

235
 Chapter 8 - Device Support Block (DSB)

impact the drive’s runtime. However, it only changes

the descriptions/meanings of the Control Word and
Status Word bits.

TIP:
The box is applicable only to the DRIVEDSB.

17. Click the Slave Status tab. The Slave Status tab displays the
responder communication standard status bits and
extended diagnostic information in the Monitoring view.
18. Click the Alarms tab. The Alarms tab is only applicable to the
GENDSB and the DRIVEDSB as you can configure alarms
only for these DSBs.
19. Click the PDC tab. The PDC tab of the DSB block is used for
defining the PDCs. You cannot proceed with the DSB
configuration until you complete the PDC configuration. To
configure the PDCs, see section Configuring the PDC tab.
20. Use the online help as a guide to complete the configuration
entries on all other tabs.
21. Click OK.

About initialization of AO/DO channels from

user-defined values
Background
In Experion R410.1 or earlier, wheneverWhenever there is a
communication break, the output channels (AO/DO) would
either initialize to zero or hold the last value based on the type
of the communication break. For example:
n PROFIBUS network is down - The outputs are initialized
immediately to 0 in AO channels and to OFF in DO
channels. This is the default setting for almost all the
responders.
n Break in the FTE network
l If the Hold On Failure parameter is selected and there is an

FTE communication break, the outputs hold the last good

236
Chapter 8 - Device Support Block (DSB)

value.
l If the Hold On Failure parameter is not selected, the

outputs are initialized to zero, immediately in case of an

FTE communication break.
n During break in the responder communication (where
Profibus network is up an running), DO/AO channels
initialized to 0 after communication break timeout expired.
This configuration is not desirable as all outputs initialize to
zero and in turn this affects the process.

Overview
In Experion R410.2 and later, the DSBs are enhanced such that
whenever there is a communication break within the Profibus
or in the FTE network, the output channels do not initialize
back to zero immediately. Instead, the output channels are
initialized back from the user-defined values after recovering
from the communication break condition. However, the way in
which the output channels initialize back from the user-defined
values differs based on communication break scenarios.
In Experion R430 and later,The GENPADSB and
GENPAGWDSB are available for PA devices. GENPADSB
integrates PROFIBUS PA devices to ExperionPlantCruise
through transparent PA segment couplers. GENPAGWDSB
integrates PROFIBUS PA devices to ExperionPlantCruise
through non-transparent Profibus DP/PA link, namely Siemens
DP/PA link IM-157. Note that AO/DO initialization is supported
when PA devices are disconnected from the transparent
gateway. However, AO/DO initialization is not supported when
PA devices are disconnected from the non-transparent
gateway. AO/DO initialization is supported for the non-
transparent gateway when the Siemens DP/PA link IM-157 is
disconnected.

ATTENTION: This feature is not supported for the Siemens

AS-i Link DSB.

The following table summarizes the various communication

break scenarios and provides a description of how the output
channels initialize back from the user-defined values.

237
 Chapter 8 - Device Support Block (DSB)

Scenario Output channel re-initialization description

l Profibus device is The output channels are initialized back

disconnected from the user-defined values only after the
from the network. connection breakout time timer has
exceeded.
l Profibus device
has a power
break condition
and the output
channels are in
an unpowered
state.

FTE is removed If the Hold On Failure parameter is not

selected, the channels are initialized back
from the user-defined values immediately.
The channels do not wait for the connection
breakout time timer.

PGM network is l If the Connection Break Timeout

down applicable for Network Down check box is
selected, the output channels initialize
back from the user-defined values after
the connection break timeout timer is
exceeded.
l If the Connection Break Timeout

applicable for Network Down check box is

not selected, the output channels
initialize back from the user-defined
values immediately.
The Connection Break Timeout applicable
for Network Down check box is added on the
Main tab of the DSB configuration form.
This check box is available from Experion
R410.2 and later.

Values that can be configured as

user-defined values

238
Chapter 8 - Device Support Block (DSB)

ATTENTION: When configuring the initialization values for

each channel, you must ensure that the failsafe mode
parameter value and the Init Value parameter value match
with each other.

The following table summarizes the various user-defined values

that you can define for the output channels to re-initialize after
recovering from the communication break scenarios.

User-
defined Description
value
0 - 100 l For AO channels, numeric initialization value defines
percentage value of the output.
l If you define the initial value as 0, the AO channel
initializes to 0.
l If you define a nonzero value as the initialization

value, the AO channel initializes the output value

using the range defined by the low and the high
range of the channel.
If you want the output to be initialized to a low
range, you must enter a small non-zero value like
0.001 as the initialization value. This enables the
channel value to initialize to the low range defined
for the channel. This difference is meaningful if an
AO channel is in 4-20 mA current loop.
l For DO channels, initialization value 0 defines OFF
state of the channel and value 1 defines ON state of
the channel.

NaN If the initial value is defined as NaN, the output

channels (AO and DO) hold the last output value.

0 If the initial value is defined as 0, the AO channel

initializes to the low range defined for the channel and
the DO channel is cleared to 0 during all error
scenarios.

Output channel behavior in various

scenarios

239
 Chapter 8 - Device Support Block (DSB)

The following table summarizes the behavior of AO and DO

channels in various scenarios in R410.2 and later and R410.1
or earlier.

Impact on
Impact on AO/DO AO/DO channel
channel value in value in
Scenario
Experion R410.2 Experion
and later R410.1 or
earlier

DSB is loaded for the first Clears to zero. Clears to zero.

time.

DSB is reloaded. Drives values Drives values

provided by the provided by the
controller for the controller for
connected PDCs. the connected
PDCs.

FTE connection break l Holds the last l Holds the

between controller and PGM. value if the last value if
DSB is the DSB is
configured to configured
hold the last to hold the
output value. last output
l If the DSB is value.
not configured l If the DSB is
to hold the last not
output value, configured
channel values to hold the
are initialized last output
from the user- value,
defined values. channel
values clear
to zero.

Extended diagnostics report Clears to zero. Clears to zero.

channel failure.

Extended diagnostics report Clears to zero. Clears to zero.

Module failure.

An extended diagnostic Clears to zero. Clears to zero.

overflow condition exists but

240
Chapter 8 - Device Support Block (DSB)

Impact on
Impact on AO/DO AO/DO channel
channel value in value in
Scenario
Experion R410.2 Experion
and later R410.1 or
earlier

the DSB is not configured to

ignore extended diagnostics
overflow (the Ignore
Extended Diagnostic
Overflow check box is not
selected).

Standard diagnostics report The channel Clears to zero.

Station Not Existent error. values are
initialized from
the user-defined
values.

NetX FW reports a network The channel Clears to zero.

down condition. values are
initialized from
the user-defined
values.

Network is down when PGM Clears to zero. Clears to zero.

starts up (Warm start).

Impact on DSB load

When initial value is defined for DO and AO channel, it is
possible that channel values may change surprisingly. For
example, assume that the initial value for an AO channel is
defined as 90% and the responder goes in power break
condition and recovers back. In this scenario, the output value
of the channel is 0 during power break condition and changes
to 90% immediately after the connection to PGM is re-
established.
During DSB load, PGM sets warning level error for each
channel where initial value is changed from zero to a nonzero
value. This error does not prevent loading of DSB block, but
indicates that the user has configured a feature that is rarely

241
 Chapter 8 - Device Support Block (DSB)

used in Profibus devices and may assume specific

configuration setting in the responder configuration.
The following error text appears in the Validation before load
dialog box during the DSB load.
This setting will determine the output behavior of the DSB upon
the return to normal following a loss of communication with the
responder. The user must ensure that the value entered will
result in the minimum negative impact on the process. Consult
the user manual for more details.

Configuring the PDC

The PDC tab of the DSB block is used to define the PDCs. The
PROFIBUS device data is accessed through the configuration
in the PDC tab. The PDC tab is divided into upper and lower
grid. The upper grid is used to configure the module types. The
lower grid displays the channels and the channel-related
information of the I/O modules selected in the upper grid.

ATTENTION: You can use the following procedure for

configuring parameters that are generic to all DSBs.
However, you must refer to the <DSB name> specific PDC
configuration guidelines section for information on DSB
specific parameters. For example, for Generic DSB specific
PDC configuration, you can refer to the section “Generic
DSB specific PDC configuration guidelines.”

Perform the following steps to configure the PDC

1. Click the PDC tab in the DSB block configuration form. The
PDC tab configuration form appears.
2. In the PDC Type list, select the appropriate I/O module. This
list represents the module types supported by the DSB. The
PDC types that appear in this list may vary based on the
DSB that is selected. When you select a specific PDC type in
the upper grid, all the channel information and the channel
parameters of the configured I/O modules appear in the
lower grid. After the PDC is associated with a PIOMB, you
cannot modify the PDC type.

242
Chapter 8 - Device Support Block (DSB)

3. In the PDC Description column, type a description for the

PDC. The description you provide here can be used to
identify the correct PDC when associating the PDCs to the
PIOMB.
4. In the Net Tag Name column, select the correct net tag name
against the PDC type. The tag names that appear in this list
are the names that you have defined while configuring the
PROFIBUS device in the "Profibus Network Configuration
Tool". The net tag name is unique for each I/O module. You
cannot select the same net tag name for two I/O modules
inside a PROFIBUS device. However, you can use the same
net tag name for another PROFIBUS device.
5. Select the Hold on failure check box if you want the DSB to
hold the last output value in the event of a communication
error between the C300/UOC/HCA and the PGM.
6. In the Number of Channels column, type the number of
channels that the PDC supports. By default, the number of
channels is set to "1."
7. In the Channel Description column, type a brief description
(maximum of 32 characters) of the channel.
8. In the Channel Type column, select the type of the channel.
l The channel types can be Digital Input, Digital Output,

Analog Input, and Analog Output.

l The values that appear in this list may vary based on the

DSB selected.
l If you have used the fixed PDC types, the channel types

are displayed automatically.

l You must define the channel type if you have used the

configurable input/output PDCs.

9. In the Channel Data Type column, select the data type of the
channel.
l The channel data types can be Boolean, Uint8, Uint16,

Uint32, Int8, Int16, Int32, and Float32. The values that

appear in this list may vary based on the DSB selected.
l If you have used the fixed PDC types, the channel data

types are displayed automatically.

l You must define the channel data type if you have used

the configurable input/output PDCs.

243
 Chapter 8 - Device Support Block (DSB)

10. In the Channel Data offset column, select the channel data
offset of the digital input/output channel.
11. In the Bit offset column, select the bit offset of the digital
input/output channel.
l If you have used the fixed PDC types, the bit offsets are

displayed automatically.
l You must define the bit offsets if you have used the

configurable input/output PDCs.

12. In the Low Range column, type the lowest raw value that the
channel supports. This parameter is applicable only for the
analog input/output PDCs. For digital input/output PDCs,
this parameter is non-editable. The channel low range must
be less than the channel high range. If channel low range is
greater than or equal to channel high range, the error
message "RangeorLimitCrossover" appears during the load
of the DSB block. In addition, the PDC will go into the
"Config Load Fail" state, and the DSB will go into the
"Configuration Error" state.
13. In the High Range column, type the highest raw value that
the channel supports. This parameter is applicable only for
the analog input/output PDCs. For digital input/output
PDCs, this parameter is non-editable. To prevent the
process data values from being scaled, you can set the
channel high and low range as "NaN." When this is
performed, the process value is limited by the values
supported by the data type. If PVLO and PVHI ranges are set
to NaN then RAW float of the ranges can be read for the
PDC.
14. In the Init Value column, define values for each output
channel from which the channels must initialize after
recovering from a network down condition. You can define
the following values as initial values.
l 0 - 100 For AO channels, numeric initialization value

defines percentage value of the output. For DO channels,

initialization value 0 defines OFF state of the channel and
value 1 defines ON state of the channel.
l NaN - If the initialization value is defined as NaN, the

output channels (AO and DO) hold the last output value.
l 0 - If the initialization value is defined as 0, the AO

channel initializes to 0 and the DO channel is cleared to 0

244
Chapter 8 - Device Support Block (DSB)

during all error scenarios. However, for the AO channel, if

you enter a small non-zero value like 0.001, the channel
value initializes to the low range defined for the channel.
For more information, refer to the section About
initialization of AO/DO channels from user-defined
values.
15. Click OK. You can view the PDC State, Data Module Number,
Data Size, Channel Status, Ch data Boolean, Numeric raw
data, Floating point value values in the Monitoring view
after the DSB is loaded.

Generic DSB specific PDC configuration guidelines

The following list summarizes the Generic DSB specific PDC
configuration guidelines that you must remember while
configuring the Generic DSB PDC.
n The number of PDCs supported by GENDSB is 16 and
GENIODSB is 64.
n In the Number of Channels column, you must enter the
number of channels manually.
n In the Channel Number column, you must enter the channel
numbers in increasing order. If not, this may result in an
unknown channel status behavior. Examples for correct
configuration: 0, 1, 2, 3, 4 ..... or 1, 2, 3, 4, 5..... Examples for
incorrect configuration: 0,0,1,1,2,2,3,4,5..... or
0,1,2,3,0,1,2,3,4,5.....
n In the Low Range column, you must enter the channel low
range based on the device that you have configured.
n In the High Range column, you must enter the channel high
range based on the device that you have configured.
n With R410, youYou can modify the values of the following
parameters even after a PDC is associated and connected to
a PIOMB. However, you must ensure that you reload both
the DSB and the PIOMB after modifying the parameter
value. If you do not reload both the DSB and the PIOMB,
there may be a break in the connection between the DSB
and the PIOMB.
l Number of Channels (NUMCHANNEL) - You can increase

or decrease the Number of Channels parameter value.

There is no restriction on increasing the number of
channels. However, if you want to decrease the number of

245
 Chapter 8 - Device Support Block (DSB)

channels, you can decrease the number only until the last
assigned channel number. For example, consider a
scenario where you have entered the number of channels
of a PDC as 10. However, you have assigned only 6
channels (channel 0 through channel 5) to the
PROFIBUS channels. In this scenario, you can reduce the
Number of Channels value to 6. If you try to reduce the
Number of Channels value to 5 or less, an error message
appears.
l Channel Description (CHDESCRIPTION)
l Channel Type (CHANNELTYPE) - You can modify the
Channel Type of a channel only if it that particular
channel is not associated with any PROFIBUS channel.
l Channel Data Type (CHANNELDATATYPE) - You can
modify the Channel Data Type for both used and unused
channels. However, you must ensure that while modifying
the channel data type for analog/numeric channels, you
must not select Boolean data type. For digital channels,
you must only select Boolean data type.
l Channel Low Range (CHLOWRANGE)
l Channel High Range (CHHIGHRANGE)
l Channel Data Offset (CHDATAOFFSET)
l Channel Bit Offset (CHBITOFFSET)

About Extended Diagnostic PDC

The Extended Diagnostic PDC is different from normal input or
output PDC. Extended diagnostic PDC can be configured to
parse extended diagnostic data as channel values and transfer
these channel value to PIOMB. You can configure multiple
extended diagnostic PDC depending on your requirement to
parse extended diagnostic data. If there is no extended
diagnostic data available, all channel values will be 0.

ATTENTION: You need not associate a net tag name to the

Extended Diagnostic PDC.

246
Chapter 8 - Device Support Block (DSB)

Generic Drive DSB specific PDC configuration

guidelines
The following list summarizes the Generic Drive DSB specific
PDC configuration guidelines that you must remember while
configuring the Generic Drive DSB PDC.
n The number of PDCs supported by Generic Drive DSB is 16.
n You must select the appropriate PPO type PDC from the
PDC type of the Drive DSB column.
l To access drive parameters through the PKW PDCs, you

must configure both an input and an output PKW PDC,

irrespective of whether you have channels configured for
both. If you configure only one PKW PDC, an error is
reported while loading the Drive DSB.
l You can have a maximum of one "PKW inputs" PDC and
one "PKW outputs" PDC, since there can be only one net
tag that maps to that 8-byte area. The DSB needs both an
input and an output PKW PDC to write to the PKW
request (the PKW In 8 bytes) and to read the PKW
response (the PKW Out 8 bytes) respectively. Therefore,
without an input and output PKW PDC, the DSB cannot
perform the PKW processing.
l The PKW PDC performs a size check at runtime to verify

that the data area is exactly 8 bytes. If the module data

size for a PKW PDC is not 8 bytes, that PDC state
(PDCSTATE) changes to "Configuration Failed" . You can
recover this state by re-configuring the PDC to point to
the correct net tag (which is the 8 byte PKW area) and
reloading the DSB.
l Even though the PKW PDCs can have 32 channels, all the

32 channels do not use 8 bytes simultaneously. Instead,

each channel "takes a turn" for using the 8 bytes for its
request/response processing.
n The 16 DI/DO channels of the first input/output PPO type
PDC are pre-populated by the status/control word bit
meaning/description depending on the drive's control
mode.
n You cannot change the channel type for the first 17
channels in an input or an output PPO type PDC. However,
you can change the channel type for the configurable
channels.

247
 Chapter 8 - Device Support Block (DSB)

n In the Channel Number column, the channel number is

automatically updated based on the number of channels
configured for the selected module. For example, if the
number of channels configured for a module is 4, then this
column lists the channel numbers as 0, 1, 2, and 3.
n The Channel Data Offset column displays the data offset of
the channel in bytes starting at the location defined by the
net tag. For example, the location defined for the PDC
standard channels of DI and DO of PPO type 3 and 4 have
the data offset of 0. The location defined for the PDC
standard channels of DI and DO of PPO type 1, 2 and 5
have the data offset of 8.
n The data offsets are automatically set when you select a
specific PPO type. For additional channels that do not use
the PKW area, you must configure the data and bit offset
appropriately.
n For PKW PDC types, the Channel Data Offset column is
disabled.
n The Bit Offset column displays the offset of the channel in
bits starting at the location defined by the data offset.
n For PKW PDC types, the Bit Offset column is disabled.
n In the Low Range column, you must define the low range of
the channel data in the FLOAT32 format.
n In the High Range column, you must define the low range of
the channel data in the FLOAT32 format.
n To create channels mapped to the PKW area for acyclic data
exchange, you must select the section type in the PKW
Section Type column.
n To configure the PKW area for the acyclic data transfer, you
must enter a valid parameter number in the Parameter
Number column. You can type multiple parameter numbers
for the same PKW area.
n To read or write a value, you must select the parameter sub-
index in the Array Parameter sub-index column. This column is
available for configuration only if you select the Section Type
as PKW Array.
n With R410, youYou can modify the values of the following
parameters even after a PDC is associated and connected to
a PIOMB. However, you must ensure that you reload both

248
Chapter 8 - Device Support Block (DSB)

the DSB and the PIOMB after modifying the parameter

value. If you do not reload both the DSB and the PIOMB,
there may be a break in the connection between the DSB
and the PIOMB.
l Number of Channels (NUMCHANNEL) - You can increase

or decrease the Number of Channels parameter value.

There is no restriction on increasing the number of
channels. However, if you want to decrease the number of
channels, you can decrease the number only until the last
assigned channel number. For example, consider a
scenario where you have entered the number of channels
of a PDC as 10. However, you have assigned only 6
channels (channel 0 through channel 5) to the
PROFIBUS channels. In this scenario, you can reduce the
Number of Channels value to 6. If you try to reduce the
Number of Channels value to 5 or less an error message
appears.
l Channel Description (CHDESCRIPTION)

l Channel Type (CHANNELTYPE) - You can modify the

Channel Type of a channel only if it that particular

channel is not associated with any PROFIBUS channel.
l Channel Data Type (CHANNELDATATYPE) - You can

modify the Channel Data Type for both used and unused
channels. However, you must ensure that while modifying
the channel data type for analog/numeric channels, you
must not select Boolean data type. Also, for digital
channels you must only select Boolean data type.
l Channel Low Range (CHLOWRANGE)

l Channel High Range (CHHIGHRANGE)

l Channel Data Offset (CHDATAOFFSET)

l Channel Bit Offset (CHBITOFFSET)

Generic DSB for PA devices (GENPADSB and

GENPAGWDSB) specific PDC configuration guidelines
The following list summarizes the GENPADSB and
GENPAGWDSB specific PDC configuration guidelines that you
must remember while configuring the GENPADSB and
GENPAGWDSB.
n The number of PDCs supported by GENPADSB is 8 and
GENPAGWDSB is 64.

249
 Chapter 8 - Device Support Block (DSB)

n In the PA Status Usage column, select the appropriate option

to define how the data status is used by these blocks. Based
on the option selected in the PA Status Usage column, the
channel status is updated in the Status column and the PA
Status column. The following table summarizes the options
that are available for the input/output channels and a brief
description of each option.

Options
in PA
Applicable
Status Description
for
Usage
column

Ignore Both input l For input channels, when you

and output select this option, irrespective of
channels the channel’s actual state, the
channel’s Status column always
displays the status as Good_
NonCascade and the PA Status
column displays the value Not
Applicable.
l For output channels, the channel

status is always set to GoodCasc_

NonSpecific. However, the PA
Status column displays the value
Not Applicable.
If the PA device is removed from the
network, the PA Status column
displays the value Not Available.

Update Input When you select this option, the

PA channels status is read from raw data. The
status channel’s Status column always
displays the status as Good_
NonCascade. However, the PA Status
column displays the actual device
status.

Update Input When you select this option, the

Ch channels status is read from raw data and
status channel status is updated. The
channel’s Status column and the PA
Status column display the actual

250
Chapter 8 - Device Support Block (DSB)

Options
in PA
Applicable
Status Description
for
Usage
column

device status. The Update channel

status option is selected by default.

Update Input When you select this option, the

Ch channels status is read from raw data. The
status Status column and the PA Status
and column display the actual device
alarm status. In addition, an alarm Data
status below limit in PDC is reported
if the status is below the defined first
acceptable PA status value. You must
define the first acceptable PA status
value while configuring the DSB
(GENPADSB/GENPAGWDSB) for the
alarms to be reported when the
channel status is below the first
acceptable PA status value.

Set Output When you select this option, the

output channels channel status is always set to
status GoodCasc_NonSpecific. However, the
PA Status column displays the value
Not Applicable. If the PA device is
removed from the network, the PA
Status column displays the value Not
Available. The Set output status
option is selected by default. For
GENPAGWDSB, the configurable
output channel status is always set to
GoodCas_NonSpecific even in the
absence of the device. However, the
extended diagnosis reports the device
unavailability. With the extended
diagnosis and the user-defined
alarms, you can set the PDC channel
state to Bad_NonSpecific for that
specific channel.

251
 Chapter 8 - Device Support Block (DSB)

CEAG DSB specific PDC configuration guidelines

The following list summarizes the CEAG DSB specific PDC
configuration guidelines that you must remember while
configuring the CEAG DSB PDC.
n The number of PDCs supported by CEAGDSB is 24.
n In the Number of Channel column, the number of channels
are automatically updated based on the PDC type.
n In the Channel Number column, the channel number is
automatically updated based on the number of channels
configured for the selected module. For example, if the
number of channels configured for a module is 4, then this
column lists the channel numbers as 0, 1, 2, and 3.
n In the Channel Type column, the channel type is
automatically set based on the PDC type.
n In the Channel Data Type column, the channel data type is
automatically set based on the PDC type.
n With R410, youYou can modify the values of the following
parameters even after a PDC is associated and connected to
a PIOMB. However, you must ensure that you reload both
the DSB and the PIOMB after modifying the parameter
value. If you do not reload both the DSB and the PIOMB,
there may be a break in the connection between the DSB
and the PIOMB.
l Channel Description (CHDESCRIPTION)

l Channel Low Range (CHLOWRANGE)

l Channel High Range (CHHIGHRANGE)

Siemens AS-I Link DSB specific PDC configuration

guidelines
The following list summarizes the Siemens AS-I Link DSB
specific PDC configuration guidelines that you must remember
while configuring the Siemens AS-I Link DSB PDC.
n The number of PDCs supported by the Siemens AS-I Link
DSB is 16.
n The PDC types are mapped to the AS-i PROFIBUS devices.
n This DSB supports only the DI/DO channels.

252
Chapter 8 - Device Support Block (DSB)

n If you have configured a PDC with a net tag that maps to the
data module on the second AS-i Segment, select Segment 2
in the ASISEGMENT column.
l The AS-I segment column appears only while configuring

the Siemens AS-i Link DSB for the AS-i Link Advanced .
This is because only AS-i Link Advanced supports two AS-
I segments.
l The AS-i Segment (ASISEGMENT) parameter indicates

the segment to which the PDC is configured. This

parameter can be used to identify whether the PROFIBUS
device is configured for Segment 1 or Segment 2. This
parameter is applicable only to the Siemens AS-i Link
DSB.
l It is an assumption that the configured data module for

segment 2 must be in slot 2, and the configured data

module for segment 1 must be slot 1.
n The net tag associated with the PDCs types must map to
the 4 bytes that covers the 7 or 8 PROFIBUS devices being
referenced. For more information on the PDC types of the
Siemens AS-I Link DSB, refer to the PROFIBUS Gateway
Module Parameter Reference Guide.
n In the Number of Channels column, the number of channels
are automatically updated based on the PDC type. The
"Responder 1-7 inputs" and "Responder 1-7 outputs" PDC
types have 28 channels. The other PDC types have 32
channels which are grouped as four channels for each
PROFIBUS device.
n In the Channel Number column, the channel number is
automatically updated based on the number of channels
configured for the selected module. For example, if the
number of channels configured for a module is 4, then this
column lists the channel numbers as 0, 1, 2, and 3.
n In the Channel Type , the channel type is automatically
selected based on the PDC type.
n In the Channel Data Type , the channel data type is always
"Boolean" as this DSB supports only the DI and DO
channels.
n The Channel Data Offset column is not applicable to the
Siemens AS-i Link DSB.

253
 Chapter 8 - Device Support Block (DSB)

n The Bit Offset column is not applicable to the Siemens AS-i

Link DSB.
n The Low Range column is not applicable to the Siemens AS-i
Link DSB as this DSB does not support analog channels.
n The High Range column is not applicable to the Siemens AS-i
Link DSB as this DSB does not support analog channels.
n With R410, youYou can modify the value of the following
parameter even after a PDC is associated and connected to
a PIOMB. However, you must ensure that you reload both
the DSB and the PIOMB after modifying the parameter
value. If you do not reload both the DSB and the PIOMB,
there may be a break in the connection between the DSB
and the PIOMB.
l Channel Description (CHDESCRIPTION)

Siemens ET200M DSB specific PDC configuration

guidelines
The following list summarizes the Siemens ET200M DSB
specific PDC configuration guidelines that you must remember
while configuring the Siemens ET200M DSB PDC.
n The number of PDCs supported by the Siemens ET200M
DSB is 16.
n The PDC configuration must be done through the IOM
configuration tab.
n In the Number of Channel column, you must enter the
number of channels manually.
n In the Channel Number column, the channel number is
automatically updated based on the number of channels
configured for the selected module. For example, if the
number of channels configured for a module is 4, then this
column lists the channel numbers as 0, 1, 2, and 3.
n In the AI Sensor Type column, select the sensor type
supported for the AI module. This parameter is available for
configuration only when you select the PDC type as AI.
Otherwise, this parameter is disabled. The possible values
are Unipolar, Bipolar, and Temperature Unit.
l When you select the sensor types as Unipolar or Bipolar,

the values of the CHHIGHRANGE and CHLOWRANGE

parameters are updated based on their channel high and

254
Chapter 8 - Device Support Block (DSB)

low values.
l When you select the sensor type as Temperature Unit, you

must enter the channel high range and low range

manually. The channel low range must be less than the
channel high range. If the channel low range is greater
than or equal to the channel high range, the error
message "RangeorLimitCrossover" appears during the
load of the DSB block. In addition, the PDC will go into
the "Config Load Fail" state, and the DSB will go into the
"Configuration Error" state.
n In the AO Sensor Type column, select the sensor type
supported for the AO module. This parameter is available for
configuration only when you select the PDC type as AO.
Otherwise, this parameter is disabled. The possible values
are Unipolar and Bipolar.
l When you select the sensor types as Unipolar or Bipolar,

the values of the CHHIGHRANGE and CHLOWRANGE

parameters are updated based on their channel high and
low values.
n With R410, youYou can modify the values of the following
parameters even after a PDC is associated and connected to
a PIOMB. However, you must ensure that you reload both
the DSB and the PIOMB after modifying the parameter
value. If you do not reload both the DSB and the PIOMB,
there may be a break in the connection between the DSB
and the PIOMB.
l Number of Channels (NUMCHANNEL) - You can increase

or decrease the Number of Channels parameter value.

There is no restriction on increasing the number of
channels. However, if you want to decrease the number of
channels, you can decrease the number only until the last
assigned channel number. For example, consider a
scenario where you have entered the number of channels
of a PDC as 10. However, you have assigned only 6
channels (channel 0 through channel 5) to the
PROFIBUS channels. In this scenario, you can reduce the
Number of Channels value to 6. If you try to reduce the
Number of Channels value to 5 or less an error message
appears.
l Channel Description (CHDESCRIPTION)

l Channel Low Range (CHLOWRANGE)

255
 Chapter 8 - Device Support Block (DSB)

l Channel High Range (CHHIGHRANGE)

l AI Sensor Type (AISENSORTYPE)
l AO Sensor Type (AOSENSORTYPE)

Turck Excom DSB specific PDC configuration

guidelines
The following list summarizes the Turck Excom DSB specific
PDC configuration guidelines that you must remember while
configuring the Turck Excom DSB PDC.
n The number of PDCs supported by the Turck Excom DSB is
34.
n The PDC configuration must be done through IOM
configuration tab.
n The number of channels are automatically updated based
on the module selected except for the DM80Ex digital
module.
n If you have selected the DM80Ex digital module, in the
Number of Channels column, you must manually enter the
number of channels for this module. You must enter a
number from 1 through 8 for this module.
n If you have selected the DM80Ex digital module, in the
Channel Number column, you must enter the channel
number. You must enter the channel number from 0
through 7. For other modules, the channel number is
automatically updated.
n In the Input Signal Type column, you must select the signal
type supported for the AI module . This parameter is
available for configuration only when you select the PDC
type as AI.
l When you select the signal type as Not Configured, this

turns off the specified channel. The inputs on this

channel are not processed. You must select this value for
all unused channels.
l When you select any signal type other than Not

Configured, the values of the CHHIGHRANGE and

CHLOWRANGE parameters are updated based on their
channel high and low values.

256
Chapter 8 - Device Support Block (DSB)

n In the Output Signal Type column, you must select the signal
type supported for the AO module . This parameter is
available for configuration only when you select the PDC
type as AO.
l When you select the signal type as Not Configured, this

turns off the specified channel. The inputs on this

channel are not processed. You must select this value for
all unused channels.
l When you select any signal type other than Not

Configured, the values of the CHHIGHRANGE and

CHLOWRANGE parameters are updated based on their
channel high and low values.
n With R410, youYou can modify the values of the following
parameters even after a PDC is associated and connected to
a PIOMB. However, you must ensure that you reload both
the DSB and the PIOMB after modifying the parameter
value. If you do not reload both the DSB and the PIOMB,
there may be a break in the connection between the DSB
and the PIOMB.
l Number of Channels (NUMCHANNEL) - You can increase

or decrease the Number of Channels parameter value.

There is no restriction on increasing the number of
channels. However, if you want to decrease the number of
channels, you can decrease the number only until the last
assigned channel number. For example, consider a
scenario where you have entered the number of channels
of a PDC as 10. However, you have assigned only 6
channels (channel 0 through channel 5) to the
PROFIBUS channels. In this scenario, you can reduce the
Number of Channels value to 6. If you try to reduce the
Number of Channels value to 5 or less an error message
appears.
l Channel Description (CHDESCRIPTION)

l Channel Low Range (CHLOWRANGE)

l Channel High Range (CHHIGHRANGE)

l Input Signal Type (INPUTSIGNALTYPE)

l Output Signal Type (OUTPUTSIGNALTYPE)

l Channel Number (CHNNUMBER)

257
 Chapter 8 - Device Support Block (DSB)

oHGuidelines for configuring Turck Excon DSB for

reading HART data
n To configure the Turck Excom DSB to read HART data in
addition to process data, you must configure the PDCs
based on the IO module.
l If you are using an output module, you must configure

two PDCs; one for the process data and one for the HART
data.
l If you are using an input module, you must configure only

one PDC.
n To read the process data, you must select the appropriate
PDC type (AIH40Ex/AIH41Ex/ AOH40Ex) and associate the
corresponding net tag name.
n To read HART data, you must select the HARTInputData PDC
and associate the corresponding net tag name. When you
select the HARTInputData PDC type, you must enter the
number of channels in the Number of Channels column as 1,
4, or 8 as the modules can be configured for reading 1, 4, or
8 HART data.
n When you enter the number of channels for reading HART
data, the lower grid becomes editable. You must enter the
physical channel number from where the HART data needs
to be read. The physical channel numbers start from 0.

ATTENTION: If the Number of Channels (NUMCHANNEL) is

not correctly entered or if the NETTAGNAME is wrongly
configured, then the DSB will be in configuration error
state.

Configuring AIH40Ex/AIH41 Ex module for HART data

The following table lists the IO modules and the respective PDC
type and the number of channels to be configured for reading
HART data.

258
Chapter 8 - Device Support Block (DSB)

Number of
secondary
Number
variables PDC type to be
Module Name of
configured configured
Channels
for the IO
module

AIH40Ex/AIH41Ex 1H AnalogInput- 5 (4 + 1)
AIH40Ex/AIH41Ex

AIH40Ex/AIH41Ex 4H AnalogInput- 8 (4 + 4)
AIH40Ex/AIH41Ex

AIH40Ex/AIH41Ex 8H AnalogInput- 12 (4 + 8)
AIH40Ex/AIH41Ex

The first 4 channels (0 to 3) always represent process data and

the remaining channels (from 4 up to 11) represent HART data.
For channels containing HART data, you must enter the
physical channel numbers (CHNNUMBER parameter present in
the lower grid) for all the secondary variables to which they are
associated.
For example, assume that the module is configured for 4
secondary variables out of which 2 are read from the first
channel and other 2 are from the fourth channel. In this case,
the CHNNUMBER parameter for the channels 4 through 7
should contain data as follows:

Channels Channel Number (CHNNUMBER)

Channel 4 and 5 0, 0

Channel 6 and 7 3, 3

Configuring AOH40Ex module for HART data

This module can also be configured for 1H, 4H, and 8H in the
network configuration tool. You must configure two net tag
names for this module, one for the output process data and
one for the input HART data. Therefore, you must configure two
PDCs; one output PDC for the usual process data and one
input PDC for the HART input data. In addition, you must
configure the NUMCHANNEL parameter correctly. If the
module is configured for 1H / 4H / 8H, then the number of

259
 Chapter 8 - Device Support Block (DSB)

channels should be correctly configured as 1 / 4 / 8

respectively. The CHNNUMBER parameter for all the channels
should contain the actual physical channel numbers from
which the HART data is read.
For example, assume that the module is configured for 8
secondary variables, reading 3 from first channel, 2 each from
second and third channel, and 1 from fourth channel. In this
case, the CHNNUMBER parameter for the channels 0 to 7
should contain data as follows:

Channels Channel Number (CHNNUMBER)

Channel 0, 1, and 2 0

Channel 3 and 4 1

Channel 5 and 6 2

Channel 7 3

Guidelines for configuring Turck Excon DSB for

gateway redundancy
To configure the Turck Excom DSB to know the gateway status
and to command gateway switchover, you must select the
following PDCs and associate the corresponding net tag
names.
n Gateway Status - for the status of the gateway.
n Gateway Command - for commanding switchover of the
gateway.
If the gateway PDC types are not configured, the data available
in the “Gateway Status/Command” group in the Gateway
Redundancy tab is invalid/not applicable. Similarly, if the
gateway redundancy mode if “Off” then the data in the
“Redundancy Status” group in the Gateway Redundancy tab is
invalid/not applicable.

ATTENTION: You cannot associate a Gateway Status or a

Gateway Command PDC to a PIOMB since these PDCs do
not send any process data to controller. If you try to

260
Chapter 8 - Device Support Block (DSB)

associate a Gateway Status or a Gateway Command PDC to a

PIOMB, an error message appears.

Alarms
The DSB blocks report alarms based on the standard and/or
extended diagnostic data received from the PROFIBUS devices.
The following are the standard alarms generated by all DSBs.
n Communication break with PROFIBUS responder
n PROFIBUS responder configuration failure
The following table lists the generic DSBs that supports user-
defined alarms and also the number of alarms supported by
each DSB.

DSB name Number of user-defined alarms supported

GENDSB 34

GENIODSB 130

GENPADSB 16

GENPAGWDSB 132

Drive DSB 16

You can configure alarms to parse single bit, multi bit, and
multi byte field from responder extended diagnostic data and
compare it with a given reference value. If the comparison with
the given reference value is true, then an alarm is reported with
configured priority and severity. One user-defined alarm can be
configured to parse a maximum of 32 bits in extended
diagnostic data.
You can also configure the priority and severity for each user-
defined alarms.
With R410, Generic DSBs are enhanced such that in addition to
reporting an alarm, you can choose to set the status of
individual channels to either “Good” or “Bad” based on your
requirement and as per responder extended diagnostic. For

261
 Chapter 8 - Device Support Block (DSB)

example, you can choose to set the status of the 8th channel of
the 5th PDC to “BAD” based on your requirement.
In R400, individualIndividual channel level status setting was
not supported by the GENDSB. Either all channels were set to
“Good” or all channels were set to “Bad.”
Refer to the section DSB block diagnostic alarms for
information on the alarms generated by the DSB blocks.

Alarms supported by GENPADSB

GENPADSB supports alarming based on diagnostics data
defined in Profibus PA profile.
Note that PA profile diagnostics do not set the channel status
or the PDC status as abnormal.
The Extended Diagnostics tab in the Monitoring view displays
details of each diagnostic data of the GENPADSB.

Alarms supported by GENPAGWDSB

GENPAGWDSB supports alarming based on diagnostic data
received from Siemens IM-157 DP Link. For best coverage, you
must configure 160 byte diagnostics data length while
configuring the Parameters page for IM-157, which contains
separate sections for Module diagnostic, module status, GW
diagnostics and PA responder diagnostic.
Note that IM-157 diagnostics activity do not set the channel
status or the PDC status as abornmal.
The Extended Diagnostics tab in the Monitoring view displays
details of each diagnostic data of the GENPAGWDSB.

About RIO (Remote IO) profile-based alarming

With R410, the Generic DSBs (GENDSB and GENIODSB)
support RIO diagnostics for devices which strictly adhere to RIO
standards. You must check the device and its alarming
behavior with Generic DSB before using the Generic DSB for
RIO profile-based alarming for any device. If the device does
not conform strictly to RIO standards and cannot be qualified
to be used with Generic DSB, then you can use user-
configurable alarms for alarming and channel status setting.

262
Chapter 8 - Device Support Block (DSB)

You can enable RIO profile based-alarming for Generic DSB by

selecting the ENABLERIOPROF parameter in the Alarms tab of
the Generic DSBs. By default, the ENABLERIOPROF parameter
is disabled. However, if you enable this option for devices that
do not conform to RIO standards, an alarm is reported.
For appropriate channel status setting in case of RIO profile-
based alarming, you must enter the channel number in the
CHNNUMBER parameter of PDCs of Generic DSB.
For example channel numbers for Turck DSB starts from 1. If
GENDSB is used to configure Turck IO rack, then CHNNUMBER
parameter for each PDC should be configured as 1,2,3,… for
proper channel status setting.
Based on the extended diagnostics received from PROFIBUS
device, Generic DSBs perform the following channel status and
alarm processing.
n When the PDC state is Configured, Opening PDC delivery, or
Connected, the following alarms are reported by the Generic
DSBs.
l If diagnostic data indicates failure in module in slot “n,”

then an alarm “Module fault on Slot” is reported. The Trip

Value field in the alarm summary display displays the slot
number of the faulty module reported in extended
diagnostics. All the channels of PDC configured with
module in the slot having alarm will go “Bad_
Nonspecific.” This alarm returns to normal when fresh
diagnostics is received from the device and it does not
indicate module failure. When the alarm returns to
normal after fresh diagnostic are received indicating no
error, all channel status changes to “Good_NonCascade”
for input channels and “GoodCasc_Nonspecific”for
output channels.
l If diagnostic data indicates fault in channels of module

configured in slot “n,” then an alarm “Channels errors of

Module” is reported. The Trip Value field in the alarm
summary displays the slot number of module. The
channel status of the channels for which extended
diagnostic reports error changes to “Bad_Nonspecific”
state. This alarm returns to normal when fresh diagnostic
is received for the slot and it does not indicate channel
failure. The channel status changes to “Good_
NonCascade” for input channels and “GoodCasc_

263
 Chapter 8 - Device Support Block (DSB)

NonSpecific” for output channels. Note that even if

extended diagnostic reports more than one channel of
module as faulty, only one alarm will be reported. You can
view the faulty channels from the PDC tab configuration
form. In addition, you can view the extended diagnostic
information in the Extended Diagnostics tab of the
Generic DSBs.
l When channel failure is active and module failure is

reported, then an alarm is reported due to channel failure

return to normal. In addition, an alarm due to module
failure is reported.
n When the PDC is not in Configured, Opening delivery, or
Connected state, then an alarm “Rack Fault on module” is
reported if extended diagnostic reports module errors. You
must view the Extended Diagnostics tab to determine which
module is faulty.
n When RIO profile is enabled and if diagnostic received could
not be recognized as channel, module, or identifier-related
diagnostic, then the Generic DSBs report the “Corrupt
diagnostic” alarm. This alarm returns to normal after fresh
diagnostic is received having proper extended diagnostic or
no extended diagnostic.
n When RIO profile is enabled, Generic DSBs look for reliable
extended diagnostic for processing. If standard diagnostic
indicates that there is overflow in extended diagnostics,
then the Generic DSB sets all channels of all PDCs to “Bad_
NonSpecific” state. No alarm is reported in this case.
Overflow in extended diagnostic means that the number of
diagnostic bytes increased buffer size for diagnostic in
responder. Note that though PROFIBUS standard buffer size
is of 244 bytes, this can vary according to the PROFIBUS
devices. Therefore, an option called Ignore extended
diagnostic overflow (IGNOREXTDIAGOVRFLO) is provided in
the Slave Status tab to ignore extended diagnostic overflow
and perform normal processing of diagnostic received.
For more information about RIO standards, refer to the RIO
standard documents.

264
Chapter 8 - Device Support Block (DSB)

Configuring alarms

Perform the following steps to configure an alarm

1. Click the Alarms tab.
2. In the Condition Description column, enter a description for
each condition. The maximum length of the condition must
be 32 characters. You can use special characters such as
".,/\\<>'\"*?|:;[]{}()\ for defining the condition.
3. In the Data Offset column, enter the data offset byte (0
through 238) for each alarm condition. For example if
Dataoffset = 5, then parsing needs to be started from 5th
byte of extended diagnostic data. The value 255 means that
the data offset is not defined. Values 238 through 254 are
not useful to data offset because they do not match with
any extended diagnostic data. However, having value 238
through 254 does not cause any errors.
4. In the Indication Bit column, enter the indication bit (0
through 7) from where multibit processing needs to be
performed for each alarm condition.Value n = Bit n in byte
represented by data offset. For example if parsing needs to
be started from bit 3 of byte 5 of extended diagnostic data,
then DataOffset = 5 and Bit offset = 3.
5. In the Indication Bit Field column, enter the number of bits
that you want to parse from this bit. By default, this
parameter value is 1 and the maximum value that can be
entered for this parameter is 32. By the virtue of value
entered in this field, you can have single bit, multi bit, and
multi byte parsing of extended diagnostic data for value. For
example,
l Single bit processing: If you want to process single bit of

extended diagnostic for alarming, then the value of the

Indication Bit Field = 1. If you want to process 3rd bit of
5th byte in extended diagnostic data, then DataOffset = 5,
Indication bit = 3, Indication Bit Filed =1.
l Multi bit processing: If you want to process multi bit of

extended diagnostic data, then the value of the Indication

Bit Field must be greater than 1. If you want to parse from
bit number 3 to bit number 5 of 5th byte in extended
diagnostic data, then DataOffset = 5, Indication Bit = 3
and Indication Bit Field = 3. Indication bit 3 and bit field 3

265
 Chapter 8 - Device Support Block (DSB)

means starting bit 3, 3 bits (bit 3, bit 4 and bit 5) will be

parsed for value.
l Multi Byte processing: If you want to parse 32 bits
starting bit number 4 of 5th byte of extended diagnostic,
then DataOffset = 5, Indication Bit = 4, and Indiciation Bit
Field = 32.
6. In the Comparison Operator column, select the comparison
operator with which you want to compare the data offset
value and the reference value. Default value of this
parameter is “Equals.”
7. In the Reference Value column, enter a value that you want to
have as a reference value for comparison. Default value of
this parameter is 1.
8. In the User Condition PDC column, enter the PDC number
that you want to set the status based on the alarm
condition. This parameter defines whether one/none/all
PDCs will be affected when a configured user-defined alarm
is active. Default value of this parameter is 255. The possible
values of this parameter are as follows:
l 254 - This means all PDCs in the DSB will be affected

when this user configurable alarm is active.

l 255 - This means none of the PDCs in the DSB will be

affected when this user configurable alarm is active.

l 0.. MAXPDCNUMBER - In this case, this parameter holds

a valid PDC number. The PDC number mentioned will get

affected when configured alarm is active.

ATTENTION: For GENDSB migrated from R400 to

R410, the value of this parameter is 255.

9. In the User Condition Channel column, enter the channel

number of the PDC selected that you want to set the status
based on the alarm condition. This parameter defines
whether one/all channels of PDC configured in the
USERCONDITPDC parameter is affected when configured
alarm is active. The possible values of this parameter are as
follows:
l 255 - This means all channels of configured PDC will be

affected when configured alarm is active.

266
Chapter 8 - Device Support Block (DSB)

l 0 ..MAXNUMOFCHANELS - When this parameter is

configured in the range 0..MAXNUMOFCHANELS, then
only the configured channel will be affected when
configured alarm is active.
10. In the Alarm Priority column, select the alarm priority as
required.
l For GENDSB, the first 8 alarms have the default value as

“HIGH” and remaining 24 alarms have the default value

as “LOW.”
l For GENIODSB, the default value is “NONE.”

11. In the Alarm Severity column, enter the alarm severity as

required. The default value of this parameter is 0 for both
GENDSB and GENIODSB.
12. In the Enable RIO Profile check box, select this check box if
you want the DSB to process the RIO diagnostics for devices
that conform to RIO standards. The Enable RIO Profile
check box is applicable only for GENDSB and GENIODSB.
13. In the Ignore Extended Diagnostic Overflow check box, select
this check box if you want to ignore the extended diagnostic
overflow condition and perform normal processing of
diagnostic received.
l The Ignore Extended Diagnostic Overflow check box is

applicable only for GENDSB and GENIODSB.

l The Ignore Extended Diagnostic Overflow check box is

enabled only when the Enable RIO Profile check box is

enabled.
l If you do not select the Ignore Extended Diagnostic Overflow

check box, all channels of all PDCs are set to “Bad_

NonSpecific” if the diagnostic overflow condition exists.

ATTENTION: When an extended diagnostic overflow

condition exists, all the channels of all the PDC’s are
set to Bad_NonSpecific. This is applicable to all DSBs.

14. Select the Enable PA Profile Diagnostics check box or the

Enable GW Diagnostics check box if you want to enable the PA
profile-based alarming or the IM-157 diagnostics based
alarming respectively.

267
 Chapter 8 - Device Support Block (DSB)

l By default, this option is disabled.

l For GENPADSB, this check box appears as Enable PA

Profile Diagnostics. For GENPAGWDSB, this check box

appears as Enable GW Diagnostics.
15. Select the first acceptable PA status value in the First
Acceptable PA Status Value list for the channel such that an
alarm is reported if the channel status is below this defined
value. The First Acceptable PA Status Value check box is
applicable only for the GENPADSB and GENPAGWDSB.
16. Click OK.

Support for device-specific alarms

DSB blocks report device alarms (DPV1 alarms) from the
responders based on the standard PROFIBUS specification.
Whenever the responders report a DPV1 alarm, the PGM
master reads and acknowledges the status alarm and then
reports the status alarms in the Experion station. The DSB
blocks enable you to configure 440 alarms.
The DPV1 alarms are configured in the Device Alarm Config tab
of the DSB blocks. The following figure displays an example
configuration of the DPV1 alarm configuration for TURCKDSB

block.

268
Chapter 8 - Device Support Block (DSB)

Device Alarm Config tab

The status alarm strings appearing in the station are vendor-
specific and read from the GSD file. The DPV1 alarms are
device-specific, and they are reported in the Alarm Summary
page.

Configuring device-specific alarms

Prerequisites
Ensure that the DSB is created.

To manually configure device-specific alarms

1. Double-click the DSB block. The DSB block configuration
form appears.
2. Click the Device Alarm Config tab.
3. Enter the number of diagnostic alarms in the Number Of
Diagnosis Alarms box. When you reduce the number of
alarms, the existing configured alarms at the end of the list
are deleted and cannot be recovered. Hence, you must
manually re-configure the alarms if you need the alarms
that were configured previously.
4. Enter the type of diagnosis in the Type Of Diagnosis box. The
DPV1 diagnostic values are read from the PROFIBUS
specification and configured in the GSD file. The following
table lists two examples for diagnostic values.

Type of diagnostic
Description
values

129 Status Model message

130 Module Status message

An example of the diagnostic values (129 and 130) from

GSD file for the TURCK device follows:UnitDiagType = 129
X_Unit_Diag_Bit(24) = "module diagnostics available" X_
Unit_Diag_Bit(27) = "station configuration changed" X_Unit_
Diag_Bit(28) = "undervoltage field supply Vo" X_Unit_Diag_
Bit(30) = "undervoltage field supply Vi" X_Unit_Diag_Bit(31) =
"overcurrent/short-circuit Ii" X_Unit_Diag_Bit(32) = "module
library rev. / CRC error" X_Unit_Diag_Bit(34) = "module bus

269
 Chapter 8 - Device Support Block (DSB)

error" X_Unit_Diag_Bit(35) = "master configuration error" X_

Unit_Diag_Bit(37) = "station configuration error" X_Unit_
Diag_Bit(38) = "I/Oassistant-Force Mode active" . . .
EndUnitDiagType UnitDiagType = 130 X_Unit_Diag_Area =
24-25 X_Value(1) = "slot 1: module error" X_Value(2) = "slot
1: wrong module" X_Value(3) = "slot 1: module absent" X_
Value_Help(3) = "The module is currently not plugged in." X_
Unit_Diag_Area_End X_Unit_Diag_Area = 26-27 X_Value(1) =
"slot 2: module error" X_Value(2) = "slot 2: wrong module" X_
Value(3) = "slot 2: module absent" X_Value_Help(3) = "The
module is currently not plugged in." X_Unit_Diag_Area_End
X_Unit_Diag_Area = 28-29 X_Value(1) = "slot 3: module error"
X_Value(2) = "slot 3: wrong module" X_Value(3) = "slot 3:
module absent" X_Unit_Diag_Area_End . . . EndUnitDiagType

5. In the Alarm Configuration table, perform the following:

a. Observe that the Alarm Help String is read from the GSD
file and displayed. You can also modify these strings.
b. Select the Alarm Priority from the list The Alarm Priority
can be one of the following:
l NOT CONFIGURED

l NONE

l JOURNAL

l LOW

l HIGH

l URGENT

c. Configure the Alarm Severity between 1 and 15.

d. Configure the Alarm Bit Index between 0 and 463.
e. Configure the Bit Field Size and the Bit Field Value.
6. Click OK.

To configure device-specific alarms using Auto-configure Slaves

1. Open the existing rule file in an XML editor or in Notepad.
2. Configure the following the elements with the appropriate
values.
a. DiagAlarmType
b. DiagAlarmNumber
c. DiagAlarmHelpString

270
Chapter 8 - Device Support Block (DSB)

d. DiagAlarmPriority
e. DiagAlarmSeverity
f. DiagAlarmBitIndex
g. DiagAlarmBitAreaSize
h. DiagAlarmBitAreaValue
3. Save the rule file at the default location.
4. Right-click the Protocol block, and click Auto-configure
Slaves. The Auto-configure Slaves window appears.
5. Select the check box for which the rule file is modified.
6. Type DSB name in the DSB Name column.
7. Click Validate. The Status column is updated with the
validation results.

Monitoring DSB block

TIP:
In this section, the state and command parameters of the
DSB block are listed for quick reference. For detailed
information about these parameters, you need to refer to
the PROFIBUS Gateway Module Parameter Reference
guide.

DSB block state after configuration and load

Main tab
The Slave State (SLAVESTATE) parameter will be
"COMMUNICATING." In the event of a communication loss
between the PROFIBUS master and the PROFIBUS device, the
Connection Lost Counter (DSBCONNLOSTCOUNT) will display
the count.

Slave Status tab

The Slave Device (SLAVEDEVICE) and the Watchdog On
(WATCHDOGON) LEDs will be green in normal conditions. If a
PROFIBUS device has extended diagnostics, the Extended
Diagnostics (EXTENDEDDIA) LED appears red. Similarly, the
corresponding LEDs will appear red based on the error
condition.

271
 Chapter 8 - Device Support Block (DSB)

You can view the extended diagnostics details from the Field
Network Configuration tab. See Viewing the PROFIBUS device's
extended diagnosis.

Alarms tab

ATTENTION: This tab is only applicable to the Generic DSBs

and the DRIVEDSB. After the Generic DSBs or the
DRIVEDSB is loaded, if any of the defined alarms is active,
the respective Condition Status (USERCONDITSTA)
parameter will be "ON" (checked).

The Condition Status (USERCONDITSTA) parameter will be "On

(1)" if any of the user-defined alarm conditions exists.

PDC tab / IOM Configuration tab

The following values in the PDC tab are updated from the DSB
running on the PGM.
n PDCSTATE - The state (PDCSTATE) of the PDCs that are
configured but not connected to a PIOMB will be "PDC
Configured." The state of the PDCs that are connected to the
PIOMB will be "PDC Connected." However, the state of the
PDCs that are not configured will be "PDC not Configured."
n DATAMODULENBR - The Data Module Number
(DATAMODULENBR) parameter will display the data module
number of the PDC provided by the "Profibus Network
Configuration Tool".
n PDCDATASIZE - The Data Size (PDCDATASIZE) parameter
will display the data size of the data module provided by the
"Profibus Network Configuration Tool" appears in the Data
Size column. This number appears in the Monitoring view
after the Generic DSBs is loaded.
n CHSTATUS - The status (CHSTATUS) parameter will display
the status of the channel. The status bytes are displayed
according to the Fieldbus Foundation variable status byte.
The status of the good analog and digital input channels is
"Good_NonCascade." Similarly, the status of the good
analog and digital output channels is "GoodCasc_
NonSpecific."

272
Chapter 8 - Device Support Block (DSB)

n CHLOWRANGE/CHHIGHRANGE - You can modify the

channel low range (CHLOWRANGE) and channel high range
(CHHIGHRANGE) only from the Project view. However, if the
PDC is associated with a PIOMB, you cannot modify the
ranges.
n CHDATARAW/CHDATAREAL - The analog input/output data
values will appear in the Numeric Raw Data (CHDATARAW)
and the Floating Point Value (CHDATAREAL) columns as
numeric raw data values and as scaled floating point values
respectively.
n CHDATABOOL - The digital input/output values will be
represented as 1 or 0 in the Ch data Boolean
(CHDATABOOL) column (the check box will be selected or
cleared).

Diagnostics tab
The Diagnostics tab is only applicable to the Siemens AS-i Link
DSB. This tab provides the following information.
n Internal error
n External error
n Unexpected responder configuration
n AS-Interface voltage low
n Hardware error
n DP/AS-i Link module is offline
n EEPROM is defective
n Responder errors (Segment 1)
n Responder errors (Segment 2)

ATTENTION: Note that even though the status of the

Responder errors of Segment 1 and Segment 2 are
displayed as OK in the Diagnostics tab, it does not indicate
that a PROFIBUS device exists at that position. This only
implies that no errors have been received.

PKW Information tab

The PKW information tab is only applicable to the DRIVEDSB.
This tab provides the following information.

273
 Chapter 8 - Device Support Block (DSB)

n Number of responder interrupts

n Number of PKW Response Errors
n Last PKW Error Response ID
n Last PKW Error ID

Extended Diagnostics tab

The Extended Diagnostics tab is only applicable to the Generic
DSBs. Generic DSBs support visualization of responder
extended diagnostics as per RIO profile.
Extended diagnostics tab contains three groups.
n ModuleStatus - The ModuleStatus group displays
diagnostics conforming to RIO standard. Each row in the
ModuleStatus group displays error for one slot. This group
displays the following parameters.
l MODULEERRSLOTNUM - This parameter indicates which

slot on the physical IO rack is faulty.

l MODULEERRTYPE - This parameter indicates the error

type on the slot. The error type conforms to RIO

standards.
n ChannelStatus -The ChannelStatus group displays
diagnostics conforming to RIO standard. Each row in the
ChannelStatus group displays error for one channel. This
group displays the following parameters.
l CHANERRSLOTNUM - This parameter indicates the slot

number on which the channel is bad.

l CHANERRCHAN - This parameter indicates the channel

number which is bad on the slot number indicated by

CHANERRSLOTNUM.
l CHANERRTYPPE - This parameter indicates the error type

on the channel. The error type conforms to RIO

standards.
n Raw Extended Diagnostic Data - The Raw Extended
Diagnostic Data group displays RAW diagnostic data
received from the device. Each row in the group displays 10
bytes of diagnostic in hexadecimal format, where each byte
is separated by comma. First row displays byte number 0 to
9, second row displays bytes number 10 to 19 and so on.

274
Chapter 8 - Device Support Block (DSB)

ATTENTION: The Module Status and Channel Status

groups display the diagnostics only if the
ENABLERIOPROF parameter is TRUE.

Extended Diagnostics tab of the GENPADSB and GENPAGWDSB

The Extended Diagnostics tab of the GENPADSB/GENPAGWDSB
displays the PA profile diagnostic messages and its respective
raw extended diagnostic data in the PA Diagnostic message and
the Raw Extended Diagnostic Data grids respectively.

ATTENTION: The extended PA diagnostic messages are

updated only if the Enable PA Profile Diagnostic option for
the GENPADSB or the Enable GW Diagnostics option for the
GENPAGWDSB is enabled while configuring the Alarms tab.

Gateway Redundancy tab

The Gateway Redundancy tab is only applicable to the Turck
Excom DSB. This tab provides information on the status of the
redundant gateway. In addition, you can also command a
gateway switchover from this tab.
The status of the redundant gateway will be displayed in the
Redundant Gateway Status region only if the redundancy mode is
selected as “Mode 1” while configuring the device in the
"Profibus Network Configuration Tool". Otherwise, the
Redundant Gateway Status section does not display the status of
the redundant gateway.
The Gateway Redundancy tab contains the following groups.
n Active Gateway Status / Command - This group contains the
following parameters.
l LEFTGATEWAYACTIVE - When this LED is “On” (green), it

indicates that the gateway on the left slot is active.

l RIGHTGATEWAYACTIVE - When this LED is “On” (green),

it indicates that the gateway on the right slot is active.

l GWSWITCHCMD - When this LED is “On” (green), it

indicates that gateway switchover is commanded from

the DSB.

275
 Chapter 8 - Device Support Block (DSB)

l GWSWITCHOVEREVENT - When this LED is “On” (green),

it indicates a gateway switchover.
n Redundant Gateway Status
l RDNGWMISSING - When this LED is “On” (red), it

indicates that the redundant gateway is missing.

l RDNGWNOTREADY - When this LED is “On” (red), it

indicates that the redundant gateway is not ready for

communication/data transfer.
l RDNGWERROR - When this LED is “On” (red), it indicates

that the redundant gateway has an error.

l RDNGWNOTCOMMUNICATING - When this LED is “On”

(red), it indicates that the redundant gateway is not

communicating with the master.

DPV1 tab
The DPV1 tab is applicable only for the following DSBs.
n GENDSB
n GENIODSB
n TURCKEXCOM
n CEAGDSB
n ET200MDSB
This tab is used for monitoring the status of the DPV1
read/write. The following parameters are used for monitoring
the DPV1 status.
n Parameter value (DPV1PARAMVALUE)
n Parameter status (DPV1PARAMSTATUS)
n Last Updated Time (DPV1LASTUPDATETIME) for each DPV1
request

DSB block status parameters

Slave State (SLAVESTATE)

The SLAVESTATE parameter indicates the status of the
PROFIBUS devices.

276
Chapter 8 - Device Support Block (DSB)

PDC State (PDCSTATE)

The PDCSTATE parameter indicates the status of the PDC.

Channel Status (CHSTATUS)

The CHSTATUS parameter indicates the status of the channels.

Condition status (USERCONDITSTA)

The USERCONDITSTA parameters indicates the status of the
user-defined alarm condition.

Monitoring the DPV1 data records

You can monitor the status of the DPV1 data communication
from the DSB block.

Parameter Status (DPV1PARAMSTATUS)

The Parameter Status (DPV1PARAMSTATUS) indicates the
status of every DPV1 request in the PGM.

Value (DPV1PARAMVALUE)
The Value (DPV1PARAMVALUE) parameter displays the values
that are parsed from the DPV1 response.

Last Update Time (DPV1LASTUPDATETIME)

The Last Update Time (DPV1LASTUPDATETIME) parameter
displays the time at which the values were last updated.
For more information about the DPV1 statistics, see the topic
Protocol block statistics parameters.

DSB block icons

The following table summarizes the various appearances a DSB
block can assume based on configuration, load operations, and
diagnostic data.

If icon
Then it indicates...
is...
The DSB is created but not loaded.

blue

277
 Chapter 8 - Device Support Block (DSB)

If icon
Then it indicates...
is...
All configuration parameters are loaded.

blue

The DSB or at least one PDC has configuration error or

PROFIBUS device indicates configuration error in
yellow diagnostics data and PROFIBUS device is
communicating. PDC configuration error can be non
bound net tag, input bound to output data or vice versa
or size of net tag bound to PDC is not big enough to
store data for all channels defined in PDC.

The device diagnostics data indicates that PROFIBUS

device is communicating and there are no configuration
green errors.

The device diagnostics data indicates that PROFIBUS

device is not communicating.
red

The DSB block has detected critical internal software

error that prevents communication with device. If the
red DSB block enters this state, the state does not change
until the DSB is reloaded.

DSB block diagnostic alarms

When active, the DSB block reports the following diagnostic
alarms.

Alarm Description

Communication This is a high-priority alarm that is reported

break with when the PROFIBUS device is not able to
PROFIBUS communicate with the master over the
responder network. This alarm is reported only when the
PROFIBUS network is functional. This alarm is
not generated when the master has only one
PROFIBUS device connected. This is because,
the master cannot identify if the network is

278
Chapter 8 - Device Support Block (DSB)

Alarm Description

down of if the PROFIBUS device is in a fault

state. To rectify this error, you must check the
PROFIBUS device address and the network
cabling.

PROFIBUS This is a high-priority alarm that is reported

responder when the PROFIBUS device configuration in
configuration the field network configuration does not match
failure with the PROFIBUS device hardware
configuration. To rectify this error, you must
check the PROFIBUS device configuration in
the field network.

Connection break This alarm is reported when a DSB is

with PROFIBUS physically disconnected from the PBLink or an
responder I/O module is physically disconnected from
the DSB.

Lost Connection This alarm is reported when a device is

to Responder disconnected from the PROFIBUS network.
This alarm returns to normal when the
PROFIBUS device is connected back in the
network.

Module fault on This alarm is reported when the diagnostic

Slot n data indicates failure in the module in slot "n."
When this alarm is reported, the Trip Value
field in the alarm summary displays the
module status reported in the extended
diagnostics. This alarm returns to normal after
fresh diagnostics are received for the slot and
the diagnostics does not indicate a module
failure. For each faulty slot, an alarm is
reported.

Channel errors of This alarm is reported when the diagnostic

Module on Slot n data indicates a fault in one ore more
channels of a module configured in the slot
"n." When this alarm is reported, the Trip Value
field in the alarm summary displays the faulty
channel. This alarm returns to normal after

279
 Chapter 8 - Device Support Block (DSB)

Alarm Description

fresh diagnostics are received for the slot and

the diagnostics does not indicate channel
failure. For each faulty slot, an alarm is
reported. Note that HART status or HART
communication errors are not reported to the
station.

Rack Fault on This alarm is reported when the extended

module diagnostics data indicates a rack failure. When
this alarm is reported, the Trip Value field in
the alarm summary displays the faulty module
number. For each faulty module, an alarm is
reported. For example, if there are three faulty
modules, three alarms are reported. This alarm
returns to normal after fresh diagnostics are
received for the slot and the diagnostics does
not indicate a rack failure.

Redundant This alarm is reported by the Turck Excom DSB

gateway is when the redundant gateway is missing in the
Missing I/O rack. The priority and severity of this alarm
is “HIGH” and “10” respectively.

Redundant This alarm is reported by the Turck Excom DSB

gateway is not when the redundant gateway is not ready for
Ready the switchover. The priority and severity of this
alarm is “HIGH” and “10” respectively.

Error in This alarm is reported by the Turck Excom DSB

Redundant when the redundant gateway is in an error
gateway state. The priority and severity of this alarm is
“HIGH” and “10” respectively.

Redundant This alarm is reported by the Turck Excom DSB

gateway is not when the redundant gateway is not
communicating communicating. The priority and severity of
this alarm is “HIGH” and “10” respectively.

Device not This alarm is reported by the Generic DSBs

conformant when the RIO profile-based alarming option is
enabled for a device that is not conformant to

280
Chapter 8 - Device Support Block (DSB)

Alarm Description

RIO.

Corrupt This alarm is reported by the Generic DSBs

diagnostic when the RIO profile-based alarming option is
enabled and if diagnostic received could not
be recognized as channel, module, or
identifier-related diagnostics. This alarm
returns to normal after fresh diagnostic with
proper extended diagnostic or no extended
diagnostic is received.

Profibus PA This alarm is reported by the GENPADSB if any

responder fault of the following diagnostics is active:
alarm
l DIA_HW_ELECTR
l DIA_HW_MECH
l DIA_TEMP_MOTOR
l DIA_TEMP_ELECTR
l DIA_MEM_CHKSUM
l DIA_MEASUREMENT
l DIA_NOT_INIT
l DIA_INIT_ERR
l DIA_ZERO_ERR
l DIA_SUPPLY
l DIA_CONF_INVAL
l DIA_WARMSTART
l DIA_COLDSTART
l DIA_MAINTENACE
l DIA_CHARACT
l IDENT_NUMBER_VIOLATION
l EXTENSION_AVAILABLE

Module fault in This alarm is reported by the GENPAGWDSB if

PA network any of the module/slot referred by the PDC
configuration has diagnostic data, is failed, or
has status that is not “Module OK”.

Profibus PA This is alarm is reported by the GENPAGWDSB

Gateway fault if the gateway status indicates “Configuration
fail” or “Invalid bus parameter.”

281
 Chapter 8 - Device Support Block (DSB)

Alarm Description

Profibus PA This alarm is reported by the GENPAGWDSB if

responder fault any of the responders in the PA network report
responder or channel-based diagnostics.

Diagnostic data is This alarm is reported by the GENPAGWDSB if

corrupted the structure of the IM-157 diagnostic data is
corrupted.

Data status below This alarm is reported by the GENPADSB

limit in PDC <PDC and/or the GENPAGWDSB whenever the
number> channel status is below the defined first
acceptable PA status value. For this alarm to
be reported, you must define the first
acceptable PA status value while configuring
the GENPADSB and/or GENPAGWDSB.

o Monitoring device-specific alarms

The device-specific alarms are reported in the Alarm Summary
page using the existing alarms with LED displays. The following
figure is an example of reporting the device-specific alarms.

Alarm Summary page

282
Chapter 8 - Device Support Block (DSB)

The status of the DPV1 alarms is monitored in the Device Alarm

Status tab of the DSB blocks. The following figure displays an
example configuration of the DPV1 alarm configuration for
TURCKDSB block.

Device Alarm Status tab

Setting the channel output values from

Monitoring view
If you have not associated a PDC to a PIOMB block, you can set
the analog or digital channel output values from the
Monitoring view.

ATTENTION: You cannot set the channel input values from

the Monitoring view. An error message appears when you
try to set the channel input values from the Monitoring
view.

283
 Chapter 8 - Device Support Block (DSB)

Setting the analog output values

Perform the following steps to set the analog output values

1. Select the PDC type from the PDC tab. All the channels of
the specific PDC type are listed in the lower grid.
2. Click the floating point value or the numeric raw data value
of the channel for which you want to modify the value. A
confirmation message appears.
3. Click Yes. If the PDC is associated with a PIOMB, you cannot
modify the output values. An error message appears if you
try to modify the output value.
4. Type the new value in the Numeric raw data column or the
Floating point value column. You must enter the raw value in
the Numeric raw data column and the percentage in the
Floating point value column.
5. Click OK.

Setting the digital output values

Perform the following steps to set the digital output values

1. Select the PDC type from the PDC tab. All the channels of
the specific PDC type are listed in the lower grid.
2. Clear or select the check box depending on whether the
output value needs to be ON or OFF. A confirmation
message appears.
3. Click Yes. If the PDC is associated with a PIOMB, you cannot
modify the output values. An error message appears if you
try to modify the output value.
4. Click OK.

DSB block station displays

Detail displays and faceplate names
The following table lists the names of the details display and
faceplate of the DSB block.

284
Chapter 8 - Device Support Block (DSB)

Tab Name Detail Display Faceplate

Configuration Details tab sysdtlDSBa.htm sysdtlDSBa_fp.htm

Calling up the displays

The following table lists the actions that you must perform to
call up the DSB block detail displays.

To call
the DSB Then …
block…

Config Type the DSB point name (for example DSB_132) in the
Details Station command zone and press F12. You can also
tab click the Search icon in the Station toolbar and
display

type the point name and click OK.

Detail display tab

Main tab

Detail Display of Main tab

285
 Chapter 8 - Device Support Block (DSB)

Slave Status tab

Detail Display of Slave Status tab

PDC Details tab

Detail Display of PDC Details tab

286
Chapter 8 - Device Support Block (DSB)

DPV1 Details tab

Detail Display of DPV1 Details tab

Device Alarm Status tab

Detail Display of Device Alarm Status tab

287
 Chapter 8 - Device Support Block (DSB)

Config. Details tab

Detail Display of Config. Details tab

288
CHAPTER

9 PROFIBUS HART INPUT/OUTPUT MODULE

(PBHIOM) FUNCTION BLOCK

In this section:

PBHIOMB block overview 290

PROFIBUS HART I/O channel 293
Functioning of PBHIOMB 295
Configuring a PBHIOMB block 296
PBHIOMB operations affecting the control behavior 303
Monitoring a PBHIOMB block 304
Monitoring the PBHCHANNEL block 308
PBHIOMB block station displays 315
PBHCHANNEL station displays 318

289
Chapter 9 - PROFIBUS HART Input/Output Module (PBHIOM) Function Block

PBHIOMB block overview

PBHIOMB function block represents a physical PROFIBUS
HART I/O module in the PROFIBUS RIO device. PBHIOMB
processes only the HART digital data. A PBHIOMB is associated
with a PDC defined in the DSB block. A single PBHIOMB block
supports maximum of 16 HART channels.

ATTENTION: The PBHIOMB function block can only be

associated with the following DSB blocks.

The following table lists the differences between the PBHIOMB

and the PIOMB blocks.

PBHIOMB PIOMB

Processes only the HART Processes only the process data.

digital data.

Assigned to the DSB Assigned to the C300/HCA (Control

blocks. HIVE)/UOC CEE.

The PBHIOMB function blocks are located in the PGM_IF

library in Control Builder. These blocks can be dragged and
dropped into the DSB blocks. The following figure displays
library view of the PBHIOMB block.

290
Chapter 9 - PROFIBUS HART Input/Output Module (PBHIOM) Function Block

Library view of the PBHIOMB block

The following configuration must be done in the PBHIOMB
blocks.
n PDC Name Reference must be associated to a PDC defined
in the DSB block to obtain the following information about
the PDC.
l Slave Address

l PDC Number

l PDC Description

l PDC Grouped

l Channel Number Offset

l Number of channels The Number of Channels parameter

291
Chapter 9 - PROFIBUS HART Input/Output Module (PBHIOM) Function Block

can be configured only when the PDCs are grouped.

l Slot Type

n Slot Number must be configured to identify the module

position in the chassis.

NOTE:
DSB blocks must be configured for configuring the PDC
Name Reference in the PBHIOMB block. The maximum
number of PBHIOMB supported for one PBLINK is 256
considering that a minimum of one HART device is
connected to each PBHIOMB. Hence, the number of
PBHIOMB supported on both the links is 512.

Bulk Build support for PBHIOMB block

When you create a bulk build of the PBHIOMB block, you must
configure the ASSIGNEDDSBNAME parameter in the excel
sheet to which the PBHIOMB needs to be associated. In
addition, you must configure the protocol block-related
information in the excel sheet to which the DSB is associated.
For more information about the ASSIGNEDDSBNAME
parameter, see Control Builder Parameter Reference.

PBHIOMB block creation

A PBHIOMB block is created by dragging a PBHIOMB module
template from the Library and assigning it to the DSB block in
the Project view.
You can also create a PBHIOMB block from the File menu.
(File> New > I/O Modules > PGM_IF > PBHIOMB – Profibus HART
I/O Module Block). In this method, the PBHIOMB block is
created under the “Unassigned” blocks. You must drag and
drop the PBHIOMB block to the DSB block.

PBHIOMB block deletion

The PBHIOMB block can be deleted from the Project view in
Control Builder even if the PBHCHANNEL is configured. To
delete the PBHIOMB block either from the Project view or
Monitoring view, right-click the PBHIOMB block and then click
Delete.

292
 Chapter 9 - PROFIBUS HART Input/Output Module (PBHIOM) Function Block

ATTENTION: THe PBHCAHNNELs configured under the

PBHIOMB block are also deleted when the PBHIOMB block
is deleted.

PROFIBUS HART I/O channel

The PROFIBUS HART I/O channel (PBHCHANNEL) is used for
monitoring the HART digital data. The PBHCHANNEL is
identical to the Experion Series C IO HART channels with
respect to HART parameters and system templates.

ATTENTION: The PROFIBUS HART I/O channel blocks are

not located in the PGM_IF library in Control Builder.

PBHCHANNEL block creation

The PBHCHANNEL block is automatically created under the
PBHIOMB block by configuring the HENABLE[0..15] parameter
as “TRUE” in the PBHIOMB block configuration form.
The following figure displays the PBHCHANNEL created under
the PBHIOMB block.

293
Chapter 9 - PROFIBUS HART Input/Output Module (PBHIOM) Function Block

PBHCHANNEL in the Project view

ATTENTION: By default, a unique channel name is created

for each PBHCHANNEL. When the channel name is
renamed in the Project view or from the Block Properties
page, it is automatically reflected in the HART
Configuration tab of the PBHIOMB.

The HART parameters defined in the PBHCHANNEL block can

be accessed in displays and peer nodes.

PBHCHANNEL block deletion

The PBHCHANNEL block can be deleted from the Project view
by configuring the HENABLE[0..15] parameter as “FALSE” in
the PBHIOMB block configuration form. To delete the

294
 Chapter 9 - PROFIBUS HART Input/Output Module (PBHIOM) Function Block

PBHCHANNEL from the Monitoring view, right-click the

PBHCHANNEL and then click Delete.

ATTENTION: You must load the PBHIOMB block from the

Project view after deleting the PBHCHANNEL if the
PBHIOMB block was already loaded.

Functioning of PBHIOMB
When the PBHIOMB block is activated, it can be used for the
following:
n Auto-discovery of devices
n HART profile
n IOM-related configuration
If the PBHIOMB block is loaded without any HART channels,
then it scans the HART devices that are connected to the
corresponding IOM and provides the details of the HART
devices.

ATTENTION: The PBHIOMB block allows you to create a

HART channel during run time. For more information about
configuring the HART channel during run time, see the
topic Creating a new HART channel (PBHCHANNEL) when
PBHIOMB is loaded.

Connection and status processing

When a PBHIOMB block is loaded, the connection status of the
PBHIOMB with the PROFIBUS responder is monitored and the
connection status is displayed in the Main tab using the IOM
status (IOMSTS) parameter.
The connection status of the PBHIOMB follows:
n OK: HART Profile is read successfully.
n Init (Hart Profile is not read): HART profile is not read.

295
Chapter 9 - PROFIBUS HART Input/Output Module (PBHIOM) Function Block

Configuring a PBHIOMB block

Prerequisites
n DSB for the PROFIBUS responder module is created and
configured.
n HART Device Description (DD)- based template is already
created in the Library.
n PDC grouping can be performed in the DSB, as applicable.

ATTENTION: If you configure the PBHIOMB for universal

modules, then you must need more than one PBHIOMB
blocks since the universal modules contain configurable
channels, which can be configured as Analog Input or
Analog Output. For example, if a universal module contains
eight channels, then the first two channels can be
configured as “Analog input channels” and the remaining
six channels can be configured as “Analog output
channels.”

To configure a PBHIOMB block when PDC is not

grouped
1. Click File > New > I/O Modules > PGM_IF > PBHIOMB.
When you create a PBHIOMB, it resides in the Unassigned
folder in the Project tree. You must drag-and-drop it to the
DSB.
2. (Optional) Perform the following steps.
a. Drag-and-drop the PBHIOMB from the PGM_IF library to
the DSB that is assigned to a PBLINK. The Name New
Function Blocks dialog box appears.
b. In the Destination column, you can accept the default
name or modify the name, if required and then click
Finish. The PBHIOMB block appears under the DSB block.

3. Double-click the PBHIOMB.

The PBHIOMB block configuration form appears.

296
Chapter 9 - PROFIBUS HART Input/Output Module (PBHIOM) Function Block

4. In the Tag Name box, type the name of the PBHIOMB (a

maximum of 40 characters) or accept the default.
5. In the Item Name box, type the item name.
6. In the Description (DESC) box, type a brief description of up
to 132 characters.
7. Click the point picker to configure the PDC Name Reference
(PDCNAMEREF) and then select the associated HART-
enabled device that is configured in the DSB block. The PDC
Name Reference parameter can be configured only if the
PBHIOMB is assigned to the DSB. Once the PDCNAMEREF
is selected the following parameters are updated
automatically.
l Slave Name (SLAVENAME)

l Slave Address (SLAVEADDRESS)

l Slot Type (SLOTTYPE)

l PDC Description (PDCDESCRIPTION)

l PDC Number

l Number of Channels (NUMCHANS)

l Channel Number Offset (CHANNUMOFFSET)

l PDC Grouped (GROUPEDPDC)

The PBHIOMB that is associated to a PDC can be viewed

from the PDC tab of the DSB configuration form.
The number of channels supported by the PDC is displayed
in the HART Configuration tab.
8. Type the physical slot number of the PBHIOMB in the Slot
Number (SLOTNUM) box.

ATTENTION: If the Slot Type (SLOTTYPE) parameter is

displayed as “Analog output (AO),” then AO channel
value must be manually set as equal to or greater than
3.6 mA for establishing the HART communication for
AO devices.

9. In the HART Configuration tab, perform the following steps.

a. Type the process data index in the Directory Process Data
Index (DIRPROCDATAINDEX) box.

297
Chapter 9 - PROFIBUS HART Input/Output Module (PBHIOM) Function Block

value must be taken from the device manual. See the

specific device manuals for the data. The value can also
obtained from the GSD file
b. Select the check boxes for the respective HART Enabled
channels. The channel name is automatically displayed in
the Channel Name (CHNLNAME) column.
The can be edited only in the Project view.
10. Click OK.
The HART Enabled channels appear under the PBHIOMB
block in the Project view.

To configure a PBHIOMB block when PDC is grouped

1. Click File > New > I/O Modules > PGM_IF > PBHIOMB. When
you create a PBHIOMB, it resides in the Unassigned folder in
the Project tree. You must drag-and-drop it to the DSB.
2. (Optional) Perform the following steps.
a. Drag-and-drop the PBHIOMB from the PGM_IF library to
the DSB that is assigned to a PBLINK. The Name New
Function Blocks dialog box appears.
b. In the Destination column, you can accept the default
name or modify the name, if required and then click
Finish. The PBHIOMB block appears under the DSB block.

3. Double-click the PBHIOMB. The PBHIOMB block

configuration form appears.
4. In the Tag Name box, type the name of the PBHIOMB (a
maximum of 40 characters) or accept the default.
5. In the Item Name box, type the item name.
6. In the Description (DESC) box, type a brief description of up
to 132 characters.
7. Click the point picker to configure the PDC Name Reference
(PDCNAMEREF) and then select the associated HART-
enabled device in which the PDC is grouped. Once the
PDCNAMEREF is selected the following parameters are
updated automatically.
l Slave Name (SLAVENAME)

l Slave Address (SLAVEADDRESS)

l Slot Type (SLOTTYPE)

l PDC Description (PDCDESCRIPTION)

298
 Chapter 9 - PROFIBUS HART Input/Output Module (PBHIOM) Function Block

l PDC Number
l Number of Channels (NUMCHANS)

l Channel Number Offset (CHANNUMOFFSET)

l PDC Grouped (GROUPEDPDC)

For example, consider that two analog input modules are

grouped and the slot 1 belongs to analog input module 1
and slot 2 belongs to analog input module 2.
The PDC Grouped (GROUPEDPDC) parameter is indicated as
“GREEN,” and the Number of channels (NUMCHANS)
parameter can be modified.
8. Type the physical slot number of the PBHIOMB in the Slot
Number (SLOTNUM) box. If the Slot Type (SLOTTYPE)
parameter is displayed as “Analog output (AO),” then AO
channel value must be manually set as equal to or greater
than 3.6 mA for establishing the HART communication for
AO devices.
9. In the Number of Channels (NUMCHANS) box, type the
number of channels to be associated with the PBHIOMB. If
you want to configure the PBHIOMB for slot 1, then type the
slot number in the SLOTNUM box and then type the number
of channels in the NUMCHANS box.
10. In the HART Configuration tab, perform the following steps.
a. Type the process data index in the Directory Process Data
Index (DIRPROCDATAINDEX) box.
value must be taken from the device manual. See the
specific device manuals for the data. The value can also
obtained from the GSD file
b. Select the check boxes for the respective HART Enabled
channels. The channel name is automatically displayed in
the Channel Name (CHNLNAME) column.
The can be edited only in the Project view.
11. Click OK. The HART Enabled channels appear under the
PBHIOMB block in the Project view.

To configure a PBHIOMB block for Universal Modules

1. Click File > New > I/O Modules > PGM_IF > PBHIOMB. When
you create a PBHIOMB, it resides in the Unassigned folder in
the Project tree. You must drag-and-drop it to the DSB.

299
Chapter 9 - PROFIBUS HART Input/Output Module (PBHIOM) Function Block

2. (Optional) Perform the following steps.

a. Drag-and-drop the PBHIOMB from the PGM_IF library to
the DSB that is assigned to a PBLINK. The Name New
Function Blocks dialog box appears.
b. In the Destination column, you can accept the default
name or modify the name, if required and then click
Finish. The PBHIOMB block appears under the DSB block.

3. Double-click the PBHIOMB. The PBHIOMB block

configuration form appears.
4. In the Tag Name box, type the name of the PBHIOMB (a
maximum of 40 characters) or accept the default.
5. In the Item Name box, type the item name.
6. In the Description (DESC) box, type a brief description of up
to 132 characters.
7. Click the point picker to configure the PDC Name Reference
(PDCNAMEREF) and then select the associated HART-
enabled device in which the PDC is grouped. Once the
PDCNAMEREF is selected the following parameters are
updated automatically.
l Slave Name (SLAVENAME)

l Slave Address (SLAVEADDRESS)

l Slot Type (SLOTTYPE)

l PDC Description (PDCDESCRIPTION)

l PDC Number

l Number of Channels (NUMCHANS)

l Channel Number Offset (CHANNUMOFFSET)

l PDC Grouped (GROUPEDPDC)

ATTENTION: The NUMCHANS and CHANNUMOFFSET

parameters are updated based on the type of
associated PDCNAMEREF.

8. Type the physical slot number of the PBHIOMB in the Slot

Number (SLOTNUM) box. You must type the correct slot
number since the number of channels is displayed based on
the slot number.

300
 Chapter 9 - PROFIBUS HART Input/Output Module (PBHIOM) Function Block

9. In the HART Configuration tab, perform the following steps.

a. Type the process data index in the Directory Process Data
Index (DIRPROCDATAINDEX) box.
Value must be taken from the device manual. See the
specific device manuals for the data. The value can also
obtained from the GSD file
b. Select the check boxes for the respective HART Enabled
channels. The channel name is automatically displayed in
the Channel Name (CHNLNAME) column.
The can be edited only in the Project view.
10. Click OK. The HART Enabled channels appear under the
PBHIOMB block in the Project view.

Configuring a PBHCHANNEL block

Prerequisites
n DSB for the PROFIBUS responder module is created and
configured.
l HART-enabled modules must be configured in the DSB.

n HART Device Description (DD)-based template is already

created in the Library.
n PBHCHANNEL block is created under the PBHIOMB block.

To configure a PBHCHANNEL block

1. From the Project view, double-click the PBHCHANNEL
block. The PBHCHANNEL configuration form appears.
2. In the Main tab, perform the following steps.
a. Select the device template from the Configured AI HART
Device (HCFGDEVAI) or Configured AO HART Device
(HCFGDEVAO) list. The respective DD file is associated to
the PBHCHANNEL. The device type is enabled based on
the PDC type configured in the DSB block.
b. Under HART Alarms and Events, select the Enable Option
(ALMENBSTATE) check box. For more information about
the HART alarm/event processing, see the topic HART
alarms/events processing. HART alarms are regenerated
with a new timestamp value (without original time stamp)
during the PGM switch-over.

301
Chapter 9 - PROFIBUS HART Input/Output Module (PBHIOM) Function Block

3. In the HART Variables tab, perform the following steps.

a. Configure the Scan Priority for HART Variable (HSCANCFG)
as “Low” or “High” as appropriate for scanning the HART
variable.
b. Select the Scan Dynamic Variables (HSCANDYN) check box
for monitoring the dynamic variables.
c. Select the Scan Device Variables (HSCANDEV) check box for
monitoring the device variables.
4. In the HART Notifications tab, perform the following steps.
a. Configure the Scan Priority for Command 48
(HSCANCFGC48) as “Low” or “High” as appropriate.
b. In the table, configure the Notification Option
(HCMD48NOTIFY) for each Command 48 Strings
(HCMD48STRNGS) bit as appropriate.Command 48 strings
(HCMD48STRNGS) are populated from the DD file.
5. Click OK.

Creating a new HART channel (PBHCHANNEL) when

PBHIOMB is loaded

Prerequisites
n PBHIOMB block is configured and loaded.
n The required empty channels are available in the loaded
PBHIOMB block.

To create a new HART channel when PBHIOMB is loaded

1. In Project view, double-click the loaded PBHIOMB block.
The PBHIOMB configuration form appears.
2. In the HART Configuration tab, select the check boxes for the
respective HART Enabled channels that are not configured.
The channel name is automatically displayed in the Channel
Name column.
3. Click OK. The created channels appear under the PBHIOMB
block in the Project view.

Results
The PBHCHANNEL is available for configuring the HART
parameters.

302
 Chapter 9 - PROFIBUS HART Input/Output Module (PBHIOM) Function Block

For configuring the PBHCHANNEL, see the topic Configuring a

PBHCHANNEL block.

PBHIOMB operations affecting the control

behavior
The following table summarizes the behavior of the
input/output type PBHIOMB under various scenarios.

ATTENTION: A fail-safe value means analog values are set

to NaN, digital values are set to Off, and the status is set to
"Bad."

Scenario Results

Deleting a l Strategies are affected if they have peer

PBHIOMB references to PBHIOMB parameters.
l PGM stops publishing data to the
C300/UOC/HCA.

Deleting the l Strategies are affected if they have peer

PROFIBUS references to PBHCHANNEL parameters.
HART I/O l PGM stops publishing data to the
Channel C300/UOC/HCA.
Block

Loading a l Strategies react to the fail-safe values.

PBHIOMB l CDA connection to PGM is open and input values
begin to be published.

Loading the When the PBHCHANNEL is loaded, it starts

PROFIBUS collecting the HART data and the data is ready for
HART I/O display or peer references after the first scan is
Channel complete. Until first scan is complete, fail-safe
Block values are used.

Reloading a When the PBHIOMB is re-loaded, it starts scanning

PBHIOMB the HART device. Until first scan is complete, fail-
safe values are used.

303
Chapter 9 - PROFIBUS HART Input/Output Module (PBHIOM) Function Block

Scenario Results

Reloading When the PBHCHANNEL is re-loaded, it starts

the collecting the HART data and the data is ready for
PROFIBUS display or peer references after the first scan is
HART I/O complete. Until first scan is complete, fail-safe
Channel values are used.
Block

Loss of communication scenarios

The following table summarizes the various communication
loss scenarios and the effect of the communication loss on the
input and output type PBHIOMBs.

Scenario Effect of communication loss

Loss of communication The CDA subscription time-out occurs

between and the value is set to fail-safe in the
C300/UOC/HCA and peer reference.
PGM

Loss of communication HART Data is reset to fail-safe values.

between PGM and the
device

PGM Switchover No impact to the peer reference. HART

alarms are regenerated with a new time
stamp values.

Monitoring a PBHIOMB block

In this section, the state and command parameters of the
PBHIOMB block are listed for quick reference. For detailed
information about these parameters, see PROFIBUS Gateway
Module Parameter Reference.

PBHIOMB block state after configuration and load

The behavior of the PBHIOMB block after loading the
PBHIOMB block is described.

304
Chapter 9 - PROFIBUS HART Input/Output Module (PBHIOM) Function Block

Main tab
The PBHIOMB block can be loaded only if a PDC Name
Reference (PDCNAMEREF) is configured.
When the PBHIOMB block is loaded, the
n PDC Name Reference (PDCNAMEREF) displays the
associated PDC name.
n associated DSB block name is displayed in the Responder
Name.
n Slot Number(SLOTNUM) displays the physical slot number
of the PBHIOMB.
n Number Of Channels (NUMCHANS) displays the number of
HART channels configured in the PBHIOMB.
n PDC Grouped (PDCGROUPED) displays whether the PDC is
grouped.

HART Configuration tab

The HART Configuration tab displays the Directory Process
Data Index (DIRPROCDATAINDEX) value. You can configure the
HART channels using the HENABLE parameter. The Channel
Name (CHNLNAME) parameter displays the HART channel
name that is configured under the PBHIOMB.

PBHIOMB block status parameters

The following sections explains the status of HART channels.

Auto Discovery Enabled (AUTODISCOVERYENABLED)

The AUTODISCOVERYENABLED parameter indicates whether
the auto-discovery can be initiated.
AUTODISCOVERYENABLED parameter is set as "ON" when the
PBHIOMB has the PBHCHANNEL that is not enabled and can
be used for future HART configuration. For example, the HART-
enabled (HENABLE) parameter has the five channels for HART
configuration. However, you have enabled only three channels
and the other two channels are not enabled.
AUTODISCOVERYENABLED parameter is set as "OFF" when the
PBHIOMB has all the PBHCHANNELs are enabled and
available for configuration in the Project view.

305
Chapter 9 - PROFIBUS HART Input/Output Module (PBHIOM) Function Block

Auto Discovery In Progress (AUTODISCOVERYSTATUS)

The AUTODISCOVERYSTATUS parameter indicates whether the
auto-discovery of the HART devices is in progress.

Find HART Devices (FINDDEVICES)

The FINDDEVICES parameter enables you to initiate the auto-
discovery of the HART devices.

NOTE:
The Find HART Devices (FINDDEVICES) parameter is
enabled only when the Auto Discovery Enabled
(AUTODISCOVERYENABLED) parameter is indicated as
GREEN.

HART Devices table

The HART Devices table provides information about the
following parameters.
n Tag (HTAG) name of the HART devices
n Manufacturer (HDEVMFG) name of the HART device
n Type (HDEVTYPENAME) name of the HART device
n Type (HDEVTYPE) of the HART device
n Revision (HDEVREV)of the HART device
n Id (Serial Number) (HDEVID) of the HART device
n Device Extended High Range (URL) of the HART device
n Device High Range (URV) of the HART device
n Device Low Range (LRV) of the HART device
n Device Extended Low Range (LRL) of the HART device
n Scan Priority for HART Variables (HSCANCFG) of the HART
device
n Scan Priority for Command (HSCANCFGC48) of the HART
device

About auto-discovery of HART devices

The PBHIOMB block enables you to find the HART devices that
are connected to the HART IO module. The auto-discovery of
the HART devices can be performed only when the loaded

306
 Chapter 9 - PROFIBUS HART Input/Output Module (PBHIOM) Function Block

PBHIOMB have some channels (PBHCHANNEL) that are not

configured.

ATTENTION: If all the channels in the PBHIOMB are

configured, then the auto-discovery of HART devices is not
possible.

You can use the Find HART Devices (FINDHDEVICES)

parameter to discover the HART devices that are connected to
the HART IO module. The following figure displays the
PBHIOMB configuration
form when the auto-discovery of HART devices is enabled.

Auto-discovery of HART channels

The following table explains when the auto discovery of HART
devices can be performed.

Table 9-1: Parameter usage for auto discovery of HART devices

Parameter Description Usage

Auto Discovery Enabled Used for Displayed as

(AUTODISCOVERYENABLED) indicating GREEN when the

307
Chapter 9 - PROFIBUS HART Input/Output Module (PBHIOM) Function Block

Parameter Description Usage

whether the auto-discovery of

auto- HART devices can
discovery of be initiated.
HART Displayed as
devices can GRAY when the
be initiated. auto-discovery of
HART devices
cannot be
initiated.

Auto Discovery In Progress Used for Displayed as

(AUTODISCOVERYSTATUS) indicating GREEN when the
the progress auto discovery of
of the auto HART devices is in
discovery of progress.
HART Displayed as
devices. GRAY when the
auto discovery of
HART devices is
not in progress.

Find HART devices Used for Lists all the HART

(FINDHDEVICES) initiating the devices that are
auto- connected to the
discovery of HART IO module.
the HART
devices.

ATTENTION: After completing the discovery of HART

devices, you must manually configure the PBHCHANNELs
from the Project view using the HENABLE parameter.

Monitoring the PBHCHANNEL block

In this section, the state and command parameters of the
PBHCHANNEL block are listed for quick reference. For detailed
information about these parameters, see PROFIBUS Gateway
Module Parameter Reference.

308
Chapter 9 - PROFIBUS HART Input/Output Module (PBHIOM) Function Block

ATTENTION: The update rate of parameters, depends on

the following conditions:

PBHCHANNEL HART Status-related parameters

General Device Status

The standard diagnostics that are active for the connected
HART device can be monitored in the General Device Status.

Device Specific Status (Command 48)

The Command 48 diagnostics that are active for the connected
HART device can be monitored in the Device Specific Status
(Command 48).

HART Communication Status (HCOMSTS)

The HART Communication Status (HCOMSTS) parameter
displays the communication status with the HART device.

Last Communication Failure (HCOMFAIL)

The Last Communication Failure (HCOMFAIL) parameter
indicates the last communication failure based on the status of
the HCOMSTS parameter.

Failed Command (HCMDFAIL)

The Failed Command (HCMDFAIL) parameter indicates the
HART command number that failed.

Failed Response Code (HCMDRESP)

The Failed Response Code (HCMDRESP) parameter indicates
the response code from the failed command listed in the
HCMDFAIL parameter.

Communication Errors (HNCOMERR)

The Communication Errors (HNCOMERR) parameter indicates
the number of communication errors occurred from last reset.

309
Chapter 9 - PROFIBUS HART Input/Output Module (PBHIOM) Function Block

Restore Errors and Failure (RESETHCOMERR)

The Restore Errors and Failure (RESETHCOMERR) parameter
resets HART communication diagnostic parameters to their
default values.

PBHCHANNEL HART Notification-related parameters

Scan Priority for Command 48 (HSCANCFGC48)

The Scan Priority for Command 48 (HSCANCFGC48) parameter
can be low or high. The ratio of high to low priority scan is
configured in the DPV1 tab of the DSB level.

Command 48 Strings (HCMD48STRNGS)

The Command 48 Strings (HCMD48STRNGS) parameter
displays the strings embedded in the DD file.

Notification Option (HCMD48NOTIFY)

The Notification Option (HCMD48NOTIFY) parameter indicates
the notification option that you have configured.

ATTENTION: This parameter is not available in the device.

However, this parameter can be configured to generate
either an Event or an alarm or View Only. By default, this
parameter is set as “Event.”

PBHCHANNEL HART Variables-related parameters

In the HART Variables tab, you can monitor the device variables
and the dynamic variables of the PBHCHANNEL.

Dynamic Variable Name (HDYNNAME)

The Name (HDYNNAME) parameter displays the HART digital
variable name provided you for identifying the variable..

Dynamic Variable Code (HDYNDVC)

The Variable Code (HDYNDVC) parameter displays the
configured HART digital variable codes.

310
Chapter 9 - PROFIBUS HART Input/Output Module (PBHIOM) Function Block

Dynamic Variable Descriptor (HDYNDSC)

The Descriptor (HDYNDSC) parameter displays the description
provided for each HART digital variable.

Dynamic Variable Value (HDYNVAL)

The Value (HDYNVAL) parameter displays the configured value
for each HART digital value.

Dynamic Variable Units (HDYNEU)

The Units (HDYNEU) parameter displays the engineering units
provided for HART digital data.

Dynamic Variable Classification (HDYNCC)

The Classification (HDYNCC) parameter displays the
classification code provided for each HART data.

Dynamic Variable Status (HDYNST)

The Status (HDYNST) parameter displays the status set for
each HART data.

Device Variable Name (HSLOTNAME)

The Name (HSLOTNAME) parameter displays the configured
slot variable name for each HART device.

Device Variable Code (HSLOTDVC)

The Variable Code (HSLOTDVC) parameter displays the variable
code provided for the configured slot.

Device Variable Descriptor (HSLOTDSC)

The Descriptor (HSLOTDSC) parameter displays the description
provided for the configured slot.

Device Variable Value (HSLOTVAL)

The Value (HSLOTVAL) parameter displays the configured
value for the configured slot.

311
Chapter 9 - PROFIBUS HART Input/Output Module (PBHIOM) Function Block

Device Variable Units (HSLOTEU)

The Units (HSLOTEU) parameter displays the engineering units
configured for the configured slot.

Device Variable Status (HSLOTST)

The Status (HSLOTST) parameter displays the variable status
set for the configured slot.

Device Variable Classification (HSLOTCC)

The Classification (HSLOTCC) parameter displays the variable
classification provided for the configured slot.

PBHCHANNEL HART Identification-related

parameters
The HART Identification tab provide information about the
HART device.

Configured Device
The following parameters display the information about the
configured HART device.
n Manufacturer (HDVMFGCD): Used for displaying the
configured manufacturer ID.
n Type (HDVTYPCD): Used for displaying the configured device
type.
n Type Name (HDVTYPCDNAME): Used for displaying the
configured device type name.
n Revision (HDVREVCD): Used for displaying the revision of
the configured device.
n Id (Serial Number) (HDEVIDCD): Used for displaying the serial
number of the configured device.

Installed Device
The following parameters display the information about the
installed HART device.
n Manufacturer (HDEVMFG): Used for displaying the
manufacturer ID of the installed HART device.
n Type (HDEVTYPE): Used for displaying the device type of the
installed HART device.

312
Chapter 9 - PROFIBUS HART Input/Output Module (PBHIOM) Function Block

n Type Name (HDEVTYPENAME): Used for displaying the device

type name of the installed HART device.
n Revision (HDEVID): used for displaying the revision of the
installed HART device.
n Id (Serial Number) (HDEVID): Used for displaying the serial
number of the installed HART device.
n Device Type Mismatch (HDEVMISM): Used for indicating the
mismatch between the currently connected device and the
configured HART device.
n Device Revision Mismatch (HREVMISM): Used for indicating
whether the existing device revision is different from the
installed device.
n Device ID Mismatch (HDEVIDFL): Used for indicating whether
the configured device ID is different from the connected
device ID.
n Supported HART version (HARTVERSION): Used for displaying
the supported HART version, like HART 6.0 and HART 7.0.
n Universal Command Revision (HUCMDREV): Used for
displaying the supported HART command revision.
n Software Revision (HSWREV): Used for indicating the software
revision.
n Hardware Revision (HHWREV): Used for indicating the
hardware revision.
n Device Profile Code (HDEVPROFILE): Used for displaying the
HART device profile information.
n Private Label Distributor (HPVTLDST): Used for displaying the
label as received in the command 0.

HART alarms/events processing

HART alarms/events are processed periodically in the
PBHCHANNEL, which is associated with the PBHIOMB.
There are two types of HART alarms/events that are used for
monitoring the HART devices.
n Device status
n Command 48
The following operations are periodically performed for
processing the HART alarms/events.

313
Chapter 9 - PROFIBUS HART Input/Output Module (PBHIOM) Function Block

1. Check if there is a change in the DD template or HART

notifications," then
a. disable all existing alarms/events
b. re-report all the existing alarms/events so that
alarms/events are updated in the station with the new
strings defined in DD file or based on new HART
notifications configuration.
2. Check whether the ALMENBSTATE/JOURNALONLY state is
changed. The alarms/events must be enabled or disabled
based on the ALMENBSTATE/JOURNALONLY state.
3. Check whether the new alarms/events are reported from the
previous scanning for both Device status and command 48
alarm/events. If yes, then report all the new alarm/events.

ATTENTION: If there is any PGM switch-over, then the

status of all existing alarms/events is RTN and the
alarms/events are regenerated with new timestamp in the
station.

Device status alarms

PBHCHANNEL supports 32 HART device status alarms (that is,
4 bytes). Each bit defines an alarm.
Byte 0 represents field device status, which is updated
periodically for every HART command response data. Byte 0
defines the following alarms.
n Bit 7: Field device malfunction alarm
n Bit 6: Configuration has changed
n Bit 5: Cold Start (device has reset/power cycled)
n Bit 4: More Status Available
n Bit 3: Loop current fixed
n Bit 2: Loop current saturated (PV out of limits)
n Bit 1: Non-primary variable out of limits
n Bit 0: Primary variable out of limits
Byte 1 and Byte 2 represent any mismatch between the
configured HART device and the connected HART device. In
addition, they represent any communication related status or
failures. Byte 1 and Byte 2 define the following alarms.

314
 Chapter 9 - PROFIBUS HART Input/Output Module (PBHIOM) Function Block

n Scan Over run

n HART Command Failed
n Excess communication errors
n HART communication failure
n Secondary master present
n Device ID mismatch
n Device revision mismatch
n Device type mismatch
n Device range mismatch
Byte 3 represents the extended field device status from the
HART 6.0 devices.
n Bit 7 - Bit 2: Not defined
n Bit 1: Device variable Alert
n Bit 0: Maintenance Required

Command 48 alarms
Command 48 alarm bits represent additional device status
information. There are totally 200 bits that are defined to
represent different status information and described in the
vendor specific DD files.

HART alarms/event regeneration

HART alarms/events are regenerated for the PBHCHANNEL
from the protocol block when there is a regeneration request
from the CDA communication.

PBHIOMB block station displays

The following table lists the detail displays and the faceplate
name that are used for viewing and monitoring the PBHIOMB
from the station.

Tab Name Detail Display Faceplate Name

Main tab sysdtlPBHIOMBa sysdtlPBHIOMBa_fp

HART channels tab sysdtlPBHIOMBb

315
Chapter 9 - PROFIBUS HART Input/Output Module (PBHIOM) Function Block

Tab Name Detail Display Faceplate Name

Config. Details tab sysdtlPBHIOMBc

Main tab - Detail Displays

The Main tab detail display provides information such as the
name of the point detail display, group detail display, and the
faceplate. In addition, a hyper-link is provided to the detail
display of the DSB to which this PBHIOMB is associated for
navigation.

Main tab detail display

HART channels-Detail Display

The HART Channels tab detail display provides information such
as the channel name, PV/OP, device tag, device manufacturer,
device type name, device type, and device revision. In addition,
a hyper-link is provided to the detail display of the HART
channel (PBHCHANNEL) to which this PBHIOMB is associated
for navigation.

316
Chapter 9 - PROFIBUS HART Input/Output Module (PBHIOM) Function Block

HART Channels detail display

Config. Details tab-Detail Display

The Config Details tab detail display is identical to the
configuration form of the PBHIOMB block (from Control
Builder).

Config. Details tab detail display

317
Chapter 9 - PROFIBUS HART Input/Output Module (PBHIOM) Function Block

PBHCHANNEL station displays

The following table lists the detail displays and the faceplate
name that are used for viewing and monitoring the
PBHCHANNEL from the station.

Tab Name Detail Display Faceplate Name

Main tab sysDtlPbHchannela sysDtlPbHchannela_fp

Config. Details sysDtlPbHchannelb

tab

Main tab - Detail Displays

The Main tab detail display provides information such as the
name of the point detail display, group detail display, and the
faceplate. In addition, a hyper-link is provided to the detail
display of the DSB to which this PBHCHANNEL is associated
for navigation.

Main tab detail display

318
Chapter 9 - PROFIBUS HART Input/Output Module (PBHIOM) Function Block

Config. Details tab-Detail Display

The Config Details tab detail display is identical to the
configuration form of the PBHCHANNEL block (from Control
Builder).

Config. Details tab detail display

319
CHAPTER

10 PROFIBUS I/O MODULE (PIOMB) FUNCTION

BLOCK

In this section:

PIOMB block overview 321

PROFIBUS I/O channel blocks 322
Functioning of PIOMB 324
Configuring a PIOMB 340
Assigning a PROFIBUS Channel to PIOMB 342
Monitoring PIOMB block 345
PIOMB block station displays 348

320
Chapter 10 - PROFIBUS I/O Module (PIOMB) Function Block

PIOMB block overview

The PIOMB function block represents a physical I/O PROFIBUS
device. It provides the user-visible interface between the control
strategies and the process data on a device. The PIOMB also
performs the scaling of the raw process data from the device.
The PIOMB is used to encapsulate the data from a PDC of a
DSB. Control data that flows in and out of the C300/UOC/HCA
Controller passes through the PIOMB to and from the
PROFIBUS I/O channel blocks. Note that process data is not
available for the control strategies from the PIOMB directly. It is
made available to the PROFIBUS I/O channel blocks that are
assigned to the PIOMB. For more information on the
PROFIBUS I/O channel blocks, see PROFIBUS I/O Channel
Blocks.
In addition to the channel process values, the PIOMB FB also
receives and provides the process data status that reflects the
health of the PROFIBUS device as well as the connection
between the PGM and the C300/UOC/HCA. The PIOMB does
not support any command or configuration parameters for
directly controlling a device. The DSB is the means by which to
access device specific data including the diagnostics
information.
The PIOMB function blocks are located in the PGM_IF library in
the Control Builder. These blocks can be dragged and dropped
into the CEE/CM in the C300/UOC/HCA. The only
configuration required by the user is associating the PIOMB
block with a PDC of a DSB contained within a PGM. Only one
PDC can be associated with a given PIOMB.
The number of PIOMB blocks that can be instantiated or
loaded to the C300/UOC/HCA is limited by the controller
resources including the total amount of process data provided
and consumed by the C300/UOC/HCA, CEE/CM memory, and
CPU.
Loading a PIOMB FB is identical to loading other function
blocks. A PIOMB block can be loaded only when it is
successfully associated with a PDC.

321
 Chapter 10 - PROFIBUS I/O Module (PIOMB) Function Block

PIOMB block creation

A PIOMB block is created by dragging a PIOMB module
template from the Library tab and assigning it to the CEE/CM
of the C300/UOC/HCA Controller in the Project view.
You can also create a PIOMB block in the Control Builder from
the File menu
(File > New > I/O Modules > PGM_IF > PIOMB - Profibus I/O
Module Block).

PIOMB block deletion

You must inactivate a PIOMB before deleting it from the
Monitoring view.
A CEE/CM cannot be deleted from the Project view in Control
Builder unless all the contained blocks including the PIOMB
and the Control Modules containing the PROFIBUS I/O
channels are deleted. After the contained blocks are deleted,
the communication with the PGM ceases.

PROFIBUS I/O channel blocks

The PROFIBUS I/O channels represent logical I/O points of the
PROFIBUS device. The PROFIBUS I/O channel blocks fetch
data from and write data to the PIOMB, based on whether the
channel type is an input channel or an output channel.
The following are the four PROFIBUS I/O channel blocks that
can be assigned to the Control Module containing the CEE to
which the PIOMB is associated.
n PbAiChannel - Represents an analog input point.
n PbDiChannel - Represents a digital input point.
n PbAoChannel - Represents an analog output point.
n PbDoChannel - Represents a digital output point.
The PROFIBUS I/O channel blocks are located in the PGM_IF
library in the Control Builder. A PROFIBUS I/O channel block is
assigned to a Control Module by dragging the appropriate
channel block from the Library view into the CM to which the
CEE containing the PIOMB block is assigned.

322
Chapter 10 - PROFIBUS I/O Module (PIOMB) Function Block

For example, if the channel type of a PDC is Digital input (DI),

you must drag-and-drop PBDICHANNEL from the PGM_IF
library into the Control Module containing the CEE.
The following figure displays a sample Control Module with
PROFIBUS I/O channel blocks.

Function
The execution period of the PROFIBUS I/O channel function
blocks is dependent on the execution period of the Control
Module which contains the PROFIBUS I/O channel.
The PbAiChannel and PbDiChannel blocks fetch real-time data
from the PIOMB for use in the control strategies.

323
 Chapter 10 - PROFIBUS I/O Module (PIOMB) Function Block

The PbAoChannel and PbDoChannel blocks feed data from the

control strategies to the PIOMB to be sent to the PROFIBUS
devices.

Functioning of PIOMB
The PIOMB function block executes as an independent block at
the base period of the CEE, which contains the PIOMB function
block.
When the PIOMB is in an "ACTIVE" execution state, it performs
the following actions.
n Connects to the DSB on load and receives data when active.
n If the PDC is an input type PDC, performs input module
processing.
n If the PDC is an output type PDC, performs output module
processing.

Connection and status processing

When a PIOMB is loaded, the connection status of the PIOMB
with the PDC is monitored and the connection status is
displayed in the Module Configuration tab of the PIOMB block.
The following are the possible connection statuses.
n Connected - The PIOMB is able to connect to the PDC with
which it is associated.
n NotConnected - The PIOMB is unable to connect to the PDC
with which it is associated.
n ConfigError - The PIOMB association with the PDC has
runtime errors.
If the communication path is not intact, the PIOMB performs
the following:
n Generates the Communication Error notification.
n Sets input data to fail-safe values.
n Sets output data to back initialize.

324
Chapter 10 - PROFIBUS I/O Module (PIOMB) Function Block

Input module processing

If the PDC type is an input type and the communication path is
intact, the PIOMB performs the following:
n Receives the most recent input data for the device from the
PGM.
n Stores the input data and the status in the function block
parameters and makes it available to the channels.

Output module processing

If the PDC type is an output type and the communication path
is intact, the PIOMB performs the following:
n Receives and stores the read-back values and the status in
the function block.
n Stores the output values that are to be sent to PGM in the
communication layers of the devices.

Clamping of output process values

The PIOMB clamps the process data in the following two
scenarios.
n If the process value to be passed between the PIOMB and
the DSB exceeds the values supported by the configured
channel data type. In such a scenario, the process value will
be clamped to the maximum or the minimum value
supported by the channel data type.
n The analog output value will be clamped to match the
channel data type. This clamping will occur only after the
value is scaled.

Scaling of process data

The PIOMB handles the process value conversion between raw
and percentage. When a PIOMB is associated with a PDC, the
channel high range and the channel low range values of each
channel is made available to the PIOMB. The channel low range
is equivalent to 0% and the channel high range is 100% of the
process value.

325
 Chapter 10 - PROFIBUS I/O Module (PIOMB) Function Block

ATTENTION: To prevent the process data from being

scaled, you can set the channel high and low range as
"NaN” when configuring the DSB. When this is performed,
the process value will be limited to those values supported
by the data type.

Notifications
The PIOMB block reports the following notification.
n Communication Error.

Example to illustrate operations affecting the control

behavior
In the following example, the CM1 has a PROFIBUS AI channel
(represents a channel from a PROFIBUS DP) connected to
C300/UOC/HCA Dataacq block. This block is connected to
PID.P1 and the PID.OP is connected to a PROFIBUS AO
channel (represents a channel from a PROFIBUS DP).

326
Chapter 10 - PROFIBUS I/O Module (PIOMB) Function Block

The following table summarizes the behavior of the

input/output type PIOMB under various scenarios.

ATTENTION: A fail-safe value means analog values are set

to NaN, digital values are set to Off, and the status is set to
"Bad."

Input type Output type

Scenario Prerequisites
PIOMB PIOMB
Inactivatin l PIOMB and l Input l Channel
g a PIOMB CM1 are process blocks
active. data is set request
l CEE is in the to fail-safe upstream
Run state. values. blocks to go
l
l Strategies into
react to the initialization.
C300
/UOC/HCA fail-safe l Upstream
and PGM are values. Regulatory
communicatin l PGM Control block
g. continues realizes it is
its connected to
operations an I/O
and Channel and
publishes goes into
data to the initialize
C300 manual state.
/UOC/HCA. l PGM output

327
 Chapter 10 - PROFIBUS I/O Module (PIOMB) Function Block

Input type Output type

Scenario Prerequisites
PIOMB PIOMB

to PROFIBUS
devices hold
their last
values.
l Channel data
is displayed
as "NaN" or
"0" and
channel
status is
displayed as
"Bad."
l Actual output
values and
channel
status are
available on
the DSB.

Inactivatin l PIOMB and l Channel l Control loop

g a CM CM1 are data is set stops
containing active. to fail-safe executing and
the l CEE is in the values. calculating
PROFIBUS Run state. l PGM new values.
I/O l continues l AOC.OP holds
Channel C300 its its last value.
Block /UOC/HCA operations l PIOMB
and PGM are and output for
communicatin publishes that channel
g. data to the holds its last
C300 value.
/UOC/HCA. l PGM output
and
PROFIBUS
device for that
point hold
their last
value.

Changing l PIOMB and l Channel l Control loop

the state of CM1 are data is set stops

328
Chapter 10 - PROFIBUS I/O Module (PIOMB) Function Block

Input type Output type

Scenario Prerequisites
PIOMB PIOMB
the CEE active. to fail-safe executing and
containing values. calculating
l CEE is in the
the PIOMB Run state. l PGM new values.
to "Idle" l continues l AOC.OP holds
C300 its its last value.
/UOC/HCA operations l PIOMB
and PGM are and output for
communicatin publishes that channel
g. data to the holds its last
C300 value.
/UOC/HCA. l PGM output
and
PROFIBUS
device for that
point hold
their last
value.

Deleting a l PIOMB is l Strategies l Strategies are

PIOMB inactive. are not not affected
l CM1 is active. affected because the
because PIOMB has
l CEE is in the
the PIOMB already been
Run state.
has already inactivated.
l
been l PIOMB closes
C300 inactivated. its PDA
/UOC/HCA l PIOMB connection
and PGM are
closes its with the PGM.
communicatin
PDA Output of
g. l

connection PROFIBU
with the device goes
PGM. unpowered as
l PGM stops defined by the
publishing DSB.
data to the
C300
/UOC/HCA
from the
associated
PDC.

Deleting a l PIOMB and l Channel is l Channel is

329
 Chapter 10 - PROFIBUS I/O Module (PIOMB) Function Block

Input type Output type

Scenario Prerequisites
PIOMB PIOMB
CM CM1 are deleted deleted when
containing active. when the the CM is
the l CEE is in the CM is deleted.
PROFIBUS Run state. deleted. l Last output
I/O l
l No changes values are
Channel C300 to the held.
Block /UOC/HCA strategies,
and PGM are the
communicatin C300
g. /UOC/HCA
to PGM
connection,
or the
PIOMB
functions
occur.

Loading a l CM1 is active. l Channel l Channel

PIOMB data is set blocks
l CEE is in the
Run state. to fail- safe request
l
values. upstream
Strategies blocks to go
C300 l

react to the into

/UOC/HCA
fail- safe initialization.
and PGM are
communicatin values. l Upstream
g. l Connection Regulatory
to PGM is block realizes
open and it is
input connected to
values an I/O
begin to be Channel and
imaged goes into
from the initialize
PGM to the manual state.
C300 l No output
/UOC/HCA . value for any
channel is
sent to the
PGM.
l Output of
PROFIBUS
device holds

330
Chapter 10 - PROFIBUS I/O Module (PIOMB) Function Block

Input type Output type

Scenario Prerequisites
PIOMB PIOMB

last output.

Loading a l PIOMB is When a CM

CM active. containing the
containing l CEE is in the PROFIBUS I/O
the Run state. channel block
PROFIBUS l
is loaded, the
I/O C300 input channel
Channel /UOC/HCA values are
Block and PGM are already being
communicatin imaged from
g. the PGM to
the
C300
/UOC/HCA so
the PIOMB
holds the
latest values.
Output
channels back
initialization
values are also
available on
the PIOMB.
None of these
values are
used by the
I/O Channel
until the CM is
activated.

Reloading l CM1 is active. You must

a PIOMB inactivate the
l CEE is in the
Run state. PIOMB to
l
reload it. You
C300 cannot make
/UOC/HCA any changes
and PGM are PROFIBUS-
communicatin specific
g.

331
 Chapter 10 - PROFIBUS I/O Module (PIOMB) Function Block

Input type Output type

Scenario Prerequisites
PIOMB PIOMB
changes or
PDC
association
specific
changes to
the PIOMB
after it is
loaded. The
connection
remains open
and the
PIOMB
behavior is
same as
loading of
PIOMB.

Reloading l PIOMB is You must

a CM active. inactivate the
Containing l CEE is in the CM to reload
the Run state. it. When a CM
PROFIBUS l
is reloaded, its
I/O C300 behavior is
Channel /UOC/HCA same as
Block and PGM are loading a CM
communicatin containing
g. PROFIBUS I/O
channel
blocks.
However, the
PIOMB will
hold the last
output value
received from
the channel
block, and this
value will be
held by the
PROFIBUS

332
Chapter 10 - PROFIBUS I/O Module (PIOMB) Function Block

Input type Output type

Scenario Prerequisites
PIOMB PIOMB
device.

Reloading l PIOMB is When When

the CEE inactive. C300 C300/UOC/HCA
containing l CEE is in the /UOC/HCA and PGM are not
the Idle state. and PGM are communicating
PROFIBUS l
communicatin - This scenario is
I/O C300 g - This identical to Loss
function /UOC/HCA scenario is of
blocks and PGM are identical to C300/UOC/HCA
communicatin deleting a power or RAM
g. PIOMB. Retention
Restart.
l The CEE
block will l The CEE
be loaded block will be
but the loaded but
control the control
strategies strategies
including including the
the PIOMB PIOMB and
and the the Control
Control Module needs
Module to be loaded
needs to be again.
loaded l The output to
again. the
l The output PROFIBUS
to the device will be
PROFIBUS set as defined
device are by the DSB
set to the for a
unpowered communicati
state. on loss
between the
C300
/UOC/HCA
and the PGM.

Checkpoint During When When

Restore of Checkpoint Save C300 C300/UOC/HCA
C300 /UOC/HCA and PGM are not
l PIOMB was

333
 Chapter 10 - PROFIBUS I/O Module (PIOMB) Function Block

Input type Output type

Scenario Prerequisites
PIOMB PIOMB
/UOC/HCA active. and PGM are communicating
Containing communicatin The control
l CEE was in
PROFIBUS the Run state g strategies
I/O including
Function
l
l The control
C300 PIOMBs, Control
strategies
Blocks /UOC/HCA Modules and all
including
and PGM were PIOMBs, Operational
communicatin Control Checkpoint Data
g Modules will be loaded as
After Checkpoint and all part of the
Save Operational Checkpoint
Checkpoint Restore.
l PIOMB is Data will be
inactive. loaded as l The output to
l CEE was in part of the the
the Idle state Checkpoint PROFIBUS
Restore. device will be
l The output set as defined
to the by the DSB
PROFIBUS for a
device are communicati
set to the on loss
unpowered between the
state. C300
/UOC/HCA
and the PGM.

Deleting a You cannot

CEE delete a CEE
containing containing the
the PIOMB PIOMB until all
contained blocks
including the
PIOMB and all
Control Modules
containing
PROFIBUS I/O
channels are
deleted. When all
the contained

334
Chapter 10 - PROFIBUS I/O Module (PIOMB) Function Block

Input type Output type

Scenario Prerequisites
PIOMB PIOMB
blocks are
deleted, and the
communication
between the
PGM and
PROFIBUS
devices stops.

Loss of communication scenarios

The following table summarizes the various communication
loss scenarios and the effect of the communication loss on the
input and output type PIOMBs.

Effect of
Cause of
Scenario communication loss
loss/prerequisites

Loss of Loss of Input type PIOMB

communication communication
between between the PIOMB receives
l

communication
C300/UOC/HCA C300/UOC/HCA
failure status.
and PGM and the PGM can
l Channel data is
occur if both FTE
set to fail-safe
cables are values.
disconnected. In l Strategies react
such a case, a to the fail-safe
notification that the values.
PGM went OFFNET Output type PIOMB
is reported. The PDA
sets the appropriate l PIOMB receives
status of the data communication
failure status.
passed to the
PIOMBs.
l Channel blocks
request upstream
blocks to go into
initialization.
l Device output
values is set to
configured fail-
safe values by
the DSB.

335
 Chapter 10 - PROFIBUS I/O Module (PIOMB) Function Block

Effect of
Cause of
Scenario communication loss
loss/prerequisites

Loss of Loss of Input type PIOMB

communication communication
l PIOMB receives
between PGM between the PGM
communication
and the device and the device can failure status.
occur under the l Channel data is
following scenarios. set to fail-safe
l Cable on the values.
l Strategies react
PROFIBUS
network breaks. to the fail-safe
l Device fails. values.
Output type PIOMB
l Device power is
disconnected. l PIOMB receives
communication
failure status.
l Channel blocks

request upstream
blocks to go into
initialization.
l Device output

values are set to

configured fail-
safe values by
the DSB.
A Device OFFNET
notification is also
reported.

Loss of PGM When a PGM loses If the devices do not

power power such that the go into a safe state,
secondary cannot the following
take over, the changes occur.
devices must put Input type PIOMB
themselves in a safe
l PIOMB receives
state, if such an
communication
operation is failure status.
supported by the l Channel data is
device. set to fail-safe
values.

336
Chapter 10 - PROFIBUS I/O Module (PIOMB) Function Block

Effect of
Cause of
Scenario communication loss
loss/prerequisites

l Strategies react
to the fail-safe
values.
Output type PIOMB
l PIOMB receives
communication
failure status.
l Channel blocks
request upstream
blocks to go into
initialization.
l Device output
values will be set
to configured
fail-safe values
by the DSB.

C300 Switchover l PIOMB and CM1 PIOMB

(with connection are active.
between the
l Output values
l CEE is in the Run are held.
C300/UOC/HCA state.
and the PGM re-
l Input values and
l C300/UOC/HCA control loops
established and PGM are maintain their
within the communicating. current values.
specified period l Switchover does
of time) not cause
strategies to set
to fail-safe
values.

C300 /UOC/HCA l PIOMB and CM1 The DSB sets the

Switchover (with are active. devices into their
connection l CEE is in the Run fail-safe states.
between the state. Input type PIOMB
C300/UOC/HCA l C300/UOC/HCA l PIOMB receives
and the PGM not and PGM are communication
re-established communicating. failure status.
within specified l Channel data is
period of time) set to fail-safe

337
 Chapter 10 - PROFIBUS I/O Module (PIOMB) Function Block

Effect of
Cause of
Scenario communication loss
loss/prerequisites

values.
l Strategies react
to the fail-safe
values.
Output type PIOMB
l PIOMB receives
communication
failure status.
l Channel blocks
request upstream
blocks to go into
initialization.
l Device output
values will be set
to configured
fail-safe values
by the DSB.

PGM Switchover l PIOMB and CM1 Input/output type

are active. PIOMB
l CEE is in the Run l Output values
state. are held.
l C300/UOC/HCA l Input values and
and PGM are control loops
communicating. maintain their
current values.
l Switchover does

not cause
strategies to set
to fail-safe
values.
However, if the
PGM does not
reestablish the
connection with the
C300/UOC/HCA,
the devices put
themselves in a

338
Chapter 10 - PROFIBUS I/O Module (PIOMB) Function Block

Effect of
Cause of
Scenario communication loss
loss/prerequisites

safe-state, if such
an option is
supported by the
device.

Loss of When a
C300/UOC/HCA C300/UOC/HCA
power or Ram loses power, the DSB
Retention Restart must put the devices
in the configured
safe-state. When the
C300/UOC/HCA
recovers, if a battery
is not present or if
the C300/UOC/HCA
module failed and
was replaced, the
configuration
(C300/UOC/HCA,
PIOMB, and CM)
must be reloaded. If
a battery is present,
the connection to
the PGM is restored.
Depending on the
CEE Restart option
of the CM, the CM
may need to be
activated after
recovery.

Loss of UOC When a UOC loses

power or Ram power, the DSB must
Retention Restart put the devices in
the configured safe-
state. When the UOC
recovers, if a
retention data is not

339
 Chapter 10 - PROFIBUS I/O Module (PIOMB) Function Block

Effect of
Cause of
Scenario communication loss
loss/prerequisites

present or if the uoc

module failed and
was replaced, the
configuration (UOC,
PIOMB, and CM)
must be reloaded. If
a retention data is
present, the
connection to the
PGM is restored.
Depending on the
CEE Restart option
of the CM, the CM
may need to be
activated after
recovery.

Configuring a PIOMB
Prerequisites
n The field network configuration in the PBLink block must be
complete.
n The DSBs must be configured.
n The PIOMB must be assigned to the C300/UOC/HCA
CEE/CM.

Perform the following steps to configure a PIOMB

1. Drag-and-drop the PIOMB from the PGM_IF library to the
CEE of the C300/UOC/HCA Controller. You can also click
File > New > I/O Modules > PGM_IF > PIOMB and create a
new PIOMB. When you create a PIOMB, it resides in the
Unassigned folder in the Project tree. You must drag-and-
drop it to the CEE of the C300/UOC/HCA Controller.
2. The Name New Function Blocks dialog box appears.

340
Chapter 10 - PROFIBUS I/O Module (PIOMB) Function Block

3. In the Destination column, you can accept the default name

or change the name if required and click Finish. The PIOMB
block appears under the I/O of C300/UOC/HCA CEE/CM.
4. Double-click the PIOMB. The PIOMB block configuration
form appears.
5. In the Tag Name field, type the name of the PIOMB (a
maximum of 40 characters) or accept the default.
6. In the Item Name field, type the item name.
7. In the Description field, type a brief description of up to 132
characters.

8. Click the point picker button next to the PDC Name

Reference box. The Point Selection dialog box appears. You
can view the following information from the Point Selection
dialog box.
l Points - Displays the tag name of the DSB block assigned

to a PBLink of a PGM.
l Types - Displays the DSB template name. For example,

GENDSBDP.
l Controller Name - Displays the PGM tag name to which the

DSB is assigned.
l Link/EE Name - Displays the PBLink tag name to which

the DSB is assigned.

ATTENTION: The Point Selection dialog box also

displays the PDC description that you have provided
while configuring the PDC tab.

9. Select the PDC to be associated to the PIOMB. You can

associate a PDC to a unique PIOMB. To associate another
PDC, you must drag-and-drop a new PIOMB from the PGM_
IF library or create a new PIOMB.
10. Click OK. The PDC that is associated to the PIOMB appears
in the PDC Name Reference box. Also, the PGM Name area
displays the PGM name to which the DSB is associated.
11. In the PDC Subscription Rate list, select the rate at which the
PGM must publish the process data to the PIOMB. By
default, the PDC data subscription rate is set to 50 ms.
However, for some configurations it is not necessary to

341
 Chapter 10 - PROFIBUS I/O Module (PIOMB) Function Block

receive process data every 50 ms. In such scenarios, you can

reduce the PDC data subscription rate as required to avoid
receiving fresh process data at a rate faster than what the
configured strategies consume.
12. Click the Module Configuration tab. The Module Configuration
tab displays the associated PDC related information such as
PDC description, PDC number, number of channels
associated with the PDC, and the connection status.
13. Click the Channel Configuration tab. You cannot configure
any parameters from the Channel Configuration tab. You can
only monitor the channel-specific configuration data such
as channel description, channel type, channel data type,
channel high range, and channel low range.
14. Click the Runtime Data tab. You cannot configure any
parameters from the Runtime Data tab. You can only monitor
the live process data of all the channels of an I/O module
from the Runtime Data tab in the Monitoring view.
15. Use the online help as a guide to complete the configuration
entries on other tabs.
16. Click OK.With R410, youYou can modify the values of the
following parameters even after a PDC is associated and
connected to a PIOMB. However, you must ensure that you
reload both the DSB and the PIOMB after modifying the
parameter value. If you do not reload both the DSB and the
PIOMB, there may be a break in the connection between the
DSB and the PIOMB.

Assigning a PROFIBUS Channel to PIOMB

After you assign a PDC to a PIOMB, you must assign a
PROFIBUS channel to the Control Module contained in the
C300/UOC/HCA CEE/CM. You must perform this to view the
data of the input or the output channel.
The following are the types of PROFIBUS I/O channel blocks
that are available and you must select the appropriate channel
block based on the channel type.
n PbAiChannel - If the channel type is analog input channel.
n PbDiChannel - If the channel type is digital input channel.

342
Chapter 10 - PROFIBUS I/O Module (PIOMB) Function Block

n PbAoChannel - If the channel type is analog output channel.

n PbDoChannel - If the channel type is digital output channel.

For example, if the channel type of a PDC is Digital input (DI),

you must drag-and-drop the PBDICHANNEL from the PGM_IF
library into the Control Module containing the CEE.

Perform the following steps to assign a PROFIBUS

channel to a PIOMB
1. Drag-and-drop the appropriate PROFIBUS I/O channel
block from the PGM_IF library to the Control Module
containing the C300/UOC/HCA Controller.
2. Double-click the PROFIBUS I/O channel block. The
PROFIBUS I/O channel block configuration form appears.
3. In the Module Name list, select the PIOMB associated with
this channel block.
4. In the Module Type list, select the module type of this
channel. The number of channels that can be assigned to
this block and the channel names appear under the Module
Type field.

343
 Chapter 10 - PROFIBUS I/O Module (PIOMB) Function Block

5. Select the appropriate channel number to which you must

assign the channel block.

6. Click Assign Channel Block. The Assign Channel Block is

unavailable until you select an available and compatible
channel number.
7. If you want to unassign the channel block, click Unassign
Channel Block You cannot unassign a PROFIBUS I/O
channel from the Project view if the CM is active. You must
delete the specific PROFIBUS I/O channel from the
Monitoring view.
8. Click OK. The Currently Assigned Channels area in the PIOMB
block Main tab configuration form displays the channels
associated to this PIOMB.

344
Chapter 10 - PROFIBUS I/O Module (PIOMB) Function Block

TIP: You must repeat this procedure to view the

channel information of all channels.

Monitoring PIOMB block

TIP:
In this section, the state and command parameters of the
PIOMB block are listed for quick reference. For detailed
information about these parameters, you need to refer to
the PROFIBUS Gateway Module Parameter Reference
guide.

PIOMB block state after configuration and load

Main tab
The PIOMB block can be loaded only if it is associated with a
PDC. When loaded, the PDC Name Reference (PDCNAMEREF)
will display the name of the PDC that is associated with this
PIOMB. The PGM Name (PGMNAME) will display the name of
the PGM to which the PDC is associated.

345
 Chapter 10 - PROFIBUS I/O Module (PIOMB) Function Block

Also, if the PROFIBUS I/O channel blocks are assigned to the

Control Module containing this PIOMB, the Currently Assigned
Channels (CHNLNAME) area will display the channels that are
associated to this PIOMB.

Module Configuration tab

When the PIOMB is loaded, the Connection Status
(PDCCONNSTATUS) will be "Connected" indicating that the
communication with the device is intact.
If the Execution State (EXECSTATE) parameter is made
"INACTIVE”, the PIOMB will hold the output values and stops
providing the input values to the control strategies.

Channel Configuration tab

When a PIOMB is associated with a PDC, the channel high
range and the channel low range values of each channel is
made available to the PIOMB. The Channel Configuration tab
will display the channel-specific configuration data such as the
channel description (CHANDESC), channel type
(CHANNELTYPE), channel data type (CHANNELDATATYPE),
channel high range (CHANHIRANGE), channel low range
(CHANLORANGE).
For analog input channels, the CHANHIRANGE and the
CHANLORANGE will display the high and low ranges of the
channels based on the DSB.
For digital channels, the CHANHIRANGE and the
CHANLORANGE will display the values "1" and "0" respectively.

Runtime Data tab

This tab will display the live process data of the channels. The
Digital Channel Data (CHANDATADIG) will display the live
digital channel data. The Analog Channel Data
(CHANDATAANA) will display the live analog channel data. The
Numeric Channel Data (CHANDATANUM) will display the live
numeric channel data. The Channel Status (CHANSTATUS) will
display the channel status of individual channels.

346
Chapter 10 - PROFIBUS I/O Module (PIOMB) Function Block

PIOMB block status parameters

Execution State (EXECSTATE)

The EXECSTATE parameter indicates the execution state of the
block and its components.

PDC Connection Status (PDCCONNSTATUS)

The PDCCONNSTATUS parameter indicates the status of the
connection between the PDC in the PGM/DSB and the PIOMB
in the C300/UOC/HCA.

CHANSTATUS
The CHANSTATUS parameter indicates the status of each
channel of the module.

PIOMB block icons

The following table summarizes the various appearances that a
PIOMB block icon can assume based on view and current
PIOMB state.

If Icon is... Then it indicates...

Project view

gray PIOMB is assigned to a CEE of

C300/UOC/HCA.

Monitoring view

blue PIOMB is inactive.

green PIOMB is active.

347
 Chapter 10 - PROFIBUS I/O Module (PIOMB) Function Block

If Icon is... Then it indicates...

red Data is not flowing from the

DSB to the PIOMB
successfully.

PIOMB notifications
When the PIOMB block is active, it generates the following
notification.

Notification Description

Communication This notification is generated when the PIOMB

Error loses connection with the associated PDC.

PIOMB block station displays

Detail displays and faceplate names
The following table lists the names of the details display and
faceplate of the PIOMB block.

Tab Name Detail Display Faceplate

Main tab sysdtlPIOMBa.htm sysdtlPIOMBa_fp.htm

Channels tab sysdtlPIOMBb.htm

Config Details tab sysdtlPIOMBc.htm

Calling up the displays

The following table lists the actions that you must perform to
call up the PIOMB block detail displays.

348
Chapter 10 - PROFIBUS I/O Module (PIOMB) Function Block

To call a
PIOMB Then …
block…

Main tab Type the PIOMB point name (for example PIOMB_
display 132) in the Station command zone and press F12. You
can also click the Search icon in the Station

toolbar and type the point name and click OK.

Channel Click the Channels tab.

tab
display

Config Click the Config Details tab.

Details
tab
display

Detail displays tabs

Main tab
The Main tab detail display provides information such as the
execution and control, I/O module information, display
information, and QVCS information.

349
 Chapter 10 - PROFIBUS I/O Module (PIOMB) Function Block

You can modify the following values from the Main tab detail
display.
n Execution State. Only a Supervisor can modify the Execution
State from the station.
n Alarm Enable State.

Channels tab
The Channels tab detail display provides actual channel values
of the PROFIBUS devices based on whether the channel is an
analog or a digital channel. For an analog channel, the detail
display appears as follows.

350
Chapter 10 - PROFIBUS I/O Module (PIOMB) Function Block

For a digital channel, the detail display appears as follows.

From the detail display, you can interpret the channel states on
the following LED colors.
n Black - The channel is "Off."
n Green - The channel is "On."
n Gray - The channel value is "Bad."

351
 Chapter 10 - PROFIBUS I/O Module (PIOMB) Function Block

ATTENTION: The number of channels that appear in the

Channel tab detail display are based on the number of
channels configured.

Config Details tab

The Config Details detail display is identical to the Main tab of
the PIOMB block (from Control Builder).

352
CHAPTER

11 PROFIBUS GATEWAY MODULE (PGM)

CONFIGURATION EXAMPLE

This section illustrates the configuration of the PGM blocks

(PGM, PB, DSB, PIOMB, PROFIBUS I/O channel blocks).
The GENDSB is used for illustrating the DSB configuration. The
ET 200M (IM153-1) device is used for illustrating the field
device configuration.

ATTENTION: Only the mandatory steps that must be

followed while configuring the PGM blocks are explained in
this section. The detailed configuration procedures are
explained in the PGM Configuration and Using Profibus
Network Configuration Tool for configuring field network
devices.

1. Choose File > New > Interface Modules > Profibus Gateway
Module (2 Links). The PGM block configuration form appears.
2. Type the name of the PGM (a maximum of 40 characters) or
accept the default. For illustration, the PGM name is
modified as PGM2_2229_EXMP.
3. Select the Module is redundant check box if you want the
module to be one of a redundant pair. If you check the box,
the secondary tag name appears in the Redundancy
Configuration box. The secondary PGM block is added when
the primary PGM block configuration form is closed.
4. Click OK. The PGM2_2229_EXMP block with two PBLink
blocks (PBLINK_2230 and PBLINK_2231) are added to the
Project tree.
5. Double-click the PBLink (PBLINK_2230). The PBLink
configuration form appears.
6. Type the name of the PBLink block (a maximum of 40
characters) or accept the default.
7. Click OK.
8. Click the Field Network Configuration tab.

353
Chapter 11 - PROFIBUS Gateway Module (PGM) Configuration Example

9. Drag-and-drop the ET 200M (IM153-1) device from the

Library view to the Network view.
10. Double-click the ET 200M (IM153-1) device in the Network
view. The configuration form of the ET 200M (IM153-1)
device appears. The Modules menu in the Navigation Area is
selected by default.
11. Choose the following modules to be associated with the ET
200M (IM153-1).
l 6ES7 321-7RD00-0AB0 4DI

l 6ES7 322-5RD00-0AB0 4D0

ATTENTION: The Config for Slot1, Config for Slot2,

and Config for Slot3 are specific to the Siemens ET
200M devices.

12. Click Insert. All the modules that you selected in the
Available Modules section appear in the Configured Modules
section.
13. Click Apply.
14. Click OK.

15. Click Save on the Field Network Configuration tab

toolbar. When you click Save , the configuration is

saved temporarily.
16. Double-click the master (PROFIBUS Gateway) in the
Network view. The configuration window appears. The Device
Assignment menu in the Navigation Area is selected by
default.
17. Click the Process Data menu in the Navigation Area. The
process data of the ET 200M(IM153-1) device appear in the
right pane.

18. Click to view the input and output modules that are
assigned to the ET 200M(IM153-1) device.
19. Select the Input_1 tag in the Tag column and modify it as
Input_1_Exm.

354
 Chapter 11 - PROFIBUS Gateway Module (PGM) Configuration Example

20. Select the Output_1 tag in the Tag column and modify it as
Output_1_Exm.
21. Click Apply.
22. Drag-and-drop the GENDSB from the DSB library to the
PBLINK_2230. The Load Dialog box appears.
23. Click OK.
24. Double-click the GENDSB.
25. Type the name of the DSB (a maximum of 40 characters) or
accept the default.
26. Click OK.
27. Click the PDC tab.
28. Select the Digital inputs ch 0-31 and Digital outputs ch 0-
31 from the PDC Type list.
29. Type the description for the Digital inputs ch 0-31 PDC as
"Digital input channel" in the PDC Description column.
30. Type the description for the Digital output ch 0-31 PDC as
"Digital output channel" in the PDC Description column.
31. Select the tag Input_1_Exm for the input PDC and Output_
1_Exm for the output PDC type in the Net Tag Name column
respectively. When you select the Digital inputs ch 0-31 or
the Digital output ch 0-31 row, the lower grid will display 4
rows (one row for each column) with all the channel
information.
32. Enter 4 in the Number of Channels column for both the input
and output types.
33. Click OK.
34. Drag-and-drop the PIOMB block from the PGM_IF library to
the CEE of the C300/UOC/HCA Controller.
35. Double-click the PIOMB (PIOMB_2239).

36. Click the point picker button next to the PDC Name
Reference box. The Point Selection dialog box appears.
37. Choose the PDC with the PDC description as "Digital input
channel" to be associated to the PIOMB.
38. Repeat step 34 through step 37 to associate a PDC with the
PDC description "Digital output channel" to another PIOMB.

355
Chapter 11 - PROFIBUS Gateway Module (PGM) Configuration Example

39. Click OK. The PDC Name Reference field will display the PDC
name that is associated to the PIOMB in the Main tab of the
PIOMB block.
40. Drag-and-drop the PBDICHANNEL from the PGM_IF library
in to the Control Module contained in the C300/UOC/HCA
Controller.
41. Double-click the PBDICHANNEL.
42. Select the PIOMB (PIOMB_2239) from the Module Name list.
43. Select Profibus I/O Module Block from the Module Type list.
The channel numbers and the channel name appear under
the Module Type field. The number of channels that will
appear is 4 (0, 1, 2, 3) as it is defined in the PDC tab of the
GENDSB.
44. Select channel number "1" to be assigned to the CM.
45. Click Assign Channel Block. The channel that is associated to
the CM will appear in the Currently Assigned Channels area in
the Main tab of the PIOMB block.
46. Repeat steps 40 through 45 to assign another PROFIBUS
channel to the CM.
47. Click OK.

356
CHAPTER

12 LOADING PROFIBUS GATEWAY MODULE

(PGM)

In this section:

Initial load order guidelines 358

Loading a PGM 361
Reloading the PGM function blocks 362

357
Chapter 12 - Loading PROFIBUS Gateway Module (PGM)

The ExperionLXPlantCruiseExperion PKS system provides the

ability to build control strategies offline, without being
connected to the actual field components. The process of
transferring the Control Strategy to the "live" working
components in the field is called the load operation.
The load operation functionally copies configuration data from
the control strategy that is stored in the Engineering Repository
Database (ERDB) to the assigned field component in the
system architecture. It indirectly assures that the planned
system matches the actual one. The communication addresses
and physical location assignments specified for components
through Control Builder configuration must match the actual
addresses and locations of components in the system.

Initial load order guidelines

Perform the initial load of control strategy components from
the Project view in the following order to minimize possible
load interaction generated error messages.

Order Component

1 PGM block (includes PBLink1 and

PBLink2)

2 DSB block

3 PIOMB block PBHIOMB block

4 Control Module containing the

PROFIBUS I/O function block Control
Module containing the PROFIBUS
HART I/O channel block

Refer to the Control

Building User's Guide for
more information about
loading components.

Loading PGM function blocks

This sections provides information on loading the PGM block
and its associated function blocks.

358
 Chapter 12 - Loading PROFIBUS Gateway Module (PGM)

Loading the PGM block

To load a PGM block, the PGM platform must be physically
present at the configured address. However, if the PGM
platform is not physically present, appropriate errors are
returned.
When you load the PGM function block for the first time, the
load transfers the PGM platform configuration data from the
ERDB to the PGM platform.
After the load is complete, the PGM platform block
automatically transitions to OK state.

Loading the PGM block with contents

To load a PGM block with contents (DSBs, PBLink blocks), the
PGM platform must be physically present at the configured
address. However, if the PGM platform is not physically present,
appropriate errors are returned.
After the load is complete, the PGM platform block
automatically transitions to RUN state.

Loading the Protocol Block

To load a Protocol Block, the PGM platform block must be
previously loaded. However, if the PGM platform is not present,
the Protocol Block load fails and will be canceled.
When you load the PGM block, the Protocol Blocks are also
automatically loaded. However, you can also load the Protocol
Blocks individually.
The Protocol Block load operation loads the Protocol Block and
the associated field network configuration to the PGM.

ATTENTION: If you make changes to the field network

configuration such as bus-related changes, after the
Protocol Block is loaded, you must reload the Protocol
Block for the changes to be updated. During the reload, the
connection between the PROFIBUS devices and the master
is lost. Therefore loading the updated Protocol Block must
be planned carefully. Also, the behavior of the PROFIBUS

359
Chapter 12 - Loading PROFIBUS Gateway Module (PGM)

devices during this connection loss is based on their

configuration. For most of the PROFIBUS devices, you can
configure connection breakout time during which they keep
their outputs. However, some of the PROFIBUS devices lose
their outputs immediately in the event of a connection loss
with the master.

Loading the DSB block

To load a DSB block, the PGM platform block and the Protocol
Block to which the DSB is associated must be previously
loaded. However, the DSB load fails and will be canceled if any
of the following errors are encountered.
n The PGM platform is not present and loaded.
n The PROFIBUS device address is not configured in the
Profibus Network Configuration Tool. For example, you enter
the PROFIBUS device address as 25 in the Main tab
configuration form of the DSB block but you have not
defined any PROFIBUS device with address 25 in the
Profibus Network Configuration Tool. In such a scenario, you
cannot load the DSB block.

Loading the PIOMB block

To load a PIOMB block, you must associate the PIOMB with a
PDC of the DSB. You cannot load a PIOMB block that is not
associated with a PDC.

ATTENTION: You can load the PIOMB block even when the
CM is not active.

Loading the PBHIOMB block

To load a PBHIOMB block, you must associate the PBHIOMB to
the DSB. You cannot load a PBHIOMB block that is not
associated with a PDC.
The PBHIOMB can be loaded by right-clicking the module and
then click Load.

360
 Chapter 12 - Loading PROFIBUS Gateway Module (PGM)

ATTENTION: When a PBHIOMB is loaded, all

PBHCHANNELs under the module are loaded
automatically. A PBHCHANNEL must be loaded individually
only when the channel is created during the run time.

Loading a PGM
You can use the following general procedure to load a PGM.
The load procedure is similar for all PGM module components.
Note that selecting a PGM for loading also selects the
associated PB function blocks.

Perform the following steps to load a PGM function

block and its associated blocks
1. Click the PGM block you must load in the Project view.
2. Click Tools > Load.

You can also click in the tool bar.

l You can also right-click the PGM block and select Load.

The Load dialog box appears.

3. With the Load check box selected, click OK. This initiates the
PGM load operation and the load progress dialog box
appears. If errors are detected, they are displayed in the
Load progress dialog and you will be asked if you want to
continue the load or cancel, depending on the nature of the
error. We suggest that you cancel the load and identify and
fix the errors. Each message contains a brief description and
includes an error code in parentheses. Note the last number
in the string. In some cases, more information about the
code number may be included in the Control Builder
Notifications Reference document. .
4. After the load operation is complete and the Load dialog box
closes, click the Monitoring tab. The PGM icon appears in
the Monitoring view.

361
Chapter 12 - Loading PROFIBUS Gateway Module (PGM)

Reloading the PGM function blocks

This sections provides information on reloading the PGM block
and its associated function blocks.

Reloading the PGM function block

Reloading the PGM block is generally not frequently performed
since you can only change very few parameters on the PGM
platform block after the initial load is successful.
After the reload is successful, the PGM platform block remains
in its RUN state.

Reloading the Protocol Block

To reload a Protocol Block, the PGM platform block must be
previously loaded. The Protocol Block reload fails if the PGM
platform is not physically present and loaded. However, if the
reload fails, appropriates errors are returned but the load is not
canceled.
The reloading of the Protocol Block loads the Protocol Block
and its associated field network configuration to the PGM.

Reloading the DSB function block

To reload a DSB block, the PGM platform block and the
Protocol Block to which the DSB is associated must be
previously loaded. The DSB load fails and will be canceled if the
following errors are encountered.
n The PGM platform is not present and loaded.
n The PROFIBUS device address is not configured in the
Profibus Network Configuration Tool. For example, you enter
the PROFIBUS device address as 25 in the Main tab
configuration form of the DSB block but you have not
defined any PROFIBUS device with address 25 in the
Profibus Network Configuration Tool. In such a scenario, you
cannot load the DSB block.
However, if the reload fails, appropriate errors are returned but
the load will not be canceled.

362
 Chapter 12 - Loading PROFIBUS Gateway Module (PGM)

ATTENTION: Whenever you reconfigure net tags for a PDC,

you must reload the DSB before removing the same net tag
in Sycon and reloading the Protocol Block. This prevents
the DSB or the PDC from going into error state during run
time while modifying the net tag usage.

Reloading the PIOMB function block

The PIOMB function block must be reloaded when there is a
modification made in the DSB. If the PIOMB block is not
reloaded, then the changes in the DSB does not replicate in the
PIOMB.

ATTENTION: You can load the PIOMB block even when the
CM is not active.

Reloading the PBHIOMB function block

The PBHIOMB block needs to be reloaded when the changes
are made to Load While Active parameters in the
PBHCHANNEL. The Load While Active parameters of the
PBHCHANNEL are,
n HART variable-related parameters
n HART notification-related parameters
If you are not reloading the PBHIOMB block using the Load
While Active option, then you must load the individual
PBHCHANNEL for which the changes are made.

Reloading a CM containing PROFIBUS I/O channel

blocks
When you reload a CM containing the PROFIBUS I/O channel
blocks, the PIOMB holds the last output value received from
the channel block. Also, this value is held by the PROFIBUS
devices.

363
Chapter 12 - Loading PROFIBUS Gateway Module (PGM)

Reloading the PROFIBUS HART I/O channel blocks

The PBHCHANNEL can be reloaded whenever there is a
configuration change made to the PBHCHANNEL.

364
CHAPTER

13 PROFIBUS GATEWAY MODULE (PGM)

MAINTENANCE

In this section:

Periodic checks 366

Replacing a non-redundant PGM 366
Replacing a redundant or secondary PGM 367
Replacing a non-redundant PGM IOTA board 368
Replacing a redundant or secondary PGM IOTA board 370

365
Chapter 13 - PROFIBUS Gateway Module (PGM) Maintenance

Periodic checks
The following table identifies checks that you should perform
periodically (every 3 to 6 months) to keep the PGM in good
working condition.

Check... Possible Corrective Action...

That all segments of the 4- If segment or LED is not lit or has

character display and the dimmed, you must replace the PGM
light emitting diodes (LED) since front-panel indicators and
on PGM are working. LEDs are not field replaceable.

That all connections are Secure connections, as needed.

secure.

That cable insulation is not Replace cables, as required.

worn or cracked.

That IOTA is secure. Tighten mounting screws.

Replacing a non-redundant PGM

This procedure can be performed only while off-process.
We recommend that you proceed with extreme caution
whenever replacing any component in a control system. Be
sure the system is offline or in a safe operating mode.
Component replacements may also require corresponding
changes in the control strategy configuration through Control
Builder, as well as downloading appropriate data to the
replaced component.

Perform the following steps to replace a non-

redundant PGM
1. Loosen screws at each side of the module cover that
secures the PGM to the IOTA board.
2. Loosen the plastic screw on the front of the PGM cover. Be
careful not to strip the plastic screw head.
3. Carefully remove the PGM from the IOTA board and
connector.

366
 Chapter 13 - PROFIBUS Gateway Module (PGM) Maintenance

4. Insert the new PGM onto IOTA board making sure that the
PGM circuit board mates properly with the IOTA board
connector.
5. Secure the PGM to the IOTA board with two screws located
at each side of the plastic cover.
6. Using a #2 Phillips screwdriver, hand tighten the plastic
screw on the front of the module cover. Be careful not to
strip the plastic screw head.
The new PGM boots up to ALIVE or NODB state.
7. Load firmware which is the same version as was running in
the old PGM.
8. From Control Builder, perform a 'Load with Contents' to the
PGM.

Replacing a redundant or secondary PGM

This procedure can be performed while on-process only if the
module to be replaced is in the secondary role.
We recommend that you proceed with extreme caution
whenever replacing any component in a control system. Be
sure the system is offline or in a safe operating mode.
Component replacements may also require corresponding
changes in the control strategy configuration through Control
Builder, as well as downloading appropriate data to the
replaced component.

Perform the following steps to replace a redundant or

secondary PGM
1. In Control Builder, double-click the primary PGM and
navigate to the Redundancy tab.
2. Click Disable Synchronization to set the Auto Synchronization
State parameter to "Disabled."
3. Loosen screws at each side of the module cover that
secures the PGM to the IOTA board.
4. Loosen the plastic screw on the front of the PGM cover. Be
careful not to strip the plastic screw head.
5. Carefully remove the PGM from the IOTA board and
connector.

367
Chapter 13 - PROFIBUS Gateway Module (PGM) Maintenance

6. Insert the new PGM onto IOTA board making sure that the
PGM circuit board mates properly with the IOTA board
connector.
7. Secure the PGM to the IOTA board with two screws located
at each side of the plastic cover.
8. Using a #2 Phillips screwdriver, tighten the plastic screw on
the front of the module cover. Be careful not to strip the
plastic screw head.
9. Load the same version of the firmware which was running in
the old PGM. The new PGM boots up to ALIVE or BKUP. If
the application image does not match the primary PGM, it is
not be synchronized.
10. Click the Redundancy tab from either the primary or
secondary PGM.
11. Click Enable Synchronization to initiate synchronization and
allow auto-synchronization.

Replacing a non-redundant PGM IOTA board

This procedure can be performed only while off-process.
We recommend that you proceed with extreme caution
whenever replacing any component in a control system. Be
sure the system is offline or in a safe operating mode.
Component replacements may also require corresponding
changes in the control strategy configuration through Control
Builder, as well as downloading appropriate data to the
replaced component.

Perform the following steps to replace a non-

redundant PGM IOTA board
1. On the defective IOTA, loosen screws at each side of the
module cover that secures the PGM to the IOTA board.
2. Loosen the plastic screw on the front of the module cover.
Be careful not to strip the plastic screw head.
3. Carefully remove the PGM from the IOTA board and
connector.
4. Label and disconnect all cables from the IOTA board
connectors, (yellow and green FTE cables, and PBLink
cables). Do not fully tighten the IOTA mounting screws

368
 Chapter 13 - PROFIBUS Gateway Module (PGM) Maintenance

before installing and tightening the power and ground

screws (24V and COM terminals) which can bind during
installation or removal. Follow instructions carefully.
5. Loosen the four mounting screws only half way that secure
the IOTA board to the channel.
6. Remove the screw from the left side of the IOTA board that
connects to the 24 Vdc bus bar.
7. Remove the screw from the right side of the IOTA board that
connects to the COM bus bar.
8. Remove completely the four mounting screws securing the
IOTA board to the channel and remove the IOTA.
9. Place screws, washers and spacers aside for reassembly.
10. Assemble screws, washers and spacers on the new IOTA
board.
11. Mount the new PGM IOTA board on the channel at the same
position as the old IOTA board.
12. Insert and thread the four mounting screws only half way to
attach the IOTA board to the channel.
13. Insert and tighten the screw to the left side of the IOTA
board that connects to the 24 Vdc bus bar.
14. Insert and tighten the screw to the right side of the IOTA
board that connects to the COM bus bar.
15. Tighten the four mounting screws securing the IOTA board
to the channel.
16. Set the Device Index address to the same address as the old
IOTA using the three rotary FTE DEVICE INDEX switches.
17. Connect FTE-A and FTE-B Ethernet link cables to the RJ-45
connectors on PGM IOTA board.
l The yellow Cat5 cable must connect to the FTEA
connector on the IOTA.
l The green Cat5 cable connects to the FTEB connector on

the IOTA.
18. Connect the PBLink cables to the IOTA board.
19. Insert the PGM onto IOTA board making sure that the PGM
circuit board mates properly with the IOTA board connector.
20. Secure the PGM to the IOTA board with two screws located
at each side of the plastic cover.

369
Chapter 13 - PROFIBUS Gateway Module (PGM) Maintenance

21. Using a #2 Phillips screwdriver, tighten the plastic screw on

the front of the module cover. Be careful not to strip the
plastic screw head.
22. The PGM boots up into an ALIVE state or a NODB operating
state.
23. Perform a Load with Contents to the PGM.

Replacing a redundant or secondary PGM IOTA

board
Perform the following steps to replace a redundant or
secondary PGM IOTA board
1. Select the Redundancy tab either from the primary or
secondary PGM FB.
2. Click Disable Synchronization to set the Auto-Synchronization
State parameter to "DISABLED."
3. On the defective IOTA, loosen screws at each side of the
module cover that secures the PGM to the IOTA board.
4. Loosen the plastic screw on the front of the module cover.
Be careful not to strip the plastic screw head.
5. Carefully remove the PGM from the IOTA board and
connector.
6. Label and disconnect all cables from the IOTA board
connectors, (yellow and green FTE cables, and PBLink
cables). Do not fully tighten the IOTA mounting screws
before installing and tightening the power and ground
screws (24V and COM terminals) which can bind during
installation or removal. Follow instructions carefully.
7. Loosen the four mounting screws only half-way that secure
the IOTA board to the channel.
8. Remove the screw from the left side of the IOTA board that
connects to the 24 Vdc bus bar.
9. Remove the screw from the right side of the IOTA board that
connects to the COM bus bar.
10. Remove completely the four mounting screws securing the
IOTA board to the channel and remove the IOTA.
11. Place screws, washers and spacers aside for reassembly.

370
 Chapter 13 - PROFIBUS Gateway Module (PGM) Maintenance

12. Assemble screws, washers and spacers on the new IOTA

board.
13. Mount the new PGM IOTA board on the channel at the same
position as the old IOTA board.
14. Insert and thread the four mounting screws only half-way to
attach the IOTA board to the channel.
15. Insert and tighten the screw to the left side of the IOTA
board that connects to the 24 Vdc bus bar.
16. Insert and tighten the screw to the right side of the IOTA
board that connects to the COM bus bar.
17. Tighten the four mounting screws securing the IOTA board
to the channel.
18. Set the Device Index address to the same address as the old
IOTA using the three rotary FTE DEVICE INDEX switches.
19. Connect FTE-A and FTE-B Ethernet link cables to the RJ-45
connectors on PGM IOTA board.
l The yellow Cat5 cable must connect to the FTEA
connector on the IOTA.
l The green Cat5 cable connects to the FTEB connector on

the IOTA.
20. Connect the PBLINK cables to IOTA board.
21. Insert the PGM onto IOTA board making sure that the PGM
circuit board mates properly with the IOTA board connector.
22. Secure the PGM to the IOTA board with two screws located
at each side of the plastic cover.
23. Using a #2 Phillips screwdriver, tighten the plastic screw on
the front of the module cover. Be careful not to strip the
plastic screw head.
The PGM boots up into an unsynchronized secondary
redundancy state with BKUP operating state.
24. Click the Redundancy tab from either the primary or
secondary PGM FB.
25. Click Enable Synchronization to initiate synchronization and
allow auto-synchronization.

371
CHAPTER

14 PROFIBUS GATEWAY MODULE (PGM)

TROUBLESHOOTING

In this section:

Behavior of PGM during fault scenarios 373

Fault Classifications 377
Initial checks 379
Fixing common problems 381
Getting further assistance 391

372
Chapter 14 - PROFIBUS Gateway Module (PGM) Troubleshooting

This chapter provides guidance and background information

about the causes and remedies for failures which may occur in
the PGM.

Behavior of PGM during fault scenarios

This section provides information on the behavior of the PGM
under various scenarios such as power off, communication loss
with the devices, communication loss with the C300/UOC/HCA
Controller and so on.

Loss of communication between PGM and

C300/UOC/HCA
This communication loss can occur when both the FTE cables
are removed from the non-redundant PGM.

ATTENTION: Even if one of the FTE cables are removed or

is faulty, the PGM can still communicate with the devices
on network.

The following table illustrates the behavior of the DSB and the
PIOMB blocks when there is a communication loss between the
PGM and the C300/UOC/HCA Controller.

DSB PIOMB

Input side behavior Input channels

l The DSB is l Input Channels will be set to fail-safe
informed of the values (NaN and OFF for analog and
communication digital values respectively).
loss. l Channel value status is set to "Bad."
l The connections l The associated function blocks react to
are removed. the fail-safe data.
l The PGM stops
data updates to
the associated
PDCs.

Output side Output channels Output Channel will

behavior request the upstream blocks to go into
initialization (INITMAN parameter should be
l The fail-safe

373
 Chapter 14 - PROFIBUS Gateway Module (PGM) Troubleshooting

DSB PIOMB

value of the set to "ON" for the PID and DEVCTL blocks).
device is set on
the DSB block.

Loss of communication between PGM and PROFIBUS

device
This communication loss between the PGM and the PROFIBUS
devices can occur in the following scenarios.
n The PROFIBUS cable is removed from the PGM.
n The PROFIBUS devices are not configured properly.
n The PROFIBUS devices are broken.
The following table illustrates the behavior of the DSB and
PIOMB blocks in the event of a communication loss between
the PGM and the PROFIBUS device.

DSB PIOMB

Input side behavior Input type PIOMB

l The DSB is informed l The PIOMB receives the
of the "Communication Fail" status and the
communication loss. channel will follow that status.
l The status of the l Input Channels will be set to fail-safe
PDCs are set to values (NaN and OFF for analog and
"Device digital values respectively).
communication l Channel value status is set to "Bad."
error."
l The data is set to fail-
safe values.
l The PDC channel
status is set to "Bad_
ConnError."

Output side behavior Output type PIOMB

l The fail-safe value of l The PIOMB receives the
the device is set on "Communication Fail" status and the
the DSB block. output channel blocks follow that

374
Chapter 14 - PROFIBUS Gateway Module (PGM) Troubleshooting

DSB PIOMB

status.
l Channel value status is set to "Bad."

Loss of communication between the PGM and control

strategies
The control strategies can lose communication with the PGM
due to any of the following conditions.
n Removal of the PGM module.
n Removal of the FTE cable from the PGM.
n Removal and re-insertion of the PROFIBUS devices.
In any of the above scenarios, the control strategies using the
PROFIBUS data go into fail-safe data.

CEEC300/UOC/HCA state is changed to Idle

When the CEESTATE parameter of the C300/UOC/HCA is
changed to "Idle," the PGM operates as follows:
n The PGM continues to operate as it was prior to this change
and publishes the new data to the C300/UOC/HCA
Controller.
n The PIOMB continues to execute since IOMs continue to
execute even when CEE is "Idle."
n The input channels are set to fail-safe values (NaN and Off
for analog and digital values respectively). The input
channel status is set to "Bad."
n The output channel status is set to "Bad."
n The output of PROFIBUS devices hold the last good value
when the CEE is "Idle."

Inactivation of PIOMB
When a PIOMB associated with a PDC is inactivated, the PGM
operates as follows:
n Input side behavior - The PGM continues to operate as it was
prior to the inactivation and publishes data to the
C300/UOC/HCA controller.

375
 Chapter 14 - PROFIBUS Gateway Module (PGM) Troubleshooting

n Output side behavior - The output of the PROFIBUS devices

hold the last value until they receive a new value.

Deletion of PIOMB
When a PIOMB associated with a PDC is deleted, the PGM
operates as follows:
n Input side behavior - The PGM continues to operate as it was
prior to the deletion and publishes data to the
C300/UOC/HCA. However, the PGM stops publishing the
data after the PIOMB closes the connection to its associated
PDC.
n Output side behavior - The PGM stops receiving output
publications from the PIOMB after it closes the connection
to its associated PDC. The output of the analog devices and
digital devices are initialized to 0 and 0% respectively.

PGM power failure

In the event of a PGM power failure, the PGM loses its
connection with C300/UOC/HCA and PIOMB. However, it
retains the field network configuration and the DSB
configuration. When the PGM is powered on, the network-
related configuration such as the PROFIBUS device
configuration, Baud Rate, Device Data Memory Offset address
is retained because of RAM retention.
The input channels are set to fail-safe values (NaN and Off for
analog and digital values respectively). The channel status is
set to "Bad."
The function blocks react to the fail-safe data.
The output channels request the upstream block to go into
initialization. The upstream Regulatory Control block should
realize that it is connected to an output channel and there is a
loss of communication with the I/O.
The Regulatory Control block should shed the mode to the
user-selected mode.

376
Chapter 14 - PROFIBUS Gateway Module (PGM) Troubleshooting

Removal of PGM from IOTA

When a PGM is removed from the IOTA under powered
condition and re-inserted, the PGM should power up
successfully and the module state must be "RUN." Also the
control strategies must work normally.

Mismatch of the PROFIBUS device and the master

addresses
The following list illustrates the behavior of the PGM during
mismatch of PROFIBUS device and the master address.
n PROFIBUS devices with identical station address - When two
PROFIBUS devices with identical station address are
connected to the network, the PROFIBUS device that is
locked by the master first for communications continues to
operate. However, the other PROFIBUS device will not be in
use.
n Two masters with identical station address - When two masters
with identical station address are connected to the network,
the read/write operations are stopped.

ExperionLXPlantCruiseExperion PKS server switchover

In the event of an ExperionLXPlantCruiseExperion PKS server
switchover, if the PGM is using a Flex station, the server
switchover results in a momentary loss of view. However, if the
PGM is using ConsoleDirect station, the server switchover does
not result in loss of view or loss of control. In both scenarios,
the DSB continues to update the PIOMB.

Fault Classifications
Faults have been classified into a number of categories
according to the severity of the failure. The PGM behavior when
a failure is detected is determined by type of fault and whether
the PGM is non-redundant, or is one of a redundant controller
pair.
The following table identifies these fault classifications and
describes PGM behavior in response to the fault type.

377
 Chapter 14 - PROFIBUS Gateway Module (PGM) Troubleshooting

Fault Classification Characteristics

Hard Failure Failure detected by hardware; operation

cannot continue. If the fault does not
prevent software processing the problem,
the affected node will be rebooted under
software control into the FAIL State.
l If failure occurs on a primary module, it
triggers a switchover to the
synchronized secondary module.
l If failure occurs on a secondary module,
it results in loss of synchronization and
reduced availability until the problem is
resolved.
l If failure occurs on a non-redundant
module, it results in loss of control and
loss of view.

Severe Failure Failure detected by software; operation

cannot continue. The affected node will be
rebooted under software control into the
FAIL State.
l Severe failure on a synchronized
primary module triggers a switchover to
the secondary module.
l Severe failure on a secondary module
causes a loss-of-synchronization (and
reduced availability until fault is
corrected).
l Severe failure on a non-redundant
module causes a loss-of-control and
loss-of-view.

Soft Failure Failure detected by software; operation

continues with full control and full view.
Soft failures are alarmed to the operator.
FTE will be monitored by the FTE System
Management Tool.
l If failure occurs on a primary module, it
does not trigger a switchover to the
synchronized secondary module.

378
Chapter 14 - PROFIBUS Gateway Module (PGM) Troubleshooting

Fault Classification Characteristics

l If failure occurs on a secondary module,

it does not result in loss of
synchronization.
l If failure occurs on a non-redundant
module, it does not result in loss of
control and loss of view.

Installation/Startup Detected by software. Module may not

Failure become operational.
l This failure does not apply to the
synchronized primary module, since
installation and startup must be
successful to reach synchronized
primary state.
l If failure occurs on a secondary module,
it results in the inability to complete the
initial synchronization and to view the
node on the network.
l If failure occurs on a non-redundant
module, it results in an inability to
commence control and to view the
module on the network.

Communication Communication errors between peer

Failure modules and/or I/O devices, including
Fault Tolerant Ethernet Bridge (FTEB), do
not cause any module state change.

Initial checks
This section offers some checks that you can make to help
isolate the problem. The checks are arranged in no particular
order.

Checking Control Builder error code reference

An indication of a problem may be in the form of an error dialog
that includes an error message and possibly an error code in
Control Builder.

379
 Chapter 14 - PROFIBUS Gateway Module (PGM) Troubleshooting

The syntax for a typical Control Builder error message is as

follows: Connection to device is not open EPKS_E_CL_
NOCONN(6L.101.3326)
In this syntax, the error code is the last four digits in the
message or 3326.
Please refer to the Control Builder Error Codes Reference book
for applicable error code information.

Viewing flash log

The Flash.txt log provides a list of firmware updates that have
been initiated.
To view the log, navigate to this file location on the server:
C:\Program Files\Honeywell\Experion\Engineering
Tools\system\bin\Flash.txt.

Viewing release information log

The ReleaseInfo.txt log provides a list of
ExperionLXPlantCruiseExperion PKS software releases that
have been installed on the computer.
To view the log, navigate to this file location on the server:
C:\Program Files\Honeywell\Experion\Engineering
Tools\system\bin\ReleaseInfo.txt.

Checking server point build log

The SvrPtBld_servername.txt log provides list of process (CB)
points built in the server database.
To check the log, navigate to this file location on the server:
C:\Program Files\Honeywell\Experion PKS\Engineering
Tools\temp\SvrPtBld_servername.txt.

Checking server point build error log

The svrptblderr_servername.txt log provides list of any errors
associated with process (CB) points built in the server
database.
To check the log, navigate to this file location on the server:
C:\Program Files\Honeywell\Experion PKS\Engineering
Tools\temp\svrptblderr_servername.txt.

380
Chapter 14 - PROFIBUS Gateway Module (PGM) Troubleshooting

Checking error log

The Errlog_n.txt log provides a running list of Control Builder
detected errors in chronological order. The "n" represents any
number that is assigned to the most recent log.
To check the log, navigate to this file location on the server:
C:\ProgramData\Honeywell\Experion PKS\ErrLog_n.txt.

Using CTool to capture diagnostic data

You can use the CTool utility to capture diagnostic data used to
examine the operating conditions within the controller. This
data also can be analyzed to determine the cause of an error or
fault. The following data can be captured using CTools:
n Trace Log
n Registers
n SSP
n Call Stack
n Instructions
See Series C8 Firmware Load Tool (CTool) for Series C8
Components in the Control Hardware Troubleshooting and
Maintenance Guide for the procedure to capture diagnostic
data.

Fixing common problems

This section identifies some common problems and describes
how you might fix them.

Loss of communication with the devices when a

switchover is initiated
Diagnostic Loss of communication with the
Check PROFIBUS devices when a switchover is
initiated.

Cause Probable PROFIBUS master

configuration (bus parameters) errors.
For example, Watchdog Control Time
and Data Control Time are not
configured properly.

381
 Chapter 14 - PROFIBUS Gateway Module (PGM) Troubleshooting

Solution Modify the Watchdog Control Time and

data control time based on the Baud
Rate. The following table lists the
various Baud Rate and the
recommended Watchdog Control Time
and the Data Control Time. These values
may differ based on the number of
PROFIBUS devices configured in the
network.

Baud Rate Watchdog Control Time Data

Control
Time

1500 1000 6000

500 1000 6000

187.5 2000 12000

93.75 3000 18000

45.45 4000 24000

19.2 5000 30000

9.6 6000 36000

Loss of connection to some of the field

network PROFIBUS devices
Diagnostic PROFIBUS devices that are not communicating with
Check the PGM have their status as "Bad."

Cause 1 Network or power supply wiring problems in the

field network.

Solution Open the Protocol Block detail displays to check the

PROFIBUS devices that are not communicating with
the PGM. Obtain the field network wiring diagram
and PROFIBUS device power supply schematics. Fix
the problematic network wiring or power supply
wiring manually. Otherwise, go to Cause 2.

382
Chapter 14 - PROFIBUS Gateway Module (PGM) Troubleshooting

Cause 2 PROFIBUS devices are not configured properly.

Solution Check for the PROFIBUS device configurations and

correct the configurations, if any. Otherwise, go to
Cause 3.

Cause 3 PROFIBUS devices are broken.

Solution Replace the broken PROFIBUS devices one by one.

Loss of power
The power supply has failed or the main power source has been
shutdown or is experiencing a brownout or blackout condition.

Diagnostic l The 4-character display on the PGM and LEDs

Check on the module and the IOTA are off.
l In the Monitoring view, the PGM icon turns red.

Cause 1 Main power source has been disconnected or

shutdown either manually or temporarily by
brownout or blackout condition.

Solution Re-connect the main power source or turn it On or

wait for temporary brownout or blackout condition
to pass.

Cause 2 The 24 Vdc power supply failed or power cable has

been disconnected or failed.

Solution Replace the 24 Vdc power supply or re-

connect/replace the power cable.

Cause 3 Power fuse (0.8A/250V Type F) opens on IOTA.

Solution Replace power fuse (0.8A/250V Type F).

Power-On Self Test (POST) does not complete

A fault is detected during the Power-On Self Test (POST).

Diagnostic A self test diagnostic code remains on display and

Check the POST does not continue. Possible indications:
Display indicates test pattern, or Tnnn (nnn = a test
number which is executed during POST). Note: If

383
 Chapter 14 - PROFIBUS Gateway Module (PGM) Troubleshooting

display indicates 'T499', POST has completed.

Cause The PGM POST has detected a failure that does not
allow startup to continue or complete.

Solution Short the reset pads on the IOTA to restart the PGM.
If error persists, replace the module.

PGM display indicates -bp- or -ts-

Diagnostic Display indicates -bp-

Check

Cause BootP service is not available.

Solution l Check FTE cable connections to FTE A and FTE B

connectors on the module IOTA.
l Verify FTE network connections between the
module IOTA and the associated server.
l Verify that the BootP service is running on the
associated server. Restart BootP service if not
running.
l In Control Builder, check System Preferences for
valid network IP address settings. Verify correct
configuration of System Time server.

Diagnostic Display indicates -SF- alternating with OK/BKUP

Check

Cause BootP service is available, but time source is not

available. Time Server may not be configured or
server may not be running the latest release time
service.

Solution Verify that the system time source is configured.

Check that the Server Windows Time Service
(w32time) is running on the server.

384
Chapter 14 - PROFIBUS Gateway Module (PGM) Troubleshooting

One or both FTE LEDs are RED

Diagnostic One or both FTE LEDs on the PGM faceplate are

Check RED.

Cause 1 No connection

Solution Check cable connections on module IOTA (FTEA

and FTEB connectors) and at CF9 IOTAs.

Cause 2 Cables bad

Solution Swap known good cable with suspect cable. Replace

bad cable.

Cause 3 Switch port bad

Solution Swap cables with known good port to identify

defective port. Replace assembly that contains
defective port.

Cause 4 IOTA bad

Solution Replace IOTA

FTE receive fault diagnostic

The PGM has detected an open receive signal line between
either of its two Ethernet interface devices and the processor
handling incoming communication.

Diagnostic l The Status LED on the front panel of the PGM

Check turns RED.
l The 'LAN_A' or 'LAN_B' indicator for the faulted
port turns RED. The indicators are found on the
FTE tab of the PGM block configuration form.
l An alarm is generated by the PGM that indicates
"FTE Port A Receive Fault" or "FTE Port B Receive
Fault."

Cause The following conditions may result in a spurious

(false) indication of an FTE Receive Diagnostic fault.
These conditions are external to the PGM that allow

385
 Chapter 14 - PROFIBUS Gateway Module (PGM) Troubleshooting

a carrier to be detected by the PGM's Port A or Port

B Ethernet interface but eliminate FTE traffic on
that port.
l Disconnecting the uplink cable of a CF9 when
only one PGM is connected to any of the
downlink ports on the CF9. In this case, the only
source of external FTE Diagnostic messages are
nodes that communicate through the uplink port
of the CF9. When the uplink cable is
disconnected, there are no incoming FTE
Diagnostic messages on the PGM. Since the
downlink cable from the CF9 to the PGM remains
attached, the PGM has a 'good' Link Status on
the port. The combination of a good Link Status
and no incoming FTE Diagnostic messages
results in the spurious indication of an FTE
Receive Fault.
l Removal and re-insertion of a CF9 module or
power cycling a CF9, when the associated PGM is
not power cycled. In this case, when the CF9 is
powered up, Link Status transitions to the 'good'
state before the CF9 completes its power on self
tests (POST) and starts passing FTE Diagnostic
messages again. This interval is long enough that
the PGM's FTE Receive Fault Diagnostic will
indicate a spurious fault.
l Throttling of Ethernet traffic during of an
abnormal amount of communication traffic on
one or both of the PGM's Ethernet ports. During a
'storm' on the FTE network, the PGM initiates
limiting of incoming Ethernet traffic on its FTE
ports. As a result of this limiting, a sufficient
number of FTE Diagnostic messages may be lost
so that one or both ports see 'good' Link Status
signals but no FTE Diagnostic messages over the
sample interval of this diagnostic. In this case, the
PGM's FTE Receive Fault Diagnostic will indicate a
spurious fault. The spurious alarm generated by
the FTE Receive Fault Diagnostic is a relatively
minor side effect, in the case of a network storm. A
network storm is signaled by other alarms in the
system.

Solution Unless you suspect that one of the causes

386
Chapter 14 - PROFIBUS Gateway Module (PGM) Troubleshooting

described above exists and is resulting in a spurious

indication, you should replace the PGM exhibiting
this diagnostic at your earliest convenience. When
this fault exists, network redundancy for this node
no longer is working.

PGM does not synchronize with backup

Diagnostic Primary module cannot synchronize with secondary
Check module. In the Monitoring view, double-click the
primary PGM icon to display the block configuration
form. Click the Redundancy tab and check the
Inhibit Sync Reason parameter description for not
achieving synchronization. Troubleshoot to correct
condition for inhibiting sync.

Cause 1 Redundancy cable bad.

Solution Replace redundancy cable. Check if the modules

synchronize.

Cause 2 PBLink cables may be disconnected.

Solution Reconnect cables to the PGM IOTA.

Cause 3 Secondary module bad.

Solution Replace the module. Check if the modules

synchronize.

Cause 4 Backup IOTA bad.

Solution Replace the IOTA. Reinstall the original secondary

module on the new IOTA. Check if modules
synchronize.

Cause 5 Primary module bad.

Solution Replace primary IOTA. Reinstall the original primary

module on the new IOTA. Check if modules
synchronize.

Cause 6 Software problem.

Solution Contact Honeywell SSC.

387
 Chapter 14 - PROFIBUS Gateway Module (PGM) Troubleshooting

Fatal ECC error

The PGM software has detected a fatal Error Checking and
Correction (ECC) condition that can be a multiple-bit error or
excessive single-bit errors in the main Random Access Memory
(RAM).

Diagnostic l The 4-character display on the modules displays

Check FAIL or mMBE.
l In the Monitoring view, the PGM icon turns red.

Cause The PGM software has detected a failure that does

not allow operation to continue. There can be many
causes for a failure including hardware. Use the
CTools utility to capture diagnostic data for the
device to determine the possible cause before
proceeding. If the error occurs in the backup RAM, a
fault is indicated. If the error occurs in main RAM,
the module freezes with mMBE on the display.

Solution Try shorting the reset pads on the IOTA to restart

the module. If error persists, replace the module.
Check the Trace log for breadcrumbs that occurred
prior to the event. Provide the results of the trace
log to Honeywell Solutions Support Center (SSC) for
analysis.

Display shows FAIL

The PGM detects failure during system integrity checks, such
as Watch Dog Timer (WDT), error detection circuits,
microprocessor static configuration registers, and Read Only
Memory (ROM) checksum.

Diagnostic l The 4- character display on the PGM displays

Check FAIL.
l In the Monitoring view, the PGM icon turns red.

Cause The PGM software has detected a background

diagnostic failure that does not allow operation to
continue.

Solution Recycle power to the module. If error persists,

388
Chapter 14 - PROFIBUS Gateway Module (PGM) Troubleshooting

replace the module. Check the Trace log for

breadcrumbs that occurred prior to the event.
Provide the results of the trace log to Honeywell
Solutions Support Center (SSC) for analysis.

Isolated (lonely) Node

For a redundant PGM pair, Fault Tolerant Ethernet (FTE)
communications with partner and FTE network are lost.

Diagnostic l The primary module determines whether or not

Check to initiate a switchover. If the secondary module
was known to be in a better condition than the
primary at the time of fault determination, then
the primary should fail so the secondary will
switchover. But, the new secondary (old primary)
still cannot restore FTE communications.
l The secondary module should reboot once, in an
attempt to restore communications. The primary
module will be able to report the problem in the
secondary. If the secondary cannot restore FTE
communications, it should be able to
resynchronize over the redundancy link and be a
partially functional backup.

Cause 1 Secondary module is defective.

Solution Replace the secondary module that initiated

switchover when fault was detected. If secondary
module synchronizes after replacement, the
removed module is defective. Otherwise, go to
Cause 2.

Cause 2 Secondary IOTA is defective.

Solution Replace the secondary IOTA that initiated

switchover when fault was detected. If secondary
module synchronizes after replacement, the
removed IOTA is defective. Otherwise, go to Cause 3.

Cause 3 Primary module is defective.

Solution Replace the primary module. If you can command

389
 Chapter 14 - PROFIBUS Gateway Module (PGM) Troubleshooting

synchronization after replacement, the removed

module is defective. Otherwise, go to Cause 4.

Cause 4 Primary IOTA is defective.

Solution Replace the primary IOTA. If the module pair

synchronize after IOTA replacement, the removed
IOTA is defective. Otherwise, go to Cause 5.

Cause 5 There is a software problem.

Solution Contact Honeywell Solution Support Center (SSC).

Duplicate Device Index setting

The FTE subsystem detects duplicate Device Index settings in
separate modules.

Diagnostic All modules will stop tracking cable status for the
Check detected duplicate Device Index value.
Communications will continue and will not impact
system performance until there is a cable fault. This
fault will also be detected by the FTE System
Management Tool. A duplicate Device Index could
cause a duplicate IP Address. In most cases, the
duplicate IP Address would be detected first and
prevent the FTE diagnostic messages from being
sent.

Cause Device Index switches on separate IOTA's are set to

same value.

Solution Change Device Index switches setting on one of the

IOTA's to a unique value.

Device Index value is zero upon power up

The PGM's 4-character display shows a Device Index value of
zero (#000).

Diagnostic Ensure that the Device Index switches on the IOTA

390
Chapter 14 - PROFIBUS Gateway Module (PGM) Troubleshooting

Check were not intentionally set to zero to initiate a Device

Index/IP Address reset.

Cause 1 Device Index switches set to zero.

Solution Change Device Index switches to correct setting.

Cause 2 The module is defective.

Solution Replace the module. If Device Index switch setting

matches Device Index number in 4-character
display upon PGM power up, the removed module is
defective. Otherwise, go to Cause 3.

Cause 3 The IOTA is defective.

Solution Replace the IOTA. If Device Index switch setting

matches Device Index number in 4-character
display upon PGM power up, the removed IOTA is
defective.

Getting further assistance

Other troubleshooting sources
The following table lists other documents and sections that
contain troubleshooting information for other
ExperionLXPlantCruiseExperion PKS subsystems.
All of these documents are available in the User Assistance
library. Some documents are also supplied as part of Station
Help. Look for the document within the User Assistance library
where RXXX represents the latest release number designation.

Document/Section Comments

Experion There is a separate interface

LXPlantCruiseExperion PKS reference for each type of controller
RXXX > Reference other than the Process Controller;
for example, the ASEA Interface
Reference. Most of these references
contain an interface-specific
troubleshooting section.

391
 Chapter 14 - PROFIBUS Gateway Module (PGM) Troubleshooting

Document/Section Comments

ExperionRXXX > Reference Troubleshooting an integrated

> TPS Integration Guide > system that uses Experion "TPS
Troubleshooting Integration" option.

Experion Describes error codes generated

LXPlantCruiseExperion PKS from within Control Builder.
RXXX > Reference > Control
Builder Error Codes
Reference

Experion The main repository for

LXPlantCruiseExperion PKS troubleshooting, maintenance and
RXXX > Troubleshooting repair of Process Controllers.
and Maintenance > Control
Hardware Troubleshooting
and Maintenance Guide

Experion Troubleshooting FTE bridges.

LXPlantCruiseExperion PKS
RXXX > Configuration >
Fault Tolerant Ethernet
Bridge User's Guide >
Service > Troubleshooting

Experion Troubleshooting FTE nodes.

LXPlantCruiseExperion PKS
RXXX > Installation and
Upgrades > Fault Tolerant
Ethernet Installation and
Service Guide >
Troubleshooting FTE Nodes

Experion Troubleshooting TDC 3000 Hiway

LXPlantCruiseExperion PKS problems.
RXXX > Reference >
Honeywell TDC 3000 Data
Hiway Interface Reference >
TDC error codes and
Troubleshooting

392
Chapter 14 - PROFIBUS Gateway Module (PGM) Troubleshooting

Document/Section Comments

Experion Troubleshooting QVCS.

LXPlantCruiseExperion PKS
RXXX > Configuration >
Qualification and Version
Control System User Guide
> QVCS Troubleshooting

Experion Describes the meaning of SafeView

LXPlantCruiseExperion PKS configuration errors.
RXXX > Configuration >
SafeView User's Guide >
Appendix D - SafeView
Error Messages

Experion Describes the meaning of error

LXPlantCruiseExperion PKS messages in the server log specific
RXXX > Reference > Server to server scripting.
Scripting Reference >
Server scripting error
messages

Experion Describes the meaning of SES

LXPlantCruiseExperion PKS Configuration errors.
RXXX > Configuration >
System Management
Configuration Guide >
Troubleshooting System
Management

Experion Describes the meaning of SPS

LXPlantCruiseExperion PKS Configuration errors.
RXXX > Configuration >
System Management
Configuration Guide >
System Performance Server
> Troubleshooting SPS
configuration

Experion RXXX > Planning Troubleshooting workstation nodes

and Design > Planning, used in Experion and TPN.
Installation, and Service for

393
 Chapter 14 - PROFIBUS Gateway Module (PGM) Troubleshooting

Document/Section Comments

WS360

Guidelines for requesting support

If you cannot resolve a problem using this guide, you can
request support from your Honeywell Solution Support Center.
When requesting support, please supply as many relevant
details as possible, including:
n Short summary of the problem.
n Product Name and release.
n Recent changes - Such as upgrades/service packs, to
ExperionLXPlantCruiseExperion PKS software, Windows or
other applications.
n Subsystem and its version/build - If the problem relates to a
particular subsystem, such as Station or Quick Builder. If the
problem relates to Display Builder, please specify whether it
is HMIWeb Display Builder (for HMIWeb displays) or Display
Builder (for DSP displays).
n Operating system, variant and service pack - For example
"Windows 2000 Server, SP5."
n Instructions on how to reproduce the problem - If the problem is
reproducible, please supply step-by-step instructions - the
more detailed the steps, the better.
n Diagnostic package which contains any relevant logs.

394
NOTICES
Trademarks
Experion®, PlantScape®, SafeBrowse®, TotalPlant®, and TDC 3000® are registered
trademarks of Honeywell International, Inc.
ControlEdge™ and Honeywell Ionic™ are trademarks of Honeywell International, Inc.
OneWireless™ is a trademark of Honeywell International, Inc.
Matrikon® and MatrikonOPC™ are trademarks of Matrikon International. Matrikon
International is a business unit of Honeywell International, Inc.
Movilizer® is a registered trademark of Movilizer GmbH. Movilizer GmbH is a
business unit of Honeywell International, Inc.

Patents
For patent information, see www.hsmpats.com

Other trademarks
Microsoft and SQL Server are either registered trademarks or trademarks of
Microsoft Corporation in the United States and/or other countries.
Other brands or trademarks are trademarks of their respective owners.
Trademarks that appear in this document are used only to the benefit of the
trademark owner, with no intention of trademark infringement.

Third-party licenses
This product may contain or be derived from materials, including software, of third
parties. The third party materials may be subject to licenses, notices, restrictions and
obligations imposed by the licensor. The licenses, notices, restrictions and
obligations, if any, may be found in the materials accompanying the product, in the
documents or files accompanying such third party materials, in a file named third_
party_licenses on the media containing the product.
Documentation feedback
You can find the most up-to-date documents in the Support section of the
Honeywell Process Solutions website at: https://process.honeywell.com
If you have comments about Honeywell Process Solutions documentation, send
your feedback to: [email protected]
Use this email address to provide feedback, or to report errors and omissions in the
documentation. For immediate help with a technical problem, contact HPS
Technical Support through your local Customer Contact Center, or by raising a
support request on the Honeywell Process Solutions Support website.

How to report a security vulnerability

For the purpose of submission, a security vulnerability is defined as a software
defect or weakness that can be exploited to reduce the operational or security
capabilities of the software.
Honeywell investigates all reports of security vulnerabilities affecting Honeywell
products and services.
To report a potential security vulnerability against any Honeywell product, please
follow the instructions at:
https://www.honeywell.com/us/en/product-security.

Support
For support, contact your local Honeywell Process Solutions Customer Contact
Center (CCC). To find your local CCC visit the website,
https://process.honeywell.com/us/en/contact-us.

Training classes
Honeywell holds technical training classes that are taught by process control
systems experts. For more information about these classes, contact your Honeywell
representative, or see https://process.honeywell.com/us/en/services/training.