ACS Script Tool: Installation and Usage Guide

What is the ACS Script Tool and how do you use it? The ACS Script Tool is a free ACS (Advanced Card Systems) program that sends APDU commands to a card, or to the reader itself, through any ACS PC/SC reader. You type the commands into its editor, one per line, or open a saved script file. The tool shows every command it sends and every reply it gets back. Get it from the official ACS utility tools page. Install the reader driver first, then choose your reader, place a card and run a one-line script such as FF CA 00 00 00. If the reply ends in 90 00, the reader, the card and the command all worked.

This guide covers where to get the current version, how to install it on Windows 10 and 11, and how to write a first script. It also shows how to read the reply, how to save a script and run it again, which commands to keep away from, and what to do when a script fails. The Script 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. We based the script syntax and screen descriptions on this page on the help file that ships with Script Tool 5 in ACS's ACR1552U SDK, and on ACS's SDK manuals. BSD has not yet run Script Tool 5.2 on its own readers. The scripts below are marked "Not yet tested on hardware" until we do, and we will add our screenshots after that test.

ACS describes the Script Tool simply: it sends APDU command scripts and runs them. An APDU (application protocol data unit) is one command to a smart card, written as a string of bytes in hexadecimal, such as FF CA 00 00 00. The card, or the reader on the card's behalf, answers with some data followed by two status bytes, SW1 SW2. 90 00 means success.

Every card program sends APDUs in the end. The Script Tool lets you send the same commands by hand and check each reply before you write any code. You can use it in two ways:

  • One command at a time. Type a single line, run it and look at the reply. This is the quickest way to check one command, for example the UID command from our UID guide.
  • As a script file. Put a sequence of commands in a plain text file, add comments and the replies you expect, and run the whole file. The tool can repeat the file a set number of times, which is useful for testing many cards the same way.

The help file for Script Tool 5 lists features that go beyond plain sending:

  • Several readers at once. Each line can be sent to a different reader.
  • Variables. Bytes from one reply can be stored and used in a later command.
  • Built-in operators and ciphers. Bitwise and arithmetic operators, plus DES, 3DES and AES.
  • Reader control commands. These go to the reader itself (through the PC/SC SCardControl call), not to the card.
  • Card polling. The tool notices a card arriving and leaving.

For a first test you need none of these extras. ACS lists the Script Tool for its PC/SC readers in general (contact, contactless and dual-interface) and for every card those readers support. It therefore applies to the ACR1252U, ACR1552U, ACR122U and ACR39U alike.

It does not check whether Windows sees your reader in the first place. That is QuickView's job: see our ACS QuickView guide. It also has no ready-made buttons for card functions, so you have to know which command to send.

Download it from the ACS utility tools page. When we checked on 17 Nov 2026, each Script Tool download link on that page led to an ACS registration form. ACS asks for your name, company, country and email before it offers the file. ACS states that its utility tools are free of charge.

Where ACS lists itName and version shownPlatform
ACS utility tools page (current download)ACS Script Tool 5.2Windows
ACS utility tools pageACS Script Tool 5 for macOS; ACS Script Tool 5 for Linux OSmacOS; Linux
ACR1552U SDK product page and SDK user manual v1.01Script Tool 5.02Windows (inside the SDK package installer), macOS (.dmg) and Linux (AppImage)
Older ACS SDK kits"Script Tool 4" (ACR39U SDK); "ACR122U PCSC Scripting Tool" (ACR122U SDK)Windows

ACS writes "5.2" on the tools page and "5.02" in the SDK. We have not yet confirmed whether these are the same build. The About box will tell you, and we will note the result here after our test. Older kits carry the earlier generations of the tool, and their script syntax may differ. This guide follows Script Tool 5, so for a new installation use the version on the tools page.

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

  1. Install the reader driver and check the reader first. The Script Tool does not install a driver. Follow the ACS driver installation guide for Windows 10 and 11. Then confirm the reader appears under Smart card readers in Device Manager (how to check). Opening QuickView once is the quickest proof that programs can see it.
  2. Download "ACS Script Tool 5.2" from the ACS utility tools page, after the short registration form. Pick the Windows entry; the macOS and Linux entries will not run on Windows.
  3. 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 SmartScreen or your antivirus warns about the file, check that it came from acs.com.hk before you continue.
  4. Or install it from an SDK kit. If you bought an ACS SDK kit such as the ACR1552U SDK, its installer has an option that installs the SDK package. ACS's SDK manual says this option puts the Script Tool, QuickView and the other utilities on the PC in one step.
  5. Close other card software, including QuickView, the BSD utilities, your own programs and any background card monitor. Then open the Script Tool from the Start menu.

