background image

 
 
 
 
 
 
 
 

Reference Manual for the CLOUD 370x F  

Contactless Desktop Readers 

For Part #:  

905502  CLOUD 3700 F 

(global version) and 

905503  CLOUD 3701 F 

(Japan-only version) 

 

     

  

 
 
 
 
 
 
 
 
 
 

Document Version:  1.0,  Last Revised On:  2014-07-22 

Summary of Contents for CLOUD 3700 F

Page 1: ...Reference Manual for the CLOUD 370x F Contactless Desktop Readers For Part 905502 CLOUD 3700 F global version and 905503 CLOUD 3701 F Japan only version Document Version 1 0 Last Revised On 2014 07 22...

Page 2: ...out the hardware and software features of the CLOUD 370x family of contactless desktop readers Audience This document is intended for system integrators and software developers Revision History Rev Da...

Page 3: ...ms and Acronyms 9 2 5 References to Other Documents 10 2 6 Conventions for Bits and Bytes 11 3 GENERAL INFORMATION ABOUT CLOUD 370X F READERS 12 3 1 Key Benefits 12 3 2 Key Features 12 3 3 Ordering In...

Page 4: ...ns 28 6 1 2 PAPDU_GET_UID 28 6 1 3 PAPDU_ESCAPE_CMD 28 6 2 Supported Pseudo APDU 30 6 2 1 PAPDU_MIFARE_READ_BINARY 30 6 2 2 PAPDU_MIFARE_UPDATE_BINARY 31 6 2 3 PAPDU_MIFARE_LOAD_KEYS 32 6 2 4 PAPDU_MI...

Page 5: ...47 6 2 25 PAPDU_NFC_TYPE1_TAG_READ8 47 6 2 26 PAPDU_NFC_TYPE1_TAG_WRITE_E8 48 6 2 27 PAPDU_NFC_TYPE1_TAG_WRITE_NE8 48 6 3 Escape Commands for the CLOUD 370x F 49 6 3 1 Sending Escape Commands to CLOUD...

Page 6: ...or modifications not expressly approved by the party responsible for compliance could void the user s authority to operate the equipment 1 2 2 Class B Section 15 Subpart C Section 15 225 NOTE This equ...

Page 7: ...ns You may NOT copy or distribute any portion of the source code without prior written consent from Identiv You may NOT combine or distribute the source code provided in this document with Open Source...

Page 8: ...his manual describes in detail the interfaces and supported commands available for developers using CLOUD 370x F in their applications 2 2 Target Audience This document describes the technical impleme...

Page 9: ...Node Address NFC Near Field Communication a set of standards for smartphones and similar devices to establish radio communication with each other by touching them together or bringing them into close...

Page 10: ...S X 6319 4 Specification of implementation for integrated circuit s cards Part 4 High speed proximity cards JICSAP Japan IC Card System Application Council PC SC Interoperability Specification for ICC...

Page 11: ...ed by one or more ordering digits which indicate its position b7 b6 b5 b4 b3 b2 b1 b0 B4 B5 B6 B7 B8 B9 B10 B11 B0 B1 B2 B3 Least significant nibble Most significant nibble 1 Byte 8 bits 2 nibbles Bit...

Page 12: ...offer best in class interoperability with various formats of tokens such as cards dongles watches or NFC mobile phones 3 2 Key Features 13 56 MHz contactless reader o ISO14443 type A B o MIFARETM o F...

Page 13: ...ment Version 1 0 Last revised on 2014 07 22 Page 13 of 82 3 3 Ordering Information Item Part number Product image CLOUD 3700 F 905502 CLOUD 3700 F with preassembled Stand foot kit 905502_5000 CLOUD 37...

Page 14: ...Source for the User Credential When the user credential is placed within the magnetic field of the reader its antenna couples with the reader and an induction current appears in the credential s anten...

Page 15: ...communication When several user credentials are in the field of the reader the load of the field increases which makes less energy available for each of them and the system is detuned For this reason...

