RF-MANAGER RF310M software
9.3 Application mode "Mobile"
SIMATIC RF310M Mobile Reader
78
Operating Instructions, 10/2013, J31069-D0191-U001-A6-7618
Only complete rows with 4 bytes each are write-protected.
If, for example, you only select the 2nd byte in the data editor using the "Address" FF05 and
"Length" 1, only this byte is transferred to the EEPROM area on the tag, but the address
range FF04…FF07 is protected.
A write operation is carried out internally at block address FF84.
The OTP area refers to the 5 block addresses FF80, FF84, FF88, FF8C and FF90. A write
command to this block address with a valid length (4, 8, 12, 16, 20 depending on the block
address) protects the written data from subsequent overwriting.
Note
If the OTP area is used, it must be ensured that the blocks are used without gaps, starting
with block 0.
Examples:
3 blocks (with write command), blocks 0, 1, 2 (FF80, length = 12): valid
2 blocks (consecutive), block 0 (FF80, length =4), block 1 (FF84, length = 4): valid
2 blocks (consecutive), block 0 (FF80, length =4), block 2 (FF88, length = 4): invalid
1 block, block 4 (FF90, length = 4): invalid
9.3.5.5
Reading the tag configuration data
You can read the configuration data of a tag by selecting the memory area "CONFIG" in the
editor and subsequently carrying out a read operation. The memory area "CONFIG" only
exists with RF300 tags.
Byte address
EEPROM
Functional description
0xFF1f
Bank switch (bits 1 and 0)
Memory bank
0xFF1e
MDS delay (bits 7:5); LFD (bit 4)
MDS delay/LFD bit
0xFF1d
Reserved
0xFF1c
Limit value A for LFD quotients
LFD (A)
0xFF1b
Limit value B for LFD quotients
LFD (B)
0xFF1a
Reserved
0xFF19
Memory configuration, INIT (bits
7...1)
Memory configuration/Init bit
0xFF18
Range for lock bits
Lock bits
0xFF17
Tag ID, byte 3
Tag ID (b24-b31)
0xFF16
Tag ID, byte 2
Tag ID (b16-b23)
0xFF15
Tag ID, byte 1
Tag ID (b8-b15)
0xFF14
Tag ID, byte 0
Tag ID (b0-b7)
