pyusb-users — PyUSB users mailing list discussion

Re: [pyusb-users] ValueError: No backend available

[Michael H. <mic...@ri...>]

zadig gives me the following options:
libusbK (v 3.0.7.0)
libusb-win32 (v 1.2.6.0)
winUSB (v 6.1.7600.16385)
USB Serial (CDC)

The current libusb0 (v 1.2.6.0) was not obtained through zadig.
I think I got it by letting Windows go fish.

My recollection is that nothing from zadig worked with avrdude.
I want avrdude and python.so I don't have to go back and forth between
libraries.
I guess I'll have to try libusb-1.0 and hope it works.
'

On Fri, Feb 23, 2018 at 9:11 PM, Xiaofan Chen <xia...@gm...> wrote:

> On Thu, Feb 8, 2018 at 8:25 AM, Michael Hennebry
> <mic...@ri...> wrote:
> > I'm having trouble make pyusb work at all.
> > When typing usb stuff in interactive mode,
> > usb.core.find(...) either produces ant empty list
> > or something that prints as nothing.
> > \Python27\python search.py
> > produced ValueError: No backend available .
> > search.py :
> > import usb.core
> > import usb.util
> > import usb.control
> > import array
> > dev = usb.core.find(find_all=True)
> > print dev
> > dev = usb.core.find()
> > dev = usb.core.find(find_all=True, idVendor=0x045e, idProduct=0x0040)  #
> my
> > mouse
> > print dev
> > dev = usb.core.find(               idVendor=0x045e, idProduct=0x0040)  #
> my
> > mouse
> > print dev
> > dev = usb.core.find(find_all=True, idVendor=0x03eb, idProduct=0x2141)  #
> > Atmel ICE
> > print dev
> > dev = usb.core.find(               idVendor=0x03eb, idProduct=0x2141)  #
> > Atmel ICE
> > print dev
> >
> > I'm on Windows 10.
> > A find on libusb produces only files with names beginning libusb0.
> > How do I make pyusb work?
>
> pyusb supports libusb-win32 and libusb (aka libusb-1.0) under Windows.
> libusb-win32 is a bit old. So the better option is libusb Windows.
>
> 1) Use Zadig to install WinUSB driver to the device you are interested.
> https://github.com/libusb/libusb/wiki/Windows#driver-installation
>
> 2) Get latest version of libusb Windows binary (libusb-1.0.dll) and put
> it into a location your Python installation recognizes.
>
>
> --
> Xiaofan
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> pyusb-users mailing list
> pyu...@li...
> https://lists.sourceforge.net/lists/listinfo/pyusb-users
>

Re: [pyusb-users] Reverse Engineering an evaluation board

[Shailendra P. <bei...@gm...>]

On Sat, Feb 24, 2018 at 8:50 AM, Xiaofan Chen <xia...@gm...> wrote:

> On Sat, Dec 23, 2017 at 3:43 PM, Shailendra Paliwal
> <bei...@gm...> wrote:
> > Hello,
> >
> > I'm trying to communicate with an Analog Devices evaluation board
> (SDP-H1).
> > AD has a windows software that initializes the board and can be used to
> read
> > the data coming from the USB connection with the board.
> >
> > I have been trying to write something in pyusb that can do the same and
> work
> > with my Raspberry Pi. So far, I have figured out how to initialize the
> > board. I need help in understanding the protocol used in fetching data
> from
> > it.
> >
> > Device Descriptor: http://shailendra.me/USB.html
>
> Page not available.
>
Thanks, I have managed to make a USB driver that works nicely so far.
Coincidentally I took down that page *only* a few hours ago of your email!
Here's a copy of the page from an older commit, link
<https://htmlpreview.github.io/?https://raw.githubusercontent.com/vcidst/vcidst.github.io/fd11064e66e702046c0b29a09eb8c4f728292d02/USB.html>


>
> > Here is the PCAP file of the USB trace:
> > https://github.com/vcidst/vcidst.github.io/blob/master/
> sdph1-data_clean.pcap
> > (you can use wireshark to open pcap files)
>
This link has been removed too.


> >
> > I've read a lot of write-ups of people reverse engineering USB protocols
> > which mostly include looking at the control transfers. However, this
> device
> > only has two bulk endpoints and all the communication is done with bulk
> > transfers.
> >
> > Quick facts about the PCAP file:
> > * Replaying packets 1-108 initialize the board.
> > * At packet 109 (use filter frame.time_relative >= 40), In the windows
> > software I chose sample size 1048576 and press Continuous Capture button.
> > * Packets 109 to 119 prepare the capture from SDP-H1.
> > * From packet 120, 6 packets of similar structure are sent/received again
> > and again.
> > * After that, I see 6 packets of different structure at
> (frame.time_relative
> >>= 41.059593)
> > * Packets after (frame.time_relative >=41.073968) are of different
> structure
> > again until the end.
> > * Towards the end, I stop the capture from the windows software thus the
> > last few packets should be stop packets .
> >
> > My questions now are,
> > 1. Is this device following any standard USB protocol format that I am
> not
> > familiar with?
>
> Most likely it uses vendor specific protocols not falling into standard
> USB device class definitions.
>
> > 2. I'm currently replaying the packets to initialize the device, is
> there a
> > better way to do this?
>
> If you do not know the protocol, this seems to be the only way.
>
> > 3. (a basic question that I still don't understand) in USB Communication,
> > after I have sent Bulk Write request. Do I need to send a bulk read
> request
> > if I need to read some data? Can the program just not read whatever the
> > device sends without me sending the device anything?
>
> No. USB does not work that way. The device does not automatically send
> data to the host without host initiate the communication.
>
> > 4. The data packets here are huge and I was wondering if I need to send
> the
> > entire packets whenever sending a bulk write request. Is there a way I
> can
> > figure out what is essential information in the packet and what is not?
>
> If you do not know the protocol, I do not think you have a way to know
> what is essential and what is not. You have to look into the huge data
> and then try to understand. All in all the efforts required may be huge.
>
> > (I have read the Bulk Transfer section from USB in a Nutshell but still
> > didn't understand why it has to be this way unlike say, RS232
> communication
> > where the device can keep on sending data in continuous mode)
>
> USB is much more complicated than serial communication.
>
> On the other hand, there is probably an easier way out without using
> the SDP-H1 if your interests are to connect your Raspberry Pi to a
> paticular
> daughter board. Quite some of them using SPI protocol. The schematics
> and documentations of the daughter boards are available.
>

I considered that option but the daughter board made the results available
on a single low voltage differential signaling self clocked interface. The
data rate required is as much as ~20 MBPS so I worked directly with their
evaluation kit first.

Thanks for your inputs. I think I will write a blog post soon detailing my
process and the tools I made use of.


>
>
>
> --
> Xiaofan
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> pyusb-users mailing list
> pyu...@li...
> https://lists.sourceforge.net/lists/listinfo/pyusb-users
>

Re: [pyusb-users] ValueError: No backend available

[Xiaofan C. <xia...@gm...>]

On Thu, Feb 8, 2018 at 8:25 AM, Michael Hennebry
<mic...@ri...> wrote:
> I'm having trouble make pyusb work at all.
> When typing usb stuff in interactive mode,
> usb.core.find(...) either produces ant empty list
> or something that prints as nothing.
> \Python27\python search.py
> produced ValueError: No backend available .
> search.py :
> import usb.core
> import usb.util
> import usb.control
> import array
> dev = usb.core.find(find_all=True)
> print dev
> dev = usb.core.find()
> dev = usb.core.find(find_all=True, idVendor=0x045e, idProduct=0x0040)  # my
> mouse
> print dev
> dev = usb.core.find(               idVendor=0x045e, idProduct=0x0040)  # my
> mouse
> print dev
> dev = usb.core.find(find_all=True, idVendor=0x03eb, idProduct=0x2141)  #
> Atmel ICE
> print dev
> dev = usb.core.find(               idVendor=0x03eb, idProduct=0x2141)  #
> Atmel ICE
> print dev
>
> I'm on Windows 10.
> A find on libusb produces only files with names beginning libusb0.
> How do I make pyusb work?

pyusb supports libusb-win32 and libusb (aka libusb-1.0) under Windows.
libusb-win32 is a bit old. So the better option is libusb Windows.

1) Use Zadig to install WinUSB driver to the device you are interested.
https://github.com/libusb/libusb/wiki/Windows#driver-installation

2) Get latest version of libusb Windows binary (libusb-1.0.dll) and put
it into a location your Python installation recognizes.


-- 
Xiaofan

Re: [pyusb-users] Reverse Engineering an evaluation board

[Xiaofan C. <xia...@gm...>]

On Sat, Dec 23, 2017 at 3:43 PM, Shailendra Paliwal
<bei...@gm...> wrote:
> Hello,
>
> I'm trying to communicate with an Analog Devices evaluation board (SDP-H1).
> AD has a windows software that initializes the board and can be used to read
> the data coming from the USB connection with the board.
>
> I have been trying to write something in pyusb that can do the same and work
> with my Raspberry Pi. So far, I have figured out how to initialize the
> board. I need help in understanding the protocol used in fetching data from
> it.
>
> Device Descriptor: http://shailendra.me/USB.html

Page not available.

> Here is the PCAP file of the USB trace:
> https://github.com/vcidst/vcidst.github.io/blob/master/sdph1-data_clean.pcap
> (you can use wireshark to open pcap files)
>
> I've read a lot of write-ups of people reverse engineering USB protocols
> which mostly include looking at the control transfers. However, this device
> only has two bulk endpoints and all the communication is done with bulk
> transfers.
>
> Quick facts about the PCAP file:
> * Replaying packets 1-108 initialize the board.
> * At packet 109 (use filter frame.time_relative >= 40), In the windows
> software I chose sample size 1048576 and press Continuous Capture button.
> * Packets 109 to 119 prepare the capture from SDP-H1.
> * From packet 120, 6 packets of similar structure are sent/received again
> and again.
> * After that, I see 6 packets of different structure at (frame.time_relative
>>= 41.059593)
> * Packets after (frame.time_relative >=41.073968) are of different structure
> again until the end.
> * Towards the end, I stop the capture from the windows software thus the
> last few packets should be stop packets .
>
> My questions now are,
> 1. Is this device following any standard USB protocol format that I am not
> familiar with?

Most likely it uses vendor specific protocols not falling into standard
USB device class definitions.

> 2. I'm currently replaying the packets to initialize the device, is there a
> better way to do this?

If you do not know the protocol, this seems to be the only way.