Page 16: ...to be implemented on the host by software developers 3 6 2 Applications Provided by Identiv Identiv does not provide payment or transport applications Identiv provides a few applications for developme...

Page 17: ...e CLOUD 370x F implementation two peripherals are connected to the device controller LED for reader status indication A radio frequency RF front end that handles the RF communication The device contro...

Page 18: ...X Because there are so many variations of Linux there may be distribution specific drivers that need to be installed using the install mechanism of your particular variation If there is none the drive...

Page 19: ...Weight 44g 0 097 lb 5 External dimensions 91 x 75 x 13 mm 3 583 x 2 953 x 0 472 in 86 x 77 x 69 mm 3 386 x 3 031 x 2 717 in with Stand foot kit Default label CLOUD 3701 F Weight 44g 0 097 lb 5 Externa...

Page 20: ...ered and communicating with reader 500 ms ON 500 ms OFF 500 ms ON 500 ms OFF Reader card errors OFF 100 ms ON 100 ms OFF Dual interface card powered using RF field 500 ms ON 500 ms OFF 500 ms ON 500 m...

Page 21: ...to 185 F Operating humidity range Up to 95 relative humidity non condensing Certifications USB 2 0 CE FCC UL RoHS2 REACH WHQL 4 2 3 2 USB 2 0 Interface Parameter Value Description DC characteristics H...

Page 22: ...Kbps support FeliCa Standard Lite Calypso CD21 NFC forum tag type 1 2 3 4 iCLASS UID support my d move SLE 66RxxP my d move NFC SLE 66RxxPN SLE 66RxxS SLE 55RxxE NFC enabled Smart Phones and Tablets1...

Page 23: ...ch is available through Windows Update or on the Identiv support pages 5 2 Utilities The following utilities are available A tool for testing the resource manager TestResMan A tool called PCSCDiag whi...

Page 24: ...pplication to identify the storage card properly its Standard and Card name describing bytes must be interpreted according to the Part 3 Supplemental Document which is maintained by PC SC Credentials...

Page 25: ...Value Designation Description 0 0x3B Initial header 1 0x8n T0 n indicates the number of historical bytes in the following ATR 2 0x80 TD1 upper nibble 8 indicates no TA2 TB2 TC2 lower nibble 0 means T...

Page 26: ...Reference Manual for the CLOUD 370x F Contactless Desktop Readers Document Version 1 0 Last revised on 2014 07 22 Page 26 of 82 Examples of the ATR built for an ISO14443 4 credential Type A Type B...

Page 27: ...atus PC_to_RDR_XfrBlock PC_to_RDR_Escape PC_to_RDR_Abort 5 4 1 3 CCID Error Codes Extensive error codes are reported on many conditions during all CCID responses Most of the error messages are reporte...

Page 28: ...PUPI of the user token This command can be used for all supported technologies Command APDU CLA INS P1 P2 Lc Data in Le 0xFF 0xCA 0x00 0x00 XX Setting Le 0x00 can be used to request the full UID or P...

Page 29: ...TMODE 0X01 escape command this pseudo APDU would be used Command APDU FF CC 00 00 02 01 04 to set to NFC test mode Response APDU 90 00 NOTES 1 To send Escape commands using this method the reader shou...

Page 30: ...ry 0xFF 0xB0 Addr MSB Addr LSB XX P1 and P2 represent the block number of the block to be read starting with 0 for sector 0 block 0 continuing with 4 for sector 1 block 0 sector no x 4 block no Regard...

Page 31: ...e Update Binary 0xFF 0xD6 Addr MSB Addr LSB XX data For a description of P1 and P2 see PAPDU_MIFARE_READ_BINARY Lc must to match the block size of the used card which is 16 bytes for MIFARE Classic 4...

Page 32: ...for the encryption else it is ignored Only one reader key 0x00 is supported by CLOUD 370x F NOTES 1 Card keys can be loaded in both secure and non secure mode Card keys can only be loaded to the Volat...

