System 800xA training

Chapter 2 PROFIBUS/HART Fundamentals

TABLE OF CONTENTS

Chapter 2 PROFIBUS/HART Fundamentals ................................................................................................................................ 1

2.1 General Information............................................................................................................................................................. 2
2.1.1 Objectives ..................................................................................................................................................................... 2
2.1.2 Legend .......................................................................................................................................................................... 2
2.1.3 Reference Documentation............................................................................................................................................. 2
2.2 Introduction ......................................................................................................................................................................... 3
2.2.1 Application Areas and Advantages............................................................................................................................... 3
2.2.2 Fieldbus Standards........................................................................................................................................................ 3
2.2.3 Communication Standards ............................................................................................................................................ 6
2.3 Basics – PROFIBUS............................................................................................................................................................ 7
2.3.1 PROFIBUS Family ....................................................................................................................................................... 7
2.3.2 ISO/OSI Transmission Layers ...................................................................................................................................... 9
2.3.3 Extended Functions..................................................................................................................................................... 10
2.3.4 Block Model and Profiles ........................................................................................................................................... 11
2.3.5 Interoperability / Interchangeability............................................................................................................................ 13
2.3.6 Transmission Technology........................................................................................................................................... 14
2.3.7 Bus Topologies and Termination................................................................................................................................ 18
2.3.8 Master / Slave ............................................................................................................................................................. 21
2.4 Basics - HART Communication ........................................................................................................................................ 24
2.4.1 Open Standard ............................................................................................................................................................ 24
2.4.2 HART Commands ...................................................................................................................................................... 25
2.4.3 Communication within the System ............................................................................................................................. 26
2.5 FDT/DTM Technology...................................................................................................................................................... 27
2.5.1 Principle...................................................................................................................................................................... 27
2.5.2 Device Type Manager (DTM) .................................................................................................................................... 28
2.5.3 Field Device Tool (FDT) ............................................................................................................................................ 29
2.5.4 Nested Communication using FDT/DTM................................................................................................................... 30
2.6 Technical Summary ........................................................................................................................................................... 31
2.6.1 Technical Summary HART ........................................................................................................................................ 31
2.6.2 Technical Summary DTM .......................................................................................................................................... 33

Chapter 2 - 1
T316-02 Fundamentals - DRAFT.doc

2.1 General Information

2.1.1 Objectives
On completion of this chapter you will be able to:
• Identify the use of the different standards
• Explain the FDT/DTM principles
• Recognize the main parts of the PROFIBUS protocol

2.1.2 Legend
<> Indicates a key name.
| Indicates when you go from one menu to a sub-menu.
Bold Indicates a menu name or an option in a menu, or file structures
“ “ Indicates dialog box buttons, tabs, instructions etc.

) Indicates start/explanation of student activity

2.1.3 Reference Documentation

30/FB-10 EN PROFIBUS solutions from ABB
http://www.profibus.com

Chapter 2 - 2
 System 800xA training

2.2 Introduction
Fieldbus systems are used as a means of communications for serial data exchange
between decentralized devices on the field level and the Control System on the process
supervision level.
All relevant signals such as input and output data, parameters, diagnostic information,
configuration settings and – for a wide range of applications (PA/H1) – the power
required for operation can be carried over two wires.
If a PA/H1 field device has high-power requirements, then this device can be powered
externally (e.g. Advanced Optima 2000 Gas Analyzer).

In addition to intelligent transmitter and actuators with a direct connection to the

fieldbus, intelligent Remote I/Os are also used as interface systems for conventional
4...20 mA or HART field devices to record process data on the field level.

2.2.1 Application Areas and Advantages

The unambiguous specification of the communications protocol makes it possible to
keep the fieldbus open for all providers who use the protocol for their devices.
As a result, the interchangeability common for 4...20 mA devices is maintained for
fieldbus devices.

The existing benefits in installation costs, engineering and commissioning are now
supplemented by those related to Asset Optimization. Digital communication enables
real time access and transfer of field resident information, previously unavailable to the
Control System.
Advanced procedures for preventive maintenance are now possible and fieldbus is
open for future new requirements.

2.2.2 Fieldbus Standards

PROFIBUS and FOUNDATION Fieldbus are the accepted Fieldbus standards for the
automation industry. Both busses (PA/H1) can offer power over the bus for field
devices and provide pure digital communications between the field and the Control
System.
In terms of Fieldbus organization they are similar with many user groups and
supported worldwide by the major manufacturers. The PROFIBUS International User
Organization has its headquarters in Karlsruhe Germany and the Fieldbus
FOUNDATION has its headquarters in Austin Texas. Both systems are part of IEC
61158.
The technologies of PROFIBUS and FOUNDATION Fieldbus are different in several
important areas although the installation guidelines of PROFIBUS PA and
FOUNDATION-H1 are similar as they share the same physical layer (see section 2.3
ISO/OSImodel).

