SCM Microsystems SCL01X, Reference Manual

Page 1: ...SCM Microsystems Reference Manual version 2 0 SCL01X Multiprotocol contactless stationary reader ...

Page 2: ......

Page 3: ...Reference manual SCL01X Multiprotocol Contactless Stationary Reader SCM Microsystems Oskar Messter Strasse 13 85737 Ismaning Germany Phone 49 89 9595 5000 Fax 49 89 9595 5555 ...

Page 4: ... Typo corrections Add the Pass_through command description Manual fro both SCL010 and SCL011 products Contact information http www scmmicro com products services smart card readers terminals contactless dual interface readers html For sales information please email sales scmmicro com ...

Page 5: ... features 14 3 3 SCL01X ordering information 15 3 4 SCL01X customization options 15 3 5 Contactless communication principles and SCL01X usage recommendations 16 3 5 1 Power supply 16 3 5 2 Data exchange 16 3 5 3 Recommendations 17 3 6 Applications 18 3 6 1 General 18 3 6 2 Applications provided by SCM Microsystems 18 4 SCL01X characteristics 19 4 1 SCL01X high level architecture 19 4 1 1 Block dia...

Page 6: ... Type 3 52 6 4 5 Commands for communicating with NFC Forum Tags Type 4 54 6 4 6 PASS_THROUGH command 54 Escape commands 56 6 4 7 Sending escape commands to SCL01X 56 6 4 8 Escape command codes 56 6 4 9 READER_GETCARDINFO 57 6 4 10 READER_LED_CONTROL_BY_FW 57 6 4 11 READER_LEDCONTROL 57 6 4 12 READER_CNTLESS_GET_ATS_ATQB 58 6 4 13 READER_CNTLESS_GET_TYPE 58 6 4 14 READER_CNTLESS_SET_TYPE 59 6 4 15 ...

Page 7: ...7 3 4 Snap on card holder 78 ...

Page 8: ...ent 1 2 2 Section 15 105 b Note This equipment has been tested and found to comply with the limits for a Class B digital device pursuant to part 15 of the FCC Rules These limits are designed to provide reasonable protection against harmful interference in a residential installation This equipment generates uses and can radiate radio frequency energy and if not installed and used in accordance with...

Page 9: ...ode or any portion thereof to any license obligations of such Open Source Software If the document contains technical drawings related to SCM Microsystems products they are provided for documentation purposes only SCM Microsystems does not grant you any license to its designs 1 4 Trademarks MIFARE is a registered trademark of NXP Semiconductors BV FeliCa is a registered trademark of Sony Corporati...

Page 10: ...heir applications 2 2 Target audience This document describes the technical implementation of SCL01X The manual targets software developers It assumes knowledge about 13 56 MHz contactless technologies like ISO IEC 14443 and commonly used engineering terms Should you have questions you may send them to support scmmicro com 2 3 Product version corresponding to the manual This manual is related to t...

Page 11: ...Type A with extensions for security NXP NA Not applicable NAD Node Address NDEF NFC Data Exchange Format data structure defined by the NFC Forum for NFC Forum tags NFC Near Field Communication Nibble Group of 4 bits 1 digit of the hexadecimal representation of a byte Example 0xA3 is represented in binary as 10100011 b The least significant nibble is 0x3 or 0011 b and the most significant nibble is...

Page 12: ...ge between systems Near Field Communication Interface and Protocol NFCIP 1 ISO IEC 18092 2004 E ISO IEC NFC Forum tag type 1 NFCForum TS Type 1 Tag_1 0 NFC Forum NFC Forum tag type 2 NFCForum TS Type 2 Tag_1 0 NFC Forum NFC Forum tag type 3 NFCForum TS Type 3 Tag_1 0 NFC Forum NFC Forum tag type 4 NFCForum TS Type 4 Tag_1 0 NFC Forum PC SC Interoperability Specification for ICCs and Personal Compu...

Page 13: ...5 B6 B7 B8 B9 B10 B11 B0 B1 B2 B3 Least significant nibble Most significant nibble 1 Byte 8 bits 2 nibbles Bit number 0 Bit number 5 String of 12 bytes Byte number 11 Byte number 2 Example 163 decimal number is represented in hexadecimal as 0xA3 in binary as 10100011 b The least significant nibble of 0xA3 is 0x3 in hexadecimal 0011 b in binary The most significant nibble of xA3 is 0xA in hexadecim...

