PC/SC Learning Tool: Complete Guide
← Back to the ACS testing and utilities centre
What is the PC/SC Learning Tool? It is a small Windows program from ACS (Advanced Card Systems) that lets you run the Windows PC/SC smart card functions one at a time, by pressing buttons instead of writing code, and shows each call and its result in an output window. ACS supplies it inside its SDK kits, including the ACR1252U SDK. When we checked on 17 Nov 2026, it was not offered on the ACS utility tools download page.
What does it teach? It shows the order in which a program talks to a reader. First it opens a session with the Windows Smart Card service (SCardEstablishContext). Then it connects to the card in a chosen reader, with a share mode and protocol (SCardConnect), reads the card's state and ATR, and reconnects or disconnects. Once you have seen these steps work, the same calls in your own C# or C++ code are easier to follow and to debug.
This guide explains where the tool comes from, what each PC/SC step means in plain words, how the steps map to real code, and which errors you are likely to meet. The PC/SC Learning 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. This page is based on ACS's kit contents list and on ACS's SDK manual, which describes the tool and shows one screenshot of it. BSD has not yet run the tool itself, so the screen descriptions below cover only what ACS shows. This page will be updated after our own test.
What the PC/SC Learning Tool Is and Where It Comes From
The PC/SC Learning Tool is published by ACS, the maker of the ACR1252U, ACR1552U, ACR122U and ACR39U readers. ACS's ACR39U SDK manual describes it as a tool for running PC/SC-compliant Windows API smart card functions, and refers to the tool's own Help menu for instructions. It is a teaching aid for developers. It is not a driver, a reader test, or a card reading and writing tool.
We checked where it appears:
| Where we looked | PC/SC Learning Tool listed? |
|---|---|
| ACS ACR1252U SDK product page (kit contents) | Yes. Listed as "PCSC Learning Tool" under Tools and Utilities, with QuickView, Script Tool 5 and the Smart Card and Reader Tool. |
| ACS ACR39U SDK v1.00 (user manual and Getting Started page) | Yes. It has its own section in the manual, with a screenshot (described below). |
| ACS utility tools page (free downloads) | No. QuickView, Script Tool, the Smart Card and Reader Tool and others are there; the PC/SC Learning Tool is not. |
| ACS ACR1552U SDK (product page 579 and SDK v1.01) | No. Its tools are QuickView, Script Tool, the Smart Card and Reader Tool and the Keyboard Configuration Tool. |
| ACS ACR122U SDK v1.3 | No. It has its own ACR122U tools instead (NFC Reader Tool, PCSC Scripting Tool, QuickView). |
So, as far as we can see, it is an SDK-only tool: it comes with certain ACS development kits and is not a separate download. Contents differ from kit to kit, so check the "Tools and Utilities" list on the ACS product page of the kit you are buying. For the ACR1252U kit as a whole (sample code, cards and manuals), see our ACR1252U SDK guide.
How to Get the Tool
- With an ACS SDK kit. The ACR1252U SDK is a development kit sold by ACS and its partners. It includes the reader, test cards and an installer with the tools, sample code and manuals. BSD Infotech can supply ACS SDK kits on enquiry.
- Install from the kit. In the ACS SDK kits we have, the tools are installed from the SDK's own setup program, together with the sample code. Install the reader driver first; the ACS driver guide for Windows 10 and 11 explains how. We have not run the ACR1252U kit's installer, so we cannot yet confirm the exact folder or Start menu name it uses for this tool.
- Without a kit. We are not aware of a public download. If you need the tool on its own, ask ACS. BSD Infotech does not redistribute ACS software. If someone offers you a copy from another website, do not use it.
If you only want to learn the call sequence, you do not need the tool. The free alternatives are ACS QuickView to see readers and cards, and the ACS Script Tool to send commands. Our C# PC/SC status check also prints the same information from your own code.
What the Tool's Window Shows
The only screenshot we have is in ACS's ACR39U SDK manual. It was taken with an ACR39U contact reader and an ACS contact card. The window has three parts:
- Left: the step list. A Teach Mode tick box (ticked in ACS's picture), four buttons Step 1 to Step 4, and Help and About buttons. In the screenshot only the current step's button is active, which suggests the steps are taken in order.
- Middle: the current step. The picture shows Step 2, the connection step. It has a Reader Port list (the reader name, here "ACS ACR39U ICC Reader 0"), Share Mode, Preferred Protocol and Active Protocol fields, and buttons for
SCardConnect,SCardReconnectandSCardDisconnect, each with a Disposition choice, plus Next. - Right: the output. A log of each call and its result. In ACS's picture it shows
SCardEstablishContext, thenSCardConnectwith the reader name, thenSCardStatewith the card state (SCARD_SPECIFIC), the protocol (SCARD_PROTOCOL_T0), the ATR length (19 bytes) and the ATR itself. Clear and Exit buttons sit below it.
ACS's material does not show what Steps 1, 3 and 4 contain, and does not explain what Teach Mode changes. The tool's Help menu covers both. We will add them here once we have run the tool.
The PC/SC Steps in Plain Words
PC/SC is the standard way for Windows programs to talk to smart card readers. Every program, including the Learning Tool, uses the same functions from Windows' winscard.dll. The table explains each one and says whether it appears in ACS's screenshot of the tool.
| PC/SC function | What it does, in plain words | In ACS's screenshot? |
|---|---|---|
SCardEstablishContext | Opens a session with the Windows Smart Card service. Nothing else works until this succeeds. | Yes, first line of the output |
SCardListReaders | Asks the service for the names of all readers it knows. Programs then pick a reader by its exact name. | Reader names appear in the Reader Port list; the call itself is not shown |
SCardConnect | Connects to the card in one reader. You choose a share mode and the protocol(s) you accept; the reader tells you which protocol was actually used. | Yes, button and output |
SCardState / SCardStatus | Reports the card's current state, protocol and ATR (the bytes the card sends when it is powered up, which identify the card type). | Yes, SCardState in the output |
SCardReconnect | Re-establishes the connection, for example after another program reset the card, optionally resetting or powering down the card first. | Yes, button |
SCardTransmit | Sends a command (an APDU) to the card and returns the card's answer, ending in a status word such as 90 00 (success). | Not shown |
SCardDisconnect | Ends the connection to the card and says what to do with it: leave it, reset it or power it down. | Yes, button |
SCardReleaseContext | Closes the session with the Smart Card service. Programs should always do this, even after an error. | Not shown |
The connection settings
- Share mode.
SCARD_SHARE_SHAREDlets other programs use the same card too; this is the right choice almost always.SCARD_SHARE_EXCLUSIVElocks everyone else out.SCARD_SHARE_DIRECTtakes the reader itself for direct control, with or without a card, for reader commands rather than card commands; other programs cannot use the reader meanwhile. - Preferred protocol. The protocols you accept:
T0,T1or both. ACS's screenshot uses T=0 with a contact card. Contactless cards may use a different protocol, so if a connect fails with a protocol error, allow both. - Active protocol. Not a setting: it is the protocol the reader actually chose, filled in after a successful connect.
- Disposition. What happens to the card when you disconnect or reconnect. The usual choices are
SCARD_LEAVE_CARD(leave it as it is),SCARD_RESET_CARD(reset it) orSCARD_UNPOWER_CARD(switch it off). Leave the card is the usual choice.
Reading the output
The state that SCardState and SCardStatus report is one value from a short list defined by Microsoft. They run from SCARD_ABSENT (no card) and SCARD_PRESENT (card there but not ready) through SCARD_POWERED and SCARD_NEGOTIABLE to SCARD_SPECIFIC. SCARD_SPECIFIC is what you want to see: the card is powered and a protocol is set, so commands can be sent. These are not the same as the SCARD_STATE_... reader flags that monitoring tools and certutil show. Those are explained in reader states and what they mean.
The ATR identifies the type of card. For contactless cards on ACS readers, the reader builds the ATR itself; our QuickView guide explains how to read one byte by byte.
From the Tool to Your Own Code
Each button in the tool matches a call your program will make. BSD's guides already include C# examples for .NET 8 (Windows, calling winscard.dll directly), so this page does not repeat them:
| What you did in the tool | The same thing in code |
|---|---|
| Open a session and see the reader names | SCardEstablishContext, SCardListReaders: C# PC/SC reader status check (read-only, never connects to a card) |
| Connect to the card, send a command, disconnect | SCardConnect, SCardTransmit, SCardDisconnect, SCardReleaseContext: the C# read-UID examples for the ACR1252U, the ACR1552U and the ACR122U |
| Read the card's state, protocol and ATR | SCardStatus after connecting, or SCardGetStatusChange without connecting (used in the status check) |
| Watch for a card arriving or leaving | SCardGetStatusChange in a loop: see reader states |
Three habits to take from the tool into your code:
- Pick the reader from a fresh list, by its exact name, rather than storing a name. ACS readers can show more than one entry (for example a PICC entry for cards and a SAM entry); our guide on ACS reader names lists them.
- Use shared mode and accept both protocols unless you have a reason not to. Most "works in the tool, fails in my program" cases come down to a different share mode or protocol.
- Always disconnect and release, even when a call fails. A program that leaves a connection open can block the reader for other programs.
Use SCardStatus in new code. The tool's output names SCardState, an older call that is not in Microsoft's current list of documented smart card functions; SCardStatus is the documented way to read the same state, protocol and ATR. The order of calls for each model, and the reader commands that go through SCardControl, are covered on the ACR1252U SDK page and the smart card SDK guide.
Common Errors at Each Step
ACS's screenshot shows only calls that worked, and we have not yet seen how the tool displays a failure. When a PC/SC call fails, Windows returns one of a fixed set of codes, and any tool or program built on PC/SC gets the same codes. These are the ones you are most likely to meet at each step. The full list, with values and fixes, is in our PC/SC error code table.
| Step | Likely error | What it usually means |
|---|---|---|
| Establish context | SCARD_E_NO_SERVICE | The Windows Smart Card service is not running. See the Smart Card service. |
| List readers | SCARD_E_NO_READERS_AVAILABLE | The service is running but has no reader: check the USB cable, the driver, or Remote Desktop. |
| Connect | SCARD_E_NO_SMARTCARD | No card on the reader. Place or insert the card first, then connect. |
| Connect | SCARD_E_SHARING_VIOLATION | Another program, often another test tool, holds the card in exclusive mode. Close it. |
| Connect | SCARD_E_PROTO_MISMATCH | The card does not use the protocol you chose. Allow T=0 and T=1. |
| Connect | SCARD_W_UNRESPONSIVE_CARD | The card does not answer: unsupported, faulty, or inserted the wrong way round. |
| Status, reconnect, transmit | SCARD_W_REMOVED_CARD, SCARD_W_RESET_CARD | The card moved away, or another program reset it. Reconnect. |
| Any step after a release | SCARD_E_INVALID_HANDLE | The session or connection was already closed. Start again from the first step. |
Other problems
- The tool is not in my SDK. Not every ACS kit includes it (see the table above). Use QuickView and the Script Tool instead.
- The reader list is empty. Close the tool, check that Windows sees the reader (detection guide) and that the Smart Card service is running, then start the tool again with the reader plugged in.
- It works in the tool but not in my program. Compare the reader name, share mode and protocol your code uses with the ones that worked in the tool, and close the tool before running your program.
- The reader is in keyboard emulation mode. A reader that types the UID as text (some ACR1552U set-ups) is not using PC/SC for that output, so the tool cannot help there.
Who Should Use the PC/SC Learning Tool
| Good fit | Use something else |
|---|---|
| Developers new to PC/SC who have an ACS SDK kit and want to see the call order before they write code | Checking that a new reader works: use QuickView or the three basic checks |
| Trying share modes, protocols and disposition choices on a real card, to see which one your card needs | Sending your own APDU commands: ACS Script Tool, listed on the ACS utility tools page |
| Training and teaching: showing a team what each PC/SC function does | Reading the UID or MIFARE, NTAG or DESFire data without code: read a card UID, BSD reader utilities |
| Support staff narrowing down a "works here, not there" problem | macOS or Linux: the tool is described as using the Windows API |
Sources
Kit contents and the utility tools list were checked on the official ACS pages on 17 Nov 2026. The tool's description and window come from the ACS ACR39U SDK manual, summarised in our own words. Function names, share modes, protocols, dispositions, card states and error codes are Microsoft's Windows smart card API (winscard).
- ACS ACR1252U SDK (kit contents: PCSC Learning Tool, QuickView, Script Tool 5, Smart Card and Reader Tool)
- ACS Utility Tools (free downloads; the PC/SC Learning Tool is not listed)
- ACS ACR39U Smart Card Reader SDK v1.00: Software Development Kit User Manual v1.00 (section 3.4.1, Figure 2) and Getting Started page; ACS ACR1552U Series SDK v1.01 and ACR122U SDK v1.3 user manuals (tool lists). Supplied with the ACS SDK kits.
- Microsoft: winscard.h API reference (SCardConnect, SCardStatus, SCardReconnect and related functions)
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. Windows is a trademark of Microsoft Corporation.
