 Honeywell.

com

PGM BASED PROFIBUS

CONFIGURATION

FF, Profibus & Third Party Interfaces

POG

EPKS 1
  Honeywell.com

Agenda

• Basics of Profibus
• PGM Architecture
• PGM Capacity & Topology
• DSB and PDC Configuration
• Control Paradigm
• Sycon.net
• Control Builder Configuration Overview

EPKS 2
  Honeywell.com

Basics of PROFIBUS

• Profibus is an Open, Vendor Independent Protocol

• Part of IEC 61158 Standard
• Three Main variants of Profibus;
– Profibus DP
– Profibus PA (FF H1 like network)
– Profibus FMS
• Integration of Experion PKS with Profibus is through Profibus DP
Profile
• Profibus DP Extensions
– Profibus DPV0 (deterministic)
– Profibus DPV1 (non-deterministic)
– Profibus DPV2

EPKS 3
  Honeywell.com

Basic Theory of PROFIBUS DPV

• PROFIBUS DP is a master/slave, token passing network, which utilizes
a request/response protocol
– Bi-directional Network
– Message from master recognized by Slave with address.
– Presentation Layer ‘not defined’
– Baud Rate 9.6kbps to 12000 kbps
• A single IO Network/bus on which all IO peripheral devices reside
• RS485 Daisy chain bus or redundant fibre optic segments
• Cyclic IO Data exchange (DPV0)
• Acyclic non-deterministic (DPV1)
• Profibus PA is powered network similar to FF H1 (valves, Tx, etc)
• Experion directly supports DP networks and can also access PA
network using DP/PA coupler
• Several Unique devices can exist on Profibus network. Examples;
PLCs, I/O nodes, drives, encoders, etc.

EPKS 4
  Honeywell.com

Profibus DP Extensions

EPKS 5
  Honeywell.com

Data Transfer Mechanism

• Station: Each node on network with unique Profibus address.
– Up to 126 unique stations can be configured on DP network
• DP Master Class-1 (PGM)
• DPV0 Mechanism: Process related data (PV, OP) is cyclic and
has highest priority and must occur within given time window
• At the end of DPV0 cycle a gap time can be established for
DPV1
• Token is passed within masters to determine network use
• Each master is assigned a set of slaves
• Each slave can send 244 bytes of input data and can receive 244
bytes of output data
• DPM1 has two tasks
– Receive inputs and send outputs to slaves
– Provide this data to and from the host control system

EPKS 6
  Honeywell.com

Profibus Gateway Module with 2 DP Networks PGM-2

ProfiBus DP
Gateway
CC-IP0101

 6 inch SC IOTA

 Shown in optionally redundant configuration

Key Characteristics:

Mounts in a standard SC cabinet

 SC look, feel, and behavior
PGM is standard FTE node
 Optional module redundancy
 Supports two DP networks per module

EPKS 7
  Honeywell.com

Architecture Scenario
1

EPKS 8
  Honeywell.com

Architecture Scenario 2

EPKS 9
  Honeywell.com

Example Architecture from a Project

EPKS 10
  Honeywell.com

FTE Topologies
Local Configuration SC PGM in remote cabinet
(same cabinet complex) (remote from C300)

To Level-2 Switch
Level-2 Switch *

Copper
CF9 * or Fiber
CF9 * CF9
*
FTE-A

C300 FTE-A
C300
SC PGM
SC PGM

* Only cable A is shown; for FTE B these components are doubled.

EPKS 11
  Honeywell.com

IOTA Connections and Major

Components SC power bus bar
Fuse Primary PGM connections

FTE A and B
ProfiBus DP (Network 1) connections

ProfiBus DP (Network 2)

Redundancy
sync cable (CAT5e)
FTE address setting
4 5 6 4 5 6 4 5 6
1 2 3

1 2 3

1 2 3

Backup PGM
7 8

7 8

7 8

0 9 0 9 0 9

100 10 1 Provides optional

module redundancy.

FTE IP
address = ### ### ### ###

Cluster
identification
EPKS 12
  Honeywell.com

PGM-2 Capacity & Topology

