manthink

Posted on Oct 28

LoRaWAN Gateway Antenna Selection and Installation Guide: Why 3 dBi Sometimes Beats 8 dBi

#hardware #howto #iot #networking

Currency note: USD figures are quoted as originally published. Reference conversion for October 2026: 1 USD ≈ 6.71 CNY. Prices marked "reference price" are subject to the manufacturer's current quotation.

Two LoRaWAN projects, less than three kilometres apart, using the same gateway model, the same batch of meters and the same ThinkLink tenant. One reaches a basement water meter 2.4 km away with -118 dBm and -12 dB still in hand. The other starts dropping packets 300 m away inside a single building — and went back to site three times.

The difference was not the gateway and it was not the platform. One project put the antenna on a ten-metre mast on the roof with the stock 3 dBi omnidirectional whip. The other bought a "higher gain" 8 dBi antenna and screwed it onto a server cabinet — a metal cabinet, with the base of the antenna buried in a cable tray.

The antenna is the part of a LoRaWAN deployment most often treated as an accessory, and it is the one variable in the link budget that routinely moves it by 10 dB. Gateway transmit power is fixed: GD73 is rated at a maximum of 27 dBm for the -1 suffix and 22 dBm for the -2 suffix (±2 dBm deviation); GD61x and GD62 are 22 dBm maximum for the -2 suffix. Receiver sensitivity is fixed too: these gateways are all specified at -141 dBm (SF12, BW 125 kHz). If both ends of the budget are given, where do the remaining decibels come from?

From the antenna, and from where you put it. This article works through the numbers.

1. Start with the band: the wrong antenna is the first line on the trouble ticket

Official frequency ranges for ManThink gateways:

Region	Frequency range
CN470	470–510 MHz
EU433	433–434 MHz
EU868	863–870 MHz
AS923	920–928 MHz
US902 / US915	902–928 MHz
AU915	915–928 MHz

The documentation states three hard constraints about antennas, and the wording is worth quoting verbatim:

GD61x user guide, step 4: "Confirm the antenna frequency band matches the gateway's regional version."
Note under the GD62 (IP67) specification table: "The RF region must be consistent with the hardware, antenna and end-device configuration."
GD62 pre-installation notes: "Connect the LoRa antenna before powering on. Do not start LoRa transmission with no antenna connected."

These cover three different things.

The first is that the antenna's own frequency range must cover the region the gateway operates in. A whip marked 433 MHz connected to a CN470 gateway is off resonance by roughly 40 MHz, and the VSWR collapses accordingly.

The second is system-level consistency: the gateway's RF hardware version, the antenna and the end devices must all sit in the same region. The mistake usually happens in procurement — a project specified for CN470 ships with an EU868 unit, and nobody notices until nothing joins. The symptom looks exactly like a broken antenna.

The third is a safety constraint, and it is the one installers skip most often: never transmit with no antenna connected. Almost all of the front-end output power reflects back into the power amplifier, and the output stage of a concentrator like the SX1301/SX1302 is not designed to absorb it. "Gateway powered up and never demodulated another packet again" traces back to exactly this — mains plugged in before the antenna was tightened.

So step one is not comparing parameters. Step one is checking: the RF region on the rating plate, the frequency range printed on the antenna label, and the regional configuration on the end devices. All three must agree before anything else happens.

2. Three things that matter more than the gain number

An off-the-shelf LoRa antenna label usually shows gain, VSWR, polarization and connector type. Buyers look at the first line. The other three decide whether the deployment works.

The unit trap: dBi vs dBd

Antenna gain uses one of two reference bases: dBi references an ideal isotropic radiator, dBd references a half-wave dipole. The conversion is fixed:

0 dBd = 2.15 dBi
dBi value = dBd value + 2.15

The same physical antenna labelled 5 dBi or 2.85 dBd is the same antenna. Compare two products without normalising units and you invent 2.15 dB out of nothing — which, by the worked example in section 4, is roughly 18% of coverage radius appearing and then disappearing again.

Gain is not amplification, it is redistribution

This has to be understood before any selection is made. A passive antenna generates no energy; gain comes from concentrating radiation into preferred directions at the expense of others. For an omnidirectional antenna, that means flattening the vertical lobe, paid for with nulls directly above and below the antenna.

