On Jan 28, 2008 6:17 AM, Adam Webster <[EMAIL PROTECTED]> wrote: > > > We recently made a change to the LLRP portion of our Data Capture software > such that the ROReport is generated when the AccessReportTrigger is > activated. This change was made to reduce the number of unnecessary tag > reports. It seems works well on our Impinj Speedway reader but the Rifidi > 1.5 simulator fails to send a report. > > > The rfid llrp inventory involves one ROSpec and one AccessSpec attached to > it, the report triggers for ROSpec and AccessSpec are: > > ROSpecReport: > Trigger: 0 > N: ignored > (No report for ROSpec) > AccessSpecReport: > Trigger: 1 > (End of AccessSpec) > > > > > > Here is the basic flow we are seeing with our Impinj reader. > > > 1. ADD_ROSPEC command: > > 4,14,0,0,0,0,0,0,0,0,0,b1,0,46,0,0,0,1,0,0,0,b2,0,12,0,b3,0,5,0,0,b6,0,9,0,0,0,0,0,0,b7,0,18,0,1,0,0,0,b8,0,9,0,0,0,0,0,0,ba,0,7,30,39,1,0,ed,0,12,0,0,1,0,ee,0,b,ff,c0,1,5c,0,5,0} > > 0,ed,0,12,0 ---> ROReportTrigger = 0 (NONE) > > 2.ADD_ACCESSSPEC command: > > 4,28,0,0,0,0,0,0,0,0,0,cf,0,65,0,0,0,1,0,0,1,0,0,0,0,1,0,d0,0,7,0,0,0,0,d1,0,49,1,52,0,27,1,53,0,23,60,0,20,0,60,0,0,0,0,0,0,0,0,0,0,0,0,0,60,0,0,0,0,0,0,0,0,0,0,0,0,1,55,0,f,0,1,0,0,0,0,c0,0,0,0,2,1,55,0,f,0,2,0,0,0,0,80,0,0,0,2,0,ef,0,5,1 > > 0,ef,0,5,1 -------> AccessReportTrigger = 1 (End of AccessSpec) > > 3. The ROReport including AccessSpec result > > 4,3d(61) 0,0,0,62 0,0,9,13 0,f0(240) 0,58 > 8d,30,8,33,b2,dd,d9,5,80,35,5,0,16,89,0,0,0,1,8e,0,1,8a,30,39,81,0,1,86,d6,87,0,1,82,0,4,43,e8,96,73,2,d8,84,0,4,43,e8,96,73,2,d8,88,0,1,90,0,0,0,1,1,5d,0,d,0,0,1,0,2,60,0,0,0,1,5d,0,d,0,0,2,0,2,e2,0,10,61 > > The last several bytes show the result report for AccessSpec: > 90,0,0,0,1, ---> AccessSpec Id =1 > 1,5d,0,d,0,0,1,0,2,60,0,0,0, > 1,5d,0,d,0,0,2,0,2,e2,0,10,61 ---> read operation results > > > Regards, > Adam
Hi, This trace would be a lot easier to understand "at a glance" as LTK-XML. Generally it is a more tractable format than hexdumps since the LLRP toolkits can convert to/from binary and support easily feeding the messages to a reader. LTK-XML provides a direct mapping between binary LLRP protocol and XML. The tool is available online at http://llrp.org/tools.html , no installation required. You just feed it a Wireshark or tcpdump capture file and it returns you LTK-XML. LTK upon which it is based is linked to by the same page. Of course, LTK offers full LTK parsers for most languages which would obviate the debugging you are doing now. Your binary LLRP encoder is broken. One problem (there may be others) is that the message length on your ADD_ROSPEC is zero. 04 14 00 00 00 00 Even if you don't use LTK, I would suggest testing your encoder/decoder against one of the LTK Toolkit variants. -- John. ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Rifidi-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/rifidi-developers
