Login | Register   
LinkedIn
Google+
Twitter
RSS Feed
Download our iPhone app
TODAY'S HEADLINES  |   ARTICLE ARCHIVE  |   FORUMS  |   TIP BANK
Browse DevX
Sign up for e-mail newsletters from DevX


advertisement
 

Get Started with RFID Development in Java : Page 4

Using RFID Anywhere, you can build a highly customized Radio Frequency Identification (RFID) application or service that meets your specific needs.


advertisement
Configuring the RFID Multiprotocol Connector
Before you begin using the RFID Anywhere simulated environment with the tags you have created, you must create an RFID Multiprotocol Simulator connector. The RFID Multiprotocol Simulator connector simulates the appearance of tags defined using the RFID Simulator Data Editor. The connector feeds simulated RFID data into RFID Anywhere via the RFID Multiprotocol Reader controller, simulating the raw data coming from an RFID reader. The RFID Multiprotocol Simulator connector uses a simulation (.smt) file to simulate RFID tags being brought into and out of the range of a real reader. To add and configure the RFID MP Simulator connector:

  • Using the Start menu, navigate to "Programs > RFID Anywhere > Administrator Console." The Administrator Console Login page opens.
  • Enter your credentials, and then click "Log On." The Administrator Console Home page opens.
  • From the Home page, choose "RFID Multiprotocol Simulator" from the Service Type dropdown list, and then click Add. That adds the RFID Multiprotocol Simulator connector to the list of local services and highlights it. The default name for new connectors follows the pattern RfidMPSimulator1, RfidMPSimulator2, etc.
To edit the properties of this new connector:
  1. Select the checkbox beside it and then click Edit. The properties for the connector appear in the Properties Manager, to the right of the Local Services list.
  2. Expand the Antenna1 set of properties by clicking the plus (+) symbol beside "Antenna1." Expand the Smoothing set of properties in the same manner.
  3. In the textbox for the Glimpsed Timeout property, type "100ms" (milliseconds).
  4. Repeat the two preceding steps for the Lost Timeout, Observed Threshold, and Observed Timeout properties.
  5. In the textbox for the Cycles per Trigger property, type 1.
  6. In the dropdown list for the Read on Start property, choose True.
  7. In the textbox type a name for the simulator.
  8. Beside the text field for the Session Data property, click Browse and locate the .smt file you created earlier, clicking Open after you locate and highlight the file.
Finally, click the green disk in the title bar of the Properties Manager to save the changes and update the InvTracSim1 RFID Multiprotocol Simulator connector. Click Refresh to view the updated properties in the Administrator Console.

Adding the TCP Messaging Connector
The TCP messaging connector sends processed information from RFID Anywhere via the TCP communications protocol. The output can be received by any external application listening on the configured port. To add and configure the TCP messaging connector, follow these steps:



  1. Choose TCP Messaging from the Service Type dropdown list and then click Add. The TCP messaging connector is added to the list of Local Services and is highlighted. The new TCP messaging connector has the default name TcpIpConnector1.
  2. Edit the properties of the new connector by selecting the checkbox beside it and then clicking Edit. The properties for the connector appear on the right side of the window.
  3. In the textbox for the IP Address property, type localhost.
  4. In the textbox for the Name property, type InvTracAleTCP.
  5. In the textbox for the Port property, type 10002.
  6. Click the green disk in the Properties Manager title bar to save the above changes and update the TCP messaging connector.
Adding the ALE Event Cycle connector
The ALE Event Cycle connector adheres to the EPC standard and specifies the correct format in which to report processed information. You can configure the connector to filter and group certain types of tags so that only relevant information gets transported across the network. For example, you can configure the connector to filter out products from certain manufacturers. To add and configure the ALE Event Cycle connector, follow these steps:

  1. Choose "ALE Event Cycle" from the Service Type dropdown list, and then click Add. A new ALE Event Cycle connector appears in the Local Services list. The new ALE Event Cycle connector has the default name AleECConnector1.
  2. Select the new ALE Event Cycle connector and then click Edit. The Properties Manager for the ALE Event Cycle connector appears to the right.
  3. Expand the Event Cycle set of properties, then expand the Start/Stop conditions set of properties.
  4. In the text field for the Duration (ms) property, type 1000.
  5. Expand the Logical Readers property. In the text field, type Source1 and then click the green plus sign to add the entry.
  6. In the textbox for the Report(s) Definition property, type 1.
  7. Expand the reportSpecs(1) set of properties. In the textbox for the Include Patterns property, enter urn:epc:pat:sgtin-96:1.1.2.*. The Include Patterns property is used to specify the tags that you want to be included in the report. When a value is entered for this property, only the tags that are specified will be reported. For purposes of this article, you only want the "AutoClean 77 Sterilizer" tags. The Exclude Patterns property specifies tags that you want to exclude from the reports. You can use the Grouping Patterns property to group certain tags together. For example you can group tags according to their manufacturers.
  8. In the dropdown list for the reportSpecs(1) > Report If Empty property, choose True. When this property is set to True, the ALE Event Cycle connector sends reports, even if it does not contain any tags; in other words the ALE Event Cycle connector sends empty reports when no tags are in the proximity of the reader antennas.
  9. In the textbox for the reportSpecs(1) > Report Name property, type Source1Filtered.
  10. In the dropdown list for the reportSpecs(1) > EPC to be reported property, choose CURRENT.
  11. In the textbox for the reportSpecs(1) > Name property, type FilteredSource1ALE.
  12. In the dropdown list for the Send Reports as Object property, choose False.
  13. Expand the Subscribers property. In the text box, enter FileOutput and press the green plus sign to add this item to the Subscribers list. Follow the same steps to add InvTracAleTCP and MSMQOutput to the Subscribers list.
  14. Click the green disk in the Properties Manager title bar to save the above changes and update the ALE Event Cycle connector.
The RFID ALE Protocol Business Module
The RFID ALE Protocol business module provides the business logic to link the reader group definition to the reader that's actually gathering data (the RFID MultiProtocol Simulator in this case). It's installed automatically in the list of Local Services and has the name ALEServiceModule. To configure the RFID ALE Protocol business module, follow these steps:

  1. Edit the properties of the RFID ALE protocol by selecting the checkbox beside "ALEServiceModule," and then clicking Edit. The properties for the business module appear on the right side of the window.
  2. In the textbox for the Logical Readers property, type Source1:InvTracSim1. This specifies that the RFID ALE Protocol business module should use the Source1 group of readers and connect to the InvTracSim1 RFID Multiprotocol Simulator connector as the raw data source.
  3. Click the green disk in the Properties Manager title bar to save the above changes and update the RFID ALE Protocol business module.


Comment and Contribute

 

 

 

 

 


(Maximum characters: 1200). You have 1200 characters left.

 

 

Sitemap