Use an External GPIO

Enables the use of an external GPIO controller if an internal GPIO is not present for the given reader. The GPIO controller supported by TagNet is the ADAM 6060 unit which is included in the TagNet SmartBox.

Log Net Change (Global)

A value of *YES indicates that event logging will only occur if the tag has not been seen previously by the same antenna group regardless of any schedule. Net change looks at the Antenna names to group them, for example; if you have 4 antennas in use with ports 1 & 2 representing Zone A and antennas 3 & 4 representing Zone B, then you would name the antennas the same for 1&2 as well as 3&4.

Note that Net Change feature is enabled at lower reader logging level and does not require any specific binding logic at the subscription level to enable it.

Log Net Change (Schedule)

A value of *YES indicates that any event logging will only occur of if the tag has not been seen previously by the same read zone within the same schedule. Net change looks at the Antenna names to group them, for example; if you have 4 antennas in use with ports 1 & 2 representing Zone A and antennas 3 & 4 representing Zone B, then you would name the antennas the same for 1&2 as well as 3&4.

Note that Net Change feature is enabled at lower reader logging level and does not require any specific binding logic at the subscription level to enable it.

Net Change (Exclude Prefix)

Tags such as employee badges with certain prefixes can be excluded from net change so they are constantly recognized.

Tag Filter (Include Prefix)

Here you can include those TagID prefixes that you want to be included in any read events with each prefix delimited by a comma as shown in example. If the TagID prefix is non-conforming it will be ignored at the Reader level, that is not take up any bandwidth nor processed by the server logic. This is an important performance consideration if your facility is seeing tags from other sources.

This feature enables the inclusion of tags that meet your organizations internal prefixes only. With the increasing adoption of UHF RFID, it is not uncommon for many purchased commodities to be RFID tagged on the packaging and thus be picked up by TagNet managed readers. This can cause excessive logging increasing database size over time as well and affecting performance. ** This Feature is supported in the SRC as of v8.4.0

Tag Count Duration (Days)

This feature is used in conjunction with Tag Count Maximum below. If populated the tag reads are not logged once the maximum tag count has been reached. The tag count resets the day after the duration (in days) is reached. An email notification is sent out and a system log is created once the maximum tag count has been exceeded. See full details here.

Tag Count Maximum

This feature is used in conjunction with Tag Count Duration above. If populated the tag reads are not logged once the maximum tag count (e.g. 50) has been reached for the specified duration (e.g. 1 day).

Allowable Timeout

Allows for a specified number of ‘internal’ timeouts before giving up trying to receive data from the physical reader after a command instruction. Note: this is different than a connection timeout whereas a socket connection cannot even be established. See Error recovery attempts under System Settings. Note2: a timeout setting of ‘9999’ means basically the schedule will attempt to receive data indefinitely and is not recommended as shutting down and reconnecting has a better chance of recovery than trying to get data endlessly.

Keep Socket Alive

Pings the reader for the given interval to ensure that the reader has not gone to sleep. Note: this is typically used for ThingMagic readers

Keep GPIO Alive

Pings the SmartBox at the given intervals to ensure that the internal I/O controller has not gone to sleep. Note: the internal ADAM I/O controller within SmartBox has a default timeout value of 10 mins and can be set as high as 65 minutes (3900 seconds) however any inactivity greater than that will require this setting be used.

Release Interval

The time in milliseconds that the reader handler will wait at the end of schedule before starting a new schedule. This can be used to slow down release and reconnect commands to account for network or reader latency.  The default value is 2000 msec. Note: if the reader thread cannot be shut down it then reattempts based on the value of error recovery attempts under System Settings.

Close Connection Delay

The time in milliseconds the reader handler will wait before closing the socket connection at the end of a schedule. Depending on the reader platform, this time can be adjusted to give the reader more time to respond to end of schedule commands before the socket is closed and new schedule begins. This time should always be less than your Release Interval.  

Tag Query Interval

Controls how frequently the input stream of queued tag reads is polled. This values represents both the sleep time between intervals as well as the processing time. If value is set too low then CPU may be overwhelmed attempting to read the queue, if too high it won’t have time to process everything in queue. A good overall default value is 50ms however the value can be less or more based on network performance and reader latency.

Data Read Only

A value of *YES starts a 2nd thread to read tag events in order to improve reader ‘up time’ by separating reader processing from that of binding logic and GPIO processing. So for example if there is a read event and a population of tags is read, the primary thread polls the reader queue and the binding logic happens in the background (and communicates with GPIO). So if there is say a 2 second business logic latency and a further 1 second delay in dwelling a light condition on, it will not hold back the reader from moving to the next read event cycle and thus not missing any tags.

Continuous Read

Used in conjunction with ‘Data Read only’ if enabled. This feature improves reader ‘up-time’ even further by reducing reader start/stop commands which can introduce minute gaps between read cycles. The reader starts at the beginning of schedule and will not end until schedule ends. The read event cycle dictates the interval in which tag reads are grouped together for processing and if no tags are read then there are no gaps in the event cycle sequencing. Not recommended if grouping tags such as employee tag with asset tag(s) as tag events might be split over two read cycles and thus logical association is lost in binding logic. This setting is supported by all LLRP 1.1 managed readers:

Autonomous Mode

When enabled with *YES, provides asynchronous connection to the LLRP reader. This is typically used in a hosted or cloud environment whereas synchronous connection to the reader can be unstable due to the general nature of the Internet. Note: currently in this mode only the last antenna seen per tag is cached, so if multiple antennas see same tag between connections then only the last one be recorded.

Connection Attempt

Used in conjunction with enabling Autonomous mode, specifies how many attempts are made to connect to the reader during the dwell period specified in Reader Schedule script

Connection Attempt Delay

Used in conjunction with enabling Autonomous mode connection attempt, specifies the time to wait in between connection attempts

On Error Restart

A value of *YES will attempt to restart the reader if it can be contacted for whatever reason (internal timeout, network down, etc.). This will only kick in once the number of recovery attempts in System Settings has been exceeded. See reader login credentials below.

User Name

The userid for the Reader to enable TagNet to perform a restart

User Password

The password for the Reader login ID

After Restart Delay

This is a delay before the Event monitor will attempt to reconnect to the reader after auto restart