A field team faces an unresolved physical question: From Path Loss to a LoRa Payload Decision They must answer it before changing extra canopy / terrain loss on the real device. Predict the direction first.
See the relationship before changing it
The figure reads from left to right. The blue card is extra canopy / terrain loss. The middle card applies this page's relationship. The green card is sf12 margin. Walk the arrows once: set the input, apply the rule, then read the result with its unit.
The retained audit below checks several chapter fixtures. This added model holds every other chapter fixture fixed, so the numeric fixture does not switch without explanation.
Derive the baseline in four named moves
- 1
Name the input. The chapter baseline for extra canopy / terrain loss is 15.
- 2
Name the relationship. P_rx = EIRP - PL - L_extra; M = P_rx - S
- 3
Substitute the chapter fixture. Set extra canopy / terrain loss to 15. The page ledger gives sf12 margin as 10.90 dB.
- 4
Read the result. Keep dB beside the value. Use it only inside the technical boundary on this page.
Predict, then change extra canopy / terrain loss
Try Predict the direction of sf12 margin. Move one control, calculate, then check your prediction.
Observe The widget uses P_rx = 14 - 125 - L_extra and M = P_rx - S, the same ledger derived above for both receiver modes. Reset the control to 15 and compare sf12 margin.
Explain Only extra canopy / terrain loss moves here. The other chapter fixtures remain fixed.
Check yourself
What should you do before trusting a moved-control result?
What does this small model leave out?
1. Begin with the physical story
A compact payload matters only inside a complete link decision. The chapter's vineyard example first estimates whether the radio signal survives the path. The selected data rate then determines payload and airtime constraints.
2. Put names and units on the maths
Keep the units beside every number. They are an error detector: only like units can be added or subtracted.
| Symbol | Meaning | Unit |
|---|---|---|
| EIRP | power launched after antenna terms | dBm |
| PL | modelled path loss | dB |
| S | receiver sensitivity | dBm |
| M | received power above sensitivity | dB |
3. Derive it with every move named
Find wavelengthλ = c/f = 3.00×10^8 / 868×10^6 = 0.346 m.
Find 1 m free-space loss20 log10(4πd₀/λ) = 31.2 dB.
Grow loss to 3 km31.2 + 10(2.7)log10(3000) = 125 dB.
Find received power14 dBm EIRP − 125 dB = −111 dBm.
Compare with sensitivityM = P_rx − S for the selected receiver mode.
Spend canopy lossSubtract the illustrative 15 dB from received power before recomputing margin.
4. Reproduce the chapter's numbers
Before extra loss, SF12 at −137 dBm sensitivity has −111 − (−137) = 25.9 dB margin; SF7 at −123 dBm has 11.9 dB. Adding 15 dB of illustrative canopy/terrain loss gives −126 dBm received power, leaving 10.9 dB for SF12 and −3.1 dB for SF7.
That supports measuring or using ADR. It does not prove every vineyard node needs SF12. In the chapter's EU863-870 DR0 example, an uplink with no FOpts can carry up to 51 application bytes; other profiles differ.
5. Try the formula
TryIncrease the extra vineyard loss from 0 to 30 dB and compare the SF12 and SF7 margins at the same received path.
ObserveObserve that both modes lose one margin dB per added loss dB, but their different sensitivities put the zero-margin crossing in different places.
ExplainThe widget uses P_rx = 14 − 125 − L_extra and M = P_rx − S, the same ledger derived above for both receiver modes.
This small widget varies one named input and holds the chapter constants fixed.
- The honesty boundary below names what it does not model
- Needs separate evidence
Use field evidence or a deeper model before release.
6. What the result buys you
Format choice comes after the measured radio profile. If ADR and field evidence require a slow constrained mode, byte count, complete packet airtime, duty cycle, receive windows, retries, and battery cost matter together. The bridge establishes the margin arithmetic; the chapter's Under the Hood explains why application-payload bit time alone is not full LoRa airtime.
7. Check yourself
Try each question before revealing the answer.
1. What is the estimated received power before extra loss?
Answer: 14 − 125 = −111 dBm.
2. What is SF12 margin before canopy loss?
Answer: −111 − (−137) = 25.9 dB, using the chapter's rounded path loss.
3. What happens to SF7 after 15 dB extra loss?
Answer: Received power becomes −126 dBm, so margin is −126 − (−123) = −3.1 dB after rounded inputs.
These are the chapter inputs, worked results, and named teaching assumptions.
- 868 MHz
- Frequency, sample rate, or event rate
- n = 2.7
- Named physical or model constant
- 3 km
- Distance, wavelength, or size
- rounded 125 dB loss
- Gain, loss, margin, or level ratio
- assumed 14 dBm EIRP
- Named teaching assumption
- catalog −137/−123 dBm sensitivities
- Named teaching assumption
- illustrative 15 dB extra loss
- Named teaching assumption
- the regional 51-byte case
- Device, payload, or sample count
- Rounding makes the displayed margins differ by tenths from unrounded intermediate calculations
- Time, interval, or service-life value
Regional rules, FOpts, radio settings, full-frame airtime, retries, ADR, and measurements remain outside this bridge.
Phoebe guides