> 3. (a basic question that I still don't understand) in USB Communication,
> after I have sent Bulk Write request. Do I need to send a bulk read request
> if I need to read some data? Can the program just not read whatever the
> device sends without me sending the device anything?

No. USB does not work that way. The device does not automatically send
data to the host without host initiate the communication.

> 4. The data packets here are huge and I was wondering if I need to send the
> entire packets whenever sending a bulk write request. Is there a way I can
> figure out what is essential information in the packet and what is not?

If you do not know the protocol, I do not think you have a way to know
what is essential and what is not. You have to look into the huge data
and then try to understand. All in all the efforts required may be huge.

> (I have read the Bulk Transfer section from USB in a Nutshell but still
> didn't understand why it has to be this way unlike say, RS232 communication
> where the device can keep on sending data in continuous mode)

USB is much more complicated than serial communication.

On the other hand, there is probably an easier way out without using
the SDP-H1 if your interests are to connect your Raspberry Pi to a paticular
daughter board. Quite some of them using SPI protocol. The schematics
and documentations of the daughter boards are available.



-- 
Xiaofan

[pyusb-users] ValueError: No backend available

[Michael H. <mic...@ri...>]

I'm having trouble make pyusb work at all.
When typing usb stuff in interactive mode,
usb.core.find(...) either produces ant empty list
or something that prints as nothing.
\Python27\python search.py
produced ValueError: No backend available .
search.py :
import usb.core
import usb.util
import usb.control
import array
dev = usb.core.find(find_all=True)
print dev
dev = usb.core.find()
dev = usb.core.find(find_all=True, idVendor=0x045e, idProduct=0x0040)  # my
mouse
print dev
dev = usb.core.find(               idVendor=0x045e, idProduct=0x0040)  # my
mouse
print dev
dev = usb.core.find(find_all=True, idVendor=0x03eb, idProduct=0x2141)  #
Atmel ICE
print dev
dev = usb.core.find(               idVendor=0x03eb, idProduct=0x2141)  #
Atmel ICE
print dev

I'm on Windows 10.
A find on libusb produces only files with names beginning libusb0.
How do I make pyusb work?

Michael Hennebry

[pyusb-users] Reverse Engineering an evaluation board

[Shailendra P. <bei...@gm...>]

Hello,

I'm trying to communicate with an Analog Devices evaluation board (SDP-H1
<http://www.analog.com/en/design-center/evaluation-hardware-and-software/evaluation-boards-kits/eval-sdp-h1.html>).
AD has a windows software that initializes the board and can be used to
read the data coming from the USB connection with the board.

I have been trying to write something in pyusb that can do the same and
work with my Raspberry Pi. *So far, I have figured out how to initialize
the board. I need help in understanding the protocol used in fetching data
from it.*

Device Descriptor: http://shailendra.me/USB.html
Here is the PCAP file of the USB trace:
https://github.com/vcidst/vcidst.github.io/blob/master/sdph1-data_clean.pcap
(you can use wireshark to open pcap files)

I've read a lot of write-ups of people reverse engineering USB protocols
which mostly include looking at the control transfers. However, this device
only has two bulk endpoints and all the communication is done with bulk
transfers.

Quick facts about the PCAP file:
* Replaying packets 1-108 initialize the board.
* At packet 109 (use filter frame.time_relative >= 40), In the windows
software I chose sample size 1048576 and press Continuous Capture button.
* Packets 109 to 119 prepare the capture from SDP-H1.
* From packet 120, 6 packets of similar structure are sent/received again
and again.
* After that, I see 6 packets of different structure at
(frame.time_relative >= 41.059593)
* Packets after (frame.time_relative >=41.073968) are of different
structure again until the end.
* Towards the end, I stop the capture from the windows software thus the
last few packets should be stop packets .

My questions now are,
1. Is this device following any standard USB protocol format that I am not
familiar with?
2. I'm currently replaying the packets to initialize the device, is there a
better way to do this?
3. (a basic question that I still don't understand) in USB Communication,
after I have sent Bulk Write request. Do I need to send a bulk read request
if I need to read some data? Can the program just not read whatever the
device sends without me sending the device anything?
4. The data packets here are huge and I was wondering if I need to send the
entire packets whenever sending a bulk write request. Is there a way I can
figure out what is essential information in the packet and what is not?

(I have read the Bulk Transfer section
<http://www.beyondlogic.org/usbnutshell/usb4.shtml#Bulk> from USB in a
Nutshell but still didn't understand why it has to be this way unlike say,
RS232 communication where the device can keep on sending data in continuous
mode)

PS: Happy Holidays to everyone!

Thanks!
Shailendra

Re: [pyusb-users] backend not loading

[Tormod V. <lis...@gm...>]

It can be discussed what is the best way, but what is supported from
the distribution point of view is installing the "python-usb" package
and not using pip.

Anyway, if the python stack trace doesn't tell what's going wrong, I'd
recommend running strace, maybe "strace -e open" for a start.

Tormod


On Thu, Dec 21, 2017 at 3:00 PM, Sylvain Martel <ki...@gm...> wrote:
> Hi,
>
>     Not sure what you mean by custom build as pyusb(1.0.2) is installed
> using pip, and python is the stock install from the OS.  But it run fine
> outside a container.  I'll try to find out why
>
>
> On 2017-12-20 06:15 PM, Tormod Volden wrote:
>> Sylvain,
>>
>> Does it work with stock python and pyusb ("python-usb" on Debian)
>> packages? Apparently you are running some custom built modules under
>> /usr/local.
>>
>> BTW, the -dev package (development headers and archives) depends on
>> the libusb-1.0-0 library package, so installing the former will pull
>> in the latter.
>>
>> Regards,
>> Tormod
>>
>>
>>
>> On Tue, Dec 19, 2017 at 8:46 PM, Sylvain Martel wrote:
>>> Hi,
>>>
>>>   No change by installing libusb-1.0-0.  I also tried pointing to it
>>> directly using this line
>>>
>>> usb.backend.libusb1.get_backend(find_library=lambda x:
>>> "/usr/lib/x86_64-linux-gnu/libusb-1.0.so")
>>>
>>> Still the same error :-/
>>>
>>> python_1    | 2017-12-19 19:40:25,197
>>> DEBUG:usb.backend.libusb1:_LibUSB.__init__(<CDLL
>>> '/usr/lib/x86_64-linux-gnu/libusb-1.0.so', handle 7cbd00 at 0x7fe8641b30f0>)
>>> python_1    | 2017-12-19 19:40:25,197 ERROR:usb.backend.libusb1:Error
>>> loading libusb 1.0 backend
>>> python_1    | Traceback (most recent call last):
>>> python_1    |   File
>>> "/usr/local/lib/python3.6/site-packages/usb/backend/libusb1.py", line
>>> 945, in get_backend
>>> python_1    |     return _LibUSB(_lib)
>>> python_1    |   File
>>> "/usr/local/lib/python3.6/site-packages/usb/_debug.py", line 60, in do_trace
>>> python_1    |     return f(*args, **named_args)
>>> python_1    |   File
>>> "/usr/local/lib/python3.6/site-packages/usb/backend/libusb1.py", line
>>> 708, in __init__
>>> python_1    |     _check(self.lib.libusb_init(byref(self.ctx)))
>>> python_1    |   File
>>> "/usr/local/lib/python3.6/site-packages/usb/backend/libusb1.py", line
>>> 595, in _check
>>> python_1    |     raise USBError(_strerror(ret), ret, _libusb_errno[ret])
>>> python_1    | usb.core.USBError: [Errno None] Other error
>>> python_1    | 2017-12-19 19:40:25,198
>>> DEBUG:usb.backend.libusb1:_LibUSB._finalize_object()
>>> west_python_1 exited with code 139
>>>
>> ------------------------------------------------------------------------------
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>> _______________________________________________
>> pyusb-users mailing list
>> pyu...@li...
>> https://lists.sourceforge.net/lists/listinfo/pyusb-users
>
> --
>
> ---------------------------------
> SVP encrypter les courriels si possible/Please encrypt e-mails if you can.
> Certificat s/mime inclus dans le message
> pgpKey Id:03044B68
>
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> pyusb-users mailing list
> pyu...@li...
> https://lists.sourceforge.net/lists/listinfo/pyusb-users

Re: [pyusb-users] backend not loading

[Sylvain M. <ki...@gm...>]

Hi,

    Not sure what you mean by custom build as pyusb(1.0.2) is installed
using pip, and python is the stock install from the OS.  But it run fine
outside a container.  I'll try to find out why


On 2017-12-20 06:15 PM, Tormod Volden wrote:
> Sylvain,
>
> Does it work with stock python and pyusb ("python-usb" on Debian)
> packages? Apparently you are running some custom built modules under
> /usr/local.
>
> BTW, the -dev package (development headers and archives) depends on
> the libusb-1.0-0 library package, so installing the former will pull
> in the latter.
>
> Regards,
> Tormod
>
>
>
> On Tue, Dec 19, 2017 at 8:46 PM, Sylvain Martel wrote:
>> Hi,
>>
>>   No change by installing libusb-1.0-0.  I also tried pointing to it
>> directly using this line
>>
>> usb.backend.libusb1.get_backend(find_library=lambda x:
>> "/usr/lib/x86_64-linux-gnu/libusb-1.0.so")
>>
>> Still the same error :-/
>>
>> python_1    | 2017-12-19 19:40:25,197
>> DEBUG:usb.backend.libusb1:_LibUSB.__init__(<CDLL
>> '/usr/lib/x86_64-linux-gnu/libusb-1.0.so', handle 7cbd00 at 0x7fe8641b30f0>)
>> python_1    | 2017-12-19 19:40:25,197 ERROR:usb.backend.libusb1:Error
>> loading libusb 1.0 backend
>> python_1    | Traceback (most recent call last):
>> python_1    |   File
>> "/usr/local/lib/python3.6/site-packages/usb/backend/libusb1.py", line
>> 945, in get_backend
>> python_1    |     return _LibUSB(_lib)
>> python_1    |   File
>> "/usr/local/lib/python3.6/site-packages/usb/_debug.py", line 60, in do_trace
>> python_1    |     return f(*args, **named_args)
>> python_1    |   File
>> "/usr/local/lib/python3.6/site-packages/usb/backend/libusb1.py", line
>> 708, in __init__
>> python_1    |     _check(self.lib.libusb_init(byref(self.ctx)))
>> python_1    |   File
>> "/usr/local/lib/python3.6/site-packages/usb/backend/libusb1.py", line
>> 595, in _check
>> python_1    |     raise USBError(_strerror(ret), ret, _libusb_errno[ret])
>> python_1    | usb.core.USBError: [Errno None] Other error
>> python_1    | 2017-12-19 19:40:25,198
>> DEBUG:usb.backend.libusb1:_LibUSB._finalize_object()
>> west_python_1 exited with code 139
>>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> pyusb-users mailing list
> pyu...@li...
> https://lists.sourceforge.net/lists/listinfo/pyusb-users

-- 

---------------------------------
SVP encrypter les courriels si possible/Please encrypt e-mails if you can.
Certificat s/mime inclus dans le message
pgpKey Id:03044B68

Re: [pyusb-users] backend not loading

[Tormod V. <lis...@gm...>]

Sylvain,

Does it work with stock python and pyusb ("python-usb" on Debian)
packages? Apparently you are running some custom built modules under
/usr/local.

BTW, the -dev package (development headers and archives) depends on
the libusb-1.0-0 library package, so installing the former will pull
in the latter.

Regards,
Tormod



On Tue, Dec 19, 2017 at 8:46 PM, Sylvain Martel wrote:
> Hi,
>
>   No change by installing libusb-1.0-0.  I also tried pointing to it
> directly using this line
>
> usb.backend.libusb1.get_backend(find_library=lambda x:
> "/usr/lib/x86_64-linux-gnu/libusb-1.0.so")
>
> Still the same error :-/
>
> python_1    | 2017-12-19 19:40:25,197
> DEBUG:usb.backend.libusb1:_LibUSB.__init__(<CDLL
> '/usr/lib/x86_64-linux-gnu/libusb-1.0.so', handle 7cbd00 at 0x7fe8641b30f0>)
> python_1    | 2017-12-19 19:40:25,197 ERROR:usb.backend.libusb1:Error
> loading libusb 1.0 backend
> python_1    | Traceback (most recent call last):
> python_1    |   File
> "/usr/local/lib/python3.6/site-packages/usb/backend/libusb1.py", line
> 945, in get_backend
> python_1    |     return _LibUSB(_lib)
> python_1    |   File
> "/usr/local/lib/python3.6/site-packages/usb/_debug.py", line 60, in do_trace
> python_1    |     return f(*args, **named_args)
> python_1    |   File
> "/usr/local/lib/python3.6/site-packages/usb/backend/libusb1.py", line
> 708, in __init__
> python_1    |     _check(self.lib.libusb_init(byref(self.ctx)))
> python_1    |   File
> "/usr/local/lib/python3.6/site-packages/usb/backend/libusb1.py", line
> 595, in _check
> python_1    |     raise USBError(_strerror(ret), ret, _libusb_errno[ret])
> python_1    | usb.core.USBError: [Errno None] Other error
> python_1    | 2017-12-19 19:40:25,198
> DEBUG:usb.backend.libusb1:_LibUSB._finalize_object()
> west_python_1 exited with code 139
>

Re: [pyusb-users] backend not loading

[Sylvain M. <ki...@gm...>]

Hi,

  No change by installing libusb-1.0-0.  I also tried pointing to it
directly using this line

usb.backend.libusb1.get_backend(find_library=lambda x:
"/usr/lib/x86_64-linux-gnu/libusb-1.0.so")

Still the same error :-/

python_1    | 2017-12-19 19:40:25,197
DEBUG:usb.backend.libusb1:_LibUSB.__init__(<CDLL
'/usr/lib/x86_64-linux-gnu/libusb-1.0.so', handle 7cbd00 at 0x7fe8641b30f0>)
python_1    | 2017-12-19 19:40:25,197 ERROR:usb.backend.libusb1:Error
loading libusb 1.0 backend
python_1    | Traceback (most recent call last):
python_1    |   File
"/usr/local/lib/python3.6/site-packages/usb/backend/libusb1.py", line
945, in get_backend
python_1    |     return _LibUSB(_lib)
python_1    |   File
"/usr/local/lib/python3.6/site-packages/usb/_debug.py", line 60, in do_trace
python_1    |     return f(*args, **named_args)
python_1    |   File
"/usr/local/lib/python3.6/site-packages/usb/backend/libusb1.py", line
708, in __init__
python_1    |     _check(self.lib.libusb_init(byref(self.ctx)))
python_1    |   File
"/usr/local/lib/python3.6/site-packages/usb/backend/libusb1.py", line
595, in _check
python_1    |     raise USBError(_strerror(ret), ret, _libusb_errno[ret])
python_1    | usb.core.USBError: [Errno None] Other error
python_1    | 2017-12-19 19:40:25,198
DEBUG:usb.backend.libusb1:_LibUSB._finalize_object()
west_python_1 exited with code 139



On 2017-12-19 02:08 PM, Srujan Chaitanya wrote:
> Try installing libusb , I think dev version just by itself not usefull.
>
>> On Dec 19, 2017, at 6:36 AM, Sylvain Martel <ki...@gm...> wrote:
>>
>> Hi,
>>
>>  I'm trying to use pyusb in a container but it has problem connecting to libusb.
>>
>> In the container, libusb is installed using "RUN apt-get install -y libusb-1.0-0-dev"
>>
>> and I'm trying this simple code:
>>
>> import usb.core
>> import usb.util
>>
>> def main(args=None):
>>     #open()
>>     usb.core.find()
>>
>> I then get this error message:
>>
>> python_1    | 2017-12-19 13:58:20,475 DEBUG:usb.backend.libusb1:_LibUSB.__init__(<CDLL 'libusb-1.0.so.0', handle 19ea450 at 0x7fdce0585c50>)
>> python_1    | 2017-12-19 13:58:20,475 ERROR:usb.backend.libusb1:Error loading libusb 1.0 backend
>> python_1    | Traceback (most recent call last):
>> python_1    |   File "/usr/local/lib/python3.6/site-packages/usb/backend/libusb1.py", line 945, in get_backend
>> python_1    |     return _LibUSB(_lib)
>> python_1    |   File "/usr/local/lib/python3.6/site-packages/usb/_debug.py", line 60, in do_trace
>> python_1    |     return f(*args, **named_args)
>> python_1    |   File "/usr/local/lib/python3.6/site-packages/usb/backend/libusb1.py", line 708, in __init__
>> python_1    |     _check(self.lib.libusb_init(byref(self.ctx)))
>> python_1    |   File "/usr/local/lib/python3.6/site-packages/usb/backend/libusb1.py", line 595, in _check
>> python_1    |     raise USBError(_strerror(ret), ret, _libusb_errno[ret])
>> python_1    | usb.core.USBError: [Errno None] Other error
>> python_1    | 2017-12-19 13:58:20,477 DEBUG:usb.backend.libusb1:_LibUSB._finalize_object()
>>
>>
>> Any idea what might cause the problem?
>> ------------------------------------------------------------------------------
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot_______________________________________________
>> pyusb-users mailing list
>> pyu...@li...
>> https://lists.sourceforge.net/lists/listinfo/pyusb-users
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> pyusb-users mailing list
> pyu...@li...
> https://lists.sourceforge.net/lists/listinfo/pyusb-users

-- 

---------------------------------
SVP encrypter les courriels si possible/Please encrypt e-mails if you can.
Certificat s/mime inclus dans le message
pgpKey Id:03044B68

Re: [pyusb-users] backend not loading

[Srujan C. <sri...@gm...>]

Try installing libusb , I think dev version just by itself not usefull.

> On Dec 19, 2017, at 6:36 AM, Sylvain Martel <ki...@gm...> wrote:
> 
> Hi,
> 
>  I'm trying to use pyusb in a container but it has problem connecting to libusb.
> 
> In the container, libusb is installed using "RUN apt-get install -y libusb-1.0-0-dev"
> 
> and I'm trying this simple code:
> 
> import usb.core
> import usb.util
> 
> def main(args=None):
>     #open()
>     usb.core.find()
> 
> I then get this error message:
> 
> python_1    | 2017-12-19 13:58:20,475 DEBUG:usb.backend.libusb1:_LibUSB.__init__(<CDLL 'libusb-1.0.so.0', handle 19ea450 at 0x7fdce0585c50>)
> python_1    | 2017-12-19 13:58:20,475 ERROR:usb.backend.libusb1:Error loading libusb 1.0 backend
> python_1    | Traceback (most recent call last):
> python_1    |   File "/usr/local/lib/python3.6/site-packages/usb/backend/libusb1.py", line 945, in get_backend
> python_1    |     return _LibUSB(_lib)
> python_1    |   File "/usr/local/lib/python3.6/site-packages/usb/_debug.py", line 60, in do_trace
> python_1    |     return f(*args, **named_args)
> python_1    |   File "/usr/local/lib/python3.6/site-packages/usb/backend/libusb1.py", line 708, in __init__
> python_1    |     _check(self.lib.libusb_init(byref(self.ctx)))
> python_1    |   File "/usr/local/lib/python3.6/site-packages/usb/backend/libusb1.py", line 595, in _check
> python_1    |     raise USBError(_strerror(ret), ret, _libusb_errno[ret])
> python_1    | usb.core.USBError: [Errno None] Other error
> python_1    | 2017-12-19 13:58:20,477 DEBUG:usb.backend.libusb1:_LibUSB._finalize_object()
> 
> 
> Any idea what might cause the problem?
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot_______________________________________________
> pyusb-users mailing list
> pyu...@li...
> https://lists.sourceforge.net/lists/listinfo/pyusb-users

[pyusb-users] backend not loading

[Sylvain M. <ki...@gm...>]

Hi,

 I'm trying to use pyusb in a container but it has problem connecting to
libusb.

In the container, libusb is installed using "RUN apt-get install -y
libusb-1.0-0-dev"

and I'm trying this simple code:

import usb.core
import usb.util

def main(args=None):
    #open()
    usb.core.find()

I then get this error message:

python_1    | 2017-12-19 13:58:20,475
DEBUG:usb.backend.libusb1:_LibUSB.__init__(<CDLL 'libusb-1.0.so.0', handle
19ea450 at 0x7fdce0585c50>)
python_1    | 2017-12-19 13:58:20,475 ERROR:usb.backend.libusb1:Error
loading libusb 1.0 backend
python_1    | Traceback (most recent call last):
python_1    |   File
"/usr/local/lib/python3.6/site-packages/usb/backend/libusb1.py", line 945,
in get_backend
python_1    |     return _LibUSB(_lib)
python_1    |   File
"/usr/local/lib/python3.6/site-packages/usb/_debug.py", line 60, in do_trace
python_1    |     return f(*args, **named_args)
python_1    |   File
"/usr/local/lib/python3.6/site-packages/usb/backend/libusb1.py", line 708,
in __init__
python_1    |     _check(self.lib.libusb_init(byref(self.ctx)))
python_1    |   File
"/usr/local/lib/python3.6/site-packages/usb/backend/libusb1.py", line 595,
in _check
python_1    |     raise USBError(_strerror(ret), ret, _libusb_errno[ret])
python_1    | usb.core.USBError: [Errno None] Other error
python_1    | 2017-12-19 13:58:20,477
DEBUG:usb.backend.libusb1:_LibUSB._finalize_object()


Any idea what might cause the problem?

Re: [pyusb-users] Please join me in congratulating Robert Wlodarczyk as the new PyUSB maintainer

[Robert W. <ro...@si...>]

Thank you Wander for the warm welcome and opportunity to be the PyUSB owner!

I would like to thank Wander for starting this project and bringing it so
far in 12 years. Without Wander's effort to kickstart this project, those
working with USB would need to go through much heavy lifting. This project
has enabled the Python community to work with USB-based hardware in a
straight forward fashion. I appreciate Wander's continued support during
the transition.

As is the case with folks in this community, PyUSB is an important part of
my work. For systems that I've developed and worked on, it is used
extensively in automated scenarios to control various measurement
instruments. Ensuring that this project remains well supported and growing
the community is an important part of the Python community that uses USB
hardware.

I appreciate the confidence Wander has placed in me and hope to deliver on
this confidence. I'd also like to echo Wander's call for more people to
become project maintainers. If you're interested in being a co-maintainer,
please let me know.

Once again, thank you Wander for the opportunity to be the owner of PyUSB
and for initiating the project and community!

On Fri, Nov 10, 2017 at 3:57 AM, Wander Lairson Costa <
wan...@gm...> wrote:

> Hi there all,
>
> Good news for the PyUSB users. As you know, I can't commit to PyUSB
> maintainership anymore and recently I started to look for a new
> maintainer.
>
> Well, the day has come, Robert volunteered to become the new maintainer!!!
>
> First of all, I would like to say thank you to the community for the
> patience and for understanding my personal issues.
>
> Taking this decision wasn't easy, PyUSB started when I was still an
> undergraduate student, 12 years ago. At that time, I never had made a
> single contribution to an open source project and created PyUSB only
> because nobody had done it yet. The intention was just to have a tool
> to write quick prototypes for USB hardware I was responsible to write
> the device drivers to.
>
> I remember my thought at the time I decided to open source it: "Well,
> 6 billion people out there, there must be someone with the same
> problem as mine, let me put this horrible code in SourceForge and make
> his/er life less painful". The project just became popular at levels I
> was not expecting.
>
> But time passes and life moves on, I am not writing USB device drivers
> anymore and my free time to commit to the project is just not enough,
> given the user base size.
>
> Now I would like to say thank you to Robert for stepping in as the
> maintainer. I am pretty sure PyUSB will be in good hands and he is
> going to do a fantastic job.
>
> With this news, I moved the PyUSB repo to a new location [1]. PyUSB
> now is an organization. Hopefully, this will make easier for more
> people to become project maintainers. We are handling further details
> in short future.
>
> Last but not least, although Robert from this day is the person
> responsible to drive the project development, I am not washing my
> hands, I offered him my support in this transition for whatever
> assistance he needs. Also, I shared my thoughts on areas PyUSB needs
> the most attention, and I even might submit a patch or two as a
> contributor in the future.
>
> Well, that's it. Congratulations Robert, you are officially the PyUSB
> owner, have fun :)
>
> --
> Best Regards,
> Wander Lairson Costa
>
> [1] https://github.com/pyusb/pyusb
>

[pyusb-users] Please join me in congratulating Robert Wlodarczyk as the new PyUSB maintainer

[Wander L. C. <wan...@gm...>]

Hi there all,

Good news for the PyUSB users. As you know, I can't commit to PyUSB
maintainership anymore and recently I started to look for a new
maintainer.

Well, the day has come, Robert volunteered to become the new maintainer!!!

First of all, I would like to say thank you to the community for the
patience and for understanding my personal issues.

Taking this decision wasn't easy, PyUSB started when I was still an
undergraduate student, 12 years ago. At that time, I never had made a
single contribution to an open source project and created PyUSB only
because nobody had done it yet. The intention was just to have a tool
to write quick prototypes for USB hardware I was responsible to write
the device drivers to.

I remember my thought at the time I decided to open source it: "Well,
6 billion people out there, there must be someone with the same
problem as mine, let me put this horrible code in SourceForge and make
his/er life less painful". The project just became popular at levels I
was not expecting.

But time passes and life moves on, I am not writing USB device drivers
anymore and my free time to commit to the project is just not enough,
given the user base size.

Now I would like to say thank you to Robert for stepping in as the
maintainer. I am pretty sure PyUSB will be in good hands and he is
going to do a fantastic job.

With this news, I moved the PyUSB repo to a new location [1]. PyUSB
now is an organization. Hopefully, this will make easier for more
people to become project maintainers. We are handling further details
in short future.

Last but not least, although Robert from this day is the person
responsible to drive the project development, I am not washing my
hands, I offered him my support in this transition for whatever
assistance he needs. Also, I shared my thoughts on areas PyUSB needs
the most attention, and I even might submit a patch or two as a
contributor in the future.

Well, that's it. Congratulations Robert, you are officially the PyUSB
owner, have fun :)

-- 
Best Regards,
Wander Lairson Costa

[1] https://github.com/pyusb/pyusb

Re: [pyusb-users] Centos 7 Usb Barcode scanner not able to read.

[Srujan C. <sri...@gm...>]

Hi 

One thing does puzzles me is that. Same Centos same versions of libusb and python to the very last version number on VirtualBox hosted on Mac OS works fine. 
I posted on stack overflow to get border attention any how here is the link to the question..

https://stackoverflow.com/questions/47087054/pyusb-usb-scanner-read-fails-on-centos-7?noredirect=1#comment81161517_47087054 <https://stackoverflow.com/questions/47087054/pyusb-usb-scanner-read-fails-on-centos-7?noredirect=1#comment81161517_47087054>

Centos 7 with lated kernel update 

CentOS Linux release 7.4.1708


>rpm -qa | grep -i libusb


libusbx-1.0.20-1.el7.x86_64
libusbmuxd-1.0.10-5.el7.x86_64

> On Nov 4, 2017, at 2:53 AM, Tormod Volden <lis...@gm...> wrote:
> 
> On Fri, Nov 3, 2017 at 10:18 PM, Srujan Chaitanya wrote:
>> 
>> Hardware is Dell Precision Tower 3000 Series.
>> 
>> 
>> down votefavorite
> 
> Hello Srujan,
> 
> If you are cross-posting a question from StackOverflow, it would only
> be polite to include a link to the original question.
> 
>> 
>> I'm trying to implement driver mechanism for usb barcode scanner on Centos.
>> 
>> Using PyUSB,
>> 
>> Here is high-level code. I am trying to achieve is to be able to read QR-Codes and BarCodes when someone scans and send it to message queue without user interaction.
>> 
>> dev = usb.core.find(idVendor=VENDOR_ID, idProduct=PRODUCT_ID)
>> if dev.is_kernel_driver_active(0) is True:
>>    dev.detach_kernel_driver(0)
>> dev.set_configuration()
>> dev.reset()
> 
> Do you need the reset() here?
Not really just attempting to try if that makes any difference.


