ACR1552U Driver, Software and Reader Test Guide

How do you install and test the ACR1552U? Download the Windows PC/SC Driver Installer from the official ACS ACR1552U download page, install it with the reader unplugged, then plug the reader in. Check that it appears under Smart card readers in Device Manager and that the Windows Smart Card service is running. Finally, tap a card in ACS QuickView or the free BSD ACR1552U utility: if the tool shows the card arriving and leaving, the reader, driver and Windows are all working.

This guide covers Windows 10 and Windows 11, step by step, and then shows what each test tool checks, including ISO 15693 tags, which the ACR1552U reads and many older NFC readers do not. BSD Infotech is an independent ACS supplier and integrator, not the manufacturer: every driver and ACS tool link on this page opens acs.com.hk, and our own utility is clearly marked as BSD software. For specifications, variants and the price, see the ACS ACR1552U USB NFC Reader IV page.

  • A Windows 10 or Windows 11 PC on which you can install software as an administrator. For the first test, plug the reader straight into a USB port on the computer, not into a hub, dock or monitor.
  • The right connector. ACS makes the ACR1552U with a USB Type-A plug (ACR1552U-M1) and a USB Type-C plug (ACR1552U-MF). The cable is fixed to the reader, so use a port that matches rather than an adapter if you can.
  • One or two test cards you own. A blank MIFARE Classic 1K card, an NTAG sticker and a DESFire card cover most tests. If your project uses ISO 15693 tags (for example library or industrial tags), have one ready for the ISO 15693 section. Use spare cards for any write test, never a card that is already in use.
  • Close other card software such as attendance or access-control programs. A program that is already connected to the reader can stop the test tools from reaching the card.

Linux, macOS and Android drivers are on the same ACS page. This guide covers Windows only. For the general method on any ACS reader, see installing ACS reader drivers on Windows 10 and 11.

  1. Open the ACS download page. Go to the ACR1552U drivers and utilities page at acs.com.hk. It lists the files under Drivers & Utilities for ACR1552U, with the version, release date and supported operating system next to each one.
  2. Choose the Windows PC/SC Driver Installer. There are three files called "PC/SC Driver Installer": pick the one whose OS column says Windows. The Linux and macOS installers will not work on a Windows PC.
  3. Leave the Configuration Tool for later. ACS marks it as for UID keyboard emulation mode only. You do not need it to use the reader with PC/SC software. It is covered in step 5.
  4. Save the file and note its version. When we checked on 16 Nov 2026, ACS listed Windows installer version 1.0.6.2 (12 Dec 2025), which contains driver version 1.0.6.0. ACS updates its files, so install whatever version the ACS page shows on the day, and write it down: you will compare it in step 3.

Download drivers only from ACS. Driver files copied to other websites can be old or altered. BSD Infotech does not host ACS drivers. We link to the ACS page so you always get the current, signed release.

The steps are the same on Windows 10 and Windows 11.

  1. Unplug the reader if it is connected. Installing first and plugging in afterwards lets Windows pick up the new driver when it first sees the reader.
  2. Extract the download if it came as a ZIP archive: right-click it, choose Extract All, and open the extracted folder. Running an installer from inside a ZIP can fail without a clear error.
  3. Run the installer. Double-click it and click Yes when Windows asks for administrator permission (the User Account Control prompt). Follow the steps to the end.
  4. Restart if asked. If the installer asks for a restart, restart before you go on.
  5. Plug in the reader. Wait 10 to 20 seconds. The reader's LED should light up, and Windows may briefly show that it is setting up a device.

Note: the ACR1552U is a USB CCID reader, and ACS lists Microsoft WHQL among its certifications. Windows may therefore show the reader even before the ACS package is installed, sometimes under a generic name. Install the ACS driver anyway, so you are running the driver ACS publishes for this reader, and so that step 3 shows a version you can check against the ACS page.

  1. Open Device Manager. Right-click the Start button and choose Device Manager (the same on Windows 10 and 11).
  2. Expand "Smart card readers". The ACR1552U should be listed there. With the ACS driver installed, the name normally includes ACS and ACR1552U.
  3. Check the driver version. Double-click the reader, open the Driver tab and look at Driver Provider and Driver Version. They should match the ACS driver you installed (for the installer we checked, driver 1.0.6.0). A generic Microsoft provider means Windows is still using its own driver: reinstall the ACS package and replug the reader.
  4. Check the device status. On the General tab, the status should say the device is working properly.
  5. Unplug and replug once. The entry should disappear and come back. If it keeps dropping out, try another USB port: the problem is the connection, not the driver.

If the reader is not under Smart card readers, look under Other devices or Universal Serial Bus devices for an entry with a yellow warning mark, and see the troubleshooting table. If the reader appears under Keyboards or Human Interface Devices and not as a smart card reader, it may be in keyboard emulation mode (see the keyboard tool).

