ACS QuickView: Installation and Usage Guide

What is ACS QuickView and how do you use it? QuickView is a free Windows, macOS and Linux utility from ACS (Advanced Card Systems) that lists the PC/SC smart card readers on your computer, shows details of each reader and of the card in it, and keeps polling, so you can see a card arrive and leave. Download it from the official ACS utility tools page, install the reader driver first, then open QuickView, select your reader and insert or tap a card. If the card and its ATR appear, and disappear when you remove it, the reader, driver and Windows smart card layer are working.

This guide covers where to get the current version, installation on Windows 10 and 11, what each part of QuickView tells you, how to read the ATR it shows, and what to do when no reader or no card appears. It also explains when another tool is the better choice. QuickView is ACS software; BSD Infotech is an independent ACS supplier and integrator and does not host or redistribute it.

Not yet tested by BSD. The QuickView steps and screen descriptions on this page are based on ACS's own descriptions and SDK manuals. BSD has not yet recorded QuickView v2.18 on its own readers; this page will be updated with screenshots after that test.

ACS describes QuickView as a tool that reads and displays smart card reader and smart card details, and that also works as a polling tool for card presence and absence. Its SDK manuals give it one main job: checking that a reader has been installed properly. In practice that makes it the first thing to open after you plug in a new ACS reader.

QuickView is good forUse something else for
Seeing which PC/SC readers Windows offers to programs, by their exact namesSending your own APDU commands and reading the response (ACS Script Tool or Web APDU Tool)
Watching a card being inserted, tapped and removedReading or writing data blocks on a MIFARE, NTAG or DESFire card
Showing the ATR, which tells you what kind of card the reader foundChanging reader settings, firmware or keyboard emulation mode
Proving a reader works before you blame your code, or before a support caseTesting a reader that is in keyboard emulation mode (that output is typed text, not PC/SC)

ACS lists QuickView for its PC/SC readers in general (contact, contactless and dual-interface) and for all cards those readers support. So the same guide applies to the ACR1252U, ACR1552U, ACR122U and ACR39U. Because it talks to readers through PC/SC, QuickView needs the same things any card program needs: a working driver and a running Windows Smart Card service.

Get QuickView from ACS, so you always have the current, unmodified version. On the ACS utility tools page it is listed three times, once per operating system. When we checked on 16 Nov 2026, the download links on that page led to an ACS registration form (name, company, country and email) before the file is offered. ACS states that its utility tools are free of charge.

Where ACS lists QuickViewVersion shownPlatform
ACS utility tools page (current download)v2.18Separate downloads for Windows, macOS and Linux
ACR1552U SDK product page, list of kit contents2.13Part of the SDK kit
ACR1552U SDK user manual (version 1.01)2.15Windows (in the SDK installer), macOS and Linux

The different numbers are normal: an SDK kit carries the build that was current when the kit was put together, and the tools page is updated separately. If you already have QuickView from an SDK kit, it will do the basic checks on this page, but download v2.18 (or whatever the tools page lists when you read this) for new installations. Older ACS SDK kits, such as the ACR122U SDK, also include QuickView.

BSD Infotech does not offer a QuickView download and does not host ACS files. If someone sends you QuickView from another website or by email, get it again from acs.com.hk instead.

  1. Install the reader driver first. QuickView does not install a driver. Follow the ACS driver installation guide for Windows 10 and 11, or the driver guide for your model: ACR1252U, ACR1552U or ACR122U.
  2. Plug the reader in and check Device Manager. It should appear under Smart card readers with no warning icon. If it does not, see how to check whether Windows detects the reader before going further.
  3. Download QuickView for Windows from the ACS utility tools page. Choose the entry marked For Windows; the macOS and Linux files will not run on Windows.
  4. Unpack and run the installer. If the download is a ZIP file, extract it to a folder first, then run the setup program inside it. Accept the Windows prompt for administrator rights if one appears. If Windows SmartScreen or your antivirus warns about the file, check that it came from acs.com.hk before you continue.
  5. Open QuickView from the Start menu. Close any other card software first, including the BSD utilities and your own programs, so nothing else is holding the reader.

Expected result: QuickView opens and, after it has examined the system, your reader appears in its reader list. Keep the reader plugged in while QuickView starts; if you plug it in later, restart or re-initialise QuickView so the list is refreshed.

macOS and Linux