Page 14: ...investment providing both flexibility and fast time to market for new applications as well as minimum risk linked to contactless technology standards evolution As a latest generation product SCL01X can be supported by SCM s middleware that resides above the PC SC API and offers better portability of applications and abstraction of smart card related details that need to be handled by applications ...

Page 15: ...t those accessories are incompatible with each other i e when the snap on card holder is fitted on the SCL01X the cradle cannot be used anymore 3 4 SCL01X customization options Upon request SCM can customize The color of the casing The logo The product label The USB strings Terms and conditions apply please contact your local SCM representative or send an email to sales scmmicro com ...

Page 16: ...tional to the magnetic flux going through the antenna of the user token 3 5 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 It is also use as a fundamental clock input for the integrated circuit microprocessor to function To send data to the user token the reader modulates the amplitude of the f...

Page 17: ...n its driver only 1 slot This means that in the event several user tokens are in the field of the SCL01X only one will be active It is recommended to present only one user credential at a time in front of SCL01X The communication between the reader and the user token is sensitive to the geometry of the system reader user token Parameters like the geometry and specially the relative size of the rea...

Page 18: ...d by software developers on the host 3 6 2 Applications provided by SCM Microsystems SCM Microsystems does not provide payment or transport applications SCM Microsystems provides a few applications for development and evaluation purposes that can function with SCL01X They are available within the software development kit There are many tools provided but the two main ones are The NFC forum tag rea...

Page 19: ...ch features The NFC front end ensures the coding decoding framing modulation demodulation required for the RF communication It is controlled by the device controller through registers The matching circuitry provides the transmission and receiver paths adaptation for the antenna to function properly 4 1 2 Software architecture Applications can interface with the driver directly through the PC SC in...

Page 20: ... Grams External dimensions L 72mm W 65mm H 11 6 mm Default color Translucent black Drawing with dimensions of the SCL01X and accessories can be found in annex 4 2 2 LED behavior The LED behavior of the SCL01X is given below SCL01X states LED Indication GREEN After plug in Driver is not installed or driver is installed but either some files related to SCL01X or OS resource manager is deleted missin...

Page 21: ...ce 12Mbit s Device Class Vendor PID 0x5291 SCL010 0x5293 SCL01X VID 0x04E6 API PC SC 2 0 ID1 format tokens supported NFC forum tag type 1 through SCM specific APDU NFC forum tag type 2 through PC SC defined APDUs NFC forum tag type 3 through SCM specific APDU NFC forum tag type 4 through PC SC APDUs ISO IEC 14443 4 PICC type A and type B MIFARE Non Secure FeliCa Type B memory card PICC through SCM...

Page 22: ...er and a card through PC SC stack The DFU utility comes with a specific driver for dynamic Device Firmware Upgrade DFU through the USB interface Operating systems supported by DFU tool Windows 2000 Windows 2003 Server 32 64 bit Windows XP 32 64 bit Windows Vista 32 64 bit Windows Server 2008 32 64 bit 5 3 Driver 5 3 1 SCL01X listing SCL01X is listed by PC SC applications as SCM Microsystems Inc SC...

Page 23: ... is built as defined in the PC SC specification For NFC Forum tag types 1 and 3 there is no definition in PC SC 5 3 3 1 Determining the technology of the user credential The ScardControl method of PC SC see http msdn microsoft com en us library aa379474 VS 85 aspx should be used to send the 0x90 IOCTL to SCL3711 in order to determine what type of technology is the user token based on The output bu...

Page 24: ...ignation 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 Nibble 0 means T 0 3 0x01 TD2 Nibble 0 indicates no TA3 TB3 TC3 TD3 Nibble 1 means T 1 4 3 n 0x80 A status indicator may be present in an optional TLV data object 0x4F Optional TLV data object Tag Application identifier Lentgh 1 byte RID Regis...

Page 25: ...esent 2 historical bytes in following ATR 2 0x80 TD1 Nibble 8 indicates no TA2 TB2 TC2 and TD2 present Nibble 0 means T 0 3 0x01 TD2 Nibble 0 indicates no TA3 TB3 TC3 Nibble 1 means T 1 4 0x02 Card Mode NFC TAG operating at Passive 106 baud rate 5 0x44 Card Type Card type is Topaz 6 0xXX TCK XOR of all previous bytes Example of the ATR built for a Topaz tag ...

