How to Test an NFC Reader on Windows: Complete Test Procedure
← Back to the ACS testing and utilities centre
How do you test an NFC reader on Windows properly? Work through six steps in order: confirm Windows and PC/SC see the reader, check that a tool sees each card arrive and leave, try every card type you will use, measure the read distance and best position, repeat the tap many times to prove it is stable, and finally read an NDEF message from an NFC tag. Write down the result of each step on a checklist. A reader that passes all six is ready for your application; a failure tells you exactly which layer to fix.
This page is the full test procedure for ACS NFC readers such as the ACR1252U, ACR1552U and ACR122U, using only free tools: the official ACS QuickView, Script Tool and Web APDU Tool, and BSD Infotech's own reader utilities. If you only want to choose a tool or run a two-minute check, start at the 3 basic checks on our testing centre. If you have not installed the reader yet, use the driver and first-test guide for your model first. BSD Infotech is an independent ACS supplier and integrator, not the manufacturer.
The Six-Step NFC Reader Test Plan
Each step depends on the one before it. If a step fails, stop and fix it: a missing reader or a stopped service makes every later test fail for the wrong reason.
| Step | What it proves | Tool | Pass looks like |
|---|---|---|---|
| 1. Reader | USB, driver and the Windows PC/SC layer work | Device Manager, Smart Card service, QuickView reader list | The reader is listed by Windows and by a PC/SC tool |
| 2. Card presence | The antenna detects a card and reports its removal | ACS QuickView | Card shown on every tap, gone on every removal |
| 3. Card types | The reader works with each card you will use | Script Tool or Web APDU Tool, BSD utility | UID read from every card type; data read where keys allow |
| 4. Read range and position | Where and how far away cards are read | QuickView and a ruler | Reliable when flat on the reader; maximum distance recorded |
| 5. Repeated taps | The reader, cable and driver stay stable | QuickView, Script Tool | Every tap of a run detected, no tool restarts needed |
| 6. NDEF tag read | The reader reads NFC Forum data, not just the UID | Script Tool or BSD utility, plus a phone | The tag's NDEF message (for example a link) is read correctly |
Before You Start: Your Test Kit
- A Windows 10 or 11 PC with the reader plugged straight into a USB port on the computer, not a hub or monitor port, for the first run.
- The ACS driver installed for your model. See the ACR1252U, ACR1552U or ACR122U driver and test guide, or the general guide to installing ACS reader drivers on Windows.
- The test tools. ACS QuickView and ACS Script Tool from the ACS utility tools page, or the browser-based ACS Web APDU Tool instead of the Script Tool. Optionally a BSD reader utility.
- A set of test cards you own, one of each type your project will use, for example MIFARE Classic 1K, NTAG or MIFARE Ultralight, and DESFire. Use cards still on their factory keys for the data tests. Label each card (A, B, C...) so results can be matched later.
- An NFC tag with an NDEF message on it, such as an NTAG with a web link, for step 6, and an NFC phone to cross-check it.
- A ruler and some non-metal spacers (sheets of card or paper) for step 4.
- The printable checklist or a copy of it in a spreadsheet.
Close every other card program before you start, including other test tools and the ACS Reader Monitor Program. A program that is connected to the card can block a test tool, and you will record a failure that is not the reader's fault.
Step 1: Confirm Windows and PC/SC See the Reader
Before you touch a card, prove the reader exists at every layer. This step is covered in depth on two separate guides, so here is only the test and its pass mark.
- Device Manager. The reader appears under Smart card readers without a warning mark, and disappears and returns when you unplug and replug it. Full method: check whether Windows detects the ACS reader.
- Smart Card service and PC/SC. The Smart Card service is running and a PC/SC tool lists the reader. Full method: check PC/SC reader status.
- QuickView reader list. Open ACS QuickView. Your reader is in its reader list. Readers with a SAM slot, such as the ACR1252U and ACR1552U, can show more than one entry: the contactless (PICC) interface is the one you test with NFC cards.
Pass: the reader is in Device Manager, the service is running and QuickView lists the reader. Record: the reader name exactly as QuickView shows it and the driver version from Device Manager (reader's Properties > Driver).
Step 2: Card Presence, Arrival and Removal
ACS describes QuickView as a polling tool that shows reader and card details and checks whether a card is present or absent. That is exactly what this step needs.
- Select the contactless reader in QuickView with no card near it. It should show no card present.
- Place card A flat in the centre of the reader. QuickView should report a card present and show its details, including the ATR (the identification bytes a PC/SC reader returns for a card).
- Lift the card away by at least 20 cm. QuickView should report the card removed.
- Repeat with one card of each type in your set.
Pass: every placement is shown as a card present and every removal as card absent, without restarting QuickView. Record: the ATR of each card type. The same card type should give the same ATR each time, which makes it a handy fingerprint for later tests.
Many ACS readers also beep or change LED colour when a card arrives, but both are controllable by software, so do not use them as the pass mark: use the tool's display.
Step 3: Test Every Card Type You Will Use
Card presence proves the antenna works. This step proves the reader can talk to each card type. Use one read-only command for every card, then one data read where you know the keys.
3a. Read the UID of every card
In the ACS Script Tool or the ACS Web APDU Tool, connect to the contactless reader and send the PC/SC Get Data command FF CA 00 00 00. The reply is the card's UID followed by the status bytes 90 00. The step-by-step method is on each model guide: ACR1252U, ACR122U, and the ACR1552U Script Tool test.
Pass: a UID and 90 00 from every card type. Typical lengths are 4 bytes for MIFARE Classic 1K cards and 7 bytes for NTAG, MIFARE Ultralight and DESFire, but some cards use other lengths, so record what you get rather than expecting a number. An error status such as 6A 81 or 63 00 means the reader did not complete the command for that card.
3b. Read data where the keys allow it
- MIFARE Classic 1K on factory keys: read one block with the key
FF FF FF FF FF FF, in the ACS Smart Card and Reader Tool (ACS lists MIFARE Classic and Ultralight among its supported cards) or in a BSD utility. - NTAG or MIFARE Ultralight: these need no key to read; step 6 covers reading their NDEF data.
- DESFire on factory settings: a UID read is enough for a reader test. The BSD ACR1252U and ACR1552U utilities can read DESFire cards whose keys are still at the factory default.
- Cards that carry your own keys: test them with your own application and your own keys. No tool on this page recovers or bypasses card keys.
Pass: the data you expect is returned. A UID that reads but a data read that fails is almost always a key or access-rights issue, not a reader fault.
Not yet tested by BSD. ISO 15693 (ICODE) tags, which only the ACR1552U of these three readers supports, and FeliCa cards are not on our test bench yet. Treat any steps for them as untested until we update this page.
Step 4: Read Range and Card Position
ACS quotes a maximum read distance for each reader (see the model table), always with the words "depending on tag type". Small tags, stickers and key fobs have small antennas and are read from closer than a full-size card. This step finds the real distance for your cards and the best place to tap.
- Find the sweet spot. With QuickView open, slide card A slowly across the reader surface. Note where it is detected first and lost. The centre of the marked area is usually best.
- Measure the distance. Put non-metal spacers (sheets of card or paper) on the reader and lay the card on top. Add spacers until detection becomes unreliable, then measure the height with a ruler.
- Repeat for each card type and for any tag in a holder, wallet or badge reel your users will have.
- Check the real installation. If the reader will sit on or near a metal desk, kiosk panel or behind a cover, repeat the test there. Metal near the antenna usually shortens the range.
- Try two cards at once if users may tap a wallet. ACS lists anti-collision for these readers; on the ACR1252U ACS notes that only one tag is accessed at a time. Record which card the tool reports and whether the result is consistent.
Pass: every card is detected reliably when laid flat on the reader in the sweet spot, and you have recorded a maximum distance for each card type. A measured distance below ACS's maximum is not a fault on its own; use it to decide how users should present cards (for example "tap and hold flat").
Step 5: Repeated Taps and Stability
A reader that works once can still fail in daily use: a loose cable, a weak USB port, a power-saving setting or another program grabbing the reader. Run these three short tests.
- 20 taps per card type. In QuickView, tap and remove the card 20 times at a normal user's speed. Count the taps the tool missed.
- Hold test. Leave a card on the reader for 10 minutes, then send
FF CA 00 00 00again in the Script Tool or Web APDU Tool. You should get the same UID and90 00without reconnecting. - Replug test. With QuickView open, unplug the reader, wait 5 seconds and plug it back in. The reader should return to the list and the next tap should be detected. Repeat on the USB port, hub or extension cable the reader will use in production.
Pass: 20 of 20 taps detected for each card type, the hold test returns the UID, and the reader recovers after replugging. One or two misses usually point to card position; repeated misses or the reader dropping out point to the USB port, cable or hub. See the troubleshooting table.
Step 6: Read an NDEF Message from an NFC Tag
NDEF (NFC Data Exchange Format) is the NFC Forum format phones use for links, text and contact cards on tags. Reading it proves the reader can read tag memory, not only the UID. Use an NTAG or MIFARE Ultralight tag that already holds a known message, such as a web link.
- Cross-check with a phone. Tap the tag on an NFC phone. It should offer to open the link. Now you know the tag holds a valid NDEF message.
- Read the tag memory in the Script Tool or Web APDU Tool. Send the ACS Read Binary command
FF B0 00 04 10, which asks for 16 bytes starting at page 4 of an NTAG or Ultralight tag. The reply should end in90 00. On a tag formatted the usual way, the data starts with03(the marker for an NDEF message) followed by the message length, and the readable text of your link appears a few bytes later. Read the next pages (FF B0 00 08 10, and so on) for longer messages. - Or use a BSD utility. The BSD ACR1252U and ACR1552U utilities can write a link or text to NTAG and Ultralight tags and read it back (reading and writing card data needs a BSD licence key; card identity is free).
Pass: the bytes you read match the message the phone showed, and a tag written by the reader opens correctly on the phone.
Not yet tested by BSD. The Read Binary bytes shown here follow the ACS API manuals and the NFC Forum tag format. We have not yet recorded them on each of these readers with our own tags, and the exact bytes depend on how the tag was formatted. We will add screenshots after our hardware session.
ACR1252U, ACR1552U and ACR122U: What Changes in the Test
The six steps are the same for all three readers. What changes is which cards you can test and how far away they should be read. The figures below are what ACS publishes; your own measurements from step 4 belong in your test record.
| ACS documents | ACR1252U | ACR1552U | ACR122U |
|---|---|---|---|
| Card types | ISO 14443 Type A and B, MIFARE (including 7-byte UID, MIFARE Plus and DESFire), FeliCa, all 4 NFC Forum tag types (ISO 18092) | ISO 14443 Type A and B, ISO 15693, ISO 18092 NFC, MIFARE, FeliCa, NFC tags, SRI/SRIX, CTS, Innovatron, Picopass, Topaz | ISO 14443 Type A and B, MIFARE, FeliCa, all 4 types of NFC tags (ISO 18092) |
| Read distance | Up to 50 mm, depending on tag type | Up to 70 mm, depending on tag type | Up to 50 mm (5 cm), depending on tag type |
| Contactless speed | Up to 424 kbps | Up to 848 kbps | Up to 424 kbps |
| NFC modes | Reader/writer, card emulation, peer-to-peer | Reader/writer, card emulation, keyboard emulation | NFC (ISO/IEC 18092) reader |
| SAM slot | Yes, one | Yes, one | Not built in (ACS mentions an optional SAM integration) |
| What it means for testing | Test with your MIFARE, NTAG and DESFire cards; ignore the SAM entry in step 1 | The only one of the three for ISO 15693 tags. If it types numbers into a text editor but QuickView sees no card, it is in keyboard emulation mode (how to check) | End of life: ACS no longer recommends it for new projects and warns about counterfeit units. Use these tests to check units already in service; for new work see the ACR122U vs ACR1552U comparison |
Source: the ACS product pages for the ACR1252U, ACR1552U and ACR122U, checked on 16 Nov 2026. Model pages on our site: ACR1252U, ACR1552U, ACR122U.
Which Tool for Which Step
The official ACS tools are free from acs.com.hk after a short ACS registration form. The BSD utilities are BSD Infotech software, not ACS products, free after a one-time email check (OTP), and work with cards on factory keys only. Card identity is free in every BSD utility; reading and writing card data needs a BSD licence key. How each tool works is explained on the testing centre's tool chooser.
| Tool | Steps it covers | Where to get it |
|---|---|---|
| ACS QuickView | 1, 2, 4, 5 | ACS utility tools |
| ACS Script Tool | 3, 5, 6 | ACS utility tools |
| ACS Web APDU Tool (Chrome or Edge, Windows 10 or later) | 3, 5, 6 | ACS Web APDU Tool page |
| ACS Smart Card and Reader Tool | 3 (MIFARE Classic and Ultralight) | ACS utility tools |
| BSD ACR1252U NFC Card Utility | 3, 6 (MIFARE Classic, NTAG/Ultralight, DESFire on factory keys) | Get the ACR1252U utility |
| BSD ACR1552U NFC Card Utility | 3, 6 (as the ACR1252U utility, plus ISO 15693) | Get the ACR1552U utility |
| BSD ACR122U NFC Utility | 3 (MIFARE Classic 1K UID and a member record) | Get the ACR122U utility |
Printable NFC Reader Test Checklist
Date: ____________ Tested by: ____________ PC and Windows version: ____________ Reader model and serial: ____________ Driver version: ____________
| # | Test | Pass when | Result (Pass / Fail) | Notes |
|---|---|---|---|---|
| 1.1 | Reader in Device Manager | Listed under Smart card readers, no warning; returns after replug | ||
| 1.2 | Smart Card service | Running | ||
| 1.3 | QuickView reader list | Contactless reader listed (name recorded) | ||
| 2.1 | Card arrival, each card type | Card shown present with ATR | ||
| 2.2 | Card removal, each card type | Card shown absent | ||
| 3.1 | UID, each card type (FF CA 00 00 00) | UID + 90 00 (UID recorded) | ||
| 3.2 | Data read where keys are known | Expected data returned | ||
| 4.1 | Sweet spot | Reliable detection flat on the reader | ||
| 4.2 | Maximum distance, each card type | Distance in mm recorded | ||
| 4.3 | Installation position (metal, cover) | Still reliable in place | ||
| 5.1 | 20 taps, each card type | 20 of 20 detected | ||
| 5.2 | 10-minute hold | Same UID + 90 00 | ||
| 5.3 | Unplug and replug | Reader returns; next tap detected | ||
| 6.1 | NDEF tag on a phone | Phone opens the link | ||
| 6.2 | NDEF read on the reader | Bytes match the message (starts with 03) |
How to Record Your Test Results
A test that is not written down cannot be compared later. Keep one record per reader so that, when something stops working, you can test again and see what changed.
- Identify the setup. Windows edition and version (run
winver), the PC or port used, the reader model and the serial number from the label, and the driver version from Device Manager. - Identify each card by its label, card type, ATR (step 2) and UID (step 3). Do not record keys or personal data held on cards.
- Save evidence. Take a screenshot (Windows + Shift + S) of QuickView with the card present and of each Script Tool response. Name the files so they sort together, for example
2026-11-30_ACR1552U_cardB_uid.png. - Note the conditions for read-range results: card type, holder or wallet, surface and any cover between the card and reader.
- Mark each line Pass or Fail and write what you saw on a failure: the error text or status bytes, and which step it was.
- Re-test after every change of driver, Windows update, USB port or cable, and keep the old sheet.
If you need help, send this sheet and the screenshots with your enquiry. It usually saves several rounds of questions.
When a Test Step Fails
| Failed at | Likely cause | What to do |
|---|---|---|
| Step 1: reader missing in Device Manager or QuickView | Driver, USB port or the Smart Card service | Follow reader not detected, then PC/SC status troubleshooting |
| Step 2: reader listed, no card ever detected | Card type not supported, card held badly, or ACR1552U in keyboard emulation mode | Check the card against the model table; hold it flat in the centre; try a second card; check the ACR1552U mode |
| Step 2: card detected, removal not shown | Another program connected to the card | Close other card software, then reopen QuickView |
| Step 3: UID reads, data read fails | Wrong key or access rights on the card | Use the card's real keys in your own application; factory-key tools cannot read re-keyed cards |
| Step 4: very short range | Small tag antenna, metal nearby, or several cards stacked | Test one card on a non-metal surface; compare with a full-size card |
| Step 5: missed taps or the reader drops out | USB hub, extension cable, front-panel port or power saving | Plug straight into a rear port; repeat step 5; see the driver error table |
| Step 6: phone reads the tag, the reader returns an error | Wrong page number or length, or the tag is not NTAG/Ultralight | Re-read from page 4 with FF B0 00 04 10; check the card type in QuickView |
Sources
Card types, read distances, speeds, NFC modes and tool descriptions were checked on the official ACS pages on 16 Nov 2026. ACS updates its pages, so check them before you buy or download.
- ACS ACR1252U USB NFC Reader III, ACS ACR1552U USB NFC Reader IV and ACS ACR122U USB NFC Reader product pages
- ACS Utility Tools (QuickView v2.18, Script Tool 5.2, Smart Card and Reader Tool v4.0.1.8, Reader Monitor Program)
- ACS Web APDU Tool
BSD Infotech is an independent ACS supplier and integrator, not the manufacturer. ACS, the ACS logo and ACS product names belong to Advanced Card Systems Ltd. MIFARE, NTAG, DESFire and FeliCa are trademarks of their owners.