Chapter 2 - 3
T316-02 Fundamentals - DRAFT.doc

2.2.2.1 PROFIBUS
PROFIBUS has evolved from the high-speed busses required between PLC and I/O
racks (PROFIBUS FMS and DP). This has resulted in a large well-developed range of
DP devices. Support for process automation was completed with the extension of DP
to intelligent field devices via the PROFIBUS PA protocol.
PROFIBUS PA can supply power over the bus for devices such as transmitters and
positioners which can be extended into Ex-(hazardous) areas (EEx i). PA segments are
connected to the DP-Line via segment coupler or Linking Devices. PA devices are
available for almost every measurement requisition.

PROFIBUS operates as Master / Slave protocol with the master as typically a DP

device and the slaves being either DP or PA devices.
Different versions of the protocol are available:
• Cyclic access (V0 protocol) of the line can be optimized already during the
planning phase (real-time behavior).
• Acyclic commands (V1 protocol, engineering interaction) are allowed for a part of
the network bandwidth.
• Direct Slave-to-Slave communication (V2 protocol) is the last expansion stage.
Device Interoperability is achieved via the use of profiles and product certification.

2.2.2.2 FOUNDATION Fieldbus

FOUNDATION Fieldbus has evolved from the intelligent fieldbus level with devices
becoming available from 1999. This is the FOUNDATION Fieldbus-H1 level and can
supply power over the bus for devices such as transmitters and positioners and can be
extended into Ex(hazardous) areas (EEx i).
FOUNDATION Fieldbus-HSE is the high-speed bus based upon Ethernet technology
and requires a Linking Device to connect to the H1 level. Ethernet was chosen to
enable the use of readily available and low cost networking components and will
become the method of choice for the connection of complex externally powered
devices to FOUNDATION systems.

FOUNDATION Fieldbus devices use the decentralized function distribution with

following features:
• Alarm stamping at source
• Deterministic communications between the field devices (AI, AO, PID etc.)
• Device to device communication
Field devices contain standard function blocks in the User Layer.
These function blocks include AI, AO, PID but can also provide for manufacturer
innovation. Interoperability is achieved via Device Descriptions (DD), Capability Files
(CFF) and independent testing – device registration.

Chapter 2 - 4
 System 800xA training

2.2.2.3 International Standards

PROFIBUS® and FOUNDATION Fieldbus™ are now worldwide standardized as a
result of the IEC fieldbus standards committee decision to append other protocols to
the IEC 61158 standard.
Eight protocols are included in IEC 61158:
1. FF-H1
2. ControlNet
3. PROFIBUS
4. Interbus
5. P-Net
6. WorldFIP
7. SwiftNet
8. FF HSE

FOUNDATION Fieldbus Standards – by country:

• British Standard DD238
• Euro Standard EN 50170
• US Standard ISA S50

PROFIBUS DP and PA Standards – by country:

• British Standard BS EN 50170
• Euro Standard EN 50170
• US Standard None

Chapter 2 - 5
T316-02 Fundamentals - DRAFT.doc

2.2.3 Communication Standards

Standardization and openness are the characteristics of modern automation systems.

IEC
IEC 61
61 131
131

TCP/IP
MMS
MMS

• On the field level PROFIBUS, FOUNDATION Fieldbus and HART

• The controller level and the operator level communicate by using TCP/IP on
MMS.
• Software applications communicate by using the COM/DCOM technology of
Microsoft. OPC and ActiveX are based on these technologies.
• The engineering tool communicates with device specific applications of other
manufacturers by using the FDT interface.
• FDT/DTM is an interface for sophisticated engineering of PROFIBUS and
HART devices within an engineering tool.
• A Remote I/O-System has to communicate with transmitters for setting
parameters and reading status information via HART-Communication.

The different standards fulfill the different requirements in terms of:

- Speed
- Safety
- Openness

Chapter 2 - 6
 System 800xA training

2.3 Basics – PROFIBUS

2.3.1 PROFIBUS Family

PROFIBUS is a manufacturer-independent fieldbus standard for general purpose there
are more than 7 millions nodes commissioned around the world. With a wide range of
vendors more than 2000 product are available in the market today.
PROFIBUS technology is described in fixed terms in DIN 19245 as a German standard
and in EN 50170 / IEC 61158 / EN 50254 as an international standard. The
PROFIBUS standard is thus available to every provider of automation products. There
are 24 regional associations with more than 1200 members.

