HART Out of Value
HART Out of Value
发布日期: 2016 年 10 月 2 日
Jonas Berge 关注
Author, award-winning speaker, digital…
发布日期: 2016 年 10 月 2 日
The HART technology has many potential benefits but in most plants and for most
devices the smart features go unused. Plants struggle to put HART technology to
good use. This is a case of technology “Consumption Gap”. Often the original
intention of the project team was to use HART for continuous online device
diagnostics for predictive maintenance, monitor the auxiliary variables, as well as
for download and configuration management etc. Smart devices with diagnostics,
some multivariable devices, control system with smart I/O cards supporting HART,
even Intelligent Device Management (IDM) software part of an Asset
Management System (AMS) were specified. Yet, in most plants, for various reasons,
HART technology doesn't get utilized other than for commissioning with the
handheld field communicator - the control system only uses the real-time 4-20 mA
signal.284Sometimes
· 46 条评论 device commissioning is even done from the local display or
through USB. How can we close this consumption
评 gap to fully utilize the smart
features in all smart赞 devices? Here are my personal
论 thoughts: 分享
Figure 1 The Consumption Gap (from B4B: How Technology and Big Data Are
Reinventing the Customer-Supplier Relationship)
Many speak of HART and 4-20 mA interchangeably, saying HART when they really
mean 4-20 mA, but they’re not the same. They don’t realize digital HART is not the
same as analog 4-20 mA, so HART does not get designed and procured correctly,
not installed and commissioned correctly, not integrated and setup properly, not
maintained properly, and people don’t get trained. As a result the plant ends up
using only handhelds or laptop, missing out on the smart online capabilities.
To get value of HART there are a few things you’ve got to do to “Get Connected”,
to close the consumption gap. Here’s some simple HART engineering guidance to
make certain the digital communication works with the control system, multiplexer,
IDM software, and smart signal conditioners etc. If you are only going to use HART
with a handheld in the workshop you need not consider these pointers, but then
again, why limit yourself?
Figure 3 Calculate the loop voltage drop to ensure the power supply is
sufficient for the device, accessories, and cable
If a device will be replaced with a new model having higher voltage drop, or an
accessory is added in series such as an indicator, signal conditioner, wireless
adapter, or HART output filter, first calculate to make sure the voltage is sufficient.
Figure 5 Maximum cable distance for single device 5 nF, 250 ohm shunt resistor
The chart also makes it clear that by using low capacitance (PE insulation) cable
with large conductor cross section, additional distance limitations are not imposed.
A full 1.5 km is possible. However, if high capacitance (PVC insulation) cable with
small conductor cross is used the distance will be limited. Many plants don’t permit
conductor size smaller than 0.75 mm2 (#18 AWG) anyway. PE insulation cable with
mutual capacitance of 60 nF/km is available from many vendors.
Additional cable requirements may apply depending on the hazardous area
classification and local regulations etc.
284 · 46 条评论
Example: Single device,赞
5 nF device capacitance,
评 250 ohm shunt resistor
分享
论
Cable Capacitance: 180 nF/km
Conductor Resistance: 49 ohm/km (22 AWG)
From the 65 microsecond-rule chart, at conductor resistance of 49 ohm/km along
x-axis, and up to cable capacitance of 180 nF/km (between the 164 and 230 lines),
the maximum length on the y-axis is approximately 1 km. If there is higher loop
resistance or capacitance due to additional components in the loop, the distance
will be shorter.
Safety barriers
Intrinsic safety barriers have to be HART compatible passing communication
through the barrier between safe side to hazardous area in both directions without
attenuating the HART signal. Make sure to specify barriers for 4-20 mA input and
4-20 mA output must be able to pass through HART communication and “shall be
compliant to the HCF_SPEC-054 specification”
All intrinsic safety rules apply. They are not covered here.
Cabling route planning
4-20 mA/HART signal wiring must be kept separate from power cables. This must
be taken into account in the design stage when planning the cable tray and
conduit layout and cable routing. 4-20 mA/HART signal wiring is routed together
with other signal wiring including fieldbus and other data communication. If signal
wiring has to cross power cables, they should only do so at a right angle. Make sure
to document the cable routing to ensure it gets done at the time of installation.
Shield connection
The cable shield must be maintained all the way from the field device to the control
system I/O card. That is, the shield of the spur from the device to the junction box
must be joined to the shield for the trunk from the junction box through the
marshalling cabinet all the way to the I/O card. Note that the shield shall not be
connected to the device housing when a single point grounding scheme is used.
This is the recommendation in the HCF_SPEC-054 specification. Make sure to
include the shield connection in all wiring diagrams and loop diagrams to ensure it
gets done at the time of installation. This is the same as fieldbus and other digital
communication.
284 · 46 条评论
Housing grounding
赞 评 分享
论
The device housing shall be connected to ground through a large cross-section
conductor. Without it the EMI/RFI protection will not work. Make sure to include the
device housing ground connection in all wiring diagrams and loop diagrams to
ensure it gets done at the time of installation. This is the same as for fieldbus and
other digital communication.
Shield grounding
The shield shall be grounded at the DCS I/O card. Note that the shield shall not be
connected to the device housing when a single point grounding scheme is used.
This is the recommendation in the HCF_SPEC-054 specification. Make sure to
include the shield ground connection in all wiring diagrams and loop diagrams to
ensure it gets done at the time of installation. This is the same as for fieldbus and
other digital communication.
Input filters
If you are installing a new system using 4-20 mA, specify analog input cards
supporting HART pass-through and compliant to HCF_SPEC-054 as well as having
internal low-pass filters to ensure the analog reading is not disturbed by HART
communication.
Some systems do not have low-pass filters internally on their inputs and therefore
require external HART input filters to be added to make sure the reading will not be
disturbed when a HART multiplexer, handheld field communicator, or laptop with
HART interface is connected.
Conflicts
284 may occur when smart signal conditioners are used because there may be
· 46 条评论
a need for three masters: DCS I/O cards, smart
评 signal conditioner, and handheld
field communicator.赞For instance, if the DCS论has HART enabled I/O分享 cards (primary
master) the smart signal conditioner must be configured as secondary master to
avoid conflicts, but this would in turn prevent the use of a handheld field
communicator (secondary master). The same applies if a HART multiplexer is the
primary master or a laptop with interface is the secondary master. Smart signal
conditioners are usually not used when a DCS or multiplexer is used as a primary
master with continuous polling.
A smart signal conditioner will not be receiving any PV if there is a conflict with
another master For instance, a HART to analog converter will set the analog output
to an failure alarm output (< 4 mA or > 20 mA) causing “Bad PV” in the receiving
input card, and shutdown of the control loop. Therefore, particular attention should
be given to the master class configuration when smart signal conditioners are used.
Burst communication
Do not use burst communication for devices connected to a control system or
multiplexer because the burst communication will cause diagnostics and auxiliary
variable monitoring etc. to slow down. Burst communication may also cause many
communication error alarms in the IDM software.
Unpolled address
Use a HART version 7 (HART7) host to ensure all devices are detected. Version 5 of
HART (HART5) only permitted address up to 15. Therefore older system software
and handheld field communicators do not support polling of addresses up to 63,
and will therefore not be able to detect newer devices such as wireless adapters
which use default addresses above 15.
Integration Planning
Some of the mistakes in integration planning that prevent HART from being put to
good use include:
Devices not supporting command 48
DD files not provided with devices
HART7 devices not supported
Polling too slow
Command
284 ·48
46 条评论
赞 评 分享
论
For devices not supporting the standard HART command 48 it is not possible for
the IDM software alarm management function to intelligently filter the instrument
diagnostic alarms from the devices. Therefore it is important devices support
command 48. Many HART5 devices do support command 48, but it was not
mandatory so not all HART5 devices support it. Command 48 was made mandatory
in HART7. HART5 devices have the same diagnostics as HART7 devices, but
without command 48 it is challenging to put the diagnostics to good use. Make
sure to specify devices “shall support command 48”.
Note: HART5 systems don’t support HART7 devices, so only specify HART7 devices
if you have a HART7 compatible system.
DD files
You can get the 4-20 mA signal without a DD file but you cannot configure the
device from IDM software without a DD file, for example temperature sensor type
and many other settings in a device that may be required to get a correct
measurement. Not all devices come with a DD file. These devices may have to be
configured form a local display or by proprietary software. Make sure to specify
devices “shall be provided with DD files”.
HART7
HART5 systems cannot support HART7 devices
Some devices can be configured to operate as HART5 or HART7 – essentially two
different devices so have two DD files.
Note: HART5 systems don’t support HART7 devices, so only specify HART7 devices
if you have a HART7 compatible system.
Polling
Early warning to operators of impending process problems resulting from device
failure requires the instrument diagnostic alarm monitoring to be fast. If the polling
time is set longer than a minute, intermittent problems may be missed and the time
left for operators to respond too short. Therefore set the polling time as short as
possible.
The triggered burst mode and event notification (sometimes referred to as report
by exception) functions are intended for WirelessHART not for 4-20 mA/HART.
284 · 46 条评论
Therefore use polling for 4-20 mA device diagnostics.
赞 评 分享
论
Devices configured for burst communication may interfere with diagnostics polling.
Therefore do not configure devices for burst communication.
Procure Correctly
To get value out of HART, the components must be procured correctly. It is up to
engineering to correctly specify a device, software, and other infrastructure
components, but it is up to procurement to ensure vendors comply with the
specifications. The lowest bidder’s component may not comply and this could
jeopardize the ability to utilize HART capabilities. When HART requirements are not
considered in the procurement, the analog 4-20 mA signal will work but the smart
features cannot be accessed and the benefits not reaped.
Some of the mistakes in procurement that prevent HART from being put to good
use include:
System analog I/O cards not supporting HART pass-through
The 4-20 mA cable not meeting HART requirements
The safety barriers not HART compliant
The field device not HART registered
The field device not provided with DD file
DC power supply not HART compliant
Devices not supporting command 48
HART7 devices not supported in system
Design engineers will specify a system supporting HART pass-through with HART7,
cable, safety barriers, and power supply meeting HCF_SPEC-054 requirements,
devices which are registered, supporting command 48, and come with DD files etc.
At the time of procurement it is important to verify the bids received meet these
requirements. That is, procurement should not specify or accept any old 4-20 mA
system, 4-20 mA cable, 4-20 mA safety barriers, DC power supply, or any HART
device.284 · 46 条评论
http://www.hartcommproduct.com/inventory2/index.php?action=list
评
赞 论 分享
Rather than specifying all the characteristic parameters, impedances, voltage levels,
signal levels, and noise levels etc. for cables, devices, and other components it is
easier to simply specify “shall be compliant to the HCF_SPEC-054 specification”
Integrate Properly
To get value out of HART, devices must be integrated correctly. In many plants they
were not, and as a result HART is underutilized. When HART requirements are not
considered in the system integration, the analog 4-20 mA signal will work but the
smart features cannot be accessed and the benefits not reaped.
Some of the integration mistakes that prevent HART from being put to good use
include:
DD files not loaded on DCS
DD files not loaded on IDM software
DD files not loaded on portable tools
Wrong DD file
Load DD files on DCS
The DCS may also be using DD files. For instance, the DD files may be used when
configuring the filtering of the diagnostics in HART command 48 in order to display
each diagnostics as human readable text (see section on Tailoring the application).
Therefore make sure DD files for all device types and versions are loaded on the
DCS to ensure the device is fully integrated.
Some DCS may not use standard DD, but instead use an internal system specific file
created for each device type and version for device diagnostics alarms
management and other functions. In this case, make sure these files are loaded.
Any internal files should be auto-generated by the system from the DD files when
the DD files are loaded. This is the same as for fieldbus and other digital
communication protocols.
Load DD files on IDM software
The IDM software uses DD (EDDL) files to display all the configuration options and
diagnostics
284 · 46etc.
条评论Without the DD file loaded it is not possible to configure sensor
type and many other settings or perform sensor
评
trim and other functions which
must be done before赞 the 4-20 mA/HART device论 is operational. That分享is, without
loading DD on the software the device cannot be made to work correctly. There will
be a 4-20 mA signal, but it may not be correct until the device is properly
commissioned. Therefore make sure DD files for all device types and versions are
loaded on the IDM software to ensure the device is fully integrated.
Some DCS may not use DD or EDDL, but instead use DTM driver software. In this
case, make sure these programs are installed for all devices and versions. In my
personal opinion FDT/DTM has several drawbacks so the plant is better off using
only EDDL.
Load DD files on portable tools
The portable tools like a handheld field communicator or laptop software for a
HART interface also use DD (EDDL) files to display all the configuration options and
diagnostics etc. Without the DD file loaded it is not possible to configure sensor
type and many other settings or perform sensor trim and other functions which
must be done before the 4-20 mA/HART device is operational. That is, without
loading DD on the portable the device cannot be made to work correctly. There will
be a 4-20 mA signal, but it may not be correct until the device is properly
commissioned. Therefore make sure DD files for all device types and versions are
loaded on the IDM software to ensure the device is fully integrated.
Correct DD file
Some devices are available in HART5 or HART7 version, or can be configured to
operate as either HART5 or HART7 to be compatible with both HART5 and HART7
systems. Depending on if the device is configured to operate as HART5 or HART7 it
will need a different DD file. If the device is configured to operate as HART7 but the
HART5 DD has been loaded, the system cannot access the device features.
Tailor Specifically
To get value out of HART, each device must be configured specifically for its
service, and settings are also required for each tag in the DCS and IDM software,
especially to make use of the diagnostics. In many plants this was not done, and as
a result HART is underutilized.
When instrument diagnostics alarm management is not considered in the setup,
the benefits
284 · 46 of
条评论diagnostics cannot be reaped. HART provides no wiring reduction or
savings. The value from HART is purely from diagnostic monitoring and other
intelligent device management.
赞 It is therefore
评 important to engineer
论 分享the instrument
diagnostic alarm management functionality in the devices and systems to make
sure the diagnostics monitoring works.
Some of the mistakes in configuration that prevent HART from being put to good
use include:
Instrument diagnostic alarm management not engineered and configured
Analog output tight-shutoff configured to 0 mA
Instrument diagnostic alarm management
Many 4-20 mA/HART devices have dozens of different instrument diagnostic
alarms. Simple devices like pressure and temperature transmitters just a few, but
advanced devices like valve positioners and flow meters many more. When
multiplied by hundreds or thousands of devices in a plant there is a potential for
instrument diagnostic alarm flooding unless the instrument diagnostic alarm
management system is engineered properly.
When too many instrument diagnostic alarms are sent to the wrong person
becoming a nuisance, the diagnostics polling will soon be turned off. The plant can
no longer benefit from the potential advantages of device diagnostics.
The ISA108 group is developing standards and technical reports as guidance to
IDM in general and instrument diagnostics alarm management in particular. In the
mean time the “Device Diagnostics Deployment and Adoption Guide” found here
can be used:
http://www.eddl.org/DeviceManagement/Pages/DeviceDiagnostics.aspx
The steps in engineering instrument diagnostics alarms management are detailed
in that guideline and will not be repeated here. This is similar to fieldbus and other
digital communication. The steps are:
Categorize instrument diagnostics alarm severity for each device type
Identify criticality to the process for each device tag
Configure system and devices
FAT to verify correct system configuration for alarm management and reports
284 · 46 条评论
Tuning of device diagnostics to fit the application
评
赞 论 分享
Rewrite maintenance procedures to include the IDM software
Customized training
Do not postpone the instrument diagnostic alarm management engineering and
configuration until after plant startup for the run & maintain team to sort out. They
may not have the same resources as the project team. Work with the EPC
contractor and system vendor to get this engineered and setup before the plant
starts up. It is part of the project responsibility. Indeed the planning portion
including categorization of instrument diagnostics alarm severity and criticality
ranking of devices etc. shall be performed at an early stage of the project after the
CHAZOP such that it can be configured in the system well before device
commissioning.
Not all faults in the device are equally severe. Some diagnostics is predictive or
advisory in nature, meaning the device still functions. Some HART devices may
have standard support for NE107 to categorize the instrument diagnostic alarms
but most don’t because it is a new feature and it is optional. Therefore, make sure
to specify a DCS which is also able to categorize instrument diagnostic alarms for
command 48 internally.
Configure the system to filter the instrument diagnostic alarms for each device. For
each instrument diagnostic alarm in each device there is a bit in HART command
48. Configure the severity for each alarm such as Failed, Maintenance, or Advisory.
This in turn controls how the system routs this instrument diagnostic alarm, for
instance to the operator, or only to the instrument technician. This configuration
work is greatly simplified if the diagnostics for each device is displayed in the DCS
engineering software as human readable text rather than cryptic bit numbers.
Therefore make sure to specify a DCS which uses information from the device DD
file to list the possible instrument diagnostic alarms from the device. If the system
is not directly using the DD files, it can instead auto-generate whatever internal
system files from the DD using some utility. Manually creating such internal system
files or waiting for the system vendor to do it can cause delays. Learn more about
internal system files from appendix 3 in the “Device Revision and Lifecycle
Management Guide” found here:
http://www.eddl.org/DeviceManagement/Pages/DeviceRevisionManagement.as
px 284 · 46 条评论
赞 评 分享
论
Figure 13 Each diagnostic in command 48 can be mapped to a status signal
Some 4-20 mA/HART devices now support NAMUR NE107 status signals
(“Condensed Status”) for instrument diagnostics alarm management. It may be a
good idea to buy devices which support standard commands 523-527 such that
when systems support NAMUR NE107 status signals for 4-20 mA/HART devices in
the future, the installed base of devices already has this functionality. However, not
many such devices are available today so it cannot be made a requirement.
Note that the NE107 implementation for HART doesn’t have priority for each
device. This will have to be supported by the system in a way specific to the system.
It is important to configure the priority appropriately for each device, because all
devices are not equally critical. Some devices are more critical than others and this
must be taken into account in instrument diagnostic alarm management.
Also note that some HART devices have some form of NE107 but the
implementation is not according to the HART “condensed status” standard
commands for NE107 which means it will not integrate with systems using the
standard commands. Therefore, verify if standard commands 523-527 are used in
the device or not.
Analog output tight-shutoff
Don’t configure control system tight-shutoff output current to 0 mA because this
turns off the smart valve positioner and any wireless adapter and other accessories
in the loop preventing diagnostics and HART communication.
The tight-shutoff current setting in the DCS shall be somewhere in the range 3.6-
3.8 mA to ensure the positioner still performs diagnostics and devices plus
accessories are able to communicate.
Test Thoroughly
To get value out of HART, the HART integration must be tested during the system
Factory Acceptance Test (FAT). For many plants it was not, and as a result HART is
underutilized. When HART requirements are not considered in the FAT, the analog
4-20 mA signal will work but the smart features cannot be accessed and the
benefits not reaped.
Some of284the
· 46 条评论
omissions in FAT that prevent HART from working properly include:
赞 评 分享
Device interoperability / integration test not论performed
Instrument diagnostic alarm routing test not performed
Interoperability/integration
During system FAT connect one of each 4-20 mA/HART device type. Open each
device type in the IDM software to make sure the DD file for the type and version of
the device has been loaded and that the device displays correctly. Download a
device configuration to make sure the download is error free. This is similar to what
is done for fieldbus and other digital devices.
Instrument diagnostic alarm routing
For each device type, simulate instrument diagnostic alarms of different severity
such as Advisory, Maintenance, and Failure and make sure they are routed to the
right person such as operators or instrument technicians as defined in the design
stage.
Install Correctly
To get value out of HART it must be installed correctly. It is up to engineering to
correctly design cable routing and grounding schemes etc, but it is up to the
installation contractor to ensure the design is followed. If cables are routed and
grounded differently this could jeopardize the ability to utilize HART capabilities.
The HART signal is small, only 1 mA. If there is noise on the wire due to poor
installation, the diagnostics, secondary (SV), tertiary (TV), and quarternary (QV)
variables will stop coming. There will be no updates to the system and
communication alarms will be generated. A smart signal conditioner may output <
4mA or > 20 mA which may cause a nuisance trip. Such issues will not be noticed
when using a handheld for device configuration and commissioning, but once
continuous monitoring is used it will be evident. Make sure to install properly. In
many plants the installation was not done correctly, and as a result HART is
underutilized. When HART requirements are not considered during installation, the
analog 4-20 mA signal will work but the smart features cannot be accessed and the
benefits not reaped.
Remember, when using a 4-20 mA/HART device with a WirelessHART adapter the
wiring must still meet the HART requirements because HART is still communicated
across the wires, if ever for a very short distance between the device and adapter.
Some of284the mistakes in installation that prevent HART from working properly
· 46 条评论
include: 评
赞 论 分享
Cable shield connected to device
Inadvertent contact between shield and grounded metal objects
Cable shields not maintained in field junction box
Signal cables routed in same tray as power cables
Cable looped too tight damaging shield
Device housing not grounded
Junction box not grounded
Signal cables and power cables coiled together
Shield and conductor insulation damaged
Cable jacket and shield stripped off unnecessarily
Multi-pair cable overall shield not grounded
Cable armor not grounded
The HCF_SPEC-054 specification includes several HART shielding and grounding
recommendations. Since most don’t have this document I have included some of
those rules below complemented with additional pointers. These are the same as
for fieldbus and other digital communication.
Don’t ground shield at device
Do not connect the shield or drain wire to ground in the device housing. Ground
the shield only in a single point, at the power supply. Only connect signal wires at
the device. Isolate the drain wire using shrink tube or tape. This is the
recommendation in the HCF_SPEC-054 specification. Some plants have other
practice.
Insulate shield at device
Do not leave the shield or drain wire “flying” as it may come in contact with the
device housing.
Cut the284shield
· 46 条评论
inside the device housing. Isolate the drain wire and shield using
shrink tube or tape赞to make sure it does not评论come in contact with 分享 grounded metal
parts. For armored cable, make sure shield drain wire is not touching the cable
armor.
Maintain shield in junction boxes
Do not ground the shield in the junction box. Do not leave ‘flying’ shield or drain
wire as it may touch other wires or grounded metal parts.
The shield shall be continuous from system panel, through junction box, up to the
device (but not connected to the device).
If two cables are joined, make sure the junction (splice) also joins the shields of the
two cables.
Route signal cables in separate tray from power cables
Do not lay communications signal cable in the same tray as power cable.
Route signal cable and power cable in separate tray. If signal cable and power cable
is laid in the same tray, maintain maximum possible separation, keeping power
cable and signal cables on separate sides of grounded metal dividing wall.
The plant designer is responsible for designing separate trays for signal cables and
power cables. Installer is responsible for laying cable in the assigned tray.
Don’t loop cable too tight
“Pig tails” are permitted but must have a sufficiently large radius to not damage the
internal shield. Do not loop/bend cable too tight – it can damage the shield
reducing noise immunity. Cable trunking / wire troughs / trays are usually too
narrow to permit looping of the cable. Do not turn corners in cable trays and on
cable ladders too tight.
Observe cable minimum bend radius, which is cable type dependent. For armored
cable it can be space taking. Use proper cable tray bend, cross, and tee pieces to
allow cable to round corners with wide radius.
Ground device housing
Without a ground connection the device EMI/RFI suppression will not work
Make sure the device housing and junction box is safety grounded to the plant
284 · 46 条评论
structural steel with a low impedance connection to ensure personnel safety and
赞 评 分享
论
EMI/RFI suppression. It is particularly important for those devices where surge
protection is used.
Ground junction boxes
Make sure the junction box is safety grounded with a low impedance connection.
When using plastic junction boxes and metal cable glands, these glands must be
connected to the safety ground bar inside the junction box, typically using a metal
plate inside junction box.
Don’t coil signal cables and power cables together
Do not coil signal cables and power cables together inside the device terminal
compartment, for example, in separately powered devices such as Coriolis and
magnetic flow meters, etc.
Keep cables short, jacket on, shielded, and separated
Don’t damage shield and conductor insulation
Do not damage shield and conductor insulation when cutting and stripping cable.
Do not use a knife to cut the cable jacket – it might damage the shield and
conductor insulation causing short circuits and reduced noise immunity. Do not use
a hacksaw to cut the tube armor or steel wire armor (SWA) – it might damage the
inner jacket, shield, and conductor insulation, the cable will no longer be
waterproof, cause short circuits, and reduced noise immunity
For cable jacket use a cable jacket/sheath stripper which only cuts the jacket
without damaging underlying layers. For tube armor use a pipe/tubing cutter which
only cuts the tube armor without damaging underlying layers. For SWA use a wire
cutter to cut strand by strand which only cuts the armor without damaging
underlying layers.
Don’t strip off more than necessary
Do not remove shield or jacket for cable running in cabinet or junction box - bare
shields (and drain wire) of different cables will touch and may cause ground loops.
Do not untwist the twisted pair.
Maintain shield and jacket as far as possible, close to the connection terminals.
Ground284overall shield for multi-pair cable
· 46 条评论
Do not leave overall赞 shield on multi-core cable
评 floating. 分享
论
On multi-core cable, the shield shall be grounded in the power supply end. Make
sure overall shield does not touch any of the individual pair shields.
Ground the cable armor
For armored cables, do not leave the cable armor floating
For armored cable, the metal cable gland must make contact with the amour of the
cable at the device and in the junction box. If plastic cable glands are used at the
junction box, or the junction box is plastic, the cable armor shall be grounded to
safety ground bar. Ground the armor in multiple points: before cable enters
marshalling cabinet, in cable tray, and in the field junction box.
Other good installation practices
Normal good installation practices apply; these are the same as for any wiring:
Do not pull cable with too much force
Make sure cable glands are tight
Seal unused conduit entries
Use correct size ferrule/fork and tool
Do not cram wires in device terminal compartment
Do not over/under-tighten screws
Make sure covers are tight
Do not tighten cable-tie too much
Label wires
Observe polarity
Commission Correctly
To get value out of HART it must be commissioned correctly. In many plants it was
not, and284as· 46a条评论
result HART is underutilized.
When HART requirements are not considered 评
at commissioning, the analog 4-20
mA signal will work赞but the smart features 论cannot be accessed and分享the benefits not
reaped.
Some of the mistakes in commissioning that prevent HART from working properly
include:
HART communication not checked during loop check (loop test)
Digital integration not verified
HART communication check at loop check (loop test)
Although it is critical to perform a 5-point look check for the 4-20 mA current loop
to verify scaling and linearity etc. at 4 mA, 8 mA, 12 mA, 16 mA, and 20 mA, as well
as < 3.6 mA and > 21 mA to verify NAMUR NE 23 functionality, it is also important
to verify the HART communication. Use a loop calibrator with HART communication
capability or a handheld field communicator to communicate with the device while
it is on the current loop to ensure communication is error free. For instance,
monitor the four dynamic variables (PV, SV, TV, and QV) for some time. This verifies
the design and installation is done correctly, so digital communication will be
reliable.
赞 评 分享
论
Just devices with diagnostics alone are not enough. Also having IDM software
won’t do it because if nobody looks at the software, the diagnostics and software is
useless. Getting into the habit of using the IDM software as part of the daily routine
is an important step. It is a culture change. This is the same as for fieldbus and
other digital communication.
Some of the work practice mistakes in that prevent diagnostics from being put to
good use, include:
Instrument diagnostic alarm summary and log not reviewed daily
Device diagnostics not reviewed before going to the field
Not rewriting Standard Operating Procedures (SOPs)
Review instrument diagnostic alarms
Instrument technicians must make it a point to review the instrument diagnostic
alarm summary and log every day to see what is happening to the instruments in
the field. By acting on predictive diagnostics, outright failures can be avoided. Also,
routine inspection of devices results in technicians spending precious time on
devices which need no service while a device that needs service gets no attention.
By using the IDM software technicians can instead focus on the device which need
their attention.
Check the software first
When operations say a device is not working, instrument technicians must make it
a point to check the software first, before going into the field to take a look,
because many times it turns out to not be a device problem. By checking the IDM
software first, many unnecessary field visits resulting in no action taken can be
avoided.
Rewriting Standard Operating Procedures (SOPs)
The work procedures related to instrumentation such as inspection, replacement,
calibration and other tasks have to be rewritten to include the use of the IDM
software. But most importantly, getting into the habit of checking the software first
is a culture change.
Maintain
284 · 46Properly
条评论
赞 评 分享
论
To get value out of HART the installation must be maintained in good condition to
ensure the HART communication continues to work error free. In many plants this is
not done, and as a result HART is disabled for one device after another as
communication deteriorates, so as to avoid communication alarms. The analog 4-
20 mA signal will work but the smart features can no longer be accessed and the
benefits not reaped. When HART communication stops working, digital
communication troubleshooting should instead be done to bring it back online.
The issues that develop over time preventing HART from working properly include:
Cable shield grounded at device by somebody not knowing it shall not be connected at
the device
Inadvertent contact between shield and grounded metal objects due to moisture or dirt,
or at device replacement
Excessive loop resistance due to corroded terminals or added series device like an
adapter
Device replaced with a device which is not HART-enabled
New source of noise
Moisture in device compartment or field junction box
Loose connections due to vibration
HART signal attenuation due to increased capacitance in aging cable or stray capacitance
Device replaced with a device which is not the correct HART protocol version
Device replaced with a device which has not been configured correctly
Additional master connected causing master conflict
Shield damaged
Shield continuity compromised
Housing ground disconnected at device replacement or due to corrosion
284 · 46 条评论
Field junction box ground poor connection due
评 to corrosion
赞 论 分享
When HART communication alarms start appearing, don’t just disable HART
communication. Instead troubleshoot the communication to fix the problem. If
HART communication is disabled, the benefits of HART are lost and only analog 4-
20 mA remains.
Monitor network health
Communication errors are usually only alarmed if there are three unsuccessful
attempts in a row. Therefore monitoring communication Packet Error Rate (PER) is a
good way to detect deteriorating communication much earlier, before alarms start
ringing. Check communication statistics for lost packages from time to time. The
control system may have built-in communication diagnostics, or external HART
analyzer software can be used. This is just like fieldbus and other digital
communication.
284 · 46 条评论
赞 评 分享
论