Can you tell me if the following errors are expected using NFCpy under windows.

I am using an SCL3711 reader with a Nexus S (Android 2.3.6) on a windows stack of:

Windows 7 (64 bit)
LibUSB 1.2.5.0 (32 bit)
Python 2.6.7 (32 bit)
PyUSB 0.4.3 (32 bit)

I can successfully echo a tag using 'python npp-echo-server.py --quirks android'. See output below:

C:\>python npp-echo-server.py --quirks android
searching for a usable reader
searching for a usb bus reader
chipset is a PN533 version 2.7
libusb0-dll:err [_usb_reap_async] timeout error

libusb0-dll:err [_usb_reap_async] timeout error

libusb0-dll:err [_usb_reap_async] timeout error

libusb0-dll:err [_usb_reap_async] timeout error

libusb0-dll:err [_usb_reap_async] timeout error

libusb0-dll:err [_usb_reap_async] timeout error

activated as p2p target in 424 kbps active mode
LLCP Link established, I'm the DEP Target
Local LLCP Settings
  LLCP Version: 1.1
  Link Timeout: 1000 ms
  Max Inf Unit: 1024 octet
  Service List: 0000000000000011
Remote LLCP Settings
  LLCP Version: 1.0
  Link Timeout: 1500 ms
  Max Inf Unit: 128 octet
  Service List: 0000000000000001
npp server bound to port 16
accepting CONNECT from SAP 33
serving npp client on remote sap 33
ndef push server got message
d1010e5402656e48656c6c6f20776f726c64
  0000: d1 01 0e 54 02 65 6e 48 65 6c 6c 6f 20 77 6f 72 ...T.enHello wor
  0010: 6c 64 ld
NDEF records:
  [0] type = urn:nfc:wkt:T
  [0] name =
  [0] data = .enHello world
sending back this same message
libusb0-dll:err [_usb_reap_async] timeout error

shutdown on link disruption
nfc.llcp.Error: [EPIPE] Broken pipe
I was the Target

The error 'libusb0-dll:err [_usb_reap_async] timeout error' repeats until I tap the reader. Is this expected?

The link doesn't seem to disconnect gracefully, generally ending with a 'nfc.llcp.Error: [EPIPE] Broken pipe' error when the Nexus S is physically moved out of range or when the screen turns off. Is this expected?