#3 Event reporting support : There has been number of requests from customers using our APIs to have a mechanism to get only new tags instead of the same tag getting reported multiple times. Having event reporting APIs will solve this problem wherein the applications can subscribe for only new tag events in which case only new tags will get reported. The other evetns like visibiulity changed events can also be supported. This feature would cover all the events currently exposed in Merlin 1.0.
The following features of Autonomous mode and RSSI/TimeBased filtering will be exposed via API3 1.1:
-
Support for enabling Autonomous Mode and configuring the following Events has been done bt expansion of TRIGGER_INFO:
-
NEW_TAG_VISIBLE
-
TAG_NOT_VISIBLE
-
TAG_BACK_TO_VISIBILITY
-
Support for RSSI Filters added in POST_FILTER and ACCESS_FILTER
-
Time based Filters - It has been decided not to support as it is achievable through existing Periodic and duration triggers.
-
API to purge Tags : RFID_PurgeTags
-
Change in READER_CAPS to report support of autonomous mode and RSSI-Filter support.
-
Change in TAG_DATA to indicate the TagEvent (New, Invisible or Back to visibility) and time at which TagEvent occured.
Event supporting
The above functionality has been done using the following custom LLRP extensions of Merlin Reader:
-
RFID_PurgeTags: MOTO_PURGE_TAGS
-
Reporting capabilities in READER_CAPS: MotoAutonomousCapabilities, MotoTagEventsGenerationCapabilities, MotoFilterCapabilities
-
RSSI-FIltering: MotoFilterList, MotoFilterRule, MotoFilterRSSIRange
-
TAG_DATA: MotoTagEventList, MotoTagEventEntry
-
Enabling Autonomous Mode through Regular ROSpec: MotoTagReportMode, MotoTagEventSelector
-
-
TAG_NOT_VISIBLE
-
TAG_BACK_TO_VISIBILITY
None
Please refer to API documentation for API/Feature Use.
-
A specific version of .NET Dll should always be used along with the C-Dll released along with it.
-
Ensure backward compatibility of API31.1 Dll with API31.0 Applications (Sample Applications, API31.0 Testcases). Wherever existing structures have been expanded out of RESERVED fields, its to be ensured that if older applications are executed, there should not be any access violations due to unintialized fields. It is better to test