• Connected to C300 via CF9 preferably same CF9 used by C300 (Best Practice)
• 2 separate IOTAs with connecting private path unlike FIM4
• Number of Profibus Networks per PGM2 : 2
• Redundant PGM2 pair must be connected to same CF9
• Unique FTE Device Index

• PGM utilizes the PDA protocol for process data transfer between the C300 Controller
and the Profibus devices over the Profibus network
• Number of PGM per Server: 40
• Each C300 can support PDA connections to 4 logical PGMs
• Each PGM2 can be PDA connected to only one C300
• Valid PROFIBUS Station address range: 0 – 125
• Each Profibus network per PGM2 can be configured with different Baud Rate

EPKS 13
  Honeywell.com

Engineering Tools
SC PGM
FTE

DP Network-1
Control Builder
DP Network-2
S
S
S
S DP Network Configuration Experion Configuration

S • Baud rate selection • Create/Configure all CB blocks

S • Slave/Master addressing • Configure SC PGM redundancy
•
+ •
S Slave type and layout Build Control Strategy
S • DP cycle time & schedule • Etc.
• Etc.
S
S
S
S
S
S
S
S

EPKS 14
  Honeywell.com

DSB & PDC Configuration

• DSB (Device Support Block): The main control objects of the PGM on PBLink. Each
DSB block is characterized by a set of parameters and an algorithm.
• Maximum DSB Blocks per PGM2 : 248
• Maximum Input/output Data Size per PGM2 Profibus Network (all slave stations):
3.5KBps (Max 244 bytes per Slave)
• DSB Blocks like Generic DSB, ET200 DSB, ProfiDrive DSB
• Generic DSB: 16 PDCs/DSB, 32 Max Channels per PDC

• Process Data Collection (PDC) - A new data structure that can store and map several
input or output process data items (channels) from a given slave device to one or more
PIOMB blocks in the C300 Controller.
• Each PDC must be configured for only “Inputs” or only “Outputs”. Minimum of 2 PDCs
required for any slave having both inputs and outputs.

• 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

EPKS 15
 CB Tree Structure &  Honeywell.com

Correlation to Field
+ C300
C300 HardwareI/O Module

D P In ter

D I-1 6
D O -4
A O -4
D I-8
A I-8
+ CEE
- CM
- CM
- SCM

- I/O
PIOMB

PIOMB

+ SC PGM (Primary) (PGM)

SC PGM
+ DP_Network_1 (PB) Primary
- Slave_A (DSB)
- Slave_B
DP Network 1

- Slave_x
DP Network 2
Slave A
+ DP_Network_2 (PB) Backup
- Slave_A (DSB) Slave B
- Slave_B

- Slave_x
Slave x
+ SC PGM (Backup) (PGM)

EPKS 16
  Honeywell.com

+ C300 Control Paradigm

+ CEE Control Module Note: All applicable control constraints (init, bad PV, etc.) will be applied.
5
- CM
- CM AI Function AO
- SCM Channel Block Channel
- I/O
Module PIOMB
4
PIOMB

+ SC PGM (Primary) (PGM) 1 C300

+ DP_Network_1 --- PB 2
- Slave_A --- DSB 3
- Slave_B
FTE
- Slave_x

+ DP_Network_2
Diagnostics - Standard & Extended SC PGM
- Slave_A
- Slave_B Slave A (V0 cyclic data)
- Slave_x AI Up to 244 bytes input data
DP
+ SC PGM (Backup)
AO Up to 244 bytes output data

EPKS 17
  Honeywell.com

Profibus Configuration Tool- Sycon.net

• Sycon.net Utility installed on Flex/Console when installed with
PGM Component
• Used for configuring field network devices
• Maintains GSD File (electronic Device Description)
• When a vendor develops a slave device, it must develop a GSD
file. This file completely describes the Profibus functionality of
device.
• Copy GSD file into GSD subdirectory
C:\ProgramData\SYCONnet\PROFIBUS\GSD

EPKS 18
  Honeywell.com

Configure the PB Link Blocks

Adding new devices to device library

To add new GSD-based devices to
SYCON.net library (device catalog), user
should first copy GSD files to: C:\\
ProgramData\SyConNet\Profibus\GSD.

After the files are copied Device Catalog