The ACR1552U SDK manual describes the other two versions briefly: on macOS QuickView comes as a disk image (.dmg); on Linux it is an AppImage, which needs pcscd (the PC/SC service on Linux) and the FUSE library installed first. BSD has not tested either; this guide concentrates on Windows 10 and 11.

The QuickView window pictured in ACS's ACR122U SDK has a reader list on the left, a details panel on the right, and buttons to initialise the check, reset it, view or save a log, and an Advanced option. ACS's manuals point to QuickView's own Help menu for full instructions. The current v2.18 window may look different; we will describe it from our own test.

1. The reader list

Each entry is a reader name exactly as the Windows Smart Card service reports it to programs. This is the same name your own software will see when it lists readers, so it is worth copying down. Readers with a contactless antenna and a SAM slot, such as the ACR1252U and ACR1552U, usually show two entries: one for the contactless (PICC) interface where you tap cards, and one for the SAM slot. Pick the contactless entry to test a tapped card. What the reader names mean explains this in more detail.

An empty list means no program can see a reader, whatever Device Manager shows. Go to Problems.

2. Card insert and remove events

Because QuickView polls the reader, its display changes when a card arrives or leaves. Insert a contact card chip first and face up, or place a contactless card flat in the middle of the reader and keep it still. The reader should change from empty to card present. Take the card away and it should go back to empty. Repeat five to ten times: a reader that only notices the card sometimes usually points to card position, distance or a damaged card, not to the driver.

3. Reader and card details

With a card present, QuickView shows the details it can read, most usefully the card's ATR (Answer To Reset). The ATR is a short string of bytes in hexadecimal, such as 3B 8F 80 01 .... The next section explains how to read it.

4. The log

The view and save log buttons let you keep a record of what QuickView found. A saved log, together with a screenshot, is a useful thing to attach to a support request, because it shows the reader name and the card's response without anyone having to guess.

The ATR is the first thing a card says when the reader powers it up. For a contact card, such as a card in an ACR39U, the chip itself sends the ATR, and it describes how the card wants to communicate. A contactless card does not send an ATR of its own. Instead the reader builds one from what it learned about the card, in a standard format from the PC/SC specification, so that card software can treat contactless cards the same way as contact cards. The ACS API manuals describe this format for their contactless readers.

Seeing any ATR already tells you something important: the reader has exchanged data with the card. Reading the bytes then tells you what kind of card it is.

Example: a MIFARE Classic 1K card on a contactless ACS reader

The ACS ACR122U API manual gives this ATR for a MIFARE Classic 1K card: 3B 8F 80 01 80 4F 0C A0 00 00 03 06 03 00 01 00 00 00 00 6A. Split into parts, it reads like this:

BytesWhat they mean
3BStart of the ATR (direct convention)
8F 80 01Format bytes. The F in 8F says 15 descriptive ("historical") bytes follow.
80 4F 0CMarker: what follows identifies the card type
A0 00 00 03 06The PC/SC Workgroup's registered ID: this ATR was built in the PC/SC standard format
03Standard: ISO 14443 Type A, part 3
00 01Card name: MIFARE Classic 1K. This is the part to look at.
00 00 00 00Reserved
6AChecksum of the bytes before it

Other card name codes in the same position, as listed in the ACR122U API manual: 00 02 MIFARE Classic 4K, 00 03 MIFARE Ultralight, 00 26 MIFARE Mini, F0 04 Topaz and Jewel, F0 11 and F0 12 FeliCa. The reference manual for your own reader model, on its ACS download page, has the full list for that reader.

Cards with a processor, such as DESFire

Cards that speak the ISO 14443-4 protocol, such as MIFARE DESFire, get a shorter ATR. It starts with 3B 8n 80 01, where n is the number of descriptive bytes, and those bytes are copied from the card's own answer (its ATS). The ACR122U API manual's DESFire example is 3B 86 80 01 06 75 77 81 02 80 00. You will not see a card name code like 00 01 here; the descriptive bytes come from the card maker.

What the ATR does not tell you

  • It is not the card's UID. Every MIFARE Classic 1K card on the same reader gives the same ATR. To get the unique ID, use a Get UID command (see other tools) or the BSD utilities.
  • It does not prove the card can be read or written. Data access needs the right keys and commands. The ATR only shows that the card answered.
  • It can differ between reader models and firmware. Compare ATRs from the same reader model when you build a list of accepted cards in your software.

