Menu
▾
▴
Re: [accada-reader-user] Accada Reader
|
From: Jonas H. <jh...@us...> - 2007-08-17 10:30:58
|
Dear Boppana, A first problem i noticed is the order you discribed in your mail: > I have used reader client and configured it to capture events > Started Event Sink > Added a new tag to Shelf 1 > But this event is not shown in Event Sink The reader establishes a connection to the sink when the command to create a notification channel is sent. If you configured the reader and started the event sink afterwards, no connection is established for the notification channel. When you close the reader and a connection was established, a message should appear in the EventSinkUI that sais 'ERROR: connection reset'. If this message does not appear, there was no connection and thus no notifications were able to reach the EventSinkUI. A potential second problem i noticed in your mail is the usage of non default DataSelector. The DataSelector was buggy and is still buggy in the latest release. I fixed it in the current developer version last week. For further testing of accada, please leave away the DataSelector configuration (steps 4 to 7 in your list of configuration commands below) until next release of a new accada version. Kind regards, Jonas On 8/16/07, Matthias Lampe <la...@in...> wrote: > > > Dear Boppana, > > > Thanks for your using Accada! I am currently travelling but will take a > look at the issue you describe beginning next week. We also fixed several > bugs in the reader module and planing a release for end of next week which > might also deal with your issues. > > Best > Matthias > > > ________________________________ > > > From: acc...@li... > [mailto:acc...@li...] On Behalf Of > Shanthi Boppana > Sent: Dienstag, 14. August 2007 23:02 > To: acc...@li... > Subject: [accada-reader-user] Accada Reader > > > > Hi, > > > I have downloded accada reader and reader client. > > > I am trying to capture reader events using > org.accada.reader.rp.client.EventSinkUI 9001 > > On the reader command line console I do see the debug statement when a > tag is read by the reader but I am not able to see the events using > EventSinkUI. > > > I have used reader client and configured it to capture events > Started Event Sink > Added a new tag to Shelf 1 > But this event is not shown in Event Sink > > > Here is my reader configuration: > > > 1) Create Notification Channel > > > <?xml version="1.0" encoding="UTF-8" standalone="yes"?> > <ns2:command xmlns:ns2="urn:epcglobal:rp:xsd:1"> > <id>44</id> > <targetName></targetName> > <notificationChannel> > <create> > <name>test</name> > <address>tcp://localhost:9001?mode=connect</address> > </create> > </notificationChannel> > </ns2:command> > > > > > 2) Creating Read Trigger > > > > > <?xml version="1.0" encoding="UTF-8" standalone="yes"?> > <ns2:command xmlns:ns2="urn:epcglobal:rp:xsd:1"> > <id>28</id> > <targetName></targetName> > <trigger> > <create> > <name>ReadTrigger2</name> > <triggerType>TIMER</triggerType> > <triggerValue>100</triggerValue> > </create> > </trigger> > </ns2:command> > > > 3) Creating NotificationTrigger > > > <?xml version="1.0" encoding="UTF-8" standalone="yes"?> > <ns2:command xmlns:ns2="urn:epcglobal:rp:xsd:1"> > <id>30</id> > <targetName></targetName> > <trigger> > <create> > <name>NotificationTrigger</name> > <triggerType>TIMER</triggerType> > <triggerValue>500</triggerValue> > </create> > </trigger> > </ns2:command> > > > > 4) Create DataSelector > > > <?xml version="1.0" encoding="UTF-8" standalone="yes"?> > <ns2:command xmlns:ns2="urn:epcglobal:rp:xsd:1"> > <id>46</id> > <targetName></targetName> > <dataSelector> > <create> > <name>DataSelector</name> > </create> > </dataSelector> > </ns2:command> > > > > 5) Adding Event Filters to Data Selectors > > > <?xml version="1.0" encoding="UTF-8" standalone="yes"?> > <ns2:command xmlns:ns2="urn:epcglobal:rp:xsd:1"> > <id>52</id> > <targetName>DataSelector</targetName> > <dataSelector> > <addEventFilters> > <eventType> > <list> > <value>EV_OBSERVED</value> > <value>EV_LOST</value> > </list> > </eventType> > </addEventFilters> > </dataSelector> > </ns2:command> > > > > 6) Adding Field Names > > > <?xml version="1.0" encoding="UTF-8" standalone="yes"?> > <ns2:command xmlns:ns2="urn:epcglobal:rp:xsd:1"> > <id>54</id> > <targetName>DataSelector</targetName> > <dataSelector> > <addFieldNames> > <fieldNames> > <list> > <value>EVENT_TYPE</value> > <value>READER_NAME</value> > <value>TAG_ID</value> > <value>TAG_ID_AS_PURE_URI</value> > <value>TAG_ID_AS_TAG_URI</value> > <value>SOURCE_NAME</value> > </list> > </fieldNames> > </addFieldNames> > </dataSelector> > </ns2:command> > > > > 7) Setting DataSelector > > > <?xml version="1.0" encoding="UTF-8" standalone="yes"?> > <ns2:command xmlns:ns2="urn:epcglobal:rp:xsd:1"> > <id>58</id> > <targetName>test</targetName> > <notificationChannel> > <setDataSelector> > <dataSelector>DataSelector</dataSelector> > </setDataSelector> > </notificationChannel> > </ns2:command> > > > 8) Setting NotificationTrigger > > > <?xml version="1.0" encoding="UTF-8" standalone="yes"?> > <ns2:command xmlns:ns2="urn:epcglobal:rp:xsd:1"> > <id>64</id> > <targetName>test</targetName> > <notificationChannel> > <addNotificationTriggers> > <triggers> > <list> > <value>NotificationTrigger</value> > </list> > </triggers> > </addNotificationTriggers> > </notificationChannel> > </ns2:command> > > > > 9) Add Current Source to Notification Channel > > > <?xml version="1.0" encoding="UTF-8" standalone="yes"?> > <ns2:command xmlns:ns2="urn:epcglobal:rp:xsd:1"> > <id>70</id> > <targetName>test</targetName> > <notificationChannel> > <addSources> > <sources> > <list> > <value>Shelf1</value> > </list> > </sources> > </addSources> > </notificationChannel> > </ns2:command> > > > > 9) Add Read Trigger to Source > > > <?xml version="1.0" encoding="UTF-8" standalone="yes"?> > <ns2:command xmlns:ns2="urn:epcglobal:rp:xsd:1"> > <id>82</id> > <targetName>Shelf1</targetName> > <source> > <addReadTriggers> > <triggers> > <list> > <value>ReadTrigger2</value> > </list> > </triggers> > </addReadTriggers> > </source> > </ns2:command> > > > Any help is greatly appreciated > > > -Boppana > -- Jonas Haller <jh...@us...> |