Page 33: ...y after padding FFFFFFFF FFFF0A0A 0A0A0A0A 0A0A0A0A AES128 Encrypted 10229E33 189403FD A9C14110 B1BB02B4 Load keys command FF82406010 10229E33 189403FD A9C14110 B1BB02B4 Load Keys Reader Secure If the...

Page 34: ...al Authenticate 0xFF 0x86 0x00 0x00 0x05 data XX The data structure is defined as follows Byte Value Description B0 0x01 Version B1 Block Number MSB always 0x00 for MIFARE Classic cards B2 Block Numbe...

Page 35: ...ord For MIFARE Classic 48 bytes of sector data read from card For MIFARE UL Entire card data is returned 64 bytes SW1 SW2 Examples Read sector 1 of a MIFARE Classic 1K APDU FF B1 00 01 00 SW12 9000 OK...

Page 36: ...01 10 SW12 9000 OK DataOut 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F AA 55 AA 55 AA 55 AA 55 AA 55 AA 55 AA 55 AA 55 00 00 00 00 00 00 FF 07 80 6...

Page 37: ...lue Description B0 0xC0 Decrement 0xC1 Increment B1 Block number B2 B5 Value LSB first Response APDU Data Status Word SW1 SW2 Example Decrement block 4 by 1 key loading and authentication are not show...

Page 38: ...ucture that defines which action should be performed which block the actions pertain to the destinations and which value should be applied for the action Tags for the action include 0xA0 Increment 0xA...

Page 39: ...6A 81 Data object XX not supported XX 67 00 Data object XX with unexpected length XX 6A 80 Data object XX with unexpected vale XX 64 00 Data object XX execution error no response from IFD XX 64 01 Dat...

Page 40: ...RC bytes from the card as is to the application P1 0x01 will discard the CRC bytes Response APDU Data Status Word Data returned by card SW1 SW2 6 2 12 PAPDU_ISO14443_PART4_PART3_SWITCH TCL MIFARE Swit...

Page 41: ...esponse APDU Data Status Word 16 bytes of NFCID2 and 2 bytes of System Code sent only if the RFU byte is 0x01 SW1 SW2 6 2 14 PAPDU_FELICA_REQ_SERVICE This command issues a REQ SERVICE as defined in JI...

Page 42: ...ytes of Manufacture ID IDm Mode SW1 SW2 6 2 16 PAPDU_FELICA_READ_BLK This command issues a READ as defined in JIS 9 6 3 P1 specifies the number of services P2 specifies the number of blocks Data buffe...

Page 43: ...Command APDU Command CLA INS P1 P2 P3 Data FeliCa Write Block 0xFF 0x48 Number of services Number of blocks 2 P1 P2 16 P2 Service Code List Block List Block Data Response APDU Data Status Word 8 byte...

Page 44: ...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 Topaz tags have a 7 bytes long UID which can be fully fetched...

Page 45: ...b7 b3 Block value between 0x0 and 0xE b2 b0 Byte within the block value between 0 and 7 Response APDU Data Status Word Data returned by card SW1 SW2 6 2 22 PAPDU_NFC_TYPE1_TAG_WRITE_E This command iss...

Page 46: ...iting the new data Execution time of this command for NFC Forum tags type 1 is approximately half that of the normal write command with erase WRITE E Using this command EEPROM bits can only be set not...

Page 47: ...P3 Data TYPE1 Tag READ SEGMENT FF 5A 00 SegAddr 00 Where the P2 Segment Address is Bit numbers Description b7 b4 Segment 0x0 0xF b2 b0 0 Response APDU Data Status Word 128 bytes of data SW1 SW2 6 2 2...

Page 48: ...iption b7 b0 General block 0x00 0xFF Response APDU Data Status Word 8 bytes of data that have been written SW1 SW2 6 2 27 PAPDU_NFC_TYPE1_TAG_WRITE_NE8 This command issues a WRITE8 to write a block of...

