SIRIT Technologies. Release Notes Device Agent for the INfinity 510 3.0.0.200909031412 INTRODUCTION ============ The Device Agent for the Infinity 510 allows for the IBM WebSphere Sensor Events server to communicate with Sirit Infinity 510 Reader. The user can use the Administrative Console that comes with the Sensor Events server to download the agent from an update site, define a device, location and controller, and start receiving events from the physical Infinity 510 Readers. Device Agent measurements can be set through the Administrative console for a given device configuration group. Applications can now subscribe to the commands and signals generated from the device agent. This allows for integration of the Infinity 510 readers into complicated RFID systems which currently run using the IBM WebSphere Sensor Events Server. UPGRADE PROCEDURE ================= 1) Extract the features and plugins directory to the Update site defined for the previous version of the Device Agent. 2) On the IBM Websphere Sensor Events Server Admin Console, select "Agent Configuration" in the right hand frame. 3) Press the "Download Agent" button 4) Select the "Update and existing agent" radio button and select the Device Agent for the INfinity 510 in the "Agent Name" combo box. Press the "Next" button. 5) Select the update site for the INfinity 510 Device Agent and press the "Next" button. 6) Select the Sirit INfinity 510 device agent with version 3.0.0.200909031412 and press the "Next" button. 7) Accept the License Agreement and press the "Next" button. 8) On the confirmation page, select the "Finished" button. 9) With this new agent, the Configuration Group for the INfinity 510 device will need to be edited. Select "Devices" in the right hand frame. 10) Click on the Configuration Group used for the INfinity 510 device. 11) Click on the Sirit INfinity 510 device agent. Data will be displayed in the "Selected Agent Details" box. Under the "PID" combo box select com.sirit.device.agent.inventory.profile.factory.DeviceAgentInventoryProfileFactory. In the "Property" combo box, select IPAddress. In the Value field, enter in the IP Address of the device. Press the "Apply" button and then the "Update" button. ***************** CURRENT RELEASE ***************** 3.0.0.200909031412 (03Sep2009): 1) Enhancements a) The TID is reported, if present in the tag event information, in the read data map using the key TID_DATA_KEY ("tid") as a byte array. b) The User Data is reported, if present in the tag event information, in the read data map using the key USERDATA_DATA_KEY ("userdata") as a byte array. c) The RSSI is reported, if present in the tag event information, in the read data map using the key PEAK_RSSI_DATA_KEY ("peakRSSI") as a float. d) The Protocol Type is reported, if present in the tag event information, in the read data map using the key TAG_TYPE_DATA_KEY ("tagType") as a string which is prefixed with "rfid_". e) The Frequency is reported, if present in the tag event information, in the read data map using the key "frequency" as an Integer. f) Three new reader tag event types are also supported; Tag Depart, Stray-Tag Elimination, and Antenna Cross as well as the default Tag Read event. The event type will be reported in the read data map using the key "eventType" as a string whose valid value are listed below. Tag Read event.tag.arrive Tag Depart event.tag.depart Stray-Tag Elimination event.tag.portal_cross Antenna Cross event.tag.antenna_cross g) Added a new property to enable/disable the reporting of Tag Read events. The new property is part of the Inventory Profile and called "Tag Arrive Event". Supported fields are true and false. h) Added a new property to set the information sent from the reader for a Tag Read event. The new property is part of the Inventory Profile and called "Tag Reporting Arrive Fields". This variable contains the fields to be reported with a tag depart. Supported fields are tag_id, tid, user_data, type, time, antenna, freq, and rssi. i) Added a new property to enable/disable the reporting of Tag Depart events. The new property is part of the Inventory Profile and called "Tag Depart Event". Supported fields are true and false. j) Added a new property to set the information sent from the reader for a Tag Depart event. The new property is part of the Inventory Profile and called "Tag Reporting Depart Fields". This variable contains the fields to be reported with a tag read. Supported fields are tag_id, tid, user_data, type, time, antenna, and repeat. k) Added a new property to enable/disable the reporting of Stray-Tag Elimination events. The new property is part of the Inventory Profile and called "Stray-Tag Elimination Event". Supported fields are true and false. l) Added a new property to set the information sent from the reader for a Stray-Tag Elimination event. The new property is part of the Inventory Profile and called "Tag Reporting Stray-Tag Elimination Fields". This variable contains the fields to be reported with a stray-tag elimination. Supported fields are tag_id, tid, type, time, antenna, freq and rssi. m) Added a new property to enable/disable the reporting of Antenna Cross events. The new property is part of the Inventory Profile and called "Antenna Cross Event". Supported fields are true and false. n) Added a new property to set the information sent from the reader for a Antenna Cross event. The new property is part of the Inventory Profile and called "Tag Reporting Antenna Cross Fields". This variable contains the fields to be reported with an antenna cross . Supported fields are tag_id, tid, type, time, antenna, freq and rssi. o) The count will reported will be one, except if "repeat" is present in the tag event information. This information is only available for the Tag Depart Event. 2) Bugs Fixed a) Fixed a bug with parsing the software version from the reader. b) Fixed the bug of the device agent not terminating waiting on a BufferedReader.readLine() call for the event handler for tag events. 3) Known Limitations a) The Device Agent for the INfinity 510 is applicable to reader firmware of 3.0 and the Sensor Events Server 6.2 4) Additional Information a) This version of the Device Agent utilizes features provided by the 3.0 firmware release of the INfinity 510. Certain features may not work when used with a reader running previous versions of firmware. It is recommended to upgrade the Device Agent. in the same timeframe as upgrading the reader firmware. ***************** PREVIOUS RELEASE ***************** 2.0.0.200803140927 (17Mar2008): 1) Enhancements a) Reworked the Device Agent to use the Rapid API. b) Enhanced to take advantage of enhancements in the reader firmware 2.0. 2) Bugs Fixed a) Reduced the number and size of the jar files used by the Device Agent. 3) Known Limitations a) The Device Agent for the INfinity 510 is applicable to reader firmware of 2.0 and the Premises Server 6.1 4) Additional Information a) This version of the Device Agent utilizes features provided by the 2.0 firmware release of the INfinity 510. Certain features may not work when used with a reader running previous versions of firmware. It is recommended to upgrade the Device Agent. in the same timeframe as upgrading the reader firmware. ***************** INITIAL RELEASE ***************** 1.0.0.200709201142 (02Sep2007): 1) Enhancements a) Initial Release. 2) Bugs Fixed a) Initial Release. 3) Known Limitations a) The Device Agent for the Infinity 510 is applicable to reader firmware of 1.4.6318 and Premises SErver 6.0 4) Additional Information