Across sites where cabling isn't feasible, two situations come up most often:

① The site simply can't be wired — a yard where trenching isn't permitted, a rented workshop where the landlord forbids conduit, a pump station two kilometers from the nearest switch.

② Wireless gear that worked fine five years ago can no longer handle new requirements — more devices, moving devices, longer distances, larger data volumes.

After reviewing numerous deployment projects, one pattern holds: there is no single "best" wireless technology, but four technologies, each winning in specific scenarios. Selection should be based on what the site already offers, not on what's trending. Here's how the breakdown works.

First, Look at What the Site Gives You

Before opening any datasheet, three questions:

Will the devices move?A fixed water meter and an AGV weaving through a warehouse have completely different needs.
How far, and how much data?A temperature reading once a minute and a vision camera streaming 24/7 aren't the same thing either.
What infrastructure already exists on site?Cellular coverage, existing APs, power availability — these determine the project budget more than any product spec.

Once these three are answered, one of the four options below usually becomes obvious.

Option 1: 5G Cellular Router — When the Site Has Nothing but Signal

Best for: remote or widely dispersed sites, no wired broadband, bandwidth-hungry applications — video surveillance, vision inspection, unmanned operations. Ports are a classic case: ship-to-shore cranes, gates, and sensors scattered across a terminal where cabling everything is simply impossible. That's exactly where a 5G cellular router holds its ground.

The idea is straightforward: if the site has cellular coverage, use it as the backbone. 5G cellular router like the USR-G816 runs SA/NSA dual-mode 5G on a Qualcomm quad-core platform, offers a gigabit Ethernet port for local devices, and includes a serial port for legacy equipment — one box covering both new IP cameras and that old RS485 controller.

Three practical lessons:

Configure the tunnel before the equipment ships. A device sitting on a public cellular network should never expose its LAN directly. Set up VPN (IPsec, OpenVPN, L2TP) back to the control center first. The G816 can act as both an OpenVPN client and server simultaneously, holding three concurrent client tunnels — handy when the SCADA team and the video platform each want their own dedicated path.
Set up alarms and save the drive to site.Nothing is worse than learning a remote site went down from an angry customer call. Device-offline and weak-signal alarms pushed via email or SMS mean problems can be caught before they reach the customer. A remote management platform also lets engineers change configurations and upgrade firmware without going on site.
Do the math on the SIM card.5G bandwidth is great — until the monthly data bill arrives. Estimate per-site traffic before scaling up, and consider WAN failover to a backup link for sites that can't afford downtime.

Trade-off:ongoing SIM cost and dependence on carrier coverage. If the site has no cellular signal, check coverage maps first.

Option 2: WiFi Roaming — When Devices Move

Best for: AGVs, transport robots, mobile inspection units — anything on wheels that must stay connected while in motion.

The failure mode here is specific and painful: an AGV drives out of one AP's range, takes two or three seconds to find the next one, and the connection drops. The vehicle freezes mid-aisle, blocking traffic, until someone nudges it back into a covered zone. Consumer WiFi gear behaves this way because roaming handover was never its priority.

An industrial wireless client built for roaming, like the WiFi Roaming USR-W650, closes this gap: handover between APs completes within 100 ms — fast enough that a moving robot never notices. It's dual-band (2.4 GHz / 5.8 GHz), and — the part that saves money on vehicles — one unit integrates five gigabit Ethernet ports, one CAN, one RS232, and one RS485. On an AGV, the drive controller, safety sensors, and a diagnostic port can share a single network device instead of three separate ones.

Two deployment lessons worth copying:

Survey before mounting.The WiFi Roaming W650 has built-in WiFi environment detection and link testing, so during the test phase it's possible to walk the route, see signal strength along the AGV path, and find dead zones before the vehicles do. Ten minutes of surveying can save weeks of "it only drops on aisle 7" debugging.
Plan APs along the vehicle's route, not by the ceiling grid.Roaming speed only matters if AP coverage truly overlaps along the path.

Trade-off:WiFi roaming assumes AP infrastructure already exists, or that one is being built. Coverage ends at the last AP — this is a within-the-fence solution.

Option 3: LoRa Modem — Kilometers of Distance, Bytes of Data

Best for: sensors and meters spread over wide areas where the data is tiny but the distance is huge — farmland sensors monitoring irrigation and soil, factory water/gas/electricity meters, livestock houses reporting temperature and feed levels.

This is exactly the scenario where people wrongly reach for cellular: a SIM card per sensor, a data plan per sensor, and a bill that swells with every node. LoRa flips the economics. LoRa modem like the USR-LG206 connects to any RS485/RS232 meter or sensor, with point-to-point transmission reaching up to 6 km as measured in the field — about 4.5 km to a LoRa gateway — no SIM, no subscription, no per-node cost.

A few keys that make these deployments actually work:

Relay mode gets around obstacles.If a building or hillside blocks the direct path, the LG206 can relay data through intermediate nodes, extending range in obstacle-rich environments.
Pair it with a gateway for real structure.With the LoRa gateway LG210, dozens of LoRa nodes feed into one point; the gateway converts Modbus RTU/TCP and pushes data to the platform over Ethernet in JSON format — the standard pattern in factory energy monitoring, where the platform polls meters on a schedule to track consumption.
LBT listen-before-talk, plus retransmission, handles interference.The node listens to the channel before transmitting, retries on collision, and encrypts data with user-configurable keys. On an RF-noisy farm or factory floor, that's the difference between reliable readings and mystery data gaps.

Trade-off:LoRa bandwidth is tiny. We're talking sensor readings and status flags — kilobits. For video, file transfers, or fast control loops, move on to the next option.

Option 4: Industrial Bridge — When One Cable Run Needs Replacing

Best for: connecting two fixed points. A PLC cabinet in the workshop talking to another PLC across the yard; a new production line that needs office-network access, but trenching costs more than the equipment.

This is the least glamorous and most underrated option. Industrial bridge like the ST208S doesn't do roaming, doesn't do cellular, doesn't do multipoint — it does one thing: it bridges an Ethernet link across up to 500 meters of open air at 300 Mbps theoretical speed, with high-gain dual antennas on both ends. Two gigabit ports per unit, PoE or DC power, and a -40 to +70 °C operating range, so an outdoor cabinet in winter is fine.

Deployment is refreshingly simple: mount both units high and facing each other, wire the PLC to the bridge with Ethernet, power up, done — often within an afternoon. PLC and Modbus traffic is small to begin with, so real-world throughput has plenty of headroom.

Trade-off:strictly point-to-point. Don't expect a bridge to serve fifty mobile clients — that's WiFi's job.

60-Second Selection Guide

Real projects are often mixed. For example, a smart farm runs LoRa nodes across the fields and backhauls the gateway through a cellular router; a warehouse puts roaming clients on its AGVs and uses a bridge to reach the yard office. Architecture should be drawn by site conditions, not by a product catalog. Map the site first, match each link to the right technology, and the "can't be wired" problem usually dissolves into four sma