Expected result: the Script Tool opens and lists the readers it found in its log area, each with an index number. In ACS's help screenshots this list appears under the heading "Detected Readers".

macOS and Linux

ACS offers separate Script Tool 5 downloads for macOS and Linux. The ACR1552U SDK manual describes the SDK copies: on macOS the tool comes as a disk image; on Linux it is an AppImage that needs pcscd (the Linux PC/SC service) and the FUSE library installed first. BSD has not tested either version; this guide covers Windows 10 and 11.

This is the Script Tool 5 window as ACS's help file describes it. Your version may differ slightly.

PartWhat it is for
Reader list (top)Chooses the default reader. Script lines that do not name a reader go to this one. For contactless cards, choose the contactless (PICC) entry, not the SAM slot.
Refresh buttonRestarts the card and reader polling. The help file says it shows green while polling runs and red when polling has stopped.
IterationsHow many times the whole script runs in a loop. Leave it at 1 for a first test.
Check Syntax, Execute, Pause, StopCheck the script for mistakes without sending anything; run it; pause it; stop it.
File iconsNew script, open a script (any text file), save the script or the logs as a text file, plus cut, copy, paste and clear logs.
Input window (editor)Holds the script with line numbers. Comment lines are shown in a different colour.
Main LogsThe detected readers, then each command sent and each reply received. An Auto save logs option writes the log to a file as the script runs.
Error LogsA table of the lines that failed, with the line number and the reason.
Help (the ? icon)The About box, and the full Script Tool help in HTML. Use it for the functions this guide does not cover.

A Script Tool 5 script is a plain text file with one command per line. The help file gives the general shape of a command line as:

[reader index]  command bytes  [expected or saved data]  (SW1 SW2)

Only the command bytes are required. The rest is optional. Five rules cover everything you need for a first script:

  1. Write bytes as two hex digits, separated by spaces: FF CA 00 00 00, not FFCA000000. Upper or lower case both work.
  2. Leave out the reader index to use the reader chosen in the reader list. To send a line to another reader, start it with that reader's index in square brackets, as listed under Detected Readers. In ACS's example the first reader is [0].
  3. Put the status word you expect in round brackets at the end: (90 00). The tool then checks the reply and stops with an error prompt if it does not match. Without it, no check is made.
  4. Put expected data, or variables to save data in, in square brackets before the status word. XX is a wildcard for "any byte here". V1, V2 and so on are variables (up to V99999).
  5. Start a line with a semicolon (;) to make it a comment. Comment freely: the next person to run the script will thank you.

A few functions use their own keywords in square brackets. The ones you are most likely to meet are:

  • [RST] [n] resets the card connection on reader n.
  • [DSP] [V1 V2 ...] shows the bytes saved in variables.
  • [CMP] compares two values.
  • [MAP] redirects a reader index used in the script to a different real reader.
  • [D] sends a control command to the reader rather than to the card.

The help file also lists the cipher functions and the bitwise and arithmetic operators.

The safest first command is Get Data, FF CA 00 00 00. The reader answers it on the card's behalf with the card's UID, and the command changes nothing on the card. Our UID guide explains each byte of it. Language: ACS Script Tool 5 script (plain text). Prerequisites: reader driver installed, Script Tool open, a contactless test card such as a MIFARE Classic 1K, NTAG or DESFire card.

Not yet tested on hardware. These scripts follow the syntax in ACS's Script Tool 5 help file. BSD will run them with an ACR1252U, ACR1552U and ACR122U on Windows 11 and Windows 10 and replace this note with the result.

Step 1: connect to the card

  1. Choose the contactless (PICC) reader in the reader list at the top.
  2. Place one card flat in the middle of the reader and leave it there. The tool polls the reader and connects to the card itself. ACS's help documents no separate "connect" command; [RST] is only for resetting a connection. If the refresh button is red, click it so polling starts again.
  3. Check Main Logs. Your reader should be listed with its index. In ACS's example, a reader with a card in it shows the card protocol and the word Active on the same line.