Page 26: ... no TA2 TB2 TC2 and TD2 present Nibble 0 means T 0 3 0x01 TD2 Nibble8 indicates no TA3 TB3 TC3 Nibble 1 means T 1 4 0x04 Card Mode NFC TAG operating at Passive 212 baud rate 5 0x43 Card Type Card type is Felica 6 0xFD IFS Maximum frame size of felica card 7 14 ID Felica card Identifier 8 bytes 15 0xXX Timeout Write Timeout indicated by card 16 0xXX TCK XOR of all previous bytes Example of the ATR ...

Page 27: ...0x80 TD1 Nibble8 indicates no TA2 TB2 TC2 Nibble 0 means T 0 3 0x01 TD2 Nibble8 indicates no TA3 TB3 TC3 Nibble 1 means T 1 4 3 n Historical bytes or application information Type A the historical bytes from the ATS up to 15 bytes Type B 8 bytes Byte 0 through 3 application data from ATQB Byte 4 through 6 protocol info byte from ATQB Byte 7 higest nibble is the MBLI maximum buffer length index from...

Page 28: ...efault PICC I O data rate is 106kbps and the maximum supported data rate is 848kbps 5 4 1 1 CCID class requests supported Abort Get Clock Frequencies Get Data rates 5 4 1 2 CCID messages supported The following CCID messages are supported when received through bulk out endpoint PC_to_RDR_IccPowerOn PC_to_RDR_IccPowerOff PC_to_RDR_GetSlotStatus PC_to_RDR_XfrBlock PC_to_RDR_Escape PC_to_RDR_Abort Th...

Page 29: ...turned when a parity error condition is detected This error will be reported in the response to a PC_to_RDR_XfrBlock message This error code has been defined in the error code table 6 2 2 of the CCID specification 5 4 2 Automatic PPS Automatic PPS is implemented in SCL01X s firmware This means that by default SCL01X switches to the maximum communication speed indicated by the card during its selec...

Page 30: ...ta in Le 0xFF 0xCA 0x00 0x00 XX Setting Le 0x00 can be used to request the full UID or PUPI is sent back e g for ISO14443A single 4 bytes double 7 bytes triple 10 bytes for ISO14443B 4 bytes PUPI 6 1 1 3 Response Data Out UID SW1 SW2 6 1 1 4 Status Words SW1 SW2 Description 0x90 0x00 NO ERROR 0x62 0x82 End of UID reached before Le bytes Le is greater than UID length 0x6C 0xXX Wrong Length 0xXX is ...

Page 31: ...SCL01X REFERENCE MANUAL 31 6 1 1 5 Examples ISO14443 4A ISO14443 4B MIFARE 4K MIFARE Ultralight NFC Forum tag type 1 NFC Forum tag type 3 ...

Page 32: ... in this manual 6 1 2 3 Response Output buffer of the escape command 6 1 2 4 Example To get the ATS or ATQB of the ISO14443 4 based user token you can use this APDU to send the READER_CNTLESS_GET_ATS_ATQB 0x93 escape command Type A passport Type B passport To get the reader status about support of 848Kbps you can use this APDU to send the READER_CNTLESS_848KBPS 0x9D escape command By default the S...

Page 33: ...lue 65535 If Le 0x00 then all the bytes until the end of the file are read within the limit of 256 for a short Le field and 65536 for an extended Le field 6 2 1 3 Response Data Out Data SW1 SW2 6 2 1 4 Status words SW1 SW2 Description 0x90 0x00 NO ERROR 0x62 0x81 WARNING part of the returned data may be corrupted 0x82 WARNING end of file reached before Le bytes where read 0x67 0x00 Length incorrec...

Page 34: ...01X REFERENCE MANUAL 34 6 2 1 5 Example For a MIFARE Classic 1K card which has the following memory content To read the seventh block you have to issue the following command and get the following response ...

Page 35: ...P2 indicate the memory block number where data should be written Lc 0x10 for MIFARE Classic 1K 4K Lc 0x04 for MIFARE Ultralight 6 2 2 3 Response Data Out SW1 SW2 6 2 2 4 Status Words SW1 SW2 Description 0x90 0x00 NO ERROR 0x69 0x81 Command not supported 0x64 0x00 State of the non volatile memory unchanged 6 2 2 5 Example For a MIFARE Classic Ultralight card which has the following memory content I...

