PDA scanner datasheet specs: the six printed lines that decide whether your team can use the device

Time：2026-10-06 Views：0

A PDA scanner datasheet runs to forty rows, thirty of them identical across every supplier: processor, memory, screen, battery, Android version, ingress class, radios. Those rows are not why a pilot fails. The scan-performance rows are — one or two each, printed without conditions, and skipped during the walkthrough.

The numbers are not fake. They are real measurements taken on somebody else's label, at somebody else's distance, under somebody else's light, and the gap to your dock is never printed. Each spec below gets four answers: what is printed, what the figure hides, how to test it, and the symptom on the floor.

1. Aperture and stand-off: what does a minimum element width tell you?

The printed line. The smallest element the reader resolves — an X-dimension in mils or tenths of a millimetre — sometimes with a distance, often without.

What it hides. Two things share the word aperture: how finely the sensor samples one element, and how wide an area it sees. Backing away keeps the element sharp but shrinks its image and widens the field, so the pixels across your narrowest bar fall while the neighbouring code enters the frame. Ask for element size against near and far limit: fixed-focus optics cannot be sharp at 10 cm and 2 m at once.

Test it yourself. Measure your two deciding labels with a caliper — symbol width over module count is arithmetic — then check whether the sheet's stand-off is where operators actually stand.

Warehouse symptom. Operators arm's-length the device to fit a long barcode inside the field, or read the neighbouring tote. Short codes get typed by hand.

2. Motion tolerance: was "reads everything" measured on a perfect label?

The printed line. "Reads all standard 1D and 2D symbologies," occasionally with a hand-carried motion tolerance, never with the test artefact named.

What it hides. The label. Print quality is graded by ISO/IEC 15416 for linear symbols and ISO/IEC 15415 for area symbols, and GS1 acceptance sits below the top of that scale. A fresh, large-element Code 128 on matte paper, square-on and evenly lit is close to the easiest target the standards contain, so a claim taken from it measures the floor of the job. Motion tolerance hides the same variable: freezing a sweeping trigger trades exposure against light.

Test it yourself. Two rows in a notebook: ten fresh labels and ten that have been in sunlight or handled on a pallet, same device and distance, twenty-five presentations each, first-pass successes only.

Warehouse symptom. New stock reads and aged stock does not; misses cluster by label supplier, print batch or lane, which is why a decoding complaint often belongs to the print process.

3. Depth of field versus scan range: which covers a mixed-distance job?

The printed line. A depth-of-field band, a scan range, or a sentence claiming the device reads "from 3 cm to 5 m".

What it hides. Two windows printed as one. Depth of field is the band over which optics stay sharp for one symbol size; a published range is usually the union of every symbol size's window, so its far end and its near end rarely describe the same label. For a fixed lens that band widens steeply with distance, which makes reach cheap to advertise and close focus the hard limit. A pallet label at 2 m and a bin label at 10 cm are two optical briefs asked of one window, and a mode switch between them costs seconds per pick. Long range is a lens decision: EDOO's MF31 is listed for long-distance code reading in a parking-lot application.

Test it yourself. Two targets at the real heights, five operators, twenty reads each, noting every step, crouch or mode change.

Warehouse symptom. The crew uses the device differently in two zones, throughput falls in deep racking, and the datasheet explains neither.

4. Duty cycle and scans per hour: which document covers your failure?

The printed line. A total scan count, an MTBF in hours, sometimes a sustained scans-per-hour figure — and, separately, a twelve-month warranty.

What it hides. That the two documents do not share a definition of a scan. A total-life count and an hourly rate are different claims — integral versus thermal condition — and a device can satisfy both printed numbers while failing at your combination: the rate decides whether illumination and sensor run hot for eight hours. The figure is measured on a bare module with a clean symbol; yours sits behind a hazed window and is triggered by a glove. Ask what unit is counted, what the warranty excludes, and what proof a claim needs; then send your scans-per-shift figure.

Test it yourself. Run one real shift at the real rate with logging and compare first-read success in the last hour against the first. Aging in this class shows as slow and intermittent, not dead.

Warehouse symptom. Misses cluster at end of shift and in the warmest hours; charging faults arrive before decoding faults. Where packs are swapped mid-shift — EDOO's M73 descriptor lists a hot-swappable battery — duty covers dock contacts and spare-pack cycles too.

5. Ambient light immunity: why a lux figure is not a glare solution

The printed line. "Ambient light: sunlight to 10,000 lux," sometimes with fluorescent light added.

