SCM Microsystems Reference Manual – version 1.
Reference manual SCM3712 NFC Reader Boards © SCM Microsystems Oskar-Messter-Straße, 13 85737 Ismaning Germany Phone +49 89 9595 5000 • Fax +49 89 9595 5555
Document history Date Version Description ofchange 01.07.2011 1.0 Initial Version Contact information http://www.scmmicro.com/products-services/smart-card-readers-terminals/contactless-dualinterface-readers.html For sales information, please email sales@scmmicro.
Table of Contents 1. 2. 3. Legal information .............................................................................................................................. 6 1.1. Disclaimers ................................................................................................................................ 6 1.2. Licenses .................................................................................................................................... 6 1.3. Trademarks .................
7. Firmware ........................................................................................................................................ 36 7.1.1. 7.1.2. 8. Transport protocol .............................................................................................................36 Automatic PPS ..................................................................................................................36 Commands description ........................................................
9.2.2. SCM3712 EA and external antenna board .......................................................................77 9.3. Annex C – Installation Guidelines ........................................................................................... 79 9.3.1. SCM3712 & SCM3712 NFC Mount on Metal Instruction .................................................80 9.3.2. SCM3712 ANT Mount on Metal Instruction ......................................................................80 9.3.3.
LIST OF FIGURES Fig.3-1: SCM3712 in a Terminal Use Application ................................................................................. 14 Fig.3-2: SCM3712 in a Kiosk Use Application....................................................................................... 15 Fig.3-3: SCM3712 based system configuration in a Terminal Use Application .................................... 18 Fig.3-4: SCM3712 based system configuration in a Kiosk Use Application .........................................
LIST OF TABLES Table 4.1: SCM 3712 xxx mechanical data overview ........................................................................... 22 Table 4.2: LED Status indication ........................................................................................................... 23 Table 4.3: Electrical Specification ......................................................................................................... 24 Table 5.1:USB Connector Pin-Out ................................................
SCM3712 REFERENCE MANUAL 6 1. Legal information 1.1. Disclaimers The content published in this document is believed to be accurate. SCM Microsystems 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.
SCM3712 REFERENCE MANUAL 7 2. Introduction to the manual 2.1. Objective of the manual This manual provides an overview of the hardware and software features of the SCM3712 NFC Reader Boards, hereafter referred to as “SCM3712”. This manual describes in details interfaces and supported commands available for developers using SCM3712 in their applications. 2.2. Target audience This document describes the technical implementation of SCM3712. The manual targets software developers.
SCM3712 REFERENCE MANUAL 2.4.
SCM3712 REFERENCE MANUAL 2.5.
SCM3712 REFERENCE MANUAL 2.6. 10 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.
SCM3712 REFERENCE MANUAL 11 3. General information about SCM3712 3.1. SCM3712 key benefits The SCM3712 product family has been designed for an easy integration into various devices. The SCM3712 form factors have been optimized for best RF performance and for minimizing the footprint for integration even into very compact devices.
SCM3712 REFERENCE MANUAL 3.3.
SCM3712 REFERENCE MANUAL Item Part number NFC Solutions Development Kit 905334 13 Device
SCM3712 REFERENCE MANUAL 14 3.4. Contactless communication principles and SCM3712 usage recommendations 3 SCM3712 is a contactless reader designed to communicate with user tokens or via the NFC PeerTo-Peer modes (Reader-To-Tag Mode & Peer-To-Peer Mode)with NFC enabled Mobile phones also with other SCM3712/SCL3711 devices. In any case the SCM3712 Reader Boards are being embedded into terminals, vending machines, kiosks or any other final device.
15 SC M3 x x x 712 SCM3712 REFERENCE MANUAL 0 12 3 4 5 6 7 User Tokens and/or NFC SmartPhone Fig.3-2: SCM3712 in a Kiosk Use Application 4 User tokens are made of a contactless integrated circuit card connected to an antenna. User tokens can take several form factors: • Credit card sized smart card • Key fob • NFC mobile phone • Mobile Device Stickers etc… The communication between SCM3712 and user tokens uses magnetic field inductive coupling.
SCM3712 REFERENCE MANUAL 16 3.4.1. Power supply When the user token is put in the magnetic field of the reader, its antenna couples with the reader and an induction current appears in the antenna thus providing power to the integrated circuit. The generated current is proportional to the magnetic flux going through the antenna of the user token. 3.4.2. Data exchange The carrier frequency of the magnetic field is used as a fundamental clock signal for the communication between the reader and the card.
SCM3712 REFERENCE MANUAL 17 3.4.3. Recommendations The communication between the reader and the user token 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 token can severally degrade the communication and even make it impossible.
SCM3712 REFERENCE MANUAL 3.5. 18 Applications 3.5.1. General SCM3712 is a transparent reader designed to interface a personal computer host supporting PC/SC interface with 13.56MHz user credentials used in public transport, loyalty programs, vending machine and payment applications.
SCM3712 REFERENCE MANUAL 19 Fig.3-4: SCM3712 based system configuration in a Kiosk Use Application SCM3712 itself handles the communication protocol but not the application related to the token. The application-specific logic has to be implemented by software developers on the host. 3.5.2. Supporting applications provided by SCM Microsystems SCM Microsystems does not provide payment or transport applications.
SCM3712 REFERENCE MANUAL 20 4. SCM3712 characteristics 4.1. SCM3712 high level architecture 4.1.1. Block diagrams Amplifier & Matching Network Integrated Antenna PN 533 Connector The link between SCM3712 and the host to which it is connected is the USB interface providing both the power and the communication channel. LED Matching Network Integrated Antenna PN 533 Connector Fig.4-1: SCM3712 Reader Board Block Schematic LED Matching Network PN 533 Connector Fig.
SCM3712 REFERENCE MANUAL 21 4.1.2. Software architecture Applications can interface either with the driver directly through the PC/SC interface or through the SCM proprietary interface to the NFC wrapper. Fig.4-4: SCM3712 xxx software layer overview The NFC wrapper simplifies the usage of the different NFC Forum tags with the SCM3712 and other SCM contactless readers.
SCM3712 REFERENCE MANUAL 4.2. 22 Quick reference data 4.2.1. SCM3712 mechanical dimensions Characteristic Weight Reader PCB Size (LxWxH) Antenna PCB Size (LxWxH) Antenna Cable Length Antenna Connector Value SCM3712 5,5 g ± 5% / 0,012 lb ± 5% 60 x 40,3 x 10 mm ± 0.13mm 2,36 x 1,59 x 0,39 Inch ± 0,005 Inch SCM3712 NFC 5,5 g ± 5% / 0,012 lb ± 5% SCM3712 EA 19,5 g ± 5% / 0,043 lb 5 ± 5% 60 x 40,3 x 10 mm ± 0.13mm 2,36 x 1,59 x 0,39 Inch ± 0,005 Inch 60 x 40,3 x 10 mm ± 0.
SCM3712 REFERENCE MANUAL 23 4.2.2. LED Status indication The LED behavior of the SCM3712 is given below. SCM3712states LED Indication (GREEN) After plug-in (no driver loaded) OFF Driver successfully loaded ON User token arriving in the field One blink User token removed from the field ON, no specific visual indication Suspend/hibernate/shutdown state OFF SCM3712disabled OFF P2P mode Three blinks Table 4.
SCM3712 REFERENCE MANUAL 24 4.2.3.
SCM3712 REFERENCE MANUAL 25 5. Hardware The SCM3712 reader board comes with an integrated USB interface, which also is used for the power supply of the unit. Therefore only the USB interface needs to be connected. The drawing and the table below are showing the exact Pin-Out of the USB connector. 5.1.
SCM3712 REFERENCE MANUAL 5.3. 26 Antenna The SCM3712 and the SCM3712NFC reader come with an integrated antenna, while the SCM3712 ANT comes with an external antenna. Any of those ready to use antennas do not require any tuning as the antennas already are being tuned for optimized performance during the production process. Any changes on the tuning circuit will result in a negatively influenced reader performance.
SCM3712 REFERENCE MANUAL 27 6. Software modules SCM3712 is provided with an installer. 6.1. Installation Make sure the SCM3712 is not plugged in your PC before you start. Start the installer by double clicking on setup.exe Click Next on the welcome page of the installer Carefully read and accept the license agreement in order to install the driver.
SCM3712 REFERENCE MANUAL Then install After a few minutes, you are notified the installation happened correctly You are ready to use your SCM3712. In some very rare cases, you may be asked to reboot your PC. Please do so if this is the case.
SCM3712 REFERENCE MANUAL 29 6.1.1. Command line parameters for installation A few parameters of the installer can be configured when launching the installer from the command line Silent mode of installation Setup.exe /s /v“/qn” Installation with no dialogs Setup.exe /v”LIMITUI=1” No reboot dialog Setup.exe /v”REBOOTREQD=0” 6.1.2. Command line parameters for de-installation.
SCM3712 REFERENCE MANUAL 6.3. 30 Driver The driver for Windows platforms is based on Microsoft WDF architecture 1.09. The driver package contains INF, SYS, CAT and the co-installer DLL required for the WDF architecture. 6.3.1.
SCM3712 REFERENCE MANUAL 31 6.3.3. PC/SC 2.0 compliant ATR 6.3.3.1. Determining the technology of the user credential The ScardControl method of PC/SC(see http://msdn.microsoft.com/enus/library/aa379474(VS.85).aspx) should be used to send the 0x90 IOCTL to SCM3712 in order to determine what type of technology is the user token based on.
SCM3712 REFERENCE MANUAL 6.3.3.2. 32 ATR for type A memory user tokens The ATR of the user token is composed as described in the table below. In order to allow the application to identify the storage card properly, it’s Standard and Card name describing bytes must be interpreted according to the Part 3 Supplemental Document, maintained by PC/SC.
SCM3712 REFERENCE MANUAL 6.3.3.3. 33 ATR for an NFC Forum tag type 1 user token (Topaz) Byte# Value Designation Description 0 0x3B Initial header 1 0x82 T0 TD1 present.
SCM3712 REFERENCE MANUAL 6.3.3.4. 34 ATR for a NFC Forum tag type 3 user token (FeliCa) Byte# Value Designation Description 0 0x3B Initial header 1 0x8C T0 TD1 present.
SCM3712 REFERENCE MANUAL 6.3.3.5. 35 ATR for ISO/IEC 14443-4 user tokens The user token exposes its ATS or application information which is mapped to an ATR. The table describes how this mapping is done. Byte# Value Designation Description 0 0x3B Initial header 1 0x8n T0 n indicates the number of historical bytes in following ATR 2 0x80 TD1 Nibble8 indicates no TA2, TB2, TC2 Nibble0means T=0 3 0x01 TD2 Nibble8 indicates no TA3, TB3, TC3 Nibble1means T=1 4...
SCM3712 REFERENCE MANUAL 36 7. Firmware 7.1.1. Transport protocol SCM3712 implements a transport protocol which is proprietary to NXP Semiconductors. 7.1.2. Automatic PPS Automatic PPS implemented is implemented. SCM3712 will automatically switch the highest baud rate commonly supported by the SCM3712 and the user token The maximum speed supported by SCM3712 is 424Kbps by default.
SCM3712 REFERENCE MANUAL 37 8. Commands description 8.1. Generic APDUs 8.1.1. Get UID Command 8.1.1.1. Description This command will retrieve the UID or SNR or PUPI of the user token. This command can be used for all supported contactless technologies. 8.1.1.2.
SCM3712 REFERENCE MANUAL 38 8.1.2. Get DATA Command 8.1.2.1. Description This command can be used to retrieve the ATS of an ISO/IEC14443-4A user token only. 8.1.2.2. Format CLA INS P1 P2 Lc 0xFF 0xCA 0x01 0x00 0x00 8.1.2.3. Response Data Out ATS + SW1 + SW2 8.1.2.4.
SCM3712 REFERENCE MANUAL 39 8.1.3. T=CL user Command 8.1.3.1. Description This command can be used to send raw data to the user token.SCM3712 will add T=CL protocol data to the raw data you send. 8.1.3.2. Format CLA INS P1 P2 P3 Data 0xFF 0xFE 0x00 0x00 Lraw_data Raw_data 8.1.3.3. Response Data Out PICC response data+ SW1 + SW2 8.1.3.4. SW1 SW2 Status Words Description User should refer to the status words defined by the PICC manufacturer for a description of the status words 8.1.
SCM3712 REFERENCE MANUAL 40 8.1.4. PASS_THROUGH command 8.1.4.1. Description This command can be used to send raw data to the user token.SCM3712 will not add transport protocol data to the raw data – e.g. PCB, NAD, CID etc. 8.1.4.2. Format CLA INS P1 P2 P3 Data 0xFF 0xEF 0x00 0x00 Lraw_data Raw_data 8.1.4.3. Response Output buffer PICC response data 8.1.4.4. Status Words 8.1.4.5.
SCM3712 REFERENCE MANUAL 8.2. 41 Set of APDU for contactless storage user tokens Command specific return codes are given under each command. Please refer section 7.1.1 (Status words table) for common return codes. 8.2.1. STORAGE_CARD_CMDS_READ_BINARY 8.2.1.1. Description Using this APDU, application can read a memory block on user tokens based on technologies like MIFARE Classic 1K or 4K (block size 0x10 bytes)or MIFARE UltraLight(block size 0x04 bytes). 8.2.1.2.
SCM3712 REFERENCE MANUAL 8.2.1.5.
SCM3712 REFERENCE MANUAL 43 8.2.2. STORAGE_CARD_CMDS_WRITE_BINARY 8.2.2.1. Description This APDU writes data pattern in to a memory address 8.2.2.2. Format CLA INS P1 P2 Lc Data in 0xFF 0xD6 0x00 Block # 0xXX Data Where: • P2 indicate the memory block number where data should be written • Lc=0x10 for MIFARE Classic 1K/4K. Lc=0x04 for MIFARE Ultralight 8.2.2.3. Response Data Out SW1 + SW2 8.2.2.4.
SCM3712 REFERENCE MANUAL 8.2.2.5.
SCM3712 REFERENCE MANUAL 45 8.2.3. STORAGE_CARD_CMDS_LOAD_KEYS 8.2.3.1. Description Some type of user tokens like MIFARE Classic may require that an authentication happens before any data can be read or written. To encrypt perform this authentication, the required keys need to be loaded in the reader’s memory using this command. 8.2.3.2.
SCM3712 REFERENCE MANUAL 46 8.2.4. STORAGE_CARD_CMDS_AUTHENTICATE 8.2.4.1. Description This command enables to perform authentication for user tokens based on MIFARE Classic 1K or 4K. Before this command can be successfully executed, the STORAGE_CARD_CMDS_LOAD_KEY command must have been executed. 8.2.4.2.
SCM3712 REFERENCE MANUAL 8.2.4.5.
SCM3712 REFERENCE MANUAL 48 8.2.5. STORAGE_CARD_CMDS_VALUE_BLOCK 8.2.5.1. Description This APDU is used to interact with MIFARE Classic e-purse applications. Please refer to MIFARE Classic documentation available from NXP Semiconductors for further details on MIFARE classic memory mapping and commands. 8.2.5.2.
SCM3712 REFERENCE MANUAL 8.3. 49 Set of APDU for ISO/IEC 14443-4 user tokens 8.3.1. T=CL Command 8.3.1.1. Description Using this command, SCM3712 transfers directly ISO/IEC7816-4 APDU to the user token. 8.3.1.2. CLA INS Format P1 P2 P3 Data Description of the APDU commands can be found in ISO/IEC 7816-4 specification. 8.3.1.3. Response Data Out PICC answer + SW1 + SW2 As defined in ISO/IEC 7816-4. 8.3.1.4. SW1 Status Words SW2 Description See ISO/IEC 7816-4 As defined in ISO/IEC 7816-4.
SCM3712 REFERENCE MANUAL 8.4. 50 MIFARE DESFire commands MIFARE DESFire native commands can be mapped onto case 4 APDU as described hereunder: CLA INS P1 P2 P3 Data Le 0x90 DESFirecmd code 0x00 0x00 Length of data field DESFire command parameters 0x00 The response from a DESFire user token will be mapped as follow Data SW1 SW2 User token answer 0x91 0xYY 0xYY is the DESFire native status byte as described in NXP documentation.
SCM3712 REFERENCE MANUAL 8.5.1.2. 51 Read All Blocks (RALL) Description The RALL command reads-out the two header ROM bytes and the whole of the static memory blocks 0x0-0xE.
SCM3712 REFERENCE MANUAL 8.5.1.3. 52 Read Byte (READ) Description This command reads a single EEPROM memory byte within the static memory model area of blocks 0x0-0xE.
SCM3712 REFERENCE MANUAL 8.5.1.5. 53 Write-No-Erase Byte (WRITE-NE) Description This command writes a byte value on an individual memory byte within the static memory model area of blocks 0x0-0xE. This command does not erase the value of the targeted byte before writing the new data. Execution time of this command by NFC Forum tags type 1, is approximately half that of the normal write command (WRITE-E). Using this command, EEPROM bits can be set but not reset.
SCM3712 REFERENCE MANUAL 8.5.1.6. 54 Read Segment (RSEG) Description This command reads out a complete segment of memory. Format CLA INS P1 P2 P3 Data 0xFF 0x5A 0x00 Segment Address 0x00 - Where P2 is coded as shown below Bit # Value Description b0 – b3 (0000)b RFU b4 – b7 Segment address (value between 0x0 and 0xF) Response Data SW1 SW2 128 bytesofdata 0x90 0x00 8.5.1.7. Read 8 bytes (READ8) Description This command reads out a block of memory.
SCM3712 REFERENCE MANUAL 8.5.1.8. 55 Write-Erase 8 bytes (WRITE-E8) Description This command erases a memory block and then writes a value to it. Format CLA INS P1 P2 P3 Data 0xFF 0x5E 0x00 Block Address 0x08 8 bytes of data to be written Where P2 codes the block address (value between 0x00 and 0xFF) Response Data SW1 SW2 8 bytes of data that have been written 0x90 0x00 8.5.1.9. Write-No-Erase 8 bytes (WRITE-NE8) Description This command writes with no erase to a block of memory.
SCM3712 REFERENCE MANUAL 56 8.5.2. Commands for communicating with NFC Forum Tags Type 2 To interact with an NFC Forum tag type 2 the commands STORAGE_CMDS_READ_BINARY and STORAGE_CMDS_WRITE_BINARY previously described in this manual should be used. Please refer to NFC Forum tag type 2specification for definition of the read and write procedures. 8.5.3.
SCM3712 REFERENCE MANUAL 8.5.3.2. 57 Request Service Description This command is used to know the area key version of the specified area and the service key version of the specified service of FeliCa card Format CLA INS P1 P2 P3 Data 0xFF 0x42 Number of services/areas 0x00 2 * P1 Service Code List / Area Code List Response Data SW1 SW2 8 bytes IDm + No. of Service or areas(n) + Service version or area version list (2*n) 0x90 0x00 8.5.3.3.
SCM3712 REFERENCE MANUAL 8.5.3.5. 58 Write Description This command is used to write the records of the specified service to the FeliCa card Format CLA INS P1 P2 P3 Data 0xFF 0x48 Number of services Number of blocks 2*(P1 + P2) + (16 * P2) Service Code List, Block List, Block Data Response Data SW1 SW2 8 bytes IDm + Status Flag 1 + Status Flag 2 0x90 0x00 8.5.3.6. Request System Code Description This command searches for the system code registered in the card and returns its value.
SCM3712 REFERENCE MANUAL 8.6. 59 Escape IOCTL’s supported in SCM3712 The reader behavior can be configured with the help of below given IOCTL’s. The ScardControl method of PC/SC (see http://msdn.microsoft.com/en-us/library/aa379474(VS.85).aspx) should be used to send those IOCTLs. Code the API as given below.
SCM3712 REFERENCE MANUAL 60 8.6.2. READER_GET_CARD_TYPE_POLLING 8.6.2.1. Description Using this escape command one can retrieve the type of the technology which the reader is configured to poll for. 8.6.2.2. Input buffer Byte # Value Description B0 0x94 Escape command code 8.6.2.3.
SCM3712 REFERENCE MANUAL 61 8.6.4.READER_CNTLESS_RF_SWITCH 8.6.4.1. Description This escape message ID can be used to retrieve the current RF state (ON/OFF) of SCM3712 as well as to switch the RF state (ON/OFF). 8.6.4.2. Input buffer Byte # Value Description B0 0x96 Escape command code B1 Configuration parameter Configuration parameter byte can take the following values Value Description 0x00 Switch the RF OFF 0x01 Switch the RF ON 0xFF Get the current RF field state 8.6.4.3.
SCM3712 REFERENCE MANUAL 62 8.6.6. READER_ENABLE_DISABLE_848 8.6.6.1. Description This escape message can be used to enable/disable 848kbps support and to get the current state of the 848kbps support. Applications may call this function, to enable/disable 848kbps support. 8.6.6.2. Input buffer Byte # Value Description B0 0x9D Escape command code B1 0x00 Disable 848kbps 0x01 Enable 848kbps 0xFF Get current state 8.6.6.3.
SCM3712 REFERENCE MANUAL 63 8.6.8. READER_FORCE_BAUDRATE 8.6.8.1. Description This escape command is used to force baud rate between the SCM3712 and the user token. Once sent, the card needs to be disconnected and reconnected before the specific setting is adopted. 8.6.8.2.
SCM3712 REFERENCE MANUAL 64 8.6.9. READER_DISABLE_NAK_POLLING 8.6.9.1. Description This escape command can be used to enable/disable NAK Polling by SCM3712 once a user token has been selected. 8.6.9.2. Input buffer Byte # Value Description B0 0xAC Escape command code B1 0x00 Enable NAK Polling 0x01 Disable NAK Polling 0xFF Gets Current state of NAK polling. 8.6.9.3.
SCM3712 REFERENCE MANUAL 8.7. 65 Vendor IOCTL used for P2P mode of operation Please note that some of the below mentioned commands do not work on all SCM3712 product versions. IOCTL Code Description IOCTL_GET_CARD_TYPE SCARD_CTL_CODE(0x90 0) Returns the type of the card detected by the reader. IOCTL_GET_DEVICE_CAPAB SCARD_CTL_CODE(0x90 1) Returns the supported target and initiator modes. IOCTL_GET_OR_SET_RW_P2P_MO DES SCARD_CTL_CODE(0x90 6) Switches the device to Reader/Write or P2P mode.
SCM3712 REFERENCE MANUAL 8.7.1.3. 66 Output buffer Byte # B0 Value Description 0x00 Type of card or target detected by the reader UNKNOWN 8.7.1.4. 0x01 MIFARE 1K 0x02 MIFARE 4K 0x03 MIFARE UL 0x04 ISO14443-4A/MIFARE DESFIRE 0x05 FeliCa 0x06 JEWEL / TOPAZ 0x07 ISO14443-4B 0x08 NFC TARGET Return Value Return Value Value Description ERROR _SUCCESS 0 Successful execution ERROR_GEN_FAILURE 31 Operation failed ERROR_INSUFFICIENT_BUFFER 122 Input or output buffer too small 8.
SCM3712 REFERENCE MANUAL 8.7.2.4. 67 Output buffer typedefstruct _DEVICE_CAPABILITIES { BYTE byInitiatorModes; BYTE byTargetModes; } DEVICE_CAPABILITIES, *PDEVICE_CAPABILITIES The bit mask used in byInitiatorModes and byTargetModes is as follows MIFARE UL - 0x01 MIFARE STD - 0x02 ISO14443-4A - 0x04 ISO14443-4B - 0x08 FeliCa - 0x10 NFC - 0x20 JEWEL / TOPAZ - 0x40 8.7.2.5.
SCM3712 REFERENCE MANUAL 68 8.7.3. IOCTL_GET_OR_SET_RW_P2P_MODES 8.7.3.1. Description IOCTL_GET_OR_SET_RW_P2P_MODES is used to switch the device from Reader/Writer mode to P2P mode and vice versa. It can also be used to retrieve the current mode of the device. By default, the device is in Reader/Writer mode. When switched to P2P mode, it can be defined whether the device shall operate in active or in passive mode. 8.7.3.2.
SCM3712 REFERENCE MANUAL 8.8. 69 P2P Initiator Mode IOCTLs 8.8.1. IOCTL_INITIATOR_POLL 8.8.1.1. Description This IOCTL is sent to the device that would act as the initiator. On receiving this IOCTL, the initiator firmware / driver would • • • Check if the device is already in the P2P mode If not, automatically switch the device to P2P mode Start polling for the target device. The response would contain the target presence / absence status. 8.8.1.2.
SCM3712 REFERENCE MANUAL 8.8.1.4. 70 Return Value Return Value Value Description ERROR _SUCCESS 0 Successful execution ERROR_GEN_FAILURE 31 Operation failed ERROR_INSUFFICIENT_BUFFER 122 Input or output buffer too small 8.8.2. IOCTL_INITIATOR_CONNECT 8.8.2.1. Description This IOCTL is sent to the device that would act as the initiator. On receiving this IOCTL, the initiator firmware / driver would Check whether the device is already in P2P mode.
SCM3712 REFERENCE MANUAL 71 BYTE byGtLen;// Length of the general bytes BYTE byGt[47];//Generalbytesshall be optional and designate general information. } INITIATOR_CONNECT_RESP, *PINITIATOR_CONNECT_RESP; 8.8.2.4. Return Value Return Value Value Description ERROR _SUCCESS 0 Successful execution ERROR_GEN_FAILURE 31 Operation failed ERROR_INSUFFICIENT_BUFFER 122 Input or output buffer too small 8.8.3. IOCTL_INITIATOR_TRANSCEIVE 8.8.3.1.
SCM3712 REFERENCE MANUAL 8.8.4.3. 72 Output Buffer NULL. 8.8.4.4. Return Value Return Value Value Description ERROR _SUCCESS 0 Successful execution ERROR_GEN_FAILURE 31 Operation failed ERROR_INSUFFICIENT_BUFFER 122 Input or output buffer too small P2P Target Mode IOCTLs 8.8.5. IOCTL_TARGET_RECEIVE 8.8.5.1. Description This IOCTL is used by the application to receive the data from the target device.
SCM3712 REFERENCE MANUAL 8.8.5.2. 73 Input Buffer Byte # Value Description B0 0x00 RW mode 0x01 P2P mode 0x00 Passive mode 0x01 Active mode B1 B2 – B3 MIFARE SENS Response B4 – B6 MIFARE NFCIDt B7 MIFARE SEL Response B8 – B9 FeliCa polling response B10 – B15 FeliCa NFCID2t B16 – B23 FeliCa PAD bytes B24 – B25 FeliCa System Code B26 NFCID3t B27 – B28 Receive timeout ranging from 1000ms to 5000ms B29 General bytes length B30 onwards General bytes (max 47 bytes) 8.8.5.3.
SCM3712 REFERENCE MANUAL 74 8.8.6. IOCTL_TARGET_SEND 8.8.6.1. Description This IOCTL is used by the application to send the data to the initiator device as response to the command sent by the initiator. 8.8.6.2. Input Buffer Input buffer should contain the data to be sent to initiator. 8.8.6.3. Output Buffer NULL. 8.8.6.4.
SCM3712 REFERENCE MANUAL 75 9. Annexes 9.1. Annex A 9.1.1. Status words table SW1 SW2 Description 0x90 0x00 NO ERROR 0x67 0x00 LENGTH INCORRECT 0x6D 0x00 INVALID INSTRUCTION BYTE 0x6E 0x00 CLASS NOT SUPPORTED 0x6F 0x00 UNKNOWN COMMAND 0x63 0x00 AUTHENTICATION ERROR 0x65 0x81 STATUS_COMMAND_FAILED 0x65 0x91 STATUS_SECUIRTY_STATUS_NOT_MET 0x68 0x00 CLASS BYTE INCORRECT 0x6A 0x81 FUNCTION NOT SUPPORTED 0x6B 0x00 WRONG PARAMETER P1-P2 9.1.2.
SCM3712 REFERENCE MANUAL 9.2. 76 Annex B – Mechanical drawings 9.2.1. SCM3712 and SCM3712 NFC Board Size: 60mm X 40.3mm / 2,36 x 1,59 Inch PCB thickness: 1.0mm ± 10% / 0,039 Inch ± 10% Max PCB height with components: 10mm / 0,39 Inch Mounting hole Diameter: 2.54mm / 0,1 Inch 33 mm 58.02mm MH Dia 3.04mm MH Dia 3.04mm 4.2mm MH dia 2.54mm MH dia 2.54mm 30mm 51.6mm All dimensions are in mm 10mm ≈ 0,39 Inch Fig.
SCM3712 REFERENCE MANUAL 77 9.2.2. SCM3712 EA and external antenna board Main board Board Size: 60mm X 40.3mm / 2,36 x 1,59 Inch PCB thickness: 1.0mm ± 10% / 0,039 Inch ± 10% Max PCB height with components: 10mm / 0,39 Inch Mounting hole Diameter: 2.54mm / 0,1 Inch 33 mm 58.02mm MH Dia 3.04mm MH Dia 3.04mm 4.2mm MH dia 2.54mm MH dia 2.54mm 30mm 51.6mm All dimensions are in mm 10mm ≈ 0,39 Inch Fig.
SCM3712 REFERENCE MANUAL 78 Antenna board Board Size: 92.7mm X 49.5mm / 3,65 x 1,95 Inch PCB thickness: 1.6mm ± 10% / 0,063 Inch ± 10% Max PCB height with components: 10mm / 0,39 Inch Mounting hole Diameter: 3mm / 0,12 Inch All dimensions are in mm 10mm ≈ 0,39 Inch Fig.
SCM3712 REFERENCE MANUAL 9.3. 79 Annex C – Installation Guidelines The SCM3712 reader is a contactless reader working on 13.56MHz. In order to enable the maximum performance the reader ideally needs to be installed in an metal free environment. The mechanical integration may not allow for metal plates or metal rings in close proximity. Smaller metallic units like single screws or rivets for mounting the reader can be used without remarkable influence on the overall performance.
SCM3712 REFERENCE MANUAL 80 9.3.1. SCM3712 & SCM3712 NFC Mount on Metal Instruction 40 ,3 60,0 >40 SCM3712 Background Metal Plate All dimensions are in mm 10mm ≈ 0,39 Inch Fig.9-4: SCM3712 & SCM3712 NFC Mount on Metal Instruction 9.3.2. SCM3712 ANT Mount on Metal Instruction 49 ,5 92,7 SCM3712 ANT >40 External Antenna Background Metal Plate All dimensions are in mm 10mm ≈ 0,39 Inch Fig.
SCM3712 REFERENCE MANUAL 81 9.3.3. SCM3712 & SCM3712 NFC Mount in Metal Environment Instruction ,3 60,0 40 >30 >40 >3 0 SCM3712 All dimensions are in mm 10mm ≈ 0,39 Inch Fig.9-6: SCM3712 & SCM3712 NFC Mount in Metal Environment Instruction 9.3.4. SCM3712 ANT Mount in Metal Environment Instruction 92,7 49 ,5 >30 >30 >3 0 External Antenna SCM3712 ANT All dimensions are in mm 10mm ≈ 0,39 Inch Fig.
SCM3712 REFERENCE MANUAL 82 9.3.5. Recommended distance between readers Contactless readers are being influenced in performance by their environment. Other contactless devices working in the same or a similar frequency range also can have an influence on the overall performance. The below drawing illustrates the minimum recommended distance between two readers without influencing each other.
SCM3712 REFERENCE MANUAL 9.4. 83 Annex D – Certifications As a service for our customers, SCM Microsystems already successfully has performed the EMI pretests to ensure the SCM3712 readers are ready for best compliance against applicable international radio certification rules like CE, FCC, VCCI or Japan Radio certification. As the reader is intended to be integrated into a final device, the final device needs to be tested against the specific rules as a complete device.