needs to be rebuilt by clicking Reload
Catalog button
in the Field Network Configuration tab
toolbar.

EPKS 19
  Honeywell.com

Configure the PB Link Blocks

• Add Slave Devices

EPKS 20
  Honeywell.com

Configure the PB Link Blocks

• Configure Slave Process Data Tags

EPKS 21
  Honeywell.com

Configure PDC Information (1)

• Configure the Applicable PDC Parameters

EPKS 22
  Honeywell.com

Configure PDC Information (2)

• Configure the Applicable Channel Parameters

EPKS 23
  Honeywell.com

Configuration Guidelines and Considerations

• All byte and bit offsets are zero based specifications. First byte of data message is
considered as byte 0. A data message of 8 bytes is 0-7 bytes

• All data offsets are indicated in units of byte means byte 0 is the byte at lowest
memory address location

• All bit offsets are made relative to a byte and therefore span the range 0-7.

• When a byte is presented in binary format, bit 0 is on right side.

– Foe example only bit 0 is set : 00000001

EPKS 24
  Honeywell.com

Configure the PIOMB Block (3)

• Configure the Applicable Parameters (Gen DSB)

EPKS 25
  Honeywell.com

Configure the PIOMB Block (4)

• Associate the PIOMB Block with the Desired PDC

EPKS 26
  Honeywell.com

Configure the Control Module (5)

• Instantiate the Desired Channel Block

• Assign the Channel to the PIOMB
EPKS 27
  Honeywell.com

Software Overview
• Blocks for the PGM
– Platform Block similar to the C300/FIM
– Protocol Block (PB Link)
– Device Support Blocks (DSB)
• Generic
• Device Specific
– Process Data Container (PDC) structure

• C300 Blocks for IO/Control Integration

– Profibus IO Module (PIOMB) encapsulates the Process Data from the PDC
– New Channel Blocks
• Analog Input
• Analog Output
• Digital Input
• Digital Output

EPKS
28
28
  Honeywell.com

Device Support Blocks Supported

• Generic DSB:
 For slaves not covered by Specific Device Profiles
 Single bit (Discrete),
 8 bit signed/unsigned integer,
 16 bit signed/unsigned integer,
 32 bit signed integer,
 32 bit IEEE floating point

• Device Specific Profiles:

 CEAG PROFIBUS Remote I/O
 Drive Type Devices
 Siemens DP/ASi
 Siemens ET200M I/O
 Turck Excom IO Gateway

EPKS 29
  Honeywell.com

DPV1 Related…
• DPV0 is cyclic data exchange and knows only about DP Master Class 1
• PDC supports only DPV0
• PGM is a transparent tunnel that can be used by ANOTHER Program in
a manner that PGM acts as DP Master Class 2 for configuration in order
to get access to device via Profibus Network
• DPV1 introduces Acyclic data and PART of this specification uses DP
Master Class 2 to impose configuration data into bus traffic
• Slaves with DPV0 can perfectly co exist with slaves of DPV1 at a PGM
driven Profibus network

• DP-V0 is a subset of DP-V1. This means if you have a DP-V1 slave,

then you can configure it via SYCON.net of course, you can even use
the DP-V0 (cyclic data) of this slave via PDC in the DSB. But you cant
get the ACYCLIC DP-V1 data into the C300 controller via DSB/PDC

EPKS 30
  Honeywell.com

Precautions
• Customer Inputs
– Latest GSD File matching with Device Firmware
– Module Configuration
– Data Frame Format (Big Endian/Little Endian)
– Data Format for AIs (e.g. 8/16/32 bit UINT/INT)
– Modbus Addressing (Not for all devices)
• No simulation capabilities available for PBus IO testing
• No Bulk Build of Profibus IOs possible
• Always make IO Channel assignment in the end to avoid rework
– If you need to change something on DSB side, you will have to first
delete from monitoring and then delete all the connections up to CM
and make necessary changes.
• Refer manufacturer manual for details of data map

EPKS 31
  Honeywell.com

References

• SLP for Profibus Implementation in EPKS R4XX..Girish Nalgirkar

• ExperionR410 PCT DFS

»Thank You

EPKS 32