How to Check (and Upgrade) ACS Reader Firmware Version
← Back to the ACS testing and utilities centre
How do I check the firmware version of an ACS reader? Ask the reader. Every ACS reader in this guide has a documented "Get Firmware Version" command, and the answer comes back as a short piece of text such as ACR1252U_V100.1. Without writing code, use the Reader tab of the free BSD ACR1252U utility, or send the command with the free ACS Script Tool. Developers send E0 00 00 18 00 to an ACR1252U or ACR1552U as a PC/SC escape command, or FF 00 48 00 00 to an ACR122U. Upgrading is a different matter: ACS says the ACR1252U and ACR1552U support USB firmware upgrades, but it publishes no upgrade files or tool on their download pages, so ask ACS or BSD before you change anything. For readers supplied by BSD Infotech, we can raise a firmware request with ACS for you.
This guide covers the ACR1252U, ACR1552U and ACR122U. Every command and reply format below comes from the ACS manual for that reader, and the manual versions are listed under Sources. BSD Infotech is an independent ACS supplier and integrator, not the manufacturer.
Not yet tested by BSD. The commands, scripts and C# example follow ACS's manuals and the ACS Script Tool help file. BSD will run them on its own ACR1252U, ACR1552U and ACR122U readers on Windows 11 and Windows 10 and add the real replies here.
Check the Firmware Version Without Writing Code
Before you start, make sure Windows can see the reader (how to check that Windows detects the reader) and that you know exactly which model you have (how to identify your ACS reader model). Then pick one of these:
| Method | Readers | What you do | Card needed? |
|---|---|---|---|
| BSD ACR1252U NFC Card Utility, Reader tab | ACR1252U | Open the Reader tab and click Reader Information. The firmware text appears in the list and in the result bar. Free; no licence key needed for this tab. | No |
| ACS Script Tool 5 | ACR1252U, ACR1552U, ACR122U | Run a two-line script (below). The reply shows in Main Logs. | Place a test card so the tool connects (see the scripts) |
| ACS QuickView | All ACS PC/SC readers | Shows the reader names, card events and the card's ATR. ACS does not say that it shows the reader firmware, and BSD has not yet confirmed whether its window does. Use it to check the reader works, then use one of the methods above for the version. | For card details |
The BSD ACR1552U and ACR122U utilities do not have a Reader tab at the moment, so use the Script Tool for those two readers. How to get each tool: BSD ACR1252U NFC Card Utility (free, one-time email check), ACS Script Tool guide and ACS QuickView guide (ACS asks for a short registration form before its utility tools download).
The Get Firmware Version Command for Each Reader
ACS gives each reader its own command. Two routes exist. A pseudo-APDU (class byte FF) is sent like a normal card command with SCardTransmit, but the reader answers it itself. An escape command is sent to the reader with SCardControl and control code SCARD_CTL_CODE(3500), so it also works with no card on the reader, by connecting in direct mode.
| Reader | Command (hex) | How it is sent | Documented reply | ACS manual |
|---|---|---|---|---|
| ACR1252U | E0 00 00 18 00 | Escape command, SCardControl, code 3500 | E1 00 00 00 + length byte + version text | API v1.17, section 5.4.1 and Appendix B |
| ACR1252U (second option) | FF 00 48 00 00 | Pseudo-APDU, listed among the "ACR122U compatible commands" | Version text only | API v1.17, section 5.7.2 |
| ACR1552U | E0 00 00 18 00 | Escape command, SCardControl, code 3500 | E1 00 00 00 + length byte + version text | Reference manual v1.09, section 6.2.1 |
| ACR122U | FF 00 48 00 00 | Pseudo-APDU. With a card connected, send it with SCardTransmit. With no card, ACS says to send it as an escape command (code 3500). | 10 bytes of version text | API v2.04, section 6.3 and Appendix A |
ACR1252U
ACS's own example connects to the contactless (PICC) reader in direct mode (SCARD_SHARE_DIRECT) and sends E0 00 00 18 00 with SCardControl. The manual's example reply is E1 00 00 00 0F followed by 15 bytes that spell ACR1252U_V100.1. Appendix B shows the same command in ACS's reader tool, under its control-transmit option. The manual also lists FF 00 48 00 00 as one of its ACR122U-compatible commands. ACS shows a reply of version text only for it, with no status word.
ACR1552U
The ACR1552U uses the same escape command, E0 00 00 18 00, and the same reply layout. ACS's example reply is E1 00 00 00 14 followed by 20 bytes that spell ACR1552 R FW 1.00.00. The ACR1552U reference manual documents no FF 00 48 pseudo-APDU, so use the escape command.
ACR122U
The ACR122U uses the pseudo-APDU FF 00 48 00 00. ACS's example reply is 10 bytes, 41 43 52 31 32 32 55 32 30 31, which spell ACR122U201. The manual shows no status word after it. Sending it through the PICC reader with a card in place is the simplest route. To send it with no card, ACS's Appendix A uses the escape route, and for Windows it also describes a registry value, EscapeCommandEnable, for the reader's USB device. Changing the registry is a system change: follow ACS's manual exactly, or ask your IT administrator, and if a card-connected SCardTransmit works for you, you do not need it. Our ACR122U SDK guide explains pseudo-APDUs in more detail.
How to Read the Reply
The version arrives as hexadecimal bytes, and each byte is one ASCII character. Take ACS's ACR1252U example, E1 00 00 00 0F 41 43 52 31 32 35 32 55 5F 56 31 30 30 2E 31:
- Check the header.
E1 00 00 00means the reader accepted the escape command. The ACR122U-style pseudo-APDU has no header: its whole reply is the version text. - Read the length. The fifth byte,
0F, is 15 in decimal, so 15 bytes of text follow. On the ACR1552U example it is14, which is 20. - Turn each byte into a character. Use the table below, an ASCII table, or a hex-to-text converter.
41 43 52 31 32 35 32 55 5F 56 31 30 30 2E 31becomesACR1252U_V100.1. - Write the whole string down exactly, including the model part. That text is what ACS or BSD support will ask for.
| Hex | Character | Hex | Character | Hex | Character |
|---|---|---|---|---|---|
30–39 | 0–9 | 41 | A | 43 | C |
46 | F | 52 | R | 55 | U |
56 | V | 57 | W | 5F | _ (underscore) |
2E | . (full stop) | 20 | space | E1 | not text: reply header |
The examples above are the ones printed in ACS's manuals. Your reader will very likely show a newer number. The number format is not the same on every model: ACS writes ACR1252U firmware conditions as "110.0 and above", and ACR1552U conditions per variant, such as "ACR1552U-M FW 1.05.00 or above".
ACS Script Tool Scripts for the Firmware Version
Language: ACS Script Tool 5 script (plain text). Prerequisites: ACS PC/SC driver installed, Script Tool open with the contactless (PICC) reader chosen in the reader list, and one test card on the reader so the tool connects. Our Script Tool guide explains the format.
Not yet tested on hardware. The syntax comes from the ACS Script Tool 5 help file: [SCC] sets the control code, and [D] sends a control command to the reader. ACS's help uses E0 00 00 18 00 as its own [D] example. BSD has not yet confirmed whether the tool can send it with no card present.
ACR1252U and ACR1552U
; Get the reader firmware version (read-only). Not yet tested on hardware.
[SCC] 3500
[D] E0 00 00 18 00
Expected result: Main Logs show a reply starting E1 00 00 00, then the length byte and the version text in hex. Decode it as shown above.
ACR122U (and the ACR1252U's second option)
; Get the reader firmware version (read-only). Not yet tested on hardware.
; A card must be on the reader: this line is sent like a card command.
FF 00 48 00 00
Expected result: the version text in hex, for example 41 43 52 31 32 32 55 32 30 31 (ACR122U201) in ACS's ACR122U manual. No expected status word is written in the script, because ACS's manual shows none for this reply.
Both commands only read. Do not change the E0 or FF 00 bytes to try other values: other reader commands change settings that are saved in the reader. The Script Tool safety rules apply.
C# Example: Read the Firmware Version with SCardControl
Language: C# (.NET 8 console app, Windows). Prerequisites: ACS PC/SC driver installed; an ACR1252U or ACR1552U plugged in; the exact PC/SC reader name of its contactless (PICC) interface, for example ACS ACR1252 1S CL Reader PICC 0 as in ACS's manual (how to find your reader name). No card is needed. It sends only the read-only Get Firmware Version command.
Not yet tested on hardware. The code compiles without warnings (checked by BSD on 17 Nov 2026). It has not yet been run against a reader. For the ACR122U, use the card-connected FF 00 48 00 00 route in our ACR122U C# example instead.
// Reads the firmware version of an ACS ACR1252U or ACR1552U (read-only).
// .NET 8 console app on Windows (PC/SC through winscard.dll). Not yet tested on hardware.
using System;
using System.Runtime.InteropServices;
using System.Text;
static class Program
{
const uint SCARD_SCOPE_USER = 0;
const uint SCARD_SHARE_DIRECT = 3;
const uint SCARD_PROTOCOL_T0 = 1, SCARD_PROTOCOL_T1 = 2;
const uint SCARD_LEAVE_CARD = 0;
// SCARD_CTL_CODE(3500), written as in the ACS manuals: 0x310000 + 3500 * 4
const uint ACS_ESCAPE = 0x310000 + 3500 * 4;
[DllImport("winscard.dll")]
static extern int SCardEstablishContext(uint scope, IntPtr r1, IntPtr r2, out IntPtr context);
[DllImport("winscard.dll", EntryPoint = "SCardConnectW", CharSet = CharSet.Unicode)]
static extern int SCardConnect(IntPtr context, string reader, uint shareMode, uint protocols, out IntPtr card, out uint activeProtocol);
[DllImport("winscard.dll")]
static extern int SCardControl(IntPtr card, uint controlCode, byte[] inBuffer, int inLength, byte[] outBuffer, int outLength, out int bytesReturned);
[DllImport("winscard.dll")]
static extern int SCardDisconnect(IntPtr card, uint disposition);
[DllImport("winscard.dll")]
static extern int SCardReleaseContext(IntPtr context);
static int Main(string[] args)
{
if (args.Length != 1)
{
Console.WriteLine("Usage: fwcheck \"ACS ACR1252 1S CL Reader PICC 0\"");
return 1;
}
int rc = SCardEstablishContext(SCARD_SCOPE_USER, IntPtr.Zero, IntPtr.Zero, out IntPtr context);
if (rc != 0) { Console.WriteLine($"SCardEstablishContext failed: 0x{rc:X8}"); return 1; }
try
{
// Direct mode: talk to the reader itself, no card needed.
rc = SCardConnect(context, args[0], SCARD_SHARE_DIRECT, SCARD_PROTOCOL_T0 | SCARD_PROTOCOL_T1, out IntPtr card, out _);
if (rc != 0) { Console.WriteLine($"SCardConnect failed: 0x{rc:X8}"); return 1; }
try
{
byte[] command = { 0xE0, 0x00, 0x00, 0x18, 0x00 }; // Get Firmware Version
byte[] reply = new byte[262];
rc = SCardControl(card, ACS_ESCAPE, command, command.Length, reply, reply.Length, out int n);
if (rc != 0) { Console.WriteLine($"SCardControl failed: 0x{rc:X8}"); return 1; }
Console.WriteLine("Reply: " + BitConverter.ToString(reply, 0, n).Replace('-', ' '));
// Documented reply: E1 00 00 00, one length byte, then the version as ASCII text.
if (n >= 5 && reply[0] == 0xE1 && reply[1] == 0x00 && reply[2] == 0x00 && reply[3] == 0x00)
{
int length = Math.Min(reply[4], n - 5);
Console.WriteLine("Firmware: " + Encoding.ASCII.GetString(reply, 5, length));
return 0;
}
Console.WriteLine("Unexpected reply. Compare it with your reader's ACS manual.");
return 1;
}
finally { SCardDisconnect(card, SCARD_LEAVE_CARD); }
}
finally { SCardReleaseContext(context); }
}
}
Expected result: two lines, for example Reply: E1 00 00 00 0F 41 43 ... and Firmware: ACR1252U_V... with your reader's real version.
If it fails: SCardConnect failed: 0x80100009 (unknown reader) means the reader name is not exactly right; copy it from QuickView. SCardControl failed usually means the command did not reach the reader's escape interface: check that the ACS driver, not only Windows' built-in driver, is installed, and that you used the PICC entry. Other codes are explained in our PC/SC error code table. For the full PC/SC call order, see the ACR1252U SDK guide and the ACR1552U SDK guide.
Why the Firmware Version Matters
ACS's manuals mark several commands as available only from a certain firmware version. If a documented command fails on your reader, compare its firmware with the condition below before you suspect your code or the card.
| Reader | Feature in the ACS manual | Firmware needed (as ACS writes it) |
|---|---|---|
| ACR1252U | Get PICC Data, FF CA 00 02 00 (ATQA + UID + SAK of a Type A card) | 110.0 and above |
| ACR1252U | Set / Read PICC Operating Parameter (Extended); Read PICC Type | 110.0 and above |
| ACR1252U | Automatic PICC Polling, bit 6 option ("NXP MIFARE ISO/IEC 14443 PICC Selection") | 111.1 and above |
| ACR1552U | Pass-through commands to ISO 15693 tags | ACR1552U-M FW 1.03.00; ACM1552U-Y / -Z FW 2.03.00 |
| ACR1552U | Get / Set RF power setting | ACR1552U-M FW 1.03.03; ACM1552U-Y / -Z FW 2.03.03 |
| ACR1552U | Pass-through commands to ISO 14443-3 tags; selective suspend setting; output order 02h and 04h of the keyboard output format | ACR1552U-M FW 1.05.00; ACR1552U-A FW 5.01.00; ACM1552U-Y / -Z FW 2.05.00 |
| ACR1552U | Retry counter data object; on-screen keyboard setting | ACR1552U-M FW 1.06.00; ACR1552U-A FW 5.02.00; ACM1552U-Y / -Z FW 2.06.00 |
| ACR1552U | Extra UI behaviour bits (1, 2, 5, 6 and 7) | ACR1552U-M FW 1.06.00; ACM1552U-Y / -Z FW 2.06.00 |
| ACR122U | No firmware conditions in the API manual v2.04 | – |
Two practical points follow. First, the version is part of every good support request. When you contact ACS or BSD about a reader problem, give the full firmware text with the model, the driver version and the Windows version; it saves a round of questions. Second, an older firmware is not a fault in itself. If the features you use do not appear in the table, a reader on older firmware can be perfectly fine. For model-level differences, see the ACR1252U, ACR1552U and ACR122U pages.
Can You Upgrade ACS Reader Firmware?
What ACS offers (checked 17 Nov 2026)
| Reader | What ACS says about upgrades | Upgrade file or tool on ACS's public pages? |
|---|---|---|
| ACR1252U | The product page says post-deployment firmware upgrade is supported without hardware changes; the API manual lists "USB Firmware Upgradeability". | No. The ACR1252U download page lists drivers, Android EVK, the iOS ApduTool and manuals only. |
| ACR1552U | The product page and the reference manual list "USB firmware upgradability". | No. The ACR1552U download page lists drivers, the Configuration Tool, Android EVK, the iOS ApduTool and manuals only. |
| ACR122U | No firmware upgrade feature in the API manual v2.04. ACS marks the reader end of life. | No. The ACR122U download page lists drivers, Android EVK and manuals only. |
The ACS utility tools page lists no firmware upgrade tool either. In short: the ACR1252U and ACR1552U are built so that their firmware can be upgraded over USB, but ACS does not publish a do-it-yourself upgrade kit for them. If you need a newer firmware, the route is through ACS (its technical enquiry page) or through your ACS supplier. BSD Infotech can raise the request for readers it supplied.
Safety rules before any firmware upgrade
- Only official ACS files and ACS tools. Use only firmware and an upgrade program that ACS itself provides for your exact model and variant, for example ACR1552U-M versus ACR1552U-A. Never use firmware files from forums, file-sharing sites or other products, and never use modified firmware. A wrong image can leave the reader unusable.
- Do not upgrade a working production reader without a reason. Upgrade only when ACS or BSD confirms that the new firmware fixes your problem or adds a feature you need, such as one in the table above. "There is a newer version" alone is not a reason.
- Ask ACS or BSD first. Send the current firmware text, the model and variant, the driver version and what you want to achieve, and follow the procedure they send you.
- Test on one spare reader first, then check your own software with it before you touch the other readers.
- Do not unplug the reader, close the program or let the PC sleep during an upgrade. Use a direct USB port on a desktop or a laptop on mains power, not a hub, and close other programs that use the reader.
- Record the version before and after. Read it with one of the methods on this page, keep both in your asset list, and check that your application still works.
BSD Infotech has not run a firmware upgrade on any of these readers and does not give step-by-step upgrade instructions on this page. If ACS provides you with an upgrade procedure, follow ACS's instructions exactly.
Firmware Version Check: Problems and Fixes
| What you see | Likely cause | What to do |
|---|---|---|
| The BSD utility's Reader Information button says the reader refused the command | The escape command is not reaching the reader, often because only Windows' built-in driver is in use | Install the ACS PC/SC driver (ACR1252U driver guide), unplug and replug the reader, and try again. |
Script Tool shows an error on the [D] line | Control code not set, wrong reader chosen, or no connection to the reader | Keep [SCC] 3500 as the line before [D], choose the PICC reader, and place a test card so the tool connects. |
An error status word, or no version text, in reply to FF 00 48 00 00 on an ACR1552U | The ACR1552U documents the firmware command only as an escape command | Use [SCC] 3500 and [D] E0 00 00 18 00 instead. |
ACR122U: no reply to FF 00 48 00 00 when no card is on the reader | Without a card the command must go as an escape command, which ACS says needs extra setup on Windows | Place a card and send it as a normal command, or follow ACS's Appendix A with your IT administrator. |
| The reply is bytes, not readable text | The version is ASCII in hex | Skip the E1 00 00 00 header and the length byte, then decode the rest (see How to read the reply). |
SCardConnect fails with the reader name | The name does not match exactly, or the SAM entry was chosen | Copy the PICC reader name from QuickView or from the reader list check. |
| The reader is not listed at all | Driver, USB or Smart Card service problem | Work through driver installation errors and reader detection checks first. |
Sources
Commands, reply formats and firmware conditions come from these official ACS manuals: ACR1252U Application Programming Interface v1.17 (sections 2.0, 5.1.8, 5.2.2.2, 5.4.1, 5.4.7, 5.4.11, 5.4.12, 5.4.16, 5.7.2, Appendix B); ACR1552U Series Reference Manual v1.09 (sections 2.0, 5.3.4, 5.3.5.4.5, 6.1.10, 6.1.14, 6.2.1, 6.2.9); ACR122U Application Programming Interface v2.04 (sections 6.0, 6.3, Appendix A); and the ACS Script Tool 5 help file ([SCC] and control command syntax). ACS web pages checked on 17 Nov 2026:
- ACS ACR1252U product page (post-deployment firmware upgrade)
- ACS ACR1552U product page (USB firmware upgradability)
- ACS ACR1252U drivers and manuals, ACR1552U drivers and manuals, ACR122U drivers and manuals
- ACS utility tools
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.