A 2 dBi omnidirectional antenna typically has a vertical half-power beamwidth of 60–80 degrees. Push it to 6–8 dBi and that may drop to 15–25 degrees. This is the physical reason behind "high-gain antenna on the roof, nothing works on the floor below" — the antenna is doing exactly what it was designed to do, which is send energy to the horizon.

Indoor scenarios are worse. A gateway antenna flush-mounted to the ceiling of a 3 m machine room, with end devices spread from basement to third floor, will favour the middle floor with a high-gain whip while the top and bottom get weaker than they would with a 2 dBi one.

VSWR measures how much energy never leaves

VSWR describes the impedance match between antenna and feeder. Ideal is 1.0. The usual engineering reading is:

VSWR	Reading	Return loss	Mismatch loss
≤ 1.5	Good	≥ 14 dB	≤ 0.18 dB
1.5 – 2.0	Acceptable	9.5 – 14 dB	0.18 – 0.51 dB
2.0 – 3.0	Investigate	6 – 9.5 dB	0.51 – 1.25 dB
> 3.0	Fail	< 6 dB	> 1.25 dB

Note the last column: even at a VSWR as poor as 3.0, the power actually wasted is only 1.25 dB. The mismatch loss itself is rarely what kills you. What kills you is what a high VSWR reveals — the antenna is not resonant anywhere near the band you are using. That is where the missing fifteen decibels went.

Antennas for low bands such as 470 MHz are physically large, and many products are electrically shortened to fit, which narrows bandwidth and reduces efficiency. This is why you select by regional band rather than buying a generic "LoRa antenna".

Polarization: twenty dB or more, silently

LoRaWAN end devices and gateways normally use linear polarization, installed vertically by default. If a device antenna is laid sideways inside an enclosure, or a meter is mounted on its side in a pit, the polarization plane rotates.

Polarization mismatch loss follows a cosine-squared relationship: roughly 3 dB at 45 degrees, about 10 dB at 70 degrees, and approaching full loss at 90 degrees — in practice a 20 dB-plus drop. It is notoriously hard to diagnose, because "the device loses packets ten metres directly below the gateway" appears to make no sense at all until you stand the device upright and it works.

3. The link budget: account for every decibel

Selection by feel is a gamble. This is arithmetic. The power balance for an uplink is:

Received power = device Tx power + device antenna gain − path loss − obstruction loss − feeder loss − connector loss + gateway antenna gain

Solving the inequality gives the maximum allowable path loss:

Allowable path loss = device Tx power + device antenna gain + gateway antenna gain − gateway sensitivity − feeder loss − connector loss − obstruction loss − design margin

Every term is measurable or documented. Fill them in one by one.

Free-space path loss

FSPL (dB) = 32.44 + 20·log₁₀(distance in km) + 20·log₁₀(frequency in MHz)

Free-space loss at three common LoRaWAN bands:

Distance	470 MHz	868 MHz	915 MHz
1 km	85.9 dB	91.2 dB	91.7 dB
2 km	91.9 dB	97.2 dB	97.7 dB
5 km	99.9 dB	105.2 dB	105.7 dB
10 km	105.9 dB	111.2 dB	111.7 dB

Note the frequency term: at the same distance, 470 MHz loses 5.8 dB less than 915 MHz. That is the natural advantage of the lower Sub-GHz band, and the reason CN470 deployments often show better coverage than US915 ones at equal power — not better hardware, just physics.

Real environments replace n

Free space assumes a path loss exponent of n = 2. Practical values:

Environment	Path loss exponent n	Loss per doubling of distance
Free space / clean line of sight	2.0	6 dB
Suburban / open campus	2.5 – 3.0	7.5 – 9 dB
Built-up urban	3.0 – 3.5	9 – 10.5 dB
Dense indoor	3.5 – 4.5	10.5 – 13.5 dB

Applied on top of the 1 km reference:

PL (dB) = FSPL(1 km) + 10·n·log₁₀(distance in km) + obstruction loss

A worked example

Scenario: CN470, an open campus with mostly outdoor installations. A GD73 (-2 suffix, 22 dBm) with a 3 dBi omnidirectional antenna at the top of a ten-metre mast. Gateway side: 1.5 m of LMR-400 plus two connectors. End device: a KC11 DTU transmitting at 14 dBm with a 0 dBi stub, inside an outdoor meter box. Target SF12, BW 125 kHz, gateway sensitivity -141 dBm.