Most "my code cannot find the reader" problems are not code problems. Ten minutes with QuickView separates the two. Work through this list with the reader and the card type your application will use:

  1. Reader listed. Note the exact reader name, including the interface (PICC or SAM). Your code should select the reader by a part of this name rather than by its position in the list, because the order can change when another reader is plugged in.
  2. Card arrives and leaves cleanly. Ten taps, ten arrivals and ten removals. If QuickView misses some, fix the card position or try another card before writing any code.
  3. ATR matches the card you expect. For example, card name 00 01 for a MIFARE Classic 1K. If you see a different card type, your test card is not what you think it is.
  4. Close QuickView. Then run your program. Two programs can both list a reader, but only one can hold a card when it asks for exclusive access, so leaving QuickView open can make your own program fail with a sharing error.
  5. Compare. Your program should report the same reader names, the same card arrival and the same ATR. If QuickView works and your program does not, the problem is in the code; the PC/SC reader status guide lists the error codes, and the SDK guides for the ACR1252U, ACR1552U and ACR122U show working C# examples.
What you seeLikely causeWhat to do
No reader listedDriver not installed, reader not detected, or the Smart Card service is stoppedCheck Device Manager (detection guide), then the Smart Card service (service settings). Restart QuickView with the reader plugged in.
No reader listed, but only over Remote DesktopThe program sees the readers of the computer you connect from, not the remote oneSee Remote Desktop and smart card readers.
Reader listed, but QuickView reports it as busy or cannot read the cardAnother program holds the card: a second test tool, a BSD utility, your own program, or a background card monitorClose all other card software and try again. If it persists, unplug and replug the reader. The reader states guide explains in-use and exclusive states.
Reader listed, but the card is never shownWrong interface selected (SAM instead of PICC), card type not supported, or the card is too far awaySelect the contactless (PICC) entry. Place the card flat in the centre and hold it still. Try a second card of a type the reader supports.
An ACR1552U types numbers into Notepad when you tap a card, and QuickView shows nothingThe reader is in keyboard emulation modeSwitch the reader back to its normal mode with the ACS configuration tool; see the testing centre.
Contact card not shown in an ACR39UCard inserted upside down or the wrong way roundInsert the card chip first, with the gold contacts facing up.
Card shown sometimes, then lostCard at the edge of the antenna field, a weak or damaged card, or a metal surface under the readerHold the card still in the middle, move the reader away from metal, and test another card.
QuickView works, your program does notReader name, share mode or connection code in your programClose QuickView first, then follow the checklist above and the PC/SC error code table.

QuickView answers one question well: does the reader see the card? For the next questions, use a different tool. The test tool chooser in our testing centre compares them all.

ACS Script Tool

Send APDU commands, one at a time or as a saved script, and see the exact response bytes. Use it for a read-only Get UID (FF CA 00 00 00) or to test a command before you put it in code.

ACS, free · ACS utility tools page

ACS Web APDU Tool

The same kind of command test from Chrome or Edge, with ACS's browser extension and a small helper program on the PC.

ACS, free · ACS Web APDU Tool page

ACS Smart Card and Reader Tool

Ready-made widgets for MIFARE Classic, MIFARE Ultralight and ACS ACOS cards, when you want to try card functions without typing commands.

ACS, free · ACS utility tools page

BSD reader utilities

Read the UID and read or write MIFARE, NTAG or DESFire cards that are still on their factory keys, without code. BSD Infotech's own software, not an ACS product; free after a one-time email check (OTP).

BSD Infotech · Compare the BSD utilities

Version numbers, platforms and the tool description were checked on the official ACS pages on 16 Nov 2026. Installation notes and the ATR format come from the ACS SDK user manuals and the ACR122U API manual, summarised in our own words. Version numbers change, so check the ACS page before you download.

  • ACS Utility Tools (QuickView v2.18 for Windows, macOS and Linux; Script Tool; Smart Card and Reader Tool)
  • ACS ACR1552U SDK (kit contents, QuickView 2.13)
  • ACS Web APDU Tool
  • ACS ACR1552U Series SDK User Manual v1.01 and ACR122U NFC Reader SDK User Manual v2.0 (QuickView), ACR122U NFC Reader API v1.4 (ATR format): supplied with the ACS SDK kits

BSD Infotech is an independent ACS supplier and integrator, not the manufacturer. ACS, the ACS logo, QuickView and ACS product names belong to Advanced Card Systems Ltd. MIFARE and DESFire are trademarks of NXP B.V. Windows is a trademark of Microsoft Corporation.

QuickView sees the card. What next?

Tell us the reader model, card type and what your software must do with the card. BSD Infotech supplies ACS readers and cards and builds the application around them.