What it hides. The angle of the light, which is the problem. A lux figure taken with the label evenly front-lit and square-on does not describe a dock door mid-afternoon, where sun arrives shallow, the label is gloss laminate and the return is a saturated specular band across the symbol; no decoder recovers a clipped highlight. Hazed or scratched polycarbonate scatters room light and the reader's own illumination back into the sensor, which is the other half of the optics. Cold rooms add condensation at a door crossing, and IEC 60529 covers liquid entering an enclosure, not water on an optical surface or the time to clear.

Test it yourself. Twenty reads on your glossiest label at the dock in the worst sun hour, then a fifteen-minute cold dwell and a count of failed attempts after the crossing.

Warehouse symptom. Failures appear only in the afternoon, or only after the freezer run. An operator wipes the window and the first read works, which is an optical finding rather than a superstition.

6. Illumination, aiming and polarization: what does "DPM capable" name?

The printed line. An illumination type (white LED, red, infrared), an aiming light, sometimes a polarizer option, and often "DPM: yes" as a checkbox.

What it hides. A direct part mark has no ink: its contrast is geometry, so the mark scatters light while the machined surface mirrors it, and under on-axis white light bright metal and its etch both go bright. Wavelength, incidence and polarization decide the read, and a handheld has least freedom: its lamp fires down roughly the lens axis beside a fixed window. Cross-polarization removes the mirror return from shrink film and polished metal but costs a large share of available light, so an "optional polarizer" line that omits the range penalty is half a sentence. The aiming dot marks one point while the decode field may be a metre across, and the two are not coaxial.

Test it yourself. Make the DPM claim name the mark process and finish, then test five of your parts and five wrapped cases: twenty-five presentations at the operators' stand-off, plus a pass tilted twenty degrees. A tilt that fixes it means a polarization problem.

Warehouse symptom. The case label reads and the part never does, and wrapped cases need a re-aim after the glare band moves. Mark reading at a station or on a moving line is the industrial fixed-mount conversation, not a handheld one.

The six lines, side by side

Spec as printed	What it was measured on	Question to ask the vendor
Minimum element width	One symbol size, one distance, dead centre	What element size at my distances, and how wide is the field?
"Reads all 1D and 2D symbologies"	A symbol near the top of the ISO/IEC 15416 or 15415 scale	What grade and X-dimension was the claim taken on?
Scan range or depth of field	The union of ranges across several symbol sizes	Near and far limits for my label, as one row
Scan life, MTBF, scans per hour	A bare module, manufacturer-chosen conditions	Which is a total, which a rate? What does the warranty exclude?
Ambient light immunity to N lux	Even front lighting, matte label, square incidence	Measured through the production window, at what glare angle?
Illumination, aiming, DPM option	The manufacturer's own reference marks	Which mark process, finish and geometry does it cover?

What to send instead of a comparison

Those six tests produce conditions attached to each printed line, and two suppliers become comparable once both must repeat your numbers on your labels. Ask for those conditions as documents via product documentation; the handheld scanner and scan engine lines are where the same optics are sold as components. Lead with your warehousing and logistics distances, labels and temperatures, and treat a custom line as an OEM or ODM question — EDOO's terms of OEM from 100 units with roughly 15-day samples leave room to test first.

FAQ

Which datasheet specs decide whether a PDA scanner will read my labels? Six printed lines decide it: the smallest element width and the stand-off it was measured at, the ISO/IEC 15416 or 15415 grade of the label behind any "reads everything" claim, depth of field as distinct from the published scan range, the duty figures behind the warranty, ambient-light immunity measured through the production window, and the illumination and polarization provisions for DPM and shrink-wrapped codes.

Is an ISO print-quality grade a promise that a PDA scanner will read my label? No — ISO/IEC 15416 and 15415 grade a label through a defined aperture, illuminant and geometry, which is a different optical system from an imager behind a scratched polycarbonate window. A grade does tell you whether a vendor's claim was taken on an easy artefact, and a large near-perfect symbol is the weakest evidence a datasheet can carry.

What is the difference between depth of field and scan range on a PDA scanner datasheet? Depth of field is the distance band over which optics stay in focus for one defined symbol size, while a published scan range is the union of windows across every symbol size the device can resolve, so its two ends rarely apply to the same label. For a fixed lens that band widens steeply with distance, which is why close focus rather than reach is the limit that fails in the field.

Can I test a PDA scanner datasheet claim without a lab? Yes, with your own worst artefacts and a notebook: measure element width with a caliper, count first-pass reads out of twenty-five on fresh and degraded prints at the real stand-off, then repeat at the dock in the worst sun hour and after a cold-room dwell. That sheet makes two datasheets comparable, and the contact team can take it before a quotation is drafted.