Why the Same UHF Reader Reads Some Cards Once — and Others Nonstop

A question landed in our inbox recently from an overseas integrator, and it is one of the best "same hardware, different behavior" puzzles in UHF RFID:

"On the same Chinese UHF reader, with the same S0/S1 inventory settings — your UHF cards get read continuously, but Zebra's cards get read exactly once. We want the read-once behavior to cut the load on the reader and the host. Why the difference?"

On paper, one reader plus one set of parameters should treat two standards-compliant cards identically. In practice, the chip inside the card quietly decides how chatty it is. The answer lives in the EPC Class 1 Gen 2 (ISO/IEC 18000-63) protocol — specifically in sessions, inventoried flags, and a very unglamorous storage capacitor.

First, a mental reset: is "read once" a tag feature or a reader feature?

Neither — it is a negotiation between the two. Two basics set the stage:

• Passive UHF tags have no battery. A tag wakes up only when the reader antenna's RF field powers it, and it replies by backscattering its EPC.
• The default behavior is chatter. As long as a powered tag hears inventory Queries, it will keep answering them. Continuous reads are not a defect — they are the protocol's default state.

So the real question is inverted: not "why does the generic card read continuously?" but "what makes the Zebra card shut up after one read?"

The mechanism: sessions and inventoried flags

Every Gen2 tag maintains an inventoried flag per session, with two states — A and B. The choreography is simple:

• Read once: when the reader successfully inventories the tag, the tag flips its flag from A to B.
• Stay quiet: while the flag stays in B, the tag ignores further Queries targeting state A in that session. One read, then silence.

If every tag played this perfectly, every card would read once. The plot twist is what happens to that flag between reader cycles.

Persistence time: where premium chips quietly win

In session S1, the B flag is not stored in permanent memory. It is held by a tiny on-die storage capacitor, and it survives only for the chip's persistence time — how long the flag outlives a dip or gap in RF power.

• Impinj Monza-family chips (what Zebra cards typically carry) — the monk. Excellent energy management keeps the B flag stable through microsecond-scale scan gaps and field-strength wobble. The flag holds, the tag stays silent, and the host sees exactly one read.
• Generic chips — the goldfish. The capacitor bleeds off during the same tiny gaps, the flag snaps back from B to A, and the reader greets the tag as a brand-new arrival. Again. And again. That is your "continuous read" stream.

Same reader, same air protocol, same commands — but one chip forgets it was already counted, and one does not.

How to get read-once behavior on purpose

Two clean engineering routes, depending on what you are allowed to touch:

Route 1 — hardware alignment (touch nothing but the card)

If the reader configuration and host software must stay frozen, specify cards built on the same silicon: Impinj Monza R6 / R6-P. The flag-persistence behavior then matches the Zebra reference card, and the same S0/S1 setup produces the same single read — no firmware, reader, or middleware changes. We build custom UHF cards on Monza and other chips from our chip catalog, and free samples let you verify the behavior on your own reader before committing.

Route 2 — system-side filtering (the sturdier habit)

Betting production stability on an analog capacitor's discharge curve is elegant until a forklift, a metal shelf, or a neighboring reader adds interference. The robust pattern:

• Switch the inventory to session S3, which holds its inventoried state far longer; in our bench tests every card — premium or generic — read once under S3.
• Enable de-duplication in the reader software or middleware: report each EPC once per window, for example "same EPC reported at most once every 3 seconds." This ends the serial-port and CPU flood regardless of which tags show up.

Route 1 fixes the symptom at the silicon level; Route 2 makes the system indifferent to which silicon arrives. Mature deployments usually do both.

The takeaway

"Mystery" RFID field behavior is almost always a protocol detail wearing a trench coat. Zebra's read-once behavior is not magic — it is a well-engineered chip's flag persistence cooperating with S1 inventory rules. You can buy the same behavior (Monza-based cards), or you can design for it (S3 plus de-duplication) and stop caring which chip shows up. Understanding the layer underneath is what turns a support ticket into a spec decision.

FAQ

Why does my UHF card keep being read continuously under S0/S1?
Because that is Gen2's default: a powered tag answers every Query. Read-once behavior only appears when the tag's inventoried flag stays in state B between inventory rounds — which depends on the session used and the chip's flag persistence time.

What is the practical difference between sessions S0/S1 and S3?
S0 resets the inventoried flag as soon as power is lost, S1 holds it only for a short capacitor-backed persistence window, and S2/S3 hold it substantially longer while the tag remains energized. For "count each tag once" workflows, S2/S3 plus a host-side de-duplication window is the dependable combination.

Can RFIDAK supply cards that behave like Zebra's read-once cards?
Yes — we manufacture UHF cards on Impinj Monza R6 / R6-P with the same flag-persistence behavior, MOQ from 500 pieces. Request free samples and test them on your own reader and session settings before ordering.