Page 36: ...SCL01X REFERENCE MANUAL 36 Results into the following memory mapping ...

Page 37: ...Format CLA INS P1 P2 Lc Data in 0xFF 0x82 0x00 Key Type Key Length Key value Where P2 can have the following values please refer to MIFARE documentation from NXP for further details on what is key A and Key B 0x60 to use the Key A 0x61 to use the Key B 6 2 3 3 Response Data Out SW1 SW2 6 2 3 4 Status Words SW1 SW2 Description 0x90 0x00 NO ERROR 0x69 0x83 Reader key not supported 0x85 Secured trans...

Page 38: ... Data in 0xFF 0x86 0x00 0x00 0x05 Data Where the data field is structured as follow Byte Value Description B0 0x01 Version B1 Address MSB B2 Address LSB B3 0x60 Key A 0x61 Key B B4 RFU should be set to 0x01 Information about memory structure of MIFARE Classic must be requested from NXP Semiconductors 6 2 4 3 Response Data Out SW1 SW2 6 2 4 4 Status Words SW1 SW2 Description 0x90 0x00 NO ERROR 0x63...

Page 39: ...Classic 1K card which has the following memory mapping Reading sector 0 or sector 1 of this card requires authentication with key A or key B The following example authenticates with key A of sector 0 reads block 2 authenticates against sector 1 reads block 5 ...

Page 40: ... the address of the block number addressed Where the data field is structured as follow Byte Value Description B0 0xC0 Increment 0xC1 Decrement B1 Block number B2 B5 Value LSB first 6 2 5 3 Response Data Out SW1 SW2 6 2 5 4 Status Words SW1 SW2 Description 0x90 0x00 NO ERROR 0x67 0x00 Length incorrect 0x68 0x00 CLA byte incorrect 0x6A 0x81 Function not supported 0x6B 0x00 Wrong P1 P2 parameters 6 ...

Page 41: ...P3 Data Description of the APDU commands can be found in ISO IEC 7816 4 specification 6 3 1 2 Response Data Out PICC answer as defined in ISO IEC 7816 4 SW1 SW2 As defined in ISO IEC 7816 4 6 3 1 3 Status Words SW1 SW2 Description See ISO IEC 7816 4 As defined in ISO IEC 7816 4 6 3 1 4 Example The following APDU sequence reads the first 256 bytes of the data group 1 as specified in ICAO LDS logica...

Page 42: ...ds SW1 SW2 Description User should refer to the status words defined by the PICC manufacturer for a description of the status words 6 3 2 4 Example Let s consider the Select command defined in ISO7816 4 This command being ISO can be sent to the user token in 2 different ways Using the T CL command Using the T CL user command Here are the 2 answers for the select command The T CL command is neverth...

Page 43: ...ESFire response data SW1 SW2 6 4 2 Commands for communicating with NFC Forum Tags Type 1 Commands for Static and Dynamic Memory Models Read Identification RID Read All Blocks 0 Eh RALL Read Byte READ Write Erase Byte WRITE E Write No Erase Byte WRITE NE Commands for Dynamic Memory Model Read Segment RSEG Read 8 Bytes READ8 Write Erase 8 Bytes WRITE E8 Write No Erase 8 Bytes WRITE NE8 6 4 2 1 Read ...

Page 44: ...ID2 UID3 0x90 0x00 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 using the Get UID APDU described earlier in this manual ...

Page 45: ...nd the whole of the static memory blocks 0x0 0xE Format CLA INS P1 P2 P3 Data 0xFF 0x52 0x00 0x00 0x00 Response Data SW1 SW2 HR0 HR1 120 bytes Blocks 0 E 0x90 0x00 Example For an NFC Forum tag type 1 that has the following memory content The following 2 APDUs can be sent to retrieve the UID and read all the memory blocks ...

Page 46: ... 0x00 Byte Address 0x00 Where P2 codes the address of the memory byte in the following way Bit numbers Description b7 b3 Block value between 0x0 and 0xE b2 b0 Byte within the block value between 0 and 7 Response Data SW1 SW2 1 byte of data 9000 Example For an NFC forum tag type 1 which has the following memory dump Sending the following sequence of APDU will read byte 0x01 of block 0x00 through 0x...

