Hello all. I have a question about the RoReportTrigger and the N fields in the RoReportSpec. The N value is the number of TagReportDataParameters that must be generated before a roaccessReport will be sent (as long as N>0 and the RoReportTrigger !=0). This means that if N=5, and tags are seen by are reader, it will send out a RoAccessReport on every 5th tag (as long as the AISpec or RORspec hasn't ended).
However, my question is: Is it the intention of the spec that the ROAccessReport generated as a result of these requirements must have N TagReportData parameters in it? For example, what if the N=5, and 10 tags appear on the reader at one time (in one read cycle for the reader). Is it required that the reader send out 2 separate RO_ACCESS_REPORTs with 5 tags, or could it send out 1 message with all ten tags on it in this case? 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
