Appendix E. Sample Codes for Setting the LED ....................35 Figures Figure 1: AET 62 System Block Diagramm ........................... 4 Figure 2: Communication Flow Chart of AET62 ........................6 Figure 3: Basic Program Flow for Contactless Applications ....................22 Tables Table 1: USB Interface ................................
Figure 1: AET 62 System Block Diagramm The purpose of this document is to describe the architecture and interface of AET62’s contactless smart card reader module, which is based on the ACR122U core. For information on the architecture and programming interface of the fingerprint module, please refer to the AET62 Fingerprint Reader Application Programming Interface document (API_AET62_v1.0).
AET62 in your smart card system. 2.1. USB Interface The AET62 is connected to a computer through USB as specified in the USB Specification 1.1. The AET62 is working in Full speed mode, i.e. 12 Mbps. Signal...
Figure 2: Communication Flow Chart of AET62 3.2. Smart Card Reader Interface Overview Just click the “Device Manager” to find out the “AET62 PICC Interface”. The standard Microsoft USB CCID Driver is used. Page 6 of 37 idvation GmbH Otto-Hesse-Straße 19 / T5...
AET62 Reference Manual Version 1.0 PICC Interface Description 4.1. ATR Generation If the reader detects a PICC, an ATR will be sent to the PCSC driver to identify the PICC. ATR format for ISO 14443 Part 3 PICCs 4.1.1. Value...
AET62 Reference Manual Version 1.0 ATR format for ISO 14443 Part 4 PICCs 4.1.2. Value Byte Designation Description (Hex) Initial Header Higher nibble 8 means: no TA1, TB1, TC1 only TD1 is following. Lower nibble N is the number of historical bytes (HistByte 0 to HistByte N-1) Higher nibble 8 means: no TA2, TB2, TC2 only TD2 is following.
AET62 Reference Manual Version 1.0 PICC Commands for General Purposes 5.1. Get Data The “Get Data command” will return the serial number or ATS of the “connected PICC”. Version 1.00 Command Class Get Data 00 01 (Full Length) Table 4: Get UID APDU Format (5 Bytes)
AET62 Reference Manual Version 1.0 Memory Cards PICC Commands (T=CL Emulation) for Mifare Classic 6.1. Load Authentication Keys The “Load Authentication Keys command” will load the authentication keys into the reader. The authentication keys are used to authenticate the particular sector of the Mifare 1K/4K Memory Card. Two kinds of authentication key locations are provided, volatile and non-volatile key locations respectively.
AET62 Reference Manual Version 1.0 6.2. Authentication The “Authentication command” uses the keys stored in the reader to execute authentication with the Mifare 1K/4K card (PICC). Two types of authentication keys are used: TYPE_A and TYPE_B. Command Class Data In...
Page 12
AET62 Reference Manual Version 1.0 Mifare 1K Memory Map. Sectors Data Blocks Trailer Block (Total 16 sectors. Each sector (3 blocks, 16 bytes per (1 block, 16 bytes) consists of 4 consecutive blocks) block) Sector 0 0x00 ~ 0x02 0x03...
Page 13
AET62 Reference Manual Version 1.0 Example: 1. To authenticate the Block with a {TYPE A, key number 0x00}. For PC/SC V2.01, Obsolete. 0x04 APDU = {FF 88 00 60 00}; 2. To authenticate the Block with a {TYPE A, key number 0x00}. For PC/SC V2.07...
AET62 Reference Manual Version 1.0 6.3. Read Binary Blocks The “Read Binary Blocks command” is used for retrieving “data blocks” from the PICC. The data block/trailer block must be authenticated first. Command Class Read Binary Blocks Block Number Number of Bytes to Read...
AET62 Reference Manual Version 1.0 6.4. Update Binary Blocks The “Update Binary Blocks command” is used for writing “data blocks” into the PICC. The data block/trailer block must be authenticated. Command Class Data In Update Block Number Number Block Data...
AET62 Reference Manual Version 1.0 6.5. Value Block Related Commands The data block can be used as value block for implementing value-based applications. Value Block Operation 6.5.1. The “Value Block Operation command” is used for manipulating value-based transactions. E.g. Increment a value of the value block etc.
AET62 Reference Manual Version 1.0 The value block to be accessed. Block Number (1 Byte): Response Data Out Result Value {MSB .. LSB} Table 25: Read Value Block Response Format (4 + 2 Bytes) The value returned from the card. The value is a signed long integer (4 Value (4 Bytes): bytes).
Page 18
AET62 Reference Manual Version 1.0 Example: 1. Store a value “1” into block 0x05 APDU = {FF D7 00 00 00 01} Answer: 90 00 2. Read the value block 0x05 APDU = {FF B1 Answer: 00 00 00 01 90 00 [9000] 3.
Retrieving and setting the reader parameters. • The Pseudo-APDUs can be sent through the “AET62 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.
AET62 Reference Manual Version 1.0 Data In: Blinking Duration Control Byte 0 Byte 1 Byte 2 Byte 3 T1 Duration T2 Duration Number of 0x00 Initial Blinking State Toggle Blinking State repetition (Unit = 100ms) (Unit = 100ms) Table 34: Bi-Color LED Blinking Duration Control Format (4 Bytes) Data Out: SW1 SW2.
AET62 Reference Manual Version 1.0 7.5. Set the PICC Operating Parameter This is used to set the PICC Operating Parameter of the reader. Command Class 0xFF 0x00 0x51 New PICC 0x00 Response Operating Parameter Table 41: Command Format (5 Bytes)
Once the tag is found and detected, the corresponding ATR will be sent to the PC. You must make sure that the PCSC Escape Command has been set. See AET62 PCSC Escape Command for more details. Step 1. The first thing is to connect the “AET62 PICC Interface”.
How to Access PCSC-Compliant Tags (ISO 14443-4)? Basically, all ISO 14443-4 compliant cards (PICCs) would understand the ISO 7816-4 APDUs. The AET62 Reader just has to communicate with the ISO 14443-4 compliant cards through exchanging ISO 7816-4 APDUs and Responses.
AET62 Reference Manual Version 1.0 8.2. How to Access DESFire Tags (ISO 14443-4)? DESFire supports ISO 7816-4 APDU Wrapping and Native modes. Once the DESFire Tag is activated, the first APDU sent to the DESFire Tag will determine the “Command Mode”. If the first APDU is in “Native Mode”, the rest of the APDUs must be in “Native Mode”...
AET62 Reference Manual Version 1.0 8.3. How to Access FeliCa Tags (ISO 18092)? Typical sequence may be: Present the FeliCa Tag and Connect the PICC Interface Read / Update the memory of the tag Step 1) Connect the Tag The ATR = 3B 8F 80 01 80 4F 0C A0 00 00 03 06 03 F0 11 00 00 00 00 8A...
AET62 Reference Manual Version 1.0 >> D5 41 00 [90 00] In which, Response Data = Page 26 of 37 idvation GmbH Otto-Hesse-Straße 19 / T5 Phone +49 6151 4923021 D-64293 Darmstadt Fax +49 6151 3689296 info@idvation.com www.idvation.com...
Page 27
AET62 Reference Manual Version 1.0 Tip: To read all the memory content of the tag << 00 >> 11 48 18 26 .. 00 [90 00] Step 3) Update the memory address 08(Block 1: Byte-0)with the data << 53 >> FF [90 00] In which, Response Data = FF Topaz Memory Map.
AET62 Reference Manual Version 1.0 8.5. Get the Current Setting of the Contactless Interface Step 1) Get Status Command << FF 00 00 00 02 D4 04 >> D5 05 [Err] [Field] [NbTg] [Tg] [BrRx] [BrTx] [Type] 80 90 00 Or if no tag is in the field >>...
Appendix A. AET62 PCSC Escape Command 1. Select the “ACS AET62 PICC Interface 0” 2. Select the “Shared Mode” if the “AET62 PICC Interface” is already connected or “Direct Mode if the “AET62 PICC Interface” is not connected. 3. Press the “Connect” button to establish a connection between the PC and the AET62 reader.
AET62 Reference Manual Version 1.0 Add a DWORD “EscapeCommandEnable” under HKLM\SYSTEM\CCS\Enum\USB\Vid_072F&Pid_0 102\Device Parameters For Vista, the path is: Computer\HKEY_LOCAL_MACHINE\SYSTEMS\C urrentControlSet\Enum\USB Look for: VID_072F&PID_0102 Then expand the node. Look under Device parameters Create a DWORD entry (32-bit) with the name: EscapeCommandEnable...
AET62 Reference Manual Version 1.0 To Modify the value of the EscapeCommandEnable double click on the entry and input 1 in the Value Page 31 of 37 idvation GmbH Otto-Hesse-Straße 19 / T5 Phone +49 6151 4923021 D-64293 Darmstadt Fax +49 6151 3689296 info@idvation.com...
AET62 Reference Manual Version 1.0 10. Appendix B. APDU Command and Response Flow for ISO 14443-Compliant Tags Assume an ISO14443-4 Type B tag is used. << Typical APDU Command and Response Flow >> Reader USB Interface RF Interface Sequences (12Mbps) (13.56MHz)
AET62 Reference Manual Version 1.0 11. Appendix C. APDU Command and Response Flow for ISO 18092-Compliant Tags Assume a TOPAZ tag is used. << Typical APDU Command and Response Flow >> Reader Sequences USB Interface RF Interface (12Mbps) (13.56MHz) 1. The command...
Page 34
AET62 Reference Manual Version 1.0 Error Error Code No Error 0x00 Time Out, the target has not answered 0x01 A CRC error has been detected by the contactless UART 0x02 A Parity error has been detected by the contactless UART...
AET62 Reference Manual Version 1.0 12. Appendix E. Sample Codes for Setting the LED Example 1: To read the existing LED State // Assume both Red and Green LEDs are OFF initially // APDU = “FF 00 40 00 04 00 00 00 00”...
Page 36
AET62 Reference Manual Version 1.0 Example 4: To turn on the Red LED for 2 sec. After that, resume to the initial state // Assume the Red LED is initially OFF, while the Green LED is initially ON. // // The Red LED will turn on during the T1 duration, while the Green LED will turn off during the T1 duration.
Page 37
AET62 Reference Manual Version 1.0 Example 6: To blink the Red and Green LEDs of 1Hz for 3 times // Assume both the Red and Green LEDs are initially OFF. // // Both Initial Red and Green Blinking States are ON //...
Need help?
Do you have a question about the AET62 and is the answer not in the manual?
Questions and answers