UCODE 9m

UCODE 9m operates as a passive backscatter tag IC in the 860-960 MHz UHF band under EPCglobal Gen2V2, harmonized with ISO/IEC 18000-63. The reader initiates all exchanges (reader-talks-first); downlink data uses pulse-interval encoding while the tag modulates backscatter amplitude/phase (ASK/PR-ASK) to return data on the carrier. Anti-collision follows the standard slotted-Q algorithm with session flags (S0-S3) and supports dense-reader-mode operation, letting many UCODE 9m tags be singulated reliably amid adjacent readers — a key requirement in industrial environments. Memory is organized into Reserved (kill/access passwords), EPC (96-bit, extendable to 496 bits), and TID (48-bit, factory-serialized) banks; there is no User memory bank, which trims die size and cost. The chip's RF front-end and antenna-matching are tuned specifically to compensate for detuning and field cancellation caused by nearby metal, distinguishing it from general-purpose UCODE variants built on the same platform, such as UCODE 9.

UCODE 9m is built for tags that must be mounted directly on or very close to metal — a scenario that kills read range on standard UHF inlays. Typical deployments include asset tracking of tools, cages, and reusable metal containers; industrial IoT identification of machinery, racks, and metal-chassis IT equipment (servers, networking gear); and supply chain tracking of metal totes and pallets in dense warehouse RF environments. It ships primarily as on-metal labels or hard tags with integrated spacer/foam layers rather than as a bare inlay, since the mounting substrate is intrinsic to its RF performance. Dense-reader-mode support makes it a strong fit for portals and gates with multiple readers operating simultaneously. Compared with the standard UCODE 9 (optimized for non-metal substrates), UCODE 9m trades some raw sensitivity for metal tolerance; compared with UCODE DNA, it omits cryptographic authentication, making it unsuitable where brand protection or anti-counterfeiting is required.

UCODE 9m works with any EPC Gen2V2 / ISO 18000-63 compliant fixed or handheld reader (e.g., Impinj, Zebra platforms); no proprietary air-interface extensions are needed for basic inventory. Standard commands apply: SELECT and QUERY/ACK for inventory, READ/WRITE against EPC bank, ACCESS to transition into the secured state using the 32-bit access password before issuing WRITE or LOCK, and KILL with the 32-bit kill password to permanently disable the tag. Cover-coding protects password transmission over the air. A key integration gotcha: there is no User memory bank, so application data must be encoded into the EPC bank itself (which supports extension up to 496 bits) — plan EPC encoding schemes accordingly, since longer EPCs can reduce effective read range and increase singulation time. The 48-bit TID is factory-locked and useful for tag authentication at the application layer (not cryptographic). Privacy mode can mask the EPC on command for data-protection use cases; verify your reader/middleware supports toggling this feature.

UCODE 9m is distributed through NXP's standard RFID inlay/label partner network and typically appears pre-converted into on-metal tags or labels by inlay converters rather than sold as a raw die to end users; check with major RFID label converters and distributors for stocked SKUs tuned to your metal substrate. Expect reel-based MOQs (commonly in the low thousands) and lead times typical of custom on-metal label conversion, which can run longer than standard inlays due to spacer-layer construction. When sourcing, ask suppliers for read-range performance data on your actual metal substrate and mounting geometry, confirm Gen2V2 firmware support on your reader fleet, and verify EPC/TID encoding services are available at conversion. If your application needs cryptographic authentication, cross-shop to UCODE DNA; if the tag will not be metal-mounted, the standard UCODE 9 may offer better range and lower cost.