Kathrein RRU 4 series Instruction sheet

Conguration manual Reader Englisch
Conguration manual for
Kathrein RFID UHF-Reader
This document is valid for all Kathrein RFID reader and describes the congurationspharameter that
are necessary to operate the reader.
Although reference is made in the text to RRU4 respect, with the same commands can be controlled
in any other reader.
RRU4
ARU4
M-ARU
ERU
RDR
version 1.01
date of creation: 01.06.2012
document no.: 936B061

Conguration manual Reader 2
Modications, misprints and errors excepted.
English
This manual applies to the following ARU4 types:
Type: Order number:
ARU4-RS4-E6 52010099
ARU4-ETG-E6 52010100
ARU4-ETL-E6 52010101
ARU4-RS4-U6 52010102
ARU4-ETG-U6 52010103
This manual applies to the following M-ARU types:
Type: Order number:
M-ARU-RS232 ETSI 52010135
M-ARU-RS232 FCC 52010136
M-ARU-ETH-E6 52010198
M-ARU-ETH-U6 52010199
RFID-UHF Reader
This manual applies to the following RRU4 types:
Type: Order number:
RRU4-RS4-E6 52010093
RRU4-ETG-E6 52010094
RRU4-ETL-E6 52010095
RRU4-RS4-U6 52010096
RRU4-ETG-U6 52010097
RRU4-ELC-E6 © KRAI 52010180
RRU4-ELC-U6 © KRAI 52010181
This manual applies to the following ERU types:
Type: Order number:
ERU-ETG-E4 52010190
ERU4-ETG-U4 52010191
This manual applies to the following RDR types:
Type: Order number:
RDR-ETH-E4 52010200
RDR-ETH-U4 52010201
Conguration manual Reader

Conguration manual Reader 3
Modications, misprints and errors excepted.
English
Foreword and general information
The reproduction or distribution of this document or extracts from it in whatever form and by whatever means (electronic or mechanical)
for whatever purpose is permitted only with the prior written permission of Kathrein.
Kathrein accepts no liability for omissions or inaccuracies in this document or in relation to the provision or use of the information
contained in this document. Kathrein reserves the right to change the products described in this document and does not accept any
liability in relation to the application or usage of the products described in this manual.
This document and the information contained in it are proprietary information of Kathrein and should be treated as condential.
Kathrein provides this document to its customers in connection with contacts of sale for the products described therein. If the person
in possession of this document, being a legal or natural person, is not a contractual sales partner of Kathrein, or Kathrein has not
intended him by other means as the recipient of the document and the information contained therein, the person in possession is hereby
informed that the use of this document is unlawful and a violation of the rights of Kathrein.
Copyright notice
The information in this manual was correct at the time of editorial deadline.
We reserve the right however to make changes at any time and without prior notice.
This document was prepared for specialist personal who install, congure and place in operation the reader.
Scope
The information contained in this manual is intended for the support of the development process and as development guidance
for the customer. In addition this manual offers supporting information about the standards to be applied at the place of installation
and the relevant safety standards for installation and conguration of the Kathrein reader.
General information
This manual contains information on the installation, conguration, operation and maintenance of the reader. In addition it gives
detailed technical data in order better to familiarise the user with the features of the reader.
In order to ensure a long working life and fault-free operation, this manual should therefore be read carefully and all the instructions
and information contained in it should be complied with.
Warranty
Switching on the AC or DC power supply prior to connecting the LAN cable is considered incorrect installation. Any functional defect
arising as a result is excluded from the warranty/guarantee. Before installing or servicing the reader, the person concerned must
have read the manual and understood its contents. Kathrein accepts no liability if the customer fails to implement the precautions
listed here. In such cases, any claims under the warranty/guarantee are void.
Disposal instruction
Electronic equipment is not classed as household waste and must be disposed of properly in accordance with
Directive 2002/96/EC OF THE EUROPEAN PARLIAMENT AND OF THE COUNCIL of 27 January 2003 on used
electrical and electronic equipment.
At the end of its service life, take this device for disposal at a designated public collection point.
Used batteries are special waste!
Do not put used batteries into your domestic waste; instead take them to a collection point for used batteries!

Conguration manual Reader 4
Modications, misprints and errors excepted.
English
List of Contents
Foreword and general information 3
List of Contents - Reader configuration 4
1. Introduction 5
1.1. Structure of the configuration IDs 5
1.2. The parameter sets 5
2. Description of the configuration parameters of the RRU4 reader system 6
2.1. The “Global” configuration group 6
2.2. The configuration group “RFInterface” 6
2.3. “MultiplexingExposureTime1...8” 9
2.4 The configuration group “Tag communication” (“TagComm”) 11
2.5 The configuration group “ObservedList” 18
2.6 The configuration group “Host communication” (“HostComm”) 19
2.7 The configuration group “ETSI” 21
2.8 The configuration group “communication standard” (“CommStandard”) 22
3. List of references 25
4. contact address 26

Conguration manual Reader 5
Modications, misprints and errors excepted.
English
1. Introduction
The RRU4 Kathrein UHF RFID reader system is characterised by great exibility in addressing RFID applications.
One reason for this is the wide variety of reading devices from the Kathrein product portfolio, which are compatible
with each other and permit optimum conguration to the application. A further reason for the high exibility
is the wide range of parameters for conguring the reader rmware. This conguration manual explains the
various conguration parameters and give instructions on how to make the optimum parameter settings for the
application of your Kathrein RFID reader.
A conguration parameter of the RRU4 reader system consists of a 32-bit long identication number (ID) and a
data part which is 8 to 32 bits depending on the parameter. The data part is referred to below as the “parameter
value” or just the “value”. The ID allows the various parameters to be read or set in the reader system.
Each ID – and hence each conguration parameter – stands for a special functionality within the reader system.
1.1. Structure of the conguration IDs
The ID of a conguration parameter is not selected arbitrary, rather it contains information about the respective
conguration parameter. The ID of a conguration parameter contains the following information:
- the conguration group to which the parameter belongs
- a sequential number to differentiate parameters within a group
- the data type (byte, word, etc.) of the value
- the number of data bytes in the value
- whether the value of the parameter is signed (are negative values possible)
- the unit of the value
For ease of handling the conguration parameters are addressed by their plain text names. The plain text name
begins with “cfgid” followed by the name of the conguration group. This includes the function name of the
parameter. That is the part that clearly states the function/use of the conguration parameter. For example:
Conguration parameter “cfgidTagCommIntelligentWrite”
“cfgid” initial code
“TagComm” Name of the conguration group
“IntelligentWrite” Function name of the parameter
For more details about the structure of the ID or the naming of conguration parameters, see the le “kongids.h” in
the source les for the programming environment of the RRU4 reader system.
For programmers: This le contains macros in the programming language “C”, which offers you the facility in your
programming environment to address the conguration parameters by their plain text names. The plain text name is
then translated into the respective conguration ID at compile time.
1.2. The parameter sets
The conguration of an RFID reader of the RRU4 reader system is organised in parameter sets. Each reader has
eight parameter sets. Apart from one exception (“cfgidGlobalDefaultParamset”) all the conguration parameters
listed below are represented in every parameter set. The use of parameter sets allows an RFID reader to switch
from one conguration to another with only one command. The parameter set selected is then designated
the “active parameter set”. Reading and writing conguration parameters using the protocol commands
“GetParameterById” and “SetParameterById” is always performed on the active parameter set. When the active
parameter set is changed it can be saved into the reader's EEPROM using “SaveActiveParamset”, and thus is
available again when the reader is restarted. Changing over between parameter sets is performed using the
command “SetActiveParamset”.

Conguration manual Reader 6
Modications, misprints and errors excepted.
English
2. Description of the configuration parameters
2. Description of the conguration parameters of the RRU4 reader system
2.1. The “Global” conguration group
2.1.1. “DefaultParamset”
Characteristics:
available from rmware: v1.30.00
Data type: Byte (8-bit)
Unit: –
Value range: 0-7
Description:
This parameter is the only one in its conguration group. In contrast to all the other parameters, this one is
“independent”. That means that this parameter is not held in any parameter set, it just exists on its own. The parameter
indicates which parameter set is loaded and activated when the reader is started up.
2.2. The conguration group “RFInterface”
2.2.1. “RFPower1...8”
Characteristics:
available from rmware: v1.30.00
Data type: Byte (8-bit)
Unit: ¼ dBm(erp)
Value range: 0; 68-136
Description:
This parameter allows the reader transmission power to be set for respective antenna port. More precisely: The
power which the antenna should radiate. The data is given in dBm(erp). So that the power radiated by the antenna
really does correspond to the value of this parameter, the parameters for the attenuation of the antenna cable
and the antenna gain must be set correctly.
It is a precondition that the transmission power is set to a value greater than 0 dBm(erp), in order that an inventory
can be performed using this antenna port.
Note
The transmission power is always set in dBm(erp). If the desired transmission power is stated in dBm(eirp),
this must be converted to dBm(erp): dBm(erp) = dBm(eirp) - 2.14

Conguration manual Reader 7
Modications, misprints and errors excepted.
English
2. Description of the configuration parameters
2.2.2. “TimeToPowerOff”
Characteristics:
available from rmware: v1.30.00
Data type: Word (16-bit)
Unit: Seconds
Value range: 0-65535
Description:
This parameter sets the duration for how long the transmission carrier remains switched on after the completion of
an inventory, or a tag operation in general.
A certain time must elapse after receipt of an inventory command before the reader can start the inventory. This
time is required by the reader amongst other things for LBT (Listen before Talk) and for an antenna test. Using this
parameter it is now possible to reduce this time: If an inventory has been completed by the reader, and the next
inventory command is received within the time congured by this parameter, the reader can dispense with the LBT and
the antenna test and start the inventory more quickly.
Note
The time during which the transmission carrier is switched on by not performing any tag operation represents an
increase in the overall power consumption of the reader.
The LBT (Listen Before Talk) operating mode is permissible only in existing systems.
2.2.3. “ModulationType”
Characteristics:
available from rmware: v1.30.00
Data type: Byte (8-bit)
Unit: -
Value range: 0; 1
Description:
This parameter is used by the reader to specify the modulation type used for tag communication.
There are two modulation types available:
0: Double Side Band (DSB)
1: Phase Reversal Amplitude Shift Keying (PR-ASK)
Note
For readers manufactured for the European Union (ETSI), Phase Reversal Amplitude Shift Keying is used
irrespective of the setting of this parameter.

Conguration manual Reader 8
Modications, misprints and errors excepted.
English
2. Description of the configuration parameters
2.2.4. “MultiplexingAntennaport1...8”
Characteristics:
available from rmware: v1.30.00
Data type: Byte (8-bit)
Unit: -
Value range: 0; 1-8
Description:
These eight parameters form the antenna multiplex list of the reader. Either an antenna port number (1 to 8) or a
zero can be entered in each of the eight list slots. If a zero is entered, the list slot is deactivated and the reader
skips to the next list slot. This is shown in the following diagram:
Inventory start
Index multiplex list := 0
Index multiplex list +1
no
yes
yes
no
Does the multiplex list
contain an entry and is
there a power congured
for this antenna port?
Perform inventory at a
specied antenna port
Has the end of the
multiplex list been
reached?
Inventory end

Conguration manual Reader 9
Modications, misprints and errors excepted.
English
2. Description of the configuration parameters
2.3. “MultiplexingExposureTime1...8”
Characteristics:
available from rmware: v1.30.00
Data type: Word (16-bit)
Unit: milliseconds
Value range: 0-65535
Description:
The values of these conguration parameters are of interest only to reader commands that start with “ASync...”.
Each parameter stands for an exposure time which species how long the reader maintains exposure for inventories
the respective position – and hence antenna – in the multiplex list. In contrast to synchronous commands, when
using asynchronous commands the reader does not proceed to the next entry in the multiplex list immediately
after performing an inventory; instead it rst waits until the exposure time given by these parameters for the
respective multiplex entry has expired. An inventory in progress is not interrupted at the expiry of the exposure time,
but is continued to completion.
2.3.1. “CableLoss1...8”
Characteristics:
available from rmware: v1.30.00
Data type: Byte (8-bit)
Unit: ¼ dB
Value range: 0-255
Description:
These parameters contain the cable attenuation of the antenna cable between the reader and the antenna for the
respective antenna port of the reader. The reader can set the transmission power correctly only if the attenuation
values for the antenna cable have been entered correctly.
2.3.2. “AntennaGain1...8”
Characteristics:
available from rmware: v1.30.00
Data type: Byte (8-bit); signed
Unit: ¼ dBic
Value range: -128 – 127
Description:
These parameters allows the antennas gain for the antennas connected to the reader to be communicated to the
reader. The reader calculates from the transmission power setting (antenna radiated power), the antenna gain
and the cable attenuation the port power at the RF output:
Use the following formula to convert an antenna gain expressed in dBi to dBic units:
Antenna gaindBic = antenna gaindBi + 3
Port powerdBm = radiated powerdBm(erp) – antenna gaindBic + cable attenuationdB + 5.14

Conguration manual Reader 10
Modications, misprints and errors excepted.
English
2. Description of the configuration parameters
Important!
Close eld antennas have a negative gain, since they are designed not for electromagnetic coupling with the
tag but for magnetic coupling. To congure close eld antennas correctly, enter the antenna gain as 5.25 dBic
(a parameter value of 21 dec) and the antenna radiated power (“RFPower1...8”) as the maximum input power stated
in the antenna data sheet.
2.3.3. “RSSIThreshold1...8”
Characteristics:
available from rmware: v1.30.00
Data type: Byte (8-bit)
Unit: -
Value range: 0; 255
Description:
When the reader is performing an inventory, at the same time the eld strength of the response from the tag that is
addressed is measured. This is called the RSSI value. These parameters allow the threshold value for the RSSI value
to be set for each antenna port. Tags with an RSSI value less than the threshold setting are then no longer detected
by the reader.
2.3.4. “MultiPowerTagAccess1...8”
Characteristics:
available from rmware: v1.30.00
Data type: Bool (8-bit)
Unit: -
Value range: 0; 255
Description:
The stronger the reader transmission signal that strikes the tag, the more difcult it is for the tag to modulate the
reader transmission signal by means of backscatter. The strength of the tag response thus decreases as the reader
transmission power increases. Because of this behaviour in certain circumstances it may occur that the reader can
no longer read a tag which is immediately in front of the antenna, but at a lower transmission power it can easily
detect it. If “MultiPowerTagAccess” is activated for an antenna port, after an inventory with high transmission power,
the reader reduces the transmission power by a half and searches for “overlooked” tags.
2.3.5. “MaxAllowedAntennaOutputPower1...8”
Characteristics:
available from rmware: v1.30.00
Data type: Byte (8-bit)
Unit: ¼ dBm(erp)
Value range: 0-255
Description:
This parameter allows the radiated power of the antenna at an antenna port to be limited to a specied value.

Conguration manual Reader 11
Modications, misprints and errors excepted.
English
2. Description of the configuration parameters
2.3.6. “EnableRSSIThresholdAtSpecicCmds”
Characteristics:
available from rmware: v1.46.00
Data type: Bool (8-bit)
Unit: –
Value range: 0; 255
Description:
The RSSI threshold value set by the “RSSIThreshold1...8” parameter applies equally to non-specic (“...GetEPCs”,
“...Any”) and specic (“...Specic”) tag reader commands. The effect on specic tag reader commands can however
be switched on and off by these conguration parameters. The following scenario can be set: “SyncGetEPCs”
commands the reader to scan cyclically for tags in the antenna eld. The conguration parameter “RSSIThreshold1...8”
means that tags with less than a specied RSSI value are not reported. One tag is now close to the RSSI
threshold and when the threshold is reached is reported by the reader to the higher level. This triggers a specic
command for the reported tag. If “EnableRSSIThresholdAtSpecicCmds” is activated it can now happen that the
specic command comes to nothing, since the RSSI value of the tag is uctuating around the threshold value.
In such a scenario, “EnableRSSIThresholdAtSpecicCmds” should be deactivated.
2.3.7. “FlashWriteAdditionalPower”
Characteristics:
available from rmware: v2.00.00
Data type: Byte (8-bit)
Unit: ¼ dB
Value range: 0-48
Description:
It takes more energy to write to a tag than to read a tag. Therefore for a given transmission power the tag must
be nearer the antenna for writing than for reading. In order to overcome this distance differential, this parameter
can be used to specify whether and by how much the reader transmission power needs to be increased
for write commands compared to read commands.
2.4. The conguration group “Tag communication” (“TagComm”)
2.4.1. “UsePilottone”
Characteristics:
available from rmware: v1.30.00
Data type: Bool (8-bit)
Unit: –
Value range: 0; 255
Description:
This parameter allows the pilot tone tag to be switched on and off. Tags to EPCGlobal Class 1 Gen 2 are able to
carry a pilot tone ahead of the user data. The purpose of the pilot tone is the synchronisation of the reader to the
response of the tag. Without a pilot tone it is more difcult for the reader to synchronise itself to the tag response.
In order to ensure reliable tag detection, this parameter should always be activated.

Conguration manual Reader 12
Modications, misprints and errors excepted.
English
2. Description of the configuration parameters
2.4.2. “InitialQ”
2.4.3. “Session”
Characteristics:
available from rmware: v1.30.00
Data type: Byte (8-bit)
Unit: –
Value range: 0-3
Description:
Tags to EPCGlobal Class 1 Gen 2 support four different “sessions”. At each session a tag can be given an inventoried
ag to indicate whether or not it has already been detected by the reader during an inventory process. Inventoried
ags have different properties for the individual sessions, which allows recognition of their persistence times.
The time thus indicates how long a tag indicates that it has been detected or not by the reader.
Tag has energy Tag has no energy
Session 0 unlimited persistence no persistence
Session 1 persistence greater than 500 milliseconds
but less than 5 seconds
persistence greater than 500 milliseconds but less than
5 seconds
Session 2 unlimited persistence persistence greater than 2 seconds
Session 3 unlimited persistence persistence greater than 2 seconds
This conguration parameter instructs the reader the session with which it should work.
Characteristics:
available from rmware: v1.30.00
Data type: Byte (8-bit)
Unit: –
Value range: 0-15
Description:
The value Q in the inventory process species how many tags there are in the reader antenna eld and which must
be detected. The number x on tag is calculated by the following formula:
The value Q is communicated to the tags by the reader, whereupon each of these selects from x a random
“Communications slot” for its response. In order to perform an inventory as quickly and efciently as possible, as
many of the x communications slots should be occupied by tags, but without there being any multiple occupation
of communications slots (which would lead to collisions). If the reader detects that the value chosen for Q is
too large (hardly any communications slots are occupied) or too small (collisions occur), it will be adjusted
automatically and loaded to the tags. Since this adjustment takes time, the reader with this conguration parameter
should be informed of the approximate number of tags to expect in the antenna eld. This allows the number
of communications slots to be set to an appropriate value right from the start of the inventory process.
-1

Conguration manual Reader 13
Modications, misprints and errors excepted.
English
2. Description of the configuration parameters
2.4.4. “MaxErrors”
Characteristics:
available from rmware: v1.30.00
Data type: Byte (8-bit)
Unit: –
Value range: 0-255
Description:
The “MaxErrors” conguration parameter indicates how often a command is issued by the reader to the tag when
the response expected by the reader from the tag remains outstanding.
2.4.5. “CommunicationProle”
Characteristics:
available from rmware: v1.30.00
Data type: Byte (8-bit)
Unit: –
Value range: 0-255
Note: Up to rmware v2.04.00 this parameter was called “DefaultProle”.
The conguration ID was not changed.
Description:
This conguration parameter sets the “communication prole” between the reader and tag. A communication prole
consists of:
- the data transmission rate (reader to tag communication)
- the data reception rate ( tag to reader communication)
- the coding of the data from tag to reader
There are various data transmission rates, data reception rates and codings available. Since not every combination
of these three properties is viable, selected combinations are available as communication proles. A list of the
viable communication proles can be downloaded from the reader by the command “GetProleList”. It is dependent
on the selected communication prole whether “Dense Reader Mode” is in operation in the reader or not.
2.4.6. “CommStandard”
Characteristics:
available from rmware: v1.30.00
Data type: Byte (8-bit)
Unit: –
Value range: 0-255
Description:
Different countries have different regulations regarding the permissible transmission power and transmission
channels that can be used for communication with RFID tags. This conguration parameter informs the reader
which regulations to comply with for radio communication with RFID tags.
For more details on the country proles that are supported, see the le “rrui4api.h” in the source les for the
programming environment of the RRU4 reader system.

Conguration manual Reader 14
Modications, misprints and errors excepted.
English
2. Description of the configuration parameters
2.4.7. “IntelligentWrite”
Characteristics:
available from rmware: v1.30.00
Data type: Bool (8-bit)
Unit: –
Value range: 0; 255
Description:
Depending on the type of tag, it requires 10 to 20 milliseconds time to write 16 bits of data (one word). If for instance
a 96-bit EPC should be written, then the time which a tag requires for saving the data is 120 milliseconds in the
worst case. Only a fth to a tenth of this time would be required for reading the data from a tag. In practice it often
happens that the data written to a tag were already present on it. Despite this, the tag requires the full stated time
to complete the write command. This conguration parameter should be activated in order to accelerate the write
event and to avoid writing data when they are already present on the tag. To achieve this, before writing to the tag
the reader rst reads the relevant data area on the tag. It then writes only those parts which it is necessary to change.
Note: If a memory area on a tag is protected by a “Lock” against overwriting, and if identical content is scheduled
to be written to the tag with “IntelligentWrite” activated, no error message is generated by the reader. No write
command is issued to the tag in the process of reading the existing data, comparing it with the data to be written
and establishing by the reader that no changed data need be written to the tag. With no write command issued,
the reader is not in the position to detect the “Lock” on the memory area.
2.4.8. “VerifyWrite”
Characteristics:
available from rmware: v1.30.00
Data type: Bool (8-bit)
Unit: –
Value range: 0; 255
Description:
After a write operation, a tag sends the result to the reader. This result can be either an error code or a success
message. The memory cells of a tag cannot be written innitely many times, since they are subject to ageing.
Depending on the tag, it has a working life of 1,000 to 1,000,000 write cycles. At the end of a tag's working life it
can occur that following a write operation a tag sends out a success message to the reader, but has not stored
the data correctly in the tag memory. If “VerifyWrite” is activated, the reader issues a read command after receiving
the success message. This reads the data in the tag memory and reports any mismatches to the higher level
as “Verify Fail”.
Important!
Even with “VerifyWrite” activated, there is no guarantee that the data are stored correctly in the tag memory.
Aged tags may “forget” the content of their memory, be it minutes or hours after the write operation!

Conguration manual Reader 15
Modications, misprints and errors excepted.
English
2. Description of the configuration parameters
2.4.9. “QueryTarget”
Characteristics:
available from rmware: v1.30.00
Data type: Bool (8-bit)
Unit: –
Value range: 0; 255
Description:
Tags to EPCGlobal Class 1 Gen 2 support four different “sessions”. At each session a tag can be given an inventoried
ag to indicate whether or not it has already been detected by the reader during an inventory process. The status of
the inventoried ag can be either “A” or “B”. When the tag is detected in the inventory, the status of the ags switches
either from A to B or from B to A. The status of the ag can also be inuenced by “Select commands”.
The conguration parameter “QueryTarget” determines which tags should participate in the inventory. If the
conguration parameter has the value zero, the tags participate in the inventory for which the inventoried ag is
set to A.
Otherwise only the tags for which the inventoried ag is set to B. In conjunction with the “Select lters”, lter tasks
can be performed in this way.
Note
See also the “EPCglobal Class 1 Generation 2 UHF RFID” ((E)) specication V1.2.0 section 6.3.2.2 (page 43f).
2.4.10. “QuerySel”
Characteristics:
available from rmware: v1.30.00
Data type: Byte (8-bit)
Unit: –
Value range: 0-3
Description:
This conguration parameter species the content of the eld “Sel” in the Gen2 command “Query”. This eld instructs
the tag whether the content of the “Selected ag” is or is not relevant for participation in the inventory. In conjunction
with the “Select lters”, lter tasks can be performed in this way.
Note
See also the “EPCglobal Class 1 Generation 2 UHF RFID” ((E)) specication V1.2.0 section 6.3.2.11.2.1 (page 57).

Conguration manual Reader 16
Modications, misprints and errors excepted.
English
2. Description of the configuration parameters
2.4.11. “ForcePowerOffAfterEPCWrite”
Characteristics:
available from rmware: v1.40.00
Data type: Byte (8-bit)
Unit: milliseconds
Value range: 0-255
Description:
During the inventory process a tag transmits its EPC and a checksum to the reader. This checksum is formed when
the tag is “Powered up” from the memory area of the EPC. If now a write command changes the EPC and a new
inventory is started without any intervening “Power up” – i.e. without switching off the antenna eld, the tag cannot
participate in the inventory, because the checksum it communicates no longer matches the EPC it transmits.
This conguration parameter species whether and for how long after a write operation to the memory bank of the EPC
the carrier should be switched off so as to “repower” the tag.
Note
See also the “EPCglobal Class 1 Generation 2 UHF RFID” ((E)) specication V1.2.0 section 6.3.2.1.2.1 (page 38).
2.4.12. “TransmitGetEPCsPreSelect”
Characteristics:
available from rmware: v1.41.00
Data type: Bool (8-bit)
Unit: –
Value range: 0; 255
Description:
The content of this conguration parameter affects only the protocol commands “SyncGetEPCs”,
“SyncBulkGetEPCs”, “ASyncGetRawEPCs” and “ASyncGetEPCs”. All other protocol commands behave as if
“TransmitGetEPCsPreSelect” is zero. Depending on the value of this conguration parameter, an inventory runs
as follows:
• “TransmitGetEPCsPreSelect” is zero:
1. the rst antenna is selected from the multiplex list
2. a Select to reset all tags within the reception range of the selected antenna is executed
3. an inventory is executed by the selected antenna, until no further tags are found
4. as long as there remain further antennas in the multiplex list, the next antenna is selected and the process
resumes at point 2
5. the protocol command is completed and the result is transferred to the higher level
• “TransmitGetEPCsPreSelect” is not equal to zero:
1. the rst antenna is selected from the multiplex list
2. a Select to reset all tags within the reception range of the selected antenna is executed
3. as long as there remain further antennas in the multiplex list, the next antenna is selected and the process
resumes at point 2
4. the rst antenna is selected from the multiplex list
5. an inventory is executed by the selected antenna, until no further tags are found
6. as long as there remain further antennas in the multiplex list, the next antenna is selected and the process
resumes at point 5
7. the protocol command is completed and the result is transferred to the higher level

Conguration manual Reader 17
Modications, misprints and errors excepted.
English
2. Description of the configuration parameters
If several antennas look at a population of tags and it is immaterial which antenna detects any tag, the time for a
complete detection of the tag population can be reduced by activation of this conguration parameter: Tags which
had already been detected by one antenna are no longer detected by the following antennas in the multiplex list.
2.4.13. “TransmitSelectIfNoFilterIsOn”
Characteristics:
available from rmware: v1.45.00
Data type: Bool (8-bit)
Unit: –
Value range: 0; 255
Description:
At the start of an inventory the reader sets all tags that are within antenna range to a dened initial status, using
a dened “select lter” or a “select” command. The subsequent inventory then detects all tags that are in this
dened initial status. If no select lters were dened, this conguration parameter can be used to specify whether
or not before the inventory a select command should be sent to perform a global reset of all tags within the
antenna range.
2.4.14. “NumberOfEPCWords”
Characteristics:
available from rmware: v2.00.00
Data type: Byte (8-bit)
Unit: –
Value range: 0-31; 255
Description:
From rmware version v2.00.00, RRU4 RFID readers of the Kathrein reader system can read tags with an EPC length
of 0 to 31 words (0 to 496-bit EPCs). This parameter allows deactivation of the automatic detection of the EPC length,
thus forcing the reader to work with a xed length.
2.4.15. “UseBlockWrite”
Characteristics:
available from rmware: v2.00.00
Data type: Bool (8-bit)
Unit: –
Value range: 0; 255
Description:
If this conguration parameter is activated, the reader uses the command “BlockWrite” for writing data to a tag.
This means that more than 16 bits (one word) can be written to a tag with just a single command and thus save
“write time”.
Note
Not all tags support the command “BlockWrite”. See also the “EPCglobal Class 1 Generation 2 UHF RFID”
((E)) specication V1.2.0 section 6.3.2.11.3.7 (page 74).

Conguration manual Reader 18
Modications, misprints and errors excepted.
English
2. Description of the configuration parameters
2.4.16. “DisableReceivingNXPReadProtectedTags”
Characteristics:
available from rmware: v2.01.00
Data type: Bool (8-bit)
Unit: –
Value range: 0; 255
Description:
If a tag from the company NXP was protected by “ReadProtect”, at inventory it would no longer communicate
its EPC or a valid checksum. The data content of the EPC and the checksum is zero. To allow such tags to be
detected, the reader allows tags for which the EPC and checksum are zero to pass. Since such tags are no
longer secured with a valid checksum, it can happen very occasionally that the reader detects such a tag where
none exists. In order to prevent this, the reception of “ReadProtected” tags can be suppressed by activation of this
conguration parameter.
2.5. The conguration group “ObservedList”
2.5.1. “GlimpsedTimeoutCnt”
Characteristics:
available from rmware: v1.30.00
Data type: Byte (8-bit)
Unit: –
Value range: 0-255
Description:
This conguration parameter applies only to asynchronous protocol commands (“ASync...”). For the duration
of an asynchronous command, the reader compiles a list of all the tags found within the antenna range. If a tag
is present in the antenna range for multiple inventories, a “coming” message is generated for that tag and the
message is sent to the higher level. If a tag is no longer detected during multiple inventories, a “going” message is
generated and sent.
Once the “going” message has been generated for a tag, this conguration parameter species the number of
inventories where the tag is not detected, which then triggers deletion of this tag from the internal administration list.
This parameter should not be changed. It has no inuence over the generation of a “coming” or “going” message.
Kathrein reserves the right to remove this parameter from rmware versions at a future point in time.
2.5.2. “ObservedThresholdCnt”
Characteristics:
available from rmware: v1.30.00
Data type: Byte (8-bit)
Unit: –
Value range: 0-255
Description:
This conguration parameter applies only to asynchronous protocol commands (“ASync...”). For the duration
of an asynchronous command, the reader compiles a list of all the tags found within the antenna range. If a tag
is present in the antenna range for multiple inventories, a “coming” message is generated for that tag and the
message is sent to the higher level. If a tag is no longer detected during multiple inventories, a “going” message is
generated and sent.
This conguration parameter species the number of inventories where the tag is detected, which then triggers the
generation of a “coming” message which is sent to the higher level.

Conguration manual Reader 19
Modications, misprints and errors excepted.
English
2. Description of the configuration parameters
2.5.3. “ObservedTimeoutCnt”
Characteristics:
available from rmware: v1.30.00
Data type: Byte (8-bit)
Unit: –
Value range: 0-255
Description:
This conguration parameter applies only to asynchronous protocol commands (“ASync...”). For the duration
of an asynchronous command, the reader compiles a list of all the tags found within the antenna range. If a tag
is present in the antenna range for multiple inventories, a “coming” message is generated for that tag and the
message is sent to the higher level. If a tag is no longer detected during multiple inventories, a “going” message is
generated and sent.
This conguration parameter species the number of inventories where the tag is no longer detected, which then
triggers the generation of a “going” message which is sent to the higher level.
2.6. The conguration group “Host communication” (“HostComm”)
2.6.1. “ExtendedResultFlag”
Characteristics:
available from rmware: v1.30.00
Data type: Byte (8-bit)
Unit: –
Value range: 0-15
Description:
This conguration parameter allows specication of which additional information on a tag should be sent when tag
data are sent to the higher level. Every bit of the lower four bits that is set to “1” in this conguration parameter
causes the sending of certain additional information:
Bit 0: Sending the antenna information (the antenna which detected the tag)
Bit 1: Sending the RSSI value (eld strength information of the tag response)
Bit 2: Sending the time stamp (the time when the tag was detected)
Bit 3: Sending the protocol control word of the tag (PC, [XPC_W1, [XPC_W2]]; see also the “EPCglobal Class 1
Generation 2 UHF RFID” specication V1.2.0 section 6.3.2.1.2 (page 38).)
2.6.2. “AntennaIndependentOperation”
Characteristics:
available from rmware: v1.30.00
Data type: Bool (8-bit)
Unit: –
Value range: 0; 255
Description:
This conguration parameter allows differentiation between “antenna-dependent” (conguration parameter
deactivated) and “antenna-independent” (conguration parameter activated) operation of the reader.
This conguration parameter is relevant to all asynchronous protocol commands (“ASync...”) and to the
command “SyncBulkGetEPCs”. In the case of the specied protocol commands the reader compares a tag
which it has detected during an inventory with the tags listed on an internal list.

Conguration manual Reader 20
Modications, misprints and errors excepted.
English
2. Description of the configuration parameters
During antenna-dependent operation the antenna information is used in this process, as well as the EPC.
That means that a tag which was detected by multiple antennas also generates multiple records in the reader.
Each record then contains the same EPC but a different antenna port number. During antenna-independent
operation the antenna information is irrelevant. A tag which was detected by multiple antennas generates only a
single record in the reader.
2.6.3. “ASyncAdditionalRSSIDataDeliveryDelta”
Characteristics:
available from rmware: v2.00.00
Data type: Byte (8-bit)
Unit: –
Value range: 0-255
Description:
This conguration parameter inuences the behaviour of all asynchronous protocol commands (“ASync...”) except
for “ASyncGetRawEPCs”.
During asynchronous commands, when a tag comes within range of an antenna, a “coming” message is generated
and sent to the higher level. When the tag leaves the antenna eld, a “going” message is generated. In various
application scenarios it is of interest to view how the eld strength (RSSI value) of a tag behaves in the time
between the “coming” message and the “going” message. This allows amongst other things conclusions to be drawn
regarding the movement of a tag within the antenna eld.
This conguration parameter species how much the change in strength of the RSSI value of a tag must
be in order to generate a “TagDataChanged” message which is then sent to the higher level. At a value of 255,
no “TagDataChanged” messages are generated.
Note
In order that the RSSI value is also included in the “TagDataChanged” message, the conguration parameter
“ExtendedResultFlag” should also be set.
2.6.4. “UseMillisecondsAsTimestamp”
Characteristics:
available from rmware: v2.00.00
Data type: Bool (8-bit)
Unit: –
Value range: 0; 255
Description:
After an inventory, a time stamp with the time of detection of the tag can also be sent to the higher level as part
of the tag information (see “ExtendedResultFlag”). This conguration parameter species whether the time
stamp should be the UTC time in seconds since the 01.01.1970 0:00, or the milliseconds elapsed since the
the reader was started. If this conguration parameter is activated, the milliseconds since the start of the reader
will be sent as the time stamp.