The Radio Is the Easy Part of a High Site

Communications tower on a mountain high site at dusk
In this Field Note
  1. Price the trip before the radio
  2. Make a power budget you can explain
  3. Keep a window into the site
  4. Give the RF design a physical inspection
  5. Name the failures you expect to survive
  6. Finish with an acceptance record

The radio arrives with a model number, a data sheet, and a delivery date. The access road, power system, mounting structure, and person who can open the gate tend to be less well specified.

That is why a high site can perform beautifully on installation day and be miserable to own. The link budget describes a radio path. The operating plan has to describe the whole site.

Before ordering equipment, work backward from two questions: what service must remain available, and how will somebody recover it on the least convenient day of the year?

Price the trip before the radio

Write down the sequence from an alarm to restored service: identify the fault, reach the right person, obtain the part, arrange access, travel, work safely, replace the equipment, and verify the result. Put a realistic time beside each step. Do not treat the ten-minute swap at the end as the entire repair.

A ridge that is easy to reach in September may be a different proposition in February. Gate access, landowner arrangements, required qualifications, escorts, weather restrictions, and the availability of qualified tower personnel belong in the design assumptions.

This gives small purchases an honest context. A labeled, controllable power port or a prepared spare may avoid an expensive visit. Conversely, a complicated redundancy scheme can create more work than it saves if nobody local can diagnose it. Spend against a defined failure and recovery cost, not a general feeling that more equipment must be safer.

Make a power budget you can explain

List every load: radios, switch, router, management modem, monitoring hardware, and environmental equipment. Record normal demand, the manufacturer’s permitted supply range, startup behavior, and the source feeding it. Include conversion and distribution losses. Confirm compatibility at the exact model level; passive PoE and standards-based PoE are not interchangeable purchasing descriptions.

Then work out the required runtime. As a deliberately simplified example, suppose a battery bank stores a nominal 1,920 watt-hours. If the design allocates 50 percent of that energy for use and assumes 90 percent delivery efficiency, it supplies 864 watt-hours to the load. At a steady 120 watts, the arithmetic gives 7.2 hours.

Those percentages are example assumptions, not battery recommendations. They do not account for a particular chemistry’s limits, aging, cold weather, discharge behavior, or a heater cycling on. The useful part of the calculation is that someone can challenge each input. The unhelpful version is “the battery should last all night.”

Use the selected manufacturer’s discharge curves, temperature limits, and charging requirements. Victron’s battery operating guidance, for example, explains how temperature and discharge conditions affect its batteries; those limits must not be generalized to an unrelated battery. Electrical protection, wiring, grounding, and battery installation need appropriately qualified design and field work.

Also ask what happens after the outage. Can the charger support the live load while replenishing the bank? Will an automatic restart produce an avoidable surge of demand? A site that survives the night but cannot recharge during normal operation has only postponed its next outage.

Keep a window into the site

Decide which observations remain available when the main link disappears. Useful signals include input-power state, battery condition, temperature, radio levels, interface errors, and the age of the last successful configuration backup.

A management VLAN carried over the main backhaul will disappear with that backhaul. It can provide useful traffic separation; it does not provide independent access. If a cellular management path is justified, test coverage at the installed antenna position and check its power, carrier, security, and data-plan dependencies.

Test remote power control as a complete operation. The controller must stay reachable while its target is off. The label must identify the actual load. The operator must know the expected boot time and how to tell recovery from another failed start. Put the demonstrated sequence in the site’s recovery manual.

Give the RF design a physical inspection

Use a path profile to assess terrain, obstructions, antenna heights, and required clearance for the selected frequency and availability objective. Cambium’s LINKPlanner profile guidance shows how clearance is represented in its planning tool. A planning model is evidence about the inputs supplied to it; it cannot confirm that the rooftop has changed or that a tree has stopped growing.

Have the proposed positions checked in the field. A clear view, adequate RF clearance, and a mounting location that qualified installers can safely build and maintain are separate requirements. Include structure, wind exposure, cable routes, strain relief, environmental sealing, and access to the equipment.

At commissioning, save receive levels, modulation, errors, delivered traffic, and latency under stated conditions. Photograph the mount and cable route as well as the radio. A close-up of a product label is useful, but it will not explain where water can enter the installation.

Name the failures you expect to survive

For each backup, complete the sentence “this protects us when…” A second radio may protect against one radio failing. If both use the same switch, power distribution, and support structure, those shared elements remain relevant failure points.

Where a secondary transport has less capacity, agree what it must carry. Protect essential traffic and verify its performance at the reduced rate. A backup that answers a ping while every useful application times out needs more work.

Keep rapid routing detection in proportion. It can help a supported routed design respond to a failed path, but it cannot restore a lost power source or arrange tower access. Wireless transport acceptance should measure the interval until useful service returns, not just the routing protocol’s timer.

Finish with an acceptance record

Agree on safe, supervised tests before the installation: normal load, the intended backup path, loss of an approved power source, alarm delivery, recovery access, and restoration. Qualified personnel should control electrical and field tests. Record anything that could not safely be demonstrated; an untested condition should not become a checked box.

The handoff needs named ownership for power, transport, physical installation, and network configuration. Include the measured baseline, access process, spares, and the next inspection or maintenance action.

For broadband and remote-site projects, Oaktown Tech can turn these dependencies into a coordinated design and commissioning plan. The radio still matters. It simply deserves a site capable of supporting it after everyone has gone home.

Share this article

LinkedInFacebookXEmail

Field discussion

What would you test next?

Ask a question, challenge an assumption, or share a lesson from the field. Keep customer names, live addresses, credentials, and sensitive network details out of public comments. Charles reviews every comment before it appears. See the privacy notice for how comment information is handled.

Join the discussion

Your comment will appear after Charles reviews it. Required fields are marked .

A pseudonym is fine.

Working through a similar problem?

Describe the network, the difficulty, and the outcome you need. Charles reviews the brief and helps establish the right scope.