Page 47: ...in the following way Bit numbers Description b7 b3 Block value between 0x0 and 0xE b2 b0 Byte within the block value between 0 and 7 Response Data SW1 SW2 Byte value that has been written 0x90 0x00 Example For an NFC forum tag type 1 which has the following memory dump The following sequence does A READ of the byte 0x03 in block 0x07 A WRITE ERASE of the byte 0x03 in the block 0x07 with value 0x0A...

Page 48: ...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 Format CLA INS P1 P2 P3 Data 0xFF 0x58 0x00 Byte Address 0x01 1 byte of data to be written Where P2 codes the address of the memory byte in the following way Bit numbers Description b7 b3 Block value between 0x0 and 0xE b2 b0 Byte within the b...

Page 49: ... 0x09 A READ of the byte 0x03 in block 0x07 One can notice that the value of the byte after the WRITE NO ERASE is not 0x09 but 0x0B because the memory value before the operation was 0x02 The memory result of a WRITE NO ERASE command is the logical OR of the value before the operation and the value written description Value binary Value 0x Memory value before 00000010 b 0x02 Value written 00001001 ...

Page 50: ... specific Topaz tags Format CLA INS P1 P2 P3 Data 0xFF 0x5A 0x00 Segment Address 0x00 P2 Segment Address b8 b5 Segment 0x0 0xF b4 b1 0 Response Data SW1 SW2 128 bytes of data 0x90 0x00 6 4 2 7 Read 8 bytes READ8 Description This command reads out a block of memory Format CLA INS P1 P2 P3 Data 0xFF 0x5C 0x00 Block Address 0x00 P2 Block Address b8 b1 General block 0x00 0xFF Response Data SW1 SW2 8 b...

Page 51: ...k of memory This command does not erase the value of the targeted block before writing the new data Using this command EEPROM bits can be set but not reset Format CLA INS P1 P2 P3 Data 0xFF 0x60 0x00 Block Address 0x08 8 bytes of data to be written P2 Block Address b8 b1 General block 0x00 0xFF Response Data SW1 SW2 8 bytes of data 0x90 0x00 Example Sending the following command to an NFC Forum ty...

Page 52: ... 4 Commands for communication with NFC Forum Tags Type 3 Proprietary APDUs defined for the following FeliCa non secure commands are described in this section SCL01X does not support FeliCa secure commands REQC Request Service Request Response Read Write 6 4 4 1 REQC Description This command is used to detect the presence of a NFC Forum tag type 3 in the field Format CLA INS P1 P2 P3 Data 0xFF 0x40...

Page 53: ... area version list 2 n 0x90 0x00 6 4 4 3 Request response Description When an NFC Forum tag type 3 receives this command it responds with its current mode 0 1 2 Format CLA INS P1 P2 P3 Data 0xFF 0x44 0x00 0x00 0x00 Response Data SW1 SW2 8 bytes IDm Mode 0x90 0x00 6 4 4 4 Read Description When an NFC Forum tag type 3 receives this command it responds with the record value of the specified service F...

Page 54: ...xFF 0x4A 0x00 0x00 0x00 Response Data SW1 SW2 8 bytes IDm No of System Codes n System Code List 2n 0x90 0x00 6 4 5 Commands for communicating with NFC Forum Tags Type 4 There is no need to define specific APDU commands as command T CL command already defined earlier can be used Please refer to NFC Forum tag type 4 specification for definition of the commands to be used 6 4 6 PASS_THROUGH command D...

Page 55: ...le This command can be used to send commands to a MIFARE Ultralight C The command for generating an 8 byte random number on MIFARE Ultralight C is 0x1A 0x00 Sending the APDU 0xFF 0xEF 0x00 0x00 0x02 0x1A 0x00 Will return 0xAF followed by 8 byte random number ...

Page 56: ... the application can send again the same escape command The following escape commands are supported by SCL01X Escape command Code READER_GETCARDINFO 0x11 READER_LEDCONTROL 0x19 READER_CNTLESS_GET_ATS_ATQB 0x93 READER_CNTLESS_GET_TYPE 0x94 READER_CNTLESS_SET_TYPE 0x95 READER_CNTLESS_RF_SWITCH 0x96 READER_CNTLESS_RAW_CFG 0x97 READER_CNTLESS_RAW_XMIT 0x98 READER_ CNTLESS_DISABLE_PPS 0x99 READER_CNTLE...

Page 57: ..._ Memory Card 0x1_ T CL card 0x2_ Dual Mode Card B2 Lower nibble 0x_0 Type A card Topaz 0x_1 Type B card 0x_4 Felica 212 kbps card 0x_8 Felica 424 kbps card 6 4 10 READER_LED_CONTROL_BY_FW This escape command may be used to enable or disable LED control by the firmware The input buffer is Byte Value Description B0 0xB2 Escape command code B1 0x00 Disable LED control by FW 0x01 Enable LED control b...

Page 58: ...put buffer contains the ATS bytes or the ATQB bytes depending on the type of PICC placed on the reader 6 4 13 READER_CNTLESS_GET_TYPE This escape command retrieves the type of the card which SCL01X is configured to poll for The input buffer shall contain the escape command code Input buffer 0x94 The output buffer shall point to a BYTE buffer which will contain the type value coded as Value Descrip...

Page 59: ...ncy of SCL01X for applications where only type A or only type B cards are expected The default is Type A type B FeliCa 0x1B The input buffer shall contain 2 bytes Byte Value Description B0 0x95 Escape command code B1 0x00 Type A 0x01 Type B 0x02 Type A type B 0x18 FeliCa only 0x19 FeliCa type A 0x1A FeliCa type B 0x1B FeliCa type A type B The output buffer is Output buffer NULL ...

Page 60: ...ut buffer is 0xFF the output buffer is a BYTE buffer with 2 possible values Output buffer Description 0x01 RF field is OFF 0x00 RF field is ON 6 4 16 READER_CNTLESS_RAW_CFG This escape command switches SCL01X to raw mode When SCL01X is in raw mode it only polls for one type of contactless card SCL01X is by default not in this mode and therefore READER_CNTLESS_RAW_XMIT would fail The input buffer c...

Page 61: ...llowing example uses the raw mode to send a REQB command First we have to switch the SCL01X into raw mode for type B communication Byte Value Description B0 0x97 READER_CNTLESS_RAW_CONFIG code B1 0x01 Type B will be used Then we can send the following bytes to obtain the ATQB response of any type B user token in the field Byte Value Description B0 0x98 READER_CNTLESS_RAW_XMIT code B1 0x05 FWI is s...

Page 62: ...sed to enable disable 848kbps support by SCL01X as well as query whether 848kbps is currently enabled or disabled by SCL01X The RF communication with a user token will only switch to 848Kbps provided the user token supports this baudrate and provided automatic PPS is ON The input buffer shall contain 2 bytes Byte Value Description B0 0x9D Escape command code B1 0x00 Disable 848Kbps support 0x01 En...

Page 63: ...from PCD to PICC 0x03 106Kbps from PICC to PCD 848Kbps from PCD to PICC 0x10 212Kbps from PICC to PCD 106Kbps from PCD to PICC 0x11 212Kbps in both directions 0x12 212Kbps from PICC to PCD 424Kbps from PCD to PICC 0x13 212Kbps from PICC to PCD 848Kbps from PCD to PICC 0x20 424Kbps from PICC to PCD 106Kbps from PCD to PICC 0x21 424Kbps from PICC to PCD 212Kbps from PCD to PICC 0x22 424Kbps in both ...

Page 64: ...ame D is required for both communication directions b8 0 if different D is supported for each communication direction Encoding of the baud rate to be forced if B1 value is 0x01 No need to send this byte in case B1 has the value x00 NULL If B1 0x00 The output buffer is Output buffer NULL A card connect has to be done after this escape command is sent to switch baudrate to the value set by the user ...

Page 65: ... below Byte Description B0 B1 VID 2 Bytes B2 B3 PID 2 Bytes B4 B17 Serial Number 14 Bytes B18 PNP String length up to 127 bytes B19 Bx PNP String up to 127 bytes 6 4 23 READER_GETSLOTINFO This escape command is used to retrieve the slot information The input buffer contains the escape command code Input buffer 0xD9 The output buffer is Byte Value Description B0 0x01 Only 1 slot supported on SCL01X...

