ACS Smart Card and Reader Tool Guide
← Back to the ACS testing and utilities centre
What is the ACS Smart Card and Reader Tool? It is a free Windows program from ACS (Advanced Card Systems) that lets you try card and reader functions through ready-made panels called widgets, instead of typing raw commands. Card widgets cover MIFARE Classic, MIFARE Ultralight, MIFARE Ultralight C and ACS's own ACOS3, ACOS6 and ACOS6-SAM cards; reader widgets give access to a specific reader's own commands and settings, such as the buzzer, LEDs and card polling. It is a standalone download (v4.0.1.8 on 17 Nov 2026) from the ACS utility tools page, where ACS asks for a short registration first, and it is also included in several ACS SDK kits, including the ACR1252U and ACR1552U kits.
This guide explains where to get it, which widgets it has, how to read a MIFARE Classic 1K card on its factory key and an NTAG tag with an NDEF message, which reader settings it can change (and why you should leave most of them alone), and when QuickView, the Script Tool or a BSD utility is the better choice. The Smart Card and Reader Tool 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 descriptions and steps on this page come from ACS's product pages, the ACS SDK manuals and the help topics listed in ACS's installer. BSD has not yet run the tool on its own readers, so button names and screen layout may differ from what is written here. We will add screenshots after our hardware test.
What the tool is, and what it is not
Most ACS test tools are either very simple or very raw. QuickView only tells you that a reader and a card are present. The Script Tool sends whatever command bytes you give it. The Smart Card and Reader Tool sits in between: you pick a widget for your card or reader, connect, and use its buttons and fields. The widget builds the commands for you and shows the reply, and the tool keeps a log of what was sent.
ACS describes it in two ways. On its utility tools page it is a tool that uses widgets to explore what particular cards and readers can do. In the ACR1552U SDK manual it is a tool for running both reader commands and card commands, and each card widget is said to give access to most of that card's commands. The card widgets work through PC/SC, so they need a PC/SC reader (all current ACS USB readers are), and ACS notes that a card widget can hold connections to several readers at once.
Good for
- Seeing what a card can do before you write code: authenticate, read a block, read a page.
- Checking a reader's own functions: firmware and reader information, buzzer and LED behaviour, polling.
- Trying the NFC features ACS demonstrates on the ACR1252U and ACR1552U kits (NFC and NDEF tools, card emulation).
- Learning which command a function uses, from the tool's log, before you build it into your own program.
Not for
- Production use, issuing cards in bulk or anything you need to repeat exactly: write a program or a Script Tool script.
- Cards whose keys you do not have. The tool needs the right key like any other program; on this site we cover factory keys only.
- macOS or Linux: ACS lists it for Windows only.
- Contact memory cards such as SLE4442 or SLE4428: they are not in ACS's list of supported cards for this tool.
Where to get it: standalone download or SDK
We checked both routes on 17 Nov 2026. The tool is not SDK-only: you can download it on its own.
| Route | What we found | Notes |
|---|---|---|
| ACS utility tools page (standalone) | Listed as "ACS Smart Card and Reader Tool v4.0.1.8", Windows, for ACS PC/SC readers (contact, contactless and dual-interface). Supported cards: MIFARE Classic, MIFARE Ultralight, MIFARE Ultralight C, ACOS3, ACOS6, ACOS6-SAM. | The download link leads to ACS's registration page, which asks for your name, company, country and email. The tool itself is free. Open the ACS utility tools page. |
| ACR1552U SDK | ACS lists "Smart Card and Reader Tool" in the kit contents and says it includes NFC and NDEF tools for the ACR1552U's card emulation and keyboard emulation. The installer in our copy of SDK v1.01 is version 4.0.2. | The SDK is a paid kit from ACS; see our ACR1552U SDK guide. |
| ACR1252U SDK | ACS lists "Smart Card and Reader Tool" in the kit contents and says it includes NFC and NDEF tools for the ACR1252U's peer-to-peer and card emulation modes. | See our ACR1252U SDK guide. |
| Other ACS kits | Our copies of two other ACS kits contain the tool too, in an older version, 3.7.0. | If your kit's copy is older than the one on the utility tools page, use the current download. |
Version numbers on ACS's page and inside the kits do not always match (4.0.1.8 on the website, 4.0.2 in the ACR1552U kit). Check the ACS page on the day you download. The ACS reader driver is a separate, direct download with no registration: see how to install an ACS reader driver on Windows.
Which widgets the tool has
Widgets come in two kinds. A card widget talks to one type of card in any PC/SC reader. A reader widget talks to one reader model and uses that model's own commands. Only the ones below are documented by ACS or found in ACS's installer; we do not list anything we could not trace to an ACS source.
| Widget | Kind | What it is for (from ACS's descriptions) |
|---|---|---|
| MIFARE Classic Card Tool | Card | Most MIFARE Classic commands: loading a key into the reader, authenticating a block, reading and writing data blocks, value-block operations. |
| MIFARE Ultralight and MIFARE Ultralight C | Card | Reading and writing the 4-byte pages of Ultralight-family tags. ACS lists both card types as supported; the installer has a separate module for each. |
| ACOS3 Card Tool | Card | Most ACOS3 commands (ACS's own microprocessor card, supplied in the SDK kits). |
| ACOS6 and ACOS6-SAM Card Tool | Card | Most ACOS6 and ACOS6-SAM commands (the SAM is used for key diversification and mutual authentication in ACS's kits). |
| Reader widgets, for example ACR1552U Reader Tool | Reader | The reader's own commands: reader information, LED and buzzer control, polling and PICC settings, and on NFC readers the NFC features. ACS says the ACR1552U Reader Tool gives access to most of the commands the ACR1552U series supports. |
Reader widgets in the installer
The installer in the ACR1552U SDK v1.01 (tool version 4.0.2) contains reader widgets named for the ACR122U, ACR1252U, ACR1552U, ACR1555U, ACR1581U, ACR1255U, ACR1251T, ACR1281U, ACR1222L and ACR3901 series and the ACM1252U and ACM1281U modules. The ACR1252U, ACR1552U and ACR122U are covered in our model guides (ACR1252U, ACR1552U, ACR122U). We found no reader widget for the ACR39U contact reader; for that reader, use QuickView and the Script Tool (see the ACR39U page).
NFC and NDEF tools
ACS's SDK pages for the ACR1252U and ACR1552U say the tool includes NFC and NDEF tools that demonstrate those readers' NFC modes (card emulation on both, peer-to-peer on the ACR1252U, keyboard emulation on the ACR1552U). The installer's help topics include NFC pages and a card emulation ("card simulation") page. We have not yet seen these tools running, so we do not describe their screens.
Other functions listed in the help
The help topics in ACS's installer also cover connecting and disconnecting a reader, getting the ATR (and ATS for contactless cards), getting the card UID, an APDU console, the command log with export, a DES calculator, and a card explorer for ACOS cards. Each widget has its own help page under the Help menu, which ACS recommends reading before you use it.
Install it on Windows 10 or 11
- Install the reader driver first. Follow the ACS driver guide for Windows and check the reader appears, as in checking that Windows detects the reader. The tool cannot see a reader that Windows does not see.
- Check .NET Framework. ACS's ACR1552U SDK manual says the tool needs Microsoft .NET Framework 4.7.2 or later. Windows 10 (recent updates) and Windows 11 normally include a newer 4.8 version already.
- Get the installer from the ACS utility tools page (after the registration form) or from your SDK kit's installer screen ("Install ACS Smart Card and Reader Tool").
- Run the setup wizard. According to ACS's ACR1252U kit guide, the default folder is "Advanced Card Systems Ltd\ACS Smart Card and Reader Tool" under Program Files (x86), and you can choose a Complete or Custom installation. Choose Complete unless you know which widgets you need.
- Close other card programs (QuickView, the Script Tool, BSD utilities, your own software) before you connect, so the tool can open the card.
- Start the tool, load a widget and connect. Pick the reader, then the card or reader widget you need. Expected result: the reader connects and the log shows the first exchange, such as the ATR when a card is present.
Walk-through: read a MIFARE Classic 1K card on the factory key
Use a new card, or your own test card, that is still on the factory key FF FF FF FF FF FF. If the card belongs to an access control, canteen or transport system, stop here: it will have its own keys, and only that system's supplier should read it. Labels below follow ACS's help topics; the exact button text may differ in your version.
- Place the card on the reader and open the MIFARE Classic Card Tool. Choose the contactless (PICC) reader name, not the SAM slot. Many ACS NFC readers appear twice in Windows, once as PICC and once as SAM.
- Connect. The ATR should appear in the log. For a MIFARE Classic 1K card on ACS readers the ATR ends with the card-name bytes
00 01; our QuickView guide explains how to read the ATR. - Load the key. Enter
FF FF FF FF FF FFas the key and store it in the reader's key slot (the widget asks for a key number; use the first one, usually 00). This only stores the key in the reader's memory; nothing is written to the card. - Authenticate block 4 with Key A. Block 4 is the first data block of sector 1. Expected result: success (status
90 00in the log). If it fails, the card is not on the factory key: see what a failed MIFARE authentication means, and do not try other keys. - Read block 4 (16 bytes). Expected result: 16 bytes; on a blank card they are all
00. - Optional: read block 0. Authenticate block 0 (sector 0) the same way and read it. The first 4 bytes are the card's UID (on 4-byte UID cards), followed by manufacturer data. This block is read-only on genuine cards.
- Optional: read the sector trailer, block 7. On a factory card you should see 6 bytes of
00(Key A is never shown when read), the access bitsFF 07 80 69, then Key B asFF FF FF FF FF FF.
Do not write to sector trailers. Blocks 3, 7, 11 and so on (the last block of each sector) hold the keys and access bits. A wrong write there can lock the sector for good. If you want to try writing, write only to a normal data block such as block 4 on your own test card, then read it back. Changing card keys is outside the scope of this guide.
The same card test with raw commands (FF 82 load key, FF 86 authenticate, FF B0 read) is in our MIFARE test guide, and reading just the UID without any key is in how to read an NFC card UID.
Walk-through: read an NTAG tag and its NDEF message
NTAG213, NTAG215 and NTAG216 tags use the same 4-byte page layout as MIFARE Ultralight, and they need no key for reading unless the owner has set a password. ACS lists MIFARE Ultralight and Ultralight C for this tool but does not name NTAG, so the Ultralight widget is the likely route but is not confirmed by ACS. If it does not accept the tag, use the tool's APDU console or the Script Tool with the read command shown below.
- Place the tag on the reader and open the MIFARE Ultralight widget on the PICC reader, then connect.
- Read page 3, the capability container. On a tag formatted for NDEF it starts with
E1; the third byte gives the data area size. Our MIFARE guide explains these bytes in the NTAG capability container section. - Read from page 4. One read returns 16 bytes, which is 4 pages. If the widget offers an APDU console instead, the PC/SC read command is
FF B0 00 04 10(read 16 bytes from page 4). Read page 8 next to get the rest of a short message. - Find the NDEF message. Look for the byte
03(NDEF message), followed by its length, then the message, thenFE(end).
Example: decoding a web link by hand
Suppose a tag holds the link https://bsdinfotech.com. Pages 4 to 9 would read:
Page 4: 03 14 D1 01
Page 5: 10 55 04 62
Page 6: 73 64 69 6E
Page 7: 66 6F 74 65
Page 8: 63 68 2E 63
Page 9: 6F 6D FE 00
03 14: an NDEF message of 0x14 = 20 bytes follows.D1 01 10 55: one short, well-known record, type length 1, payload length 0x10 = 16 bytes, type55= "U" (a URI).04: URI prefix code for "https://".62 73 ... 6D: the text "bsdinfotech.com" in ASCII.FE: end of the NDEF data.
If your reader's widget has the NDEF tool that ACS describes for the ACR1252U and ACR1552U, it should decode this for you. Reading by hand is still useful to check what a tag really holds. For reading and writing links or text on NTAG tags without commands, the BSD utilities have an NTAG tab (see below).
Reader settings: buzzer, LED and polling
Reader widgets can change how the reader itself behaves. The help topics in ACS's installer include buzzer settings, LED and buzzer behaviour, automatic polling and polling options, PICC operating parameters (which card types the reader looks for), transmission settings, exclusive mode and, on NFC readers, card emulation. Which of these your reader has depends on the model; the ACS reference manual for the model lists them.
Do not change settings you do not understand
Some of these settings are stored inside the reader and stay after you unplug it. If you switch off polling for a card type, the reader will simply stop detecting those cards, which looks exactly like a broken reader. If you enable card emulation or keyboard emulation, the reader may stop behaving as a normal PC/SC card reader for your software. Before changing anything, note the current value (take a screenshot), change one setting at a time, test, and change it back if you do not need it. Never change reader settings on a reader that is in use in a live system.
Safe things to try
- Reader information: read the firmware version and reader details. Read-only.
- LED and buzzer control for a moment: make the LED or buzzer react once, to check the reader responds to commands. This does not change stored settings.
- Get the UID and ATR of a card. Read-only.
Leave alone unless you have a reason
- Default buzzer behaviour on card detection (some users want it silent; that is fine, but write down the old value).
- Automatic polling, polling interval and PICC operating parameters.
- Card emulation, keyboard emulation (ACR1552U) and exclusive mode.
If an ACR1552U has been switched into keyboard (HID) emulation, it types the card UID into a text editor instead of working as a PC/SC reader. ACS's Keyboard Configuration Tool is the tool for that mode; see our ACR1552U driver and test guide.
Smart Card and Reader Tool vs QuickView, Script Tool and BSD utilities
| Tool | Best for | How you use it | Get it |
|---|---|---|---|
| ACS QuickView | Is the reader working, and does it see the card? ATR and card presence. | No commands at all. Windows, macOS, Linux. | ACS utility tools page (registration). Our QuickView guide. |
| ACS Smart Card and Reader Tool | Trying card functions (MIFARE Classic, Ultralight, ACOS) and reader functions through widgets. | Buttons and fields; the log shows the commands. Windows only. | ACS utility tools page (registration), or the ACR1252U and ACR1552U SDK kits. |
| ACS Script Tool | Sending exact APDU commands, and repeating a sequence from a script. | You type or load the command bytes. | ACS utility tools page (registration). Our Script Tool guide. |
| BSD utilities (BSD Infotech's own software, not ACS) | Card identity, MIFARE Classic, NTAG and DESFire tests on factory keys, for the ACR1252U, ACR1552U, ACR122U, ACR39U and ACR35. | One window per reader model, no commands. Reading and writing card data needs a BSD licence key; card identity is free. | Free download after a one-time email check: ACR1252U, ACR1552U, ACR122U. |
Not sure which one you need? The tool chooser on our testing hub answers it question by question, and the BSD utilities section explains the email check and the licence key. The BSD utilities work with factory keys only and cannot change card keys.
Smart Card and Reader Tool problems and fixes
| What you see | Likely cause | What to do |
|---|---|---|
| The tool does not start, or Windows reports a .NET error | .NET Framework 4.7.2 or later is missing | Install the current .NET Framework 4.8 from Microsoft, then start the tool again. |
| No reader in the list | Driver not installed, reader not detected, or the Smart Card service is stopped | Work through reader detection and the Smart Card service check. |
| No reader on a Remote Desktop session | Windows redirects smart card readers differently over Remote Desktop | See readers over Remote Desktop, or test on the PC the reader is plugged into. |
| Connect fails, or a sharing or "in use" error | Another program (QuickView, a BSD utility, your own software) holds the card | Close the other program, lift the card, place it again and reconnect. Error codes are explained in PC/SC error codes. |
| Your reader model has no reader widget | Older tool version (for example 3.7.0 from an older kit), or a model ACS has no widget for | Download the current version from ACS. Card widgets still work on any PC/SC reader. |
| MIFARE authentication fails | The card is not on the factory key, wrong key type (A or B), or wrong block | Check you loaded FF FF FF FF FF FF and chose Key A. If it still fails, the card has its own keys: see failed MIFARE authentication. Do not try lists of keys. |
| Authentication works but the read fails | The block is in a different sector from the one you authenticated | Authenticate a block in the same sector (blocks 4 to 7 are sector 1), then read. |
| The Ultralight widget does not read an NTAG tag | NTAG is not on ACS's supported list for this tool, the page is outside the tag's memory, or it is password-protected | Use the APDU console or Script Tool with FF B0 00 04 10; check page ranges in our NTAG section. |
| Cards stopped being detected after you changed settings | Polling or a card type was switched off in the reader | Restore the value you noted before the change. If you did not note it, check the default in ACS's reference manual for your model, or contact us. |
| ACR1552U types numbers into Notepad but the tool sees nothing | The reader is in keyboard (HID) emulation mode | Switch it back with ACS's Keyboard Configuration Tool; see the ACR1552U guide. |
Sources
The tool name, version, platform, supported cards and download route were checked on the official ACS pages on 17 Nov 2026. Installation notes, widget descriptions and help topic names come from ACS SDK documentation and ACS's installer, summarised in our own words. The MIFARE and NDEF byte layouts are standard card facts. Version numbers change, so check the ACS page before you download.
- ACS Utility Tools (Smart Card and Reader Tool v4.0.1.8, Windows; supported cards)
- ACS ACR1552U SDK (kit contents; NFC and NDEF tools)
- ACS ACR1252U SDK (kit contents; NFC and NDEF tools)
- ACS ACR1552U Series SDK User Manual v1.01 (widgets, .NET Framework requirement) and the ACR1252U SDK v2.00 installation guide (setup wizard), supplied with the ACS SDK kits
BSD Infotech is an independent ACS supplier and integrator, not the manufacturer. ACS, the ACS logo, ACOS and ACS product names belong to Advanced Card Systems Ltd. MIFARE, MIFARE Classic, MIFARE Ultralight, NTAG and DESFire are trademarks of NXP B.V. Windows and .NET are trademarks of Microsoft Corporation.
