ACR122U NFC Reader
ACR122U USB contactless reader/writer for PC/SC integration.
RFID & NFC Readers
Desktop NFC reader/writers and a Bluetooth animal-ID scanner for integrators encoding and testing cards and tags. Support varies by model across MIFARE, DESFire, NTAG and 125 kHz, with PC/SC or SDK interfaces. Confirm your card or tag, operating system, software interface and required operations, and ask about current availability and sample evaluation before selecting a model.
Find your starting point
-
-
Bluetooth RFID Scanner
The R901 is a handheld 134 kHz low-frequency RFID reader with Bluetooth, designed for reading FDX-B animal ear tags in livestock management.
-
NFC Reader/Writer with Free SDK
The Digital Logic µFR Classic CS is a desktop NFC reader/writer for supported 13.56 MHz cards and tags, using the manufacturer's SDK by default.
Selection & ordering guide
Choose a reader for your cards and software
This catalogue includes desktop NFC readers and a Bluetooth animal-ID scanner. These are different integration paths. A purchasing decision needs the exact card or tag, host device and software interface; the connection type alone does not define compatibility.
List the cards and required operations
Provide the precise chip or tag standard and explain whether the application reads an identifier, reads application data or writes and authenticates cards. Confirm each required operation against the selected reader’s documentation.
Define the host integration
Specify the operating system and version, application stack, host interface and whether your software expects PC/SC or a manufacturer SDK. Ask the software developer to review the driver and API requirements before ordering.
Check model status and test a unit
Some listed desktop models are legacy products. Confirm current availability, driver support and any proposed replacement, then test a sample with your actual cards and application before approving a deployment quantity.
Choosing a reader or writer for your cards and software
The catalogue readers are desktop NFC encoders for 13.56 MHz card families and a Bluetooth LF scanner for animal ID; these are different integration paths. Confirm the card, the host and the software interface — the connection type alone does not define compatibility. Work through the factors below before choosing a model.
For PC-linked HF issuance and encoding, review the ACR122U against your supported card application, and the NFC reader/writer with free SDKs where the host software integrates through an SDK; the Bluetooth animal-ID scanner covers LF livestock workflows. Confirm the driver and API with your developer, and test a unit with your actual cards before ordering a deployment quantity. Bulk or bureau encoding is available through the RFID encoding service.
| Reader attribute | What to confirm | Why it decides fit |
|---|---|---|
| Interface | USB, serial, Ethernet or Bluetooth to the host | Sets how the reader connects and whether it suits a fixed desk or a mobile workflow |
| Frequency band | 13.56 MHz HF/NFC, or 125/134 kHz LF (134.2 kHz for FDX-B animal ID) | A reader only reads its own band; an HF encoder cannot read an LF animal tag, and vice versa |
| Supported chips | The exact card standard, and whether you read a UID, read data, or write and authenticate | A reader listed for a family may still not perform every operation your application needs |
| Driver model | PC/SC versus a manufacturer SDK | PC/SC is the portable path for desktop HF readers; an SDK adds features but ties you to a language and version |
| Operating system | The exact OS build the host runs | Drivers diverge across Windows, macOS and Linux versions, and across ARM hardware |
| Keyboard-wedge output | Whether the reader can type a UID as keystrokes | A wedge needs no driver for simple ID capture, but cannot write or authenticate a card |
| Typical job | One-at-a-time issuance and encoding, or mobile field scanning | Match the reader to the dominant task rather than to the enclosure shape |
What to include in your enquiry
- Exact cards or tags and the operations the application must perform.
- Host device, operating system, interface and software or SDK requirements.
- Existing reader model, required accessories and replacement constraints.
- Evaluation quantity, deployment quantity, destination and intended schedule.
Include what you know. If the chip or product is undecided, describe the application and current equipment so we can review the options with you.