InsightHardware & power

Hardware built for the field

Field hardware lives where the weather, the wildlife and the lightning are. It survives there as a system: an enclosure matched to its environment, power sized for the dark weeks, protection that gives a surge somewhere safe to go, and a design that a technician can service in the rain1.

  • 7 min read
  • Figures 7
  • Sources 8
  • Updated

A small field site drawn to scale: a lattice tower with radios, a solar and battery microgrid beside it, a rugged equipment case at the foot of the tower and a weather station mast nearby.

Figure 1 A field site as one system: tower, power, equipment and instruments

Key points

  1. Field hardware is a system: enclosure, power, protection and maintenance are designed together.
  2. Enclosures are chosen against a stated environment class, not a brochure adjective.
  3. Autonomy is a budget between the battery, the load and the sun at the worst time of year.
  4. Lightning protection works by giving surges a planned path to earth, so bonding matters as much as the protectors.
  5. Hardware that reports on its own health turns maintenance from a guess into a plan.

Field hardware is a system, not a box

Field hardware is everything that keeps an instrument working where nobody is watching: the mast, the enclosure, the power system, the radios, the protection and the cables between them.

Each piece is easy to specify alone. The hard part is that they fail together. A cracked cable gland lets in water, the water corrodes a connector, the connector raises a resistance, and the battery drains faster than the solar budget allowed.

So the site is designed as one system. The environment it must survive is written down first, and every part is chosen against that description rather than against a catalogue adjective such as rugged.

Agencies that run large field networks say the same in procurement terms. They ask buyers to look past the lowest bid to life-cycle costs, serviceability, expandability and compatibility with the systems around the station2.

The rest of this article takes the parts in turn: enclosures, environment, power, lightning, maintenance and the health data that ties them together.

Enclosures and ingress protection

The enclosure is the outer line of defence. The degree of protection it gives is classified by the IP code, an international standard for enclosures of electrical equipment rated up to 72.5 kV3.

A rating is a tested property of the enclosure as built, not of the electronics inside it. Every hole made afterwards, for a cable, a vent or an antenna, has to keep the protection the rating describes.

A stack of protective layers from the outside in: the environment class, the enclosure shell and its rating, seals and cable glands, the thermal path, shock and vibration mounting, and the electronics at the core.

Figure 2 Protection from the outside in

That makes the details decisive. Cable glands sized to their cables, gaskets that are compressed evenly, drip loops on every cable and connectors with their seals in place keep water out far more reliably than a heavier box.

Water also comes from inside. A sealed case that warms by day and cools at night draws in moist air, and the moisture condenses on the coldest surface it finds. Breather vents with membranes, desiccant and a little heat keep that surface dry.

Field programmes write these details into their maintenance rules. One national standard asks technicians to check cables for cracking and corrosion, confirm that the O-rings are installed on every connector and treat connectors with moisture inhibitor where the maker requires it2.

Designing for the environment class

Telecommunications equipment has long been specified against named environmental classes. A class is a systematic description of the environment for a family of locations with similar properties, built from the parameters that most affect equipment1.

The severities in those classes are chosen to have a low probability of being exceeded, generally less than 1 per cent1. That is a design choice worth stating: the hardware is expected to meet its class almost always, not always.

The same site drawn twice. On the left a rugged equipment case stands exposed on the ground. On the right the equipment sits in a walk-in shelter beside it.

Figure 3 Exposed case and sheltered equipment

The same standard separates stationary use, storage and transportation, because equipment meets different hazards in each1. A case that survives years on a mast may still be damaged on a truck if nobody designed for the journey.

Sectors add their own requirements. Equipment for power substations has general requirements covering construction, design and environmental conditions, with electromagnetic compatibility in line with other equipment such as protection relays4.

The choice between an exposed case and a shelter follows from the class. An exposed case must meet the outdoor class itself; a shelter moderates the climate for the equipment inside, but then needs its own cooling, power and protection.

Power and autonomy

Most remote sites run on sun and batteries. The design question is not average output but autonomy: how long the site keeps working through the darkest, coldest stretch of the year.

That starts with the solar resource at the site. Public datasets provide solar and meteorological data from satellite observations and models for users anywhere in the world, so the worst month can be found before the array is sized5.

An interactive power calculator. Set the battery capacity, the station load, the solar array and the peak sun hours; it shows the autonomy without sun, the daily energy balance and the days until the battery is empty.

Figure 4 How long a field site can run on its own

The simulator shows the trade. The battery sets how long the site lasts with no sun at all; the array and the sun hours set whether each day refills what the night used. A daily deficit only delays the moment the battery empties.

Temperature changes the budget too. Cold reduces the energy a battery can deliver and heat shortens its life, so the battery belongs inside the thermal design, not beside it.

Power should also report on itself. Fire weather stations record battery voltage every hour for remote troubleshooting and data validation, with a stated minimum below which the data are suspect2.

Lightning, surges and grounding

Field sites are often the tallest thing around, and tall objects are more likely than the ground nearby to send up the connecting spark that a lightning flash follows6. Masts on hills are doubly exposed.

