On July 20, 2026 in All, Automation, Industrial, Industrial Automation, RF, Robotics, Wireless by Hector Barresi

Coordinating radio technology can prevent simple overlaps from having major consequences

Wireless networks have become essential on the factory floor, carrying everything from pressure and temperature readings to video, diagnostics, and mobile data. Plants often run multiple systems side by side—Wi-Fi^®, Bluetooth^®, Zigbee^®, WirelessHART, ISA100 Wireless, and others—frequently added at different times by different teams. When those systems share spectrum without coordination, they can quietly drift into conflict.

Consider the following example. At a chemical plant, a team installs Zigbee sensors along a fence line to track emissions. The sensors share the same frequency band as the plant's WirelessHART network, and no one coordinates the rollout. Within three weeks, plant sensors begin draining batteries faster than usual and miss scheduled update windows. Channel checks trace the problem to overlapping frequencies. Once each network is assigned its own slice of spectrum, performance returns to normal, but not before retry counts climb and one-second updates stretch to four. A simple coordination step could have prevented these errors, highlighting the importance of ownership in today’s multi-protocol industrial networks.

The consequences of this example capture the core challenge of wireless co-existence: managing and coordinating multiple radio systems that share the same spectrum without causing interference or starving one another of timely, reliable updates. Plants now demand wireless to effectively manage immense amounts of data, as well as to reduce facility expenses. Wiring often costs more than the sensors themselves, and moreover, radio links expand monitoring of pressure, temperature, level, and flow without tearing up existing runs. The result is visibility into previously hidden conditions and decisions that land on time. Coexistence is the plan that makes this scale.

In this blog, we explain why intentionally designing for coexistence is essential to achieving reliable wireless communication on the factory floor. We also highlight how selecting the right radio, ensuring timely sensor updates, and maintaining predictability in mixed networks—through band and channel separation, proper spacing, thorough site surveys, and clear ownership—contribute to effective coexistence strategies in industrial environments.

Match the Radio to the Job

Understanding why coexistence matters begins with recognizing that different wireless technologies serve different purposes, while also knowing which radio fits which job.

In practice, most facilities run more than one wireless system because no single radio fits every application. WirelessHART and the ISA100 series of standards commonly carry continuous monitoring, delivering on-time readings with multi-year batteries, even when radio frequency (RF) is busy. Typical update rates sit between 100 milliseconds and one second, configured per device based on how quickly the process variable can change. At scale in major facilities, few alternatives match that mix today.

Wi-Fi, on the other hand, prioritizes overall throughput. It is ideal for information technology (IT) traffic like reports, tablets, and video, where total throughput matters more than precise timing. During heavy activity, such as software updates or large file transfers, Wi-Fi timing can vary. That variation is acceptable for user devices, but not for control inputs that expect a steady cadence.

Bluetooth remains useful for walk-around diagnostics and hand-held access. Lower-frequency links around 900MHz reach assets across long distances—hundreds of meters or farther—with clear line of sight. These links also deliver data from behind heavy steel, where 2.4GHz struggles, making this approach fit for tank farms and pipe racks but unsuitable for time-critical sensor inputs.

Since the 2.4GHz band does not pass through steel effectively, many process plants lean on mesh topologies for ISA100 and WirelessHART, allowing sensors to relay signals around obstructions. The outcome is a portfolio approach that improves coverage without major rewiring.

Tailor the Wireless Combination to the Facility

It is important to remember that coexistence strategies are not universal. What works depends on the type of facility and the nature of its operations.

The right portfolio depends on what the plant makes and how it operates. A refinery and a robotics cell share the need for reliable wireless, but their priorities differ, meaning their technology choices will also diverge from each other.

Continuous process plants optimize for predictable, long-lasting monitoring. WirelessHART and ISA100 form the backbone for pressure, temperature, level, and flow, while Wi-Fi, Bluetooth, and lower-frequency links add convenience, logistics visibility, and non-critical telemetry around that core.

Discrete manufacturing and robotics follow a different pattern. Private 5G—dedicated cellular networks operated by the facility itself—and IO-Link Wireless—a short-range protocol designed for fast sensor and actuator communication—support short, fast exchanges where tight timing outweighs multi-year battery life. The application sets the requirement and the technology follows. Standards-based systems tend to integrate more smoothly as deployments grow.

On-Time Delivery Versus Best Effort

Once you know which radio does what, the next question becomes why they cannot simply share the same spectrum without consequence. The answer lies in how each technology treats time.

