User's Manual
Table Of Contents
- 1. FEATURES
- 2. DESCRIPTION
- 3. PINNING INFORMATION
- 4. Communication Protocol
- 4.1 Communication Setting
- 4.2 Communication Format
- 4.3 Command Overview
- 4-4. Command List
- 4-4-1 System Function Command
- 4-4-2 ISO14443A - Mifare Function Command
- 4-4-2-1. Request(Card A)
- 4-4-2-2. Anticollision(Card A)
- 4-4-2-3. Select card (Card A)
- 4-4-2-4. Halt (Card A)
- 4-4-2-5. Authenticate
- 4-4-2-6. Read block
- 4-4-2-7. Write block
- 4-4-2-8. Initialize electronic purse
- 4-4-2-9. Read purse value
- 4-4-2-10. Decrease purse value (including Transfer)
- 4-4-2-11. Increase purse value (including Transfer)
- 4-4-2-12. Restore purse value
- 4-4-2-13. Transfer
- 4-4-2-14. Get ATS of CPU A
- 4-4-2-15. Exchange data between PICC and PCD according with T = CL protocol
- 4-4-2-16. Ultralight card Anticoll and Select
- 4-4-2-17. Write a page of data into ultralight card
- 4-4-2-18. Authenticate password of Ultralight_C
- 4-4-2-19. Change password of Ultralight_C
- 4-4-2-20. SHC1102 card check password
- 4-4-2-21. Read data block of SHC1102 card
- 4-4-2-22. Write data block of SHC1102 card
- 4-4-2-23. Request DESFire and reset
- 4-4-2-24. Get version of Ntag213/216
- 4-4-2-25. Read page of data of Ntag213/216
- 4-4-2-26. Fast read page of data of Ntag213/216
- 4-4-2-27. Get NFC counter of Ntag213/216
- 4-4-2-28. Authenticate password of Ntag213/216
- 4-4-3 NFC Function Command
StrongLink SL060
http://www.stronglink-rfid.com
6
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.2 Communication Format
Host to Reader:
Preamble Len DeviceID Command Data Checksum
Preamble: 2 bytes equal to 0xAABB
Len: 2 bytes, indicating the number of bytes from DeviceID to Checksum
In this reader, the first byte is effective, the second byte keep 0
DeviceID: 2 bytes
Command: 2 bytes, Command code, see Table 3
Data: Variable length depends on the command code
Checksum: 1 byte, XOR of all the bytes from DeviceID to Data
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, writing data (0x00112233445566778899AABBCCDDEEFF) to block 1
Host->SL060:AABB1600000009020100112233445566778899AA00BBCCDDEEFF0A
Reader to Host:
Preamble Len DeviceID Command Status Data Checksum
Preamble: 2 bytes equal to 0xAABB
Len: 2 bytes, indicating the number of bytes from DeviceID to Checksum
In this reader, the first byte is effective, the second byte keep 0
DeviceID: 2 bytes
Command: 2 bytes
Status: 1 byte, 00 = success, Not 0 = fail
Data Range: Response data, may blank
Checksum: 1 byte, XOR of all the bytes from DeviceID to the last of the Command
Sending data