> 
>> data = dev.read(endpoint.bEndpointAddress, 120,
>>                    timeout=10000)
>> currentData = list(chunks(data))
>> 
>> This code work fine on the same system with Ubuntu operating system. But on Centos 7 , All I hear rapid beeps, and nothing read from the scanner.
>> 
>> Here is everything installed on Centos, almost similar to Ubuntu that I ran on the same machine.
>> 
>> "libgusb.x86_64                         0.2.9-1.el7                     @base
>> libgusb-devel.x86_64                   0.2.9-1.el7                     @base
>> libusb.x86_64                          1:0.1.4-3.el7                   @base
>> libusb-devel.x86_64                    1:0.1.4-3.el7                   @base
> 
> The most important difference is probably the version of libusb that
> is in use. Upstream libusb.info is now at 1.0.21. Please be more
> specific about which libusb versions you have on the two systems,
> which versions of the OS, and try a newer version if possible.
> 
> Regards,
> Tormod
> 
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> pyusb-users mailing list
> pyu...@li...
> https://lists.sourceforge.net/lists/listinfo/pyusb-users

Re: [pyusb-users] Centos 7 Usb Barcode scanner not able to read.

[Tormod V. <lis...@gm...>]

On Fri, Nov 3, 2017 at 10:18 PM, Srujan Chaitanya wrote:
>
> Hardware is Dell Precision Tower 3000 Series.
>
>
> down votefavorite

