Field Bus Etc Notes

Download as docx, pdf, or txt
Download as docx, pdf, or txt
You are on page 1of 12

Field bus standardisation Smart transmitters- transmission modes, profibus,

international field bus standards-

What is a Fieldbus ?
Fieldbus is a digital two-way multidrop communication link between intelligent field
devices. It is a local area network dedicated to industrial automation. It replaces
centralized control networks with distributed control networks and links the isolated
field devices such as smart sensors/ transducers/actuators/controllers.

Foundation Fieldbus H1 and PROFIBUS-PA are the two fieldbus technologies used in
process control. In this two-way communication, it is possible to read data from the
smart sensor and also write data into it. The multidrop communication facility in
fieldbus results in enormous cable savings and resultant cost reduction.

A fieldbus device must have a fieldbus interface unit for proper communication to
take place, and is shown in Figure.

A conventional 4–20 mA current transmission system has two wires each for each of
the individual field devices employed.Compared with this, a fieldbus system has two
wires running for many devices that belong to the same segment. A segment may
consist of 32 devices.
Fig : Fieldbus interface unit in a fieldbus transmitter

In 1985, industry experts in the field sat together to work out a vendor independent
fieldbus standard—i.e., it would be interoperable. The bus standard would provide bus
power, intrinsic safety, and the ability to communicate long distances over existing
wires—the basic requirements for a process plant automation system.

There are many types of fieldbuses in use today; the particular type to be used
depends on the type of industry—discrete or manufacturing automation. Different
types of fieldbuses include: Foundation Fieldbus, PROFIBUS, DeviceNet,
ControlNet, InterBus, HART, AS-i, MODBUS, CAN Bus, Ethernet, LonWorks, and
WorldFIP.

(smart) HART
Communication Protocol
Overview
HART is a digital signal that rides on a standard 4 mA … 20 mA process control loop.
In the field of process automation, the 4 mA … 20 mA loop is very steady. You may
hear of it being referred to as “quasi-static,” as it doesn’t change much. Field devices
like mass flow, temperature, pressure transmitters, or valve positioners use this 4 mA
… 20 mA signal. HART information is extra information that you get back from your
field instruments.

Historically, HART communication uses the BELL 202 telephone communication


standard, which telephone land lines still use today. This standard was introduced in
the early 1980s and uses Frequency Shift Keying (FSK) technology. FSK simply
means that the information is keyed or coded into the frequency, which is how the
data communicates back and forth. HART layers its digital communication signals on
top of the 4 mA … 20 mA control signal.

HART is limited to 1200 bits/second and ranges from 1200 Hz to 2200 Hz.
Information (1, 0) is represented by different frequencies. The HART signal creates 0s
and 1s. A logic 1 is represented by 1200 Hz. A logic 0 is represented by 2200 Hz. On
the plus side, HART communication doesn’t interrupt the 4 mA … 20 mA signal, and
it allows a host application (master) to get up to three digital updates per second from
a field device.

Also, the HART information is easily extracted without interfering with the 4 mA …
20 mA signal used by the host system. Host systems are most commonly a distributed
control system (DCS), programmable logic controller (PLC), asset management
system, safety system, or a handheld device. HART enables two-way field
communication to take place and makes it possible for additional information beyond
the normal process variable to be communicated to or from a smart field instrument.

HART – Highway Addressable Remote Transducer Protocol

is an early implementation of Fieldbus, a digital industrial automation protocol. Its


most notable advantage is that it can communicate over legacy 4-20 mA analog
instrumentation wiring, sharing the pair of wires used by the older system.

1. Regardless of the age or capability of your control, safety or asset management


system, HART technology can provide additional information to help extend
time between shutdowns, lower maintenance cost and improve process
performance.
2. The two most common tools used to temporarily connect to a HART-enabled
device are: a handheld communicator or a PC running a configuration software
application and connected via an external modem.
3. A handheld communicator or a properly equipped PC can be connected at any
point on the loop to access HART Communication data – eliminating the need to
be located at or connected to the terminals on the specific device.

4. In order to access all of the intelligent information in a specific device, the


handheld communicator or the PC-based software application need to contain the
current device description (DD) that matches the model and revision level of
your device.
5. There are 35-40 standard data items in every registered HART device that can be
accessed without using the DD.
6. Once a device has been configured, the configuration can be saved to facilitate
device replacement or maintenance / regulatory record keeping.
7. HART technology can be used on a Point-to-Point basis – monitoring the
information from a single device – or on a Multipoint basis – simultaneously
monitoring the information from many devices.
8. The information from intelligent HART-enabled devices can be monitored for
device status alerts on a temporary basis (daily scan of all devices on the
network) or can be monitored full-time and the information integrated into the
control or monitoring system.
9. The translation of the digital HART Protocol signal can be done by an external
(or stand alone) device or can be done using a HART-enabled I/O system that
allows the termination of the 4-20mA signal to an I/O card. (The Primary
Variable is converted to a digital signal and the HART data is translated into
digital information, which can be used by the system.)
10. The actual conversion or translation of HART Protocol information can be done
in the field – close to the HART-enabled device – or in the control or relay room.
11. Many products and tools are available to retrofit existing systems to access
HART data. With these tools, you can easily replace wire termination boards (in
some cases pin-for-pin replacements), which allows the 4-20mA signal to be
passed into the control system – unchanged. The HART data is passed to the
HART-enabled asset management system.
12. Since HART data is read using a modem, it is important to know the ratio of
modems to input signals in the HART-enabled I/O. This item is one of the main
factors used to determine the scan rate of each signal connected to the I/O card.
13. Gateways are used to convert HART Protocol information to other standardized
protocols such as HART to Modbus, PROFIBUS, Ethernet, TCP/IP, etc.
14. HART multiplexers can be used as the primary I/O front end for a HART-based
control or monitoring system
15. Not all suppliers implement HART Protocol the same way. It is important to
understand how your suppliers implement this enabling technology so that you
will be better able to predict performance and results.
16. Gaining access and using HART data can be done one loop at a time. Migrating
to larger applications will provide full-time monitoring of more devices,
therefore increasing the benefit. This scalability offers the User the ability to
determine the size and scope of the use of valuable HART Protocol information.
Notes-
 HART technology enables two-way digital communication to occur between
intelligent devices and connected host or control systems.
 That HART is an enabling technology meaning that it can be applied in many
different application including control, monitoring, safety, asset management,
etc.
 HART provides two simultaneous communication channels: the 4-20mA analog
signal and a digital signal.
 The digital signal contains information from the device including device status,
diagnostics, additional measured or calculated values, etc.
 The 4-20mA signal communicates the primary measured value (in the case of a
field instrument) using the 4-20mA current loop.
 The digital communication part of the communication is a request-response
communication protocol, which means that during normal operation, each device
communication is initiated by a request from a host device.
 The digital signal is made up of two frequencies – 1,200 Hz and 2,200 Hz
representing bits 1 and 0. Sine waves of these two frequencies are superimposed
on the direct current (dc) analog signal wire to provide simultaneous analog and
digital communications.
 A minimum loop impedance of 230 ohms is required for communication.
 HART devices can operate in one of two network configurations-point-to-point
or multidrop.
 The HART Command Set includes three classes: universal, common practice,
and device specific.
 There are 35-40 data items that are standard in every HART registered device.
Host applications may implement any of the necessary commands for a particular
application.
 The HART device suppliers provide a DD file for each HART device and the DD
file combines all of the information needed by the host application into a single
structured file.
 The DD file includes all of the information needed by a host application to fully
communicate with the field device and access all of the information available
from the device.
 The new HART enhanced Device Description Language extends the capabilities
of DDL to provide for advanced visualization of intelligent device information.
 HART Protocol is backward compatible with the installed base of
instrumentation and control systems in use today. A new HART-enabled device
can replace an existing 4-20mA analog-only device of similar measurement
capability without change to the host system or wire.
 Most HART devices provide multiple process variables, which can be used for
monitoring or control to gain a better insight into the process.
 Device diagnostics and status information are returned with every
communication message.
 The installation practice for a HART communicating device is similar for a
conventional 4-20mA instrument.
 HART communicating devices can be used in applications that require IS
operation.

transmission modes
Profibus
PROFIBUS (Process Field Bus) is a standard for fieldbus communication in automation technology and was
first promoted in 1989 by BMBF (German department of education and research) and then used by Siemens. It
should not be confused with the PROFINET standard for Industrial Ethernet. PROFIBUS is openly published
as part of IEC 61158.

There are two variations of PROFIBUS in use today; the most commonly used PROFIBUS DP, and the lesser
used, application specific, PROFIBUS PA:

 PROFIBUS DP (Decentralised Peripherals) is used to operate sensors and actuators via a centralised
controller in production (factory) automation applications. The many standard diagnostic options, in
particular, are focused on here.
 PROFIBUS PA (Process Automation) is used to monitor measuring equipment via a process control
system in process automation applications. This variant is designed for use in explosion/hazardous areas
(Ex-zone 0 and 1). The Physical Layer (i.e. the cable) conforms to IEC 61158-2, which allows power to be
delivered over the bus to field instruments, while limiting current flows so that explosive conditions are
not created, even if a malfunction occurs. The number of devices attached to a PA segment is limited by
this feature. PA has a data transmission rate of 31.25 kbit/s. However, PA uses the same protocol as DP,
and can be linked to a DP network using a coupler device. The much faster DP acts as a backbone network
for transmitting process signals to the controller. This means that DP and PA can work tightly together,
especially in hybrid applications where process and factory automation networks operate side by side.
In excess of 30 million PROFIBUS nodes were installed by the end of 2009. 5 million of these are in the
process industries.

Technology
PROFIBUS Protocol (OSI reference model)

OSI-Layer PROFIBUS

7 Application DPV0 DPV1 DPV2

6 Presentation

5 Session
--
4 Transport Management

3 Network

2 Data Link FDL

1 Physical EIA-485 Optical MBP

Application layer (OSI-Layer 7)[edit]


To use these functions, various service levels of the DP protocol were defined:
 DP-V0 for cyclic exchange of data and diagnosis
 DP-V1 for acyclic data exchange and alarm handling
 DP-V2 for isochronous mode and data exchange broadcast (slave-to-slave communication)
Security layer (OSI-Layer 2)[edit]
The security layer FDL (Field bus Data Link) works with a hybrid access method that combines token
passing with a master-slave method. In a PROFIBUS DP network, the controllers or process control systems
are the masters and the sensors and actuators are the slaves.
Each byte is secured with an even parity and transferred asynchronously with a start and stop bit. There may
not be a pause between a stop bit and the following start bit when the bytes of a telegram are transmitted. The
master signals the start of a new telegram with a SYN pause of at least 33 bits (logical "1" = bus idle).
Various telegram types are used. They can be differentiated by their start delimiter (SD):

SD1 = 0x10

SD1 DA SA FC FCS ED

Variable length data[edit]


SD2 = 0x68

SD2 LE LEr SD2 DA SA FC DSAP SSAP PDU FCS ED

Fixed length data[edit]


SD3 = 0xA2

SD3 DA SA FC PDU FCS ED

Token[edit]
SD4 = 0xDC

SD4 DA SA

Fields[edit]

SD Start Delimiter

LE Length of protocol data unit, (incl. DA,SA,FC,DSAP,SSAP)

LEr Repetition of length of protocol data unit, (Hamming distance = 4)


FC Function Code

DA Destination Address

SA Source Address

DSAP Destination Service Access Point

SSAP Source Service Access Point

PDU Protocol Data Unit (protocol data)

Frame Checking Sequence, calculated by simply adding up the bytes within the specified length. An
FCS
overflow is ignored here.

ED End Delimiter (= 0x16)

Fieldbus Standards

The FOUNDATION protocol is designed to be compatible with the officially sanctioned SP50
standards project of the ISA, as well as and the specifications of the International
Electrotechnical Committee (IEC). Since its founding, the Fieldbus Foundation has made
compliance with the ISA/IEC standards a priority.

The IEC voted to include the FOUNDATION HI and HSE specifications in the IEC
61158 international standard. The CENELEC Technical Bureau added the
FOUNDATION H1 specifications to EN 50170 Euronorm. In addition,
FOUNDATION technology is the only implementation of the ANSI/ISA-50.02
standard.

The FOUNDATION specifications are also compliant with IEC 61804 (Function Blocks for Process
Control and Electronic Device Description Language) and IEC 61508 (Functional Safety of
Electrical/Electronic/ Programmable Electronic Safety-related Systems).

Both NAMUR (Germany) and JEMIMA (Japan) have voiced support for
FOUNDATION technology, and provided input from the end user community that aided in
specification development.

Approval and support by key international industry bodies gave users the confidence that their
investments in FOUNDATION-registered solutions were based on recognized global standards and
sound best practices from industry groups.

The FOUNDATION Technical specifications is based on the ISO/OSI layered communications


model, and consists of three major functional components: the Physical Layer, the
communication "stack," and the User Layer.

The Physical Layer corresponds to OSI Layer 1, which receives encoded messages from the
upper layers and converts the messages to physical signals on the fieldbus transmission medium
and vice-versa.

The communication "stack" corresponds to Layers 2 and 7 in the OSI model. Layer 7, the
Application Layer (AL), encodes and decodes User Layer commands. Layer 2, the Data Link
Layer (DLL), controls transmission of messages onto the fieldbus through Layer 1. The DLL
also manages access to the fieldbus through a deterministic, centralized bus scheduler called the
Link Active Scheduler (LAS). The LAS is used for scheduling transmissions of deterministic
messages and authorizing the exchange of data between devices. The fieldbus does not use the
OSI Layers 3, 4, 5 and 6.

You might also like