| all | frequencies |
|
exhibits | applications |
|---|---|---|---|---|
| manual |
| app s | submitted / available | |||||||
|---|---|---|---|---|---|---|---|---|
| 1 |
|
Users Manual | Users Manual | 926.46 KiB | ||||
| 1 | Cover Letter(s) | |||||||
| 1 | External Photos | |||||||
| 1 | ID Label/Location Info | |||||||
| 1 | Internal Photos | |||||||
| 1 | Test Report | |||||||
| 1 | Test Setup Photos |
| 1 | Users Manual | Users Manual | 926.46 KiB |
ACR1281S ACR1281S Specification V1.01 Advanced Card Systems Ltd. Page 1 of 56 ACR1281S Rev Number V1.00 Revision History Date Author Notes 2010-08-19 Nathan Li/ Kit Au Preliminary specification for ACR12 V1.01 2010-12-15 Vincent Zhong/Jessy Wei Modify Peripherals Control command 81S Advanced Card Systems Ltd. Page 2 of 56 ACR1281S INDEX Index ....................................................................................................................................................3 Introduction..........................................................................................................................................5 features.................................................................................................................................................5 Terms ...................................................................................................................................................6 Quick Overview of the ACR1281S Reader.........................................................................................7 1. ACR1281S (with Contact Card Option)......................................................................................7 2. ACR1281S (without Contact Card Option).................................................................................7 3. ACR1281S ICC Interface ............................................................................................................8 4. ACR1281S PICC Interface..........................................................................................................8 System description.............................................................................................................................10 1. The Reader Block Diagram .......................................................................................................10 2. Communication Flow Chart of ACR1281S...............................................................................11 Hardware Description ........................................................................................................................12 3. USB Interface ............................................................................................................................12 4. LED Indicator ............................................................................................................................12 5. Buzzer ........................................................................................................................................13 6. ICC Interface (Contact Smart Card) ..........................................................................................13 7. PICC Interface (Contactless Smart Card)..................................................................................13 Serial Communication Protocol (CCID-liked FRAME Format).......................................................14 8. Bulk-OUT Command ................................................................................................................15 8.1 HOST_to_RDR_IccPowerOn..............................................................................................15 8.2 HOST_to_RDR_IccPowerOff .............................................................................................15 8.3 HOST_to_RDR_XfrBlock ..................................................................................................16 8.4 HOST_to_RDR_GetSlotStatus............................................................................................16 8.5 HOST_to_RDR_SetParameters...........................................................................................17 8.6 HOST_to_RDR_Escape ......................................................................................................17 9. Bulk-IN Response......................................................................................................................19 9.1 RDR_to_HOST_DataBlock ................................................................................................19 9.2 RDR_to_HOST_SlotStatus .................................................................................................20 9.3 RDR_to_HOST_Parameters................................................................................................20 9.4 RDR_to_HOST_Escape ......................................................................................................21 10. RDR_to_PC_NotifySlotChange Messages .............................................................................21 11. Error Handling .........................................................................................................................23 12. Protocol Flow Examples..........................................................................................................24 Peripherals Control ............................................................................................................................26 1. Set Serial Communication Mode...............................................................................................26 2. Get Firmware Version ...............................................................................................................26 3. Enter Firmware Upgrade Mode .................................................................................................27 4. LED Control ..............................................................................................................................27 5. Buzzer Control...........................................................................................................................28 6. Default LED and Buzzer State ..................................................................................................28 7. Automatic PICC Polling ............................................................................................................29 8. PICC Polling for specific PICC Types ......................................................................................29 9. Auto PPS for the PICC Interface (Communication Speed Change) .........................................30 10. Antenna Field ON/OFF for the PICC Interface.......................................................................30 Advanced Card Systems Ltd. Page 3 of 56 ACR1281S 11. Exclusive Mode Configure ......................................................................................................30 12. Request Command Test...........................................................................................................31 13. Continuous Wake Up Command Sending Test for the PICC Interface ..................................32 14. Read and Update the RC531 Register for the PICC Interface ................................................32 15. Go into Contactless EMV Terminal Loop...............................................................................32 16. Go into Contact EMV Terminal Loop.....................................................................................32 17. Read and Initial Card Insert Counter .......................................................................................32 18. Initial RC531 Setting For PICC...............................................................................................33 PICC Interface Description................................................................................................................34 1. ATR Generation ........................................................................................................................34 PICC APDU Commands for General Purposes.................................................................................36 1. Get Data .....................................................................................................................................36 PICC APDU Commands (T=CL Emulation) for MIFare 1K/4K MEMORY Cards ........................37 2.1 Load Authentication Keys .......................................................................................................37 2.2.1 Authentication for MIFARE 1K/4K.....................................................................................39 2.3 Read Binary Blocks .................................................................................................................42 2.4 Update Binary Blocks..............................................................................................................43 2.5 Value Block Related Commands.............................................................................................44 2.5.1 Value Block Operation .........................................................................................................44 2.5.2 Read Value Block .................................................................................................................45 2.5.3 Restore Value Block .............................................................................................................46 Basic Program Flow for Contactless Applications ............................................................................47 1. How to access PCSC Compliant Tags (ISO14443-4)? .............................................................48 2. How to access DESFIRE Tags (ISO14443-4)? .........................................................................51 Basic Program Flow for Contact Applications .................................................................................53 1. How to access ACOS3 ICC Cards (ISO7816)?.........................................................................53 Annex A.............................................................................................................................................55 Technical Specification .....................................................................................................................56 Advanced Card Systems Ltd. Page 4 of 56 ACR1281S INTRODUCTION The ACR1281S is a dual-interface reader(IFD and PCD) that supports both contact and contactless
(PICC) smart cards. FEATURES One standard ICC landing type card acceptor. ISO 7816 Parts 1-4 Compliant for Contact Smart Card Interface. Support contact memory cards. ISO 14443 Parts 1-4 Compliant for Contactless Smart Card Interface. A built-in antenna for PICC contactless access applications. The ACR1281 supports the following Tag Types:
o MIFARE Classic. E.g. MIFARE 1K, 4K, MINI and Ultralight. o ISO14443-4 Type A and B. T=CL emulation for MIFare 1K/4K PICCs. Multi-Blocks Transfer Mode is provided for efficient PICC access. High Speed (424 kbps) Communication for PICCs. #Maximum 848 kbps. Intelligent Support for Hybrid Cards and Combi Cards. Energy saving modes for turning off the antenna field whenever the PICC is inactive, or no PICC is found. It prevents the PICC from exposing to the field all the time. User-Controllable Peripherals. E.g. LED, Buzzer. CCID-liked Frame Format. Serial Interface up to 500kbps. Device Firmware Upgradeable through the USB Interface. Advanced Card Systems Ltd. Page 5 of 56 ACR1281S TERMS IFD: Interface Device. A terminal, communication device, or machine to which the integrated circuit(s) card is electrically connected during operation. PCD: Proximity Coupling Device. ISO 14443 Contactless Reader. ICC: Integrated Circuit(s) Card. Refer to a plastic card containing an integrated circuit, which is compatible with ISO 7816. PICC: Proximity Integrated Circuit(s) Card. Contactless Cards operating without mechanical contact to the IFD, using magnetic coupling. Combi-Card: A smart card that supports both ICC and PICC Interfaces. But only one interface can be operating at any one time. Hybrid-Card: A smart card that consists of both ICC and PICC cards. Both ICC and PICC cards can be operating at the same time. USB: Universal Serial Bus, a common device interface used in PC environment. CCID: The specifications for USB devices that interface with ICC or act as interfaces with ICC/PICC. PCSC: Personal Computer Smart Card, a specification that can facilitate the interoperability necessary to allow ICC/PICC technology to be effectively utilized in the PC environment. ISO 7816: A standard for contact smart cards (ICC). T=0: Character-oriented asynchronous half duplex transmission protocol for ICCs (ISO 7816). T=1: Block-oriented asynchronous half duplex transmission protocol for ICCs (ISO 7816). ISO 14443: A standard for contactless smart cards (PICC) T=CL: Block-oriented asynchronous half duplex transmission protocol for PICCs (ISO 14443). APDU: Application Protocol Data Unit. ATR: Answer-to-Reset. The transmission sent by an ICC to the reader (IFD) in response to a RESET condition. ATS: Answer-to-Select. The transmission sent by a PICC Type A to the reader (PCD) in response to a SELECT condition. ATQB: Answer-to-Request. The transmission sent by a PICC Type B to the reader (PCD) in response to a REQUEST condition. Card Insertion Event: Either an ICC or a PICC is just appeared to the reader. Card Removal Event: Either an ICC or a PICC is removed from the reader. NAK: Negative Acknowledge, only used to get the last response or slot change message report in ACR1281S. XOR : Exclusive OR RDR: ACR1281S. HOST: Host Controller. HOST_to_RDR: Host Controller -> ACR1281S RDR_to_HOST: ACR1281S -> Host Controlle Advanced Card Systems Ltd. Page 6 of 56 ACR1281S QUICK OVERVIEW OF THE ACR1281S READER 1. ACR1281S (with Contact Card Option) 2. ACR1281S (without Contact Card Option) Advanced Card Systems Ltd. Page 7 of 56 ACR1281S 3. ACR1281S ICC Interface 4. ACR1281S PICC Interface Advanced Card Systems Ltd. Page 8 of 56 ACR1281S Recommended ICAO E-Passport Placement ICAO E-Passport In case the E-Passport is not accessible, try to place the E-Passport above the reader by 5~10mm. 5~10mm Advanced Card Systems Ltd. Page 9 of 56 ACR1281S SYSTEM DESCRIPTION 1. The Reader Block Diagram LED & Buzzer Built-In Antenna RC531 NFC Interface SPI Chip AT90SCR100H Host Controller Serial USB Firmware Upgrade PC Operation System Contactless Interface Carrier = 13.56MHz ISO7816 Interface PICC Contactless Card ICC Contact Card Advanced Card Systems Ltd. Page 10 of 56 ACR1281S 2. Communication Flow Chart of ACR1281S Host ACR128U PCSC ICC Interface ACR128U PCSC PICC Interface Serial Interface
(CCID liked Format) Physical Interface PCSC Layer ACR1281S ISO 7816 Part1-4 ICC Interface T=CL &T=1 Emulation ISO 14443 Part1-4 PICC Interface ICC And PICC ICC
(Landing Type Acceptor ) PICC
(Built-In Antenna ) Advanced Card Systems Ltd. Page 11 of 56 ACR1281S HARDWARE DESCRIPTION 3. USB Interface The ACR1281S is connected to a Host through the RS232 Serial Interface; the max speed is up to 500kbps. Pin 1 2 3 4 Signal Function VCC RXD TXD GND
+5V power supply for the reader. The signal from the reader to the host. The signal from the host to the reader. Reference voltage level for power supply 4. LED Indicator The LEDs are used for showing the state of the contact and contactless interfaces.The Red LED is used for showing PICC status and Green LED for ICC. Reader States 1. No PICC Found or PICC present but not activated. 2. PICC is present and activated 3. PICC is operating 4. ICC is present and activated 5. ICC is absent or not activated 6. ICC is operating Advanced Card Systems Ltd. Red LED PICC Indicator A single pulse per
~ 5 seconds ON Blinking Green LED ICC Indicator ON OFF Blinking Page 12 of 56 ACR1281S 5. Buzzer A monotone buzzer is used to show the Card Insertion and Card Removal events. Events 1. The reader powered up and initialization success. 2. Card Insertion Event (ICC or PICC) 3. Card Removal Event (ICC or PICC) 6. ICC Interface (Contact Smart Card) Buzzer Beep Beep Beep A landing type Smart Card Acceptor is used for providing reliable operations. The minimum life cycle of the acceptor is about 300K times of card insertion and removal. 7. PICC Interface (Contactless Smart Card) A built-in antenna is used for communication between the PCD and PICC. Advanced Card Systems Ltd. Page 13 of 56 ACR1281S SERIAL COMMUNICATION PROTOCOL (CCID-LIKED FRAME FORMAT) Communication setting: 9600 bps(Default), 19200 bps, 38400 bps, 57600 bps and 115200 bps,128000bps, 250000bps, 500000bps. Byte format: 8-N-1. The communication protocol between the Host and ACR1281S is very similar to the CCID protocol. Command Frame Format Bulk-OUT Header APDU Command Checksum ETX
(0x03) STX
(0x02) Or Parameters M Bytes
(If applicable) 1 Byte 10 Bytes 1 Byte 1 Byte NOTE: Checksum = XOR {Bulk-OUT Header, APDU Command or Parameters}
Status Frame Format STX
(0x02) 1 Byte Status Checksun 1 Byte 1 Byte ETX
(0x03) 1 Byte NOTE: Checksum = Status Response Frame Format Bulk-IN Header APDU Response Checksum ETX
(0x03) STX
(0x02) 1 Byte 10 Bytes 1 Byte 1 Byte Or abData N Bytes
(If applicable) NOTE: Checksum = XOR {Bulk-IN Header, APDU Response or abData}
Advanced Card Systems Ltd. Page 14 of 56 ACR1281S 8. Bulk-OUT Command 8.1 HOST_to_RDR_IccPowerOn This command is used to activate the ICC and PICC . The ATR will be returned if available in response RDR_to_HOST_DataBlock Format (See 2.1). Command Frame Format STX
(0x02) 1 Byte Bulk-OUT Header Parameters Checksum
(HOST_to_RDR_IccPowerOn) 10 Bytes 0 Byte 1 Byte ETX
(0x03) 1 Byte HOST_to_RDR_IccPowerOn Format Offset 0 1 Size Value 1 4 Field bMessageType dwLength
<LSB .. MSB>
bSlot bSeq bPowerSelect 1 1 1 00h,01h 00h-FFh 00h, 01h, 02h, 03h Description 62h 00000000h Message-specific data length 00h forPICC interface, 01h for ICC Sequence number for command Voltage that is applied to the ICC 00h Automatic Voltage Selection 01h 5.0 volts 02h 3.0 volts 03h 1.8 volts Reserved for Future Use 8 abRFU 2 Note: The ICC interface must be activated before access contact cards while PICC interface is optional. Example: Power on PICC slot Command: 02 62 00 00 00 00 00 00 00 00 00 62 03 ACK: 02 00 00 03 Response: 02 80 10 00 00 00 00 00 00 81 00 3B 8B 80 01 4A 43 4F 50 33 31 33 36 47 44 54 4C 2A 03 8.2 HOST_to_RDR_IccPowerOff This command is used to deactivate the ICC. For PICC, it does nothing. Command Frame Format STX
(0x02) 1 Byte Bulk-OUT Header Parameters Checksum
(HOST_to_RDR_IccPowerOff) 10 Bytes 0 Byte 1 Byte ETX
(0x03) 1 Byte HOST_to_RDR_IccPowerOff Format Offset 0 1 Size Value 1 4 Description 63h 00000000h Message-specific data length 1 1 3 00h,01h 00-FFh 00h forPICC interface, 01h for ICC Sequence number for command Reserved for Future Use Advanced Card Systems Ltd. Page 15 of 56 Field bMessageType dwLength
<LSB .. MSB>
bSlot bSeq abRFU 5 6 7 5 6 7 ACR1281S Example: Power off PICC slot Command: 02 63 00 00 00 00 00 00 00 00 00 63 03 ACK: 02 00 00 03 Response: 02 81 00 00 00 00 00 00 00 81 00 00 03 8.3 HOST_to_RDR_XfrBlock This command is used to exchange APDUs between the Host and ACR1281S. Command Frame Format STX
(0x02) 1 Byte Bulk-OUT Header APDU Commands Checksum
(HOST_to_RDR_XfrBlock) 10 Bytes M Bytes 1 Byte ETX
(0x03) 1 Byte HOST_to_RDR_XfrBlock Format Offset 0 1 Size Value 1 4 6Fh M Field bMessageType dwLength
<LSB .. MSB>
bSlot bSeq bBWI 1 1 1 wLevelParameter 2 abData Byte array 5 6 7 8 10 Description Message-specific data length 00h,01h 00-FFh 00-FFh 0000h 00h forPICC interface, 01h for ICC Sequence number for command Used to extend the Block Waiting Timeout. Data sent to the reader. Example: Read 256 bytes from PICC slot Command: 02 6F 05 00 00 00 00 00 00 00 00 80 B2 00 00 00 58 03 ACK: 02 00 00 03 Response: 02 80 02 01 00 00 00 00 00 81 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F 10 11 12 13 14 15 16 17 18 19 1A 1B 1C 1D 1E 1F 20 21 22 23 24 25 26 27 28 29 2A 2B 2C 2D 2E 2F 30 31 32 33 34 35 36 37 38 39 3A 3B 3C 3D 3E 3F 40 41 42 43 44 45 46 47 48 49 4A 4B 4C 4D 4E 4F 50 51 52 53 54 55 56 57 58 59 5A 5B 5C 5D 5E 5F 60 61 62 63 64 65 66 67 68 69 6A 6B 6C 6D 6E 6F 70 71 72 73 74 75 76 77 78 79 7A 7B 7C 7D 7E 7F 80 81 82 83 84 85 86 87 88 89 8A 8B 8C 8D 8E 8F 90 91 92 93 94 95 96 97 98 99 9A 9B 9C 9D 9E 9F A0 A1 A2 A3 A4 A5 A6 A7 A8 A9 AA AB AC AD AE AF B0 B1 B2 B3 B4 B5 B6 B7 B8 B9 BA BB BC BD BE BF C0 C1 C2 C3 C4 C5 C6 C7 C8 C9 CA CB CC CD CE CF D0 D1 D2 D3 D4 D5 D6 D7 D8 D9 DA DB DC DD DE DF E0 E1 E2 E3 E4 E5 E6 E7 E8 E9 EA EB EC ED EE EF F0 F1 F2 F3 F4 F5 F6 F7 F8 F9 FA FB FC FD FE FF 00 90 00 92 03 8.4 HOST_to_RDR_GetSlotStatus This command is used to get the status of ICC, PICC slots. Command Frame Format STX
(0x02) 1 Byte Bulk-OUT Header Parameters Checksum
(HOST_to_RDR_XfrBlock) 10 Bytes 0 Byte 1 Byte ETX
(0x03) 1 Byte HOST_to_RDR_GetSlotStatus Format Advanced Card Systems Ltd. Page 16 of 56 ACR1281S Offset 0 1 5 6 7 Field bMessageType dwLength
<LSB .. MSB>
bSlot bSeq abRFU Size Value 1 4 Description 65h 00000000h Message-specific data length 1 1 3 00h,01h 00-FFh 00h forPICC interface, 01h for ICC Sequence number for command Reserved for Future Use 8.5 HOST_to_RDR_SetParameters This command is used to change the parameters for contact interface to implement PPS. Command Frame Format STX
(0x02) 1 Byte Bulk-OUT Header Parameters Checksum
(HOST_to_RDR_XfrBlock) 10 Bytes 5 or 7 bytes 1 Byte ETX
(0x03) 1 Byte HOST_to_RDR_SetParameters Format Offset 0 1 Size Value 1 4 Field bMessageType dwLength
<LSB .. MSB>
bSlot bSeq bProtocolNum 61h 00000005h, 00000007h 00h,01h 00-FFh 00h,01h 1 1 1 abRFU abProtocolDataStructure Byte array 2 5 6 7 8 10 Description Message-specific data length 00h forPICC interface, 01h for ICC 00h for protocol T=0, 01h for T=1. Used to extend the Block Waiting Timeout. Reserved for Future Use Protocol Data Structure Remarks:
For protocol T = 0, dwLength = 00000005h; for protocol T = 1, dwLength = 00000007h. More detail about the abProtocolDataStructure field, please refer to CCID specification. 8.6 HOST_to_RDR_Escape This command is used to peripherals control such as LED & Buzzer control, Get firmware Version, set the serial communication mode and so on. Command Frame Format STX
(0x02) 1 Byte Bulk-OUT Header Commands Checksum
(HOST_to_RDR_XfrBlock) 10 Bytes M bytes 1 Byte ETX
(0x03) 1 Byte HOST_to_RDR_Escape Format Offset 0 1 Field bMessageType dwLength
<LSB .. MSB>
Advanced Card Systems Ltd. Size Value 1 4 6Bh M Description Message-specific data length Page 17 of 56 ACR1281S 5 6 7 10 bSlot bSeq abRFU abData 00h,01h 00-FFh 1 1 3 Byte array 00h for PICC interface, 01h for ICC 00h for protocol T=0, 01h for T=1. Reserved for Future Use Data block sent to the reader. Example for buzzer on 50ms :
Command: 02 6B 06 00 00 00 01 00 00 00 00 E0 00 00 28 01 05 A0 03 ACK: 02 00 00 03 Response: 02 83 06 00 00 00 01 00 02 00 00 E1 00 00 00 01 05 63 03 Advanced Card Systems Ltd. Page 18 of 56 ACR1281S 9. Bulk-IN Response 9.1 RDR_to_HOST_DataBlock The reader in response to the HOST_to_RDR_IccPowerOn and HOST_to_RDR_XfrBlock command messages. Response to the HOST_to_RDR_IccPowerOn:
Response Frame Format STX
(0x02) 1 Byte Bulk-IN Header abData Checksum
(RDR_to_HOST_DataBlock) 10 Bytes N Bytes of ATR 1 Byte
(If card is available) ETX
(0x03) 1 Byte RDR_to_HOST_DataBlock Format Offset 0 Field bMessageType Size Value 1 80h 1 5 6 dwLength
<LSB .. MSB>
bSlot bSeq 4 1 1 1 bStatus bError 1 bChainParameter 1 7 8 9 Response to HOST_to_RDR_XfrBlock Response Frame Format Description Indicates that a data block is being sent from the ACR1281S Size of abData field. (N Bytes) 00h for PICC interface, 01h for ICC Sequence number for corresponding command. N Same as Bulk-OUT Same as Bulk-OUT STX
(0x02) 1 Byte Bulk-IN Header abData Checksum
(RDR_to_HOST_DataBlock) 10 Bytes N Bytes 1 Byte ETX
(0x03) 1 Byte RDR_to_HOST_DataBlock Format Offset 0 Field bMessageType Size Value 1 80h 1 5 6 7 8 9 dwLength
<LSB .. MSB>
bSlot bSeq 4 1 1 1 bStatus bError 1 bChainParameter 1 N Same as Bulk-OUT Same as Bulk-OUT Description Indicates that a data block is being sent from the ACR1281S Size of abData field. (N Bytes) 00h for PICC interface, 01h for ICC Sequence number for corresponding command. Advanced Card Systems Ltd. Page 19 of 56 ACR1281S 9.2 RDR_to_HOST_SlotStatus The reader in response to the HOST_to_RDR_IccPowerOff and HOST_to_RDR_GetSlotStatus command messages. Response Frame Format STX
(0x02) 1 Byte Bulk-IN Header abData Checksum
(RDR_to_HOST_SlotStatus) 10 Bytes 0 Byte 1 Byte ETX
(0x00) 1 Byte RDR_to_HOST_SlotStatus Format Offset 0 Field bMessageType Size Value 1 81h 1 5 6 7 8 9 dwLength
<LSB .. MSB>
bSlot bSeq bStatus bError bClockStatus 4 1 1 1 1 1 00000000h Same as Bulk-OUT Same as Bulk-OUT 9.3 RDR_to_HOST_Parameters Description Indicates that a data block is being sent from the ACR1281S Size of abData field. (0 Bytes) 00h for PICC, 01h for ICC Sequence number for corresponding command The reader in response to the HOST_to_RDR_SetParameters command messages. Response Frame Format STX
(0x02) 1 Byte Bulk-IN Header abData Checksum
(RDR_to_HOST_SlotStatus) 10 Bytes 5 or 7 Bytes 1 Byte ETX
(0x00) 1 Byte RDR_to_HOST_SlotStatus Format Offset 0 Field bMessageType Size Value 1 82h 1 5 6 7 8 9 10 dwLength
<LSB .. MSB>
bSlot bSeq 4 1 1 bStatus bError bProtocolNum abProtocolDataStructure Byte array 1 1 1 00000005h, 00000007h Same as Bulk-OUT Same as Bulk-OUT Remarks:
Description Indicates that a data block is being sent from the ACR1281S Size of abData field. 00h for PICC, 01h for ICC Sequence number for corresponding command Protocol Data Structure For protocol T = 0, dwLength = 00000005h; for protocol T = 1, dwLength = 00000007h. More detail about the abProtocolDataStructure field, please refer to CCID specification. Advanced Card Systems Ltd. Page 20 of 56 ACR1281S 9.4 RDR_to_HOST_Escape The reader in response to HOST_to_RDR_Escape command messages. Response Frame Format STX
(0x02) 1 Byte Bulk-IN Header abData Checksum
(RDR_to_HOST_DataBlock) 10 Bytes N Bytes 1 Byte ETX
(0x03) 1 Byte Description Indicates that a data block is being sent from the ACR1281S Size of abData field. (N Bytes) 00h for PICC, 01h for ICC Sequence number for corresponding command Reserved for Future Use Data sent from reader. RDR_to_HOST_Escape Format Offset 0 Field bMessageType Size Value 1 83h dwLength
<LSB .. MSB>
bSlot bSeq 4 1 1 bStatus bError bRFU abData 1 1 1 Byte array N Same as Bulk-OUT Same as Bulk-OUT 00h 1 5 6 7 8 9 10 10. RDR_to_PC_NotifySlotChange Messages This message is used to report the Card Insertion/Removal Event to the HOST. Frame Format STX
(0x02) 1 Byte Interrupt-In Messages Checksum 2 Bytes 1 Byte ETX
(0x03) 1 Byte Advanced Card Systems Ltd. Page 21 of 56 ACR1281S RDR_to_PC_NotifySlotChange Format Offset 0 1 Size Value Field bMessageType 1 bmSlotCardState 1 50h Description Each slot has 2 bits. The least significant bit reports the current state of the slot (0b = no card present, 1b = card present). The most significant bit reports whether the slot has changed state since the last RDR_to_PC_NotifySlotChange message was sent (0b = no change, 1b = change). bmSlotCardState Bit Map Offset Bit0 Bit1 Bit2 Bit3 Bit4 Bit5 Bit6 Bit7 Field Slot 0 current state Slot 0 changed status Slot 1 current state Slot 1 changed status Slot 2 current state Slot 2 changed status RFU RFU Description PICC slot state PICC slot changed status ICC slot state ICC slot changed status RFU RFU RFU RFU Advanced Card Systems Ltd. Page 22 of 56 ACR1281S 11. Error Handling
- ACK Frame: {02 00 00 03}. If the frame sent by the HOST is correctly received by the RDR, a positive status frame = {02 00 00 03} will be sent to the HOST immediately to inform the HOST the frame is correctly received. The HOST has to wait for the response of the command. The RDR will not receive any more frames while the command is being processed.
- NAK Frame = {02 00 00 00 00 00 00 00 00 00 00 00 03} // 11 zeros The NAK Frame is only used by the HOST to get the last response or card insertion/ removal event messages. In case of errors, a negative status frame will be sent to the HOST to indicate the frame is either corrupted or wrong formatted.
- Checksum Error Frame = {02 FF FF 03}. The received data checksum is not correct.
- Length Error Frame = {02 FE FE 03}. The length dwLength is greater than 0x0105 bytes.
- ETX Error Frame = {02 FD FD 03}. The last byte is not equal to ETX 0x03.
- Slot error Frame = {02 FB FB 03}. The Slot number is not 00 or 01 .
- Time out Error Frame : {02 99 99 03}. The time of data transmit is over. Advanced Card Systems Ltd. Page 23 of 56 ACR1281S 12. Protocol Flow Examples 1) Activate a ICC 1. HOST sends a frame 2. RDR sends back a positive status frame immediately 3. RDR sends back the response of the command HOST
02 62 00 00 00 00 01 00 00 00 00 63 03 02 00 00 03 (positive status frame) RDR
.. after some processing delay .. 02 80 13 00 00 00 01 00 00 81 00 3B BE 11 00 00 41 01 38 00 00 01 00 00 00 00 00 01 90 00 6F 03
HOST 2) Activate a ICC (Incorrect Checksum, HOST ) 1. HOST sends a corrupted frame 2. RDR sends back a negative status frame immediately 3. HOST sends the frame again. 4. RDR sends back a positive status frame immediately 5. RDR sends back the response of the command
HOST 3) Activate a ICC (Incorrect Checksum, RDR) 1. HOST sends a frame 2. RDR sends back a positive status frame immediately 3. RDR sends back the response (corrupted) of the command 4. HOST sends a NAK frame to get the response again. 5. RDR sends back the response of the command
02 62 00 00 00 00 01 00 00 00 00 [Incorrect Checksum] 03 02 FF FF 03 (negative status frame) 02 62 00 00 00 00 01 00 00 00 00 63 03 02 00 00 03 (positive status frame)
.. after some processing delay .. 02 80 13 00 00 00 01 00 00 81 00 3B BE 11 00 00 41 01 38 00 00 01 00 00 00 00 00 01 90 00 6F 03 02 62 00 00 00 00 01 00 00 00 00 63 03 02 00 00 03 (positive status frame)
.. after some processing delay .. 02 80 13 00 00 00 01 00 00 81 00 3B BE 11 00 00 41 01 38 00 00 01 00 00 00 00 00 01 90 00
[Incorrect Checksum] 03 02 00 00 00 00 00 00 00 00 00 00 00 03 02 80 13 00 00 00 01 00 00 81 00 3B BE 11 00 00 41 01 38 00 00 01 00 00 00 00 00 01 90 00 6F 03 RDR RDR Advanced Card Systems Ltd. Page 24 of 56 ACR1281S 4) Exchange APDU with ICC 1. HOST sends a frame 2. RDR sends back a positive status frame immediately 3. RDR sends back the response of the command HOST
02 6F 05 00 00 00 01 00 00 00 00 80 84 00 00 08 67 03 02 00 00 03 (positive status frame) RDR
.. after some processing delay ..
:02 80 0A 00 00 00 01 00 00 81 00 C2 FF 2D 23 C5 F6 5C F2 90 00 34 03 02 50 0C [Checksum] 03 02 50 07 [Checksum] 03 02 50 07 [Checksum] 03 HOST APDU Command: 80 84 00 00 08 APDU Response: 22 5C E9 1C A4 5A A4 D6 90 00 5) Insert contact card into the ICC slot 1. Insert contact card into the ICC slot 2. RDR sends a Interrupt-In Message frame to HOST 3. Present contactless card to the Antenna field 4. RDR sends a Interrupt-In Message frame to HOST 5. HOST sends a NAK frame to get the Message again. 6. RDR sends back the last messages.
RDR Advanced Card Systems Ltd. Page 25 of 56 ACR1281S PERIPHERALS CONTROL The readers peripherals control is implemented by Escape Command. 1. Set Serial Communication Mode APDU Command = {44 CMD}
APDU Response = {90 Status}
CMD Bit Map Offset Bit 0-3 Description Indicate Serial Communication Speed Bit 4 Bit 5 Bit 6 Bit 7 RFU RFU RFU Interrupt-In Message(CCID-
liked Format) Description 0 = 9600bps(Default) 1= 19200bps 2 = 38400bps 3 = 57600bps 4 = 115200bps 5 = 128000bps 6 = 230400bps 7 = 250000bps 8 = 256000bps 9 = 500000bps Other value reserve for future use. RFU RFU RFU 1 = Report Interrupt-In Message. 0 = Not report(Default). The Status bit map is the same as CMD. Example: change the communication speed to 115200bps Command: 02 6B 02 00 00 00 01 00 00 00 00 44 04 28 03 ACK : 02 00 00 03 Response: 02 83 02 00 00 00 01 00 00 81 00 90 04 95 03 Remarks:
After the communication speed is changed successfully, the program has to adjust its communication speed so as to continue the rest of the data exchanges. The initial communication speed is 9600 bps (Default) and not report Interrupt-In Message. 2. Get Firmware Version APDU Command = {E0 00 00 18 00}
APDU Response = {E1 00 00 00 Frame Length {Firmware Version}}
Example:
Command: 02 6B 05 00 00 00 01 00 00 00 00 E0 00 00 18 00 97 03 ACK: 02 00 00 03 Response: 02 83 12 00 00 00 01 00 00 81 00 E0 00 00 00 00 41 43 52 31 32 38 31 53 20 56 31 30 33 BC 03 In which, Firmware Version = 11 bytes;
e.g. Response = E1 00 00 00 0F 41 43 52 31 32 38 31 53 20 56 31 30 33 Advanced Card Systems Ltd. Page 26 of 56 ACR1281S Firmware Version (HEX) = 41 43 52 31 32 38 31 53 20 56 31 30 33 Firmware Version (ASCII) = ACR1281S V103 3. Enter Firmware Upgrade Mode Command = {FF 00 00 E0 00}
Response = {FF 00 00 E1 02 90 00}
Example:
Command: 02 6B 05 00 00 00 01 00 00 00 00 FF 00 00 E0 00 70 03 ACK: 02 00 00 03 Response: 02 83 07 00 00 00 01 00 00 00 00 FF 00 00 E1 02 90 00 09 03 Hints:
After the response display, the reader will enter the firmware upgrade mode that the reader can be upgraded firmware. 4. LED Control
Setting the LED State:
APDU Command = {E0 00 00 29 01 CMD}. APDU Response = {E1 00 00 00 01 Status}
Reading the existing LED State:
APDU Command = {E0 00 00 29 00}. APDU Response = {E1 00 00 00 01 Status}
CMD Bit Map CMD Bit 0 Bit 1 Bit 2 Bit 3 Bit 4 Bit 5 Bit 6 Bit 7 Description Description RED LED GREEN LED RFU RFU RFU RFU RFU RFU 1 = ON; 0 = OFF 1 = ON; 0 = OFF RFU RFU RFU RFU RFU RFU The Status bit map is the same as CMD. Example: Red LED ON Command: 02 6B 06 00 00 00 01 00 00 00 00 E0 00 00 29 01 01 A5 03 ACK: 02 00 00 03 Response: 02 83 06 00 00 00 01 00 00 81 00 E0 00 00 00 01 01 E5 03 Advanced Card Systems Ltd. Page 27 of 56 ACR1281S 5. Buzzer Control
Setting the Buzzer State:
APDU Command = {E0 00 00 28 01 Duration} Unit = 10mS 00 = Turn off 01 ~ FE = Duration FF = Turn o APDU Response = {E1 00 00 00 01 Status}
Reading the existing Buzzer State:
APDU Command = {E0 00 00 28 00}
APDU Response = {E1 00 00 00 01 Status}
Example for buzzer on 50ms :
Command: 02 6B 06 00 00 00 01 00 00 00 00 E0 00 00 28 01 05 A0 03 ACK: 02 00 00 03 Response: 02 83 06 00 00 00 01 00 00 81 00 E0 00 00 00 01 05 E1 03 6. Default LED and Buzzer State CMD Bit 0 MODE ICC Activation Status LED Bit 1 PICC Polling Status LED Description To show the activation status of the ICC interface. 1 = Enable; 0 =Disable To show the PICC Polling Status. 1 = Enable; 0 =Disable Bit 2 PICC Activation Status LED To show the activation status of the Bit 3 Card Insertion and Removal Events Buzzer Bit 4 Bit 5 Bit 6 Bit 7 RFU RFU RFU Card Operation Blinking LED PICC interface 1 = Enable; 0 =Disable To make a beep whenever a card insertion or removal event is detected. (For both ICC and PICC) 1 = Enable; 0 =Disabled RFU RFU RFU To blink the LED whenever the card
(PICC or ICC) is being accessed.
Setting the LED and Buzzer behaviors:
Command = { E0 00 00 21 01 CMD}. Default value of CMD = 8F;
Response = {E1 00 00 00 01 Status}
Reading the existing behaviors of the LED and Buzzer:
Command = { E0 00 00 21 00}
Response = {E1 00 00 00 01 Status}
Hints:
If you want to enjoy the silent environment, just set the CMD value to 87. Advanced Card Systems Ltd. Page 28 of 56 ACR1281S 7. Automatic PICC Polling Whenever the reader is connected to the PC, the PICC polling function will start the PICC scanning to determine if a PICC is placed on / removed from the built-antenna. We can send a command to disable the PICC polling function. The command is sent through the PCSC Escape command interface. To meet the energy saving requirement, special modes are provided for turning off the antenna field whenever the PICC is inactive, or no PICC is found. The reader will consume less current in power saving mode. Register 0x23: Automatic PICC Polling (Default value = 0x8F) Description Description CMD Bit 0 Bit 1 Bit 2 Bit 3 Bit 5 .. 4 Auto PICC Polling Turn off Antenna Field if no PICC found Turn off Antenna Field if the PICC is inactive. Activate the PICC when detected. PICC Poll Interval for PICC 1 = Enable; 0 =Disable 1 = Enable; 0 =Disable 1 = Enable; 0 =Disable 1 = Enable; 0 =Disable
<Bit 5 Bit 4>
<0 0> = 250 msec
<0 1> = 500 msec
<1 0> = 1000 msec
<1 1> = 2500 msec
1= Enable; 0= Disable. Bit 6 Bit 7 RFU Enforce ISO14443A Part 4 Enable Auto PICC Polling Function = { E0 00 00 23 01 8F}
Disable Auto PICC Polling Function = { E0 00 00 23 01 8E}
Read the existing status = { E0 00 00 23 00}; Response = {E1 00 00 00 01 Status}
Hints:
1. It is recommended to enable the option Turn Off Antenna Field if the PICC is inactive, so that the Inactive PICC will not be exposed to the field all the time so as to prevent the PICC from warming up. 2. The longer the PICC Poll Interval, the more efficient of energy saving. However, the response time of PICC Polling will become longer. The Idle Current Consumption in Power Saving Mode is about 60mA, while the Idle Current Consumption in Non-Power Saving mode is about 130mA.
#Idle Current Consumption = PICC is not activated. 3. The reader will activate the ISO14443A-4 mode of the ISO14443A-4 compliant PICC automatically. Type B PICC will not be affected by this option. 4. The JCOP30 card comes with two modes: ISO14443A-3 (MIFARE 1K) and ISO14443A-4 modes. The application has to decide which mode should be selected once the PICC is activated. 8. PICC Polling for specific PICC Types The PICC polling function can be configured to detect ISO14443 Type A PICCs or ISO14443 Type B PICCs or both. Advanced Card Systems Ltd. Page 29 of 56 ACR1281S ISO 14443 Type A PICCs Only = { E0 00 00 20 01 01}
ISO 14443 Type B PICCs Only = { E0 00 00 20 01 02 }
ISO 14443 Type A and B PICCs = { E0 00 00 20 01 03} #default setting Read the existing status = { E0 00 00 20 00}; Response = {E1 00 00 00 01 Status}
Hints:
1. It is recommended to specific the PICC types in the application so as to speed up the card detection process. 9. Auto PPS for the PICC Interface (Communication Speed Change) Whenever a PICC is recognized, the reader will try to change the communication speed between the PCD and PICC defined by the Maximum Connection Speed. If the card does not support the proposed connection speed, the reader will try to connect the card with a slower speed setting. Set Connection Speed = {E0 00 00 24 02 Max Tx Speed Max Rx Speed}
<Max Tx Speed> & <Current Tx Speed> or <Max Rx Speed> & <Current Rx Speed>
106k bps = 00 212k bps = 01 424k bps = 02 #default setting 848k bps = 03 Read the existing status = {E0 00 00 24 00};
Response = {E1 00 00 00 04 Max Tx Speed Current Tx Speed Max Rx Speed Current Rx Speed}
Hints:
1. Normally, the application should know the maximum connection speed of the PICCs being used.
#The environment also affects the maximum achievable speed. The reader just uses the proposed communication speed to talk with the PICC. The PICC will become inaccessible if the PICC or environment does not meet the requirement of the proposed communication speed. 2. The reader supports different speed between sending and receiving. 10. Antenna Field ON/OFF for the PICC Interface This command is used for turning on/off the antenna field. Antenna Field ON APDU Command = {E0 00 00 25 01 01}
Antenna Field OFF APDU Command = {E0 00 00 25 01 00}
Read the existing status APDU Command = {E0 00 00 25 00};
APDU Response = {E1 00 00 00 01 Status}
Hints:
1. Make sure the Auto PICC Polling is disabled first before turning off the antenna field. 11. Exclusive Mode Configure Advanced Card Systems Ltd. Page 30 of 56 ACR1281S To speed up the card detection time, we can enable the Enforce ICC & PICC Exclusive Mode Enforce ICC & PICC Exclusive Mode = {E0 00 00 2B 01 New Mode Configuration}.
<New Mode Configuration> #default value 01 00 = Both ICC & PICC interfaces can be activated at the same time. 01 = Either ICC or PICC interface can be activated at any one time. But not both!
Read the existing status = {E0 00 00 2B 00}
Response {E1 00 00 00 01 Current Mode}
<Current Mode >
00 = Exclusive Mode is not activated. PICC Interface is available. 01 = Exclusive Mode is activated now. PICC Interface is not available until the ICC interface is deactivated. Hints 1Dont insert any card into the contact card acceptor while the PICC is activate,or the PICC may be deselected. 12. Request Command Test This command is used for sending REQA/REQB by the reader to test antenna field and the response. Command = {E0 00 00 26 02 Command Speed}
Response = {E1 00 00 00 Length Data}
106k bps = 00 212k bps = 01 424k bps = 02 Command coding:
REQA = 01 REQB = 02 WUPA = 03 WUPB = 04 Speed coding:
Length:
Data:
Hints:
1. Make sure the Auto PICC Polling is disabled first before sending this command. No response: 00 ATQA: 02 ATQB: 0C Others: RFU Response Data (ATQA/ATQB/Others) Advanced Card Systems Ltd. Page 31 of 56 ACR1281S 13. Continuous Wake Up Command Sending Test for the PICC Interface This command is used for sending WUPA/WUPB by the reader continuously to test antenna field. Command = {E0 00 00 27 02 Command Speed}
Disable Command Sending = { E0 00 00 27 02 00 00}
Response = {E1 00 00 00 01 Status}
WUPA = 01 WUPB = 02 106k bps = 00 212k bps = 01 424k bps = 02 Command coding:
Speed coding:
Status:
Hints:
1. Make sure the Auto PICC Polling is disabled first before sending this command. 2. The reader will send the command continuously as long as the command starts. It can be stopped WUPA Sending = 01 WUPB Sending = 02 by E0 00 00 27 02 00 00. 14. Read and Update the RC531 Register for the PICC Interface Read the Register APDU Command = {E0 00 00 19 01 Register No}
APDU Response = {E1 00 00 00 01 Current Value}
Update the Register APDU Command = {E0 00 00 1A 02 Register No New Value}
APDU Response = {E1 00 00 00 00}
15. Go into Contactless EMV Terminal Loop Command = {0E 00 01 00 00}
Response = {90Current Value}
16. Go into Contact EMV Terminal Loop Command = {0E 01 01 00 00}
Response = {E1 00 00 00 01 Current Value}
17. Read and Initial Card Insert Counter Read the Register = {E0 00 00 09 00}
Initialize the counter = {E0 00 00 09 04 ICC Counter (LSB) ICC Counter (MSB) PICC Counter (LSB) PICC Counter (MSB)}
Response = {E1 00 00 00 04 ICC Counter (LSB) ICC Counter (MSB) PICC Counter
(LSB) PICC Counter (MSB)}
Update the counter data to static storage unit = {E0 00 00 0A 00}
Advanced Card Systems Ltd. Page 32 of 56 ACR1281S 18. Initial RC531 Setting For PICC Read the Register = {E0 00 00 2F 00}
Update the Registers:
E0 00 00 2F 13 BModeIndex RxAThres106 RxAThres212 RxAThres424 RxAThres848 RxBThres106 RxBThres212 RxBThres424 RxBThres848 RxACtl106 RxACtl212 RxACtl424 RxACtl848 RxBCtl106 RxBCtl212 RxBCtl424 RxBCtl848 CWAConductonce CWBConductonce Response:
E1 00 00 00 13 BModeIndex RxAThres106 RxAThres212 RxAThres424 RxAThres848 RxBThres106 RxBThres212 RxBThres424 RxBThres848 RxACtl106 RxACtl212 RxACtl424 RxACtl848 RxBCtl106 RxBCtl212 RxBCtl424 RxBCtl848 CWAConductonce CWBConductonce Advanced Card Systems Ltd. Page 33 of 56 ACR1281S PICC INTERFACE DESCRIPTION 1. ATR Generation If the reader detects a PICC, an ATR will be sent to the PCSC driver for identifying the PICC. 1.1 ATR format for ISO 14443 Part 3 PICCs. Designation Description Initial Header Byte 0 1 2 3 4 To 3+N Value
(Hex) 3B 8N 80 01 80 4F 0C RID SS T0 TD1 TD2 T1 Tk 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. Lower nibble 0 means T = 0 Higher nibble 0 means no TA3, TB3, TC3, TD3 following. Lower nibble 1 means T = 1 Category indicator byte, 80 means A status indicator may be present in an optional COMPACT-TLV data object Application identifier Presence Indicator Length Registered Application Provider Identifier
(RID) # A0 00 00 03 06 Byte for standard Bytes for card name RFU # 00 00 00 00 Exclusive-oring of all the bytes T0 to Tk C0 .. C1 00 00 00 00 4+N UU RFU TCK e.g. ATR for MIFare 1K = {3B 8F 80 01 80 4F 0C A0 00 00 03 06 03 00 01 00 00 00 00 6A}
Length (YY) = 0x0C RID = {A0 00 00 03 06} (PC/SC Workgroup) Standard (SS) = 03 (ISO14443A, Part 3) Card Name (C0 .. C1) = {00 01} (MIFare 1K) Card Name (C0 .. C1) 00 01: Mifare 1K 00 02: Mifare 4K 00 03: Mifare Ultralight 00 26: Mifare Mini FF [SAK]: undefined tags Advanced Card Systems Ltd. Page 34 of 56 ACR1281S 1.2 ATR format for ISO 14443 Part 4 PICCs. Designation Description Initial Header Byte 0 1 2 3 4 to 3 + N Value
(Hex) 3B 8N 80 01 XX XX XX XX T0 TD1 TD2 T1 Tk 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. Lower nibble 0 means T = 0 Higher nibble 0 means no TA3, TB3, TC3, TD3 following. Lower nibble 1 means T = 1 Historical Bytes:
ISO14443A:
The historical bytes from ATS response. Refer to the ISO14443-4 specification. ISO14443B:
The higher layer response from the ATTRIB response (ATQB). Refer to the ISO14443-3 specification. Exclusive-oring of all the bytes T0 to Tk 4+N UU TCK E.g 1. ATR for DESFire = { 3B 81 80 01 80 80 } // 6 bytes of ATR Hint: Use the APDU FF CA 01 00 00 to distinguish the ISO14443A-4 and ISO14443B-4 PICCs, and retrieve the full ATS if available. ISO14443A-3 or ISO14443B-3/4 PICCs do have ATS returned. APDU Command = FF CA 01 00 00 APDU Response = 04 2C 46 71 E6 23 80 90 00 ATS = {04 2C 46 71 E6 23 80}
Command: 02 6F 05 00 00 00 00 00 00 00 00 FF CA 00 00 00 5F 03 ACK: 02 00 00 03 Response: 02 80 09 00 00 00 00 00 00 81 00 04 2C 46 71 E6 23 80 90 00 C2 03 Advanced Card Systems Ltd. Page 35 of 56 ACR1281S PICC APDU COMMANDS FOR GENERAL PURPOSES 1. Get Data The Get Data command will return the serial number or ATS of the connected PICC. Table 1.1-1a: Get UID APDU Format (5 Bytes) Command Class INS Get Data FF CA P1 00 01 P2 00 Le 00
(Max Length) Table 2.1-1b: Get UID Response Format (UID + 2 Bytes) if P1 = 0x00 Response Result Data Out UID
(LSB) UID
(MSB) SW1 SW2 Table 2.1-1c: Get ATS of a ISO 14443 A card (ATS + 2 Bytes) if P1 = 0x01 Response Result Table 2.1-1d: Response Codes Data Out ATS SW1 SW2 Results SW1 SW2 Meaning Success Warning Error Error Error 90 62 6C 63 6A 00 82 The operation is completed successfully. End of UID/ATS reached before Le bytes
(Le is greater than UID Length). XX Wrong length (wrong number Le: XX encodes the exact number) if Le is less than the available UID length. The operation is failed. Function not supported 00 81 Examples:
// To get the serial number of the connected PICC UINT8 GET_UID[5]={0xFF, 0xCA, 0x00, 0x00, 0x00};
// To get the ATS of the connected ISO 14443-4 A PICC UINT8 GET_ATS[5]={0xFF, 0xCA, 0x01, 0x00, 0x00};
Advanced Card Systems Ltd. Page 36 of 56 ACR1281S PICC APDU COMMANDS (T=CL EMULATION) FOR MIFARE 1K/4K MEMORY CARDS 2.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. Table 2.1-1a: Load Authentication Keys APDU Format (11 Bytes) Command Class INS P1 P2 Lc Data In 06 82 FF Key Key Number Key Structure Load Authentication Keys Key Structure (1 Byte):
0x00 = Key is loaded into the reader volatile memory. 0x20 = Key is loaded into the reader non-volatile memory. Other = Reserved. Key Number (1 Byte):
0x00 ~ 0x1F = Non-volatile memory for storing keys. The keys are permanently stored in the
(6 bytes) reader and will not be disappeared even the reader is disconnected from the PC. It can store up to 32 keys inside the reader non-volatile memory. 0x20 (Session Key) = Volatile memory for storing a temporally key. The key will be disappeared once the reader is disconnected from the PC. Only 1 volatile key is provided. The volatile key can be used as a session key for different sessions. Default Value = {FF FF FF FF FF FF}
Key (6 Bytes):
The key value loaded into the reader. E.g. {FF FF FF FF FF FF}
Table 2.1-1b: Load Authentication Keys Response Format (2 Bytes) Response Data Out Result SW1 SW2 Table 2.1-1c: Load Authentication Keys Response Codes Results SW1 SW2 Meaning 90 63 00 00 The operation is completed successfully. The operation is failed. Success Error Advanced Card Systems Ltd. Page 37 of 56 ACR1281S Examples:
// Load a key {FF FF FF FF FF FF} into the non-volatile memory location 0x05. APDU = {FF 82 20 05 06 FF FF FF FF FF FF}
<Similarly>
// Load a key {FF FF FF FF FF FF} into the volatile memory location 0x20. APDU = {FF 82 00 20 06 FF FF FF FF FF FF}
Hints:
1. Basically, the application should know all the keys being used. It is recommended to store all the required keys to the non-volatile memory for security reasons. The contents of both volatile and non-volatile memories are not readable by the outside world. 2. The content of the volatile memory Session Key 0x20 will remain valid until the reader is reset or power-off. The session key is useful for storing any key value that is changing from time to time. The session key is stored in the Internal RAM, while the non-volatile keys are stored in EEPROM that is relatively slower than Internal RAM. 3. It is not recommended to use the non-volatile key locations 0x00 ~ 0x1F to store any temporally key value that will be changed so often. The non-volatile keys are supposed to be used for storing any key value that will not change frequently. If the key value is supposed to be changed from time to time, please store the key value to the volatile key location 0x020. Advanced Card Systems Ltd. Page 38 of 56 ACR1281S 2.2.1 Authentication for MIFARE 1K/4K The Authentication command uses the keys stored in the reader to do authentication with the MIFARE 1K/4K card (PICC). Two types of the keys are used for authentication, TYPE_A and TYPE_B respectively. Table 2.2-1a: Load Authentication Keys APDU Format (6 Bytes) #Obsolete Command Class INS P1 P2 P3 88 FF Authentication Table 2.2-1b: Load Authentication Keys APDU Format (10 Bytes) Block Number 00 Key Type Data In Key Number Command Class INS 86 FF Authentication Authenticate Data Bytes (5 Byte):
P1 00 P2 00 Lc 05 Data In Authenticate Data Bytes Byte1 Byte 2 Byte 3 Byte 4 Byte 5 0x00 Key Type Key Number Block Number Version 0x01 Block Number (1 Byte):
The memory block is authenticated. For MIFARE 1K Card, it has totally 16 sectors and each sector consists of 4 consecutive blocks. E.g. Sector 0x00 consists of Blocks {0x00, 0x01, 0x02 and 0x03}; Sector 0x01 consists of Blocks
{0x04, 0x05, 0x06 and 0x07}; the last sector 0x0F consists of Blocks {0x3C, 0x3D, 0x3E and 0x3F}. Once the authentication is done successfully, there is no need to do the authentication again provided that the blocks to be accessed are belonging to the same sector. Please refer to the MIFARE 1K/4K specification for more details.
#Once the block is authenticated successfully, all the blocks belonging to the same sector are accessible. Key Type (1 Byte):
0x60 = Key is used as a TYPE A key for authentication. 0x61 = Key is used as a TYPE B key for authentication. Key Number (1 Byte):
0x00 ~ 0x1F = Non-volatile memory for storing keys. The keys are permanently stored in the reader and will not be disappeared even the reader is disconnected from the PC. It can store 32 keys into the reader non-volatile memory. 0x20 = Volatile memory for storing keys. The keys will be disappeared when the reader is disconnected from the PC. Only 1 volatile key is provided. The volatile key can be used as a session key for different sessions. Table 2.2-1b: Load Authentication Keys Response Format (2 Bytes) Advanced Card Systems Ltd. Page 39 of 56 ACR1281S Response Data Out Result SW1 SW2 Table 2.2-1c: Load Authentication Keys Response Codes Results SW1 SW2 Meaning Success Error 90 63 00 00 The operation is completed successfully. The operation is failed. MIFARE 1K Memory Map. Sectors Data Blocks Trailer Block
(Total 16 sectors. Each
(3 blocks, 16 bytes
(1 block, 16 bytes) sector consists of 4 consecutive blocks) Sector 0 Sector 1
.. . Sector 14 Sector 15 per block) 0x00 ~ 0x02 0x04 ~ 0x06 0x38 ~ 0x0A 0x3C ~ 0x3E 0x03 0x07 0x3B 0x3F MIFARE 4K Memory Map. Sectors Data Blocks Trailer Block
(Total 32 sectors. Each
(3 blocks, 16 bytes
(1 block, 16 bytes) sector consists of 4 consecutive blocks) Sector 0 Sector 1
.. . Sector 30 Sector 31 per block) 0x00 ~ 0x02 0x04 ~ 0x06 0x78 ~ 0x7A 0x7C ~ 0x7E 0x03 0x07 0x7B 0x7F Sectors Data Blocks Trailer Block
(Total 8 sectors. Each sector consists of 16 consecutive blocks) Sector 32 Sector 33
.. . Sector 38 Sector 39
(15 blocks, 16 bytes
(1 block, 16 bytes) per block) 0x80 ~ 0x8E 0x90 ~ 0x9E 0xE0 ~ 0xEE 0xF0 ~ 0xFE 0x8F 0x9F 0xEF 0xFF Examples:
1K Bytes 2K Bytes 2K Bytes Advanced Card Systems Ltd. Page 40 of 56 ACR1281S
// To authenticate the Block 0x04 with a {TYPE A, non-volatile, key number 0x05}.
// PC/SC V2.01, Obsolete APDU = {FF 88 00 04 60 05};
<Similarly>
// To authenticate the Block 0x04 with a {TYPE A, non-volatile, key number 0x05}.
// PC/SC V2.07 APDU = {FF 86 00 00 05 01 00 04 60 05}
Hints:
MIFARE Ultralight does not need to do any authentication. The memory is free to access. Advanced Card Systems Ltd. Page 41 of 56 ACR1281S 2.3 Read Binary Blocks The Read Binary Blocks command is used for retrieving a multiple of data blocks from the PICC. The data block/trailer block must be authenticated first before executing the Read Binary Blocks command. Table 2.3-1a: Read Binary APDU Format (5 Bytes) Command Class INS Read Binary Blocks FF B0 P1 00 P2 Le Block Number Number of Bytes to Read Block Number (1 Byte):
The starting block. Number of Bytes to Read (1 Byte):
Multiply of 16 bytes for MIFARE 1K/4K or Multiply of 4 bytes for MIFARE Ultralight Maximum 16 bytes for MIFARE Ultralight. Maximum 48 bytes for MIFARE 1K. (Multiple Blocks Mode; 3 consecutive blocks) Maximum 240 bytes for MIFARE 4K. (Multiple Blocks Mode; 15 consecutive blocks) Example 1: 0x10 (16 bytes). The starting block only. (Single Block Mode) Example 2: 0x40 (64 bytes). From the starting block to starting block+3. (Multiple Blocks Mode)
#For safety reason, the Multiple Block Mode is used for accessing Data Blocks only. The Trailer Block is not supposed to be accessed in Multiple Blocks Mode. Please use Single Block Mode to access the Trailer Block. Table 2.3-1b: Read Binary Block Response Format (Multiply of 4/16 + 2 Bytes) Response Result Data Out Data (Multiply of 4/16 Bytes) SW1 SW2 Table 2.3-1c: Read Binary Block Response Codes Results SW1 SW2 Meaning Success Error 90 63 00 00 The operation is completed successfully. The operation is failed. Examples:
// Read 16 bytes from the binary block 0x04 (MIFARE 1K or 4K) APDU = {FF B0 00 04 10}
// Read 240 bytes starting from the binary block 0x80 (MIFARE 4K)
// Block 0x80 to Block 0x8E (15 blocks) APDU = {FF B0 00 80 F0}
Advanced Card Systems Ltd. Page 42 of 56 ACR1281S 2.4 Update Binary Blocks The Update Binary Blocks command is used for writing a multiple of data blocks into the PICC. The data block/trailer block must be authenticated first before executing the Update Binary Blocks command. Table 2.3-1a: Update Binary APDU Format (Multiple of 16 + 5 Bytes) Lc Command Data In Class INS P1 P2 Update Binary Blocks FF D6 00 Block Number Number of Bytes Block Data
(Multiple of 16 to Update Bytes) Block Number (1 Byte):
The starting block to be updated. Number of Bytes to Update (1 Byte):
Multiply of 16 bytes for MIFARE 1K/4K or 4 bytes for MIFARE Ultralight. Maximum 48 bytes for MIFARE 1K. (Multiple Blocks Mode; 3 consecutive blocks) Maximum 240 bytes for MIFARE 4K. (Multiple Blocks Mode; 15 consecutive blocks) Example 1: 0x10 (16 bytes). The starting block only. (Single Block Mode) Example 2: 0x30 (48 bytes). From the starting block to starting block+2. (Multiple Blocks Mode)
#For safety reason, the Multiple Block Mode is used for accessing Data Blocks only. The Trailer Block is not supposed to be accessed in Multiple Blocks Mode. Please use Single Block Mode to access the Trailer Block. Block Data (Multiply of 16 + 2 Bytes, or 6 bytes):
The data to be written into the binary block/blocks. Table 2.3-1b: Update Binary Block Response Codes (2 Bytes) Results SW1 SW2 Meaning Success Error 90 63 00 00 The operation is completed successfully. The operation is failed. Examples:
// Update the binary block 0x04 of MIFARE 1K/4K with Data {00 01 .. 0F}
APDU = {FF D6 00 04 10 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F}
// Update the binary block 0x04 of MIFARE Ultralight with Data {00 01 02 03}
APDU = {FF D6 00 04 04 00 01 02 03}
Advanced Card Systems Ltd. Page 43 of 56 ACR1281S 2.5 Value Block Related Commands The data block can be used as value block for implementing value-based applications. 2.5.1 Value Block Operation The Value Block Operation command is used for manipulating value-based transactions. E.g. Increment a value of the value block etc. Table 2.5.1-1a: Value Block Operation APDU Format (10 Bytes) Command Class INS Value Block Operation FF D7 P1 00 P2 Lc Data In Block Number 05 VB_OP VB_Value
(4 Bytes)
{MSB .. LSB}
Block Number (1 Byte):
The value block to be manipulated. VB_OP (1 Byte):
0x00 = Store the VB_Value into the block. The block will then be converted to a value block. 0x01 = Increment the value of the value block by the VB_Value. This command is only valid for value block. 0x02 = Decrement the value of the value block by the VB_Value. This command is only valid for value block. VB_Value (4 Bytes):
The value used for value manipulation. The value is a signed long integer (4 bytes). E.g. 1: Decimal 4 = {0xFF, 0xFF, 0xFF, 0xFC}
VB_Value MSB FF FF FF E.g. 2: Decimal 1 = {0x00, 0x00, 0x00, 0x01}
VB_Value MSB 00 00 00 LSB FC LSB 01 Table 2.5.1-1b: Value Block Operation Response Format (2 Bytes) Response Data Out Result SW1 SW2 Table 2.5.1-1c: Value Block Operation Response Codes Results SW1 SW2 Meaning Success Error 90 63 00 00 The operation is completed successfully. The operation is failed. Advanced Card Systems Ltd. Page 44 of 56 ACR1281S 2.5.2 Read Value Block The Read Value Block command is used for retrieving the value from the value block. This command is only valid for value block. Table 2.5.2-1a: Read Value Block APDU Format (5 Bytes) P2 Command Class INS P1 Le 00 FF B1 Read Value Block Block Number (1 Byte):
The value block to be accessed. Table 2.5.2-1b: Read Value Block Response Format (4 + 2 Bytes) Block Number 00 Response Result Data Out Value
{MSB .. LSB}
SW1 SW2 Value (4 Bytes):
The value returned from the card. The value is a signed long integer (4 bytes). E.g. 1: Decimal 4 = {0xFF, 0xFF, 0xFF, 0xFC}
Value MSB FF FF FF E.g. 2: Decimal 1 = {0x00, 0x00, 0x00, 0x01}
Value MSB 00 00 00 LSB FC LSB 01 Table 2.5.3-1c: Read Value Block Response Codes Results SW1 SW2 Meaning Success Error 90 63 00 00 The operation is completed successfully. The operation is failed. Advanced Card Systems Ltd. Page 45 of 56 ACR1281S 2.5.3 Restore Value Block The Restore Value Block command is used to copy a value from a value block to another value block. Table 2.5.3-1a: Restore Value Block APDU Format (7 Bytes) Command Class INS Value Block Operation FF D7 P1 00 Lc 02 P2 Source Block Number Data In 03 Target Block Number Source Block Number (1 Byte): The value of the source value block will be copied to the target value block. Target Block Number (1 Byte): The value block to be restored. The source and target value Table 2.5.3-1b: Restore Value Block Response Format (2 Bytes) blocks must be in the same sector. Response Data Out Result SW1 SW2 Table 2.5.3-1c: Restore Value Block Response Codes Results SW1 SW2 Meaning Success Error 90 63 00 00 The operation is completed successfully. The operation is failed. Examples:
// Store a value 1 into block 0x05 APDU = {FF D7 00 05 05 00 00 00 00 01}
// Read the value block 0x05 APDU = {FF B1 00 05 00}
// Copy the value from value block 0x05 to value block 0x06 APDU = {FF D7 00 05 02 03 06}
// Increment the value block 0x05 by 5 APDU = {FF D7 00 05 05 01 00 00 00 05}
Advanced Card Systems Ltd. Page 46 of 56 ACR1281S BASIC PROGRAM FLOW FOR CONTACTLESS APPLICATIONS Step 0. Start the application. The reader will do the PICC Polling and scan for tags continuously. Present a PICC tag at the field of the reader. Step 1. Power on the PICC Interface Step 2. Access the PICC by exchanging APDUs. Step 2. Access the PICC by exchanging APDUs. . Step N. Power off the PICC Interface. Shut down the application. Advanced Card Systems Ltd. Page 47 of 56 ACR1281S 1. How to access PCSC Compliant Tags (ISO14443-4)?
Basically, all ISO 14443-4 complaint cards (PICCs) would understand the ISO 7816-4 APDUs. The ACR1281S Reader just has to communicate with the ISO 14443-4 complaint cards through exchanging ISO 7816-4 APDUs and Responses. ACR1281S will handle the ISO 14443 Parts 1-4 Protocols internally. MIFARE 1K, 4K, MINI and Ultralight tags are supported through the T=CL emulation. Just simply treat the MIFARE tags as standard ISO14443-4 tags. For more information, please refer to topic PICC Commands for MIFARE Classic Memory Tags Table 3.1-1a: ISO 7816-4 APDU Format Command Class ISO 7816 Part 4 Command INS P1 P2 Lc Data In Le Length of the Data In Expected length of the Response Data Table 3.1-1b: ISO 7816-4 Response Format (Data + 2 Bytes) Response Result Data Out Response Data SW1 SW2 Table 3.1-1c: Common ISO 7816-4 Response Codes Results SW1 SW2 Meaning 90 63 00 00 The operation is completed successfully. The operation is failed. Success Error Advanced Card Systems Ltd. Page 48 of 56 ACR1281S Typical sequence may be:
- Present the Tag and Connect the PICC Interface
- Read / Update the memory of the tag Step 1) Connect the Tag The ATR of the tag is 3B 8C 80 01 50 00 05 70 3B 00 00 00 00 33 81 81 20 In which, The ATQB = 50 00 05 70 3B 00 00 00 00 33 81 81. It is an ISO14443-4 Type B tag. Step 2) Send an APDU, Get Challenge. APDU Command: 00 84 00 00 08 APDU Response: 1A F7 F3 1B CD 2B A9 58 90 00 Hint:
For ISO14443-4 Type A tags, the ATS can be obtained by using the APDU FF CA 01 00 00 Advanced Card Systems Ltd. Page 49 of 56 ACR1281S For Example: ISO7816-4 APDU
// To read 8 bytes from an ISO 14443-4 Type B PICC (ST19XR08E) APDU Command ={80 B2 80 00 08}
Class = 0x80 INS = 0xB2 P1 = 0x80 P2 = 0x00 Lc = None Data In = None Le = 0x08 APDU Response: 00 01 02 03 04 05 06 07 90 00 Advanced Card Systems Ltd. Page 50 of 56 ACR1281S 2. How to access DESFIRE Tags (ISO14443-4)?
The DESFIRE supports ISO7816-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 Native Mode, the rest of the APDUs must be in Native Mode format. Similarly, If the first APDU is ISO7816-4 APDU Wrapping Mode, the rest of the APDUs must be in ISO7816-4 APDU Wrapping Mode format. Example 1: DESFIRE ISO7816-4 APDU Wrapping.
// To read 8 bytes random number from an ISO 14443-4 Type A PICC (DESFIRE) APDU = {90 0A 00 00 01 00 00}
Class = 0x90; INS = 0x0A (DESFire Instruction); P1 = 0x00; P2 = 0x00 Lc = 0x01; Data In = 0x00; Le = 0x00 (Le = 0x00 for maximum length) Answer: 7B 18 92 9D 9A 25 05 21 91AF
# Status Code{91 AF} is defined in DESFIRE specification. Please refer to the DESFIRE specification for more details. Example 2: DESFIRE Frame Level Chaining (ISO 7816 wrapping mode)
// In this example, the application has to do the Frame Level Chaining.
// To get the version of the DESFIRE card. Step 1: Send an APDU {90 60 00 00 00} to get the first frame. INS=0x60 Answer: 04 01 01 00 02 18 05 91 AF Step 2: Send an APDU {90 AF 00 00 00} to get the second frame. INS=0xAF Answer: 04 01 01 00 06 18 05 91 AF Step 3: Send an APDU {90 AF 00 00 00} to get the last frame. INS=0xAF Answer: 04 52 5A 19 B2 1B 80 8E 36 54 4D 40 26 04 91 00 Advanced Card Systems Ltd. Page 51 of 56 ACR1281S Example 3: DESFIRE Native Command.
// We can send Native DESFire Commands to the reader without ISO7816 wrapping if we find that the Native DESFire Commands are more easier to handle.
// To read 8 bytes random number from an ISO 14443-4 Type A PICC (DESFIRE) APDU = {0A 00}
Answer: AF 25 9C 65 0C 87 65 1D D7 In which, the first byte AF is the status code returned by the DESFire Card. The Data inside the blanket [1DD7] can simply be ignored by the application. Example 4: DESFIRE Frame Level Chaining (Native Mode)
// In this example, the application has to do the Frame Level Chaining.
// To get the version of the DESFIRE card. Step 1: Send an APDU {60} to get the first frame. INS=0x60 Answer: AF 04 01 01 00 02 18 05 Step 2: Send an APDU {AF} to get the second frame. INS=0xAF Answer: AF 04 01 01 00 06 18 05 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 Hints:
In DESFIRE Native Mode, the status code [90 00] will not be added to the response if the response length is greater than 1. If the response length is less than 2, the status code [90 00] will be added in order to meet the requirement of PCSC. The minimum response length is 2. Advanced Card Systems Ltd. Page 52 of 56 ACR1281S BASIC PROGRAM FLOW FOR CONTACT APPLICATIONS Step 0. Start the application and insert a ICC Card into the ICC Interface. Step 1. Power on the ICC Interface Step 2. Access the ICC by exchanging APDUs. . Step N. Power off the ICC Interface. Shut down the application. 1. How to access ACOS3 ICC Cards (ISO7816)?
Typical sequence may be:
Insert the Card and Power On the ICC Interface
- Read / Update the date of the Card Step 1) Power on the Tag Command: 02 62 00 00 00 00 01 00 00 00 00 63 03 ACK:02 00 00 03 Response: 02 80 13 00 00 00 01 00 00 81 00 3B BE 11 00 00 41 01 38 00 00 01 00 00 00 00 00 01 90 00 6F 03 The ATR of the Card is 3B BE 11 00 00 41 01 38 00 00 01 00 00 00 00 00 01 90 00 In which, TD1 = 00 and TD2 is absent ,So the Card is a T=0 ICC Card 2) Get a random for the ACOS3 Command:02 6F 05 00 00 00 01 00 00 00 00 80 84 00 00 08 67 03 ACK:02 00 00 03 Response:02 80 0A 00 00 00 01 00 00 81 00 C2 FF 2D 23 C5 F6 5C F2 90 00 34 03 3) Create a file at the Card and Open it Command: 02 6F 0D 00 00 00 01 00 00 00 00 80 20 07 00 08 41 43 4F 53 54 45 53 54 C4 03 ACK:02 00 00 03 Response:02 80 02 00 00 00 01 00 00 81 00 90 00 92 03 Command:02 6F 07 00 00 00 01 00 00 00 00 80 A4 00 00 02 FF 02 B2 03 ACK:02 00 00 03 Response: 02 80 02 00 00 00 01 00 00 81 00 90 00 92 03 Command: 02 6F 09 00 00 00 01 00 00 00 00 80 D2 00 00 04 00 00 01 00 30 03 ACK:02 00 00 03 Response: 02 80 02 00 00 00 01 00 00 81 00 90 00 92 03 Command: 02 6F 07 00 00 00 01 00 00 00 00 80 A4 00 00 02 FF 04 B4 03 ACK:02 00 00 03 Response: 02 80 02 00 00 00 01 00 00 81 00 90 00 92 03 Command: 02 6F 0B 00 00 00 01 00 00 00 00 80 D2 00 00 06 FF 01 00 00 55 55 CF 03 ACK:02 00 00 03 Response: 02 80 02 00 00 00 01 00 00 81 00 90 00 92 03 Advanced Card Systems Ltd. Page 53 of 56 ACR1281S Command: 02 6F 07 00 00 00 01 00 00 00 00 80 A4 00 00 02 55 55 4F 03 ACK:02 00 00 03 Response: 02 80 02 00 00 00 01 00 00 81 00 91 00 93 03 File name is 55 55 4)Write a date to the file in 3)step Command: 02 6F 0d 00 00 00 01 00 00 00 00 80 d2 00 00 08 01 02 03 04 05 06 07 08 31 03 ACK:02 00 00 03 Response: 02 80 02 00 00 00 01 00 00 81 00 90 00 92 03 5) Read a date from a file Command: 02 6F 05 00 00 00 01 00 00 00 00 80 B2 00 00 08 51 03 ACK:02 00 00 03 Response: 02 80 0A 00 00 00 01 00 00 81 00 01 02 03 04 05 06 07 08 90 00 92 03 Advanced Card Systems Ltd. Page 54 of 56 ACR1281S ANNEX A Example of XOR:
The Checksum byte is one byte in length and is calculated as the exclusive-OR of all the bytes with the Bulk-Header field and information field. E.g.:
Command: 02 6F 05 00 00 00 01 00 00 00 00 80 B2 00 00 08 51 03 The Bulk-Header field is 6F 05 00 00 00 01 00 00 00 00, and the information field is 80 B2 00 00 08 and the checksum is 0x51 Advanced Card Systems Ltd. Page 55 of 56 ACR1281S TECHNICAL SPECIFICATION Universal Serial Bus Interface Power source........................................ From +5V power or USB Speed ................................................... up to 500Kbps Supply Voltage...................................... Regulated 5V DC Supply Current ..................................... 200mA (max); 100mA (normal) Contactless Smart Card Interface Standard ............................................... ISO 14443 A & B Parts 1-4 Protocol ................................................ ISO14443 T=CL for ISO14443-4 compliant cards and T=CL Emulation for MIFARE 1K/4K. Smart card read / write speed ............... 106 kbps, 212 kbps, 424 kbps and 848 kbps Contact Smart Card Interface Standard ............................................... ISO 7816 1/2/3, Class A, B (5V, 3V), T=0 and T=1 Supply current....................................... max. 60mA Smart card read / write speed ............... max412kbps Short circuit protection ......................... +5V / GND on all pins CLK frequency ...................................... 4.8 MHz Card connector ..................................... Landing Card insertion cycles............................. min. 300,000 Case Dimensions ........................................... 120.48 mm (L) x 71.97 mm (W) x 20.4 mm (H) Material................................................. ABS Color ..................................................... Metallic Silver Grey Antenna Antenna Size ........................................ 65mm x 60mm Operating distance................................ up to 50 mm Operating Frequency for Contactless Cards Access Operating Frequency ............................ 13.56 MHz Built-in peripherals Monotone buzzer Dual-Color LED Operating Conditions Temperature ......................................... 0 - 50 C Humidity................................................ 10% - 80%
Cable Connector Length................................................... 10m (RS232 Standard/Certifications CE, FCC OS Windows 98, ME, 2K, XP OEM OEM-Logo possible, customer-specific colors, casing, and card connector Advanced Card Systems Ltd. Page 56 of 56 FCC Caution:
Any Changes or modifications not expressly approved by the party responsible for compliance could void the users authority to operate the equipment. This device complies with part 15 of the FCC Rules. Operation is subject to the following two conditions:
(1) This device may not cause harmful interference, and (2) this device must accept any interference received, including interference that may cause undesired operation. Note: This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference in a residential installation. This equipment generates, uses and can radiate radio frequency energy and, if not installed and used in accordance with the instructions, may cause harmful interference to radio communications. However, there is no guarantee that interference will not occur in a particular installation. If this equipment does cause harmful interference to radio or television reception, which can be determined by turning the equipment off and on, the user is encouraged to try to correct the interference by one or more of the following measures:
Reorient or relocate the receiving antenna. Increase the separation between the equipment and receiver. Connect the equipment into an outlet on a circuit different from that to which the receiver is connected. Consult the dealer or an experienced radio/TV technician for help.
| frequency | equipment class | purpose | ||
|---|---|---|---|---|
| 1 | 2011-03-14 | 13.56 ~ 13.56 | DXX - Part 15 Low Power Communication Device Transmitter | Original Equipment |
| app s | Applicant Information | |||||
|---|---|---|---|---|---|---|
| 1 | Effective |
2011-03-14
|
||||
| 1 | Applicant's complete, legal business name |
Advanced Card Systems Limited
|
||||
| 1 | FCC Registration Number (FRN) |
0018508291
|
||||
| 1 | Physical Address |
Units 4108 - 4110, 41st Floor, Manhattan Place
|
||||
| 1 |
Hong Kong, N/A
|
|||||
| 1 |
Hong Kong
|
|||||
| app s | TCB Information | |||||
| 1 | TCB Application Email Address |
b******@baclcorp.com
|
||||
| 1 | TCB Scope |
A1: Low Power Transmitters below 1 GHz (except Spread Spectrum), Unintentional Radiators, EAS (Part 11) & Consumer ISM devices
|
||||
| app s | FCC ID | |||||
| 1 | Grantee Code |
V5M
|
||||
| 1 | Equipment Product Code |
ACR1281S
|
||||
| app s | Person at the applicant's address to receive grant or for contact | |||||
| 1 | Name |
G****** L****
|
||||
| 1 | Title |
Senior Vice President, Sales and Marketing
|
||||
| 1 | Telephone Number |
27967********
|
||||
| 1 | Fax Number |
27961********
|
||||
| 1 |
g******@acs.com.hk
|
|||||
| app s | Technical Contact | |||||
| n/a | ||||||
| app s | Non Technical Contact | |||||
| n/a | ||||||
| app s | Confidentiality (long or short term) | |||||
| 1 | Does this application include a request for confidentiality for any portion(s) of the data contained in this application pursuant to 47 CFR § 0.459 of the Commission Rules?: | Yes | ||||
| 1 | Long-Term Confidentiality Does this application include a request for confidentiality for any portion(s) of the data contained in this application pursuant to 47 CFR § 0.459 of the Commission Rules?: | No | ||||
| if no date is supplied, the release date will be set to 45 calendar days past the date of grant. | ||||||
| app s | Cognitive Radio & Software Defined Radio, Class, etc | |||||
| 1 | Is this application for software defined/cognitive radio authorization? | No | ||||
| 1 | Equipment Class | DXX - Part 15 Low Power Communication Device Transmitter | ||||
| 1 | Description of product as it is marketed: (NOTE: This text will appear below the equipment class on the grant) | Contactless Smart Card Reader and Writer | ||||
| 1 | Related OET KnowledgeDataBase Inquiry: Is there a KDB inquiry associated with this application? | No | ||||
| 1 | Modular Equipment Type | Does not apply | ||||
| 1 | Purpose / Application is for | Original Equipment | ||||
| 1 | Composite Equipment: Is the equipment in this application a composite device subject to an additional equipment authorization? | No | ||||
| 1 | Related Equipment: Is the equipment in this application part of a system that operates with, or is marketed with, another device that requires an equipment authorization? | No | ||||
| 1 | Is there an equipment authorization waiver associated with this application? | No | ||||
| 1 | If there is an equipment authorization waiver associated with this application, has the associated waiver been approved and all information uploaded? | No | ||||
| app s | Test Firm Name and Contact Information | |||||
| 1 | Firm Name |
Bay Area Compliance Laboratory Corp. (Shenzhen)
|
||||
| 1 | Name |
J****** C****
|
||||
| 1 | Telephone Number |
08675******** Extension:
|
||||
| 1 | Fax Number |
08675********
|
||||
| 1 |
j******@baclcorp.com
|
|||||
| Equipment Specifications | |||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Line | Rule Parts | Grant Notes | Lower Frequency | Upper Frequency | Power Output | Tolerance | Emission Designator | Microprocessor Number | |||||||||||||||||||||||||||||||||
| 1 | 1 | 15C | 13.56000000 | 13.56000000 | |||||||||||||||||||||||||||||||||||||
some individual PII (Personally Identifiable Information) available on the public forms may be redacted, original source may include additional details
This product uses the FCC Data API but is not endorsed or certified by the FCC