LoRa & LoRaWAN · Study deck

LoRa Modulation and Spreading Factors

Picture a field sensor whose short message barely reaches the receiver.

Radio Remi is your guide for this deck.

loramodulation

Radio Remi, the module guide, in a scene from this chapter.

After studying this chapter

Learning objectives

You will be able to:

"Explain LoRa chirp spread spectrum, spreading factor, and symbol-time tradeoffs"
"Connect bandwidth, coding rate, payload, and retries to airtime evidence"
"Write bounded modulation review records with link evidence and retest triggers"
"Evaluate when ADR can own data-rate changes and when manual boundaries are safer"

Major section

Start Simple

Making the radio easier to hear may keep it on air much longer, which costs energy and shared channel time.

The first comparison changes one setting and measures both effects.
Bandwidth means the range of radio frequencies used to carry a signal.
Modulation means changing a radio signal over time to carry information.

Major section

Start Simple (continued)

A payload means the useful reading or command inside a message.

Weaken the path, repeat the packet, change one setting, and restart the receiver.
This runway does not prove coverage, legal compliance, or fleet capacity from one bench link.
The deeper sections explain chirps, spreading, coding, data rate, airtime, sensitivity, regional limits, and measured trade-offs.

Major section

Overview: LoRa Modulation Turns Radio Settings Into Airtime Evidence

LoRa is the physical radio modulation used by LoRaWAN.

LoRaWAN adds the network behavior around that radio, but modulation review starts with radio settings, payload size, observed link evidence, and time on air.
The beginner mistake is choosing the highest spreading factor by habit.
A simple scale check keeps the tradeoff concrete.

Calculated LoRa SF10 symbol-256 spectrogram at 125 kHz, starting 31.25 kHz above the channel's lower edge and wrapping at 6.144 ms within an 8.192 ms symbol. Below, a zero-based bar chart plots SF7 through SF12 symbol times of 1.024, 2.048, 4.096, 8.192, 16.384, and 32.768 milliseconds. — A calculated SF10 LoRa chirp sweeps across a 125 kHz channel. At the same bandwidth, each step from SF7 to SF12 doubles symbol duration, from 1.024 ms to 32.768 ms; complete packet airtime also includes payload and protocol overhead.

Major section

Overview: LoRa Modulation Turns Radio Settings Into Airtime Evidence (continued)

At SF12 it is about 32.768 ms, or 32 times longer before payload, preamble, header, coding-rate, and retry details are counted.

Higher spreading factors can help weak links, but they also keep the channel occupied longer.
Spreading FactorControls symbol duration.
BandwidthDefines the channel span used by the chirp.

Major section

Overview: LoRa Modulation Turns Radio Settings Into Airtime Evidence (continued)

A defensible choice records why the setting fits the device group, message schedule, gateway evidence, regional profile, and ADR handoff.

If you only need the intuition, this layer is enough: spreading factor is not a quality slider.
Lower settings reduce airtime; higher settings can support weaker links when the evidence justifies the cost.
Coding RateAdds redundancy for error tolerance.
More redundancy can help robustness, but it also adds transmitted symbols.

Major section

Practitioner: Write the Modulation Review Record

The reviewer should not approve "LoRa works" as a broad claim.

The record should say which payload, which message schedule, which regional profile, which gateway evidence, which data-rate or ADR policy, and which retest trigger are in scope.
The review tests one small message but approves every message pattern.

Chirp spread spectrum explains the radio mechanism; the release record still needs observed link and airtime evidence.

Major section

Practitioner: Write the Modulation Review Record (continued)

The chosen data rate is not tied to observed link evidence.

One lab point is treated as field coverage evidence.
Whether ADR owns the final data-rate adjustment, what history it can trust, and when manual override is allowed.
ADR is enabled without a device profile that makes historical evidence useful.

Major section

Practitioner: Write the Modulation Review Record (continued)

Payload, firmware, placement, antenna, gateway, regional profile, ADR policy, or message-schedule change.

The release record has no condition that reopens the review.
ReviseThe setting may be plausible, but the record lacks payload, airtime, field, or ADR evidence for the reviewed scope.
DeferThe reviewer cannot tie the radio setting to a real device group, regional profile, gateway path, or release owner.

Major section

Under the Hood: Symbol Time Drives the Tradeoff

LoRa symbols are represented by chirps.

Spreading factor changes how many possible symbol states are represented and how long each symbol occupies the channel.
A higher spreading factor can make weak-link decoding more practical, but it also extends the time on air for the same payload family.

The raw chirp shape behind the symbol-time formula: each step up in SF doubles the chirp period, so half as many chirps fit in the same window.

Major section

Under the Hood: Symbol Time Drives the Tradeoff (continued)

Airtime affects channel occupancy, retries, downlink opportunities, regional profile fit, battery behavior, and gateway capacity.

ADR can help only when the device pattern gives it useful, recent evidence.
The useful under-the-hood shortcut is T symbol = 2 SF / bandwidth.
The same shortcut can be written as a rate check.

Major section

Under the Hood: Symbol Time Drives the Tradeoff (continued)

Symbol time = 2^SF / bandwidth; complete packet airtime also depends on preamble, header, coding, payload, and retries.