The PROFIBUS family is composed of three types of protocol, each of which is used
for different tasks. Of course, devices with all three protocols can communicate with
each other in a complex system by means of a PROFIBUS network: applications in
manufacturing, process and building automation. For this standard
• PROFIBUS FMS (Fieldbus Message Specification)
• PROFIBUS DP (Decentralized Periphery)
• PROFIBUS PA (extension for Process Automation)

Only two protocol types, DP and PA are important for process automation.

Chapter 2 - 7
T316-02 Fundamentals - DRAFT.doc

PROFIBUS DP
PROFIBUS DP (RS 485) is responsible for communication between the Controller
level of a process automation system (PLC) and the decentralized periphery in the
field, also intrinsic safety (RS485-IS) via DP-Ex barriers into hazardous area. One
feature of PROFIBUS DP is its high speed of transmission upon to 12 Mbit/s.

PROFIBUS PA
This PROFIBUS variant was developed for the process industry. Communication and
power supply to transmitter and positioners are handled direct via one 2-line cable and
correspond to IEC Standard 61158-2 (named also as MBP, MBP-LP). Intrinsic safety
(EEx i) (MBP-IS) installations in Zone 1 / Div.1 are possible.

Coupling components (segment couplers, Linking Devices) are used to integrate PA

bus lines into the PROFIBUS DP network. This ensures that all information is
available in a continuously connected network through the complete PROFIBUS
system (DP and PA).

Chapter 2 - 8
 System 800xA training

2.3.2 ISO/OSI Transmission Layers

In accordance with the international ISO/OSI model, a fieldbus protocol can be
uniquely described by means of up to 7 transmission levels (layers). Specific tasks are
assigned to each level in this system.

Profibus
Devices
FMS DP PA

FMS-Profiles DP-Profiles PA-Profiles

User-
Layer
DP-Extensions (DP/V1)
USIF
DDLM DP-Basic functions

Application-
Layer FMS, LLI 7

Layer-Level
not used 3-6

Data-Link-
Fieldbus Data Link (FDL) IEC Interface 2
Layer

Physical-
Layer RS 485 Fiber Optic IEC 1158-2 1

OSI = Open-System-Interconnection, manufacturer independent communication

EN 50170-2 DIN E 19245-T4 PROFIBUS Guidelines

ISO/OSI-Layer Model on PROFIBUS

PROFIBUS DP and PROFIBUS PA use only the first two layers as well as the user
interface, which resides in layer 7 and where application functions that can be utilized
by the user are determined along with system and device behavior.
• Layer 1 the physical layer defines cables, connectors, voltage etc. being the
physical condition for safe data transmission.
• Layer 2 the data link layer defines the traffic rules for access to the medium, data
plausibility, data format and saving.
• Layers 3-6 are not used on PROFIBUS because there is no routing necessity etc.
• Layer 7 represents the user layer. Services and profiles are defined on this layer.

Direct access from the user interface (UI) to layer 2 is possible through the Direct Data
Link Mapper (DDLM).

Chapter 2 - 9
T316-02 Fundamentals - DRAFT.doc

2.3.3 Extended Functions

The extended functions of PROFIBUS DP are required to set parameters and operate
the system. The characteristics of devices and their behavior are described in profiles
and are specified in the standard.
These extended functions are optional so that it is still possible to continue using older
PROFIBUS DP devices.

Presently the basic and extended functions are:

DP V2
Deterministic Time Mode
Redundancy
Upload / Download
Clock Sinc and Time Stamp
Publisher / Subscriber
Isochronous Mode
Slave to Slave Communication

DP V1
Master/Salve Acyclic Data Exchange
Alarm Handling
EDD and FDT Integration
Fail Safe
Function Blocks IEC 61131-3

DP V0
Master/Salve Cyclic Data Exchange
GSD
Diagnostic

All functions and the PA profile are used both for PA and DP field devices. Both types
of devices can be operated with the aid of simple couplers on a bus system.

Chapter 2 - 10
 System 800xA training

2.3.4 Block Model and Profiles

The block model, which corresponds to international guidelines, is used for profiles.
A part of these data has to be realized in any case, others are optional. Parameters,
which cannot be found in the profile belong to the manufacturer-specific group.
To be able to configure also these parameters, including the profile parameters, the
open FDT/DTM Device Management Tool is used today.

Profile distinction is made between the

• Physical Block
defines the hardware
• Transducer Block
parameters of physical measurement size, present multiple times for multi-function
sensors
• Function Block
functions from the point of view of the PLC or DCS, for example analog input for
sensors or analog output for actuators

The dynamic process values of a "Analog Input" Function Block consisting of the
measured value (4 Byte) and the assigned status (1 Byte) are read or written
cyclically by a PLC and/or DCS.

The profile parameters of all blocks can only be read and / or written acyclically.

