free hit counter
Identive CLOUD 47x0 F Reference Manual
  1. Manuals
  2. Brands
  3. Identive Manuals
  4. Card Reader
  5. CLOUD 47x0 F
  6. Reference manual

Identive CLOUD 47x0 F Reference Manual

Dual interface smartcard readers
Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
Identive Infrastructure
Reference Manual – version 1.0
CLOUD 47x0 F
Dual Interface Smartcard Readers

Advertisement

Table of Contents
loading

Related Manuals for Identive CLOUD 47x0 F

Summary of Contents for Identive CLOUD 47x0 F

  • Page 1 Identive Infrastructure Reference Manual – version 1.0 CLOUD 47x0 F Dual Interface Smartcard Readers...
  • 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 Initial Version Contact information CLOUF 4700 F CLOUD 4710F For sales information, please email sales@identive-infrastructure.com...

  • Page 4: Table Of Contents

    CLOUD 47x0 F ordering information ................15 3.4. Available options ......................15 3.5. CLOUD 47x0 F customization options ................. 15 3.6. Contactless communication principles and CLOUD 47x0 F usage recommendations 16 3.6.1. Power supply......................16 3.6.2. Data exchange ...................... 16 3.6.3.
  • Page 5 6.2.24. PAPDU_NFC_TYPE1_TAG_RSEG ..............49 6.2.25. PAPDU_NFC_TYPE1_TAG_READ8 ..............49 6.2.26. PAPDU_NFC_TYPE1_TAG_WRITE_E8 ............. 50 6.2.27. PAPDU_NFC_TYPE1_TAG_WRITE_NE8 ............50 6.3. Escape commands for the CLOUD 47x0 F ..............51 6.3.1. Sending Escape commands to CLOUD 47x0 F ........... 51 6.3.2. Escape command codes ..................52 6.3.3.
  • Page 6 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. Specific for Contactless Interface ................. 59 6.3.4.1. CNTLESS_GET_CARD_INFO .................. 59 6.3.4.2. CNTLESS_GET_ATS_ATQB ..................61 6.3.4.3. CNTLESS_CONTROL_PPS ..................61 6.3.4.4. CNTLESS_RF_SWITCH ................... 62 6.3.4.5.
  • Page 7 Annex A – Status words table ..................91 7.1. Annex B – Sample code using escape commands ............92 7.2. Annex C – Mechanical drawings .................. 95 7.3. 7.3.1. Outline and cable positions ................... 95 7.3.2. Stand ........................96 7.3.3. Reader mounted to Stand ..................

  • Page 9: 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...

  • Page 10: 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.

  • Page 11: Definition Of Various Terms And Acronyms

    CLOUD 47 0 F R EFERENCE ANUAL 2.4. Definition of various terms and acronyms Term Expansion APDU Application Protocol Data Unit Answer to Reset, defined in ISO7816 Answer to select, defined in ISO/IEC 14443 Byte Group of 8 bits CCID Chip Card Interface Device Card Identifier Device Firmware Upgrade...

  • Page 12: References

    Part 3. Supplemental Document for Contactless ICCs CCID Specification for Integrated Circuit(s) Cards USB-IF Interface Devices 1.1 Universal Serial Bus Specification 2.0 USB-IF AN337 Application Note describing handling of DESFire Identive EV1 cards AN338 Application Note describing handling of MIFARE Identive Plus cards...

  • Page 13: Conventions

    CLOUD 47 0 F R EFERENCE ANUAL 2.6. 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. Bit number 5 Bit number 0 Most significant nibble Least significant nibble 1 Byte = 8 bits = 2 nibbles...

  • Page 14: General Information About Cloud 47X0 F

    CLOUD 4710 F perfectly fits environments where access to contactless cards with simultaneous access to a contact SAM card is required. As for all Identive GmbH products, CLOUD 47x0 F is designed to offer best in class interoperability.

  • Page 15: Cloud 47X0 F Ordering Information

    Upon request, Identive GmbH can consider customizing:  The color of the casing  The logo  The product label  The USB strings Terms and conditions apply, please contact your local Identive representative or send an email to sales@identive-infrastructure.com.

  • Page 16: Contactless Communication Principles And Cloud 47X0 F Usage Recommendations

    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.

  • Page 17: Recommendations

    {reader, credential}. Parameters like the geometry and especially the relative size of the reader’s and credential’s antennas directly influence the inductive coupling and therefore the communication. CLOUD 47x0 F was designed and optimized to function with user credentials of various technologies and sizes. ...

  • Page 18: Applications Provided By Identive Gmbh

    Interface device 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. The application-specific logic has to be implemented by software developers on the host.

  • Page 19: 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. ISO7816 contact smart card interface...

  • Page 20: Software Architecture

    Reader PICC The CLOUD 47x0 F leverages a PC/SC CCID driver that is freely available for all supported operating systems (Windows, MacOSX and Linux). With current Windows versions (starting with Windows Vista) and MacOSX, this driver is already included in the basic installation.

  • Page 21: Quick Reference Data

    113 mm X 93 mm X 22 mm dimensions Cable length 1.5 meter long with USB type A connector Default color White and grey CLOUD 4710 F Default label Drawing with dimensions of the CLOUD 47X0 F and accessories can be found in annex.

  • Page 22: Led Behavior

    CLOUD 47 0 F R EFERENCE ANUAL 4.2.2. LED behavior CLOUD 47X0 F is equipped with one bicolor LED. Its behavior is described in the table below. Reader states GREEN Just after plug-in (with drivers already installed) Just after DFU operation...

  • Page 23: Usb

    0 F R EFERENCE ANUAL 4.2.3.2. Parameter Value/Description High bus powered (CLOUD 47x0 F draws power from USB bus) Voltage: 5V DC characteristics Avg.. Current : 110mA (RF on, no cards present) Suspend Current: 400µA USB 2.0 FS Device USB specification...

  • Page 24: Software Modules

    Nevertheless, due to some limitations of the available CCID drivers under some circumstances, Identive does provide a dedicated driver for this reader, as well, which is available through Windows Update or on the Identive support pages.

  • Page 25: Pc/Sc 2.0 Compliant Atr For Contactless Interface

    CLOUD 47 0 F R EFERENCE ANUAL 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.

  • Page 26: Atr For Iso/Iec 14443-4 User Tokens

    CLOUD 47 0 F R EFERENCE ANUAL 5.3.3.2. 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 Description 0x3B Initial header 0x8n...

  • Page 27: Firmware

    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.
  • Page 28 CLOUD 47 0 F R EFERENCE ANUAL 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.

  • Page 29: Commands Description

    CLOUD 47 0 F R EFERENCE ANUAL 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.
  • Page 30 CLOUD 47 0 F R EFERENCE ANUAL 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)

  • Page 31: Supported Pseudo Apdu (Contactless Interface)

    CLOUD 47 0 F R EFERENCE ANUAL 6.2. 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: Papdu_Mifare_Update_Binary

    CLOUD 47 0 F R EFERENCE ANUAL 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. Command APDU Command Data Update Binary 0xFF 0xD6 Addr MSB Addr LSB data For a description of P1 and P2, see...

  • Page 33: Papdu_Mifare_Load_Keys

    CLOUD 47 0 F R EFERENCE ANUAL 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. Command APDU: Command...
  • Page 34 CLOUD 47 0 F R EFERENCE ANUAL 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: Papdu_Mifare_Authenticate

    CLOUD 47 0 F R EFERENCE ANUAL 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. Command APDU: Command Data General Authenticate 0xFF 0x86 0x00 0x00 0x05 data the data structure is defined as follows: Byte # Value...

  • Page 36: Papdu_Mifare_Read_Sector

    CLOUD 47 0 F R EFERENCE ANUAL 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. Command APDU: Command Data Read Sector...

  • Page 37: Papdu_Mifare_Read_Sector_Ex

    CLOUD 47 0 F R EFERENCE ANUAL 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. Command APDU: Command Data...

  • Page 38: Papdu_Mifare_Write_Sector

    CLOUD 47 0 F R EFERENCE ANUAL 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 47 0 F R EFERENCE ANUAL 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...

  • Page 40: Papdu_Mifare_Value_Blk_New

    CLOUD 47 0 F R EFERENCE ANUAL 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. Command APDU: Command Data Increment/ BER- Decrement The data object consists of a TLV structure that defines, which action should be performed, which block the actions pertain to (the destination(s)) and which value should be applied for the...

  • Page 41: Papdu_Tcl_Pass_Thru (T=Cl Pass Thru)

    CLOUD 47 0 F R EFERENCE ANUAL 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 1 data object; 02 = error in the 2 data object;...

  • Page 42: Papdu_Iso14443_Part3_Pass_Thru (Mifare Pass Thru)

    CLOUD 47 0 F R EFERENCE ANUAL 6.2.11. PAPDU_ISO14443_PART3_PASS_THRU (Mifare Pass Thru) 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 –...

  • Page 43: Papdu_Felica_Reqc

    CLOUD 47 0 F R EFERENCE ANUAL 6.2.13. 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 Data 2 bytes of system code, FeliCa REQC 1 byte RFU, 1 byte TSN Response APDU:...

  • Page 44: Papdu_Felica_Req_Response

    CLOUD 47 0 F R EFERENCE ANUAL 6.2.15. 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 Data FeliCa REQ Response...

  • Page 45: Papdu_Felica_Write_Blk

    CLOUD 47 0 F R EFERENCE ANUAL 6.2.17. 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: Papdu_Nfc_Type1_Tag_Rid

    CLOUD 47 0 F R EFERENCE ANUAL 6.2.19. PAPDU_NFC_TYPE1_TAG_RID This command issues a RID to get the tag’s identification data. Command APDU: Command Data TYPE1 Tag RID Response APDU: Data Status Word HR0 HR1 UID0 UID1 UID2 UID3 SW1, SW2 Where ...

  • Page 47: Papdu_Nfc_Type1_Tag_Read

    CLOUD 47 0 F R EFERENCE ANUAL 6.2.21. 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. Command APDU: Command Data TYPE1 Tag Byte Addr READ Where P2 codes the address of the memory byte in the following way: Bit numbers Description b7 –...

  • Page 48: Papdu_Nfc_Type1_Tag_Write_Ne

    CLOUD 47 0 F R EFERENCE ANUAL 6.2.23. 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.

  • Page 49: Papdu_Nfc_Type1_Tag_Rseg

    CLOUD 47 0 F R EFERENCE ANUAL 6.2.24. 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: Papdu_Nfc_Type1_Tag_Write_E8

    CLOUD 47 0 F R EFERENCE ANUAL 6.2.26. 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. Command APDU: Command Data TYPE1 Tag...

  • Page 51: Escape Commands For The Cloud 47X0 F

    Please note, that SCardTransmit will only work when connected to a card. In Windows, in order to be able to send Escape commands for the CLOUD 47x0 F, the feature has got to be enabled by setting a REG_DWORD value named ‘EscapeCommandEnable’ in the registry to a value of ‘1’.

  • Page 52: Escape Command Codes

    ANUAL 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.

  • Page 53: Reader_Getmode

    CLOUD 47 0 F R EFERENCE ANUAL The following table defines the values for the Mode parameter: Mode Value Remarks ISO 7816 mode – Applicable for both contact slot and contactless ISO 7816 0x00 slot EMV – Applicable only for contact slot and ignored by contactless 0x01 interface Memory card mode (Synchronous) –...

  • Page 54: Reader_Get_Ifdtype

    PID value Description 0x20 0x57 Identive CLOUD 4700 F Dual Interface Reader 0x21 0x57 Identive CLOUD 4710 F Contactless + SAM Reader 0x10 0x57 Identive CLOUD 2700 F Smart Card Reader 0x50 0x57 Identive CLOUD 2910 F Smart Card Keyboard Reader 6.3.3.4.

  • Page 55: Reader_Get_Info_Extended

    CLOUD 47 0 F R EFERENCE ANUAL 6.3.3.5. 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:...

  • Page 56: Reader_Led_Control_By_Fw

    CLOUD 47 0 F R EFERENCE ANUAL 6.3.3.6. 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. Byte1 Byte0 Value...

  • Page 57: Reader_Generic_Escape

    CLOUD 47 0 F R EFERENCE ANUAL 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 Byte2 to Byte251 Byte0 Value Description Read 249 bytes of user data...

  • Page 58: Reader _Control_Contact_Slot

    (opcode) status Byte2 and Byte3 constitute the world wide unique vendor ID as assigned by the USB organization. For Identive based readers Byte2 = 0x04 and Byte3 = 0xE6 since it USB Vendor ID is 0x04E6 Output: If the command is successful, a single byte is returned. This byte indicates the status of contact slot which needs to be interpreted as below.

  • Page 59: Specific For Contactless Interface

    CLOUD 47 0 F R EFERENCE ANUAL 6.3.4. Specific for Contactless Interface ESCAPE COMMAND ESCAPE CODE CNTLESS_GETCARDINFO 0x11 CNTLESS_GET_ATS_ATQB 0x93 CNTLESS_CONTROL_PPS 0x99 CNTLESS_RF_SWITCH 0x96 CNTLESS_SWITCH_RF_ON_OFF 0x9C CNTLESS_GET_BAUDRATE 0x9E CNTLESS_CONTROL_RETRIES 0xA7 CNTLESS_CONTROL_POLLING 0xAC CNTLESS_GET_CARD_DETAILS 0xDA CNTLESS_SET_CONFIG_PARAMS 0xE1 CNTLESS_IS_COLLISION_DETECTED 0xE4 CNTLESS_FELICA_PASS_THRU 0xF3 CNTLESS_P2P_SWITCH_MODES 0xE9 CNTLESS_P2P_TARGET_RECEIVE...
  • Page 60 CLOUD 47 0 F R EFERENCE ANUAL Output: Byte0 Byte1 Byte2 Card Type Info (Upper nibble indicates Card to Reader communication memory card/T=CL/dual Contactless card present baud rate (0xNN - see table mode card; (0x01) below for details) Lower nibble indicates Type A/ Type B card See Table below for values) Card to Reader communication baud rate BYTE is defined as follows:...

  • Page 61: Cntless_Get_Ats_Atqb

    CLOUD 47 0 F R EFERENCE ANUAL 6.3.4.2. 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...

  • Page 62: Cntless_Rf_Switch

    CLOUD 47 0 F R EFERENCE ANUAL 6.3.4.4. 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. Byte1 Output Byte0...

  • Page 63: Cntless_Get_Baudrate

    CLOUD 47 0 F R EFERENCE ANUAL 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: Cntless_Control_Retries

    CLOUD 47 0 F R EFERENCE ANUAL 6.3.4.7. 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. Input Output Byte0...

  • Page 65: Cntless_Control_Polling

    CLOUD 47 0 F R EFERENCE ANUAL 6.3.4.8. 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. Input Output Byte0...
  • Page 66 CLOUD 47 0 F R EFERENCE ANUAL Output: Byte # 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...

  • Page 67: Cntless_Set_Config_Params

    CLOUD 47 0 F R EFERENCE ANUAL 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: Cntless_Is_Collision_Detected

    CLOUD 47 0 F R EFERENCE ANUAL 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...

  • Page 69: Cntless_P2P_Switch_Modes

    CLOUD 47 0 F R EFERENCE ANUAL 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.
  • Page 70 CLOUD 47 0 F R EFERENCE ANUAL Target Mode Bytes Offset Detailed description (Sample Values) 0x00 0x00 0x04 SENS_RES 0x03 SENS_RES 0x01 NFCID1 0xFE NFCID1 0x0F NFCID1 0x40 SEL_RES 0x01 NFCID2 0xFE NFCID2 0x0F NFCID2 0xBB NFCID2 0xBA NFCID2 0xA6 NFCID2 0xC9 NFCID2...
  • Page 71 CLOUD 47 0 F R EFERENCE ANUAL 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 ...

  • Page 72: Cntless_P2P_Target_Receive

    CLOUD 47 0 F R EFERENCE ANUAL 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). Input Buffer: Offset Description Detailed description...

  • Page 73: Cntless_P2P_Target_Send

    CLOUD 47 0 F R EFERENCE ANUAL 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, device should have been successfully switched target mode using CNTLESS_P2P_SWITCH_MODES (E9). Input: Offset Description Detailed description 0xEB Target Send...

  • Page 74: Cntless_P2P_Initiator_Tranceive

    CLOUD 47 0 F R EFERENCE ANUAL 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 initiator mode using CNTLESS_P2P_SWITCH_MODES (E9). Input: Offset Description Detailed description 0xE7...

  • Page 75: Cntless_Nfc_Singleshot

    CLOUD 47 0 F R EFERENCE ANUAL 6.3.4.18. CNTLESS_NFC_SINGLESHOT This Escape command is used to switch the device to Single-shot mode. Input: Offset Description Detailed description 0xEC NFC Single-shot NFC_DEP supported. 0x01 If a value other than 0x01 is given, NFC_DEP supported preceding I-Blocks.

  • Page 76: Cntless_Get_Set_Nfc_Params

    CLOUD 47 0 F R EFERENCE ANUAL 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. Input: To set the parameters the command syntax is: Byte0 Byte1 Byte2...

  • Page 77: Cntless_Get_P2P_External_Rf_State

    CLOUD 47 0 F R EFERENCE ANUAL 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...

  • Page 78: Specific For Contact Interface

    CLOUD 47 0 F R EFERENCE ANUAL 6.3.5. Specific for Contact Interface ESCAPE COMMAND Escape code CONTACT_GET_SET_PWR_UP_SEQUENCE 0x04 CONTACT_EMV_LOOPBACK 0x05 CONTACT_EMV_SINGLEMODE 0x06 CONTACT_EMV_TIMERMODE 0x07 CONTACT_APDU_TRANSFER 0x08 CONTACT_DISABLE_PPS 0x0F CONTACT_EXCHANGE_RAW 0x10 CONTACT_GET_SET_CLK_FREQUENCY 0x1F CONTACT_CONTROL_ATR_VALIDATION 0x88 CONTACT_GET_SET_MCARD_TIMEOUT 0x85 CONTACT_GET_SET_ETU 0x80 CONTACT_GET_SET_WAITTIME 0x81 CONTACT_GET_SET_GUARDTIME 0x82 CONTACT_READ_INSERTION_COUNTER...

  • Page 79: Contact_Get_Set_Pwr_Up_Sequence

    CLOUD 47 0 F R EFERENCE ANUAL 6.3.5.1. 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: Contact_Emv_Loopback

    CLOUD 47 0 F R EFERENCE ANUAL Output: For retrieving all settings (0xFE), the output will be: Byte0 Byte 1 Byte2 Value Description Bit Map of all Voltage Starts with Class C voltage. Classes (1.8V – 3V – 5V order) 0x00 Time delay...

  • Page 81: Contact_Emv_Singlemode

    CLOUD 47 0 F R EFERENCE ANUAL 6.3.5.3. 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...

  • Page 82: Contact_Apdu_Transfer

    CLOUD 47 0 F R EFERENCE ANUAL 6.3.5.5. CONTACT_APDU_TRANSFER This Escape command exchanges a short APDU with the smart card. The user has to ensure that card inserted powered before issuing this Escape command. This Escape command mostly is used by the MCard API to access synchronous memory cards.

  • Page 83: Contact_Exchange_Raw

    CLOUD 47 0 F R EFERENCE ANUAL 6.3.5.7. 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: Contact_Get_Set_Clk_Frequency

    CLOUD 47 0 F R EFERENCE ANUAL 6.3.5.8. 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.

  • Page 85: Contact_Control_Atr_Validation

    CLOUD 47 0 F R EFERENCE ANUAL 6.3.5.9. 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.

  • Page 86: Contact_Get_Set_Mcard_Timeout

    CLOUD 47 0 F R EFERENCE ANUAL 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: Contact_Get_Set_Etu

    CLOUD 47 0 F R EFERENCE ANUAL 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: Contact_Get_Set_Waittime

    CLOUD 47 0 F R EFERENCE ANUAL 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.

  • Page 89: Contact_Get_Set_Guardtime

    CLOUD 47 0 F R EFERENCE ANUAL 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.

  • Page 90: Contact_Read_Insertion_Counter

    CLOUD 47 0 F R EFERENCE ANUAL 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 6 byte is the Escape code 0x00 to identify the command.

  • Page 91: Annexes

    CLOUD 47 0 F R EFERENCE ANUAL 7. Annexes Annex A – Status words table 7.1. Description 0x90 0x00 NO ERROR 0x63 0x00 NO INFORMATION GIVEN 0x65 0x81 MEMORY FAILURE 0x67 0x00 LENGTH INCORRECT 0x68 0x00 CLASS BYTE INCORRECT 0x6A 0x81 FUNCTION NOT SUPPORTED 0x6B...

  • Page 92: Annex B - Sample Code Using Escape Commands

    CLOUD 47 0 F R EFERENCE ANUAL Annex B – Sample code using escape commands 7.2. File Name: CLOUD 47x0 F Escape.h #ifndef _CLOUD_47x0F_ESCAPE_H_ #define _CLOUD_47x0F_ESCAPE_H_ #ifdef __cplusplus extern"C" #endif # pragmapack typedefstruct BYTE byMajorVersion; BYTE byMinorVersion; BYTE bySupportedModes; WORD wSupportedProtocols;...
  • Page 93 InByte, i; DWORD BytesRead, ActiveProtocol; ULONG ret; char char *ReaderName[] = {"Identive CLOUD 4700 F Contact Reader 0", "Identive CLOUD 4700 F Contactless Reader 0", NULL}; /*************************************************************************************** *****************/ ContextHandle = -1; ret = SCardEstablishContext(SCARD_SCOPE_USER, NULL, NULL, &ContextHandle); if (ret == SCARD_S_SUCCESS) s = ReaderName[0];...
  • Page 94 CLOUD 47 0 F R EFERENCE ANUAL ret = SCardReleaseContext(ContextHandle); else printf("\n SCardEstablishContext failed with %.8lX",ret); printf("\npress any key to close the test tool\n"); getch();...

  • Page 95: Annex C - Mechanical Drawings

    CLOUD 47 0 F R EFERENCE ANUAL Annex C – Mechanical drawings 7.3. 7.3.1. Outline and cable positions...

  • Page 96: Stand

    CLOUD 47 0 F R EFERENCE ANUAL 7.3.2. Stand...

  • Page 97: Reader Mounted To Stand

    CLOUD 47 0 F R EFERENCE ANUAL 7.3.3. Reader mounted to Stand...

  • Page 98: Cloud 4710 F - Sam Slot

    CLOUD 47 0 F R EFERENCE ANUAL 7.3.4. CLOUD 4710 F - SAM slot...

Table of Contents