Symbol time measures one symbol duration from the spreading factor and bandwidth.This is the duration of one symbol, not the airtime of a complete packet.
Preamble, header, coding, payload, and retries add packet airtime.Use the full packet structure and confirmed retries when estimating channel use.
Keep the symbol example tied to its stated bandwidth.The 125 kilohertz examples show symbol duration under an idealized calculation.

Symbol time = 2^SF / bandwidth; complete packet airtime also depends on preamble, header, coding, payload, and retries.

Major section

Under the Hood: Symbol Time Drives the Tradeoff (continued)

A field record that says "SF12 worked once" therefore proves only a narrow reception event unless it also shows the payload family, traffic count, retry rate, gateway diversity, and regional airtime headroom.

If a fixed meter has weeks of stable uplinks, ADR may be able to move it toward a lower spreading factor and return channel capacity.
If a tracker moves between basements, loading docks, and outdoor yards, old uplinks can overstate the current margin.
The review should name when ADR owns the decision, when a manual boundary is safer, and which movement or gateway change reopens the calculation.

Major section

Under the Hood: Symbol Time Drives the Tradeoff (continued)

Symbol DurationLonger symbols can support weaker links, but every longer frame also consumes more shared channel time.

Payload CouplingHeaders, MAC commands, joins, retries, acknowledgements, and encoded payload size all change the airtime record.
ADR LimitsADR is strongest for relatively stable devices with useful history.
Mobile or bursty devices may need narrower review boundaries.

Major section

Summary

Its coded rates are idealized calculations, so use the regional data rate for an airtime record.

One LoRa symbol is one chirp.
LoRa modulation review connects radio settings to evidence.
Spreading factor, bandwidth, coding rate, payload size, regional profile, gateway evidence, and ADR policy all affect whether a LoRaWAN message pattern is fit for release.

LoRa chirp modulation, spreading-factor airtime, and LoRaWAN device-class listening behaviour form one deployment trade-off.

Deck summary

Key takeaways

Making the radio easier to hear may keep it on air much longer, which costs energy and shared channel time.

A payload means the useful reading or command inside a message.
LoRa is the physical radio modulation used by LoRaWAN.
At SF12 it is about 32.768 ms, or 32 times longer before payload, preamble, header, coding-rate, and retry details are counted.
A defensible choice records why the setting fits the device group, message schedule, gateway evidence, regional profile, and ADR handoff.

Retrieval practice

Recall check 1 of 4

Radio Remi says: answer from memory, then check your reasoning.

Q1A team chooses the highest spreading factor for every LoRaWAN sensor because it sounds safest. What should the review require first?

AApprove it because the highest spreading factor is always safest.

BDrop ADR evidence because manual settings do not need retest.

CProve the SF is needed and that added airtime fits the schedule.

DIncrease payload size because higher SF automatically raises throughput.

Show answer

Answer: C Higher spreading factors can help weak links, but the device group, airtime cost, and message schedule must justify the choice.

Retrieval practice

Recall check 2 of 4

Radio Remi says: answer from memory, then check your reasoning.

Q2A field pilot proves one small uplink at one gateway and then the team approves a larger alarm payload at the same spreading factor. What is the review gap?

AThe larger payload and cadence need new airtime and field evidence.

BThere is no gap; one small uplink proves every larger payload will work.

CGateway evidence is irrelevant because modulation never affects the payload.

DADR must be disabled permanently after any successful field pilot.

Show answer

Answer: A Evidence for one message class does not automatically approve another payload and schedule.

Retrieval practice

Recall check 3 of 4

Radio Remi says: answer from memory, then check your reasoning.

Q3A device moves between locations, and ADR keeps adjusting data rate from old uplink history. What should the deeper review question be?

AWhether every device should use the same highest spreading factor forever.

BCheck ADR has recent link evidence; otherwise set a narrower manual boundary.

CWhether payload size can be ignored because ADR controls only the radio.

DWhether gateway metadata should be deleted after the first successful uplink.

Show answer

Answer: B ADR depends on useful device-profile history; movement or changing link conditions can make the evidence boundary stale.

Retrieval practice

Recall check 4 of 4

Radio Remi says: answer from memory, then check your reasoning.

Q4A pilot reports symbol time only, then increases payload size and retries for the fleet. What airtime claim can the reviewer make?

AThe symbol time still proves complete packet airtime.

BRetries reduce total channel use because the gateway has more copies.

CPayload size cannot change airtime once spreading factor is fixed.

DRecalculate complete packet airtime with payload, coding, and retry evidence.

Show answer

Answer: D Symbol time alone omits payload and coding overhead, while retries add channel use.

Print reference

Answers

Answer key.

C · Higher spreading factors can help weak links, but the device group, airtime cost, and message schedule must justify the choice.
A · Evidence for one message class does not automatically approve another payload and schedule.
B · ADR depends on useful device-profile history; movement or changing link conditions can make the evidence boundary stale.
D · Symbol time alone omits payload and coding overhead, while retries add channel use.

C: justify the highest spreading factor with airtime evidence. A: estimate a changed payload again. B: use representative history for moving devices. D: include packet structure and retries in complete airtime.