Chapter 2 - 11
T316-02 Fundamentals - DRAFT.doc

Below is listed, in what detail profiles describe the features of a transmitter:

Physical Block
Manufacturer, name of unit, serial number, diagnosis (selftest), password, certification,
factory setting, unit description, unit information, date of manufacture, software
revision, hardware revision, TAG, configuration meter

Transducer Block (e. g. pressure transmitter)

Sensor calibration, test of the sensor limits, sensor alarms, conversion into physical
units depending on the application, sensor type, process connection material, material
of diaphragm, filling fluid, pressure level, O ring material
• Transmitters:
temperature, pressure, flow, level, density, weight mass, speed, rotary speed,
radiation, quality, electrical variables
• Control actuators:
electric actuator, electro-pneumatic and electro-hydraulic actuator
• Binary input / binary output

Function Block
Input channel, filter time constant, scaling of the process variables, scalability of output
variables, alarms (HI_HI, HI_, LO_, LO_LO, hysteresis), simulation,
An analog input or output signal consists of 4 bytes for the valueand1 byte for the
status, so one analog signal needs 5 bytes in the data unit of a cyclic telegram.
The analog value representation is a floating point value based on the data type
REAL(4 bytes for sign, mantissa and exponent).
A discrete input or output signal consists of 1 byte for the valueand1 byte for the status,
so one discrete signal needs 2 bytes in the data unit of a cyclic telegram.

Chapter 2 - 12
 System 800xA training

2.3.4.1 Example: Analog Input Block

The analog input block of the profile thus represents the basic functionality linking all
sensors. Profile version V3.0 is presently most up to date.

It provides the physical limit, measurement range and measurement value of the
measurement converter, two upper and two lower threshold values as well as the
corresponding status messages and alarms.
These parameters and status messages can be similarly and effectively used with all
measurement transformers.

2.3.5 Interoperability / Interchangeability

Using PROFIBUS profiles makes devices interoperable, in other words devices of
different manufacturers can be physically connected to a single bus and are able to
communicate with each other and with foreign host.
In addition to this, however, they are also interchangeable, which means devices of
different manufacturers with standard GSD’s can be exchanged one for another
without engineering effort to change the configuration in the process automation
system.

Chapter 2 - 13
T316-02 Fundamentals - DRAFT.doc

2.3.6 Transmission Technology

2.3.6.1 PROFIBUS DP
The transfer method of PROFIBUS DP is RS 485, which has been used successfully
for many years. This technology can always be used to advantage if high transfer rates
and a simple method of installation are required.
A twisted, shielded two-wire copper cable (Type A) is used as the transfer medium.
Depending on local conditions, the shield should be connected on one or both ends of
the cable segment to the potential equalization system.
The bus structure makes it possible to add devices step by step and also to extend or
limit the number of subscribers in operation on the system. You can select a transfer
rate between 9.6 kBits/s and 12 Mbits/s.

Physical Telegram / RS485 NRZ

UART = universal asynchronous receiver/transmitter
PROFIBUS DP is exchanging the data in the NRZ Code (non return to zero), that
means, the signal state of binary "0" or "1" does not change during the bit duration
(unlike the Manchester Code which is used with PROFIBUS PA).

The cabling consists of two wires:

• B (red color, positive)is the origin
• A(green color, negative) is the inverted data line
The logic signal level “1” (High, True) means positive voltage on B opposite to A.
The logic signal level “0” (Low, False) means negative voltage on B opposite to A.

Chapter 2 - 14
 System 800xA training

2.3.6.2 PROFIBUS PA
Profibus PA uses the Profibus DP-V1 protocol. Profibus PA is the profile for Process
Automation, typically with synchronous transmission at a defined rate of 31.25 Kbit/s
and Manchester coded.
In addition to the general requirements such as transfer security, range and transfer
rate, additional requirements must be fulfilled for two-line measurement transformers.
• Power and data transmission through a common cable
• Explosion protection (intrinsic safety) for the chemical and petro-chemical
industry

PROFIBUS PA lines are connected via Linking Devices (e.g. LD 800P from ABB) to
PROFIBUS-DP-segments. These linking devices adapt the RS-485-physic to the IEC-
61158-2-physic and provide the power supply for the PA slaves.

Physical Telegram / IEC-61158-2 Manchester Code

Manchester coded means, that a binary “0” (Low, False) is represented by an edge
change from “0” to “1” and a binary “1” (High, True) by a change from “1” to “0”.
(in opposite to RS 485 with the method NRZ).
These continuous edge changes enable the receiver to constant synchronization and
provide the intrinsic feed current (direct current average value) for the devices.

Chapter 2 - 15
T316-02 Fundamentals - DRAFT.doc

