System Manual
Table Of Contents
- SIMATIC RF200
- Legal information
- Table of contents
- 1 Introduction
- 2 Safety notes
- 3 System overview
- 4 Planning the RF200 system
- 4.1 Fundamentals of application planning
- 4.1.1 Selection criteria for SIMATIC RF200 components
- 4.1.2 Transmission window and read/write distance
- 4.1.3 Width of the transmission window
- 4.1.4 Impact of secondary fields
- 4.1.5 Permissible directions of motion of the transponder
- 4.1.6 Operation in static and dynamic mode
- 4.1.7 Dwell time of the transponder
- 4.1.8 Communication between communication module, reader and transponder
- 4.2 Field data of transponders and readers
- 4.3 Installation guidelines
- 4.4 Chemical resistance of the reader and transponders
- 4.5 Further information
- 4.1 Fundamentals of application planning
- 5 Readers
- 5.1 SIMATIC RF210R
- 5.2 SIMATIC RF210M
- 5.3 SIMATIC RF220R
- 5.4 SIMATIC RF240R
- 5.5 SIMATIC RF250R
- 5.6 SIMATIC RF260R
- 5.7 SIMATIC RF280R
- 5.8 SIMATIC RF285R
- 5.9 SIMATIC RF290R
- 6 Antennas
- 7 Transponder
- 7.1 Memory configuration of ISO the transponders
- 7.2 MDS D100
- 7.3 MDS D117
- 7.4 MDS D124
- 7.5 MDS D126
- 7.6 MDS D127
- 7.7 MDS D139
- 7.8 MDS D160
- 7.9 MDS D165
- 7.10 MDS D200
- 7.11 MDS D261
- 7.12 MDS D324
- 7.13 MDS D339
- 7.14 MDS D400
- 7.15 MDS D421
- 7.16 MDS D422
- 7.17 MDS D423
- 7.18 MDS D424
- 7.19 MDS D425
- 7.20 MDS D426
- 7.21 MDS D428
- 7.22 MDS D460
- 7.23 MDS D521
- 7.24 MDS D522
- 7.25 MDS D522 special variant
- 7.26 MDS D524
- 7.27 MDS D525
- 7.28 MDS D526
- 7.29 MDS D528
- 7.30 MDS D560
- 8 System integration
- 9 System diagnostics
- A Appendix
System diagnostics
9.2 Diagnostics functions - STEP 7
SIMATIC RF200
System Manual, 03/2019, J31069-D0227-U001-A11-7619
413
9.2.2 Transponder diagnostics with "Tag Status" (MDS Status)
The command can be used to scan the status data of the transponder that is located within
the antenna field.
Table 9- 3 Attribute "0x83" (mode 03), corresponds to UDT 230
Name
Type
Possible Values
(hex)
Comment
UID array[1…8] byte
0x000000000
0000000 ...
0xFFFFFFFF
FFFFFFFF
Unique identifier
=8 byte UID, MSB first
MDS_type byte
--
Transponder type (chip vendor, designation):
0x01
= ISO 15693 general
0x03
= ISO 15693 (Infineon, MDS D3xx)
0x04 = ISO 15693 (Fujitsu - 2 KB, MDS D4xx);
ISO 15693 (Fujitsu - 8 KB, MDS D5xx)
1)
0x05
= ISO 15693 (NXP, MDS D1xx)
0x06
= ISO 15693 (TI, MDS D2xx)
0x07
= ISO 15693 (STM, MDS D261)
IC_version
byte
0x00 ... 0xFF
Chip version
size word 0x00 ... 0xFF Memory size in bytes
Depending on transponder type, e.g. MDS D3xx: 992 bytes
lock_state
byte
0x00 ... 0xFF
–not used with RF200
block_size byte 0x00 ... 0xFF Block size of the transponder
for each transponder type, e.g. MDS D3xx: 4 bytes
nr_of_blocks byte 0x00 ... 0xFF Number of blocks
Depending on transponder type, e.g. MDS D3xx: 248 bytes
1)
Except for RF280R; possible value "0x08"