Stop Trigger Type (ROSpec)

This is set by TagNet based on reader manufacturer behavior and should not be modified. A value of *NULL basically instructs reader to read forever, a value of *DURATION indicates how long with using directive below

Duration Trigger (ROSpec)

This is set by TagNet based on reader manufacturer behavior and should not be modified.

Stop Trigger (AISpec)

This is set by TagNet based on reader manufacturer behavior and should not be modified. A value of *NULL basically instructs reader to read forever, a value of *DURATION indicates how long with using directive below

Duration Trigger(AISpec)

This is set by TagNet based on reader manufacturer behavior and should not be modified.

Log Antenna RSSI

Logs the tag RSSI in base logging (PHLOG) based on the following options:

*YES - RSSI is enabled (basic logging only)

*NO – RSSI not enabled (same as blank)

*ZONE – select this for RSSI zone based configuration

*FILTER - select this for simple RSSI cut-off logic

Antenna RSSI Option

Used in conjunction with Log Antenna option above:

*MINIMUM – select tag with weakest RSSI value

*MAXIMUM – select tag with strongest RSSI value

*AVERAGE – select this for RSSI zone based configuration

*COUNT – select tag with highest number of read counts

Antenna RSSI Filter

Specifies what RSSI threshold should not be logged. Used in conjunction with *FILTER and *ZONE.

The value entered will be the RSSI cutoff so as an example if the value = (-70) then only tags read that are stronger than -70 will be considered

Tag Translation

This feature translates the EPC based on the selection value described below:

*TEXT – This performs a full conversion from HEX to ASCII. Works with 96, 128, & 256 Bit EPC's

*PLOT_BID – This performs a selective conversion from HEX to ASCII based on customers unique EPC encoding for 128 bit EPC's. Converts beginning '50303030’ (= ‘P000’ in ASCII) and the remaining is unconverted decimal

*MIXED – This combines both *PLOT_BID and *TEXT together (Inventory Bids and Plot Bids)

Hold Events and Reports

Used when SRC is deployed, only one LLRP report is generated at the end of the read event cycle

Full Event Cycle

When executing a full inventory (RFDFULL), anytime the read event cycle is not completed the tags read are not evaluated for IMOVE. Why? if the RFID cabinet door has been opened prematurely before the read cycle ends, this compromises the integrity of the read cycle and it is aborted. The next read event cycle will adjust for any tag movements.

Antenna Event Notification

Logs an error if an enabled antenna (in the TagNet profile) is no longer recognized during a read event schedule for any LLRP enabled reader. This is is to account for antennas that may get disconnected or damaged during operation. Note: for some readers this event notification may not send out until the read schedule ends.

Delete the Access Spec

This was an early feature used to reduce the connection timeouts during schedule restarts for Zebra FX7500/9500/9600 readers. Keep this as *NO and use the 'Close Synchronously' feature below.

Close Synchronously

This feature will reduce the connection timeouts during schedule restarts for Zebra FX7500/9500/9600 readers. It waits for for a response from the reader after each LLRP directive to ensure it is listening correctly.

JSM Server IP Address

Specifying an IP address and port will redirect this reader to be supported by another Java Service Manager (JSM) instance other than the default instance. Note: this feature is typically only used when supporting a larger (more than 50) readers and the reader management needs to be broken up for performance considerations.

X & Y Coordinates

Indicates the x & y value of where the actual physical reader is (** future use **).

Last Activity

This is a heartbeat timestamp that is updated by the SRC to send periodic updates to the server during normal operation. It is either the last tag read event cycle update to server, or if there has been no tag read event activity it will be the [Last Activity Interval] value specified in the Smart Reader Client attribute group.

To summarize, the Last Activity Value is updated based on the following logic:

1 -  the last tag read event cycle posted to server

2 - if no tag is read within the interval period, then it will report the time based on the interval period.

3-  When the reader is waiting on a trigger to start a read event cycle, the Keep Socket Alive setting dictates the interval for the periodic updates.