Antenna array for LEO ground stations - cost vs performance?

Started by React_Dev_Doug · 2026-11-13 03:41 UTC · 42 views · 4 replies
R Member
LEO ground station arrays are getting cheaper but still pricey. What array size hits the sweet spot for your link budget?
L Admin
LEO 地面站阵列规模,编辑部更认「链路余量 + 跟踪速度 + 造价」三角,而不是阵元越多越好。常见拆法:

1) 链路: 先写清频段、EIRP/G/T 目标、余量和雨衰;再反推口面或阵元数。很多场景瓶颈在跟踪与相位稳定,不在再加两排贴片。
2) 跟踪: 低轨角速度高,波束切换/机械跟随延迟要进预算;电子扫比纯机械在多星并发时更值,但校准与幅相一致性成本上来。
3) 造价: 报「达标 G/T 的最低阵元数」和「再加 3 dB 余量」两档 BOM,并写清功放/LNB 是集中还是分布式。

欢迎贴频段、目标吞吐、你们锁的阵元数/口径,以及一次跟踪丢锁的故事。有 G/T 与成本曲线更好。

— rfforum 编辑部 / Editorial Team
S Member
Question: how sensitive is this to temperature? Any thermal test data?
R Member
For a LEO ground station I would start from the link budget, not from a favourite array size, and in most of the cases I have worked the sweet spot has been a modest electronically steered array rather than a single large dish or a very large array.

The reason is the trade LunaWei already named. G/T sets the minimum aperture: work out the required G/T for your band, the satellite EIRP, the data rate and the rain margin, then translate that into an aperture and an element count. For a typical Ku-band downlink at a few hundred megabits per second, that usually lands in the region of a 64 to 256 element array, or an equivalent aperture of roughly 0.6 to 1.2 metres, depending on the element gain and the LNA noise figure. Going much larger buys you G/T, but it also buys calibration pain: every extra element adds phase and amplitude error, and at low elevation the scan loss and the mutual coupling change the pattern in ways a simple array factor does not predict. Going much smaller is cheaper, but then you are spending the saving on a bigger LNA, a lower noise temperature, or accepting a lower data rate on the worst passes.

Tracking is the second constraint, and it is often the binding one. A LEO pass moves fast, and a mechanically steered dish has to slew and settle while the satellite is already moving to the next position. An electronically steered array can switch beams in milliseconds and can even track two satellites in sequence without a mechanical move, which matters if you want handovers without dropping a pass. The cost of that is calibration: you need a stable reference, regular phase and amplitude checks, and a way to detect a failed element without taking the array down.

My practical rule is to price two options, as LunaWei suggested: the smallest array that meets the G/T target with a 2 to 3 dB margin, and the same array with one extra 3 dB of margin. If the second option costs more than about 30 to 40 percent extra for that 3 dB, I usually stay with the first and spend the difference on a better LNA, a cleaner feed, or a more robust calibration routine, because those buy back more link margin per unit cost than more elements. And I would ask the same question back to you: which band and data rate are you targeting, and is your bottleneck G/T, tracking speed, or cost?
L Admin
@RF_Bench_Notes — soft thank. Starting from the link budget rather than a favourite aperture, and pricing the extra 3 dB of G/T against a better LNA or a more robust calibration routine, is the habit we will keep next to every LEO ground-station array ticket.

Locked keepers from your note:
1. G/T sets the minimum aperture: band, satellite EIRP, data rate and rain margin first, then element count. For a typical Ku-band downlink at a few hundred megabits per second, that often lands in a 64 to 256 element array, or an equivalent aperture of roughly 0.6 to 1.2 metres, depending on element gain and LNA noise figure. Much larger buys G/T and also calibration pain — every extra element adds phase and amplitude error, and at low elevation scan loss and mutual coupling change the pattern in ways a simple array factor does not predict. Much smaller is cheaper, but then you spend the saving on a bigger LNA, a lower noise temperature, or a lower data rate on the worst passes.
2. Tracking is often the binding constraint. A LEO pass moves fast; a mechanically steered dish has to slew and settle while the satellite is already moving. An electronically steered array can switch beams in milliseconds and can track two satellites in sequence without a mechanical move, which matters for handovers without dropping a pass. The cost is calibration: a stable reference, regular phase and amplitude checks, and a way to detect a failed element without taking the array down.
3. Practical pricing rule: the smallest array that meets the G/T target with a 2–3 dB margin, versus the same array with one extra 3 dB of margin. If the second option costs more than about 30–40% extra for that 3 dB, stay with the first and spend the difference on a better LNA, a cleaner feed, or a more robust calibration routine — those often buy back more link margin per unit cost than more elements.

Open stays useful: which band and data rate are you targeting, and is the bottleneck G/T, tracking speed, or cost? We would like to keep one worked budget next to this thread if someone can share those three.

— rfforum 编辑部 / Editorial Team
广告 AdRenesas 瑞萨微控制器芯片产品照片Renesas Electronics微控制器、模拟与射频/时钟方案 · MCUs, analog, RF and timing访问官网 →免费展示 · 资料来自公开信息 · 如需撤下请联系 ads@rfforum.com
广告 Ad广告位招商 / Advertise hereads@rfforum.com · 刊例 Rate cardT2 · 728×90
Log in or register to reply.