When there is no reader
Connecting a reader needs the installed Android app with the reader maker’s own library available. A browser has no way to talk to the hardware, and the iOS app does not support readers yet. Where none of that is in place, the screen says No reader on this device and why — for example This build has no reader plugin, so tags are read by camera or by a wedge scanner. A wedge scanner (one that types what it reads into the box you are in) works with any scan box in the app without being connected here.Connecting
With a supported reader present, the screen shows the reader’s maker and model and its state:
Connecting is a decision about the handset rather than about one screen: pick a sled off the charging rack at the start of a shift, connect it once, and every scan box in the app — Scan, the verification count, encoding and locating tags — knows about it from then on.
Sweeping for tags
What can you hear? reads for a moment and lists the tags that answered, nearest first, each with its signal strength and how many times it was heard ( dBm · ). It marks this one where one tag is clearly closest, too close to call where two are about as near, and nothing heard twice where no tag answered reliably. Nothing answered in that half-second. means no tag replied — move closer and try again. This is useful for finding which asset in a rack answers to which tag, or confirming a tag is readable at all. To look a tag up in the register, use Read a tag on Scan.Encode and locate tags
Writing an asset’s code onto a tag, and finding it again.
Labels
Designing the labels and tag codes your assets carry.