Gateway-side losses line by line:

Item	Value	Note
Feeder, LMR-400 @ 470 MHz, 1.5 m	0.13 dB	≈ 0.09 dB/m
Two connectors	0.40 dB	≈ 0.2 dB each
Gateway-side total	0.53 dB	count as 0.6 dB

Maximum allowable path loss:

14 dBm (device Tx) + 0 dBi (device antenna) + 3 dBi (gateway antenna) − (−141 dBm) (gateway sensitivity) − 0.6 dB (feeder and connectors) − 20 dB (box penetration and clutter) − 10 dB (design margin)
= 127.4 dB

Back-solving distance at n = 3.0:

85.9 + 30·log₁₀(d) ≤ 127.4
log₁₀(d) ≤ 1.383
d ≤ 24 km

Which is obviously larger than any real campus deployment. Section 5 explains why. The point here is this: the power budget is inherently generous, which means the real constraint on LoRaWAN coverage is almost never transmit power — it is antenna placement and environment.

4. Feeder cable: the easiest 3 dB to throw away

In the example above the feeder accounted for only 0.6 dB, because it was LMR-400 and only 1.5 m long. Change one of those two things and the picture changes quickly.

Typical coaxial cable attenuation in the Sub-GHz range:

Cable type	@ 470 MHz	@ 900 MHz	Total over 3 m @ 470 MHz
RG-58	≈ 0.35 dB/m	≈ 0.57 dB/m	≈ 1.05 dB
RG-213	≈ 0.20 dB/m	≈ 0.32 dB/m	≈ 0.60 dB
LMR-400	≈ 0.09 dB/m	≈ 0.13 dB/m	≈ 0.27 dB
1/2" corrugated copper feeder	≈ 0.02 dB/m	≈ 0.03 dB/m	≈ 0.06 dB

Add connectors at roughly 0.1–0.3 dB each in this range, counting an adapter (N-type to SMA, say) as two.

All small numbers. Two observations follow.

First, feeder loss applies in both directions. Ten metres of RG-58 costs 3.5 dB on receive and another 3.5 dB on transmit. That is why "keep the gateway in the rack and run a long feeder up to the roof" is a bad plan — you lose 3.5 dB at each end, roughly 55% of the power in each direction.

Second, remember what 3 dB is. It is half the power. A cheap ten-metre run can take a 22 dBm radio down to well under half its effective radiated output. The care you put into choosing antenna gain is easily wiped out by the cable you saved money on.

There is only one correct engineering answer: move the gateway closer to the antenna, not the feeder closer to the antenna. A device like the GD62 (IP67), rated for -25 °C to 60 °C with IP67 protection, was designed to be mounted on a pole. Put the antenna on the chassis connector with a short jumper, and run Ethernet/PoE back to the rack — 100 m of Ethernet costs nothing in RF terms, 10 m of feeder costs decibels.

Where a long feeder is genuinely required for lightning protection or routing, spend the money on the cable instead: 1/2" feeder loses about 0.02 dB/m at 470 MHz, so 20 m costs only 0.4 dB. It needs adapters and demands better workmanship, but it is money well spent.

5. Antenna height matters more than antenna gain

Back to that absurd 24 km. Where did it come from?

Height. LoRa in the Sub-GHz bands is substantially quasi-line-of-sight, and the real limiter is often the radio horizon. With standard atmospheric refraction (4/3 Earth radius):

Radio horizon (km) ≈ 4.12 × (√h₁(m) + √h₂(m))

where h₁ is gateway antenna height and h₂ is device antenna height. Taking the device at 1.5 m:

