nfc system composition: labels, readers and handheld terminals
RFID Knowledge

nfc system composition: labels, readers and handheld terminals

PublishedShanghai Zejie Smart Technology Co., Ltd.

The warehouse inventory was marked with labels that could not be read; the reader changed, and the field personnel did not operate. The NFC equipment system did not buy a single machine but was completed by the "store-identify-process" together with the label, the reader and the handheld terminal.

There was a problem at the scene: what can three types of equipment do?

In a warehouse area, the NFC label on a container is responsible for preserving or connecting information about the item, the reader is responsible for sending radio frequency signals and reading labels, the handheld terminal is shown to the staff member, continues to complete the library, inventory, access or review. When there is one missing point, the process breaks down.

Equipment Main roles What do you want to see when you choose?
NFC Label Save Numbering, Status or Data Index Frequency band, storage capacity, containment material, temperature-resistant wett
Reader Creates up-to-date communication with tags Communication protocols, antenna forms, interfaces, read stability
Handheld Terminal Run applications and submit business results System compatibility, sweep and NFC capability, re-routing, protection level.

The NFC usually works in 13.56 MHz bands, and common communication norms include ISO/IEC 14443 and ISO/IEC 15693. The former are suitable for more close-range cards, vouchers and small label identification, which is often used for scenarios requiring a wider range of recognition. Actual distance is subject to label sizes, antenna design, metal shielding and power effect, not only by reference to protocol name effects. Source: ISO/IEC 14443:2018, ISO/IEC 15693:2018.

The label is still not read: the problem is usually in the material and location.

The most easily ignored feature on the project site is the labeling environment. Normal paper labels are placed in a card box, plastics swinger, and are usually easier to debug; and on metal shelves, metal tools or liquid-containing containers, label antennas can be detracted, i.e., convilation, with reduced reading and writing distance and stability.

Mark by environment

The data in the label should not be inserted directly into the full business file. It is more prudent to write a fixed-length asset number, such as 12 to 24 characters, and then handheld terminal search for names, locations and status in the business system. This reduces the pressure on label capacity and facilitates subsequent change of labels. The capacity, reading and writing times and data retention time should be based on a specific chip data manual, which cannot be replaced by common parameters.

A small range test can be performed when installed: 10 samples are taken from the same label, read in empty loads, attached to target materials and actual packaging, 20 times per sample read over again, records success, average response time and unusual position. This test is a project acceptance method, not a common industry indicator; the actual threshold values should be set according to operational beats and on-site risk.

Readers are loaded, data is unstable: the communication link has to be debugged separately.

The reader is not so simple as to "see the label" but also completes the search card, conflict prevention, identification and data reading and writing. Fixed-readers are suitable for installation at workstations, door-barriers or devices, mobile readers are better suited for inspection and inventory. Both antenna positions, powering methods and communication interfaces are different, and cannot be mixed with test conclusions.

Debugging can be carried in this order:

  1. Confirms that label types are consistent with the agreements supported by the reader and avoids frequency-band identical but uncommunicationable.
  2. Read without a cover and gradually add to the actual material such as containers, pallets, metal packages, etc., positioning factors that affect stability.
  3. Checks the connection of USB, serial, bluetooth or network interfaces to confirm data formats, character encoding and timeout.
  4. Sets a double-read filter to avoid a label being kept in the system on a continuous basis while remaining in the induction area.
  5. Retain original UID, business code, time stamp and equipment number to facilitate back-checking in case of dispute.

If a tag is read repeatedly in the detection zone, set a deduplication window at the application layer. For example, if the same UID appears repeatedly within three seconds, keep only one record. This is just a common starting point and should be adjusted for walking speeds, work pace, and device response times. A reader reports the result of communication with the tag. Whether an item was successfully received into stock must still be validated by the business system.

Handheld terminal access blocked: the real impact on efficiency is the process

Handheld terminals often carry the most tasks: to activate NFC, read labels, call interfaces, display items, get people to confirm results, upload records. When equipment is not configured properly, frequent log-ins are made on site, networks cannot be reconnected, screens are not visible outside, etc.

A functional operating page usually retains only four core states: To scan, recognized, confirmed, submitted. Read successful and show asset numbers, names, current positions and current status; keep local records when submitting failed, and clearly display "to upload" and do not allow staff to duplicate the operation with feelings.

The selection can be checked around the following parameters:

In Shanghai-based Selecting Tech's program design, we separate "Readable" from "Does Business Finished": First, we use a test tool to confirm tags and writers, then we check login with real workflows, confirm, upload, autopsy and report back. This leads to problems with interface fields, access and network strategies.

Once the three sets of equipment are completed: one process form for acceptance and inspection

The acceptance should not just show a picture of the label being read, but rather move from an on-site action to a data result. Using the asset inventory, for example, staff members take up the handheld terminal, enter the inventory task, read the tag, confirm the item, submit the record; and the system rechecks whether the number exists, the location matches, or the status duplicates.

Receiving and Inspection Results to be identified
Tag Recognition Stable reading in target material and installation position
reader Communications Interface data complete. Repeated reading does not result in duplicate entries
Terminal Operations Clear path for scanning, confirming, submitting and failure to retest
Operational verification Numbering, location, status and time record
Unusual treatment Break-nets, mislabelling, damage to and repetition of labels are all remedies.

If only closeness is required to identify the identity, handheld terminals may be sufficient; if a fixed position is automatically collected, fixed-type readers can be added; if the material is complex on the ground, anti-metal labels, antenna positions and actual packaging should be included in the test. The NFC equipment system does not focus on the number of devices, but rather on the label, the reader, the functional boundary between the handheld terminal and the business system is clear, and data can be accurately dropped from one reading to one operational action.