InHand Networks Technical Team · Published 2026-06-16 · Renewable Energy / Industrial IoT

Wind turbines are placed where the wind is strongest — ridges, hillsides, coastal and offshore sites. That is exactly where trenching fiber or leasing a line to every tower is uneconomic. A 5G router for wind farm monitoring solves that operational problem: pull SCADA traffic back to the control center without civil works, without a per-site leased circuit, and without sending a technician on a four-hour drive every time the link drops.

Below: the architecture, the protocols (Modbus RTU, MQTT, IEC 61400-25), the multi-carrier failover pattern, the cybersecurity controls that satisfy IEC 62443 and NERC CIP, and the field constraints that determine whether a router will survive a 20-year deployment at a remote turbine base.

Why Wind Farms Need Cellular SCADA

Wind turbines produce 30-200 data points each: rotor RPM, pitch, yaw, generator winding temperature, gearbox vibration, nacelle temperature, wind speed/direction, power output, and dozens of fault and status registers. Operators want that data at the control center at 1-10 second cadence for condition monitoring, predictive maintenance, and grid compliance.

Traditional options all have a cost problem on a wind farm:

• Fiber trenching across a 10-km ridge can cost more per kilometer than the SCADA hardware at each turbine, with 6-18 months of civil works and permitting.
• Leased lines are often unavailable from the local carrier at remote turbine bases, or priced like a small enterprise circuit per site, recurring over a 20-year asset life.
• Private radio requires line-of-sight and licensed spectrum. Adding a turbine means a new path study and often a new tower.

Cellular — 4G LTE today, 5G in newer coverage areas — shortens deployment from months to days and turns the connectivity cost into a predictable per-site monthly data plan. A 2025 published offshore wind farm case study used a 5G+4G dual-link backup architecture to maintain 99.99% online rate during a typhoon that cut the fiber link; the cellular router auto-switched from fiber to 5G in under 50 ms and from 5G to 4G in under 3 seconds. That resilience is what makes cellular a primary path, not just a fallback, in modern wind farm designs.

Architecture: 4-Tier Cellular SCADA Stack

1. Tier 1 — Turbine PLC / RTU. The vendor's turbine controller, typically Modbus RTU on RS485 or Modbus TCP on Ethernet. Some modern controllers also support IEC 61400-25 or OPC UA.
2. Tier 2 — Edge gateway. The InHand IG502 is a typical pick: it reads Modbus RTU/TCP, OPC UA, EtherNet/IP, ISO on TCP, runs a Python SDK for custom logic, and pushes the result to AWS IoT, Azure IoT Hub, ThingsBoard, or InHand DeviceLive.
3. Tier 3 — Cellular backhaul. The InHand IR624 covers this tier: dual NANO SIM (Verizon, AT&T, T-Mobile certified), optional eSIM, RS232+RS485, four GbE ports, -20°C to +70°C in a metal IP30 housing.
4. Tier 4 — SCADA control center. A cloud SCADA platform (AWS IoT, Azure IoT Hub, ThingsBoard, OSIsoft PI, or an on-premises historian) ingests the MQTT stream and pushes firmware-over-the-air (FOTA) back down to the field devices.

The split between Tier 2 and Tier 3 is deliberate. A pure router does not speak Modbus well; a pure gateway does not have the radio performance or carrier certification of a router. Combining the two — gateway for protocol conversion, router for cellular and security — is the deployment pattern in most published wind farm case studies.

Hardware: Industrial 5G Router and Edge Gateway

Wind farm cabinets are not data-center racks. Two operational facts drive hardware selection:

• Temperature swing. Tower-base cabinets in cold-climate wind farms swing from -30°C in winter to +55°C in summer, with the cabinet adding 10-15°C of internal heat rise. The router and gateway must be rated for the full operating range as a single unit.
• EMC and surge. Turbine converters and pitch/yaw motors generate large switching transients. The router and gateway need EN61000-4-2/3/4/5/6 EMC compliance at level 3, plus surge protection on the power input.

For the cellular router tier, the IR624 is a field-typical pick: 5G Sub-6 + mmW at 4.67 Gbps downlink peak, dual NANO SIM (Verizon, AT&T, T-Mobile certified), optional eSIM, RS232 + RS485, four GbE ports, DC 9-48V, metal IP30 housing rated -20°C to +70°C operating, -40°C to +85°C storage, DIN-rail and wall mounting.

