This AI-assisted article was approved by Volker Cesinger. It presents his personal perspective and is not an official Checkpoint Systems publication.
- Choose session and target
- Tag responds
- Flag may change
- Check next round
A label is read in one round and is missing from a second list shortly afterwards. That is a symptom, not yet a diagnosis. Besides materials, movement and radio power, inventory control can play a role. Before increasing reader power, I would check which tags the reader was actually asking to respond in that round.
A session is not a business status
GS1 Gen2 provides four sessions: S0, S1, S2 and S3. A tag maintains an independent inventoried flag for each, with values A and B. The reader selects a session and target value for an inventory round. Appropriate commands can change the flag of an inventoried tag. This organises responses within a tag population.
A and B do not mean paid and unpaid. They are not a storage location or completed dispatch either. Business states require separate data and process logic. Flag persistence and reset behaviour are not identical across all sessions; actual settings must fit the task.
Two readers can see a population differently
A synthetic setup contains six independently documented samples. Reader one and reader two initially use the same session and target value. Behaviour after a previous round may therefore differ from a fresh trial. Settings are subsequently changed deliberately and the expected responses compared.
This is not a universal configuration recommendation. Different sessions can coordinate inventories, but do not automatically remove radio interference. Readers, tags and timing need joint assessment. Nor should another round accidentally create six new goods movements.
Selection is a separate question
Supported selection functions can restrict the population before or during inventory, for example to examine a defined identifier group. The filter must match actual encoding. An incorrect mask can exclude intended items even when their tags are physically readable.
GS1 Gen2v3 and vendor-specific extensions such as Gen2X are not interchangeable names. Availability of a function depends on actual reader, firmware and chip versions. A standard name in a datasheet does not replace this check.
A manageable diagnostic sequence
- Independently document expected samples and their actual identifiers.
- Record reader, firmware, region, session, target value and filters.
- Start without unnecessary selection filters.
- Compare the sequence with and without a previous inventory round.
- Add the second reader under controlled conditions, changing one parameter.
- Separate raw responses, deduplication and business events.
If a tag appears in the raw log but not in the application, investigate processing after the radio link. If it remains absent even in an isolated, documented test, investigate label, object and capture conditions. The two cases need different corrective actions.
Next step
Record one reproducible failure with a small reference population. A configuration log is more useful than a general claim that a reader is too weak. Understand read zones or discuss the capture setup.
Sources
- GS1 Gen2, Release 3.0.1, particularly sessions and inventoried flags in section 6.3.2.2.
- RAIN System Design Guidelines, sessions and inventory control.