2.3.6.3 Transfer Rates / Cable Lengths

PROFIBUS DP
When selecting transfer rates for a DP line you should take into consideration that the
usual distances of 500 m to 1000 m are only possible by reducing the transfer rates or
using bus amplifiers (Repeater).
The maximum length of the line can be increased by using Repeaters.

Transmission rate / cable length per segment in case of copper cable

For applications in strong electro-magnetic interference fields or at a very long
distance, fiber optical cables can be used.

PROFIBUS PA
PROFIBUS PA uses a fixed, uniform transfer rate of 31.25 kBit/s. (IEC-61158-2). At
this rate, cable lengths per segment of up to:
• 1900 m are possible in non Ex(hazardous) areas
• 1000 m are possible in Ex(hazardous) areas
In practice these max. lengths are reduced considerably by the voltage drop on the line,
the limited feed current and the number of PA transmitters. By selecting a cable with a
larger diameter it will be compensated to a certain extent.
An additional restriction in Ex(hazardous) areas is the limited available supply current,
which is determined by the type of explosion protection selected.

When a PA-Segment is coupled to a DP-Segment with a standard coupler (e.g. SK-1

Chapter 2 - 16
 System 800xA training

from Pepperl&Fuchs with fixed transmission ratio of 3 to 1) the transmission rate in

the DP-Segment has to be set to 93,75 kBit/s.
The coupler LD800 P from ABB or the SK-2 from Pepperl & Fuchs allow all
transmission rates up to 12 000 kBit/s on the DP site.

Chapter 2 - 17
T316-02 Fundamentals - DRAFT.doc

2.3.7 Bus Topologies and Termination

The example shows a PROFIBUS line with 4 segments:

Max. 32 field devices may be connected to a RS485-segment, active or passive.

(DPMaster + DPSlave + Coupler + Repeater + Converter <= 32).
The restriction on the number of subscribers results from the fact, that each subscriber
on the bus weakens the bus signal.
NOTE! The number of subscribers that can be connected to a PA
segment is also limited to 32.

If there are more than 32 subscribers (including the master), a bus repeater must
therefore be used to maintain the viability of the bus signal.
The number of cascaded repeaters depends on the vendors’ recommendation (up to 9)

The bus lines that are separated by bus repeaters are called segments. Each individual
segment must again be terminated on both sides by a resistor network.

PROFIBUS DP
For transmission rates ≤ 1.5 Mbit/s stub lines of max. 0.3 m are possible (but not
recommendable), above 1.5 M Bit/s, stub lines not allowed.
In this case the incoming and outgoing cable must be switched through in the
connector.

PROFIBUS PA
In contrast to the PROFIBUS DP, the physical features of the PROFIBUS PA bus also
allow network topologies with long stub lines, such as tree structures.
The tree structure is comparable with the traditional field installation technique.
Signals from the field devices are collected via stub lines in sub-distributors (Multi
Barriers) and are the connected to the main PA cable in parallel.

Chapter 2 - 18
 System 800xA training

2.3.7.1 Address Range

Up to 126 DP or PA field devices can be addressed (address 0..125) by PROFIBUS DP
connected to a PLC / DCS.
Address range for Masters and Slaves:
• 0 … 125 for cyclic communication
• 126 default address for a new device
• 127 broadcast address (multicast, sync and freeze, time sync. etc.)

In real applications you will usually find about 40...60 slaves on one line.

2.3.7.2 Termination
To avoid reflections, the line structure must be terminated by a bus termination resistor
network at either end.

PROFIBUS DP
This network must be provided with a ground-free voltage of 5 volts. Often the
required bus termination is already integrated into the device so that it can be inserted
into the circuit easily if the device is located at the beginning or end of the line
structure. According to the rules of certification, a DP device must be able to provide
this voltage at a minimum of 5 V.

Active Termination Network (principle)

In this manner it is possible to ensure that communication with subscribers

downstream is properly maintained if the device is replaced.

Chapter 2 - 19
T316-02 Fundamentals - DRAFT.doc

Subscribers should preferably be connected to the bus via 9- pin D-sub connectors.

Termination in the 9- pin D-sub connector

If there is no traffic on the bus, the correct terminations will perform an idle potential
of about 1 Volt between B and A.
You can check cabling and termination with a multimeter between pin 3 (B,+) and pin8
(A,-), if the PROFIBUS DP connector has a test socket.

PROFIBUS PA
A passive line terminator (RC) must be provided at both ends of the main PA cable
for all topologies.

Chapter 2 - 20
 System 800xA training

2.3.8 Master / Slave

There are mono-master and multi-master systems. With a mono master system you will
get the fastest transfer rate.
Masters detect themselves on the bus. Only the master who has the token can
communicate with the slaves, afterwards he turns over the token to the next master.
The master communicates by using the master-slave mechanism, which means that
only after a request from the master the slave has to respond. Every slave has the same
priority.

