A technician must decide whether free-space range is safe before changing fade-margin deduction on the real device. The result is unresolved until the rule and units are checked. Predict the direction first.
See the relationship before changing it
The figure reads from left to right. The blue card is fade-margin deduction. The middle card applies this page's rule. The green card is free-space range. 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 model keeps those stated values fixed and changes only fade-margin deduction, so the numeric fixture does not switch without explanation.
Derive the baseline in four named moves
- 1
Name the input. The chapter baseline is 0 dB.
- 2
Name the relationship. range = 10^((49.95 dB - fade margin) / 20)
- 3
Substitute with units. 10^(49.95 / 20) = 314.4 m
- 4
Read the result. Keep the unit beside the value. Use it only inside the technical boundary on this page.
Predict, then change fade-margin deduction
Try Predict the direction of range = 10^((49.95 dB - fade margin) / 20). Test another fade-margin deduction, then compare free-space range.
Observe Every added fade-margin decibel reduces the range allowed by the same budget. Reset fade-margin deduction to 0 and compare free-space range.
Explain Every added fade-margin decibel reduces the range allowed by the same budget.
Check yourself
What should you do before trusting a moved-control result?
What does this small model leave out?
1. Start with the physical question
Solve a link budget for ideal range and expose two different causes of shrinkage. A simulator setting with a named physical cause.
2. Name every algebra move
Build the reference lossPL0=20log10(4πd0/λ).
Find usable budgetB=Pt−sensitivity−margin.
Isolate the distance logarithmlog10(d/d0)=(B−PL0)/(10n).
Undo log base tend=d0×10^((B−PL0)/(10n)).
Spend 3 dB separatelyRepeat with B−3 for the battery-sag power cut.
3. Reproduce the chapter case
n=3.5: d=26.7 m; n=2: d=315 m; collapse=11.8×; 3 dB-cut open range=223 m
The arithmetic reproduces the chapter case while keeping its assumptions explicit.
4. Try the controlling input
TryMove the control and watch every displayed result come from the shown formula.
ObserveAt n=3.50, the ideal range is 26.7 m versus 314.5 m in free space, while a separate 3 dB cut leaves 222.6 m in free space.
ExplainObstruction changes the distance exponent; battery sag spends transmit-power budget. Both shrink range, but they are different fault causes.
This compact engine isolates one relationship; it is not a deployment certificate.
- Propagation
- A single exponent omits shadowing, fading, antenna orientation, and interference
- Radio
- Voltage sag is represented as a specified 3 dB RF power cut
- Range
- Sensitivity crossing is not a packet-delivery or latency guarantee
Measure the real system and reopen the decision when its inputs change.
5. Name the injected fault
When the lab shrinks range, state whether it represents obstruction, transmit-power loss, antenna damage, interference, or a deliberate policy. Capture the corresponding evidence.
6. Keep the fault record
Record frequency, transmit power, sensitivity, exponent, margin, battery state, antenna state, range setting, packet results, intended cause, owner, and retest trigger.
7. Check yourself
Why is the free-space estimate about 315 m?
Why does n=3.5 collapse it to about 26.7 m?
Does the 222.6 m sagged result predict a real deployment?
The worked values are traceable chapter examples or explicitly labelled teaching assumptions.
- 0 and −90 dBm
- Catalog-typical teaching radio values
- n=3.5
- Explicit obstructed example
- 3 dB
- Illustrative battery-driven RF power cut
Correct, not complete: field evidence still decides acceptance.
Packet Pete guides