A useful RFID reader quote identifies the card or tag, reading or writing task, host interface, output and quantity. Compare the same configuration and included items, then confirm sample costs, lead time and order terms in writing. Henrium quotes by model and configuration; this guide helps you prepare the requirements.
Choose the reader from the exact card chip and required task. L110-U reads the ID of EM4100-compatible 125kHz cards; H110-U reads the UID of supported 13.56MHz ISO/IEC 14443A cards. Neither model reads the other band or writes cards. ICODE uses a different HF protocol. Confirm the chip, host and complete output with your actual cards before ordering.
ISO/IEC 14443 and 15693 both use 13.56 MHz, but a reader must list the tag's protocol. In Henrium's catalogue, H110-U reads ISO 14443A UIDs and H155-U reads ICODE 2 ISO 15693 UIDs at up to 80 mm. H155-U does not access tag user memory or AFI/EAS. Its default 10-digit decimal output is not the full 8-byte UID; confirm the required output and test unnamed chips with your samples.
Choose the interface from the device that receives the card number. USB keyboard emulation suits PC and Android software that accepts typed input. RS232 suits a COM port within about 15 m. RS485 suits long or shared runs up to about 1,200 m. Wiegand suits door access controllers, and TCP/IP suits readers that report to a networked server.
EM4100 and TK4100 are interchangeable read-only 125kHz chips. Each sends one thing to a reader: a fixed 64-bit code carrying a 32-bit ID number. The card has no writable memory and no security. Readers show the ID as a 10-digit decimal, 8-digit hex or Wiegand facility and card number, so pick the format your system stores.
An ISO magnetic stripe has three tracks. Track 1 stores up to 79 alphanumeric characters at 210 bpi, Track 2 up to 40 digits at 75 bpi, and Track 3 up to 107 digits at 210 bpi. HiCo (about 2,750 Oe) and LoCo (about 300 Oe) describe how hard a stripe is to write or erase, not which tracks it holds.
MIFARE Classic, MIFARE Ultralight and NTAG213 are all ISO/IEC 14443A chips at 13.56 MHz, so any 14443A reader can read their UID. They differ in UID length (usually 4 or 7 bytes), memory and security. Reading memory or NDEF records needs a read/write reader; a UID-only keyboard reader outputs the chip's serial number only.
NFC is a 13.56MHz subset of RFID. An NFC reader, including a phone, reads 13.56MHz cards and tags such as MIFARE and NTAG, but it cannot read 125kHz EM4100 or TK4100 cards, 134.2kHz animal microchips or UHF tags. No app or update changes this. Those tags need a reader built for their frequency.
An RFID card stores one binary ID, but readers, card printers and controllers display it in different formats. The same EM4100 card can appear as 0793541918 (10-digit decimal), 2F4C7D1E (8-digit hex) or 076,32030 (Wiegand 26). Mismatches almost always come from base, truncation or byte order, not from a faulty card.
A keyboard wedge is a reader that presents itself to the computer as a USB keyboard. When a card is presented, it types the card number, often followed by Enter, wherever the cursor is. It needs no driver or SDK, but data flows one way only. Choose virtual COM or PC/SC when software must control the reader.
Choose a USB-C reader by tag: H220-C for ISO 14443A UIDs, L220-C for EM4100-compatible IDs, U220-C for EPC Gen2 EPCs and A220-C for FDX-B/EMID animal IDs. On Android, Henrium's plug-in models need USB OTG and type IDs into the focused field; they do not read tag user memory or write tags. Confirm the exact host, chip and full output string on a sample. iOS is not a listed host.
When an RFID reader does not read a card, the cause is usually a mismatch, not a fault. Check power first, confirm the card's frequency and standard, present one card flat within range, then find where the output goes. Test with a known-good card in a text editor before you blame the reader or your software.
Match a keyboard-output reader to the exact card chip and host. Format the card-number column as Text before reading, keep the input cell focused and confirm Enter or Tab behavior. Compare the complete output with the number your system stores. The downloadable English workbook provides a blank text-formatted card log; timestamps are entered manually.
Find the format your controller stores, such as a 10-digit decimal or a Wiegand 26 facility code and card number. Set the USB desk reader, or the software, to produce that same number. Enroll one pilot card and check it at a door before bulk issue. Then enroll each card by clicking the card field and presenting the card.
Wiegand 26 and Wiegand 34 use the same two data wires and timing; they differ in how many ID bits reach the controller. A 26-bit frame carries 24 data bits (8-bit facility code 0–255 plus 16-bit card number 0–65,535) between two parity bits. A 34-bit frame carries 32 data bits, so a full 4-byte card ID arrives intact.
A Wiegand reader needs four core connections: +V (usually 12 V DC), GND, D0 and D1, plus optional LED and buzzer control. Tie the reader and controller grounds together, use shielded stranded cable and check the voltage at the reader under load. Most faults on site come from swapped D0/D1, a missing common ground or a format mismatch.
Choose by what moves. If tagged vehicles, pallets or people pass a fixed point, use a fixed or integrated reader. If staff walk to tags on shelves or assets, use a handheld. If a person presents one tag at a desk, use a desktop reader/writer. An integrated reader houses reader and antenna together, so it installs as one unit.
For desk encoding, Henrium U120-U and U140-U EPC Gen2 reader/writers list up to 0.2 m write range and 0.5 m read range. Their default USB keyboard output sends reads to a focused field; writing requires confirmed host software and a command-capable build, typically virtual COM. Match the tag chip, memory bank and EPC length, encode one tag at a time, and read back each write. Standard Gen2 TID memory cannot be rewritten.
A UHF reader separates many tags by anti-collision: each Gen2 tag answers in a random time slot set by the Q value, and tags already read stay quiet according to their session flag. To raise multi-tag read rates, fix tag placement and antenna layout first, then tune RF power, session, target and Q, and count unique tags read.
UHF RFID has no single worldwide band. The US, Canada and Mexico use 902–928 MHz at 4 W EIRP; the EU and UK use 865.6–867.6 MHz at 2 W ERP; India uses 865–867 MHz; China 920.5–924.5 MHz; Japan 916.7–920.9 MHz. EPC Gen2 tags work in all of them, but each reader must be supplied for the country where it operates.
UHF RFID read range depends on how much reader power reaches the tag chip. That depends on radiated power (EIRP), capped at 4 W EIRP in the US and 2 W ERP in the EU, on the tag's chip and antenna, and on what the tag is mounted on. Desktop readers are built for 0.5 m, gate readers for meters.
No. A phone's NFC works only at 13.56MHz, while ISO pet microchips work at 134.2kHz, so no app can read an implanted chip with the phone alone. A phone can show the number if you add a 134.2kHz reader: a USB-C plug-in for Android, or a handheld scanner that sends the ID over Bluetooth.
FDX-B and HDX are the two ways ISO 11785 lets a 134.2kHz animal tag send the same 64-bit ISO 11784 ID. An FDX-B tag replies while the reader's field is on. An HDX tag stores energy, then replies while the field is off. A reader reads HDX tags only if it supports HDX.
ISO 11784 defines the 64-bit code stored in an animal RFID tag. ISO 11785 defines how a 134.2kHz reader powers the tag and receives that code, by FDX-B or HDX. Readers usually show the code as 15 digits: a 3-digit country or manufacturer code, then a 12-digit national ID.
A useful RFID reader quote identifies the card or tag, reading or writing task, host interface, output and quantity. Compare the same configuration and included items, then confirm sample costs, lead time and order terms in writing. Henrium quotes by model and configuration; this guide helps you prepare the requirements.
To source RFID readers, write an RFQ around the card, the host, the interface and the exact output, then ask for a quotation on a standard reader that already reads your cards. Test a sample quantity and configuration confirmed in the quotation against a written plan, record the accepted settings in the order specification, and confirm prices, lead time and warranty terms before a volume order.
We use optional Google Analytics cookies to understand site use. Google Analytics stays off unless you allow it.
You can change your choice in the footer. Privacy policy