Get the Current Setting of the Contactless Interface............30 Appendix A. ACR122U PC/SC Escape Command ............31 Appendix B. APDU Command and Response Flow for ISO 14443-Compliant Tags.. 33 Appendix C. APDU Command and Response Flow for ISO 18092-Compliant Tags.. 34 ...
Page 3
Current LED State (1 Byte) ....................19 Table 5: PICC Operating Parameter. Default Value = FF ..............21 Table 6: Page 3 of 38 info@acs.com.hk ACR122U NFC Reader API Document Title Here Document Title Here Document Title Here Version 2.00 www.acs.com.hk...
The ACR122U is a PC-linked contactless smart card reader/writer used for accessing ISO 1444 3-4 Type A and Type B, Mifare, ISO 18092 or NFC, and FeliCa tags. The ACR122U is PC/SC compliant so it is compatible with existing PC/SC appli cations. Furthermore, the standard Microsoft CCID driver is used to simplify driver installation.
2.1. Communication Flow Chart of ACR122U The Standard Micro soft CCID and PC/SC drivers ar e used; thus, no ACS drivers are required because the drivers are al ready built in side the wi ndows operating system. you’re the computer’s registry settings can also be modified to be able to use the full capabilitie s of the ACR122 U NFC Reader.
00 26: MiFare Mini …. F0 04: Topaz and Jewel F0 11: FeliCa 212K F0 12: Felica 424K …FF [SAK]: Undefined Page 6 of 38 info@acs.com.hk ACR122U NFC Reader API Document Title Here Document Title Here Document Title Here Version 2.00 www.acs.com.hk...
12 bytes long with no CRC-B Note: You can refer to the ISO7816, ISO14443 and PC/SC standards for more details. Page 7 of 38 info@acs.com.hk ACR122U NFC Reader API Document Title Here Document Title Here Document Title Here Version 2.00...
UINT8 GET_UID[5]={0xFF, 0xCA, 0x00, 0x00, 0x04}; 2. To get the ATS of the “connected ISO 14443 A PICC” UINT8 GET_ATS[5]={0xFF, 0xCA, 0x01, 0x00, 0x04}; Page 8 of 38 info@acs.com.hk ACR122U NFC Reader API Document Title Here Document Title Here Document Title Here Version 2.00...
{FF FF FF FF FF FF} into the key location 0x00. APDU = {FF 82 00 00 06 FF FF FF FF FF Page 9 of 38 info@acs.com.hk ACR122U NFC Reader API Document Title Here Document Title Here Document Title Here Version 2.00 www.acs.com.hk...
Response Data Out Result Response Codes Results Meaning Success The operation is completed successfully. Error The operation is failed. Page 10 of 38 info@acs.com.hk ACR122U NFC Reader API Document Title Here Document Title Here Document Title Here Version 2.00 www.acs.com.hk...
Page 11
Data35 Data read/write Data36 Data37 Data38 Data39 Data read/write Data40 Data41 Data42 Data43 Data read/write Data44 Data45 Data46 Data47 Page 11 of 38 info@acs.com.hk ACR122U NFC Reader API Document Title Here Document Title Here Document Title Here Version 2.00 www.acs.com.hk...
Page 12
= {FF 86 00 00 05 01 00 60 00} Note: Mifare Ultralight does not need to do any authentication. The memory is free to access. Page 12 of 38 info@acs.com.hk ACR122U NFC Reader API Document Title Here Document Title Here Document Title Here Version 2.00 www.acs.com.hk...
3. Read 16 bytes starting from the binary Page (Mifare Ultralight) (Pages 4, 5, 6 and 7 will 0x04 be read) APDU = {FF B0 00 Page 13 of 38 info@acs.com.hk ACR122U NFC Reader API Document Title Here Document Title Here Document Title Here Version 2.00 www.acs.com.hk...
Value Block Operation APDU Format (10 Bytes) Command Class Data In VB_Value Value Block (4 Bytes) Block VB_OP Number {MSB .. Operation LSB} Page 14 of 38 info@acs.com.hk ACR122U NFC Reader API Document Title Here Document Title Here Document Title Here Version 2.00 www.acs.com.hk...
Where: Value: 4 Bytes. The valu e returned from the card. The value is a signe d long intege r (4 Page 15 of 38 info@acs.com.hk ACR122U NFC Reader API Document Title Here Document Title Here Document Title Here Version 2.00...
1. Store a value “1” into block 0x05 APDU = {FF D7 00 00 00 01} Answer: 90 00 Page 16 of 38 info@acs.com.hk ACR122U NFC Reader API Document Title Here Document Title Here Document Title Here Version 2.00 www.acs.com.hk...
Page 17
4. Increment the value block by “5” 0x05 APDU = {FF D7 00 00 00 05} Answer: 90 00 [9000] Page 17 of 38 info@acs.com.hk ACR122U NFC Reader API Document Title Here Document Title Here Document Title Here Version 2.00 www.acs.com.hk...
Retrieving and setting the reader parameters. The Pseudo-APDUs can be sent through the “ACR122U PICC Interface” if the tag is already connected. Or the Pseudo-APDUs can be sent by using “Escape Command” if the tag is not presented yet.
Page 19
F. The make the buzzer operating, the “number of repetition” must greater than zero. G. To control the LED only, just set the parameter “Link to Buzzer” to zero. Page 19 of 38 info@acs.com.hk ACR122U NFC Reader API Document Title Here Document Title Here Document Title Here Version 2.00...
To set the time interval between 1 = 250 ms Polling Interval successive PICC Polling. 0 = 500 ms Page 20 of 38 info@acs.com.hk ACR122U NFC Reader API Document Title Here Document Title Here Document Title Here Version 2.00 www.acs.com.hk...
Page 21
Auto AT 0 = Skip Generation must be disabled first. PICC Operating Parameter. (Default Value = FF) Table 6: Page 21 of 38 info@acs.com.hk ACR122U NFC Reader API Document Title Here Document Title Here Document Title Here Version 2.00 www.acs.com.hk...
Once the tag is found and detected, the corresponding ATR will be sent to the P C. You must make sure that the PC/SC Escape Command has been set. See Appendix A for more details. Step 1. The first thing is to connect the “ACR122U PICC Interface”. Step 2. Access the PICC by sending APDU commands.
Basically, all ISO 14443-4 compliant ca rds (PICCs) would understand the ISO 7816-4 APDUs. The ACR122U Reader just has to communicate with the ISO 14443-4 compliant cards through exchanging ISO 7816-4 APDUs and Responses. ACR122U will handle the ISO 14443 Parts 1-4 Protocols internally.
Page 24
Tip: If the authentication failed, the error code [XX] will be returned. [00] = Valid, other = Error. Please refer to Error Codes Table Page 24 of 38 info@acs.com.hk ACR122U NFC Reader API Document Title Here Document Title Here Document Title Here Version 2.00...
Page 25
Tip: For KEY B Authentication << FF 00 00 00 0F D4 40 FF FF FF FF FF FF 03 04 05 06 Page 25 of 38 info@acs.com.hk ACR122U NFC Reader API Document Title Here Document Title Here Document Title Here Version 2.00 www.acs.com.hk...
Step 3: Send an APDU {AF} to get the last frame. INS=0xAF Answer: 00 04 52 5A 19 B2 1B 80 8E 36 54 4D 40 26 04[$2604] Page 26 of 38 info@acs.com.hk ACR122U NFC Reader API Document Title Here Document Title Here Document Title Here Version 2.00...
Step 2) Read the memory address (Block 1: Byte-0) without using Pseudo APDU << 01 >> [90 00] In which, Response Data = Page 27 of 38 info@acs.com.hk ACR122U NFC Reader API Document Title Here Document Title Here Document Title Here Version 2.00 www.acs.com.hk...
Page 28
Step 3) Update the memory address 08(Block 1: Byte-0)with the data << 53 >> FF [90 00] In which, Response Data = FF Page 28 of 38 info@acs.com.hk ACR122U NFC Reader API Document Title Here Document Title Here Document Title Here Version 2.00 www.acs.com.hk...
Page 29
Memory Address 10 (hex) = 2 x 8 + 0 = Block 2: Byte-0 = Data8 Please refer to the Jewel and Topaz specification for more detailed information. Page 29 of 38 info@acs.com.hk ACR122U NFC Reader API Document Title Here Document Title Here Document Title Here Version 2.00...
0x00 : ISO14443 or Mifare® 0x10 : FeliCa™ 0x01 : Active mode 0x02 : Innovision Jewel® tag Page 30 of 38 info@acs.com.hk ACR122U NFC Reader API Document Title Here Document Title Here Document Title Here Version 2.00 www.acs.com.hk...
2. Select the “Shared Mode” if the “ACR122U PICC Interface” is already connected, or “Direct Mode” if the “ACR122U PICC Interface” is not connected. 3. Press the Connect button to establish a connection between the PC and the ACR122U reader. 4. Enter “3500” in the Command Text Box 5.
Page 32
EscapeCommandEnable double click on the entry and input 1 in the Value data with the base set in Hexadecimal. Page 32 of 38 info@acs.com.hk ACR122U NFC Reader API Document Title Here Document Title Here Document Title Here Version 2.00 www.acs.com.hk...
Frame [APDU [APDU Response] Response] embedded in e.g. [11 22 ISO14443 33 44 55 66 Frame 77 88] (90 Page 33 of 38 info@acs.com.hk ACR122U NFC Reader API Document Title Here Document Title Here Document Title Here Version 2.00 www.acs.com.hk...
00 (90 00) ISO18092 Frame Pseudo APDU Response + [Native Response] e.g. D5 41 00 [00] (90 00) Page 34 of 38 info@acs.com.hk ACR122U NFC Reader API Document Title Here Document Title Here Document Title Here Version 2.00 www.acs.com.hk...
Mismatch between the NFCID3 initiat or and the NFCID3 target in DEP 0x2C 212/424 kbps passive. An over-current event has been detected 0x2D NAD missing in DEP frame 0x2E Page 35 of 38 info@acs.com.hk ACR122U NFC Reader API Document Title Here Document Title Here Document Title Here Version 2.00 www.acs.com.hk...
T2 = 0ms T1 = 2000ms Red LED Off Green LED On Green LED Off Buzzer On Buzzer Off Page 36 of 38 info@acs.com.hk ACR122U NFC Reader API Document Title Here Document Title Here Document Title Here Version 2.00 www.acs.com.hk...
Page 37
Red LED Off T1 = T2 = 500ms 500ms Green LED On Green LED Off Buzzer On Buzzer Off Page 37 of 38 info@acs.com.hk ACR122U NFC Reader API Document Title Here Document Title Here Document Title Here Version 2.00 www.acs.com.hk...
Page 38
Link to Buzzer = 0x01 APDU = “FF 00 40 D0 04 05 05 03 01”; Response = “90 00” Page 38 of 38 info@acs.com.hk ACR122U NFC Reader API Document Title Here Document Title Here Document Title Here Version 2.00...
Need help?
Do you have a question about the ACR122U and is the answer not in the manual?
Questions and answers