INfinity 510 Protocol Reference Guide - Sirit

Chapter 4 - Reader Behavior
Operating Mode
NOTE
Data fields displayed in
an event.tag.report
event may include some
or all fields requested by
any of the following
variables:
tag.reporting.report_field,
tag.reporting.arrive_field,
tag.reporting.depart_field,
tag.reporting.taglist_field.
Any software receiving
this event should ignore
those fields not needed
for event handling.
In the ETSI region, there are also four different sub-regions. The first setting
(EN300220) is for operation complying with the EN300220 standard which
uses a transmit frequency of 869.525 MHz. The other three settings
(EN302208_NO_LBT, EN302208, EN302208_DENSE) provide operation
that complies with variations on the EN302208 standard. You must ensure
that the specific sub-region setting is allowed in the local regulatory region.
EN302208_NO_LBT – Utilizes the standard frequency band of 865 to
868MHz with 200 KHz channelization but does not perform the listen
before talk (LBT) function prior to transmitting on a frequency. This
mode can only be used in select countries of the EU.
EN302208 – Utilizes the standard frequency band of 865-868MHz with
200 KHz channelization and provides support for all aspects of the
standard. This mode can only be used in select countries of the EU.
EN302208_DENSE – Utilizes the standard frequency band of 865 to
868 MHz but with 600 KHz channelization and performs the LBT
function prior to transmitting on a frequency. This mode can only be
used in select countries of the EU.
The setup.operating_mode variable controls the operational mode of
the reader. There are four operational modes for the reader: active,
standby, autonomous, and polled.
active – Reader is continuously attempting to singulate tags, stores
singulated tags in the database and automatically reports any
singulated tag via an asynchronous event. The host application can
either register for these events or poll the tag database, or use any
combination of these two methods. The "active" mode supercedes the
previous autonomous and polled modes.
standby –Reader is not transmitting any energy, unless processing a tag
related command. The RF transmitter is enabled at the beginning of the
command processing, any protocol operations required for the
command are performed, and then the RF transmitter is turned back
off. In this mode, a host application could scan the reader’s field of
view for tags by performing the tag.db.scan_tags(1000)
command where the parameter value of 1000 represents the amount
of scan time, in milliseconds.
autonomous – Superceded by active mode. Reader is continuously
attempting to singulate tags and automatically reports any singulated
tag via an asynchronous event notification on the event channel.
polled – Superceded by active mode. Reader is continuously attempting
to singulate tags.
INfinity 510 Protocol Reference Guide 17