Navigation: Filtering & Collection > Event Bindings > Available Bindings > Internal Bindings >

RFDPEVG

Still need help? Create a Support Ticket with Stratum Support

Send comments on this topic.

← Previous Next →

 

 

Binding Function

RFDPEVG

 

Binding ID

PEV_BROADCAST

 

Binding Description

Universal Inventory Mgmt Binding

 

Purpose

This is a universal binding that is commonly used for TagNet Inventory management, PEV visualization. and IP Camera support. It does not integrate directly with any external systems. This is designed to be used in conjunction with the PEV (Portal Event viewer) client application and IMOVE logic.

Logic

Collects whatever tags are seen during a read event cycle from a given portal and performs the following logic:

Processes IMOVE rules is so specified in Binding properties and automatically transfers inventory from location A to Location B. Sends out email if IMOVE has [EMAIL] keyword anywhere in description.

Processes TMOVE rules is so specified in Binding properties and updates base logging (PHLOG)

Supports full GPIO script as a result of standard MATCH / NOMATCH/ NOTAG variables.

Resolves each tag to its mapped object attributes (Product, Asset, or Person) and pushes them in real time to the PEV display Client.

Triggers Camera support if so configured in the Physical Reader profile

Supports all Filter keywords (including *RSSI, *PRODTYPE, *ANTENNA)

Supports Binding Email Exceptions

Restrictions

None identified

Files Updated

RFDLOCIN, RFDLOCIH (Insert), RFDTAGVS (tag last seen by Location/Reader/Ant), RFDTAGPR (tag last seen globally), RFDASSEX (last read stamp if configured & object is Asset)

Comments

 

Program Name

URI set to RFDPEVG

Binding Setup

Binding Properties

Email Notification

The email address to send binding specific alerts. Note: This overrides the default SMTP Recipient value under System Settings

 

Dwell

This is the time period that TagNet will ignore further read events until the dwell period has expired. For example, when a tagged object goes through a read zone and TagNet changes its location state from A to B, the dwell period gives it time to move away from the read zone before it is evaluated again for another inventory move (i.e returning back through same B to A).  The dwell time should be long enough to allow the object to move away from the portal read zone but not too long that if it is brought back in the reverse direction it will be not be ignored. There are (4) dwell time options in the dropdown. 

[Global] indicates that if the Tag was seen previously at any TagNet Physical Reader its LRE (Last Read Event) will be taken into consideration.

[Location] indicates that only if the Tag was seen at a Physical Reader within the same Logical Reader group, will its LRE will be taken into consideration.

[Reader] indicates that only if the Tag was seen at the same Physical Reader will its LRE will be taken into consideration.  ** Future

[Antenna] indicates that only if that Tag was seen at the same Antenna on a given Physical Reader will its LRE will be taken into consideration. ** Future

 

Note: The LRE time is updated every time the tag is read anywhere unless it is specifically filtered out in the Event Subscription Binding.  Though the tag event will be logged, it will not be evaluated for any business logic nor will it update the LRE. This filtering is typically done so that downstream read zones will not ignore it because its LRE was updated (e.g. if the tagged object has a specific inventory state or attribute that precludes it from being considered for dwell based logic).

 

Inventory Movement Rules

In the example below, the Inventory Movement rules are set to *RESULTSET (along with Log Result Set) which is used if Dwell is specified. Refer to the the Binding Change for detailed explanations of each directive.

 

 


Copyright © 2022 Stratum Global, Inc.