Using an ACS Reader in Keyboard Emulation Mode (UID Typing)

Can an ACS reader type a card number like a keyboard? Yes, on the readers ACS builds for it. In keyboard emulation mode an ACS reader such as the ACR1552U reads the UID of a contactless card and types it into whichever program has the cursor, followed by Enter if you set one. You switch the mode on with ACS's free ACR15XX Keyboard Configuration Tool for Windows. The ACR1252U and ACR122U do not have this mode.

This guide covers when keyboard mode is the right choice and when PC/SC software is better, which ACS readers support it, how to set it up with the ACS tool, the output settings ACS documents, how to switch the reader back to PC/SC mode, and how to fix the usual problems. BSD Infotech is an independent ACS supplier and integrator, not the manufacturer; the ACS tool comes from acs.com.hk.

Not yet tested by BSD. Everything on this page comes from ACS's published pages and the ACR1552U Series Reference Manual. We have not yet run keyboard mode on our own ACR1552U or ACR1581U. We will add our results and screenshots after our hardware test.

A normal ACS NFC reader is a PC/SC reader. Windows lists it under "Smart card readers", and nothing happens when you tap a card until a program (QuickView, a BSD utility, your own software) connects to the reader and sends commands. That gives software full control, but it means every PC needs that software.

In keyboard emulation mode the reader works the other way round. It tells Windows it is a USB keyboard. When a card is tapped, the reader itself reads the card's UID (its serial number) and "types" it as a string of key presses, exactly as if someone had typed the number. Notepad, Excel, a browser form, a login screen field or an existing attendance program all receive it without any driver, plug-in or code. People also call this a keyboard wedge or UID typing.

ACS describes this mode for the UIDs of ISO 14443 Type A and Type B cards, such as MIFARE Classic, MIFARE Ultralight, NTAG and DESFire. The reader only types the UID. It does not read sectors, files or NDEF records, and it cannot write to the card.

What a UID is, why one card can show different numbers, and how hex and decimal relate are explained in our guide to reading an NFC card UID with an ACS reader. This page does not repeat that; it is about the keyboard mode itself.

Keyboard mode is the quickest way to put card numbers into software that already has a text box for them. It is the wrong tool when the card's content matters, or when the input must be trusted.

QuestionKeyboard emulation modePC/SC mode with software
Software needed on the PCNone. Any program with a text field.A program that talks to the reader (ACS tool, BSD utility or your own).
What it readsThe card UID onlyUID, card type, data blocks, files, NDEF; with the right keys
Write to the cardNoYes, where the card and keys allow it
Where the number goesInto whichever window has the cursor, even the wrong oneOnly to the program that is connected to the reader
Card removed / present eventsNot availableAvailable
Typed by hand or tapped?The program cannot tell the differenceThe program knows a reader read it
Web applicationsWorks in any browser formBrowsers cannot talk to PC/SC directly; needs a helper program or extension
SecurityUID only, which is not a secret and can be copiedCan authenticate with keys (MIFARE, DESFire)

Good fits for keyboard mode

  • Attendance and canteen software that already has an "employee card number" box and just needs the number typed in, followed by Enter.
  • Web forms and cloud software (HR, library, visitor or membership systems) where you cannot install anything on the PC.
  • Enrolment: tapping a batch of new cards into an Excel sheet to record their numbers before issuing them.
  • Quick checks: confirming a card has a readable UID without installing any tool.

Use PC/SC software instead when

  • you need data stored on the card (balance, employee ID in a sector, DESFire files), or need to write to it;
  • the card number must be trusted, for example for payments or door access, because a UID can be typed by hand or copied;
  • your cards use a random UID (some DESFire and MIFARE Plus cards give a new number on every tap);
  • the PC is used for other work at the same time and stray card numbers in the wrong window would be a problem;
  • you want to control the reader's LED or buzzer, or several readers on one PC.

For those cases, BSD Infotech's free Default Key utilities and ACS's own tools work in PC/SC mode; see the BSD reader utilities. If your existing software needs something in between (for example a small program that reads a sector and types it), that is the kind of integration we build on request.

Checked on the official ACS pages on 17 Nov 2026. "Listed by ACS" means ACS names the reader for the keyboard tool; it does not mean BSD has tested it.

