RFID MODULE NFC MIFARE MODULE SL060 User Manual Version 1.
StrongLink SL060 CONTENT 1. FEATURES ..................................................................................................................... 4 2. DESCRIPTION .............................................................................................................. 5 3. PINNING INFORMATION .......................................................................................... 5 4. Communication Protocol ...................................................................................
StrongLink SL060 4-4-2-24. Get version of Ntag213/216........................................................................................... 13 4-4-2-25. Read page of data of Ntag213/216................................................................................ 14 4-4-2-26. Fast read page of data of Ntag213/216 ........................................................................ 14 4-4-2-27. Get NFC counter of Ntag213/216 .......................................................................
StrongLink SL060 1. FEATURES • Tags supported: Mifare 1k, Mifare 4k, Mifare UltraLight, Mifare UltraLight C, NTAG203, NTAG213, and NTAG216. • Built-in antenna • UART Interface, baud rate 9,600 ~ 115,200 bps(Default:9600bps) • 13.56MHz RF Operating Frequency • Protocol supported: ISO14443, ISO18092 NFCIP-1 mode(text&url) • 2.5 ~3.6 VDC Operating, I/O supports 5.0 VDC • Work current less than 50mA@3.
StrongLink SL060 2. DESCRIPTION Being developed based on NXP’s NFC transponder IC, NFC Module SL060 is a mini NFC reader/writer. This RFID module supports MIFARETM Classic 1K, MIFARETM Classic 4K, MIFARE UltralightTM, MIFARE DESFireTM and NFC NFCIP-1 mode. The maximum working current is less than 50mA. It integrates all necessary components and antenna in the PCB. SL060 can offer NFCIP-1 functions. Users can send NFC message to NFC device to open a web URL or display text words in the window. 3.
StrongLink SL060 4. Communication Protocol 4.1 Communication Setting The communication protocol is byte oriented. Both sending and receiving bytes are in hexadecimal format. The communication parameters are as follows, Baud rate: 9600bps(default) Data: 8 bits Stop: 1 bit Parity: None Flow control: None 4.
StrongLink SL060 Attention If there is any byte equaling to AA occurs between Len and Checksum, one byte 00 will be added after this byte to differentiate preamble. However, the Len keeps unchanged. Example, reading data (0x00112233445566778899AABBCCDDEEFF) from block 1 SL060 -> Host：ABB1600000009020000112233445566778899AA00BBCCDDEEFF0B 4.
StrongLink 0x5402 0x5502 0x0D01 0x0E01 SL060 Authenticate password of Ntag213/216 Get ECC signature of Ntag213/216 Set the NFC field Send the NFC command Status Overview Table 2 Status Description 0x00 Operation successes 0x01 NFC connect fails 0x0A Operation fails 0x0B Command is not supported 0x0C Parameter is error 0x0D No cards 0x0E RF base station is damaged 0x14 Searching card fails 0x15 Reset card fails 0x16 Verifying key fails 0x17 Reading fails 0x18 Writing fails 4-4.
StrongLink SL060 0xAA 0xBB Len DeviceID 0x02 0x01 Status Checksum Status: 0x00: Operation succeed Remark: SL060 only response to the command that Device ID is in accord with itself, and broadcast command that DeviceID equals to 0x0000 4-4-1-3. Get device ID 0xAA 0xBB Len DeviceID 0x03 0x01 Checksum Response: 0xAA 0xBB Len DeviceID 0x03 0x01 Status Data Checksum Data: 2 bytes device ID Status: 0x00: Operation succeed 4-4-1-4.
StrongLink SL060 0xAA 0xBB Len DeviceID 0x02 0x02 Checksum Data: None Response: 0xAA 0xBB Len DeviceID 0x02 0x02 Status Data Checksum Data: UID Status: 0x00: Operation succeed 0x0A: Operation fails 4-4-2-3. Select card (Card A) 0xAA 0xBB Len DeviceID 0x03 0x02 Data Checksum Data: UID Response: 0xAA 0xBB Len DeviceID 0x03 0x02 Status Data Checksum Data: SAK Status: 0x00: Operation succeed 0x0A: Operation fails 4-4-2-4.
StrongLink SL060 Status: 0x00: Operation succeed 0x18: Writing fails 4-4-2-8. Initialize electronic purse 0xAA 0xBB Len DeviceID 0x0A 0x02 Data Checksum Data: 1 byte absolute block number+4 bytes data Response: 0xAA 0xBB Len DeviceID 0x0A 0x02 Status Checksum Status: 0x00: Operation succeed 0x18: Writing fails 4-4-2-9.
StrongLink SL060 Status: 0x00: Operation succeed 0x18: Writing fails 4-4-2-14. Get ATS of CPU A 0xAA 0xBB Len DeviceID 0x10 0x02 Checksum Response: 0xAA 0xBB Len DeviceID 0x10 0x02 Status Data Checksum Data: ATS Status: 0x00: Operation succeed 0x18: Writing fails 4-4-2-15.
StrongLink SL060 0x16: Verifying key fails 4-4-2-19. Change password of Ultralight_C 0xAA 0xBB Len DeviceID 0x42 0x02 Data: 16 byte new password Response: 0xAA 0xBB Len DeviceID 0x42 0x02 Status: 0x00: Operation succeed 0x18: Writing fails 4-4-2-20. SHC1102 card check password 0xAA 0xBB Len DeviceID 0x20 0x02 Data: 4 bytes password Response: 0xAA 0xBB Len DeviceID 0x20 0x02 Status: 0x00: Operation succeed 0x16: Verifying key fails 4-4-2-21.
StrongLink SL060 Data: Status: 8 bytes Product version information 0x00: Operation succeed 0x17: Reading fails 4-4-2-25. Read page of data of Ntag213/216 0xAA 0xBB Len DeviceID 0x51 0x02 Data: 1 byte start page address Data Checksum Response: 0xAA 0xBB Len DeviceID 0x51 0x02 Status Data Checksum Data: 16 bytes Data content of the addressed pages Status: 0x00: Operation succeed 0x17: Reading fails 4-4-2-26.
StrongLink 0x17: SL060 Reading fails 4-4-3 NFC Function Command 4-4-3-1. Set the NFC field 0xAA 0xBB Len DeviceID 0x0D 0x01 Data Checksum Data: 0: turn off the NFC field 1: turn on the NFC field Response: 0xAA 0xBB Len DeviceID 0x0D 0x01 Status Checksum Status: 0x00: Operation succeed 4-4-3-2. Send the NFC command 0xAA 0xBB Len DeviceID 0x0E 0x01 Data Checksum Data: NFC command, see Table 3 Table 3 Language： 0: N/A Text : 0x54—‘T’ 1:English 2:German 3:French Protocol: 0:N/A 1:http://www.
StrongLink SL060 23:tftp: 24:btspp:// 25:btl2cap:// 26:btgoep:// 27:tcpobex:// 28:irdaobex:// 29:file:// 30:urn:epc:id: 31:urn:epc:tag: 32:urn:epc:pat: 33:urn:epc:raw: 34:urn:epc: 35:urn:nfc: 36-255:RFU Example: aabb1f0000000e015401534e4550207465737420737472696e6720504e2d3531320074 means sending the text’ SNEP test string PN-512’. Response: 0xAA 0xBB Len DeviceID 0x0E 0x01 Status Checksum Status: 0x00: Operation succeed 0x01: NFC connect fails Remark: Uri must be lowercase letters. http://www.
Federal Communications Commission (FCC) Interference Statement THIS DEVICE COMPLIES WITH PART 15 OF THE FCC RULES. OPERATION IS SUBJECT TO THE FOLLOWING TWO CONDITIONS: (1) THIS DEVICE MAY NOT CAUSE HARMFUL INTERFERENCE, AND (2) THIS DEVICE MUST ACCEPT ANY INTERFERENCE RECEIVED, INCLUDING INTERFERENCE THAT MAY CAUSE UNDESIRED OPERATION. NOTE: THE GRANTEE IS NOT RESPONSIBLE FOR ANY CHANGES OR MODIFICATIONS NOT EXPRESSLY APPROVED BY THE PARTY RESPONSIBLE FOR COMPLIANCE.
Regulatory Module Integration Instructions This module has been granted modular approval for mobile applications. OEM integrators for host products may use the module in their final products without additional FCC certification if they meet the following conditions. Otherwise, additional FCC approvals must be obtained. The host product with the module installed must be evaluated for simultaneous transmission requirements.
Device Classifications Since host devices vary widely with design features and configurations module integrators shall follow the guidelines below regarding device classification and simultaneous transmission, and seek guidance from their preferred regulatory test lab to determine how regulatory guidelines will impact the device compliance. Proactive management of the regulatory process will minimize unexpected schedule delays and costs due to unplanned testing activities.
Simultaneous Transmission Evaluation This module has not been evaluated or approved for simultaneous transmission as it is impossible to determine the exact multi-transmission scenario that a host manufacturer may choose. Any simultaneous transmission condition established through module integration into a host product must be evaluated per the requirements in KDB447498D01(8) and KDB616217D01,D03 (for laptop, notebook, netbook, and tablet applications).
