When I invoke the constructor in LLRP.LLRPClient that accepts a port, the reader does not correctly pass read events to my client application. It appears that this second constructor doesn't do the same things that the default constructor performs, specifically related to threading. Looks like a simple fix (hopefully).