Gateway antenna height	Radio horizon	vs 2 m
2 m (top of a cabinet, within arm's reach)	≈ 10.6 km	baseline
5 m (second floor, external wall)	≈ 12.5 km	+18%
10 m (roof mast)	≈ 14.6 km	+38%
20 m (tower)	≈ 17.9 km	+69%

Compare that with changing antennas. Going from 3 dBi to 8 dBi buys 5 dB, which at n = 3 improves coverage radius by a factor of about 1.47 (+47%). Raising the antenna from 2 m to 10 m extends the horizon by about 38%.Comparable numbers, but there is one essential difference:

Height costs you nothing. Gain costs you vertical coverage nearby.

And in urban environments you never reach the horizon anyway; obstruction dominates. That is where height wins outright: ten metres up usually means the antenna has cleared the building edge and moved away from every reflective surface on a metal roof. No amount of gain goes through a building.

So the selection order should be:

Win the height first — find the highest compliant mounting position.
Then pick the right gain, not the highest gain.
Choose cable and connectors last — although this is where the cheapest decibels usually are.

6. Verify uplink and downlink separately

This is a very common trap. During commissioning the uplinks look rock solid and everyone signs off on coverage. A week later ADR is not taking effect, Join Accepts are missing, and downlink commands need three retries.

The reason is that the two directions do not balance. Four points:

First, gateway sensitivity is usually better than device sensitivity. ManThink gateways are specified at -141 dBm (SF12, BW 125 kHz). Common device radios such as the SX1262 sit around -137 dBm — roughly 4 dB worse.

Second, gateway transmit power is usually higher. GD73 delivers up to 27 dBm (-1) or 22 dBm (-2); a typical LoRaWAN device transmits at 14 dBm. Another 8–13 dB in the gateway's favour.

Third, many regions impose a separate limit on gateway downlink EIRP. Under the ERC 70-03 framework commonly applied to EU868, most sub-bands cap EIRP at 25 mW (14 dBm), with 500 mW permitted in 869.4–869.65 MHz subject to duty-cycle conditions. That pulls gateway downlink EIRP down to roughly the device's level, leaving the 4 dB sensitivity advantage as the only compensation — so the downlink breaks first, inevitably. Always confirm current limits against the local spectrum authority's regulations and the equipment's type approval.

Fourth, feeder loss is bidirectional. Those 3 dB on the gateway side hurt both links, and in most self-built deployments only the gateway has a feeder at all.

Conclusion: always run two budgets. The uplink budget decides whether you receive data. The downlink budget decides whether joins, ADR and downlink commands work at all. Many two-way applications — valve control, remote verification, configuration pushes, FUOTA — fail on the downlink, not the uplink.

The simplest field test: once installed, perform a join with a real device at the furthest point. A join is inherently bidirectional — the device sends a Join Request and must receive the Join Accept for the join to succeed. A missing 3 dB in either direction shows up there first.

7. Selecting by scenario: five typical combinations

Applying the above to concrete hardware, using documented specifications:

Gateway	Form factor and key specs	Antenna and installation approach
GD61x / GD62 (IP67)	ESP32-S3 + SX1301/SX1302; GD62 is IP67, -25 to 60 °C, 164 × 124 × 50 mm, wall or pole mount, gwTool6 configuration, web OTA with A/B dual firmware partitions	Compact and pole-mountable; connect the antenna with a short jumper. Suited to dense, low-cost single-point coverage
GDI51	Ubuntu gateway with ThinkLink built in (LS1012A); 8 frequency points / 16 demodulators / 65 logical channels; sensitivity -141 dBm; PoE or Type-C	Indoor coverage for smart buildings. Prefer a 2–3 dBi antenna designed for floor-to-floor coverage rather than high gain
GD73	SX1302; type A 8 frequency points / type D 16; `-1` up to 27 dBm, `-2` up to 22 dBm; sensitivity -141 dBm	Projects requiring at least 25 dBm must specify the `-1` version. Suited to campus-scale distance, with a proper mast and low-loss feeder
GDO51	Outdoor IP67; up to 16 frequency points / 32 demodulators / 130 logical channels; sensitivity -141 dBm; PoE / 4G / Wi-Fi / Ethernet / GPS; external SIM slot and debug port; published reference price USD 345 (about ¥2,315, subject to current quotation)	Outdoor and demanding sites. Full outdoor waterproofing is mandatory; connect LTE, GPS and Wi-Fi antennas to their matching labelled ports

One variable is still routinely forgotten: the gateway and the end devices must be in the same regional band. Worth restating because export projects get this wrong more than anything else — CN470 is 470–510 MHz and EU433 is 433–434 MHz. One character differs on the purchase order; the antennas are entirely different.

And a note on product positioning. The GD6 series is an entry-level, edge-side form factor suited to single-point coverage and functional validation. Building-scale and industrial deployments generally need devices with more channels, more demodulators and higher reliability designs — GDI51, GD73 or GDO51. Do not expect an edge-class device to carry a building-scale network's capacity just because you changed the antenna.

8. Ten installation steps, straight from the manuals

Merging the installation requirements from the GD61x, GD62 (IP67) and GD72 manuals gives ten steps. The first three are done with the power disconnected:

Step 1. Confirm the device is powered off and that the LoRa antenna matches the gateway band.
Step 2. Connect the LoRa antenna to the LoRa / RF port and tighten it, letting the connector seat naturally — do not force-twist the connector body.
Step 3. If external Wi-Fi or 4G antennas are supplied, fit them to the matching labelled ports — LTE, GPS/BDS and Wi-Fi each have their own.
Step 4. For cellular backhaul, insert the SIM card, then fit the waterproof cover.
Step 5. For wall mounting, mark out to the bracket hole pattern and use fixings appropriate to the wall material. For pole mounting, check the pole diameter first — the GD72 manual gives a range of 30–52 mm — fit the clamp and tighten evenly.
Step 6. Keep the correct orientation per the supplied installation drawing; the GD72 manual explicitly requires "keep the gateway facing upwards".
Step 7. Leave room for the antenna, connectors and cable bending radius. Never let the cable's weight pull directly on a connector.
Step 8. Route the Ethernet cable through the supplied waterproof gland in assembly order (the seal must match the cable outside diameter), seat the RJ45, then tighten.
Step 9. Complete the waterproofing check, then apply power.
Step 10. Watch the status: the GD61x normal operating indication is an LED slow flash, 1 s on / 1 s off.

Four points on waterproofing

The GD72 manual provides a checkable list. Verify against it:

Every outdoor antenna connector is sealed according to site practice — insulating tape, self-amalgamating tape or dedicated waterproofing material suitable for outdoor use, applied so that it fully covers the joint and forms a continuous seal.
Priority areas: cable entries, antenna ports, SIM card cover, power and network ports.
Drip loop: always leave one, so rain cannot track along the cable into a connector.
Unused ports stay sealed with their original plugs, fitted and tightened.

Two more points on outdoor power: PoE adapters and any supply not rated for outdoor use must sit in a dry location or a suitable enclosure, and the GD72 manual adds that the adapter should be mounted vertically with its ports facing down.

And one point that is easy to forget because it lives on a different timescale:

Inspect sealing material periodically and replace it promptly if aged, cracked or loose.

Where to mount it — and where not to

Drawing on the GD62 (IP67) "Before Use" section and the propagation analysis above:

Avoid: standing water, heat sources, inside metal roofs or cable trays, electrical risers containing high-power equipment, anywhere permanently shadowed by heavy machinery.

Prefer: high points, open aspects, and positions a maintenance technician can reach safely.

Mind the stated environmental limit too: the actual ambient temperature at the mounting position must stay within -25 °C to 60 °C.

9. Six things you must not do

These are the prohibitions written into the documentation. Ignore them and no warranty applies:

Prohibition	Official wording
Transmitting with no antenna	"Connect the LoRa antenna before powering on. Do not start LoRa transmission with no antenna connected."
Mismatched band and accessories	"The RF region must be consistent with the hardware, antenna and end-device configuration." / "Confirm the antenna frequency band matches the gateway's regional version."
Choosing a supply by port name	"Before connecting PoE, check the supply standard, voltage and wiring requirements. Do not select a power source based on the port name alone."
Multiple supplies at once	"Do not connect multiple power sources simultaneously unless expressly permitted in the delivery documentation."
Overvoltage on Type-C / wrong terminals	"Do not apply more than 5 V to the Type-C port. Do not connect a supply to the A+ / B- terminals."
Opening the enclosure or modifying seals	"Do not open the enclosure or modify the sealing structure without authorisation."

Two protection limits from the GD72 manual:

IP67 does not mean submersible: the IP67 rating applies with the enclosure intact and seals and connectors correctly assembled. The unit is not intended for prolonged immersion, and interfaces must not be washed with a high-pressure jet.

These six prohibitions and two limits are the complete set of installation-related restrictions stated in the manuals.

And one operational sequence, from the GD61x manual:

Do not disconnect power during a firmware upgrade, configuration write or factory reset.

10. Commissioning: how to read RSSI and SNR

Finishing the installation is not the end of acceptance testing; it is the start. Two values need recording: RSSI (received signal strength) and SNR (signal-to-noise ratio). They mean quite different things, and reading them together without understanding both leads to wrong conclusions.

SNR decides whether demodulation is possible at all. LoRa is a spread-spectrum modulation, and demodulation depends on the signal exceeding the demodulation threshold for that spreading factor. Typical values from Semtech transceiver datasheets:

Spreading factor	Typical SNR demodulation threshold
SF7	≈ −7.5 dB
SF8	≈ −10 dB
SF9	≈ −12.5 dB
SF10	≈ −15 dB
SF11	≈ −17.5 dB
SF12	≈ −20 dB

The key point: a negative SNR is normal. Demodulating below the noise floor is the whole point of spread spectrum. An SNR of -12 dB is perfectly healthy at SF10.

RSSI tells you how much margin is left. Its absolute value means little on its own — a gateway with -141 dBm sensitivity receiving -115 dBm still has 26 dB of margin, while the same signal at a device with -137 dBm sensitivity leaves only 22 dB. Always read RSSI against the receiver's sensitivity.

Practical acceptance bands:

SNR and RSSI	Reading	Action
SNR ≥ −5 dB, RSSI ≥ −100 dBm	Plenty of margin	Let ADR reduce the data rate and save device power and channel occupancy
SNR −10 to −5 dB, RSSI −110 to −100 dBm	Healthy	Normal operation
SNR close to the SF threshold (margin < 5 dB)	Marginal	Record and re-measure; weather and clutter changes will drop it
SNR below threshold, or RSSI < −125 dBm	Unusable	Check antenna, placement and feeder. Do not paper over it by raising the SF further

Record three things per point: RSSI, SNR, and the SF in use at the time. The same RSSI means completely different margins at SF7 and SF12, and future capacity planning is impossible without the third number.

Also plan for at least two measurement rounds: a baseline at installation, and a re-measurement one to two months later. Antennas and connectors degrade gradually, and a poorly sealed connector commonly shows a 5–10 dB RSSI drop within two months.

11. One page for the field team

A checklist to hand out at project kick-off.

Selection

Confirm the RF region for the gateway suffix; the antenna's frequency range must cover the corresponding band (CN470: 470–510 MHz).
Normalise dBi and dBd before comparing gain. Prefer 2–3 dBi for indoor and dense short-range deployments; consider 5–8 dBi for open line-of-sight.
Confirm VSWR ≤ 2.0 across the operating band (prefer ≤ 1.5). Ask suppliers for a measured sweep across the band, not a single-spot figure.
Decide between the -1 (27 dBm) and -2 (22 dBm) versions, and check local EIRP limits for the band.
Look feeder losses up against the actual band. Beyond three metres, use LMR-400 or better, and keep the connector count down.

Installation

Work de-energised. Antenna on before power.
Match LTE / GPS / Wi-Fi antennas to their labelled ports; never swap them.
Win the height: clear the building-obstruction zone at minimum, ten metres or more where possible.
Waterproof completely: self-amalgamating tape, continuous seal, drip loop, original plugs on unused ports.
Keep the PoE adapter dry, mounted vertically with ports facing down, and not sharing duty with another supply.

Acceptance

Perform a real join at the furthest point to confirm the downlink works.
Record RSSI / SNR / SF for every point as the baseline.
Re-measure after one to two months and compare.

Conclusion

LoRaWAN link budgets usually look like this: twenty or thirty dB of theoretical headroom, and an actual outage caused by an unloved antenna sitting on top of a rack.

The real cause is rarely that the power budget does not add up. It is almost always one of three small things: the antenna is not resonant in the band you are using, the feeder silently ate 3 dB, or the antenna was never taken somewhere it can see the target.

None of the three is expensive, and none appears on the gateway's price list. They show up in the budget under a different heading: the second visit. And the third.

Which is why selection and installation belong in the design phase, not at the tail end of construction.

DEV Community