Coexistence is ultimately about timing. A reading is only useful if it arrives exactly when needed. Wi-Fi is designed to move high volumes of data overall, not to deliver every packet at a fixed moment. While that works for reports and screens, it does not work for signals feeding optimization or safety logic. Industrial sensor networks use scheduled exchanges—time slots assigned in advance so each device knows exactly when to transmit—resulting in readings that arrive on a steady rhythm that the control system expects, even when air traffic is heavy.

Separation and Structure Keep Networks Predictable

Recognizing that different systems have incompatible timing needs means determining how to organize them so each gets what it requires?

When coexistence is engineered intentionally, each system finds its lane. Industrial mesh networks, such as ISA100 and WirelessHART, operate at 2.4GHz because that is where their ecosystems live. Employee Wi-Fi often moves to 5GHz or 6GHz, where more channels and wider bandwidths accommodate user traffic. Deterministic or safety-critical signals still travel on cable. Lower-frequency links near 900MHz serve assets set back by distance or equipment-dense areas. Effective coexistence requires channel planning, where teams record channel choices so adjacent networks do not compete for the same slices of spectrum.

Physical placement is equally important as channel planning. High-power transmitters can desensitize nearby receivers whether they sit on the same or different frequencies. Placing a WirelessHART gateway within a meter of a Wi-Fi access point can degrade receiver sensitivity, even when the two operate on non-overlapping channels. In tighter areas, plants often schedule high-bandwidth user traffic outside expected update windows in order to keep their cadence.

How Coexistence Fails in Practice

Even with clear roles and separation strategies in place, coexistence can still unravel when those principles are not maintained with new additions.

Conflicts rarely announce themselves with a single alarm. More often, they drift in. A new network raises the background noise on the same part of the band that another system uses. Sensors begin re-sending messages. Update intervals stretch into multi-second territory, while batteries empty sooner than expected. The system still works—but out of rhythm, and at mounting cost.

Once teams identify the overlap and move off the noisiest slices, cadence returns to normal. The pattern is straightforward. Uncoordinated additions create invisible collisions that only surface later as performance issues. It rarely fails loudly. It drifts, and the cost shows up later.

When radios collide, the early signs come from operations rather than specialized tools. In practice, teams look at message retries and signal quality in the affected area, compare local channel choices, and check whether any access points were moved or added. Small course corrections at that stage usually restore the expected cadence before visibility is lost.

What Site Surveys Reveal About the Factory Floor

Theory helps, but the physical environment has the final say. That is where site surveys come in.

However good separation strategies and channel plans look on paper, the true test is executing those principles in the physical environment. Steel structures, rotating equipment, and existing transmitters create a radio landscape that drawings alone cannot predict. This is why site surveys are necessary for success, and they should be done before deployment to establish a baseline, as well as after problems emerge to pinpoint what changed.

A survey often confirms what drawings cannot. In steel-heavy areas, small shifts in sensor location change reflection paths and can turn a weak link into a strong one. Gateways that look convenient when located together often work better when spaced away from persistent noise sources like welders and large motors. Survey data also reveals whether channel assignments made in the planning phase actually deliver clean spectrum at each sensor location, or whether local interference demands adjustments.

Even in well-designed systems, the final step into control is usually cleaner over fiber. Wireless domains aggregate at the gateway, and timing stability is preserved on the wired side. A thorough survey documents not just signal strength but also the noise floor, retry rates during typical operations, and the locations of any RF-noisy equipment. This information proves invaluable when troubleshooting later.

Shared Ownership Keeps Systems Stable

Technical strategies only hold if someone is accountable for maintaining them.

Networking failures like the chemical plant example discussed in the introduction read less like a technical defect and more like a gap in ownership. Plants that treat wireless as shared infrastructure avoid such pitfalls by keeping a simple register of who operates what, on which channels, and where gateways and access points sit. This register also supports cybersecurity reviews, since every radio is a potential network entry point. New deployments should pass a quick review against that map so additions align with what is already working. Deterministic traffic stays on wires, wireless domains end at gateways, and control systems see the additions over fiber. Over time, this becomes a habit rather than a checklist—one that prevents surprises and allows for growth that does not disturb what already works.

Conclusion

Coexistence is achievable, but only when it is treated as part of the design, not an afterthought.

Plants adopt wireless to observe more points and respond faster at lower cost. Success comes from treating radio links as infrastructure for environments dense with steel and electrical noise. Clear separation between wireless domains, sensor networks built to tolerate interference, and placements validated by field surveys all contribute to predictable behavior.

With intentional design and simple monitoring, Wi-Fi, Bluetooth, lower-frequency links, and industrial mesh networks can function as a single reliable system. Coexistence is not automatic—it is engineered. Treat the airwaves like infrastructure and the result is simple: signals arrive when they should and teams trust what they see.