Token Passing

Master-Slave
PROFIBUS-DP
input data
output data

DP V0

DP V1

The master supervises the response time and also the slave, who has to react, if master
request fails. There is cyclic communication ( PROFIBUS-DP V0) and acyclic
communication (PROFIBUS-DP V1).
The use of cyclic communication is to write and read the output and the input data of
a field device (slave). The slave gets the output data from the master with the request
telegram and sends the input data to the master with the response telegram.
To read or write some parameters from or to a slave it is not necessary to use the cyclic
data transfer. The acyclic traffic uses specific SAP’s (Service Access Points), a data
channel which is only open for a short time. The acyclic data transfer is superposed on
the cyclic data transfer.

Chapter 2 - 21
T316-02 Fundamentals - DRAFT.doc

The main task of a PROFIBUS-System is to update the slave data with the data in the
masters process image cyclically.

Every telegram is recognized by each subscriber, checked and if the address matches, it
will be accepted from the addressed device.
The class 1 master supervises the data exchange with his slaves. Every slave is
retriggering with each received valid telegram based on the monitoring time of its
watchdog.

NOTE! After a reset or voltage failure the master tries to get in

contact with all slaves.

Chapter 2 - 22
 System 800xA training

2.3.8.1 State Machine in the Slave

The master gets the information about slave parameter and configuration data from the
GSD file, which is delivered with the slave. It has to be imported into the engineering
tool of the PLC/DCS before starting the configuration.
To establish the cyclic data exchange, the slave has to receive (after being connected to
the bus, power on and internal startup) a parameter and a configuration telegram
from the master.

This is initialized by the master and supported from the state machine in the slave
interface module (within PROFIBUS DP a slave interface module -SIM- denominates
a bus connector and a complete PROFIBUS stack).
In minimum, the parameter telegram contains PNO defined information as e.g.
identification number, sync and freeze, watchdog time, supported transfer rates, master
address and so on. Additional user specific parameters are possible.
The configuration telegram defines the number of input and output bytes. The master
informs the slave, how many I/O bytes have to be exchanged in every transfer cycle.

Chapter 2 - 23
T316-02 Fundamentals - DRAFT.doc

2.4 Basics - HART Communication

2.4.1 Open Standard

The HART communication protocol is an open standard owned by the more than 100
member companies in the HCF (HCF = HART Communication Foundation).

H
Highway
ighway
A
Addressable
ddressable
R
Remote
emote
Primary T
Transducer
ransducer
Master

Master
Master

Secondary
Master

4-20mA Slave
Slave

Value
Value ++ Communication
Communication

The communication is based on a superimposed oscillation to the 4-20 mA signal.

The 4-20 mA analog signal is not affected by the HART signal and can be used for
process control in the normal way. The HART communication digital signal gives
access to secondary variables and other data that can be used for operations,
commissioning, maintenance, and diagnostic purposes.

Master-Slave Communication
Two masters can be connected to each HART loop.
Generally the primary master is a distributed control system (DCS), a programmable
logic controller (PLC), or a personal computer (PC). The secondary master can be a
handheld terminal or another PC.
Slave devices include transmitters, actuators, and controllers that respond to commands
from the primary or secondary master.

Chapter 2 - 24
 System 800xA training

Frequency Shift Keying

The HART communication protocol is based on the Bell 202 telephone communication
standard and operates using the frequency shift keying (FSK) principle. The digital
signal is made up of two frequencies - 1,200 Hz and 2,200 Hz - representing bits 1 and
0, respectively.

Point-to-Point Mode
In point-to-point mode, the traditional 4-20 mA signal is used to communicate one
process variable, while additional process variables, configuration parameters, and
other device data are transferred digitally using the HART protocol.

Multi-Drop-Mode
The multidrop mode of operation requires only a single pair of wires and, if applicable,
safety barriers and an auxiliary power supply for up to 15 field devices.
All process values are transmitted digitally.
In multidrop mode, all field device polling addresses are >0, and the current through
each device is fixed to a minimum value (typically 4 mA).

2.4.2 HART Commands

The HART command set provides uniform and consistent communication for all field
devices. The command set includes three classes:
UNIVERSAL Commands
All devices using the HART protocol must recognize and support the universal
commands. Universal commands provide access to information useful in normal
operations (e.g., read primary variable and units).

COMMON PRACTICE Commands

Common practice commands provide functions implemented by many, but not
necessarily all, HART communication devices.

DEVICE SPECIFIC Commands

Device-specific commands represent functions that are unique to each field device.
These commands access setup and calibration information, as well as information
about the construction of the device. Information on device-specific commands is
available from device manufacturers.

Chapter 2 - 25
T316-02 Fundamentals - DRAFT.doc

2.4.3 Communication within the System

Each HART device has a 38-bit address that consists of the manufacturer ID code,
device type code, and device-unique identifier. A unique address is encoded in each
device at the time of manufacture.

Analog Input / Analog Output

Modules

TCP/IP
CEX-Bus ModuleBus
PROFIBUS DP

HART Com.0

Manufacturer ID
Device Type Code
Device Unique ID

Command 0, Read Unique Identifier

Command 0 is the preferred method to establish the communication with a slave
device because it enables a master to learn the address of each slave device without
user interaction. Each polling address (0–15) is probed to learn the unique address for
each device.

Chapter 2 - 26
 System 800xA training

2.5 FDT/DTM Technology

With the proliferation of intelligent field devices with digital interfaces such as HART
and PROFIBUS, there is a requirement for configuration tools using these protocols.
It is desirable for this configuration tool to have a rich graphic user interface whilst
provide access to devices from multiple manufacturers.

2.5.1 Principle
Similar to the driver software for a printer, a DTM (Device Type Manager) belongs to
a field device. The DTM corresponds to the FDT interface, uses for example the
ActiveX or COM/DCOM technology that has been introduced by Microsoft and is
totally multimedia capable.

The goal is not a new device description language, but rather a device-independent interface.
This allows for the integration of a device-specific software component (DTM) into each
engineering tool.

Chapter 2 - 27
T316-02 Fundamentals - DRAFT.doc

2.5.2 Device Type Manager (DTM)

The actual field device manufacturer makes the DTM available, since only the
manufacturer knows the details of the device that go beyond the profile. A DTM might
include all device parameter, user dialogs and plausibility checking for parameters.

The DTM includes the complete configuration software for the cyclic and acyclic
operation and thus replace for PROFIBUS the GSD file and for HART the DDs.

A DTM is a device-specific software component with a graphical user interface for

PROFIBUS or HART devices.

Example: DTM for the MV 2000 Multivariable Transmitter

Thus same DTM can be used in standalone tools like SMART Vision or in the
PLC/DCS system.
It is only necessary to learn to use the device with DTM once, because it is 100 %
identical in every engineering environment.
This helps to reduce costs in administering and handling devices, tasks that often
significantly exceed the investment costs for the devices themselves.

Chapter 2 - 28
 System 800xA training

2.5.3 Field Device Tool (FDT)

The Field Device Tool is the interface between a frame application and the DTM’s.

FDT is delivered with the software of the frame application like System 800xA:
• is an open, vendor independent interface for control systems
• enables advanced diagnosis functionality
• provides user friendly graphical user interface

Scope of FDT Frame Application

DTM Applications
Diagnosis Persistent
Parameters Client Storage
Project
Applications Data

CallBack
Storage
DTM
Communication

Communication
Communication

Field Devices

Chapter 2 - 29
T316-02 Fundamentals - DRAFT.doc

2.5.4 Nested Communication using FDT/DTM

The basic idea is that each component wraps the communication frame of the
component below, without knowing the contents.

To
Tothe
thenetwork
network
Sys
Sys DP
DP HART-
HART-Frame
Frame DP
DP Sys
Sys

DCS
DCSCommunication
Communication
Component
Component
DP
DP HART-
HART-Frame
Frame DP
DP

Remote
RemoteI/O
I/OCommunication
Communication
Component
Component
HART-
HART-Frame
Frame

HART
HARTDTM
DTM
Remote I/O
Remote I/O
Profibus-HART
Profibus-HART
Gateway
Gateway
HART

Routing through system topology

• A DTM does not have any knowledge about the network topology
• A DTM must only support its own communication protocol
• Communication/routing through ANY network topology, no limitations
• Communication/routing is possible even if the underlying protocol is unknown by
the engineering or standalone tool

To achieve that, the environment has to support „tunneling“.

Chapter 2 - 30
 System 800xA training

2.6 Technical Summary

2.6.1 Technical Summary HART

Digital Process Variable Values
- Primary variable with engineering units
- Secondary Process variables with engineering units
- Loop current (milliamps)
- Percent range

Status and Diagnostic

- Device malfunction
- Primary variable out of limits
- Secondary variable out of limits
- Loop current fixed or saturated
- Configuration changed
- Loop test (forces loop current)

Device Identification
- Instrument Tag and descriptor manufacturer
- Device type and revision
- Final assembly number
- Sensor serial number
- Calibration Information

Data
- Range Units
- Upper and lower range values
- Upper and lower sensor limits
- Sensor min span
- Damping
- Message

