Direct answer: A fixed UHF RFID reader quote must include the power source, Ethernet path, reader model and firmware, antenna installation, event software and restart procedure. A lit network port proves neither that the reader obtained the power level needed for its intended configuration nor that an accepted business event can reach the application. Test the installed read point as a system, including a controlled power interruption.
The fixed-versus-handheld guide determines where the business observation belongs. The RF power guide compares conducted output and radiated configurations. This page addresses a different procurement gap: whether the installed fixed point receives its specified electrical power, stays connected to the intended network service, and recovers without falsely completing or losing events.
Quote the power path, not merely “PoE supported”
Record the exact reader SKU and regional variant, PoE class or manufacturer power requirement, switch or injector model, available port budget, cable path, permitted accessories and antenna configuration. Ask whether a feature requires PoE+ rather than basic PoE and how the reader reports the allocated power. The project should not assume that a port link light means full-power operation.
As a bounded third-party example, the Impinj R700 Series RAIN RFID Readers Datasheet, version 2.0 lists Ethernet-based 802.3af PoE and 802.3at PoE+ with LLDP power negotiation for the R700/R720 series. Its model table gives different maximum transmit-power conditions for PoE and PoE+. The Impinj R700 Series Quick Start Guide recommends PoE+ for full reader functionality and maximum transmit power. Those statements apply to the named Impinj series and documented versions—not to every fixed reader, an AIDC GO handheld, or a site’s approved RF setting. Verify the actual offered reader’s current documentation before selecting a switch.
Power budget is not only a nominal switch rating. Document how many ports will be powered simultaneously, any injector and backup-power plan, and which peripheral loads are allowed by the exact reader instructions. A separate DC input must not be inferred from the presence of an Ethernet jack; the Impinj datasheet describes its named series as powered through Ethernet. Follow the proposed manufacturer’s installation and region rules for antennas and RF output.
Trace one observation through the network
Editorial scenario, not a customer installation or test result: a warehouse proposes two fixed readers at a controlled dispatch lane. Reader R-A sees tag T-17 as a load moves past, while the application should create one approved dispatch observation for task D-204. The site has an available PoE switch port but has not established its allocated power, VLAN access or restart behavior. An installation check must retain four separate facts: the reader is powered in its required operating mode, the tag observation is produced, the application receives the event, and the dispatch rule accepts the intended task. None substitutes for the next.
- Power and boot: identify the switch/injector port, document negotiation or allocated power by the vendor-supported method, and observe the reader’s boot and antenna configuration. A link LED alone is insufficient.
- Network delivery: use the approved address, firewall and application endpoint configuration. Confirm reader identity and time source in the event record. Do not expose management interfaces simply to make a trial work.
- Business decision: compare raw tag observations with the application’s accepted task event. A nearby non-task load must not be silently included as a dispatch.
- Recovery: under a controlled maintenance window, interrupt and restore the authorized power or network path. Check whether the reader returns to the intended configuration, how gaps are marked, and whether buffered or repeated observations generate duplicate accepted events.
If T-17 is visible in reader output but absent from the application, investigate transport and mapping before changing antenna power. If the reader restarts but the application shows its previous event as new, retain source timestamp and task identity to diagnose replay. If a network outage cannot be safely induced, label recovery evidence incomplete and use an approved bench setup; do not stage an unsafe production interruption.
Separate three failure classes at acceptance
Insufficient or mis-negotiated power: the device may boot yet operate under a reduced permitted configuration. Compare its actual status with the exact vendor documentation, not a generic PoE assumption. Network or service failure: the reader may observe tags locally while events never reach the assigned endpoint; preserve local and server-side timestamps and errors. Business-rule failure: raw events arrive, but the application accepts the wrong task, direction or duplicate. A stronger RF signal cannot correct an event-rule defect.
For each failure, record the proposed reader model and firmware, power-source part and port, switch configuration owner, Ethernet path, antenna and region configuration, software interface, expected event and recovery owner. Set project-specific availability and event criteria before a trial; this article provides no uptime, cable-length or read-rate guarantee. The multiple-reader guide covers overlapping read zones after the physical points are selected.
Resolve the commercial boundary
Ask the fixed-reader supplier for its approved installation and current firmware/API documentation, and the site IT team for the port, addressing and service route. AIDC GO’s RFID mobile-computer range may support a separate manual exception check; it is not a claim that AIDC GO sells the fixed reader, PoE infrastructure or event software described here. Bring the site diagram, task rule and sample tags to Integration Support and contact AIDC GO to define the mobile/fixed integration boundary.
Sources and limits
The Impinj R700 Series datasheet, version 2.0 and R700 Series Quick Start Guide were checked on 2026-09-24 for model-specific power and Ethernet statements. They do not certify any AIDC GO product or the site’s switch, network, RF configuration or application outcome. The dispatch example and acceptance sequence are editorial plans, not measurements.