Datasheet

ManualsBrandsCHIPDRIVE ManualsofficeCLOUD 4700F

Identive Infrastructure

Reference Manual – version 1.0

CLOUD 47x0 F

Dual Interface Smartcard Readers

Summary of content (98 pages)

PAGE 1
Identive Infrastructure Reference Manual – version 1.
PAGE 2
Reference manual CLOUD 47x0 F Dual Interface Smartcard Readers © Identive GmbH Oskar-Messter-Strasse, 13 85737 Ismaning Germany Phone +49 89 9595 5000 • Fax +49 89 9595 5555
PAGE 3
Document history Date Version Description of change 01/24/2013 1.0 Initial Version Contact information CLOUF 4700 F CLOUD 4710F For sales information, please email sales@identive-infrastructure.
PAGE 4
Table of Contents 1. 2. 3. Legal information ................................................................................................................... 9 1.1. Disclaimers ..................................................................................................................... 9 1.2. Licenses ......................................................................................................................... 9 1.3. Trademarks ..................................................
PAGE 5
.3.2. 5.3.3. 5.4. 5.3.3.1. ATR for contactless storage user tokens ................................................................... 25 5.3.3.2. ATR for ISO/IEC 14443-4 user tokens ....................................................................... 26 Firmware ...................................................................................................................... 27 5.4.1. 6. Supported operating systems ...........................................................................
PAGE 6
.3.3.6. READER_LED_CONTROL_BY_FW ......................................................................... 56 6.3.3.7. READER_RD_WR_USER_AREA ............................................................................. 56 6.3.3.8. READER_GENERIC_ESCAPE ................................................................................. 57 6.3.3.9. READER _CONTROL_CONTACT_SLOT ................................................................. 58 6.3.4. CNTLESS_GET_CARD_INFO ...........................
PAGE 7
.1. Annex A – Status words table ...................................................................................... 91 7.2. Annex B – Sample code using escape commands...................................................... 92 7.3. Annex C – Mechanical drawings .................................................................................. 95 7.3.1. 7.3.2. 7.3.3. 7.3.4. Outline and cable positions ................................................................................... 95 Stand .....
PAGE 8
PAGE 9
CLOUD 47X0 F REFERENCE MANUAL 1. Legal information 1.1. Disclaimers The content published in this document is believed to be accurate. Identive Gmbh does not, however, provide any representation or warranty regarding the accuracy or completeness of its content and regarding the consequences of the use of information contained herein. If this document has the status “Draft”, its content is still under internal review and yet to be formally validated.
PAGE 10
CLOUD 47X0 F REFERENCE MANUAL 10 2. Introduction to the manual 2.1. Objective of the manual This manual provides an overview of the hardware and software features of the CLOUD 47x0 F dual interface smart card readers (CLOUD 4700 F and CLOUD 4710 F). This manual describes in detail interfaces and supported commands available for developers using CLOUD47x0 F in their applications. 2.2. Target audience This document describes the technical implementation of CLOUD 47x0 F.
PAGE 11
CLOUD 47X0 F REFERENCE MANUAL 2.4.
PAGE 12
CLOUD 47X0 F REFERENCE MANUAL 2.5.
PAGE 13
CLOUD 47X0 F REFERENCE MANUAL 2.6. 13 Conventions Bits are represented by lower case ‘b’ where followed by a numbering digit. Bytes are represented by upper case ‘B’ where followed by a numbering digit.
PAGE 14
CLOUD 47X0 F REFERENCE MANUAL 14 3. General information about CLOUD 47x0 F 3.1. CLOUD 47x0 F key benefits With its combination of a modern slim design and its state of the art feature set, CLOUD 4700 F is the perfect desktop reader choice for environments where both contact and contactless smart card support is required while CLOUD 4710 F perfectly fits environments where access to contactless cards with simultaneous access to a contact SAM card is required.
PAGE 15
CLOUD 47X0 F REFERENCE MANUAL 3.3. 15 CLOUD 47x0 F ordering information Item Part number CLOUD 4700 F 905320 CLOUD 4710 F 905324 Standing Base Kit 905412 3.4. Available options The Standing Base Kit consists of a stand and a wireholder. It could be used to either place the reader on the desktop with an angle of 40° in regard to the desk or to mount it to a wall with a 40° angle in regard to that. The wireholder keeps the contactless token in place when using this option. 3.5.
PAGE 16
CLOUD 47X0 F REFERENCE MANUAL 16 3.6. Contactless communication principles and CLOUD 47x0 F usage recommendations CLOUD 47x0 F is a dual interface reader capable of reading both contact smart cards and contactless user tokens. The following paragraph focuses on a few specifics of contactless communication to outline usage recommendations in order to ensure best user experience. CLOUD 47x0 F is a contactless reader1 designed to communicate with user credentials.
PAGE 17
CLOUD 47X0 F REFERENCE MANUAL 17 3.6.3. Recommendations The communication between the reader and the user credential is sensitive to the presence of material or objects interfering with the magnetic field generated by the reader. The presence of conductive materials like metal in the vicinity of the reader and the user credential can significantly degrade the communication and even make it impossible.
PAGE 18
CLOUD 47X0 F REFERENCE MANUAL 18 Network ` RF link (13.56MHz) ISO14443 interface Smartcard contacts ISO7816 CL O 47 UD x0 F USB link PC/SC interface CLOUD 4700 CLOUD 4710 Host CLOUD 47x0 F Credentials/SAM Application logic Interface device Application logic + User personal data for given set of applications CLOUD 47x0 F itself handles the communication protocol but not the application related to the token or card.
PAGE 19
CLOUD 47X0 F REFERENCE MANUAL 19 4. CLOUD 47x0 F characteristics 4.1. CLOUD 47x0 F high level architecture 4.1.1. Block diagram The link between CLOUD 47x0 F and the host to which it is connected is the USB interface providing both the power and the communication channel. To host Device controller RF front-end EMC filter + Matching circuitry Antenna ISO7816 contact smart card interface text text text LED The device controller has several interfaces available.
PAGE 20
CLOUD 47X0 F REFERENCE MANUAL 20 4.1.2. Software architecture Applications can interface with the driver directly through the PC/SC interface. Contactless Reader Contact Reader PC/SC Layer Driver - Contact Smart Card Reader Driver - Contactless Card Reader T= 0 / T= 1 T = CL SLOT 0 FIRMWARE LAYER SLOT 1 CLOUD 47x0 F Reader ICC PICC The CLOUD 47x0 F leverages a PC/SC CCID driver that is freely available for all supported operating systems (Windows, MacOSX and Linux).
PAGE 21
CLOUD 47X0 F REFERENCE MANUAL 4.2. 21 Quick reference data 4.2.1. CLOUD 47x0 F dimensions Item Characteristic Value Weight 143g without stand Stand: 52g External dimensions Cable length Default color 126 mm X 93 mm X 22 mm 1.5 meter long with USB type A connector White and grey CLOUD 4700 F Default label Weight External dimensions Cable length Default color 157g without stand Stand: 52g 113 mm X 93 mm X 22 mm 1.
PAGE 22
CLOUD 47X0 F REFERENCE MANUAL 22 4.2.2. LED behavior CLOUD 47X0 F is equipped with one bicolor LED. Its behavior is described in the table below.
PAGE 23
CLOUD 47X0 F REFERENCE MANUAL 4.2.3.2. 23 USB Parameter Value/Description DC characteristics High bus powered (CLOUD 47x0 F draws power from USB bus) Voltage: 5V Avg.. Current : 110mA (RF on, no cards present) Suspend Current: 400µA USB specification USB 2.0 FS Device USB Speed Device Class PID VID Full Speed Device (12Mbit/s) CCID 0x5720 0x04E6 4.2.3.3.
PAGE 24
CLOUD 47X0 F REFERENCE MANUAL 24 5. Software modules 5.1. Installation On Operating Systems with a CCID driver pre-installed, no installation is necessary. Where there’s no CCID driver pre-installed – e.g. Linux systems or old Windows systems – the driver has to be installed using distribution-specific measures or using the available source packages.
PAGE 25
CLOUD 47X0 F REFERENCE MANUAL 25 5.3.3. PC/SC 2.0 compliant ATR for contactless interface When a user credential is placed on the reader, initialization, anti-collision is done. The user credential is automatically activated and an ATR is built as defined in the PC/SC specification. For further information, please refer to section 3.1.3.2.3 of [PCSC3] and to [PCSC3-SUP] 5.3.3.1. ATR for contactless storage user tokens The ATR of the credential is composed as described in the table below.
PAGE 26
CLOUD 47X0 F REFERENCE MANUAL 5.3.3.2. 26 ATR for ISO/IEC 14443-4 user tokens The credential exposes its ATS or application information which is mapped to an ATR. The table describes how this mapping is done. Byte# Value Designation 0 1 2 0x3B 0x8n 0x80 Initial header T0 TD1 3 0x01 TD2 upper nibble 0 indicates no TA3, TB3, TC3 lower nibble 1 means T=1 Historical bytes or application information Type A: the historical bytes from the ATS (up to 15 bytes) Type B (8 bytes): 4...
PAGE 27
CLOUD 47X0 F REFERENCE MANUAL 5.4. 27 Firmware 5.4.1. CCID transport protocol CLOUD 47x0 F implements a transport protocol that is compliant with USB Device Class: Smart Card CCID Specification for Integrated Circuit(s) Cards Interface Devices Revision 1.10. This paragraph describes the CCID specification features that are implemented. 5.4.1.1.  CCID class requests supported Abort 5.4.1.2.
PAGE 28
CLOUD 47X0 F REFERENCE MANUAL 28 The following sub-sections discuss when and why these error codes are returned: 5.4.1.3.1. HW_ERROR This error code is returned when a hardware short circuit condition is detected, during application of power to the card or if any other internal hardware error is detected. 5.4.1.3.2. XFR_PARITY_ERROR This error code is returned when a parity error condition is detected. This error will be reported in the response to a PC_to_RDR_XfrBlock message. 5.4.1.3.3.
PAGE 29
CLOUD 47X0 F REFERENCE MANUAL 29 6. Commands description 6.1. Generic APDU 6.1.1. Working with DESFire and MIFARE Plus tokens To work with DESFire EV1 and MIFARE Plus tokens, please refer to the according application notes [AN337] and [AN338], respectively. Please note that, since these application notes contain information available only under NDA with NXP, you’d need to sign an NDA with NXP to be allowed to receive them. 6.1.2.
PAGE 30
CLOUD 47X0 F REFERENCE MANUAL 30 Example: 1) To issue the “READER_GETIFDTYPE (0x12)” escape command , this pseudo APDU would be used: Command APDU : FF CC 00 00 01 12 Response : 20 57 90 00 2) To issue the “READER_SETMODE (0X01)” escape command, this pseudo APDU would be used: Command APDU : FF CC 00 00 02 01 01 (to set to EMV mode) Response APDU : 90 00 Note: 1) To send Escape commands using this method, the reader should be connected in shared mode using T0 or T1 protocol.
PAGE 31
CLOUD 47X0 F REFERENCE MANUAL 6.2. 31 Supported Pseudo APDU (Contactless Interface) All Pseudo APDUs specific to Contactless Interface supported in the reader are explained in this section 6.2.1. PAPDU_MIFARE_READ_BINARY This command is used to read data from a Mifare card. Refer to section 3.2.2.1.8 of [PCSC3] for details.
PAGE 32
CLOUD 47X0 F REFERENCE MANUAL 32 6.2.2. PAPDU_MIFARE_UPDATE_BINARY This command is used to update the non-volatile memory of a Mifare card. Refer to section 3.2.2.1.9 of [PCSC3] for further details.
PAGE 33
CLOUD 47X0 F REFERENCE MANUAL 33 6.2.3. PAPDU_MIFARE_LOAD_KEYS This command is used to load the key to the volatile memory of the reader. It can be used for all kinds of contactless cards. Refer to section 3.2.2.1.4 of [PCSC3] for further details.
PAGE 34
CLOUD 47X0 F REFERENCE MANUAL 34 Examples Load Keys – Card – Non-Secure The command to load Mifare key A “FF FFFFFFFFFF” is FF82006006 FFFFFFFFFFFF Load Keys – Card – Secure: If the default AES128 reader is key is 00010203 05060708 0A0B0C0D 0F101112 then the following explains the steps needed to calculate the key for secure mode.
PAGE 35
CLOUD 47X0 F REFERENCE MANUAL 35 6.2.4. PAPDU_MIFARE_AUTHENTICATE This command is used to authenticate using the key number. Refer to section 3.2.2.1.6 of [PCSC3] for further details.
PAGE 36
CLOUD 47X0 F REFERENCE MANUAL 36 6.2.5. PAPDU_MIFARE_READ_SECTOR This command reads the specified sector from a Mifare Classic card (first 3 blocks of the sector, excluding the Key block) or the entire content of Mifare UL/UL C cards.
PAGE 37
CLOUD 47X0 F REFERENCE MANUAL 37 6.2.6. PAPDU_MIFARE_READ_SECTOR_EX This command read the specified sector from a Mifare Classic card (all the 4 blocks of the sector, including the Key block) or the entire content of Mifare UL/UL C cards.
PAGE 38
CLOUD 47X0 F REFERENCE MANUAL 38 6.2.7. PAPDU_MIFARE_WRITE_SECTOR This command writes the contained data to the specified sector of a Mifare classic or Mifare UL/UL C card (first blocks of the sector, excluding the Key block are written in case of Mifare Classic).
PAGE 39
CLOUD 47X0 F REFERENCE MANUAL 39 Response APDU: Data Status Word - SW1, SW2 Example: decrement block 4 by 1 (key loading and authentication not shown) (block 4 has got to be set up as value block prior to executing this command, see datasheet for Mifare Classic cards) APDU: FF B0 00 04 00 // Read Block 4 SW12: 9000 (OK) DataOut: A9 AA AA AA 56 55 55 55 A9 AA AA AA 05 FA 05 FA (16 bytes) APDU: FF F0 00 04 06 C0 04 01 00 00 00 // decrement block 4 by 1 SW12: 9000 (OK) APDU: FF B0 00 04 00 // Read Block
PAGE 40
CLOUD 47X0 F REFERENCE MANUAL 40 6.2.9. PAPDU_MIFARE_VALUE_BLK_NEW This command increments or decrements the value of a data object if the card supports it. Refer to section 3.2.2.1.10 of [PCSC3-AMD1] for further details.
PAGE 41
CLOUD 47X0 F REFERENCE MANUAL 41 Error Status Description XX SW1 SW2 XX = number of the bad data object in the APDU; 00 = general error of APDU; 01 = error in the 1stdata object; 02 = error in the 2nddata object; etc. 00 90 00 No error occurred XX 62 82 Data object XX warning, requested information not available XX 63 00 No information.
PAGE 42
CLOUD 47X0 F REFERENCE MANUAL 6.2.11. Thru) 42 PAPDU_ISO14443_PART3_PASS_THRU (Mifare Pass This command is used to send raw data using Type A standard framing to a card. CRC bytes will be appended automatically. The reader will not add transport protocol data to the raw data – e.g. PCB, NAD, CID etc. Command APDU: Command CLA INS P1 P2 P3 Data Part 3 Passthrough FF EF Transmit CRC 00 Lc Data P1 = 0x00 will transmit the CRC bytes form the card as is to the application.
PAGE 43
CLOUD 47X0 F REFERENCE MANUAL 6.2.13. 43 PAPDU_FELICA_REQC This command Issues REQC as defined in JIS 7.5.1. It is used to detect the presence of a NFC Forum tag type 3 in the field Command APDU: Command CLA INS P1 P2 P3 Data FeliCa REQC FF 40 00 00 04 2 bytes of system code, 1 byte RFU, 1 byte TSN Response APDU: Data Status Word 16 bytes of NFCID2 + 2 bytes of System Code (sent only if the RFU byte is 0x01) SW1, SW2 6.2.14.
PAGE 44
CLOUD 47X0 F REFERENCE MANUAL 6.2.15. 44 PAPDU_FELICA_REQ_RESPONSE This command issues a REQ RESPONSE as defined in JIS 9.6.1. When an NFC Forum tag type 3 receives this command, it responds with its current mode (0/1/2). Command APDU: Command CLA INS P1 P2 P3 Data FeliCa REQ Response FF 44 00 00 00 - Response APDU: Data Status Word 8 bytes IDm + Mode SW1, SW2 6.2.16. PAPDU_FELICA_READ_BLK This command issues a READ as defined in JIS 9.6.
PAGE 45
CLOUD 47X0 F REFERENCE MANUAL 6.2.17. 45 PAPDU_FELICA_WRITE_BLK This command issues a WRITE as defined in JIS 9.6.4   P1 specifies the number of service P2 specifies the number of blocks When an NFC Forum tag type 3 receives this command, it writes the records of the specified service.
PAGE 46
CLOUD 47X0 F REFERENCE MANUAL 6.2.19. 46 PAPDU_NFC_TYPE1_TAG_RID This command issues a RID to get the tag’s identification data. Command APDU: Command CLA INS P1 P2 P3 Data TYPE1 Tag RID FF 50 00 00 00 - Response APDU: Data Status Word HR0 HR1 UID0 UID1 UID2 UID3 SW1, SW2 Where  HR0 and HR1 are the 2 bytes Header ROM which identify the tag  UID0 through UID3 are the first 3 bytes of the tag’s UID.
PAGE 47
CLOUD 47X0 F REFERENCE MANUAL 6.2.21. 47 PAPDU_NFC_TYPE1_TAG_READ This command issues a READ to read a single EEPROM memory byte within the static memory model area of blocks 0x0-0xE.
PAGE 48
CLOUD 47X0 F REFERENCE MANUAL 6.2.23. 48 PAPDU_NFC_TYPE1_TAG_WRITE_NE This command issues a WRITE-NE to write a byte value to one byte within the static memory model area of blocks 0x0-0xE. It does not erase the value of the targeted byte before writing the new data. Execution time of this command for NFC Forum tags type 1 is approximately half that of the normal write command (WRITE-E). Using this command, EEPROM bits can only be set, not reset.
PAGE 49
CLOUD 47X0 F REFERENCE MANUAL 6.2.24. 49 PAPDU_NFC_TYPE1_TAG_RSEG This command issues a RSEG to read out a complete segment (or block) of the memory within dynamic memory model. Please note that this command works only on specific Topaz tags in the dynamic memory model.
PAGE 50
CLOUD 47X0 F REFERENCE MANUAL 6.2.26. 50 PAPDU_NFC_TYPE1_TAG_WRITE_E8 This command issues a WRITE8 to erase and then write a block of eight bytes. Please note that this command only works on Topaz tags in dynamic memory model.
PAGE 51
CLOUD 47X0 F REFERENCE MANUAL 6.3. 51 Escape commands for the CLOUD 47x0 F With Amendment 1 of the PC/SC specification, Part 3, a method to define vendor specific commands has been introduced. CLOUD 47x0 F provides the command READER_GENERIC_ESCAPE to send commands using this method. However, most of the escape commands listed here are not defined according to this method because of backward compatibility reasons. All newly defined commands will adhere to this new standard.
PAGE 52
CLOUD 47X0 F REFERENCE MANUAL 52 6.3.2. Escape command codes Escape commands can be used by an application to configure CLOUD 47x0 F to function in a mode that is not its default configured mode or to get specific information. To put the CLOUD 47x0 F back into its default mode, it either has to be unplugged and plugged again or the application can send the same Escape command again. The following Escape commands are supported by CLOUD 47x0 F: 6.3.3.
PAGE 53
CLOUD 47X0 F REFERENCE MANUAL 53 The following table defines the values for the Mode parameter: Mode Value Remarks ISO 7816 0x00 ISO 7816 mode – Applicable for both contact slot and contactless slot EMV 0x01 EMV – Applicable only for contact slot and ignored by contactless interface Synchronous 0x02 Memory card mode (Synchronous) – Applicable only for contact slot and ignored by contactless interface NFC Test 0x04 NFC Test Mode – Applicable only for contactless interface ISO mode uses APDU
PAGE 54
CLOUD 47X0 F REFERENCE MANUAL 6.3.3.3. 54 READER_GET_IFDTYPE This Escape command is used to get the current IFD type from the reader. Input: The first byte of the input buffer contains the escape code. Byte0 Escape code(0x12) Output: The reader returns its PID LSB first.
PAGE 55
CLOUD 47X0 F REFERENCE MANUAL 6.3.3.5. 55 READER_GET_INFO_EXTENDED This Escape command is used to get the firmware version, reader capabilities, and Unicode serial number of the reader. Input: The first byte of the input buffer contains the escape code. Byte0 Escape code(0x1E) Output: The firmware will return data as per structure SCARD_READER_GETINFO_PARAMS_EX mentioned below.
PAGE 56
CLOUD 47X0 F REFERENCE MANUAL 6.3.3.6. 56 READER_LED_CONTROL_BY_FW This Escape command is used to enable/disable LED control by firmware. Input: The first byte of the input buffer contains the escape code. The second byte specifies if LED control by firmware should be disabled or enabled. The output buffer is NULL.
PAGE 57
CLOUD 47X0 F REFERENCE MANUAL 57 Input: The first byte of the input buffer contains the escape code. The second byte specifies if user area is to be read or written as described below. Byte1 Byte0 Byte2 to Byte251 Value Description 1 Read 249 bytes of user data None 2 Write 249 bytes of user data Data to be written Escape code(0xF0) Output: Operation Data (Byte0-BYTE248) Read 249 bytes of user data Write No bytes returned 6.3.3.8.
PAGE 58
CLOUD 47X0 F REFERENCE MANUAL 6.3.3.9. 58 READER _CONTROL_CONTACT_SLOT This Escape command is supported through the READER_GENERIC_ESCAPE message. This command can be used to disable the contact slot until it is re-enabled through the same command or until the reader is re-plugged. When a dual interface card is placed in the contact slot it will get detected in both “contact” and “contactless” mode.
PAGE 59
CLOUD 47X0 F REFERENCE MANUAL 59 6.3.4.
PAGE 60
CLOUD 47X0 F REFERENCE MANUAL Output: Byte0 Contactless card present (0x01) 60 Byte1 Byte2 Card to Reader communication baud rate (0xNN - see table below for details) Card Type Info (Upper nibble indicates memory card/T=CL/dual mode card; Lower nibble indicates Type A/ Type B card See Table below for values) Card to Reader communication baud rate BYTE is defined as follows: b0 – 212kbps supported (direction reader to card) b1 – 424kbps supported (direction reader to card) b2 – 848kbps supported (dir
PAGE 61
CLOUD 47X0 F REFERENCE MANUAL 6.3.4.2. 61 CNTLESS_GET_ATS_ATQB This Escape command retrieves the ATS for Type A T= CL or the ATQB for Type B cards. Input: The first byte of input buffer contains the escape code. Byte0 Escape code(0x93) Output: The output buffer contains the ATS bytes or the ATQB bytes depending on the type of PICC placed on the reader 6.3.4.3. CNTLESS_CONTROL_PPS This Escape command disables the automatic PPS done by the firmware/device for contactless cards.
PAGE 62
CLOUD 47X0 F REFERENCE MANUAL 6.3.4.4. 62 CNTLESS_RF_SWITCH This Escape command can be used to switch the RF field ON or OFF. Input: The first byte of input buffer contains the escape code. The second byte either sets the mode or contains a code to retrieve the setting.
PAGE 63
CLOUD 47X0 F REFERENCE MANUAL 63 Output: No response is returned for set state. For Get State 1 byte response is received. Output buffer NULL or current state 6.3.4.6. CNTLESS_GET_BAUDRATE This Escape command is used to get the current baud rate of card-reader communication. Input: The first byte of input buffer contains the escape code.
PAGE 64
CLOUD 47X0 F REFERENCE MANUAL 6.3.4.7. 64 CNTLESS_CONTROL_RETRIES This Escape command is used to enable/disable CRC/PROTOCOL/TIMEOUT error retries which are enabled by default for contactless cards. Input: The first byte of input buffer contains the escape code. The second byte either sets the mode or contains a code to retrieve the setting.
PAGE 65
CLOUD 47X0 F REFERENCE MANUAL 6.3.4.8. 65 CNTLESS_CONTROL_POLLING This Escape command is used to enable/disable firmware polling for contactless cards. Input: The first byte of input buffer contains the escape code. The second byte either sets the mode or contains a code to retrieve the setting.
PAGE 66
CLOUD 47X0 F REFERENCE MANUAL 66 Output: Byte # B0 B1 B2 Value Description 0x00 Type A card 0x01 Type B card 0x04 FeliCa 212 0x08 FeliCa 424 0x00 Memory card 0x01 T-CL card 0x02 Dual interface card 0x43 FeliCa 0x44 Topaz 0x45 B-prime 0x46 i-Class ‘xx’ ‘xx’ is the PUPI / UID Length 0x08 For FeliCa cards THEN EITHER PUPI/UID bytes B3-B12 0x00 byte padding used if length smaller than 10 B13 B14 0x00 CID not supported 0x01 CID supported 0x00 NAD not supported 0x01 NAD
PAGE 67
CLOUD 47X0 F REFERENCE MANUAL 67 6.3.4.10. CNTLESS_SET_CONFIG_PARAMS This Escape command is used to configure RXGAIN and RXTHRESHOLD of the RF receiver for different baud rates and card types. All configured parameters are volatile. Input: The first byte of input buffer contains the escape code. The following 16 bytes contain the below defined parameters.
PAGE 68
CLOUD 47X0 F REFERENCE MANUAL 68 6.3.4.11. CNTLESS_IS_COLLISION_DETECTED This Escape command is used to identify if multiple Type A cards are detected in the field. Input: The first byte of input buffer contains the escape code. Byte0 Escape code(0xE4) Output: Byte0 Value Description 0x00 Collision is not detected 0x01 Collision is detected 6.3.4.12. CNTLESS_FELICA_PASS_THRU This Escape command is used as a pass through to send FeliCa commands to FeliCa cards.
PAGE 69
CLOUD 47X0 F REFERENCE MANUAL 69 6.3.4.13. CNTLESS_P2P_SWITCH_MODES This Escape command is used to switch the device between the reader/writer and P2P modes of operation and to query the current mode. By default, the device is in the reader/writer mode. Input: The first byte of input buffer contains the escape code. The second byte either sets the mode or contains a code to retrieve the setting. Additional data bytes will be needed for Initiator/Target mode.
PAGE 70
CLOUD 47X0 F REFERENCE MANUAL 70 Target Mode Bytes Offset Detailed description (Sample Values) 2 0x00 RFU 3 0x00 RFU 4 0x04 SENS_RES 5 0x03 SENS_RES 6 0x01 NFCID1 7 0xFE NFCID1 8 0x0F NFCID1 9 0x40 SEL_RES 10 0x01 NFCID2 11 0xFE NFCID2 12 0x0F NFCID2 13 0xBB NFCID2 14 0xBA NFCID2 15 0xA6 NFCID2 16 0xC9 NFCID2 17 0x89 NFCID2 18 C0 FeliCa Padding Bytes 19 C1 FeliCa Padding Bytes 20 C2 FeliCa Padding Bytes 21 C3 FeliCa Padding Bytes 22 C4 Feli
PAGE 71
CLOUD 47X0 F REFERENCE MANUAL Output Buffer:  Initiator Mode : On successful detection of target, the entire ATR_RES buffer from the target device would be given to the host computer  Target Mode : On successful detection by the initiator the entire ATR_REQ buffer from the initiator device would be given to the host computer  Reader Mode : The output buffer would be empty  Get Current Mode : A single byte response indicating the currently selected mode as described below o 0x00 => P2P Initiator
PAGE 72
CLOUD 47X0 F REFERENCE MANUAL 72 6.3.4.14. CNTLESS_P2P_TARGET_RECEIVE This Escape command is used to receive data from the initiator device. Prior to using this command, the device should have been successfully switched to target mode using CNTLESS_P2P_SWITCH_MODES (E9).
PAGE 73
CLOUD 47X0 F REFERENCE MANUAL 73 6.3.4.15. CNTLESS_P2P_TARGET_SEND This Escape command is used to send data to an initiator device. Prior to using this command, the device should have been successfully switched to target mode using CNTLESS_P2P_SWITCH_MODES (E9).
PAGE 74
CLOUD 47X0 F REFERENCE MANUAL 74 6.3.4.17. CNTLESS_P2P_INITIATOR_TRANCEIVE This Escape command is used to send data to a target device. Prior to using this command, the device should have been successfully switched to initiator mode using CNTLESS_P2P_SWITCH_MODES (E9).
PAGE 75
CLOUD 47X0 F REFERENCE MANUAL 75 6.3.4.18. CNTLESS_NFC_SINGLESHOT This Escape command is used to switch the device to Single-shot mode. Input: Offset Description 0 0xEC Detailed description NFC Single-shot NFC_DEP supported. 1 0x01 If a value other than 0x01 is given, NFC_DEP is not supported in the preceding I-Blocks. Output: Output buffer NULL 6.3.4.19. CNTLESS_NFC_LOOPBACK This Escape command is used to switch the device to Loop-back mode.
PAGE 76
CLOUD 47X0 F REFERENCE MANUAL 76 6.3.4.20. CNTLESS_GET_SET_NFC_PARAMS This Escape command is supported through the READER_GENERIC_ESCAPE command. During NFC operation, number parameters like DID, LRi, PSL_REQ_BRS and PSL_REQ_FSL can be controlled from application.
PAGE 77
CLOUD 47X0 F REFERENCE MANUAL 77 6.3.4.21. CNTLESS_GET_P2P_EXTERNAL_RF_STATE This Escape command is supported through the READER_GENERIC_ESCAPE message. This command is used to check if external RF is reset after the reader got detected in target mode. Input: Byte0 Byte1 Byte2 Byte3 Byte4 CLA INS P1 P2 Lc 0xFF 0x70 0x04 0xE6 0x01 Byte5 0x06 (opcode) Le 00 Output: If the command is successful, a single byte is returned. This byte indicates the value of parameter.
PAGE 78
CLOUD 47X0 F REFERENCE MANUAL 78 6.3.5.
PAGE 79
CLOUD 47X0 F REFERENCE MANUAL 6.3.5.1. 79 CONTACT_GET_SET_PWR_UP_SEQUENCE This Escape command is used to get or set the following parameters:    Smart card Power-on sequence Delay between successive Activation retires Enable/Disable any Voltage Class As soon as card insertion is detected and Power ON message is received from the host, the firmware will start Activation with the configured voltage sequence.
PAGE 80
CLOUD 47X0 F REFERENCE MANUAL 80 Output: For retrieving all settings (0xFE), the output will be: Byte0 Byte 1 Value Description 0x00 Starts with Class C voltage. (1.8V – 3V – 5V order) 0x01 Starts with Class A voltage. (5V – 3V – 1.
PAGE 81
CLOUD 47X0 F REFERENCE MANUAL 6.3.5.3. 81 CONTACT_EMV_SINGLEMODE This Escape command lets the host perform a one-shot EMV Loop-back application as specified in the EMV Level 1 Testing Requirements document. Input: Byte0 Escape code(0x06) Output: Output buffer NULL 6.3.5.4. CONTACT_EMV_TIMERMODE This Escape command lets the host perform a timer mode EMV Loop-back application as specified in the EMV Level 1 Testing Requirements document Input: The input buffer contains the escape code value.
PAGE 82
CLOUD 47X0 F REFERENCE MANUAL 6.3.5.5. 82 CONTACT_APDU_TRANSFER This Escape command exchanges a short APDU with the smart card. The user has to ensure that a card is inserted and powered before issuing this Escape command. This Escape command mostly is used by the MCard API to access synchronous memory cards. Input: The input buffer contains the Escape code value followed by the short APDU to be sent to the card.
PAGE 83
CLOUD 47X0 F REFERENCE MANUAL 6.3.5.7. 83 CONTACT_EXCHANGE_RAW This Escape command can be used to perform raw exchange of data with the card. The user must ensure that a card is inserted and powered on before issuing this Escape command. The Card is deactivated upon any reception error.
PAGE 84
CLOUD 47X0 F REFERENCE MANUAL 6.3.5.8. 84 CONTACT_GET_SET_CLK_FREQUENCY This Escape command is used to instruct the reader to change the clock for the smart card or to get the current Clock divisor used. Once set, the change in frequency will take effect immediately. Default divisor value is 10, that is 4.8MHz. Input: The first byte of the input buffer contains the Escape code; the next byte contains the clock divisor value to set the clock frequency or 0xFF to get the clock frequency.
PAGE 85
CLOUD 47X0 F REFERENCE MANUAL 6.3.5.9. 85 CONTACT_CONTROL_ATR_VALIDATION This Escape command is used to enable or disable the ATR validation by the firmware in ISO/IEC 7816 mode. In case the card would emit an ATR that is not ISO/IEC 7816 compliant, the card reader may fail to power up the card. In these cases, disabling ATR validation will let you work with the card regardless of ISO conformity of the ATR. By default, ATR validation is enabled.
PAGE 86
CLOUD 47X0 F REFERENCE MANUAL 86 6.3.5.10. CONTACT_GET_SET_MCARD_TIMEOUT This Escape command is used to get or set the delay which is applied after a Write operation to memory cards. The delay is specified in milliseconds. Input: The first byte of the input buffer will contain the Escape code; the next byte will contain the memory card write delay in seconds.
PAGE 87
CLOUD 47X0 F REFERENCE MANUAL 87 6.3.5.11. CONTACT_GET_SET_ETU This Escape command is used by the HOST to get/set the current ETU for smart cards. Once set, the new ETU value will take effect immediately. Input: The input buffer contains the Escape code followed by an 8 bit GET/SET identifier. For SET ETU, a DWORD specifying the value to be set is following.
PAGE 88
CLOUD 47X0 F REFERENCE MANUAL 88 6.3.5.12. CONTACT_GET_SET_WAITTIME This Escape command is used to get/set the Character/Block Waiting Time for smartcards. The wait time is specified in terms of ETU. Once set, the new Wait time will take effect from the next card communication. Input: The input buffer contains the Escape code followed by an 8 bit GET/SET identifier, an 8 bit Wait time identifier and a 32 bit Wait time value. BWT must be specified in units of 1.25ms and CWT in units of ETU.
PAGE 89
CLOUD 47X0 F REFERENCE MANUAL 89 6.3.5.13. CONTACT_GET_SET_GUARDTIME This Escape command is used to get/set the Character/Block Guard Time of the reader. The guard time is specified in terms of ETU. Once set, the new Guard time will take effect immediately. Input: The input buffer contains the Escape code followed by an 8 bit GET/SET identifier, an 8 bit guard time identifier and a 32 bit guard time value in ETU.
PAGE 90
CLOUD 47X0 F REFERENCE MANUAL 90 6.3.5.14. CONTACT_READ_INSERTION_COUNTER This Escape command is supported through the READER_GENERIC_ESCAPE command and retrieves the number of times a contact smart card has been inserted into the reader. Input: The first five bytes of the input buffer follow APDU structure as per [PCSC3-AMD1]. The 6thbyte is the Escape code 0x00 to identify the command.
PAGE 91
CLOUD 47X0 F REFERENCE MANUAL 7. Annexes 7.1.
PAGE 92
CLOUD 47X0 F REFERENCE MANUAL 7.2. 92 Annex B – Sample code using escape commands File Name: CLOUD 47x0 F Escape.
PAGE 93
CLOUD 47X0 F REFERENCE MANUAL 93 File Name: CLOUD 47x0 F Escape.c #include #include #include #include #include #include #include "winscard.h" "winerror.h" "CLOUD 47x0F Escape.
PAGE 94
CLOUD 47X0 F REFERENCE MANUAL ret = SCardReleaseContext(ContextHandle); } else { printf("\n SCardEstablishContext failed with %.
PAGE 95
CLOUD 47X0 F REFERENCE MANUAL 7.3. Annex C – Mechanical drawings 7.3.1.
PAGE 96
CLOUD 47X0 F REFERENCE MANUAL 7.3.2.
PAGE 97
CLOUD 47X0 F REFERENCE MANUAL 7.3.3.
PAGE 98
CLOUD 47X0 F REFERENCE MANUAL 7.3.4.