Hello Srujan,

If you are cross-posting a question from StackOverflow, it would only
be polite to include a link to the original question.

>
> I'm trying to implement driver mechanism for usb barcode scanner on Centos.
>
> Using PyUSB,
>
> Here is high-level code. I am trying to achieve is to be able to read QR-Codes and BarCodes when someone scans and send it to message queue without user interaction.
>
> dev = usb.core.find(idVendor=VENDOR_ID, idProduct=PRODUCT_ID)
> if dev.is_kernel_driver_active(0) is True:
>     dev.detach_kernel_driver(0)
> dev.set_configuration()
> dev.reset()

Do you need the reset() here?

> data = dev.read(endpoint.bEndpointAddress, 120,
>                     timeout=10000)
> currentData = list(chunks(data))
>
> This code work fine on the same system with Ubuntu operating system. But on Centos 7 , All I hear rapid beeps, and nothing read from the scanner.
>
> Here is everything installed on Centos, almost similar to Ubuntu that I ran on the same machine.
>
> "libgusb.x86_64                         0.2.9-1.el7                     @base
> libgusb-devel.x86_64                   0.2.9-1.el7                     @base
> libusb.x86_64                          1:0.1.4-3.el7                   @base
> libusb-devel.x86_64                    1:0.1.4-3.el7                   @base