Step 2: send GET DATA

Click Create New Script and type these three lines into the input window:

; BSD first script: read the card UID (read-only). Not yet tested on hardware.
; Choose the contactless (PICC) reader above and place one card on it.
FF CA 00 00 00

Click Check Syntax. It should report no errors. Then click Execute.

Step 3: read the response and the status word

The Main Logs show the command with a < in front of it and the reply with a >. For a card with a 4-byte UID, the result looks like this (the UID here is an example, not a recorded result):

< FF CA 00 00 00
> A1 B2 C3 D4 90 00

Expected result: the last two bytes are 90 00 and everything before them is the UID: 4 bytes for most MIFARE Classic cards, 7 bytes for NTAG, Ultralight and most DESFire cards. If the reply is only two bytes starting with 6, the command failed. Look the code up in the status word table in our UID guide.

Step 4: let the tool check the reply for you

Add the expected status word, and the tool will stop if it does not get it. The second version below also stores the first four UID bytes in variables and displays them, which shows how variables work:

; Version 2: check the status word. Not yet tested on hardware.
FF CA 00 00 00 (90 00)

; Version 3: also save the first 4 UID bytes in V1-V4 and show them.
FF CA 00 00 00 [V1 V2 V3 V4] (90 00)
[DSP] [V1 V2 V3 V4]

If it fails: an error prompt offers Ignore This Error, Ignore All Errors or Quit Execution, and the Error Logs tab gives the line number and the reason. Double-click a line in the output to jump to the script line that produced it. Common causes are in Problems below.

The same pattern works for the read-only MIFARE and NTAG commands in our MIFARE card test guide, one command per line. That guide explains which commands are safe and in what order to send them, so we do not repeat them here.

Every reply follows the same pattern: data bytes, if any, then exactly two status bytes. Read it from the end:

  1. Look at the last two bytes first. 90 00 means success. Anything starting with 6 (for example 63 00 or 6A 81) means the command was refused or failed, and there is usually no data in front of it.
  2. Count the data bytes. Check the number against what the command asks for: a UID is 4, 7 or 10 bytes, and a MIFARE Classic block read returns 16.
  3. Note the reader and the card type with the result. Status words for reader commands (class byte FF) are set by the reader. The same command can give a different error code on a different reader model, so the reference manual for your reader is the final word.

For the status words of Get Data, and how to write a UID as a number, see the UID guide. For the replies to authentication and block reads, see the MIFARE test guide.

  • Save: use the save icon. Scripts are plain text files, so give them a clear name such as get-uid-acr1252u.txt and keep them with your project.
  • Re-run: use the open icon to load the file into the input window, place the card and click Execute. You can also edit a script in Notepad; the tool only needs a text file.
  • Repeat: set Iterations to run the whole script several times in a row. The log numbers each pass ("Loop 1", "Loop 2"...). Use this for read-only scripts only. A script that writes will write again on every loop.
  • Keep the evidence: save the Main Logs as a text file, or tick Auto save logs. ACS's help says auto-saved files are named ACS_ScriptTool5_Logs_ followed by the date and time, and each file holds up to 2 MB. A saved log tells a developer or a support engineer exactly what was sent and what came back.

Before you share a script or a log, remove any real keys or customer data from it.

The Script Tool sends exactly what you type

The tool does not ask "are you sure?". A single wrong write can make a card, or one sector of it, unusable for good. Follow these rules on every test:

  • Use only test cards on factory keys (MIFARE Classic: FF FF FF FF FF FF), labelled and kept apart from live cards. Never test on cards that are in use.
  • Never write a MIFARE sector trailer (the last block of each sector, such as block 03, 07 or 0B). The trailer holds the keys and access bits.
  • Never change keys. That means no sector trailer writes on MIFARE Classic, and no ChangeKey or format command on DESFire. Leave key management to your finished application.
  • Never write block 0, or pages 0 to 3 of an Ultralight or NTAG tag.
  • Read every line of a script you did not write before you run it, and never set Iterations above 1 on a script that writes.
  • Leave the [D] reader control commands alone unless your reader's reference manual documents the exact command. They change how the reader behaves.