Communication Signals
- Traditional analog 4-20mA
- Digital FSK, based on the BELL 202 telephone communication standard
- Logical “0” frequency 2,200Hz
- Logical “1” frequency 1,200Hz

Data Update Rate

- Request/Response Mode 2-3 updates per second
- Optional burst mode 3-4 updates per second

Data Byte Structure

- 1 Start Bit
- 8 Data Bits
- 1 Odd parity Bit
- 1 Stop Bit

Chapter 2 - 31
T316-02 Fundamentals - DRAFT.doc

Data Integrity
- Two dimension error checking
- Status information in every reply message

Command Structure
- Universal, common in all devices
- Common practice, Optional, used by many devices
- Device Specific, for unique product features

Communication Masters
- Two Communication Masters

Variables
- Up to 256 variables per device
- EEE 754 floating point (32 bits) with engineering units

Wiring Topologies
- Point-to-Point, simultaneous analog and digital
- Point-to-Point, digital only
- Multidrop network, digital only (up to 15 devices per line)

Cable lengths
- Max. twisted pair length, 3000 m
- Max. multiple twisted pair, 1500 m
- Cable length depends on the characteristics of individual products/cable

Intrinsically Safe
- With appropriate barrier/isolator

Chapter 2 - 32
 System 800xA training

2.6.2 Technical Summary DTM

The DTM is the functional representation of the device.

with GUI

Applications
peer-to-peer
w/o GUI Communication

Instance device
Information

Applications without GUI

- are defined in the FDT-Specification by the methods available at the DTM‘s
interfaces
- are used by the control system in background processes like downloading of data
- may comprise communication to the device
- may depend on the used communication protocol.

Applications with GUI

- are called for a specific context at the DTM‘s interfaces
- are running asynchronously to the “Frame Application”
- are dependent on the devices capabilities may depend on the used communication
protocol

Instance Information
- is needed to introduce device features to the “Frame Application”
- is necessary for accessing device data within the automation functions
- allows displaying device information in “Frame Applications” without starting a
DTM’s GUI.

Cyclic I/O data

- location of signals in PROFIBUS data frames
- data types
- association of status signals

Chapter 2 - 33
T316-02 Fundamentals - DRAFT.doc

Acyclic Device Data

- addresses or command number for data access
- Profibus: DPV1 slot/index information
- HART: Command number
- description of meaning and use

Fieldbus Configuration Data

- length and structure of data frames
- bus communication parameters

Public Parameters
- units
- ranges

Diagnosis Data
- status information for a device or single channels
- mapping between error codes and textual information

Alarm/Events
- alarm types
- alarm limits

Communication
- Logical peer to peer communication link to the device
- Asynchronous method calls for communication; use of call-back mechanisms
- Communication oriented to device channels
- Several gateways for different protocols
- Channels may have their own GUI to configure the gateway
- Protocol-specific information interchange via protocol-specific XML documents

XML
- EXtended Mark-up Language
- XML is a method for putting structured data in a text format
- Standardized by the World Wide Web Consortium (W3C)
- XML provides an extendable standard for data exchange
- XML is used for the data transfer only
- XML is not meant to describe a device model
- XML is meant to provide access to data that is stored in a proprietary format
- Fieldbus independent interfaces, but fieldbus specific tags
- XML is a format that makes it possible to connect DTMs with the rest of the world

Chapter 2 - 34
 System 800xA training

Exercise 2.1 PROFIBUS/HART Fundamentals

2.1.1 Goals
Describe some principles of the Fieldbus communication using PROFIBUS/HART,
independent of the implementation with System 800xA.

2.1.2 Legend
<> Indicates a key name.
| Indicates when you go from one menu to a sub-menu.
Bold Indicates a menu name or an option in a menu, or file structures
“ “ Indicates dialog box buttons, tabs, instructions etc.

) Indicates start/explanation of student activity

Exercise 2.1 - 1
T316-02 Exercise 2.1 - DRAFT.doc

2.1.3 Exercise Steps

) Describe the cyclic communication between PRODIBUS Master and Slave?

…………………………………………………………………………………………
…………………………………………………………………………………………
…………………………………………………………………………………………

) What does the abbreviation HART mean and how does it works?
…………………………………………………………………………………………
…………………………………………………………………………………………
…………………………………………………………………………………………

) What is the meaning of “Nested Communication”?

…………………………………………………………………………………………
…………………………………………………………………………………………
…………………………………………………………………………………………

) Is it possible to run a DTM independently?

…………………………………………………………………………………………
…………………………………………………………………………………………
…………………………………………………………………………………………

) What is the purpose of the Frame application?

…………………………………………………………………………………………
…………………………………………………………………………………………
…………………………………………………………………………………………

Exercise 2.1 - 2