Fieldbus & Industrial Networking


Is HART technology still useful as manufacturing moves to Industry 4.0?

December 2018 Fieldbus & Industrial Networking

With its bidirectional communication between intelligent field devices and host systems, HART has become a global standard. The example of valves shows how important the data provided by field devices can be for processes. Often, it is not only a question of how often the valve is operated, but also how long it takes to open. If this time period gets longer, it may be an indication of wear.

The correct times for maintenance or replacement are relevant. Whereas a premature replacement increases costs, a date scheduled too late may lead to a total system failure. The fact that HART is also useful with Industry 4.0 is shown in the solutions for two very different requirements: the essential differences are whether a plant is modernised toward 4.0 by means of a new control system, or whether the operator only wants to prepare more information for the targeted implementation with 4.0.

When modernising a plant, a remote I/O system is the ideal solution since new control systems work with bus protocols such as Profibus, Profinet, Modbus RTU or Modbus TCP. The remote I/O system replaces the point-to-point connection between field devices and control levels, thus enabling migration to a bus protocol. However, only the connection from the control system to the remote I/O is a bus; the existing cabling from the remote I/O to the field devices remains. The benefit of this is that plant operators can retain the existing structure with HART and 4-20 mA, and all of its advantages. In parallel to Profinet or Modbus TCP, there is an Ethernet-based communication with the control system, such as HART IP via Profinet. Direct access to the field device is also possible via HART IP. In addition, an OPC UA server can be implemented into a remote I/O gateway. The advantage of OPC UA is standardised communication according to IEC 62541 with a high data throughput for connecting different systems. The operator can then choose whether data shall be accessed via HART or other protocols.

However, if the operator only requires more information from the field devices for Industry 4.0, without a modernisation, it can be conveniently implemented via a HART multiplexer. This is connected with the control system via an RS-485 interface. The multiplexer can integrate in up to 32 different loops in the field and request HART data from each of the devices. The multiplexer can also ensure that requests from the asset management system are forwarded. This variant can be used with OPC UA to access data via the serial interface and distribute it as needed.

What are the advantages of HART-enabled devices to the operator?

The simplification of processes using HART is reflected in three different areas: the unified integration of device software; the reduced complexity with simple functions; and easy diagnostic options.

The reduced complexity is an important aspect because modern devices offer an ever greater number of higher quality functions.

Standards facilitate easy handling

More standards and fewer proprietary solutions facilitate easy handling. This includes NAMUR NE 107 for the self-monitoring and diagnosis of field devices. With a unified colour scheme and symbols, this standard ensures that five classified states can be quickly recognised by the operator. In addition, a standard such as OPC UA allows the user to exchange the actual data as well as the descriptions.

Standardised information models make it possible to interpret the data and thus reduce the configuration work. The next generation of device integration builds on this exact concept with FDI (field device integration), which specifies how the information model can provide clients via an OPC-UA interface according to IEC 62541. Previously, when a new measuring instrument or an actuator was integrated into the process, the user deployed EDDL or FDT. This meant either a text-based parameter description or a standardised, multi-vendor software interface that allowed the programming and description of complex functions and displays.

However, neither variant alone meets the current requirements when it comes to integrating functions of field devices. In contrast, FDI provides the full description of a device in an FDI device package. This is supplied by the device manufacturer and contains all the essential information for integration.

The device parameters are described via an EDDL interpreter (electronic device description language) and supplemented by complex graphic elements in freely programmable user plug-ins, just as with FDT. A further advantage of FDI is that it can be easily integrated into existing system architecture. An FDI-enabled host must therefore be available for new plants. In the case of existing plants with FDI devices in the field, the control systems must be able to understand EDDL and FDT.



Credit(s)



Share this article:
Share via emailShare via LinkedInPrint this page

Further reading:

Why secure industrial communication depends on deployment as well
Fieldbus & Industrial Networking
The Industrial Security Harmonisation Group has released a joint industry perspective highlighting a critical truth in industrial cybersecurity: secure communication is not determined by protocols alone, but by how they are deployed and managed in real-world environments.

Read more...
A single platform for all automation functions
Beckhoff Automation Fieldbus & Industrial Networking
The introduction of TwinCAT in 1996 marked a decisive evolutionary step for PC-based control. Today, the TwinCAT platform combines all automation functions in a strictly deterministic real-time environment, from PLC and motion control through CNC and measurement technology and beyond, to vision, robotics and pioneering AI tools.

Read more...
Loop signature Part 2-4: Feedforward Control: Part 3
Michael Brown Control Engineering Editor's Choice Fieldbus & Industrial Networking
In the previous articles in this series, the basic theory behind feedforward control was discussed, and it was also shown how to apply feedforward in practice. In this article, it will be shown how well feedforward can work in practice by giving a couple of examples.

Read more...
Control Station and Dimension Software partner to connect control performance monitoring with enterprise operations intelligence
Fieldbus & Industrial Networking
Control Station has entered into a strategic technology partnership with Dimension Software, a leading provider of industrial operations management platforms. The collaboration connects Control Station’s PlantESP control loop performance monitoring platform with Dimension Software’s Asset Intellect operations intelligence environment, enabling manufacturers to operationalise control performance insights across their organisations.

Read more...
PCIe digitiser cards for optimal GHz signal acquisition and analysis
Vepac Electronics Fieldbus & Industrial Networking
The addition of two new PCIe Digitiser cards from Spectrum Instrumentation extends the company’s flagship M5i series to deliver optimal GHz signal acquisition and analysis capabilities.

Read more...
Precise, synchronised control for automated steel mesh handling system
Fieldbus & Industrial Networking
Automation specialist Hambi Maschinenbau has developed a world-first system that automates the cutting, handling and stacking of heavy reinforcing steel mesh – a task that previously required up to six human operators.

Read more...
Loop signature Part 2-3: Feedforward Control: Part 2
Michael Brown Control Engineering Editor's Choice Fieldbus & Industrial Networking
Feedforward control tuning is not nearly as critical as feedback tuning, and fairly simple models are usually fine for the purpose in hand.

Read more...
Upgrading radiological surveillance systems in nuclear facilities
Omniflex Remote Monitoring Specialists Fieldbus & Industrial Networking
Nuclear plant operators face an uncomfortable reality. Many of the control and monitoring systems still in use today were never designed to support the full operational lifespan of the facilities they serve.

Read more...
Next-level CAN Software enables easy access to CAN XL
Industrial Data Xchange (IDX) Fieldbus & Industrial Networking
With the release of its PCAN-Explorer 7, PEAK delivers a major update that adds full support for CAN XL, multiple symbol files per connection, Python scripting and flexible licensing including floating licenses.

Read more...
Loop signature Part 2-2: Feedforward Control: Part 1
Michael Brown Control Engineering Fieldbus & Industrial Networking
Feedforward control is a powerful technique that can dramatically improve control variance in cases where load changes cause big deviations from setpoint and the actual process dynamics are too slow to allow the feedback controller to operate fast enough to catch these disturbances.

Read more...









While every effort has been made to ensure the accuracy of the information contained herein, the publisher and its agents cannot be held responsible for any errors contained, or any loss incurred as a result. Articles published do not necessarily reflect the views of the publishers. The editor reserves the right to alter or cut copy. Articles submitted are deemed to have been cleared for publication. Advertisements and company contact details are published as provided by the advertiser. Technews Publishing (Pty) Ltd cannot be held responsible for the accuracy or veracity of supplied material.




© Technews Publishing (Pty) Ltd | All Rights Reserved