Math Bridge: Gateway margin and retry energy

← Back to A Repeatable Design Method
Math BridgeDesign MethodologyStruggle-friendly runway

When does gateway distance become battery drain?

Follow one 868 MHz link from spherical spreading to obstruction loss, retry energy, and a reviewable gateway decision.

Blueprint Bina, the design guideBlueprint Bina guides
The one targetCarry link margin into retry energy.
The chapter case1,500 m; n=3.3; 18 dB obstruction; four reports/day.
What it buys youA gateway choice tied to both RF and battery evidence.

A field team faces an unresolved physical question: When does gateway distance become battery drain? They must answer it before changing distance 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 distance. The middle card applies this page's relationship. The green card is 1 m loss. 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.

Distance changes 1 m loss An input card leads through the page relationship to the 1 m loss result. SET INPUT ONE CONTROL APPLY RULE predict calculate check units READ RESULT
Walk the arrows. The log-distance term removes decibels as distance grows. Once the remaining margin is negative, the same radio-on pulse must be paid again.

Derive the baseline in four named moves

  1. 1

    Name the input. The chapter baseline for distance is 1500.

  2. 2

    Name the relationship. FSPL₀=31.20 dB; PL(1500)=136.01 dB Mnominal=14-136.01-(-137)=14.99 dB Mobstructed=14.99-18=-3.01 dB Ereport=0.100x3.3x1.5=0.495 J=495 mJ; one retry=990 mJ

  3. 3

    Substitute the chapter fixture. Set distance to 1500. The page ledger gives 1 m loss as 31.20 dB.

  4. 4

    Read the result. Keep dB beside the value. Use it only inside the technical boundary on this page.

Predict, then change distance

Try Predict the direction of 1 m loss. Move one control, calculate, then check your prediction.

1500
Chapter baseline
1 m loss

Observe The log-distance term removes decibels as distance grows. Once the remaining margin is negative, the same radio-on pulse must be paid again. Reset the control to 1500 and compare 1 m loss.

Explain Only distance moves here. The other chapter fixtures remain fixed.

Check yourself

What should you do before trusting a moved-control result?
Answer: Predict its direction, apply the shown relationship, keep the units, and reset to the worked baseline.
What does this small model leave out?
Answer: Only distance moves. Field effects named in the page's technical boundary stay fixed.

Honesty note. This teaching model changes only distance. It replays the chapter fixture; it is not a field prediction.

1. Start with power spreading out

Radio power crosses a growing spherical surface. At twice the free-space distance, the same power is shared over four times the area. Decibels turn repeated multiplication and division into addition and subtraction.

Blueprint Bina: Draw the physical path before writing the budget.

2. Name every algebra move

1

Anchor one metreFSPL₀=20 log₁₀(4πd₀/λ).

2

Scale the distancePL=FSPL₀+10n log₁₀(d/d₀).

3

Subtract lossesM=EIRP−PL−Srx−Lsite.

4

Price one transmissionE=IVt.

5

Price one retryTwo attempts use 2E, so the avoidable part is one extra E.

3. Reproduce the 1,500 m case

FSPL₀=31.20 dB; PL(1500)=136.01 dB
Mnominal=14−136.01−(−137)=14.99 dB
Mobstructed=14.99−18=−3.01 dB
Ereport=0.100×3.3×1.5=0.495 J=495 mJ; one retry=990 mJ

Four avoidable retry transmissions per day spend 0.550 mWh/day, or about 0.201 Wh/year per device.

4. Try the gateway distance

TryMove the worst device from 1,500 m toward 750 m while keeping the same site allowance.

Distance
1 m loss
Path loss
Nominal margin
After obstruction
One report
One retry case
Avoidable daily
Avoidable annual

ObserveDistance changes both nominal and obstructed margin; report energy stays fixed until a failed link forces another attempt.

ExplainThe log-distance term removes decibels as distance grows. Once the remaining margin is negative, the same radio-on pulse must be paid again.

Technical boundaries.

This is a planning ledger, not a site qualification.

Propagation
One fitted exponent cannot represent every wall, terrain shape, antenna angle, or season
Retry
A failed report may retry zero, one, or many times under the real protocol policy
Energy
Startup, receive windows, sleep, sensing, and battery voltage behaviour are outside this radio pulse

Use RF surveys, packet counters, and current traces before approving gateway count or service life.

5. Test the risky assumption

Measure the hardest links with the intended antenna height, enclosure, weather, and traffic. Keep both successful and failed packets so retries do not disappear from the average.

6. Record the decision state

Store frequency, EIRP, sensitivity, exponent source, site allowance, distance, retry policy, current trace, gateway plan, and the change that forces a rerun.

7. Check yourself

Why is 15 dB nominal margin not enough evidence?
Answer: The named 18 dB site allowance changes it to about −3 dB.
Why is a retry an energy cost?
Answer: The radio repeats its current-by-voltage-by-time pulse.
Does positive arithmetic qualify one gateway?
Answer: No. A model must be checked against installed RF and packet evidence.
Honesty boundary.

The formulas and constants reproduce the chapter's catalog-typical teaching case.

n=3.3
Obstructed-suburban teaching exponent, not a measured site fit
18 dB
Explicit obstruction allowance, not a universal wall value
0.201 Wh/year
Four single avoidable retries per day, not a complete battery budget

Correct, not complete: this link ledger does not qualify a gateway deployment.

Return to A Repeatable Design Method with the maths unpacked →