I am having a bit of trouble understanding the relationship between an accessreport and a roreport. From what I understand, each tag seen as a result of an AISpec generates a tagReportData. Then, a roreport (which is a collection of tagReportData params) can be sent at one of several times (at the end of an AISpec, at the end of a ROSpec, or after N tags have been seen).
What I don't understand is how access operations affect this. If an access operation is performed on a tag, should the results of it go on the same tagReportData parameter that was generated because of the AI? The LLRP Spec seems to indicate so: "If there was an access operation performed on the tag, the results of the OpSpecs are mandatory in the report." However, accessreports can be set to send either after N accessspecs have been executed or after the rospec is done that the access specs were contained in. This seems to conflict with the access spec results being a part of the tagReportData generated by the aispec. For example, suppose the reader can see one tag. Suppose RoReports are set to send after every AISpec. Suppose that accessReports are set to be sent after every 1 accessSpec is executed. The reader executes the aispec and an access spec operation on the tag. Should one report be sent out, or two? If just one, should it be sent out after the access operation or after the AI? Thanks, Kyle ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ llrp-toolkit-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/llrp-toolkit-devel