Page 49: ...0 F is HKEY_LOCAL_MACHINE SYSTEM CurrentControlSet Enum USB VID_04E6 PID_5790 Device Instance xxxx Device Parameters while the value for CLOUD 3701 F is HKEY_LOCAL_MACHINE SYSTEM CurrentControlSet Enu...

Page 50: ...s Upon power on the reader will reset to the default ISO7816 mode Input The first byte of the input buffer contains the escape code value and the second byte contains the value for the desired mode of...

Page 51: ...ader mode will be returned as a byte value Mode Value Remarks ISO 0x00 ISO 7816 mode NFC Test 0x04 NFC Test Mode 6 3 3 3 READER_GET_IFDTYPE This Escape command is used to get the current IFD type from...

Page 52: ...ED change when using this IOCTL Input The first byte of the input buffer contains the escape code followed by the LED number when more than one LED is present otherwise set to 0 and then the desired L...

Page 53: ...inorVersion Minor Version in BCD 1 bySupportedModes Bit map indicating the supported modes of the reader 0x01 EMV mode 0x02 Memory card mode 0x04 NFC test mode 0x04 for Contactless only readers 0x07 f...

Page 54: ...S Frequent writes should be avoided because the non volatile memory supports only 100K writing cycles A maximum of 249 bytes can be read and written The sector can be read and written only as a whole...

Page 55: ...read and written only as a whole If complete data 8 bytes is not given during a write operation then the operation will fail and return an error If you want to modify only partial data in the reader...

Page 56: ...ollow the APDU structure as per PCSC3 AMD1 The 6th byte shall be the command code used to identify the specific command Byte0 Byte1 Byte2 Byte3 Byte4 From Byte 5 up to Lc bytes Byte Lc 5 Byte 5 Byte 6...

Page 57: ..._PPS 0x9D CNTLESS_CONTROL_848 0x9E CNTLESS_GET_BAUDRATE 0xA7 CNTLESS_CONTROL_RETRIES 0xAC CNTLESS_CONTROL_POLLING 0xAD CNTLESS_FORCE_BAUDRATE 0xDA CNTLESS_GET_CARD_DETAILS 0xE1 CNTLESS_SET_CONFIG_PARA...

Page 58: ...rate Byte1 settings bit Description b0 1 212 Kbps supported from reader to card b1 1 424 Kbps supported from reader to card b2 1 848 Kbps supported from reader CLOUD 3700 F only to card b3 Always 0 b4...

Page 59: ...s or the ATQB bytes depending on the type of PICC placed within the field of the reader 6 3 4 3 CNTLESS_GET_TYPE This Escape command retrieves the type of cards which the reader is configured to poll...

Page 60: ...r shall point to a WORD buffer in case the extension specifier is given and will contain the type value coded as bitmask as Cards Type Bit Mask Lo Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0...

Page 61: ...s of cards are expected The default is Type A Type B 0x02 Input The input buffer shall contain either two or three bytes Byte0 Byte1 Byte3 Description Escape code 0x95 0x00 Type A 0x01 Type B 0x02 Typ...

Page 62: ...is ON 1 RF field is OFF Output No response is returned for Set State For Get State a 1 byte response is received Output buffer NULL or current state 6 3 4 6 CNTLESS_CONTROL_PPS This Escape command dis...

Page 63: ...Protocol Parameter Selection PPS is ON NOTE Only the CLOUD 3700 F reader supports 848 Kbps the CLOUD 3701 F reader s maximum baud rate is 424 Kbps Input The input buffer shall contain 2 bytes Byte0 B...

Page 64: ...CD 848 Kbps from PCD to PICC 0x10 212 Kbps from PICC to PCD 106 Kbps from PCD to PICC 0x11 212 Kbps in both directions 0x12 212 Kbps from PICC to PCD 424 Kbps from PCD to PICC 0x13 212 Kbps from PICC...

Page 65: ...ROL_POLLING This Escape command is used to enable or disable firmware polling for contactless cards Input The first byte of the input buffer contains the escape code The second byte either sets the mo...

Page 66: ...value is 0x01 There is no need to send this byte when B1 has the value x00 When bit 1 1 DR 4 is supported When bit 2 1 DR 8 is supported Bit 3 shall be set to 0 the value of 1 is reserved for future...

Page 67: ...th 0x08 For FeliCa cards THEN EITHER B3 B12 PUPI UID bytes 0x00 byte padding used if length is smaller than 10 B13 0x00 CID not supported 0x01 CID supported B14 0x00 NAD not supported 0x01 NAD support...

Page 68: ...Value Description B0 0xE1 Escape code B1 Type A RXGAIN for polling or 106 Kbps B2 Type A RXGAIN for 212 Kbps B3 Type A RXGAIN for 424 Kbps B4 Type A RXGAIN for 848 Kbps B5 Type A RX THRESHOLD for pol...

Page 69: ...This Escape command is used as a pass through to send FeliCa commands to FeliCa cards Input The first byte of the input buffer contains the escape code and the following bytes contain a FeliCa comman...

Page 70: ...d byte either sets the mode or contains a code to retrieve the setting Additional data bytes are used for Initiator or Target mode Offset Description Detailed description 0 Escape code 0xE9 Switch mod...

Page 71: ...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 Pad...

Page 72: ...Writer mode 6 3 4 17 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...

Page 73: ...Chaining 1 Chaining Chaining byte 5 Timeout Low Byte 6 Timeout High Byte Offset 7 to offset 7 N N data bytes Bytes to be sent to Initiator device Output After the data bytes are sent successfully the...

Page 74: ...transceive 1 0x00 Reserved for future use 2 0x00 Reserved for future use 3 0x00 Reserved for future use 4 0 No Chaining 1 Chaining Chaining 5 Timeout Low Byte 6 Timeout High Byte Offset 7 to offset 7...

Page 75: ...ol Tag 4 Type A and Type B test cases 1 0x01 NFC_DEP supported To perform test cases in Peer2Peer mode as defined in the NFC Test Cases For Digital Protocol If a value other than 0x01 is given NFC_DEP...

Page 76: ...0x03 0x04 opcode 0x00 GET NFC Parameter 00 The value of byte 7 NFC Parameter is interpreted from this table Byte 7 Value Description 0x00 DID Device Identification Number 0x01 LRi Length Reduction fi...

Page 77: ...1 Appendix A Status Words table SW1 SW2 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 FUNC...

Page 78: ...02 define READER_GETIFDTYPE 0x12 define READER_LED_CONTROL 0x19 define READER_LED_CONTROL_BY_FW 0xB2 define READER_GETINFO_EXTENDED 0x1E define READER_RDWR_USR_AREA 0xF0 define CNTLESS_GETCARDINFO 0x1...

Page 79: ...Connecting to reader s n s ret SCardConnect ContextHandle s SCARD_SHARE_DIRECT SCARD_PROTOCOL_UNDEFINED CardHandle ActiveProtocol if ret SCARD_S_SUCCESS InByte 0x1E ret SCardControl CardHandle IOCTL_C...

Page 80: ...rReaderInfo bySerialNoLength i if strReaderInfo abySerialNumber i 0 printf c strReaderInfo abySerialNumber i else printf SCardControl failed 08X n ret else printf SCardConnect failed 08X n ret ret SCa...

Page 81: ...D 370x F Contactless Desktop Readers Document Version 1 0 Last revised on 2014 07 22 Page 81 of 82 7 3 Appendix C Mechanical Drawings 7 3 1 Reader without stand NOTE All dimensions on these mechanical...

Page 82: ...Reference Manual for the CLOUD 370x F Contactless Desktop Readers Document Version 1 0 Last revised on 2014 07 22 Page 82 of 82 7 3 2 Reader on Stand...

Reviews: