RFID Lab Check: Placement and Read Analysis

Start With the Decision

Moving an antenna a few centimetres can change which tags are seen. The test must hold other factors still and compare read patterns.

Route Overview

This is part 2 of 2. Review RFID Lab Check: Inventory and Trace Evidence for the preceding evidence.

Learning Objectives

• Run controlled RFID antenna-placement tests.
• Analyse missed, duplicate, and dense-inventory reads.

Chapter Roadmap

• Lab 3: Antenna Placement Tests
• Lab 4: Missed and Duplicate Read Analysis
• Dense Inventories and Q Scaling
• Check Q Scaling Evidence
• Middleware Evidence
• Privacy, Safety, and Fallback Checks
• Assessment Rubric
• Release and Retest Record
• Knowledge Check
• Match the Evidence
• Order the Lab Workflow
• Common Pitfalls
• Summary
• Key Takeaway
• What’s Next

Lab 3: Antenna Placement Tests

Antenna placement is a test variable, not a decoration. Change one placement factor at a time and keep the tag set fixed while you compare outcomes.

Use this sequence:

When a placement improves one scenario but creates stray reads in another, record both effects. The correct result may be a narrower read zone, a second antenna, a different tag mount, or a workflow change that prevents ambiguous reads.

Figure turns the preceding test variables into an ordered comparison. Follow the workflow from a recorded baseline through boundary, orientation, and material checks before accepting one documented change.

Inspect controlled setup and boundary check in Figure for lab 3: antenna placement tests. At the decision point in lab 3: antenna placement tests, find the boundary between controlled setup and boundary check on it. archive setup photo and config each time identifies the later check.

Read controlled setup with boundary check in Figure for lab 3: antenna placement tests. Check it from the controlled setup field to boundary check, then the archive setup photo and config each time disposition. Both controlled setup and boundary check need evidence. For lab 3: antenna placement tests, record the result beside archive setup photo and config each time.

In the workflow diagram Figure, the baseline fixes the geometry and reader configuration that later runs must share. The boundary check tests unwanted reach, the orientation check exposes coupling changes, and the material check introduces realistic detuning or blockage. Only after those observations does the change record permit one controlled adjustment and a repeated run. This sequence keeps a better result attributable to a specific placement change rather than to several moving variables.

The workflow becomes concrete in Figure, where a real doorway antenna, bracket, cable, and surrounding structure show what a “10 cm move” actually alters.

Inspect two vertical antenna pedestals and overhead frame in Figure for lab 3: antenna placement tests. Before carrying lab 3: antenna placement tests forward, put two vertical antenna pedestals and overhead frame into the same reading of it. tagged crates on the pallet limits the claim.

Read two vertical antenna pedestals with overhead frame in Figure for lab 3: antenna placement tests. Locate its interfaces with the two vertical antenna pedestals beside the overhead frame, while tagged crates on the pallet supplies another reference. The image fixes context, not measured performance. The conclusion in lab 3: antenna placement tests now has a named boundary.

In Figure, begin at the mounted antenna face, then inspect its bracket and cable route, and finally consider the doorway and nearby equipment that bound the field. A re-aim changes polarization and coverage; a move changes distance and multipath; disturbed cabling can change loss or service reliability. The photograph connects the controlled workflow in Figure to the installed object that must be photographed, measured, traced, and retested.

Photo: Geirvevle, CC BY-SA 3.0.

Lab 4: Missed and Duplicate Read Analysis

Treat missed and duplicate reads as evidence, not as random noise. A deployable lab result explains how the workflow handles both.

Missed reads usually require checking:

• Tag orientation or placement on the object.
• Material near the tag or between tag and antenna.
• Reader configuration changes between runs.
• Antenna blind spots or destructive overlap between antennas.
• Middleware timeout values that mark tags as departed too quickly.

Duplicate reads usually require checking:

• Whether the same physical tag is counted multiple times inside one dwell period.
• Whether two antennas report the same tag and the middleware lacks a zone ownership rule.
• Whether a moving tag crosses a boundary slowly enough to create multiple arrival events.
• Whether the tag identity is reused across sample tags or fixtures.

Stray reads require a separate decision: either shrink the read zone or mark that boundary as a known operational risk. Do not hide stray reads by filtering tag IDs unless the filter is part of the actual release design and is documented.

Dense Inventories and Q Scaling

Dense UHF RFID inventories take time because tags do not get fixed private time slots. In EPC Gen2-style inventory, the reader opens a frame of 2^Q slots, tags choose slots, and each slot becomes one of three outcomes: a singleton that can be read, a collision where multiple tags answered together, or an empty slot. The reader adjusts Q as it observes those outcomes:

• Too many collisions means the frame is too small for the tag population, so the reader increases Q.
• Too many empty slots means the frame is too large, so the reader decreases Q.
• The goal is roughly one tag per slot, not a guarantee that every slot succeeds.

Inspect Announces Q and T3 in Figure for dense inventories and q scaling. Before accepting dense inventories and q scaling, use it to distinguish Announces Q from T3. Tags randomly choose slots limits the claim.

Read Announces Q with T3 in Figure for dense inventories and q scaling. Follow it starting at Announces Q, crossing T3, and closing on Tags randomly choose slots. A failure at T3 changes the route from Announces Q. Reopen dense inventories and q scaling whenever T3 changes.

The arithmetic explains a common lab surprise. With 64 nearby tags and Q=4, the reader has only 2^4 = 16 slots, so the average load is 64 / 16 = 4 tags per slot. Under a simple slotted ALOHA model, the expected useful singletons are roughly N * e^-G, where G is the average tags per slot. That gives about 64 * e^-4 = 1.2 successful tag replies per frame, so the trace will be dominated by collisions. With Q=6, the frame has 64 slots and G = 1, giving about 64 / e = 23.5 useful singletons per frame. It still takes multiple rounds to see every tag, but the trace is no longer thrashing.

The consequence for assessment is concrete: a release record must separate RF inventory performance from application logic. If a dense box takes three rounds before every expected tag appears, the middleware must either wait long enough before declaring a miss or mark the result as provisional. If a Select command narrows the population to one product family or location, the lab should capture that filter because it changes the inventory denominator.

This is also why a lab should avoid unsupported range promises. A bench reader may see all tags quickly when they are spread flat, then miss several when the same count is stacked, rotated, near liquid, or close to metal. The under-the-hood evidence does not need to identify every RF cause perfectly; it must show the trace signature, the controlled change, the repeated scenario, and the release decision.

Check Q Scaling Evidence

Middleware Evidence

Middleware is where raw RFID observations become IoT events. Assessment should review the decision logic, not just the reader output.

Collect evidence for:

• De-duplication window and how it is chosen.
• State transitions such as unknown, present, departed, exception, and reconciled.
• Multi-antenna ownership rules when two antennas see the same tag.
• Offline behavior when the gateway, network, or application endpoint is unavailable.
• Audit log fields that explain why the system accepted, ignored, or flagged a tag event.
• Manual correction workflow for expected tags that were missed or unexpected tags that were observed.

For a classroom lab, a CSV trace and a short script summary can be enough. For an operational pilot, preserve the actual gateway configuration export, middleware rule version, and sample application event payloads.

Privacy, Safety, and Fallback Checks

RFID labs often collect identifiers tied to people, assets, medicine, tools, or locations. Keep the review practical and bounded:

• Do tag IDs reveal a person, patient, employee, or sensitive asset without an authorized lookup?
• Can tags be read from a place outside the intended workflow?
• Is there signage, policy, or operator instruction where people need notice?
• Are emergency, manual, or offline procedures documented?
• Can a failed reader leave the process in a safe state?
• Are logs retained only for the operational need defined by the course or project?

These checks are not a substitute for organizational policy review, but they keep the lab from treating identifiers and movement traces as harmless by default.

Assessment Rubric

Use the rubric to score the lab result. A strong submission can be reproduced by another team member using the record alone.

Release and Retest Record

The release record closes the lab. It should be short enough to maintain and precise enough to retest.

Retest after a reader firmware change, antenna move, tag type change, packaging change, middleware rule change, layout change, or incident report. If the workflow depends on a physical read zone, physical changes are software changes for assessment purposes.

Inspect reader and tags and same scenarios in Figure for release and retest record. Before acting on release and retest record, trace reader and tags toward same scenarios in it. one loop per change marks the next check.

Read reader and tags with same scenarios in Figure for release and retest record. Step through it starting at reader and tags, crossing same scenarios, and closing on one loop per change. That ordering makes one loop per change depend on reader and tags. Return to release and retest record with same scenarios explicitly tested.

Knowledge Check

Match the Evidence

Order the Lab Workflow

Common Pitfalls

• Changing too many variables at once: If antenna aim, reader power, and tag placement change together, the trace cannot explain which change mattered.
• Testing only happy paths: Expected tags alone do not prove a read zone. Boundary tags, absent tags, moving tags, and obstructed tags reveal the system limits.
• Counting raw reads as inventory events: A raw read is an observation. Inventory state needs middleware rules for dwell time, de-duplication, and departure.
• Ignoring object material: A tag that works on a plastic badge may fail on a metal tool, a liquid container, or a dense package.
• Hiding failures in the final report: Misses, duplicates, and strays are the material for improvement. Preserve them and explain the retest.

Summary

RFID lab assessment is evidence work. A useful result names the read zone, controls the scenarios, captures trace data, explains middleware decisions, and records what changed between runs. The release decision should state the known limits and the retest trigger so the workflow can survive layout, tag, reader, or middleware changes.

Key Takeaway

RFID labs and assessments should measure read behavior, missed reads, duplicates, materials, orientation, and middleware filtering rather than only proving one successful scan.

What’s Next

• RFID Design and Deployment: turn lab findings into site surveys, placement decisions, and deployment records.
• RFID Troubleshooting: diagnose read failures, interference, and antenna issues in more depth.
• RFID Security and Privacy: review tag identity, access control, tracking risk, and privacy controls.
• RFID Comprehensive Review: consolidate RFID concepts before module assessment.

Continue Your Route

This final part closes the route from Lab 3: Antenna Placement Tests through What’s Next. Return to RFID Lab Check: Inventory and Trace Evidence or continue from the rfid-nfc-uwb module index.