For the edge gateway tier, the IG502 is a field-typical pick: ARM Cortex-A8 600 MHz, 512 MB DDR3, 8 GB eMMC, two 10/100 Ethernet ports, RS232 + RS485, optional 4× DI / 4× DO, optional Wi-Fi 2.4G, GPS, and BLE, plus a Python SDK and 80+ industrial protocols. The platform supports Modbus RTU, Modbus TCP, OPC UA, EtherNet/IP, ISO on TCP, and PPI natively. Power is DC 12-48V at 250 mA @ 12V working, 500 mA @ 12V peak (about 3-6 watts).

Sources: inhandgo.com IR624 and IG502 product pages; InGateway502 product spec V3.3 (PDF).

Modbus RTU to MQTT at the Edge

Most wind turbine controllers are Modbus-first. The PLC exposes vibration, temperature, pitch, yaw, RPM, power, and fault registers polled over RS485 (Modbus RTU) or TCP (Modbus TCP). Cloud SCADA platforms — AWS IoT, Azure IoT Hub, ThingsBoard, OSIsoft PI — do not speak Modbus natively; they want MQTT or HTTP/JSON.

On the IG502, the protocol conversion is configured, not coded: the operator maps Modbus register addresses to JSON tag names, sets the polling interval (1-10 seconds per turbine), and the gateway publishes the result to the cloud broker. The Python SDK lets an integrator add local logic — alarm thresholds, vibration-spectrum FFT pre-processing, gearbox-temperature rate-of-change — before the data leaves the site.

Three patterns show up in field deployments:

1. Pass-through. Every Modbus register goes up as JSON. A 30-turbine site can produce 1-3 MB/day of telemetry.
2. Edge-filtered. Only register changes above a delta threshold, or values outside a normal band, get pushed. Bandwidth drops 60-80% in steady state; alarm latency stays the same.
3. Edge-aggregated. The gateway computes 1/15/60-minute averages on-site and pushes only the aggregates, with raw values retained locally. Useful for metered data plans.

For wind farms using IEC 61400-25 (the wind-industry data model), the gateway maps the IEC 61400-25 logical nodes (WTUR, WROT, WGEN, WTRM, WNAC) into the cloud broker's tag structure. The IG502 supports this through its Python SDK and its OPC UA server mode. For Modbus-specific deployments, the Modbus Organization specification defines the register model that most wind turbine PLCs use.

Multi-Carrier Failover

A wind farm SCADA link that goes dark during a regional carrier incident is a service-level event — the asset manager notices within the hour, and the regional grid operator may notice within the day if the farm has grid commitments. Single-carrier SIM designs are not enough.

The standard pattern is dual-carrier failover. The IR624 takes two NANO SIMs (one Verizon, one AT&T) and monitors the primary link continuously. When the primary's signal drops below a configurable threshold, the data sessions drop, or the SIM idle timer expires, the router shifts traffic to the secondary in seconds. The optional eSIM adds a third profile for international roaming or for swapping carriers without a physical site visit.

Failover triggers worth configuring:

• Weak signal (RSRP below -110 dBm for a sustained period) — common at the cell edge of a remote ridge site.
• Data limit on the primary SIM — prevents bill shock on a misbehaving device.
• Network denied / no network — for tower maintenance windows and regional outages.
• Heartbeat timeout — independent of the cellular radio, useful for catching VPN tunnel failures that the radio layer does not see.

The strongest resilience comes from a multi-link design: 5G cellular as primary at most turbines, a fiber drop at the hub turbine, and 4G LTE as the final fallback. The 2025 PUSR case study used this 4-link pattern (5G + 4G + fiber + WiFi) and reported 99.99% online rate through a typhoon that cut the fiber link.

Field Constraints: Power, Temperature, Cabinet

Power

Most wind farm cabinets run on the turbine's auxiliary 24V DC or 48V DC bus, sometimes backed by a small UPS. A few remote met-mast or sub-station cabinets are solar + battery. The IR624 runs on DC 9-48V; the IG502 runs on DC 12-48V at 250 mA @ 12V working (about 3 watts). A pair fits comfortably on a 30-watt budget, leaving room for an Ethernet switch and a small cellular booster.

Temperature

Cabinet internal temperature typically runs 10-15°C above ambient. A site that hits -25°C ambient needs a device rated to -35°C operating; a -20°C to +70°C rated device covers the bulk of on-shore wind regions. The IR624 and IG502 are both rated to -20°C to +70°C operating, with -40°C to +85°C storage. For high-altitude or arctic sites, specify a cabinet heater and confirm the device's cold-start behavior with the manufacturer.

Cabinet environment

Dust, salt spray (coastal sites), humidity, and condensation are routine. The IR624 and IG502 are both metal-housed, IP30, fanless, and rated 5% to 95% non-condensing humidity. For offshore or coastal sites, the cabinet itself should be IP65 or better, with the router and gateway mounted inside on a DIN rail away from cable glands.

Cybersecurity: IEC 62443 and NERC CIP

Wind farm SCADA falls under critical-infrastructure cybersecurity rules. The two standards most often in the specification are IEC 62443 (international, for industrial automation and control systems) and NERC CIP (North American, for the bulk electric system). IEC 61400-25 is the wind-industry communications standard and is referenced alongside, not in place of, IEC 62443.

What the cellular router and edge gateway need to provide:

• IPsec VPN tunnel between the remote site and the SCADA control center, with the operator's PKI managing device identity. Both the IR624 and IG502 support IPsec; the IG502 also supports OpenVPN.
• Stateful firewall to segment SCADA traffic from any local maintenance network. The IR624's policy routing and zone-based firewall are the typical configuration targets.
• Multi-level user authorization on the local management interface, with separate engineering and operator accounts.
• Firmware signing and secure boot, with FOTA managed centrally from the cloud SCADA platform. InHand DeviceLive provides FOTA for both devices.
• Audit logging of configuration changes, logins, and link events, exportable to the operator's SIEM.

For IEC 62443, the integrator typically defines a Security Zone (the turbine-base cabinet and its PLC) and a Conduit (the cellular backhaul). The router is the conduit's enforcement point: it terminates the IPsec tunnel, applies the firewall rules, and authenticates the device. The gateway, by contrast, is inside the security zone and is treated as a trusted element.

From Edge to Cloud SCADA

Once the cellular link and the protocol conversion are in place, the cloud side is the same as any other industrial IoT deployment. A typical dashboard runs in the operator's historian — OSIsoft PI, Ignition by Inductive Automation, or a cloud-native stack on AWS IoT or Azure IoT Hub. The cellular gateway pushes MQTT topics at the configured cadence; the historian subscribes, time-stamps, and stores the data. Dashboards render in the operator's web UI; alarms fire when a register crosses a threshold.

Three things are worth getting right. Tag naming: a consistent schema (e.g., site/turbine_id/signal_name) makes downstream analytics, anomaly detection, and ML model training dramatically easier; the IEC 61400-25 logical-node structure (WTUR, WROT, WGEN) is a reasonable starting schema for greenfield deployments. Time synchronization: all field devices should sync to NTP — the IR624 and IG502 both support NTP client mode, and the SCADA historian should be the NTP source of truth. Fleet management: with dozens of turbines at multiple sites, configuring each device by hand does not scale, so InHand DeviceLive is the typical platform for pushing configuration templates, running FOTA, and receiving link-health alerts across the entire fleet from a single dashboard.

Payback: Cellular vs Fiber and Leased Line

Fiber trenching across a 10-km ridge with 30 turbines commonly runs in the multi-million-dollar range, with 6-18 months of civil works, permitting, and weather delays. Leased lines run $300-1,500 per month per site, with carrier availability often the limiting factor at remote turbine bases. Cellular SCADA flips that: capex in the low-thousands per site, plus a single 4G/5G data plan per site ($20-100 per month), and a deployment timeline measured in days per site.

Field-reported paybacks for cellular SCADA vs leased line are typically 12-24 months in retrofit scenarios, and shorter in greenfield deployments where the alternative is trenching. The added benefit of operational flexibility — adding a new turbine, swapping a faulty device, or moving a turbine in a repowering project — does not show up in the payback calculation but shows up clearly in the operations team's day.

The right time not to use cellular is when the wind farm is grid-connected at a substation that already has fiber back to the control center, and the operator is willing to accept the cost of running fiber drops to each turbine from that substation. In that case, cellular is the backup path, not the primary one.

FAQ

Bottom Line

A wind farm SCADA deployment does not need fiber to every turbine to be reliable. What it needs is an industrial cellular router and edge gateway sized for the cabinet environment, multi-carrier failover at the radio layer, IPsec VPN at the security layer, and Modbus-to-MQTT protocol conversion at the data layer. The InHand IR624 + IG502 combination is a field-typical stack: 5G multi-carrier backhaul with -20°C to +70°C operation, plus a Modbus/OPC UA edge gateway with a Python SDK for the IEC 61400-25 data model. For greenfield sites, cellular SCADA is typically a 12-24 month payback against leased lines, and a multi-month savings against fiber trenching. For brownfield retrofits, it is a deployment measured in days per site, not months.