User's Manual

i-PORT MB – Manual
Version 1.1 02.02.2007 Page 34/ 37
Application
Inhibit
time
(seconds)
Re-
reporting
time
(seconds)
List
behaviour
Uses get
tags
extended
telegram
Remark
Gate
application
60 0 0 no Tag is reported once if it enters the
reading range and reported again if it
reenters after not having been detected
for longer than the inhibit time value (60
seconds).
Area inventory 300 10 0 optional Tag is reported if it enters the reading
range. If it stays within the reading range
it is reported again if 10 seconds have
expired since the last reporting. A short
re-reporting time is typical for
applications which use the short “Get
Tags” command.
Area inventory
with low
bandwidth to
database
300 290 0 yes Keeping a database with a time resolution
of f.e. 300 seconds needs at least one
message in the interval. So the re-
reporting time is set slightly shorter than
300 seconds (sum of tag ping rate,
message transfer latency, jitter of
message transfer latency and of database
query cycle jitter have to be accounted
for).
Use fields TimeFirst and TimeLast in the
Get Tags extended Command telegram.
Tag control or
test purpose
NA NA 4 no Allows getting each transmission of the
tag to f.e. check for the ping rate.
Typically this will be used in conjunction
with a low sensitivity setting. Note: this
mode causes the highest traffic on the
bus. The parameters inhibit time and re-
reporting time don’t have an effect in this
mode and are left at the default setting
here.
5.6 Exchanging a reader within the daisy chain
− Stop the application program on the host
− exchange the reader
− Restart the application program on the host. If the application on the host checks on startup the
readers serial numbers as recommended, it will detect the changed configuration and require either
manual intervention or automatically configure the reader.