Page 66: ...al interface card 0x43 FeliCa B2 PUPI UID Length 0x08 For FeliCa cards THEN EITHER B3 B12 PUPI UID bytes 0x00 byte padding used if length smaller than 10 B13 0x00 CID not supported 0x01 CID supported B14 0x00 NAD not supported 0x01 NAD supported B15 Bit Rate Capability B16 FWI B17 IFSC B18 MBLI B19 SAK B20 SFGI OR B3 B10 8 Bytes NFCID2 B11 Request service command response time parameter see JIS 63...

Page 67: ...4A MIFARE FeliCa 6 4 25 READER_IS_SCL01x This escape message may be used to check if the connected device is an SCL01x device The input buffer contains the escape command code Input buffer 0xDB The output buffer shall point to a BYTE buffer with following possible values Output buffer Description 0x01 SCL01x device connected NULL Device connected is not SCL01x ...

Page 68: ...ATTRIB_WITH_INF This Escape command may be used to send application layer bytes to a type B card along with the ATTRIB command in the higher layer INF field The input buffer is Byte Value Description B0 0xE2 Escape command code B1 onwards INF Bytes ...

Page 69: ... 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 ...

Page 70: ...S 0xFF9B define CCID_SET_PUPI_ON 0x019B define CCID_SET_PUPI_OFF 0x009B define MINTIMEOUT 300 ifdef __cplusplus endif File Name T_pupi CPP include windows h include winbase h include stdio h include conio h include winscard h include winerror h include T_pupi H VOID main VOID SCARDCONTEXT ContextHandle SCARDHANDLE CardHandle BYTE OutByte WORD InWord i DWORD ActiveProtocol ICC protocol ULONG InBufL...

Page 71: ...L ContextHandle if ret SCARD_S_SUCCESS ret SCardConnect ContextHandle ReaderName 0 SCARD_SHARE_SHARED SCARD_PROTOCOL_T0 SCARD_PROTOCOL_T1 CardHandle ActiveProtocol if ret SCARD_S_SUCCESS get actual PUPI status ON OFF InBufLen 2 InWord CCID_GET_PUPI_STATUS ret SCardControl CardHandle IOCTL_CCID_ESCAPE InWord InBufLen OutByte 1 ResLen printf n Get PUPI status lx 2x ret OutByte Reader 0 dwCurrentStat...

Page 72: ...Word CCID_SET_PUPI_ON ret SCardControl CardHandle IOCTL_CCID_ESCAPE InWord InBufLen OutByte 1 ResLen ret SCardDisconnect CardHandle SCARD_RESET_CARD ret SCardConnect ContextHandle ReaderName 0 SCARD_SHARE_SHARED SCARD_PROTOCOL_T0 SCARD_PROTOCOL_T1 CardHandle ActiveProtocol get actual PUPI status ON OFF InBufLen 2 InWord CCID_GET_PUPI_STATUS ret SCardControl CardHandle IOCTL_CCID_ESCAPE InWord InBu...

Page 73: ...PI InBufLen 2 InWord CCID_SET_PUPI_OFF ret SCardControl CardHandle IOCTL_CCID_ESCAPE InWord InBufLen OutByte 1 ResLen ret SCardDisconnect CardHandle SCARD_RESET_CARD ret SCardConnect ContextHandle ReaderName 0 SCARD_SHARE_SHARED SCARD_PROTOCOL_T0 SCARD_PROTOCOL_T1 CardHandle ActiveProtocol get actual PUPI status ON OFF InBufLen 2 InWord CCID_GET_PUPI_STATUS ret SCardControl CardHandle IOCTL_CCID_E...

Page 74: ...printf nATR for i 0 i Reader cbAtr i printf 2x Reader rgbAtr i printf n n ret SCardDisconnect CardHandle SCARD_RESET_CARD else printf n SCardConnect failed with 0x 8lX ret ret SCardReleaseContext ContextHandle else printf n SCardEstablishContext failed with 8lX ret printf npress any key to close the test tool n getch ...

Page 75: ...SCL01X REFERENCE MANUAL 75 7 3 Annex C Mechanical drawings 7 3 1 Top casing ...

Page 76: ...SCL01X REFERENCE MANUAL 76 7 3 2 Bottom casing ...

Page 77: ...SCL01X REFERENCE MANUAL 77 7 3 3 Cradle ...

Page 78: ...SCL01X REFERENCE MANUAL 78 7 3 4 Snap on card holder ...