ACS readerKeyboard emulationEvidence (ACS)BSD status
ACR1552U (USB NFC Reader IV)YesProduct page lists keyboard emulation as one of its three NFC modes; download page has the Configuration Tool "for UID keyboard emulation mode only"; reference manual documents the settingsNot yet tested by BSD (reader on our bench)
ACR1581U (DualBoost III)Yes, per ACSProduct page lists keyboard emulation "configured by this tool"; download page has the same Configuration Tool; listed on the utility tools pageNot yet tested by BSD (reader on our bench)
ACR1555U-A1Yes, per ACS (including over Bluetooth)Listed for the keyboard tool; product page lists keyboard emulation modeNot on our test bench
AquaGuard, WalletMate II seriesListed by ACSListed for the keyboard toolNot on our test bench
ACR1281U-C2 Card UID ReaderKeyboard output onlyA dedicated UID reader with its own ACR1281U-C2 Configuration Tool; it is not a PC/SC readerNot on our test bench
ACR1252UNoNot listed for the keyboard tool; no keyboard mode on its product page or in its API manualUse PC/SC software
ACR122UNoNot listed for the keyboard tool; no keyboard mode on its product page or in its API manualUse PC/SC software

If you already own an ACR1252U or ACR122U and need card numbers typed into another program, the reader cannot do it on its own. You need a small PC/SC program that reads the UID and passes it on, or a reader from the list above.

ACS's tool is called the ACS ACR15XX Keyboard Configuration Tool on its utility tools page and simply Configuration Tool on the ACR1552U and ACR1581U download pages. According to ACS, it puts the reader into keyboard emulation mode and saves the settings to the reader over USB.

ItemAs listed by ACS (checked 17 Nov 2026)
Current versionVersion 207, dated 27 Oct 2025, 567.78 KB (ACR1552U and ACR1581U download pages). The ACR1552U SDK kit also includes a Keyboard Configuration Tool (ACR1552U SDK user manual v1.01), and the ACR1552U product page still names "Keyboard Configuration Tool V100", so the download page is the place to get the current version.
Operating systemWindows
CardsISO 14443 Type A and B (Parts 1 to 4)
Where to get itThe ACS utility tools page, or the Drivers & Utilities list on the ACR1552U download page and the ACR1581U download page (acs.com.hk, opens in a new tab).
RegistrationOn the utility tools page, ACS asks for a short registration (name, company, country and email) before the download.

BSD Infotech does not host or redistribute the tool. Always download the version ACS shows on the day, because ACS replaces files when it updates them.

These steps follow ACS's description of the tool and the settings in the ACR1552U reference manual. Screen names may differ slightly between tool versions. For the ACR1552U, the short version is also in our ACR1552U driver and software guide.

  1. Connect the reader and check Windows sees it. Plug the ACR1552U or ACR1581U into a USB port on a Windows 10 or 11 PC. Out of the box the reader is in PC/SC mode (the manual gives "CCID reader only" as the default), so it should appear under "Smart card readers" in Device Manager. If it does not, see how to check an ACS reader is detected and install the ACS driver first.
  2. Download the Configuration Tool from ACS. Use one of the links in the table above, complete ACS's registration if asked, and unzip the file into a folder of its own.
  3. Run the tool with the reader plugged in. Close any other program that is using the reader (QuickView, a BSD utility, attendance software), so the tool can reach it.
  4. Choose keyboard output. Set the reader to keyboard emulation. The manual documents three interface settings: keyboard only, PC/SC (CCID) only, and keyboard plus PC/SC. Choose keyboard only for a dedicated attendance or enrolment PC; choose keyboard plus PC/SC if you also want PC/SC tools to keep working, where your tool version offers it.
  5. Choose the number format. Set the display mode (hex or decimal), the byte order, the UID length option and the letter case. If the number must match an existing system, see the output settings below before you pick.
  6. Set what is typed after the number. Most attendance and web forms need an Enter at the end, so the record is saved without a mouse click. Leave the start and between characters empty unless your software expects them.
  7. Match the keyboard layout. Leave it on English unless Windows on that PC uses a French (AZERTY) or Lithuanian keyboard layout.
  8. Save the settings to the reader. ACS says the tool saves the settings to the device. If Windows does not pick up the change, unplug the reader and plug it in again.
  9. Test in Notepad. Open Notepad, click inside it and tap a card. You should see the number appear as typed text, followed by a new line if you set Enter. Tap the same card three times: the number should be identical each time.
  10. Test in your real software. Click in the card-number field and tap the card. Compare the result with the number your system already holds for that card. If it differs, change the format, not the card.

Not yet tested by BSD: the exact screens of Configuration Tool version 207, whether every setting in the manual appears in the tool, and whether the settings survive unplugging the reader. We will confirm these on our ACR1552U and ACR1581U.

The ACR1552U Series Reference Manual (version 1.09, from the ACS ACR1552U download page) lists the keyboard-mode settings below. They decide which number the reader types for the same card, so check them first whenever two systems disagree. The ACR1581U uses the same tool, but we have taken these settings from the ACR1552U manual only.

SettingOptions in the manualWhat it changes
Display modeHex; decimal; decimal byte by byte; fixed-length formats named 6H-6H, 8H-8H, 10H-10H, 14H-14H, 20H-20H, 6H-8D, 6H-10D, 8H-10D, 10H-14D, 2H4H-8D and 14H-17DHex or decimal, and how many digits are typed
Output orderDefault (UID byte 0 first, as the card sends it) or reverse (last byte first). Newer firmware adds "reverse ISO 14443 and FeliCa only" and "reverse ISO 15693 only"Byte order, the usual cause of a "wrong" number
UID length4-byte UIDs only, or 4, 7, 8 and 10-byte UIDsHow cards with longer UIDs are handled
Letter caseUpper or lower caseHex letters A to F, for example A1B2 or a1b2
Start, between and end charactersOne key each, or noneA prefix, a separator between bytes, and a suffix such as Enter or Tab
Keyboard layoutEnglish (default), French, LithuanianWhich key presses the reader sends for each character
Host interfaceKeyboard only; CCID (PC/SC) reader only (default); keyboard plus CCIDWhether PC/SC software can still see the reader
On-screen keyboardDisable (default) or enable the keyboard pop-upWhether a tablet's touch keyboard pops up; newer firmware only

The manual gives firmware minimums for the newer options: for the per-card-type reverse orders, ACR1552U-M firmware 1.05.00 or later and ACR1552U-A firmware 5.01.00 or later; for the on-screen keyboard setting, 1.06.00 and 5.02.00. On older firmware those options may be missing. The manual also notes that USB selective suspend (power saving) cannot be on while the reader is in keyboard mode.

Which format should you choose?

Choose the format your existing system already stores, not the one that looks nicest. The explanation of hex versus decimal, byte order and leading zeros, with worked examples, is in the byte order and decimal section of our UID guide. In short:

  • If your system shows the card number with letters A to F, use hex, and try default order first.
  • If it shows a number of digits only, use a decimal mode, and try both byte orders with one card you already know the number of.
  • If your cards have 7-byte UIDs but the system was built for 4-byte cards, look at the 4-byte UID only option and the fixed-length formats, and test with a real card before rolling out.

The format we meet most often

In the attendance, access and membership projects where BSD Infotech connects ACS readers, the most common card number is the 10-digit decimal number made from a 4-byte UID, with leading zeros kept. By its name, the 8H-10D format (8 hex digits in, 10 decimal digits out) looks like that number, but the manual does not define the fixed-length formats in words, so compare it with your system's number for one known card before you rely on it.

For developers: the same settings as escape commands

The manual also documents these settings as reader escape commands (class E0), sent with SCardControl while the reader is visible in PC/SC mode. This is useful if your own software has to set up many readers the same way. Each "set" command has a matching "get" command with 00 as the last byte.

SettingSet command (ACR1552U manual v1.09)Data bytes
Output format and orderE0 00 00 90 02 [format] [order]Format: upper half = case and UID length bits, lower half = display mode (0 hex, 1 decimal byte by byte, 2 decimal, 3 to D the fixed formats). Order: 00 default, 01 reverse
Start, between, end charactersE0 00 00 91 03 [between] [end] [start]A USB keyboard key code each, or FF for none. In the USB key-code tables Enter is 28 and Tab is 2B
Keyboard layoutE0 00 00 92 01 [layout]00 English, 01 French, 03 Lithuanian
Host interfaceE0 00 00 93 01 [interface]00 keyboard only, 01 CCID only, 02 keyboard plus CCID

Not yet tested on hardware. Copied from the manual's command tables, not run on a reader by BSD. Note the byte order of the character command (between, end, start). How to send an escape command from C# is shown on our ACR1552U SDK page. Once a reader is set to keyboard only, PC/SC software can no longer reach it to send these commands; use the ACS Configuration Tool to change it back.

You need PC/SC mode again for ACS QuickView, the ACS Script Tool, BSD Infotech's utilities, the ACS SDK and any software that reads card data. If a reader set to keyboard only is plugged in, those programs report no reader at all, which is easy to mistake for a driver fault.

  1. Open the ACS Configuration Tool with the reader plugged in.
  2. Set the interface back to the PC/SC (CCID) reader (the factory default per the manual), or to keyboard plus PC/SC if you want both and your tool version offers it.
  3. Save to the reader, then unplug it and plug it in again.
  4. Check Windows. The reader should be back under "Smart card readers" in Device Manager. Then open ACS QuickView and tap a card to confirm PC/SC works; our NFC reader test guide for Windows has the full check.

If several people share readers, label any reader left in keyboard mode. It saves a lot of time when someone later tries to use it with PC/SC software.

Not yet tested by BSD: the switch-back steps on Configuration Tool version 207, and how the reader appears in Device Manager in each interface setting.

What you seeLikely causeWhat to do
Nothing is typed when you tap a cardThe reader is still in PC/SC mode (the default), or the settings were not savedRun the Configuration Tool again, set keyboard output, save, then unplug and replug the reader.
Nothing is typed, reader mode is correctThe cursor is not in a text field, or the card is not ISO 14443 (for example an ISO 15693 library tag)Click inside Notepad and try a MIFARE or NTAG card. ACS lists ISO 14443 Type A and B cards for this mode.
The tool does not find the readerAnother program has the reader open, or the reader is not an ACR15XX modelClose QuickView, BSD utilities and attendance software; check the model on the reader's label against the table above.
Digits are typed, but not the number your system expectsDifferent byte order, hex instead of decimal, or leading zerosChange the output order or display mode, testing with one card whose number you know. See the byte order and decimal explanation.
Symbols such as & é " ' instead of digits, or A and Q swappedThe reader's keyboard layout setting does not match the Windows keyboard layout (on a French AZERTY layout, digits need Shift)Set the reader's layout to match Windows, or switch Windows to the layout the reader is set for.
The number appears but the form does not submitNo end character setSet Enter as the end character, or Tab if the form needs to move to the next field.
The form submits twice or skips a fieldThe software already adds its own Enter or Tab after a scanSet the end character to none.
Long numbers for some cards, short for othersA mix of 4-byte and 7-byte UID cardsUse one card type, or set the UID length and fixed-length format your system needs.
A different number on every tap of the same cardThe card uses a random UID (privacy feature on some DESFire and MIFARE Plus cards)Keyboard mode cannot identify these cards. Use cards with a fixed UID, or PC/SC software that reads a stored ID with the card's key.
Card numbers end up in the wrong windowKeyboard output always goes to the focused windowKeep the entry program in front (kiosk mode), or use PC/SC software if the PC is shared.
QuickView, the ACS SDK or BSD utilities say no reader is connectedThe reader is set to keyboard onlySwitch it back to PC/SC mode.
A touch keyboard pops up on a tablet at each tapThe reader's on-screen keyboard setting (newer firmware)Disable the keyboard pop-up setting, if your firmware and tool offer it.

Not yet tested by BSD: these causes are based on ACS's documentation and general USB keyboard behaviour in Windows, not on our own test results yet.

Tool names, versions, supported readers and cards were checked on the official ACS pages on 17 Nov 2026:

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.

Want card taps to land in your software?

Tell us your reader, your cards and the program the card number must reach. BSD Infotech supplies ACS readers and cards and sets up keyboard mode or builds PC/SC software to match.