st
Date:05/05/2014 12:35 PM (GMT-05:00)
To: pyusb-users@lists.sourceforge.net
Subject: Re: [pyusb-users] read function
Inman
I remember reading failing for me too, until I realized I had to read an exact
amount of bytes, corresponding to the transfer packet size used in your
configuration; wMAX
2014-05-05 13:19 GMT-03:00 Walker Inman :
> Thanks, that sounds reasonable. I also have some cdc type devices that use
> a totally different library. Ill check those out. I think adding a wrapper
> in my application should take care of it.
>
> Regarding debug, where & how can I configure?
>
If
Inman
I remember reading failing for me too, until I realized I had to read an exact
amount of bytes, corresponding to the transfer packet size used in your
configuration; wMAXPacketSize in the EP descriptor.
I do not know if this is a problem on the Windows driver side, or if this is
mandated
From: Wander Lairson Costa
Date:05/05/2014 8:15 AM (GMT-05:00)
To: pyusb-users
Subject: Re: [pyusb-users] read function
2014-05-02 11:40 GMT-03:00 Walker Inman :
> To further the below, I have now tested both on windows and linux with the
> same result. It always takes until the 4th read cal
2014-05-02 11:40 GMT-03:00 Walker Inman :
> To further the below, I have now tested both on windows and linux with the
> same result. It always takes until the 4th read call until my response
> appears, even with the delay between reads set to zero. This seems like
> read() is causing some state
-Walker
Original message
From: Walker Inman
Date:05/01/2014 5:21 PM (GMT-05:00)
To: pyusb-users@lists.sourceforge.net
Subject: [pyusb-users] read function
I'm having a bit of difficulty reading from my device.. It seems that I have to
make the Device.read() call multiple ti
I'm having a bit of difficulty reading from my device.. It seems that I have to
make the Device.read() call multiple times in order to get the response. I
wrote a short test code that inserts a variable delay between reads.
Regardless of the delay value it seems to always take 3 or 4 read() ca
