Navigation: Reader Management > Physical Readers > Physical Reader Profile (Change) >

Advanced Settings

Still need help? Create a Support Ticket with Stratum Support

Send comments on this topic.

← Previous Next →

 

Advanced Settings for a Physical Reader Profile

This attribute group enables changing/updating values specific to advanced settings as described below.

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). Note: this unconditionally logs each tag RSSI value per read point (antenna) and should only be used for testing and not with production Bindings as there can be unpredictable results when same tag is processed more that once.

*NO – RSSI not enabled (same as blank)

*ZONE – select this for RSSI zone based configuration

*FILTER - select this for a hard RSSI cut-off logic. Ensure your RSSI value it set correctly or you can risk toss out tags you really want. Refer to  Calibration Section for further guidance.

 

Note: using RSS Filtering (*FILTER) in combination with Net Change (NC) can be counter-productive in certain use cases. For example: if you have a -65 ceiling with net change enabled, and the tag is read weakly on the first read cycle when tagged object approaches the read zone, it will not have a chance to register higher on the next read cycle when it is fully positioned in the read zone (or when passing through) because NC will ignore it. So the takeaway is to consider NC carefully when RSSI filtering is also being used.

 

Antenna RSSI Option

Used in conjunction with Log Antenna option above: Note: this setting is not applicable for *ZONE option as Average is used unconditionally

*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 & logged.

 

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)

** This Feature is supported in the SRC as of v8.4.0

 

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.

 

Event Binding For Delete

This feature will purge all Reader logging (via a high speed SQL function) if the Reader Profile is deleted. The value entered here represents the Binding ID when implementing the SQL Purge feature (must be installed and configured for this to work).

 

x-Coordinate

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

 

y-Coordinate

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

 

 


Copyright © 2024 Stratum Global, Inc.