As luck would have it, we were able to schedule a call with them yesterday to talk about this. One important item that wasn't anywhere in their documentation or sample app was that we have to send an ACK back to the device if we get a well formed response to a previous command. Otherwise, the device could hang waiting for that acknowledgement. That's good to know.

So, I'm making modifications to my existing wrapper and hopefully with the protocol tidbits I gleaned from the call I'll be able to make this work.

>Wow, their website sucks. I've found most card readers have had either a COM interface I could use or a .NET class I could interface with. I remember looking at the USBHID drivers for .NET at some point and I think I had similar issues - it would randomly lock up or not work. Thankfully I was able to find a more direct driver to use.
>
>Have you tried contacting their support dept. to see what's available? It's obvious they don't make it directly available on their website (or if they do, they've made it nearly impossible to find).