Integrating HMIs with PLCs and PACs

Understanding the differences among controllers is essential when designing an automation system.


Figure 1: PC-based HMIs usually offer full functionality and advanced graphics, albeit at a higher price point than embedded HMI. Courtesy: AutomationDirectToday's industrial manufacturing, utility, and distribution companies require extensive data collection and analysis to stay competitive. Although newer automation technologies have made it relatively easy for these businesses to gather tremendous amounts of data, simply collecting data isn't sufficient. To achieve continuous improvement goals, these data must be presented to users in ways that facilitate analysis through user-friendly displays and interfaces.

Analysis is where data acquisition shows its real value, as this is where areas for improvement come to light. Application requirements not only help define the type and method of data acquisition, but also affect how these collected data are analyzed.

However, before analysis can take place, local and remote human machine interfaces (HMIs) are required for real-time monitoring and control-and in some instances for data handling. There are different approaches for integrating programmable logic controller (PLC) or programmable automation controller (PAC) data with HMIs. Tight integration between data gathering and presentation can help businesses improve diagnostics and overall system performance.

PC-based or embedded HMI?

An HMI can be a PC running off-the-shelf software configured for the application, or an operator interface terminal (OIT) with an embedded operating system and prepackaged software. PC-based software usually offers more functionality, while an OIT provides simpler setup and operation at a lower cost (see Figure 1).

Whether selecting a PC or an OIT, software must be configured by the end user for the specific application. Custom, complex, or advanced applications may require programming in a development environment, such as C++ or Visual Basic. However, most applications can be handled by configuring off-the-shelf software programs-a simpler process.

PC-based HMIs typically use a Windows operating system and provide easy connectivity to a multitude of PAC and PLC controllers. This class of HMI features high-end performance, but costs are relatively high as users must purchase a PC and the HMI software.

OITs generally don't include all of the features of PC-based HMIs, but they are lower in cost-both up front and in operation. Deployment is also much simpler as the HMI software is closely matched to the embedded operating system. A PC is typically used to configure the HMI software for the specific application, which is then downloaded to the target OIT.

Tightly integrated communications

HMIs are the key vehicle for providing a user interface for almost any industrial application including machine control, discrete part manufacturing, and process control. PLCs and PACs are used to control the equipment and processes, so it's natural they should be closely integrated with HMIs and OITs. Most PC-based HMIs and OITs include driver software to communicate with a wide range of popular controllers, eliminating the need to write, test, and maintain custom communication driver software.

In addition, common networking protocols, such as various flavors of Ethernet, exist to allow these distinct technologies to communicate. This has made integration much easier, and an HMI or OIT can be quickly programmed to extract data from or push commands to the controller.

Although an HMI or OIT and a controller can communicate at a basic level, they may not be truly exchanging data in the most effective and efficient manner. Moreover, there are key differences in how to integrate an HMI or an OIT with a PLC, as opposed to communications with a PAC.

PLC and PAC differentiators

Modern PLCs and PACs are designed to satisfy the complex requirements of today's automation applications. Over the years, these controllers have evolved into full-featured systems, especially in terms of data collection.

Both PLCs and PACs can store data internally, or they can transfer it to other systems. Communications from either controller to other computing systems including HMIs and OITs are typically performed through an Ethernet port, which is built into most modern PLCs and PACs. The support of popular Ethernet and other protocols negates the need to write complex drivers to exchange data between the controller and external systems.

PLCs have been around for more than 40 years. However, recent advances have greatly increased their capabilities. PLC-HMI integration advantages include:

  • Lower purchase cost
  • Greater familiarity for users
  • Better for simple machine control
  • Excellent execution speeds from advanced PLCs
  • Combined PLC/OIT devices for lower end applications.

However, these increased capabilities have led to some confusion as to which type of controller is best suited for each application.

In general, PLCs work well for machine control-both simple and high speed. But an architecture based on ladder logic and a focus on discrete on-off control can make expanding a typical PLC beyond its original capabilities difficult.

For example, an older or lower-end PLC often requires the addition of separate hardware cards to accomplish functions outside its core capabilities, such as networking among multiple components, extensive process control, or sophisticated data manipulation.

On the other hand, a PAC is geared more toward complex control and data handling. It's also usually a better match for applications with extensive process control requirements because a PAC is more capable in handling analog I/O and related control functions.

Another relatively new device on the market is the integrated PLC/OIT. By combining the controller and interface into one device, costs can be lowered significantly. These combination PLC/OIT units provide simplicity and minimize the amount of required cabling and cabinet space. However, these solutions are not a replacement for standard PLCs and HMIs or OITs in more complex applications.

Because they share a common CPU and memory, these resources can be taxed. The main function of a PLC is real-time control, and if the OIT portion is using a lot of processing power and/or dynamic memory, the control functions can be compromised. Therefore, these devices are best suited for lower end applications, not those with high I/O counts and more advanced functionality requirements.

When a combination PLC/OIT unit isn't sufficient, it becomes necessary to integrate the PLC or the PAC with the HMI or the OIT.

See the next page for more about pairing a PLC with an HMI or OIT.

<< First < Previous 1 2 Next > Last >>

No comments
The Engineers' Choice Awards highlight some of the best new control, instrumentation and automation products as chosen by...
Each year, a panel of Control Engineering editors and industry expert judges select the System Integrator of the Year Award winners.
The Engineering Leaders Under 40 program identifies and gives recognition to young engineers who...
Learn how to increase device reliability in harsh environments and decrease unplanned system downtime.
This eGuide contains a series of articles and videos that considers theoretical and practical; immediate needs and a look into the future.
Learn how to create value with re-use; gain productivity with lean automation and connectivity, and optimize panel design and construction.
Go deep: Automation tackles offshore oil challenges; Ethernet advice; Wireless robotics; Product exclusives; Digital edition exclusives
Lost in the gray scale? How to get effective HMIs; Best practices: Integrate old and new wireless systems; Smart software, networks; Service provider certifications
Fixing PID: Part 2: Tweaking controller strategy; Machine safety networks; Salary survey and career advice; Smart I/O architecture; Product exclusives
The Ask Control Engineering blog covers all aspects of automation, including motors, drives, sensors, motion control, machine control, and embedded systems.
Look at the basics of industrial wireless technologies, wireless concepts, wireless standards, and wireless best practices with Daniel E. Capano of Diversified Technical Services Inc.
Join this ongoing discussion of machine guarding topics, including solutions assessments, regulatory compliance, gap analysis...
This is a blog from the trenches – written by engineers who are implementing and upgrading control systems every day across every industry.
IMS Research, recently acquired by IHS Inc., is a leading independent supplier of market research and consultancy to the global electronics industry.

Find and connect with the most suitable service provider for your unique application. Start searching the Global System Integrator Database Now!

Case Study Database

Case Study Database

Get more exposure for your case study by uploading it to the Control Engineering case study database, where end-users can identify relevant solutions and explore what the experts are doing to effectively implement a variety of technology and productivity related projects.

These case studies provide examples of how knowledgeable solution providers have used technology, processes and people to create effective and successful implementations in real-world situations. Case studies can be completed by filling out a simple online form where you can outline the project title, abstract, and full story in 1500 words or less; upload photos, videos and a logo.

Click here to visit the Case Study Database and upload your case study.