Math Bridge: Two RFID Range Limits

← Back to RFID Fundamentals
Math BridgeRFIDTwo-leg range

Why do two RFID tags run out of range differently?

Separate the power needed to wake a passive chip from the faint return a battery-assisted tag must send back.

Eddie, the electronics guideEddie guides
The one targetCompute the two different range ceilings without mixing their equations.
The chapter case13.56 MHz HF, 915 MHz UHF, under 10 m passive, and roughly 30 m BAP.
What it buys youA bounded starting point for separate forward- and return-link tests.

A field team faces an unresolved physical question: Why do two RFID tags run out of range differently? They must answer it before changing wake threshold 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 wake threshold. The middle card applies this page's relationship. The green card is hf wavelength. 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.

Wake threshold changes hf wavelength An input card leads through the page relationship to the hf wavelength result. SET INPUT ONE CONTROL APPLY RULE predict calculate check units READ RESULT
Walk the arrows. Changing chip sensitivity moves the forward wake limit, not the separately computed return limit.

Derive the baseline in four named moves

  1. 1

    Name the input. The chapter baseline for wake threshold is -18.

  2. 2

    Name the relationship. λHF = 3x10⁸ / 13.56x10⁶ = 22.12 m; rnf = 3.52 m Lforward = 36 + 1.8 - (-18) = 55.8 dB; dpassive = 16.09 m Lreturn = 36 + 2(1.8) + 6 - (-80) = 125.6 dB; dBAP = 36.02 m

  3. 3

    Substitute the chapter fixture. Set wake threshold to -18. The page ledger gives hf wavelength as 22.12 m.

  4. 4

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

Predict, then change wake threshold

Try Predict the direction of hf wavelength. Move one control, calculate, then check your prediction.

-18
Chapter baseline
HF wavelength

Observe Changing chip sensitivity moves the forward wake limit, not the separately computed return limit. Reset the control to -18 and compare hf wavelength.

Explain Only wake threshold 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 wake threshold moves. Field effects named in the page's technical boundary stay fixed.

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

1. Start with the physical story

A passive UHF tag must harvest enough reader power to wake. A battery-assisted tag is already awake, so its faint backscatter return can become the limiting leg.

Eddie: “Range” is one word for two stopping conditions. Name the leg before trusting the distance.

2. Name every algebra move

1

Find wavelengthDivide wave speed by frequency.

2

Mark near fieldDivide wavelength by 2π for the HF boundary screen.

3

Budget forward lossSubtract the passive wake threshold from EIRP plus tag gain.

4

Budget the returnUse the two-way 40 log distance term for backscatter.

3. Reproduce the chapter case

λHF = 3×10⁸ / 13.56×10⁶ = 22.12 m; rnf = 3.52 m
Lforward = 36 + 1.8 − (−18) = 55.8 dB; dpassive = 16.09 m
Lreturn = 36 + 2(1.8) + 6 − (−80) = 125.6 dB; dBAP = 36.02 m

The ideal values bracket the chapter's installed claims only after polarization, packaging, detuning, multipath, and reliability margin are added.

4. Try one real input

TryMove the passive chip wake threshold while every other chapter constant stays fixed.

Wake threshold
HF wavelength
HF near-field boundary
UHF wavelength
Forward path budget
Passive ideal range
Return path budget
BAP ideal range
BAP/passive ratio
Margin to 10 m

ObserveAt -18 dBm, the ideal passive ceiling is 16.09 m and needs 4.13 dB of derating to become 10 m; the BAP return screen stays 36.02 m.

ExplainChanging chip sensitivity moves the forward wake limit, not the separately computed return limit.

Technical boundaries.

These are ideal free-space link screens, not released read zones.

Near field
The λ/2π line marks a regime screen; LF and HF coupling needs coil geometry and detuning evidence.
Forward link
Polarization, packaging, orientation, fading, and chip sensitivity spread reduce reliable passive range.
Return link
The simplified two-way budget omits radar cross-section, modulation depth, receiver implementation, and protocol timing.

Correct, not complete: these numbers do not approve a tag or read zone.

5. Use the result in the lab

Measure passive wake and BAP return success separately across orientation, material, distance, and power settings.

6. Record the evidence state

Keep frequency plan, EIRP, antenna gains, tag part and threshold distribution, reader sensitivity, geometry, environment, misses, and false reads.

7. Check yourself

Does 16.09 m prove a passive tag reads reliably at 16 m?
Answer: No. It is an ideal wake ceiling before installation loss and reliability margin.
Why does a BAP tag use a different limiting equation?
Answer: Its battery removes the passive wake constraint, so the faint two-way return can dominate.
Can gain and EIRP describe an HF tap deep in the near field?
Answer: Not by themselves. Coil coupling, alignment, and detuning govern that regime.
Honesty boundary.

The bridge makes the two chapter mechanisms arithmetically distinct.

Computed
Wavelength, boundary, path budgets, ideal ranges, ratio, and derating are reproducible.
Specified
Tag threshold, antenna gains, EIRP, reader sensitivity, and service margin come from selected hardware and policy.
Observed
Wake success, returned replies, misses, cross reads, and range distributions decide the deployment.

Correct, not complete: validate both link legs in the real read zone.

Return to RFID Fundamentals with the two range limits separated →