Key takeaways
- 13.56 MHz describes frequency; it does not establish ISO 14443 and ISO 15693 support in the same reader.
- NTAG213/215/216 use ISO 14443 Type A; ICODE SLIX2 uses ISO 15693. Identify the actual chip before choosing a reader.
- UID capture, memory access, NDEF writing and authenticated application reads are separate acceptance requirements.
- Use the complete SKU and firmware when comparing readers. PC-110-MS-N-IC and HF-160-V-T explicitly list ICODE read/write.
- Validate representative tags, host software, output format and the final installation before a bulk purchase.
A reader marked 13.56 MHz can read your NTAG card and still miss an ICODE label. The frequency matches, but the communication protocol may not. Before replacing cards or ordering readers, identify the chip, check the complete reader variant, and define whether you need a UID, memory data or an authenticated application transaction.
ISO 14443 and ISO 15693: what to check
| Purchase question | ISO/IEC 14443 | ISO/IEC 15693 |
|---|---|---|
| RF frequency in this comparison | 13.56 MHz | 13.56 MHz |
| Example chips | NTAG213/215/216: Type A; DESFire: Type A with ISO 14443-4 | ICODE SLIX2 |
| Reader specification to request | Required Type A and/or Type B, plus the card commands | ISO 15693 and required tag commands |
| Application requirement | UID, memory or protected application access, specified separately | UID, block access or chip-specific operations, specified separately |
| Working distance | Validate the reader/tag installation | Validate the reader/tag installation |
NXP identifies NTAG21x as NFC Forum Type 2 and ISO 14443 Type A, while ICODE SLIX2 uses ISO 15693 and NFC Forum Type 5. NFC Forum’s Type 5 specification defines NDEF detection, reading and writing over NFC-V. “NFC” therefore does not identify one interchangeable tag protocol. A multi-protocol reader must list the technologies you actually use.
If the chip is unknown, start with the tag supplier’s specification or a diagnostic report from a compatible reader. On Android, tag technology APIs distinguish NfcA, NfcB, NfcV, IsoDep and Ndef; getTechList() reports discovered technologies. Keep the chip identification and target device/application in your sample brief. A phone’s successful scan does not establish compatibility with a different desktop reader.
Three different meanings of “reads the card”
UID capture returns an identifier. Your enrollment database may require a specific byte order, length or decimal conversion. Compare the exact output with one known record; our USB output format guide covers those checks.
Memory access reads or writes the intended pages, blocks or files. A reader that reports an NTAG UID may lack NTAG writing commands. Reading raw memory also differs from encoding a valid NDEF URL. Specify payload, target area, protection state and software workflow.
Authenticated application access needs the credential’s supported authentication, reader commands, application settings and controlled keys. DESFire EV3, for example, supports application authentication and protected file access. A reader’s DESFire UID listing does not establish those transactions. Use the Classic/DESFire guide when secure access is the requirement.
Compare exact reader variants
These are documented selection candidates, with operations taken from their product records. They are not a tested compatibility list for your tags or software.
| Complete SKU | Documented capability relevant here | What still needs confirmation |
|---|---|---|
| PC-120-M | USB 13.56 MHz UID reader; this family does not list ISO 15693 | Actual credential and output format; unsuitable as an assumed ICODE solution |
| PC-110-MS-N-IC | USB top tier adds ISO 15693 / ICODE 2 read/write | Exact ICODE chip, commands and host application; other PC-110 tiers omit this addition |
| HF-160-MA-T | ISO 14443A build with NTAG read/write and APDU commands; TTL UART, 5 V supply | Required chip/operation and host logic limits |
| HF-160-V-T | ISO 15693 build: ICODE read/write; other ISO 15693 tags listed as read-only; TTL UART, 5 V supply | Exact chip, command protocol and host electrical interface |
| HF-200-U | USB CCID / PC/SC; ISO 14443A/B and 15693 listed, including 15693 read/write commands | External 50 Ω antenna, listed Windows host and application transactions |
HF-160 builds are distinct configurations; do not combine their capabilities into one order. For HF-200-U, PC/SC describes host access, not keyboard output or automatic NDEF encoding. See the USB buying guide or OEM module guide for broader interface choices.
A sample acceptance check before buying in volume
- Record the configuration. Reader SKU, firmware, tag chip, host OS/application and antenna or enclosure.
- Test the real task. Compare UID output with the database. For writing, write approved test data, remove the tag, then read it back. Use dedicated test tags rather than production credentials.
- Test protected operations separately. Define authorized test credentials and success/failure behavior. Keep secret keys out of an inquiry; agree a secure provisioning process separately.
- Measure placement and repeatability. Test orientations, nearby metal, the required distance and consecutive presentations. Record missed, repeated and incorrect transactions.
- Agree pass criteria. Specify expected output or read-back bytes, acceptable failures and the tested tag/host combinations before approving the batch.
Send a useful compatibility inquiry
If you do not know the chip, say so. Provide the tag label/specification or diagnostic technology report, the task, and the existing reader model if available.
Your brief should include:
- Tag chip or protocol, plus representative sample availability.
- UID capture, memory read/write, NDEF encoding or authenticated access.
- Expected output example or approved test payload; no secret keys.
- Host OS/application and USB, UART or other required interface.
- Mounting surface, target working distance, sample quantity and forecast quantity.
Request a compatibility review and quote or use the USB project brief to prepare your requirements. Confirm the proposed variant and sample test scope before ordering.
Sources and review scope
Reviewed 6 October 2026. Product comparisons use the linked ValenID records; firmware, commands and the actual system require sample validation. The following sources explain protocol and application distinctions and do not certify these reader products:
- NXP NTAG213/215/216: Type 2 / ISO 14443 Type A.
- NXP ICODE SLIX2: ISO 15693 / Type 5.
- NFC Forum Type 5 Tag specification: NDEF operations over NFC-V.
- Android advanced NFC: tag technologies, NDEF and direct communication.
- NXP MIFARE DESFire EV3: ISO 14443 Type A and application authentication.
Frequently asked questions
Can every 13.56 MHz reader read ISO 15693 tags?
No. Check for explicit ISO/IEC 15693 support on the ordered variant and confirm the required tag commands. A frequency listing or ISO 14443 support alone is insufficient.
Why does my MIFARE reader not read ICODE tags?
The reader may support ISO 14443 but omit ISO 15693. Check the exact ICODE chip, reader variant and enabled protocol. Also test tag placement, mounting materials and the host application's expected data.
Is ISO 15693 the same as NFC Type 5?
NFC Forum Type 5 defines tag operation using NFC-V technology based on ISO 15693. ICODE SLIX2 is a Type 5 example. ISO 15693 support alone does not establish NDEF formatting or every chip-specific operation.
Does reading a UID mean the reader can write the tag?
No. UID capture does not establish memory writing, NDEF encoding or secure application access. Confirm the exact chip, commands, writable or protected areas and host software.
Does ISO 15693 guarantee a longer read distance?
No fixed distance follows from the protocol name. The reader, antenna, tag, power and installation determine the working distance. Measure the required operation with the actual sample assembly.
Want a second opinion on your spec?
Send your application, existing hardware, interfaces and quantities — we'll review the requirements and quote within 24 hours.