LoRaWAN Adaptive Data Rate (ADR) Animation
Watch how LoRaWAN ADR turns uplink SNR history into spreading-factor and transmit-power commands
LoRaWAN Adaptive Data Rate Workbench
Watch the network server collect uplink SNR, calculate link margin, then command a lower spreading factor or transmit power only when the safety buffer is strong enough.
What
ADR is a network-server feedback loop that adjusts LoRaWAN data rate and TX power from measured link quality.
Why
Lower SF means shorter airtime, less battery drain, and less channel occupancy, but only if the link still has margin.
Try First
Select Rooftop meter. The strong SNR lets ADR move from SF12 toward SF7 and then reduce transmit power.
Notice
ADR is not a mobility fix. Moving devices can leave the coverage conditions that ADR optimized for.
ADR decision model
Rooftop meter: stable link, 20 uplinks, ADR enabled, current SF12 at 14 dBm.
Network feedback loop
SNR history and margin
Spreading factor ladder
Current server message
LinkADRReq can be scheduled. The command requests a new data rate and TX power. The device validates the request, applies it if supported, then answers with LinkADRAns status bits.1. Uplink
Device sends an uplink with the ADR bit set when it allows network optimization.2. Measure
Gateways attach SNR/RSSI metadata. The server keeps recent best-gateway SNR values.3. Calculate
Server compares max recent SNR with the required SNR and installation margin.4. Command
LinkADRReq asks for a new data rate, TX power, channel mask, or redundancy setting.5. Apply
Device validates the request and replies with LinkADRAns acceptance bits.Learning Support
Minimum Background
SNR is signal quality in dB. Spreading factor trades data rate for sensitivity: SF7 is fast, SF12 is slow but easier to decode.
Mental Model
ADR is like choosing the quietest reliable speaking mode. If the listener hears clearly, speak faster and use less power.
Network Role
The network server has gateway measurements and sends LinkADRReq. The device does not invent these server commands locally.
Stable Devices
Use ADR for meters, environmental sensors, and fixed assets where radio conditions change slowly enough for history to matter.
Mobile Devices
Disable ADR for moving trackers unless the implementation can detect instability. The optimized SF may become unsafe after movement.
Not Instant
ADR needs recent uplinks and a downlink opportunity. It is a slow optimization loop, not a per-packet rescue mechanism.
Quick Reference
Margin Formula
ADR margin = max recent SNR - required SNR for current data rate - installation margin.
Step Formula
Teaching model: Nstep = floor(ADR margin / 3 dB). Positive steps optimize; negative steps add robustness.
Required SNR
Typical LoRa thresholds: SF7 -7.5, SF8 -10, SF9 -12.5, SF10 -15, SF11 -17.5, SF12 -20 dB.
EU868 DR Mapping
DR5 is SF7, DR4 is SF8, DR3 is SF9, DR2 is SF10, DR1 is SF11, and DR0 is SF12 for BW125.
LinkADRReq
Contains DataRate, TXPower, channel mask, and redundancy fields. The device validates all requested changes before applying them.
ADR_ACK_CNT
After many uplinks without downlink, a device can set ADRACKReq and eventually move toward more robust settings.
Guided Practice
Strong Link
Use Rooftop meter. Reduce the installation margin and watch the recommendation become more aggressive.
Weak Link
Use Rural edge node. Notice that SF12 may be kept because there is no spare margin to trade away.
Not Enough History
Set recent uplinks below 20. The server collects data instead of immediately sending a data-rate change.
Mobile Risk
Use Mobile tracker. ADR is disabled because a good SNR history from one location may not fit the next location.
Downlink Silence
Raise uplinks since last downlink above 64, then above 96. Watch the ADRACKReq and fallback explanation change.
Field Check
Compare recommendation with packet delivery, gateway diversity, interference, duty cycle, and regional data-rate limits.