Protection against lightning is standardised as a whole: structures, the installations and contents inside them, and people7. The current edition adds the idea of damage that impairs the availability of internal systems, and specifies surge currents for sizing protectors on power and telecom lines7.

A systems diagram of surge paths: a strike on the mast, the power feed and the antenna cable pass through the air terminal and two surge protectors to a bonding bar and the earth electrode. In the broken-bond scenario no path reaches earth.

Figure 5 Where a surge goes

Radio sites have their own recommendation for protection against lightning discharges8. The principle behind all of these is the same: give the current a short, planned path to earth, and keep every metal part at the same potential while it passes.

That is why bonding matters as much as the protectors. An air terminal and down conductor carry a direct strike, surge protectors divert what arrives on power and antenna cables, and a single bonding point ties them all to the earth electrode.

The diagram shows those paths. Break the bond and the protectors have nowhere to send the surge, so it looks for a path through the electronics instead.

Built to be maintained

Every field site is visited eventually, often in bad weather and by someone who did not build it. Hardware that is easy to maintain is hardware that stays in service.

Maintenance can be planned. One national network requires an on-site visit to every station each year, within 45 days either side of the last visit's date, to check sensors, site and station condition2.

A field service vehicle parked beside a lattice tower, with a rugged equipment case at the tower foot and a weather station mast nearby, drawn to scale.

Figure 6 A service visit: everything reachable from the vehicle

The same standard lists what to look at: the mast for damage, alignment and level, the antenna for loose or bent elements and corroded connectors, and the batteries against the maker's replacement schedule2.

Design makes those visits short. Parts that wear are reachable without tools from the ground or a single lift, connectors are keyed and labelled, and spares are interchangeable across sites, so a technician brings one kit rather than a site-specific box.

A visit should also leave evidence. The date, the parts changed with their serial numbers and a short narrative of the visit belong in the station record, so the next person starts from what was actually done2.

Hardware that reports on its own health

The cheapest maintenance visit is the one planned from data. A site that reports its own health tells the operator what to bring before anyone sets out.

Battery voltage is the classic example, recorded hourly for remote troubleshooting2. Enclosure temperature and humidity, door switches, surge counters and charge controller states extend the same idea to the rest of the hardware.

A stack of health values a field site reports alongside its observations: battery voltage and state of charge, solar input, enclosure temperature and humidity, door state, surge events and the next maintenance date.

Figure 7 Health values that travel with the data

Those values are evidence about the observations too. A temperature reading taken while the enclosure was flooded, or while the battery sagged below its minimum, deserves a flag, and only the health record can raise it.

Health data should travel with the observations, in the same open terms. An operator can then see at a glance which values came from hardware working inside its design envelope and which did not.

Nexus Observatory Inc. designs its field hardware on this principle: every enclosure, power system and protector is chosen against a stated environment, and every site reports the health of the hardware behind its data.

Questions and answers

Does a high IP rating make an enclosure suitable for any site?

No. The IP code classifies the degree of protection an enclosure gives as built3. Temperature, sun, condensation, vibration and every opening added afterwards still have to be designed for.

How is a solar and battery system sized for a remote site?

From the load and the worst month of solar resource at the site, so that the battery covers the longest dark stretch and the array refills it5.

Why is bonding so important for lightning protection?

Because protectors only divert a surge if there is a short, low-resistance path to earth, and bonding keeps every metal part at the same potential while the current passes7.

Glossary

IP code
The international classification of the degree of protection that an enclosure for electrical equipment provides3.
Environmental class
A systematic description of the environment for a family of similar locations, used to specify equipment1.
Surge protective device
A component that diverts a transient overvoltage on a power or signal line to earth.
Autonomy
How long a site keeps running on stored energy with no input from the sun or the grid.

References

  1. Standard or official statistic: ETSI EN 300 019-1-0: Environmental conditions and environmental tests for telecommunications equipment; Classification of environmental conditions; Introduction. European Telecommunications Standards Institute. . etsi.org (accessed )
  2. Government or regulator: NWCG Standards for Fire Weather Stations, PMS 426-3. National Wildfire Coordinating Group. . fs-prod-nwcg.s3.us-gov-west-1.amazonaws.com (accessed )
  3. Standard or official statistic: IEC 60529:1989+AMD1:1999+AMD2:2013 CSV: Degrees of protection provided by enclosures (IP Code). International Electrotechnical Commission. webstore.iec.ch (accessed )
  4. Standard or official statistic: IEC 61850-3:2013: Communication networks and systems for power utility automation, Part 3: General requirements. International Electrotechnical Commission. . webstore.iec.ch (accessed )
  5. Government or regulator: NASA Prediction Of Worldwide Energy Resources (POWER). NASA Langley Research Center. power.larc.nasa.gov (accessed )
  6. Government or regulator: Severe Weather 101: Lightning Basics. NOAA National Severe Storms Laboratory. nssl.noaa.gov (accessed )
  7. Standard or official statistic: IEC 62305-1:2024: Protection against lightning, Part 1: General principles. International Electrotechnical Commission. . webstore.iec.ch (accessed )
  8. Standard or official statistic: ITU-T K.56: Protection of radio base stations against lightning discharges. International Telecommunication Union. itu.int (accessed )

As of