The most important difference is probably the version of libusb that
is in use. Upstream libusb.info is now at 1.0.21. Please be more
specific about which libusb versions you have on the two systems,
which versions of the OS, and try a newer version if possible.

Regards,
Tormod

[pyusb-users] Centos 7 Usb Barcode scanner not able to read.

[Srujan C. <sri...@gm...>]

Hardware is Dell Precision Tower 3000 Series.





> 
> down vote
>  <>favorite
>  <https://stackoverflow.com/questions/47087054/pyusb-usb-scanner-read-fails-on-centos-7#>	
> I'm trying to implement driver mechanism for usb barcode scanner on Centos.
> 
> Using PyUSB,
> 
> Here is high-level code. I am trying to achieve is to be able to read QR-Codes and BarCodes when someone scans and send it to message queue without user interaction.
> 
> dev = usb.core.find(idVendor=VENDOR_ID, idProduct=PRODUCT_ID)
> if dev.is_kernel_driver_active(0) is True:
>     dev.detach_kernel_driver(0)
> dev.set_configuration()
> dev.reset()
> data = dev.read(endpoint.bEndpointAddress, 120,
>                     timeout=10000)
> currentData = list(chunks(data))
> This code work fine on the same system with Ubuntu operating system. But on Centos 7 , All I hear rapid beeps, and nothing read from the scanner.
> 
> Here is everything installed on Centos, almost similar to Ubuntu that I ran on the same machine.
> 
> "libgusb.x86_64                         0.2.9-1.el7                     @base
> libgusb-devel.x86_64                   0.2.9-1.el7                     @base
> libusb.x86_64                          1:0.1.4-3.el7                   @base
> libusb-devel.x86_64                    1:0.1.4-3.el7                   @base
> libusbmuxd.x86_64                      1.0.10-5.el7                    @base
> libusbmuxd-devel.x86_64                1.0.10-5.el7                    @base
> libusbmuxd-utils.x86_64                1.0.10-5.el7                    @base
> libusbx.x86_64                         1.0.20-1.el7                    @base
> libusbx-devel.x86_64                   1.0.20-1.el7                    @base
> pyusb.noarch                           1.0.0-0.11.b1.el7               @base
> usb_modeswitch.x86_64                  2.4.0-5.el7                     @base
> usb_modeswitch-data.noarch             20160612-2.el7                  @base
> usbmuxd.x86_64                         1.1.0-1.el7                     @base
> usbredir.x86_64                        0.7.1-2.el7                     @base
> usbutils.x86_64                        007-5.el7                       @base"
> Not sure what's the isse.
> 
> If I run, bellow block in loop,
> 
>  print("Waiting to Read")
>  data = dev.read(endpoint.bEndpointAddress, 120,
>                     timeout=10000)
>  currentData = list(chunks(data))
> Output is Waiting to read
> 

[pyusb-users] Looking for a new maintainer

[Wander L. C. <wan...@gm...>]

Hi there all,

A few months I sent a message explaining why PyUSB has been steady for
such a long time. Although my health has strongly improved since then,
things are still ongoing, I don't have time to work as a maintainer
anymore and as such, I am looking a volunteer to take the leadership
of the project.

That said, I don't intend to be a complete strange in the project, I
still intend to participate as an occasional contributor, I just can't
handle the burden of being a maintainer of the project. This has not
only have to do with my health issues but also because I am working
with stuff unrelated to the project nowadays.

