Navigation: TagNet Extension Framework (EF) > EF Endpoint >

IMOVE API Settings

Still need help? Create a Support Ticket with Stratum Support

Send comments on this topic.

← Previous Next →

 

IMOVE API Settings

This function enables changing/updating values specific to IMOVE Binding Functions:

Execute Imove Rules

Enabling this checkbox will allow the EF to execute IMOVE logic independently from core TagNet Binding

 

Map Unmapped Tags?

If the tag read is unmapped, it will attempt to map that tag based on the Default Tag ID mapping as detailed below. This is typically used when TagNet is not part of the initial tag commissioning workflow and thus has no knowledge of the object being read. This mapping is done using a default TagID (see below). That value is then used to map to the default Item (see below) and put into a location that represents the default Item and location to be used (see below). Once the tag is mapped it will attempt to process any IMOVE rules (if setup) right after mapping is complete

 

Tag Mapping Setup Example

 

 

Tag Location Setup Example

 

Default Tag ID

Enter the default TagID used as a template for mapping, the default is '*DEFAULT' however can be any other value such as 'NEW_PART' or 'ITEM4522'. Note that this is not actually mapped to a real tag so it does not have to conform to Hex encoding standards.

 

Map Container Field

Specify via check box whether to map the container field with a timestamp. Using an example value of '24F-200417' the first 3 digits represent the last 3 hex of the TagID and the rest after the '-' is the timestamp YYMMDD where YY is last two digits of year.

 

Send Error Alert Emails?

Specify via check box whether to send email error alerts (example: if level relationship does not exist based on the IMOVE Target location) Note: when the Hold State feature enabled, this send outs alerts specific to that feature.

 

Update Asset Comment Field?

If enabled, will update the Asset comment field with the last (2) levels of the new inventory location when an IMOVE occurs. This makes the current location easier to view in the Geiger Counter and Physical Inventory modules when working with Asset Objects.

 

Only Send IMOVE's to Viewer?

Specify via check box whether to only send read events that invoke an IMOVE rule to display in Event Viewer.

 

Log Events?

Specify via check box whether to log IMOVE events for diagnostic purposes. This logging is displayed in the IMOVE Events function

 

Log Event Groups?

If enabled, events will be logged that detail the movement of a given tag. This is to evaluate performance for directional logic as viewed in the IMOVE Event Groups Inquiry

 

Max Event Group Time (Minutes)

The number of minutes an event group (e.g. a single tag with 1 or many IMOVE events across 1 or many zones) will stay open. This parameter is meant to shut down an event group and startup a new one if a given tag is constantly been seen (e.g. left at a doorway choke point). This was put in for performance reasons.

This is used in conjunction with IMOVE event limit whereas if the tag goes quiet for more than the event limit time). 

 

 

IMOVE Event Limit (seconds)

The number of seconds allowable for a tag to remain in an event group. If this time is exceeded when a tag moves from one read zone to another, a new event group is created.

 

Log Hold State?

When enabled this feature provides exact start/end times when a given tagged container dwells at a location (that is associated with a hold state code). Additionally the ProcessHoldStates job needs to be setup in the Job scheduler.  Note: This updates the custom [EF.TagHoldState] table.

 

 

 

 

 

 

 

 

 

 


Copyright © 2022 Stratum Global, Inc.