On 9/25/07, Craig Graham <[EMAIL PROTECTED]> wrote:
> This is a general LLRP question I posted to the Rifidi list, but given I'm
> working on a toolkit in dotnet to conform to the EPC spec and the XML
> schema the toolkit is using I thought it worth copying here. The dotnet
> thing I'm working on will be commercial, though, which may influence how
> welcome I am here..
>

You are completely welcome. There will eventually be a open source
.Net library available free on this site, but you are certainly
welcome as a user of the LTK schemas, and as a member of the LLRP
community.

> I've started playing with LLRP and using Rifidi as the target (also
> playing with Intelleflex but wanting to avoid locking into possibly
> non-spec dialects).
>
> According to the EPC spec 1.0.1 section 18.1, when we connect to an LLRP
> compliant reader the first thing it's supposed to send is a status report
> message, and clients aren't supposed to send anything until receiving that
> message.
>

That's right.

> I've set up Rifidi to give me an LLRP reader, but when I establish a TCP
> connection to the appropriate port it just sits there silently.
>

That's non-conforming behavior.

> I've packet sniffed a simple LLRP client and discovered that as soon as
> the client connects, it sends a packet which I manually decode as being an
> ADD_ROSPEC message with parameters;
>

You are welcome to use the online decoder at http://llrp.org in the
Tools section. It is free to use, and beats manually decoding stuff.
It is based on a variant of LTK Perl.

> 1) an AccessSpec parameter
> 2) a C1G2TagInventoryStateAwareSingulationActionParameter
> 3) an ROSpec parameter and associated sub elements.
>
> The reader then sends back a satisfactory ADD_ROSPEC_RESPONSE.
>
> So I'm confused on two counts- first the fact the client doesn't wait and
> receive the initial status message and second that the first two of those
> three parameter blocks aren't valid as far as I can see in the spec, and
> yet all appears to be fine!
>
> Can anyone enlighten me on this?
>

Post a trace from the online decoder, and we should be able to help you.

-- 
http://devwrights.com/blog

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
llrp-toolkit-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/llrp-toolkit-devel

Reply via email to