I am going to update website and README soon with this new information.

-- 
Best Regards,
Wander Lairson Costa

[pyusb-users] Starizona microtouch focuser

[mohamed k. <eng...@ya...>]

Dear all    I am using ubuntu and I have a python code to move the motor but there is no any response.This is my script:#starizona id (0x10c4,0x82f4)

import sys
import time
import usb.core
import usb.util

# find our device
dev = usb.core.find(idVendor=0x10c4, idProduct=0x82f4)

# was it found?
if dev is None:
    raise ValueError('Device not found')
#print dev

    # set the active configuration. With no arguments, the first
    # configuration will be the active one
    
dev.set_configuration()

    # get an endpoint instance
cfg = dev.get_active_configuration()
intf = cfg[(0,0)]

ep = usb.util.find_descriptor(
    intf,
        # match the first OUT endpoint
    custom_match = \
    lambda e: \
        usb.util.endpoint_direction(e.bEndpointAddress) == \
        usb.util.ENDPOINT_OUT)

assert ep is not None

# write the data
input=1
while input :
    # get keyboard input
    data = raw_input('Enter your command here:')
    if data == 'exit':
        #sys.close()
        input=0
    else:
        #this is requested by my device)
        ep.write(data)
        time.sleep(5)
I appreciate if any one can help me 

Yoursmohamed

Re: [pyusb-users] Errors on Windows 10 (Tried making an issue on github but no response after almost a month)

[Bill G. <chi...@gm...>]

Plus this was an issue / bug report which the readme says to put on github
while questions should be directed towards here.

On Thu, Aug 3, 2017 at 3:48 PM, Wander Lairson Costa <
wan...@gm...> wrote:

> 2017-08-03 17:29 GMT-03:00 Bill Gaylord <chi...@gm...>:
> > Okay. I did not really find the mailing list till now.
> >
>
> I think I have to be more explicit on advertising mailing list, some
> users have complained about that in the past.
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> pyusb-users mailing list
> pyu...@li...
> https://lists.sourceforge.net/lists/listinfo/pyusb-users
>

Re: [pyusb-users] Errors on Windows 10 (Tried making an issue on github but no response after almost a month)

[Wander L. C. <wan...@gm...>]

2017-08-03 17:29 GMT-03:00 Bill Gaylord <chi...@gm...>:
> Okay. I did not really find the mailing list till now.
>

I think I have to be more explicit on advertising mailing list, some
users have complained about that in the past.

Re: [pyusb-users] Errors on Windows 10 (Tried making an issue on github but no response after almost a month)

[Bill G. <chi...@gm...>]

Okay. I did not really find the mailing list till now.

On Thu, Aug 3, 2017 at 3:20 PM, Wander Lairson Costa <
wan...@gm...> wrote:

> Hi,
>
> Sorry for the delay, I posted a response in the issue. Bear in mind
> that request assistance through github issues, possibility I am the
> only person who will see your question, in mailing list, otherwise, a
> lot of people that potentially had similar problems may help :)
>
> 2017-08-03 16:32 GMT-03:00 Bill Gaylord <chi...@gm...>:
> > So I am having odd errors on Windows 10 using python 2.7 64-bit.
> >
> > I will just link to the github issue that the dev seems to ignore...
> >
> > https://github.com/walac/pyusb/issues/186
> >
> >
> >
> > ------------------------------------------------------------
> ------------------
> > Check out the vibrant tech community on one of the world's most
> > engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> > _______________________________________________
> > pyusb-users mailing list
> > pyu...@li...
> > https://lists.sourceforge.net/lists/listinfo/pyusb-users
> >
>
>
>
> --
> Best Regards,
> Wander Lairson Costa
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> pyusb-users mailing list
> pyu...@li...
> https://lists.sourceforge.net/lists/listinfo/pyusb-users
>

Re: [pyusb-users] Errors on Windows 10 (Tried making an issue on github but no response after almost a month)

[Wander L. C. <wan...@gm...>]

Hi,

Sorry for the delay, I posted a response in the issue. Bear in mind
that request assistance through github issues, possibility I am the
only person who will see your question, in mailing list, otherwise, a
lot of people that potentially had similar problems may help :)

2017-08-03 16:32 GMT-03:00 Bill Gaylord <chi...@gm...>:
> So I am having odd errors on Windows 10 using python 2.7 64-bit.
>
> I will just link to the github issue that the dev seems to ignore...
>
> https://github.com/walac/pyusb/issues/186
>
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> pyusb-users mailing list
> pyu...@li...
> https://lists.sourceforge.net/lists/listinfo/pyusb-users
>



-- 
Best Regards,
Wander Lairson Costa

[pyusb-users] Errors on Windows 10 (Tried making an issue on github but no response after almost a month)

[Bill G. <chi...@gm...>]

So I am having odd errors on Windows 10 using python 2.7 64-bit.

I will just link to the github issue that the dev seems to ignore...

https://github.com/walac/pyusb/issues/186

Re: [pyusb-users] How to send VENDOR_DEVICE messages with pyusb?

[Karl P. <ka...@tw...>]

Read this, mostly...

http://www.beyondlogic.org/usbnutshell/usb6.shtml

Or...

something like...

import usb.util as uu
....
dev.ctrl_transfer(uu.CTRL_TYPE_VENDOR | uu.CTRL_RECIPIENT_DEVICE,
blah, wop)


just like any other control transfer


Cheers,
Karl P

chmedly via pyusb-users <pyu...@li...>
wrote:
> I'm basically trying to replicate the setup messages for a
> device that I've snooped using snoopypro. Here's an example of
> a snooped message I can't seem to send with the ctrl_transfer
> method from pyusb. +++URB Header (length: 80)SequenceNumber:
> 4Function: 0017 (VENDOR_DEVICE)PipeHandle: 00000000
> SetupPacket:0000: 00 90 00 00 00 00 85 ff bmRequestType: 00
> DIR: Host-To-Device TYPE: Standard RECIPIENT: DevicebRequest:
> 90 unknown!
> 
> No TransferBuffer+++
> As far as I can tell, Microsoft considers this function
> deprecated and I haven't found much info in general with the
> google for "VENDOR_DEVICE". But there has to be a way to
> replicate these messages. Does anyone have some insight?
> Thanks,
> 
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org!
> http://sdm.link/slashdot_______________________________________________
> pyusb-users mailing list pyu...@li...
> https://lists.sourceforge.net/lists/listinfo/pyusb-users