Transponder
7.1 Overview
SIMATIC RF600
360
System Manual, 06/2019, J31069-D0171-U001-A22-7618
7
7.1.2
Transponder classes and generations
The transponder classes are distinguished by the different communication protocols used
between the reader and transponder. Transponder classes are usually not mutually
compatible.
The following transponder classes/protocol types are supported by the RF600 system:
Ⴠ
ISO 18000-62
Ⴠ
ISO 18000-63
Transponders supported
RF600 system supports passive transponders with the following minimum characteristics:
Ⴠ
EPC ID (Electronic Product Code IDentifier)
Ⴠ
TID
Ⴠ
A function which permanently ensures that transponders no longer respond.
Ⴠ
After the lock programming can no longer be reprogrammed.
7.1.3
Electronic Product Code (EPC)
The Electronic Product Code (EPC) supports the unique identification of objects (e.g. retail
items, logistical items or transport containers). This makes extremely accurate identification
possible. In practical use, the EPC is stored on a transponder and scanned by the reader.
There are different EPC number schemes with different data lengths. Below is the structure
of a GID-96-bit code (EPC Global Tag Data Standards V1.1 Rev. 1.27) :
Ⴠ
Header: identifies the EPC identification number that follows with regard to length, type,
structure and version of the EPC
Ⴠ
EPC Manager: identifies the company/corporation
Ⴠ
Object class: Corresponds to the article number
Ⴠ
Serial Number: consecutive number of the article
The Siemens UHF transponders are all suitable for working with EPC and other number
schemes. Before a transponder can work with a number scheme, the relevant numbers must
first be written to the transponder.