The full list of protected blocks and pages, and a test-card log, is in the safety section of our MIFARE test guide. BSD Infotech gives no guidance on recovering or guessing unknown keys. If a card's keys are not the factory keys and you do not know them, use a different card.

You want toBest toolWhy
Check that Windows and programs see the reader, and that a card is detectedACS QuickViewNo commands needed. It shows reader names, card arrival and the ATR.
Send a command, check the reply, and keep the sequence as a file to run againACS Script Tool (this page)Scripts, expected-reply checks, variables, several readers, loops and logs
Send a few commands quickly from Chrome or Edge, or test a web-based card ideaACS Web APDU ToolRuns in the browser, with ACS's extension and a small helper program installed on the PC
Try MIFARE Classic, Ultralight or ACOS card functions with buttons instead of commandsACS Smart Card and Reader ToolReady-made widgets for the card types ACS lists
Read the UID, or read and write factory-key MIFARE, NTAG or DESFire cards, without typing commandsBSD reader utilitiesBSD Infotech's own software. Factory keys only; cannot change keys.

The test tool chooser in our testing centre compares all of them side by side. A common order is: QuickView to prove the reader, then the Script Tool to prove the commands, then your own code using the same commands. The SDK guides for the ACR1252U, ACR1552U and ACR122U show the same commands sent from C#.

What you seeLikely causeWhat to do
No reader in the list or under Detected ReadersDriver missing, reader not detected, or the Windows Smart Card service stoppedCheck Device Manager (detection guide) and the Smart Card service. Restart the Script Tool with the reader plugged in.
No reader, but only over Remote DesktopThe session sees the readers of the computer you connect fromSee Remote Desktop and smart card readers.
Card placed but nothing happens, refresh button redCard and reader polling has stoppedClick the refresh button. If it stays red, unplug and replug the reader and restart the tool.
Error that the card is in use, or a sharing violationAnother program holds the card: QuickView, a BSD utility, your own program, or a background monitor such as ACS's Reader Monitor ProgramClose the other card software and run the script again. The reader states guide explains why only one program can hold a card exclusively.
Check Syntax reports errorsBytes not written as two hex digits with spaces, a letter that is not hex (such as O for zero), or a bracket left openRewrite the line as FF CA 00 00 00. Errors and warnings list the line number.
Error prompt says the expected data is not equalThe reply did not match the bytes in your [ ] or ( ). Usually the command failed, so the reply was a 6X XX status word.Remove the check, run the line again and read the real reply. Then look up the status word (Get Data codes).
Line sent to the wrong readerThe script uses a reader index that belongs to another reader on this PC (indexes change when readers are added)Remove the index so the line uses the reader chosen in the list, or redirect it with [MAP].
Command fails only on a contactless cardSAM entry chosen instead of PICC, or the card moved during the scriptChoose the PICC entry, keep the card still in the middle of the reader, and use [RST] or place the card again.
An ACR1552U types numbers into Notepad, and the Script Tool gets no cardThe reader is in keyboard emulation mode, which is not PC/SCSwitch it back with the ACS configuration tool; see the testing centre.
Linux AppImage does not start or sees no readerFUSE library or pcscd missingInstall both, as ACS's SDK manual says, then start the AppImage again. (Not tested by BSD.)

We checked the tool names, versions, platforms and the registration step on the official ACS pages on 17 Nov 2026. The script syntax and the screen descriptions come from the Script Tool 5 help file in ACS's ACR1552U SDK, and the installation notes from ACS's SDK user manuals. Everything is summarised in our own words. Version numbers change, so check the ACS page before you download.

  • ACS Utility Tools (ACS Script Tool 5.2 for Windows; Script Tool 5 for macOS and for Linux; QuickView; Smart Card and Reader Tool; Reader Monitor Program)
  • ACS ACR1552U SDK (kit contents: Script Tool 5.02)
  • ACS ACR1552U Series SDK User Manual v1.01 and the Script Tool 5 help file in its SDK package; ACR39U SDK User Manual v1.00 (Script Tool 4); ACR122U NFC Reader SDK User Manual v2.0 (PCSC Scripting Tool): supplied with the ACS SDK kits

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

Commands work in the Script Tool. What next?

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