ACM (Adaptive Coding and Modulation) in VSAT: How It Works and Why It Matters

Published by Bravosatcom · VSAT Engineering Series

ACM — Adaptive Coding and Modulation — is the feature that most dramatically changed VSAT economics after DVB-S2 introduced it in 2005. Before ACM, every VSAT link had to be designed for worst-case propagation conditions, wasting expensive satellite capacity during the 99% of the time conditions are better than worst case. ACM eliminates that waste by continuously adjusting the modulation and coding rate to match actual channel conditions in real time.

The Problem ACM Solves

Every satellite link has a link budget: a calculation that determines the minimum signal margin required to maintain the target availability (e.g., 99.5% of the time). In Ku-band, the main variable that depletes margin is rain fade — heavy rainfall attenuates the signal, reducing the carrier-to-noise ratio at the receiver.

Without ACM (called “fixed coding” or CCM — Constant Coding and Modulation), the link must be designed to remain operational during the worst rain events that occur within the required availability window. For a 99.5% availability target at a Gulf location, this might be 4–6 dB of rain margin. That 4–6 dB of margin is “safety stock” that the link never actually uses during the other 99%+ of operating time — it represents paid-for satellite capacity that delivers no throughput.

ACM converts that margin buffer into usable throughput. During clear sky, the link runs at the highest modcod the signal supports (e.g., 32APSK 5/6, 4.17 bits/Hz). When rain starts and SNR drops, the hub detects the degradation and steps down to a lower, more robust modcod (e.g., 8PSK 3/4, 2.25 bits/Hz). The link stays up throughout; throughput decreases during rain and recovers afterward. No manual intervention is required.

How ACM Works in Practice

ACM adaptive coding modulation VSAT modcod changes during rain event — Figure 1 — ACM modcod selection during a 60-minute period with a 30-minute rain event. The system automatically steps down from 32APSK 5/6 to QPSK 3/4 during peak rain and recovers as conditions improve.

ACM vs. Fixed Coding: Capacity Comparison

ACM vs fixed coding VSAT capacity utilisation comparison — Figure 2 — ACM vs. fixed QPSK 3/4 capacity during clear sky, light rain, and heavy rain. ACM delivers 2.78× the throughput of a fixed worst-case modcod during clear-sky conditions.

ACM System Architecture

ACM VSAT system architecture hub remote Eb/No feedback loop — Figure 3 — ACM operates as a closed-loop system. Remote terminals report their Eb/No every 100–200 ms. The hub NMS selects the optimal modcod per remote and adjusts the outbound carrier in real time.

ACM in Star vs. Mesh Topologies

ACM is straightforward in a star topology, where the hub controls the outbound carrier modcod per remote. In a mesh topology (remote-to-remote direct links), each link has its own ACM loop, which increases signalling complexity. Most commercial VSAT platforms (iDirect, Comtech, Newtec) implement ACM primarily on the hub-to-remote (outbound) direction. Return-link ACM (remote-to-hub) is also supported by most modern platforms and follows the same principle, with the hub monitoring each remote’s inbound signal quality and commanding modcod changes.

Practical Limits of ACM

ACM is not magic. The modcod can only step up to the maximum supported by the terminal’s SNR. If the satellite beam EIRP is low (edge of footprint) or the antenna is small, the clear-sky SNR may not support high-order modulation regardless of ACM. ACM maximises utilisation of whatever margin exists, but it cannot create margin that the link budget does not provide.

Additionally, ACM requires a return channel for the SNR feedback from the remote to the hub. In a broadcast-only (one-way) DVB-S2 link, pure ACM is not possible — VCM (Variable Coding and Modulation) is used instead, with pre-assigned per-slot modcods rather than real-time feedback.

Frequently Asked Questions

Does ACM affect latency?

The modcod change itself is nearly instantaneous (one or two frames, <1 ms). The latency impact comes from the reduced throughput during rain events — if your application generates 10 Mbps of traffic and ACM drops the link to 4 Mbps during heavy rain, TCP queuing increases. Application-level latency is therefore higher during rain events. GEO satellite propagation delay (550–600 ms RTT) is unchanged by ACM.

How quickly does ACM respond to a rain event?

Modern ACM implementations respond within 200–500 ms of a detected SNR drop, depending on the platform. The hub measures Eb/No from each remote on every return frame (typically 100 ms intervals), compares it to the modcod threshold table, and issues a modcod change command if needed. The remote updates its demodulator lock within one or two outbound frames after the command.

Does my modem need to support ACM specifically?

Yes. ACM requires both the hub modem and the remote modem to support the ACM signalling protocol. Both the DVB-S2 and DVB-S2X standards define ACM signalling in the Physical Layer Header (PLHeader). Proprietary ACM extensions exist (e.g., iDirect’s Mx-DMA), but mixing equipment from different manufacturers on an ACM network requires careful verification. For VSAT networks using iDirect or Comtech hubs, the remote modems must be from the same platform ecosystem to use ACM.