Every PC/SC program, including the ACS tools and the BSD utility, reaches the ACR1552U through the Windows Smart Card service. If the service is not running, they all say "no reader found", even when Device Manager shows the reader.

  1. Open Services. Press Windows + R, type services.msc and press Enter.
  2. Find "Smart Card". With the reader plugged in, its status should be Running. Windows normally starts it by itself when a reader is connected, so it can show as stopped while no reader is plugged in.
  3. Start it if needed. If it is stopped with the reader connected, right-click it and choose Start. If the startup type is Disabled, a company policy may have turned it off: ask your IT team.

Prefer the command line? Open Command Prompt and type sc query SCardSvr. The STATE line should say RUNNING.

ACS offers free Windows tools on its utility tools page; ACS asks for a short registration (name, company, country, email) before the download. Start with QuickView, then use the others for the questions QuickView cannot answer. The ACS testing and utilities centre compares all of them.

QuickView: does the reader see the card?

  1. Install QuickView for Windows from the ACS utility tools page and open it.
  2. Select the ACR1552U in the reader list. If there are two entries for the reader, start with the one for the contactless interface. The other one is usually the SAM slot.
  3. Tap a MIFARE Classic 1K card flat in the middle of the reader and keep it still. QuickView should show that a card is present, with its details such as the ATR.
  4. Lift the card away: QuickView should show it has gone. Repeat with an NTAG and a DESFire card.

If every card arrives and leaves cleanly, the reader passes the basic test.

Script Tool: does a command get the right answer?

The ACS Script Tool sends APDU commands to the card through the reader and shows the exact response. A good first command is Get Data (UID), defined in the PC/SC specification for contactless readers:

Command (hex): FF CA 00 00 00
Expected response: the card UID (4, 7 or 10 bytes for ISO 14443 Type A cards, 8 bytes for ISO 15693 tags), followed by the status word 90 00, which means success.

Not yet tested on hardware. We have not yet run this command on an ACR1552U with the Script Tool. A different status word, such as 6A 81 (function not supported) or 63 00 (operation failed), usually means no card is on the reader or the card moved while the command ran. The ACR1552U Reference Manual on the ACS download page lists all the reader's commands and status words.

Smart Card and Reader Tool: MIFARE Classic and Ultralight without commands

This ACS tool tests card features through ready-made widgets. ACS lists MIFARE Classic, MIFARE Ultralight and Ultralight C (plus ACS's own ACOS cards) as the supported card types. With a blank MIFARE Classic 1K card you can load the factory key FF FF FF FF FF FF, authenticate a sector and read a data block. DESFire and ISO 15693 tags are not in its list, so test those with QuickView, the Script Tool or the BSD utility instead.

Keyboard Configuration Tool: keyboard emulation mode

The ACR1552U can also act like a USB keyboard: tap a card and the reader types the card UID into whatever program has focus, such as Notepad, a spreadsheet or a web form. ACS sets this mode with its Configuration Tool, which is on the ACR1552U download page and also listed as the ACR15XX Keyboard Configuration Tool on the ACS utility tools page.

  1. Download the Configuration Tool from the ACS ACR1552U download page and run it with the reader plugged in.
  2. Switch the reader to HID keyboard emulation and save the setting.
  3. Open Notepad, click inside it, and tap an ISO 14443 Type A or Type B card. The UID should appear as typed text.
  4. When you have finished, set the reader back to its normal mode with the same tool before you test with PC/SC software again.

ACS describes this output as HID keyboard input, not CCID, and lists ISO 14443 Type A and B cards for this mode. So while keyboard mode is on, test in a text editor, not in QuickView, and do not expect an ISO 15693 tag to type a UID.

The ACS tools prove the reader works. To read and write real card data without writing software, BSD Infotech offers its own ACR1552U NFC Card Utility for Windows 10 and 11. It is BSD software, not an ACS product, and ACS does not support it.

How to get it and what this edition covers

  • Free, after a one-time email check. Open the download box, enter your name, email, mobile and city, type the one-time password (OTP) we email you, and the download starts.
  • Default Key edition: factory keys only. It works with MIFARE Classic cards that still use the factory key FF FF FF FF FF FF. It reads and writes DESFire cards only while their keys are still the factory (all-zero) keys.
  • Detection is free; reading and writing need a licence key from BSD Infotech, as explained on the download page.
  • Cards with your own keys need the Custom Key edition: ask for the Custom Key edition.

A test plan with the BSD utility

Steps 1 and 2 are free. Steps 3 to 6 read or write card data, so they need the licence key.

  1. Reader check. Open the utility with the reader plugged in. It should find the ACR1552U.
  2. Card detection. Tap each test card in turn. The utility detects the card type and opens the matching tab.
  3. MIFARE Classic 1K (factory key). Read the sectors, write a short value to a spare data block, read it back and compare.
  4. NTAG / Ultralight. Write a short text or web link, then read it back, or tap the tag with a phone to check that the link opens.
  5. DESFire (factory keys). Read the card, then write and read back a test file. Use a spare card: if its keys have already been changed, this edition cannot read it, and that is expected.
  6. ISO 15693 tag, if you have one: see the next section.

The utility has safety locks that stop a card being locked by mistake. Even so, write only to cards you own and can afford to reuse for testing.

ISO 15693 support is one of the main reasons to choose the ACR1552U over the end-of-life ACR122U. ISO 15693 "vicinity" tags also work at 13.56 MHz, but they use a different radio protocol from ISO 14443 cards such as MIFARE and DESFire. They are common as library book tags, industrial and asset labels, and some ticket and access tags. Their memory is a row of numbered blocks, and there are no MIFARE-style sector keys. Instead, blocks can be locked, and on most tags a lock is permanent.

Not yet tested by BSD. We do not yet have an ISO 15693 tag on our test bench, so these steps are based on the ISO 15693 standard and on ACS's and our own tool descriptions. They have not been run on an ACR1552U yet. We will update this section after testing.

  1. Detect the tag in QuickView. Place the tag in the centre of the reader. ISO 15693 tags are often thin labels with large antennas, so hold them flat and still. QuickView should show a card present.
  2. Read the UID in the Script Tool with FF CA 00 00 00 (see above). An ISO 15693 UID is 8 bytes, and its most significant byte is E0. Depending on the reader and software, that byte can come first or last, so check the byte order before you compare the UID with the number printed on a tag or reported by another reader.
  3. Read the blocks in the BSD utility. Its ISO 15693 / ICODE tab reads all the blocks of supported tags. The download page lists ICODE SLI, SLIX and SLIX2, ST LRI and Tag-it tags.
  4. Write a test only to a spare tag. Write a short text to an unused block and read it back. Never use a lock command on a test tag: a locked ISO 15693 block usually cannot be unlocked.

Need ISO 15693 commands for your own software? The ACR1552U Reference Manual on the ACS download page documents them. The ACR1552U SDK and integration guide covers the programming side.

Work from the top: a problem higher in the table hides the ones below it.

What you seeLikely causeWhat to do
The installer will not run, or stops with an errorRunning from inside the ZIP, or no administrator rightsExtract the ZIP first, then run the installer and accept the administrator prompt. On a managed PC, ask IT to install it.
No LED and nothing in Device Manager when the reader is plugged inUSB port, hub or adapter problemPlug straight into another USB port on the PC. On a Type-C model, avoid adapters for the first test.
Reader appears under Other devices with a yellow warning markDriver missing or failed to installRun the ACS Windows PC/SC Driver Installer again, then unplug and replug the reader.
Reader is listed, but with a generic name or a Microsoft driver versionWindows is using its own driverInstall the ACS driver and replug. Check the Driver tab against the version on the ACS page.
Device Manager shows the reader, but every tool says "no reader found"Smart Card service stopped or disabledStart the Smart Card service (step 4), then reopen the tool.
Tapping a card types numbers into Notepad, and QuickView sees nothingKeyboard emulation mode is onSet the reader back to its normal mode with the ACS Configuration Tool (step 5).
The reader is found, but a card is not detectedCard not held flat and still, a card type the reader does not support, or a damaged cardHold the card flat in the centre. Try a second card. Check the card type against the ACR1552U specifications.
The card is detected, but reading MIFARE Classic data failsThe card does not use the factory key, or the wrong key type was usedUse the card's real keys. The BSD Default Key edition reads only factory-key cards: ask for the Custom Key edition.
A DESFire card is detected, but the BSD utility cannot read or write filesThe card's keys are no longer the factory keys, or there is no licence keyTest with a new DESFire card. Check the licence status in the utility.
An ISO 15693 tag is not detected, or reads only sometimesTag antenna not aligned, or a metal surface behind the tagHold the tag flat and centred, away from metal. Try a different tag.
A tool worked a minute ago, but now cannot connect to the cardAnother program has taken the cardClose other card software, including other test tools, and try again.

Still stuck? Send us your Windows version, what Device Manager shows and which card you used.

File names, versions, supported cards, tool descriptions and certifications were checked on these official ACS pages on 16 Nov 2026. ACS updates its files, so check the ACS page before you download.

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. Other card names belong to their owners.

Need help with an ACR1552U project?

Tell us your Windows version, card type and what the software should do. BSD Infotech can supply ACR1552U readers and cards, test them with your cards and build the application around them.