Wireless PLC Communications: 5-Mile Pipeline Link Design

A five-mile pipeline link should not be selected by comparing radio data rates alone. The control requirement comes first: which values must cross the path, how quickly stale data must be detected, how long the process can tolerate an outage, and what the PLC must do when the channel disappears. A radio can show excellent signal strength and still deliver unacceptable jitter, packet loss, or recovery time for the application.

Satellite service may remain suitable for supervisory reporting, voice, or slow SCADA polling, but a shared service is a poor default for tightly timed controller exchange. Geostationary paths add substantial propagation delay before congestion, weather, and provider routing are considered. A dedicated terrestrial radio link removes that satellite path, yet it does not make Ethernet deterministic. The radios, queues, retries, interference, and protocol design still control the result.

The engineering target is a bounded and supervised data path, not simply a successful ping across the right-of-way.

Write the communications contract before choosing a band

List every exchanged item and classify it as control, alarm, sequence, diagnostic, or historian data. Define the normal update interval, maximum acceptable age, outage action, and recovery behavior. Leak detection deserves particular care: a remote value should never remain believable indefinitely after communications stop. Include a heartbeat, sequence counter, source timestamp, and explicit quality state so the receiving controller can distinguish a new sample from a repeated packet.

Do not let the wireless link become the only protective layer for a hazardous process. Independent shutdowns, local permissives, pressure protection, and the site safety lifecycle remain responsible for safe action. The remote PLC should enter a documented degraded state when data quality expires rather than continuing control with stale measurements.

Understand which EtherNet/IP traffic crosses the air

Explicit MSG traffic is request-and-response communication and can be scheduled at a rate the radio can support. Implicit I/O and produced/consumed data use cyclic delivery and are more sensitive to variable delay and packet loss. Rockwell guidance for wireless EtherNet/IP emphasizes application-specific validation of latency and jitter, along with suitable RPIs and connection settings. That is a reason to test the actual controller traffic, not proof that every wireless path is suitable for a fast RPI.

Keep engineering access, video, and general site traffic away from the control channel or enforce a measured quality-of-service policy. A dedicated VLAN improves traffic separation but is not a security boundary by itself. Use managed switches, access controls, encrypted radio management, unique credentials, and restricted administrative paths. Avoid exposing radio management interfaces to the business network or public internet.

Calculate the RF path, including the space around the line of sight

Visual line of sight is only the centerline. Radio energy occupies the first Fresnel zone around that line, and terrain, vegetation, buildings, and future growth can intrude into it. At an eight-kilometer path midpoint, the first-zone radius is approximately 26 meters at 900 MHz and 10 meters at 5.8 GHz. A common design objective is to keep at least 60 percent of that zone clear, but the final clearance must include antenna height, terrain profile, earth curvature where material, and the vendor's path model.

The free-space loss over the same distance is about 110 dB at 900 MHz and 126 dB at 5.8 GHz. Those figures are only the starting point. The link budget adds transmitter power and antenna gain, then subtracts feedline, connector, polarization, obstruction, and implementation losses. The remaining fade margin must cover the site's weather, foliage, alignment tolerance, and required availability. Regulatory power and antenna limits apply in the installation jurisdiction.

Terrain clearance, antenna system losses, and fade margin matter more than the radio's headline throughput.

Choose frequency by path and traffic, not fashion

Sub-gigahertz systems can provide useful propagation for modest data rates, but the larger Fresnel zone may require taller structures. A 5 GHz bridge can carry more traffic and has a smaller zone, while higher free-space loss and obstruction sensitivity increase the importance of alignment and clear path design. Some 5 GHz channels are subject to dynamic frequency selection, so a radar event can force a channel change. Channel policy must be confirmed for the country and radio model instead of copied from another project.

Throughput specifications also need translation into usable control capacity. Encryption, retries, management frames, and changing modulation consume airtime. Measure one-way delay if the application needs it; a ping provides only round-trip behavior. Record median, high-percentile, and worst observed latency together with packet loss. A stable average can hide bursts that repeatedly trip a controller connection.

Build a resilient field architecture

Provide surge protection, protective earth, weather-rated connectors, drip loops, and a documented antenna grounding arrangement. Size the remote power system for the radio, switch, PLC, heater, and any solar or battery duty. If communications availability justifies redundancy, avoid two links that share the same mast, power supply, frequency congestion, or upstream switch. Diversity is useful only when the failure modes are actually independent.

Use stable controller and management addressing, but keep configuration recovery practical. Store radio configurations, firmware versions, antenna orientation, cable loss, and credentials under change control. Monitor RSSI, signal-to-noise ratio, retry count, link rate, temperature, and uptime through the plant's approved management path. An alarm should indicate degrading margin before the link fails completely.

Commission with the real traffic and failure modes

Start with a spectrum survey and terrain profile, then align the link while recording both ends. Run the intended MSG or produced/consumed workload for long enough to include busy network periods and changing weather. Verify controller heartbeat timeout, stale-data handling, reconnect behavior, and alarm delivery. Introduce a controlled radio outage and confirm that both sites enter the specified state without unsafe chatter when the path returns.

Repeat tests with expected engineering traffic and any permitted supervisory load. Capture latency distribution, loss, reconnection time, RSSI, noise floor, and available fade margin in the acceptance record. A link that passes only a clear-day throughput test is not commissioned for pipeline service.

Relevant hardware can be reviewed in the ProSoft communications collection, including an industrial wireless hotspot listing. Product selection still requires a licensed RF survey, regional approval, antenna design, and confirmation that the exact radio supports the required bridge, security, and environmental features.

Engineering view

The speed of light across five miles is not the limiting factor; propagation takes only a few tens of microseconds. Queueing, retries, interference, protocol timing, and failure recovery dominate. A good design therefore treats the radio as a variable-quality network segment, supervises every control value, and proves the complete application under loss—not just the RF link under ideal conditions.