A telemetry repeater station is a relay site placed on high ground to bridge a radio path that a master and a remote cannot make on their own. It receives data from one side and re-transmits it to the other, effectively stitching two shorter, clearer hops into one working link across terrain that would otherwise block the signal. This guide explains what a repeater station is, how store-and-forward relaying differs from simple simplex and duplex repeaters, and why each extra hop is a trade between coverage and speed.
Telemetry Repeater in one line: A telemetry repeater station is a physical relay site - a radio, antennas, tower, and power - positioned on elevated terrain to receive field data and re-transmit it, extending a radio network's coverage past hills, distance, or the earth's curvature that a direct link cannot overcome. It works by breaking one impossible long path into two viable hops, and depending on the design it may re-broadcast in real time or store a message and forward it, adding coverage at the cost of some latency and channel time per hop.
Radio links fail for terrain reasons long before they fail for distance reasons. A ridge between the master and a remote, a valley that drops a site below the line of sight, or simply the earth's curvature over a long path can block a direct link no matter how much power or antenna gain is thrown at it. When no reasonable antenna height clears the obstruction, the answer is not a bigger radio but a relay placed where it can see both ends.
The repeater station goes on high ground - a hilltop, a tall tower, a tank, or an existing structure with elevation - chosen so it has clear line of sight and adequate Fresnel clearance to both the master and the remotes it serves. From that vantage it hears sites that the master cannot and speaks to them on the master's behalf. One well-placed repeater can bring a whole cluster of otherwise-unreachable remotes into the network.
A repeater is a full site, not just a component: it needs its own radio or radios, antennas, feedline, surge protection, grounding, and a reliable power source, often solar with battery backup at remote locations. Because everything downstream depends on it, a repeater site is typically built and maintained to a higher reliability standard than an individual remote.
Repeaters differ in how they relay traffic. A store-and-forward repeater receives a complete message, holds it briefly, and then re-transmits it - useful when the incoming and outgoing hops cannot happen simultaneously, but it adds latency because each message waits to be fully received before being sent on. This message-level relaying is distinct from the broader store-and-forward buffering concept, which is about holding data through outages; here it describes how the physical repeater passes each packet along.
A simplex repeater uses a single frequency and cannot receive and transmit at the same time, so it too must take in a transmission and then re-send it, effectively doubling the channel time each message consumes. A duplex repeater uses separate receive and transmit frequencies so it can relay closer to real time, receiving on one channel while re-transmitting on another, at the cost of needing two coordinated frequencies and more equipment. The right choice depends on how much traffic the network carries and how much latency the polling can tolerate.
In some networks the repeater function lives inside the remote radios themselves rather than at a dedicated site: a remote configured as a digipeater both reports its own data and relays packets for radios further out. This distributes the relaying across the network but makes each hop dependent on the site doing the relaying, so a dedicated, well-powered repeater station is generally more robust for critical paths.
Every repeater hop a message passes through adds latency and consumes channel time, so hop count is a design constraint, not a free lever. A single hop through one repeater is common and inexpensive in performance; chaining several repeaters to reach a very distant cluster multiplies the delay and the airtime each poll uses, which slows the whole polling cycle and reduces how many remotes a channel can serve. Good network design reaches the field in as few hops as the terrain allows.
Hop count also affects reliability, because each additional relay is another point of failure and another link that must maintain its own fade margin. A remote reached through two repeaters depends on three separate hops all working; if any one degrades, the remote goes dark. This is why repeater sites are engineered carefully and why designers avoid unnecessary hops - fewer, well-placed repeaters beat many marginal ones.
From the SCADA host's perspective, repeaters are invisible when they work and painfully obvious when they do not. A cloud SCADA such as Merobix simply sees data arriving from remotes on schedule, regardless of how many relays it crossed. But when a repeater site loses power or its link degrades, every remote behind it drops off at once - a distinctive pattern in the host's diagnostics that immediately points at the shared relay rather than at each individual site. Recognizing that a whole branch of the network went silent together is the fastest way to isolate a failed repeater and get a crew to the one site whose repair restores many remotes.
When terrain - a ridge, a valley, or the earth's curvature over a long path - blocks a direct radio link between the master and a remote, and no reasonable antenna height clears the obstruction. A repeater placed on high ground that can see both ends breaks the impossible path into two viable hops. One well-sited repeater can bring an entire cluster of otherwise-unreachable remotes onto the network.
A repeater station is the physical relay site that receives and re-transmits radio signals to extend coverage over terrain. Store-and-forward, in the broader sense, is a data-handling concept where a device buffers readings through a communications outage and sends them once the link returns. A repeater may use message-level store-and-forward as its relaying method, but the two terms describe a site versus a buffering behaviour.
Each repeater hop adds latency and consumes channel airtime, so more hops slow the polling cycle and reduce how many remotes a channel can serve. Every additional hop is also another point of failure whose fade margin must hold. Good design reaches the field in as few hops as the terrain allows, favouring fewer, well-placed repeaters over many marginal ones.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.