Automation—It’s All About the I/O
Global Recruiters of Palmetto (GRN) Automation Recruitment Specialist
Three golden rules for accomplishing success: attract talent, hire talent and keep talent. It is that simple.
Source: Automation World
Inputs and outputs (I/O) are fundamental to the world of computing, industrial control and data/information processing. Without them, industrial and electronic devices of all kinds would have no way of receiving data, and the user would have no way of manipulating or interacting with the data sources. Since they form the basis of our relationship with almost all the industrial devices we use, it’s important to understand how I/O modules function.
As a key component of industrial systems, I/O modules ensure connectivity and control of systems, processes and devices. They usually include analog channels, digital channels or a combination of both. Analog inputs can detect various signals including frequency, voltage or current. Digital I/O are used for low-level on/off signals. I/O modules that have analog inputs and digital outputs often incorporate an analog-to-digital (A to D) converter to process the signal.
Essentially, I/O modules act as mediators between a central processor and the industrial device. For example, the input modules on a programmable logic controller (PLC) receive signals from switches, sensors, transmitters, actuators and other equipment connected to it. The output modules on the PLC send response signals to the devices controlled by the PLC in response to the received signals.
Common functions enabled by I/O include:
Centralized or distributed
A highly centralized I/O system is characterized by concentrated I/O hardware in a single entity, with network or hardwired connections extending from that location. A highly distributed I/O system, on the other hand, has the I/O hardware distributed across many operational and physical areas, with localized network or hard-wired connections extending from these remote locations.
Local I/O is a subsystem typically housed within the same cabinet or rack as the controller. Due to its proximity to the controller, a local I/O wouldn’t have any computing power. Remote I/O, also known as distributed I/O, is usually located away from the main controller.A distributed I/O architecture incorporates small field devices with a range of I/O options, such as digital and analog channels, temperature measurements and counter inputs. These modular devices provide a flexibility lacking in traditional industrial devices that require a high-density channel count and long cable runs.
The distributed approach allows for short cable runs because the measuring devices are located closer to the sensors. Direct connection of sensors also eliminates the need for signal conditioning. Distributed I/O modules can be integrated into existing communication networks, providing a low cost, flexible upgrade path.
Advanced automation drives I/O demand
Companies of all sizes have begun retrofitting older machines and manufacturing processes with advanced electronics to enable remote monitoring and control. Many have also embraced the use of cloud computing, analytics and artificial intelligence to improve quality, streamline production, detect safety issues and cut costs.
As a result, companies are turning to I/O manufacturers to design smarter, more advanced products that integrate embedded computing technology (typical of distributed I/O). This is a key factor in modern manufacturing operations considering the need for I/O to interface with a growing assortment of sensors for Internet of Things applications. These devices also serve to offload some of the computing duties from the host computer or controller, pushing decision making closer to the edge. This minimizes the latency time from when data is gathered to when a response to that data can be generated, facilitating the near-real-time actions required by smart factories.
Another example of smart I/O is called universal I/O. It enables greater flexibility for I/O changes, most notably from its ability have as many inputs or outputs as needed, thereby bypassing the common I/O module constraint of eight inputs and eight outputs. With a traditional analog I/O system, a lot of upfront work was required to specify the right field I/O module, electrical panels, installation, wiring, power, distribution and networking. Because an I/O system is typically associated with a central controller, extensive programming was often required to get these systems to communicate effectively with each other.Universal I/O simplifies machine design and system building due to its ability to work with many different PLC environments and fieldbus protocols, thereby reducing or removing the need to replace I/O modules to meet protocol-specific requirements. This I/O technology is also preferred for its ability to work with both new and legacy equipment.
Trends in I/O technology
Though I/O modules don’t often receive the level of attention garnered by controllers and data visualization hardware and software, I/O is the core means of connectivity and interoperability in any industrial automation application—whether its basic inter- or intra-machine communications or as part of the industrial Internet of Things.
Given I/O’s centrality to industrial connectivity, it’s not surprising that both end user and system integrators responding to Automation World’s 2023 survey on industrial I/O use cited the same three recent advances in I/O technology as being the most noteworthy advances. Those three advances are: Ethernet connectivity, multiple protocol handling capabilities and high density/smaller footprint.
End users and integrators agreed that Ethernet connectivity is the number one advance to have been made recently in I/O technology, with the number two spot going to multiple protocol handling and the number three spot to high density/smaller footprint.;Running close to the number three spot for end users was onboard intelligence (a typical feature of distributed I/O), which ranked just 2 points behind high density. For integrators, however, onboard intelligence ranked fifth in importance, with ruggedization ranking fourth. Interestingly, onboard intelligence ranked seven points lower than ruggedization and 10 points lower than higher density/smaller size among integrators.
I/O type preference
The lower ranking for onboard intelligence in I/O, particularly among our integrator respondents, is reflected in the preference for in-cabinet and remote I/O over distributed I/O, which is known for having onboard computing power as part of a distributed control system (DCS). This preference for in-cabinet and remote I/O in our survey results is also reflective of our respondents’ industries—only 25% of end users and 38% of integrators responding to our survey work in continuous processing industries where DCS use is more common.
As a point of further clarification, just over 50% of end users and integrators cited use of in-cabinet I/O for the bulk (25% to 75%) of their applications and about 45% of end users and integrators use remote I/O in most of their applications. Whereas only about 30% of respondents use distributed I/O for most of the applications.
In an open field response area of the survey for respondents to note other advances they saw as important, end users cited low-power requirements and support for MQTT and OPC UA, while integrators noted IO-Link, automatic identification capabilities and Power over Ethernet.For those unfamiliar with it, IO-Link is an IEC 61131-9 standardized, point-to-point I/O technology based on the established three-wire sensor and actuator connection. According to the IO-Link Consortium (of which numerous automation technology suppliers are members), IO-Link is not a fieldbus, but a “further development of the existing, tried-and-tested?connection technology for sensors and actuators.”
Considering that most respondents work in the discrete and batch/hybrid manufacturing industries, their use of in-cabinet versus remote I/O is a key factor to focus on with regard to industry trends. And it’s clear that remote I/O is a clear winner—with only 28% of end users and 27% of integrators preferring in-cabinet I/O. In contrast, 42% of end users and 37% of integrators prefer remote I/O.
Among end users, the most prominent reasons for their preference include:
In-cabinet I/O
领英推荐
Remote I/O
Distributed I/O
Integrators cited the following reasons for their I/O type preference:
In-cabinet I/O
Remote I/O
Distributed I/O
End user selection and implementation recommendations
Responses to our survey question asking for their top recommendations to industry peers when it comes to choosing and implementing I/O modules provided a long tail of answers that were often specific to the respondent’s application or industry vertical. However, several common themes were also evident.
For example, many end users respondents advised that I/O module selection should be based primarily on two factors: the technical requirements of the application and the economic cost of the complete system being designed. This latter piece of advice is a good one to keep in mind amid the burgeoning intelligent capabilities deployed at all levels of automation technologies. Be sure to ask yourself if you really need those added features now or potentially in the near term before choosing a more expensive, feature-laden device whose capabilities you may likely never use.
In keeping with this piece of advice, another respondent said to stay focused on factors such as the required number and type of inputs and outputs, the communication protocols supported, and the environmental conditions in which the I/O module will be located.A somewhat surprising response given the increasing levels of interoperability among automation devices was to“stay within a brand family” when choosing I/O modules. The essence of this point is that, while vendors are offering more interoperable or “universal” I/O devices, some respondents contend that integration and operation is easier and more reliable when using the same brand of I/O and controller. As one respondent noted: “sticking to the PLC's ecosystem is quicker than trying to integrate something foreign to it.”
Other common recommendations included:
Integrator?selection and implementation recommendations
Reflective of ongoing supply chain issues for critical electronic components as a result of recent chip shortages, one system integrator responding to our survey dispensed with offering specific recommendations and honestly replied that, “at the moment, we prioritize things that are in stock.”
Others were more detailed in their response. One integrator even went so far as to provide the following detailed set of recommendations addressing several factors to ensure selection of the most appropriate I/O for your application:
Compatibility—Ensure that the I/O products you select are compatible with your control system and communication protocol. This will help to ensure smooth integration and reduce the risk of compatibility issues.
Accuracy and precision—Consider the accuracy and precision requirements of your application and choose I/O products that meet or exceed those requirements. This will help ensure that your system operates with high accuracy and reliability.
Signal type and range—Ensure that the I/O products you select support the types and ranges of signals you need to acquire or control. This may include analog or digital signals, high or low voltage signals, and other specialized signal types.
Reliability and ruggedness—Choose I/O products that are designed to operate reliably in your specific industrial environment. This may include products that are designed to withstand extreme temperatures, humidity, vibration or other harsh conditions.
Expandability and flexibility—Consider the scalability and flexibility of the I/O products you select and choose products that can be easily expanded or reconfigured as your system requirements change over time.
Cost—Choose products that offer a good balance of features, performance and value for your specific application. However, be sure not to sacrifice quality or reliability for cost savings, as this can ultimately lead to more expensive problems down the line.
Other frequently noted recommendations by integrators included: