LoRaWAN Spreading Factor Workbench
Tune SF7-SF12 and watch symbol time, data rate, airtime, link margin, duty-cycle pressure, and ADR trade-offs change together.
LoRaWAN Spreading Factor Workbench
Tune spreading factor, bandwidth, coding rate, payload size, and distance. The same setting updates the chirp symbol, airtime, link margin, duty-cycle pressure, and capacity warning so the trade-off stays visible.
Scenario
Choose a deployment pattern, then adjust the physical and LoRa parameters. The model is intentionally transparent rather than pretending to be a site survey.
Spreading factor
At a fixed bandwidth, each higher SF doubles chips per symbol and symbol time. That makes weak signals easier to detect, but every message occupies the channel longer.
- Range is model-based, not guaranteed.
- SFs are quasi-orthogonal, not magic collision immunity.
- ADR is best for mostly stationary devices.
The selected SF keeps useful margin, but the airtime cost is visible. Try lowering SF until the link margin falls near the target.
For stationary nodes with stable uplinks, ADR should usually push toward the lowest SF that keeps enough margin.
Higher SF improves sensitivity by a few dB per step; it does not simply double real-world range.
| SF | Chips/symbol | Symbol time | Bit rate | Airtime | Example sensitivity | Comment |
|---|
Independent learning reference
- Symbol time:
Tsym = 2^SF / bandwidth. - Nominal bit rate:
SF * bandwidth / 2^SF * coding-rate. - Airtime includes preamble, header, CRC, payload symbols, coding rate, and low-data-rate optimization.
- Example sensitivity values vary by radio, noise figure, bandwidth, implementation, and data rate.
- SFs are quasi-orthogonal. Near-far effects, gateway demodulator limits, and interference still matter.
- Regional data-rate plans map SF and bandwidth differently, so verify the target region profile.