• Operating distance: Up to 50mm, depending on tag
• Storage temperature: -40 ºC ~ +85 ºC
• Operating temperature: -25 ºC ~ +55 ºC
• Dimension: 46 × 46 × 3 mm
• The OUT pin at low level indicates tag in detective range, and high
level indicating tag out
• Auto-detection: LED is on when card is in the detection range
1
Suppots all cards above except ISO14443-4 cards like DESFire/DESFire EV1 and MifarePlus L0/L2/L3. There is
http://www.stronglink-rfid.com
1
Page 4
StrongLink SL032 V3.1
4
PIN
SYMBOL
TYPE
DESCRIPTION
1
VDD
PWR
Power supply, 2.7 to 3.6VDC
2
IN
Input
Falling edge wake up SL032 from power down mode
3
TXD
Output
Serial output port
4
RXD
Input
Serial input port
Tag auto-detection signal
high level indicating tag out
6
GND
PWR
Ground
7
NC 8 NC 9 NC
10
NC
2. PINNING INFORMATION
5 OUT Output
Attention: Pin IN must be connected HIGH voltage when working, so SL032 can
enter power down mode properly.
low level indicating tag in
Auto-detection command to control its on/off.
http://www.stronglink-rfid.com
Page 5
StrongLink SL032 V3.1
5
R6
R7
Baud rate bps
no
no
9,600
yes
no
19,200
no
yes
57,600
115,200
( default )
Preamble
Len
Command
Data
Checksum
Preamble
Len
Command
Status
Data
Checksum
3. BAUD RATE SETTING
R6 & R7 are used for setting baud rate as follows sheet
Assembled
yes yes
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: 9,600 ~ 115,200 bps
Data: 8 bits
Stop: 1 bit
Parity: None
Flow control: None
4-2. Communication Format
Host to Reader:
Preamble: 1 byte equal to 0xBA
Len: 1 byte, indicating the number of bytes from Command to Checksum
Command: 1 byte Command code, see Table 3
Data: Variable length depends on the command type
Checksum: 1 byte XOR of all the bytes from Preamble to Data
Reader to Host:
Preamble: 1 byte equal to 0xBD
Len: 1 byte indicating the number of bytes from Command to Checksum
Command: 1 byte Command code, see Table 3
Status: 1 byte Command status, see Table 4
Data: Variable length depends on the command type.
Checksum: 1 byte XOR of all the bytes from Preamble to Data
http://www.stronglink-rfid.com
Page 6
StrongLink SL032 V3.1
6
Command
Description
0x01
Select Mifare card
0x02
Login to a sector
0x03
Read a data block
0x04
Write a data block
0x05
Read a value block
0x06
Initialize a value block
0x07
Write master key (key A)
0x08
Increment value
0x09
Decrement value
0x0A
Copy value
0x10
Read a data page (Ultralight & NTAG203)
0x11
Write a data page (Ultralight & NATG203)
0x12
Download Key
0x13
Login sector via stored Key
0x20
Request for Answer to Select (ISO14443-4)
0x21
Exchange Transparent Data according to T = CL
0x40
LED control
0x50
Go to Power Down mode
0x60
3Des Authentication(Ultralight C)
0x61
Update Key(Ultralight C)
0x80
MFP WritePerso
0x81
MFP CommitPerso
0xF0
Get firmware version
0xFE
Turn on/off Auto-detection
Status
Description
0x00
Operation succeed
0x01
No tag
0x02
Login succeed
0x03
Login fail
0x04
Read fail
0x05
Write fail
0x06
Unable to read after write
0x08
Address overflow
0x09
Download Key fail
0x0A
Collision occur
0x0C
Load key fail
0x0D
Not authenticate
0x0E
Not a value block
0x0F
Input len invalid
4-3. Command Overview
Table 3
Status Overview
Table 4
http://www.stronglink-rfid.com
Page 7
StrongLink SL032 V3.1
7
0x12
MFP WritePerso fail
0x13
MFP CommitPerso fail
0x14
Ulralight c authenticate fail
http://www.stronglink-rfid.com
Page 8
StrongLink SL032 V3.1
8
0xBA
Len
0x01
Checksum
0xBD
Len
0x01
Status
UID
Type
Checksum
0xBA
Len
0x02
Sector
Type
Key
Checksum
0xBD
Len
0x02
Status
Checksum
4-4. Command List
4-4-1. Select Mifare card
Response:
Status: 0x00: Operation succeed
0x01: No tag
0x0A: Collision occur
0xF0: Checksum error
UID: The uniquely serial number of Mifare carde
Type: MFMini_4B 0x01
MFMini_7B 0x02
MF1K_4B UID/ MFPLUS2K SL1_4B UID 0x03
MF1K_7B UID/ MFPLUS2K SL1_7B UID 0x04
MF4K_4B UID/ MFPLUS4K SL1_4B UID 0x05
Mifare Plus SL0 and SL3 can tell differences via ATS(ISO14443-4). Before ATS, they have the same ATQA and
SAK(ISO14443-3). SL032 judges card type only via ISO14443-3 layer for the compatibility.
http://www.stronglink-rfid.com
Page 9
StrongLink SL032 V3.1
9
0xBA
Len
0x03
Block
Checksum
0xBD
Len
0x03
Status
Data
Checksum
0xBA
Len
0x04
Block
Data
Checksum
0xBD
Len
0x04
Status
Data
Checksum
0xBA
Len
0x05
Block
Checksum
0xBD
Len
0x05
Status
Value
Checksum
0xBA
Len
0x06
Block
Value
Checksum
0xBD
Len
0x06
Status
Value
Checksum
4-4-3. Read a data block
Block: The block number to be read, 1 byte
Response:
Status: 0x00: Operation succeed
0x04: Read fail
0x0D: Not authenticate
0xF0: Checksum error
Data: Block data returned if operation succeeds, 16 bytes.
4-4-4. Write a data block
Block: The block number to be written, 1 byte.
Data: The data to write, 16 bytes.
Response:
Status: 0x00: Operation succeed
0x05: Write fail
0x06: Unable to read after write
0x0D: Not authenticate
0xF0: Checksum error
Data: Block data written if operation succeeds, 16 bytes.
4-4-5. Read a value block
Block: The block number to be read, 1 byte.
Response:
Status: 0x00: Operation succeed
0x04: Read fail
0x0D: Not authenticate
0x0E: Not a value block
0xF0: Checksum error
Value: Value returned if the operation succeeds, 4 bytes.
4-4-6. Initialize a value block
Block: The block number to be initialized, 1 byte.
Value: The value to be written, 4 bytes.
Response:
Status: 0x00: Operation succeed
http://www.stronglink-rfid.com
Page 10
StrongLink SL032 V3.1
10
0xBA
Len
0x07
Sector
Key
Checksum
0xBD
Len
0x07
Status
Key
Checksum
0xBA
Len
0x08
Block
Value
Checksum
0xBD
Len
0x08
Status
Value
Checksum
0xBA
Len
0x09
Block
Value
Checksum
0xBD
Len
0x09
Status
Value
Checksum
0x05: Write fail
0x06: Unable to read after write
0x0D: Not authenticate
0xF0: Checksum error
Value: Value written if the operation succeeds, 4 bytes.
4-4-7. Write master key (key A)
Sector: The sector number to be written, 1 byte.
Key: Authentication key, 6 bytes
Response:
Status: 0x00: Operation succeed
0x05: Write fail
0x0D: Not authenticate
0xF0: Checksum error
Key: Authentication key written if the operation succeeds, 6 bytes.
4-4-8. Increment value
Block: The block number to be increased, 1 byte.
Value: The value to be increased by, 4 bytes.
Response:
Status: 0x00: Operation succeed
0x05: Write fail
0x06: Unable to read after write
0x0D: Not authenticate
0x0E: Not a value block
0xF0: Checksum error
Value: The value after increment if the operation succeeds, 4 bytes
4-4-9. Decrement value
Block: The block number to be decreased, 1 byte
Value: The value to be decreased by, 4 bytes
Response:
Status: 0x00: Operation succeed
0x05: Write fail
0x06: Unable to read after write
0x0D: Not authenticate
0x0E: Not a value block
http://www.stronglink-rfid.com
Page 11
StrongLink SL032 V3.1
11
0xBA
Len
0x0A
Source
Destination
Checksum
0xBD
Len
0x0A
Status
Value
Checksum
0xBA
Len
0x10
Page
Checksum
0xBD
Len
0x10
Status
Data
Checksum
0xBA
Len
0x11
Page
Data
Checksum
0xBD
Len
0x11
Status
Data
Checksum
0xF0: Checksum error
Value: The value after decrement if the operation succeeds, 4 bytes
4-4-10. Copy value
Source: The source block copy from, 1 byte
Destination: The destination copy to, 1 byte
The source and destination must in the same sector
Response:
Status: 0x00: Operation succeed
0x05: Write fail
0x06: Unable to read after write
0x0D: Not authenticate
0x0E: Not a value block (Source)
0xF0: Checksum error
Value: The value after copy if the operation succeeds, 4 bytes
4-4-11. Read a data page (Ultralight & NTAG203)
Page: The page number to be read, 1 byte
Response:
Status: 0x00: Operation succeed
0x04: Read fail
0xF0: Checksum error
Data: Block data returned if operation succeeds, 4 bytes.
4-4-12. Write a data Page (Ultralight & NTAG203)
Page: The page number to be written, 1 byte.
Data: The data to write, 4 bytes.
Response:
Status: 0x00: Operation succeed
0x05: Write fail
0x06: Unable to read after write
0xF0: Checksum error
Data: page data written if operation succeeds, 4 bytes.
http://www.stronglink-rfid.com
Page 12
StrongLink SL032 V3.1
12
0xBA
Len
0x12
Sector
Type
Key
Checksum
0xBD
Len
0x12
Status
Checksum
0xBA
Len
0x13
Sector
Type
Checksum
0xBD
Len
0x13
Status
Checksum
0xBA
Len
0x20
Checksum
0xBD
Len
0x20
Status
ATS
Checksum
0xBA
Len
0x21
Data
Checksum
0xBD
Len
0x21
Status
Data
Checksum
4-4-13. Download Key
Sector: 0 - 39
Type: Key type (0xAA: KeyA, 0xBB: KeyB)
Key: 6 bytes, stored in SL032
Bnr: 2Byte Block or Key Address to be written, MSB first.
For example,
Master Key Address is 0x9000, and write it as 0xFFFF..FF(16Bytes)
BA14809000FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFBEh
Configuration Key Address is 0x9001, and write it as 0xFFFF..FF(16Bytes)
BA14809001FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFBFh
Switch to Level 2 Key Address is 0x9002, and write it as 0xFFFF..FF(16Bytes)
BA14809002FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFBCh
Switch to Level 3 Key Address is 0x9003, and write it as 0xFFFF..FF(16Bytes)
BA14809003FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFBDh
This command commit the Write Perso and switch th e card to security level 1(SL 1 card) or
level 3(SL3 card).
Response:
Status: 0x00: Operation succeed
0x11: Communicate with card failed
0x13: Card Commit Perso failed
0xF0: Checksum error
Attention: According to NXP MifarePlus card document, Commit Perso will make effect
after you have “Write Perso” the Master KEY, Configuration KEY and SWL3 KEY.
If your card is L1 card, after Commit Perso, the card will switch L0 to L1;
If your card is L3 card, after Commit Perso, the card will switch L0 to L3.
4-4-23. Get firmware version
Response:
Status: 0x00: Operation success
0xF0: Checksum error
Data: firmware version.
4-4-24. Turn on/off Auto-detection
Data: 0x00: Turn off Auto-detection
0x01: Turn on Auto-detection
For example,
02FE00h // Turn off Auto-detection
02FE01h // Turn on Auto-detection
Response:
Status: 0x00: Operation succeed
http://www.stronglink-rfid.com
Page 16
StrongLink SL032 V3.1
16
5. DIFFERENCES FROM PREVIOUS VERSION
Although we make efforts on the compatibility between the new SL032 V3.1and the
old SL032, there are still some differences you need to know.
1. New SL032 has the auto-detection function which can close automatically when
there is a DESFire or MifarePlus L0/L2/L3 card coming into the detection range.
By the way, we also offer you the Turn On/Off Auto-detection command.
2. New SL032 supports nearly all cards of NXP Mifare series now and we rebuilt the
card type characters.(Details see to Command Select Mifare Card Description)
3. New SL032 also has PIN OUT function indicating tag auto-detection status like
SL025 and SL031 now.
4. New SL032 has the 3des authentication and update key function for ulralight c.
http://www.stronglink-rfid.com
Page 17
Product Information
Product Name:
MIFARE MODULE
Model No.:
SL032_V3.1
RFID:
13.56MHz
Antenna Type:
Integrated Antenna
Product Name:
Host device
Model No.:
T032
Manufacturer:
BEIJING STRONGLINK TECHNOLOGY CO,. LTD.
Host Information
The regulated power supply of the host is as below:
T032 is a host device of SL032_V3.1 for command sets testing.
Its power supply is obtained by 12V AC-DC adapter, and converting 12V to 5V through DC to DC
LM2575 and 5V to 3.3V through LDO AMS1117, to power stable 3.3V to MCU and the SL032_V3.1
module.
Page 18
Federal Communications Commission (FCC) Interference Statement
The limited modular transmitter is only FCC authorized for the specific rule part (FCC Part15.225)
listed on the grant, and that the host product manufacturer is responsible for compliance to any other
FCC rules that apply to the host not covered by the modular transmitter grant of certification.
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.
FCC Caution: Any changes or modifications not expressly approved by the party responsible for
compliance could void the user's authority to operate this equipment.
For additional hosts other than the specific host originally granted with a limited module, a Class II
permissive change is required on the module grant to register the additional host as a specific host
also approved with the module.
OEM/Host integrator is responsible for complying with the instructions and requirements for each
transmitter they choose to integrate into a host product.
RF exposure warning
This equipment complies with FCC radiation exposure limits set forth for an uncontrolled
environment.
This product may not be collocated or operated in conjunction with any other antenna or transmitter.
This equipment must be installed and operated in accordance with provided instructions and the
antenna(s) used for this transmitter must be installed to provide a separation distance from all persons
and must not be collocated or operating in conjunction with any other antenna or transmitter.
Additional text needed for the host product manufacturer to provide to end users in their end-product
manuals.
Page 19
OEM Integration Instructions:
This device is intended only for OEM integrators under the following conditions:
The module can be used to installation in other host. The antenna must be installed such that 20 cm is
maintained between the antenna and users, and the transmitter module may not be co-located with
any other transmit or antenna. The module shall be only used with the integral antenna(s) that has
been originally tested and certified with this module. As long as 3 conditions above are met, further
transmitter test will not be required. However, the OEM integrator is still responsible for testing their
end-product for any additional compliance requirement with this module installed (for example, digital
device emission, PC peripheral requirements, etc.)
IMPORTANT NOTE:
In the event that these conditions cannot be met (for example certain laptop configuration or
co-location with another transmitter), then the FCC authorization for this module in combination with
the host equipment is no longer considered valid and the FCC ID of the module cannot be used on the
final product. In these and circumstance, the OEM integrator will be responsible for re-evaluating. The
end product (including the transmitter) and obtaining a separate FCC authorization. The final end
product must be labeled in a visible area with the following: