Read-Zone Evidence: Dwell Time, Inventory Rounds, and Filtering

Read-Zone Evidence: Dwell Time, Inventory Rounds, and Filtering

Ada re-derives the chapter’s own dwell time, inventory-round opportunities, and read-zone filtering rates

foundations
math-foundations
rfid
read-zone
beginner
Ada ADA · CALCULATION AUDIT

Read-Zone Evidence: Dwell Time, Inventory Rounds, and Filtering

RFID evidence is physics plus bookkeeping. The radio field gives the tag a short read window; the ledger proves which raw observations became accepted business events.

A tagged tool cabinet should identify its 18 tools while ignoring 3 nearby bench tools, yet its raw trace shows 63 observations for those 18 real items. A moving portal has a different denominator: 32 tagged cartons pass through a 2.4 m read zone at 1.6 m/s, giving about 1.5 s of dwell time and, at a 200 ms inventory round, roughly 7.5 rounds before the cartons leave the zone — and the pilot actually reads 29 of the 32. This audit asks the question those two examples invite: what evidence turns 63 raw observations and a 29-of-32 pilot into a trustworthy read-zone claim, rather than just an RF success story?

Companion to the chapter How RFID Identifies Objects — every number here comes from that chapter.

See the relationship before changing it

The figure reads from left to right. The blue card is carton speed. The middle card applies this page's rule. The green card is read-zone dwell time. 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 carton speed, so the numeric fixture does not switch without explanation.

Carton speed changes read-zone dwell time An input card leads through the rule dwell = 2.4 m / speed to the read-zone dwell time result. INPUT PAGE INPUT APPLY THE RULE predict calculate check units OUTPUT RESULT
Walk the arrows. A faster carton spends less time inside the fixed 2.4 metre read zone.

Derive the baseline in four named moves

  1. 1

    Name the input. The chapter baseline is 1.6 m/s.

  2. 2

    Name the relationship. dwell = 2.4 m / speed

  3. 3

    Substitute with units. 2.4 m / 1.6 m/s = 1.50 s

  4. 4

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

Predict, then change carton speed

Try Predict the direction of dwell = 2.4 m / speed. Test another carton speed, then compare read-zone dwell time.

1.6 m/s
Chapter baseline
Read-zone dwell time

Observe A faster carton spends less time inside the fixed 2.4 metre read zone. Reset carton speed to 1.6 and compare read-zone dwell time.

Explain A faster carton spends less time inside the fixed 2.4 metre read zone.

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 carton speed moves here. Field effects named in the technical boundary stay fixed.
Try

Feed the audit a 2.4 m read zone, 1.6 m/s motion, and 0.2 s inventory rounds, then select Check audit.

Observe

Dwell time reads 1.5 s and the opportunity count becomes 7.5 rounds; the pilot evidence also separates 29 accepted events from 3 misses.

Explain

The 7.5 read opportunities matter only after duplicates and nearby tags are filtered, so raw observation count is not the acceptance denominator.

Convert motion into dwell time

1. Convert motion into dwell time. The portal example gives a 2.4 m read zone and a carton speed of 1.6 m/s.

dwell time = zone length / speed = 2.4 / 1.6 = 1.5 s

That is the physics constraint: a carton is only inside the useful RF evidence boundary for about 1.5 s.

Convert dwell time into inventory opportunities

2. Convert dwell time into inventory opportunities. The chapter states an observed inventory round time of 200 ms, which is 0.2 s.

round opportunities = 1.5 / 0.2 = 7.5 rounds

The result is not a guaranteed read count. It says the system has about seven and a half inventory opportunities before the cartons leave the zone, so misses still need a cause: orientation, material, anti-collision timing, antenna aim, or middleware timeout.

Audit the read-zone ledger

Evidence question Chapter values Audit arithmetic Checked result
Did the cabinet accept the in-scope tools? 18 expected tools, 18 accepted 18 / 18 = 1.00 100% accepted verified
Did the cabinet reject nearby bench tools? 0 accepted from 3 nearby tools 0 / 3 = 0 0% stray acceptance verified
How much raw observation noise was filtered? 63 raw observations, 18 accepted events 63 - 18 = 45; 45 / 63 = 0.714 45 observations filtered, about 71.4% of the raw trace
How strong was the portal pilot? 29 reads from 32 cartons 29 / 32 = 0.90625; 3 / 32 = 0.09375 90.6% read rate, 9.4% miss rate

Review rule: accept the RFID claim only when the read-zone length, object speed, round timing, accepted-event denominator, rejected-nearby denominator, and duplicate filter are all recorded with the pilot trace.

Every number above is taken from the chapter’s own portal and cabinet examples and re-derived step by step.

Technical boundaries: The opportunity count does not model RF fading, antenna pattern, pallet shielding, tag orientation, anti-collision timing variance, or duplicate-filter behaviour under bursty reads.

Ready: work the ledger before checking it.